Closed Grieverheart closed 8 months ago
Couple of things: Are you sure Disk-O-Matic is not be able to load your 30 GB image? It should map your file into virtual memory and keep physical RAM consumption to a minimum. It won't be fast, but it shouldn't kill your system.
It's hard to say what's missing because there are a few interconnected pieces here. However:
Hope this helps a bit
About Disk-O-Matic, maybe then I had an issue because there is not enough free space on my hard drive for the virtual memory+output image. Hopefully if you can specify the output directory in a future release it might work.
I hope you don't mind, but I'll dump the contents of the partition information before and after the editing. Note that I also compared the hex output with a file generated by Disk Jockey, and it looked like it should, with only the number of blocks changed. The only other thing I found weird, is that Drive Setup made the volume bootable
, and added 2 boot blocks (signature LK). I also tried zeroing out these two blocks, but that didn't have an effect either.
I compared the binary output again, and found a discrepancy. It was in the reserved fields of the partition map, i.e. the fields after the processor type id. I didn't expect there to be data, so after I parsed/copied that properly, the drive was found! I cannot find any information online about these fields. Do you have any idea what they are used for? They seem to be populated only for the Driver PMs.
Unfortunately that didn't fix the drive corruption I see when I load it on my Quadra. Also, Finder is having a real hard time with the drive, so perhaps it's best if I make a big drive image with just all SIT/CDs and a smaller drive image ~4GB for installing just a few games I'm currently playing.
I have a large image (30GB) which somehow got corrupted when running on a Quadra 840AV. I used
dd
and formatted the image with Drive Setup 1.7.3 and then installed a large number of games.The drive image works fine on Basilisk II so that got me thinking that it might have something to do with the SCSI driver since Basilisk doesn't use SCSI. My idea now was to use the driver partitions generated by Disk Jockey. Unfortunately Disk-o-Matic reads the whole image in memory, so a 30GB image is never going to fit in my 8GB RAM. Instead I learned a bit about how apple disks are structured, and HFS and built a parser for boot0 and apple partition maps. Then, I parsed these from a Disk Jockey image, modified the number of blocks and appended to the modified boot0, partition maps, and driver partition, the data partition from the problematic image. Finally, I loaded the image on my BlueSCSI but the image failed to mount. The drive can certainly be seen, but it fails to mount. Do you know if there are other things I also need to modify, perhaps in the actual data volume to make it work with the Disk Jockey partitions?
EDIT: Maybe it's useful to add, that the way I installed games was using Basilisk and copying the SITs on the Desktop folder, expanding and moving the contents to the disk image. I thought this process might be flawed, but I tried it on two empty drives, one created with Drive Setup and one with Disk Jockey, and didn't have any problems.
Maybe the problem is somehow caused by Basilisk, since it crashed sometimes while installing games. But again, I wonder if I can find out why it's fine under Basilisk.