Skip to main content
Home▸ Forums▸ 68kMLA▸ Snow Leopard and Classic Mac OS — #59
Post #59 by napabar
Source Forum68kMLA
CategoryNetworking
Post DateTue, 8 Sep 2009 - 00:54
Original URLhttps://68kmla.org/bb/threads/snow-leopard-and-classic-mac-os.18406/
Post
I just found out that Snow Leopard treats old HFS disks as read only, and the Disk Image Utility will no longer create HFS disks!!
Oh you have got to be KIDDING ME! Seriously? So Snow Leopard can no longer create an HFS disk for use with an older Mac? What the hell is wrong with them? I mean imagine ... you need to prep a disk for use with an older Power PC. I mean this is really taking the forced upgrade thing way too far. What is the harm in allowing HFS? It's simply a file structure. I have hope that if MFS could be implemented under Tiger that someone will add HFS to Snow Leopard, which (as I've pointed out) is still currently far more useful and relevant.
It gets worse, but I have to disagree with you on this being Apple's desire to force us to upgrade. These Classic Macs are NOT our production machines! The very reason we have them is because they are antiques, and we like fooling around with them. Cutting off support to them isn't going to make us buy a new machine! We have them because they are what they are.

That being said, I've ran into some more challenges with Snow Leopard. First, the disk mounting utility doesn't seem to launch Disk Copy 4.2 images or older anymore. Disk Copy 6 images mount ok.

2nd, I have a folder where I keep my classic apps and installers. Many are stuffed, but many are just laying around in folders. I noticed most of my un-stuffed file are not showing up correctly. Several apps appear as text files now. Even if I take them to my 6500, and rebuild the desktop, they don't work. It seems the resource fork has been screwed up. A few seem OK, though, so I'm not sure what the difference is. Point is, we can no longer trust that the resource forks are going to work when the bare files are exposed in 10.6.

Solution: On a OS 8.1 or later Mac, create a Disk Image with Disk Copy 6.3.3 large enough to house your retro files. Format it HFS+, and copy all your files to it. Next, covert the image to read only. Now place this image on 10.6, and mount it. As read only, the resource forks will be safe. From this mounted disk image, they can be shared with ZTerm directly to the Mac128k.

Why HFS+ instead of HFS you ask? After all, HFS mounts as read only in 10.6 to begin with. Well, I figure, how much longer will Mac OS X read HFS disks? HFS+ is still the foundation of OS X, and I figure it will be with us for many years as a supported format. A lot longer than HFS I would gather!