Search results

This is super cool - following this thread!

I don’t care what that book tried to teach me in 1991, I am still putting two spaces after a sentence. See? And again! Ohhhh that’s funny …. The forum software automatically removes the second space when you save your post … ouch

Helpful link, but Basilisk can run 7, as noted above.

Oh look, I even commented in that thread! (but since forgot about it) For the record, the conclusion of that thread was that the model in question was indeed a Macintosh ED (just missing the front wordmark for some reason). So we still have no record of the existence of any Platinum 512Ke...

Ah yes I remember that old image. I decided years ago it was a (220V) Macintosh ED from which someone acetone’d the front wordmark… It would have totally made sense for Apple to sell 512KEs that look like this - just use the Plus front bucket and don’t bother to silkscreen the wordmark there …...

@ClassicGuyPhilly is it worth noting that the Macintosh ED variant of the 512ke came in (I think) only the Platinum color? Also, Wikipedia has for years persisted in saying that there was a Platinum variant of the (non-ED) 512ke (i.e., with no front wordmark, and with a Mac Plus-style unframed...

As written step 6 would work starting from any year, right? For example 1901.

I’ve given this a lot of thought also and implemented a chunk of this a few years ago, then lost interest because … we’ve got time. But yeah we can make almost every application work by patching all of the various OS Utilities and International Utilities routines that mess with date/times...

Very cool (for historical purposes), where did you find it? That circular rainbow gradient is so “look it’s 1987 and I have a Mac II”.

128k’s get a bad rap! They are perfectly great for playing Infocom games, Mouse Stampede, Airborne (with a shorter musical overture sadly) and cooking up some nifty programs in MS-BASIC. And the original MacPaint remains a beautiful piece of software. That said I haven’t turned mine on in 18...

Now available here on the Garden https://macintoshgarden.org/apps/tidymenus

Small bug fix here -- in the edge case where you had the Label menu hidden after a restart and then, without ever pulling down any Finder menu, opened the TidyMenus control panel and un-hid it, the last version would (falsely) report an error but still work. That’s now fixed.

I tested the floppies from my folio-edition Enchanter, Sorcerer, and Infidel (forgot I had that one). The first two disks have gone bad, but Infidel is just as you describe — created 1/1/1904, modified June 1984, and it runs in a normal draggable window and supports desk accessories. Now I’m...

OK. I’ll check my collection too. (I have every Infocom IF game in a box, as well as the earlier folio editions of Witness, Deadline, Enchanter, Sorcerer — if anything I’m guessing these might hold these alleged non-Toolbox versions, of whose existence, for the record, I am very skeptical.)

@jkheiser I find that Digital Antiquarian comment to be … interesting. I would like to know about more it. I played Infocom games on the Mac in ‘84 and they (appeared to) run in ordinary windows, though I recall the windows couldn’t be moved/resized, had no close box and I’m not entirely sure...

All right, I couldn’t stop myself so went ahead and worked out how to do the MacOS 8 thing and, when they “Hide Label menu” checkbox is selected under System 7, move the Label menu to a hierarchical submenu under the ‘File’ menu* instead of just hiding it entirely. This way the Label menu is...

I think both.

Yeah I just checked and there is surprisingly little specific info available online about disk-based MacWrite. It was an important upgrade at the time, and the floppy disks even included the phrase “Disk-Based” printed alongside the original MacWrite “Picasso” style graphic. I think it may be...

That’s true about the original version of MacWrite, but “disk-based” MacWrite came out shortly thereafter (1985? I recall it being a free upgrade that we received in the mail maybe?) and solved this problem. Dog Cow’s point was just that it was indeed solvable.

Thanks @cheesestraws , good idea. Here’s my working code. void Notify(Str255 s) // Notify() allocates a buffer to hold (1) a simple response cleanup proc (defined // with inline machine instructions below), (2) the NMRec that points to the // cleanup proc, and (3) the notification...