As far as I recall, none of the USB drives of the iMac era could read 400/800K GCR disks, they were PC drives that could only use 720/1440K disks. The Imation SuperDisk drives could also use their own 120MB “floptical” disis. Later versions extended it to 240MB, and could also write 32MB to a standard floppy disk. MFS refers to the file system used on 400K disks. 800K disks used HFS.

I wonder why the prebuilt Mac OS 9.2.1 VM has disappeared from the UTM gallery

I learned Objective-C and Cocoa in the days of manual reference counting. I use Swift for new personal projects, I don’t plan to rewrite the old ones in Swift for no reason, but I may add new features in Swift even if not strictly necessary.

The Apple IIc was not a Mac

I did something similar, but targeting macOS on x86_64, so a lot of things were available through catalyst: https://github.com/zydeco/aah

I abandoned it when macs with Apple Silicon were announced, only some simple apps could run (GeekBench would crash through the Lua test iirc)

I made a platinum theme (and a few other mac-like ones) for xfwm some years ago: https://www.opendesktop.org/p/1016308

Ah, so you're the one I have to thank for that! I've used it on Solus and a few others after my dual 867 "Mirrored Drive Doors" machine went down. Thanks!

Will it have a spatial file manager?

Pre-T2 macs had eficheck to verify the EFI's integrity, but with the T2 being so secure, it's not necessary anymore: https://openradar.appspot.com/radar?id=5020911870672896

How are these hackers modifying the EFI section without any kind of digital signature? It's really wide open for writing on all new Macs?

The EFI firmware is validated by the T2, which then passes it on to the x86 CPU. I assume this modification would not persist after the T2 reboots.

Unfortunately, this is not the complete picture. The T2 simply programs the embedded flash within the PCH over an eSPI interface. Meaning, a successful reprogram from the T2 WILL persist until the following occurs:

- A T2 Restore

- A macOS System Update

rickmark here: Sorry no, that's inaccurate. The T2 provides MacEFI.im4 to the Intel processor by emulating a flash controller over eSPI. So by modifying this file, and removing signature checks you can run any payload you like (see the EFI replacement video)

So there is some kind of signature defeat involved, correct?

Yes, sigchecks had to be patched out of the kernel. And yes, it does not persist T2 reboot, but T2 only reboots if you hold power button for 5 sec. MacOS "reboot" does _not_ reboot T2.

Not to be confused with Vapor (https://vapor.codes), the server-side Swift framework

Yeah, could've chosen a better name. I thought it was a fork of this or something.

or Vapor (https://vapor.laravel.com), the serverless PHP platform

That wasn't the QuickDraw that came to my mind

API docs for that can be found here:

[PDF] https://developer.apple.com/library/archive/documentation/ma...

Because Google's is named "Quick, Draw!"

For a reference: https://quickdraw.withgoogle.com/ / https://experiments.withgoogle.com/quick-draw

// This and some variation of "Quick, Draw" was presented two (?) years ago in many meetups (co-)organized by Google.

Edit: Also worth taking a look at: https://www.autodraw.com/ / https://experiments.withgoogle.com/autodraw

Ok, we've put in some punctuation above.

Thanks dang!