-
Hey There, I wanted to ask if there was a way to "bless" a disk image without booting up an emulator and double clicking the system folder? To see what makes an imaged blessed I created a new image with the following:
Copied a minimal 7.1 install to this image using:
Attempted to boot from this image, which didn't work (expected). After booting up from a working 7.1 image, I blessed the newly created image by double clicking on the system suitcase and immediately shutting down. Opening these two files in a hex editor, we can see that the start of the image is slightly different: I'm not familiar with HFS enough to know how to go from here. I could just copy this bit over whenever I needed to bless, but that doesn't seem right. Does anyone have any thoughts? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Blocks 0 and 1 hold the boot blocks on an HFS volume. The format is described here. I didn't try to set this up in the volume formatter because I wasn't sure if a "one size fits all" boot block would work generally, since it has executable 68K code in it. There's a flag in the version field that seems to disable execution of code in the boot block, so maybe the code is only needed for specific hardware or older machines? Might be worth playing with to see if there's a general solution that will save a step when creating new system volumes. FWIW, you can save a copy of the boot blocks like this:
and then write them to new image disk images with this:
Additional disks can be written from the two text files. You could also just copy the blocks directly:
(One caution: if you're working with an APM multi-part volume image then you need to specify the HFS volume, or you'll end up overwriting the partition map.) FWIW, here's what I found in an old Mac Classic.
|
Beta Was this translation helpful? Give feedback.
Blocks 0 and 1 hold the boot blocks on an HFS volume. The format is described here. I didn't try to set this up in the volume formatter because I wasn't sure if a "one size fits all" boot block would work generally, since it has executable 68K code in it. There's a flag in the version field that seems to disable execution of code in the boot block, so maybe the code is only needed for specific hardware or older machines? Might be worth playing with to see if there's a general solution that will save a step when creating new system volumes.
FWIW, you can save a copy of the boot blocks like this: