Maximum disk image size?

[fdanapfel]

Trying to run dingusppc with a disk image file that is about 8.5GB (its an image of the phyical disk in a Power Mac 8500 created with the Initiator mode of BlueSCSIv2 Desktop):

% ll -h "/HD Images/Mac/PM8500/HD00_imaged.hda"
-rwxrwxrwx@ 1 frank  staff   8.5G Jan  1 00:00 /HD Images/Mac/PM8500/HD00_imaged.hda

dingusppc drops into the debuger with an error stating that the image file is to large:

% ./run_emu.sh
Device Bandit1 Settings
------------------------------------
                  pci_A1 : 
                  pci_B1 : 
                  pci_C1 : 
Device AdbBus Settings
------------------------------------
             adb_devices : Mouse,Keyboard
Device Escc Settings
------------------------------------
          serial_backend : null
Device Sc53C94 Settings
------------------------------------
                 cdr_img : 
                 hdd_img : /Users/frank/Documents/HD Images/Mac/PM8500/HD00_imaged.hda
Device MeshTnt Settings
------------------------------------
                cdr_img2 : 
                hdd_img2 : 
Device Swim3 Settings
------------------------------------
                 fdd_fmt : 
                 fdd_img : 
             fdd_wr_prot : on
Device ControlVideo Settings
------------------------------------
            gfxmem_banks : 3
             gfxmem_size : 4
                  mon_id : Multiscan20in
Device Chaos Settings
------------------------------------
                   vci_D : 
                   vci_E : 
Device Sixty6Video Settings
------------------------------------
           has_composite : off
              has_svideo : off
Device MachineTnt8500 Settings
------------------------------------
                     cpu : 604
                    emmo : off
           rambank0_size : 0
          rambank10_size : 0
          rambank11_size : 0
          rambank12_size : 0
           rambank1_size : 128
           rambank2_size : 128
           rambank3_size : 0
           rambank4_size : 0
           rambank5_size : 0
           rambank6_size : 0
           rambank7_size : 0
           rambank8_size : 0
           rambank9_size : 0
BootROM path: /Users/frank/Downloads/Macintosh/ROM/Old_World_Mac_Roms/4MB ROMs/1995-08 - 9630C68B - Power Mac 7200&7500&8500&9500 v2.ROM
Execution mode: 0
(   0.269s)              scsihd.cpp:63    FATL| ABORT: ScsiHD,0: image file too large

Welcome to the DingusPPC command line debugger.
Please enter a command or 'help'.

FFF00100: dingusdbg> quit
./run_emu.sh: line 2: 52534 Abort trap: 6           ~/Source/dingusppc/build/bin/dingusppc.app/Contents/MacOS/dingusppc -m pm8500 -b "/ROM/Old_World_Mac_Roms/4MB ROMs/1995-08 - 9630C68B - Power Mac 7200&7500&8500&9500 v2.ROM" --rambank1_size 128 --rambank2_size 128 --mon_id Multiscan20in --hdd_img "/HD Images/Mac/PM8500/HD00_imaged.hda"

The run_emu.sh script looks like the following:

% cat run_emu.sh 
#!/bin/sh
~/Source/dingusppc/build/bin/dingusppc.app/Contents/MacOS/dingusppc -m pm8500 -b "/ROM/Old_World_Mac_Roms/4MB ROMs/1995-08 - 9630C68B - Power Mac 7200&7500&8500&9500 v2.ROM" --rambank1_size 128 --rambank2_size 128 --mon_id Multiscan20in --hdd_img "/HD Images/Mac/PM8500/HD00_imaged.hda"

What's the maximum disk image size supported by dingusppc?

[dingusdev]

It's 8.3 GB (8,589,934,080 bytes - 512 x 0xFFFFFF). You just went slightly over that.

[joevt]

The main fork outputs an error if the disk image for a SCSI HD is ≥ 8 GiB (8.5899 GB).
My fork has a commit to fix this: scsihd: Remove 8 GiB limit.
You should be able to apply it to your fork and try again.

For ATA hard disks, I have a commit to support LBA48: atahd: Implement 48-bit LBA (in progress).
It says (in progress) because I haven't done a lot of testing for it. I think Mac OS 9 supports LBA48. I'm working on new kexts for Mac OS X for the OHare/Heathrow ATA devices and the B&W G3's CMD646. Open Firmware doesn't support LBA48 for those devices. Open Firmware has a bug with OHare/Heathrow ATA where LBA28 is not detected correctly so it's limited to CHS. I have Open Firmware patches to fix Heathrow ATA LBA28 support in Open Firmware. A larger patch loaded from disk can add LBA48 support in Open Firmware for Heathrow ATA.

[fdanapfel]

@dingusdev

It's 8.3 GB (8,589,934,080 bytes - 512 x 0xFFFFFF). You just went slightly over that.

Thanks for the quick reply and the clarification.

Are there any plans to lift that restriction?
And what is the reason for this limitation?

On real hardware much larger disks can be used without issues.

[fdanapfel]

@joevt

The main fork outputs an error if the disk image for a SCSI HD is ≥ 8 GiB (8.5899 GB). My fork has a commit to fix this: scsihd: Remove 8 GiB limit. You should be able to apply it to your fork and try again.

Thanks (also for the quick response)! After applying joevt@5a1492a to my local fork of the main repo I'm now able too boot the emulated PowerMac 8500 from the disk image of the real machine.

For ATA hard disks, I have a commit to support LBA48: atahd: Implement 48-bit LBA (in progress). It says (in progress) because I haven't done a lot of testing for it. I think Mac OS 9 supports LBA48. I'm working on new kexts for Mac OS X for the OHare/Heathrow ATA devices and the B&W G3's CMD646. Open Firmware doesn't support LBA48 for those devices. Open Firmware has a bug with OHare/Heathrow ATA where LBA28 is not detected correctly so it's limited to CHS. I have Open Firmware patches to fix Heathrow ATA LBA28 support in Open Firmware. A larger patch loaded from disk can add LBA48 support in Open Firmware for Heathrow ATA.

Good to know. But I don't have any Macs that support ATA devices, all the old Macs I have only use SCSI disks.

Btw. I first tried to just do a build of dingusppc using your fork, but with that the emulated PowerMac 8500 would not boot from my disk image. It just hangs with a grey screen. I guess there are other changes in your fork that make it incompatible with the disk image I'm trying to use.

[joevt]

My fork should boot everything that the main fork does. If there's an issue then it's a bug that I should fix.

The SCSI disk image limit has been removed in the main fork. See latest commit: scsihd: Remove 8 GiB limit.

[fdanapfel]

My fork should boot everything that the main fork does. If there's an issue then it's a bug that I should fix.

The SCSI disk image limit has been removed in the main fork. See latest commit: scsihd: Remove 8 GiB limit.

Thanks for helping to get this fixed.

Have to give your fork another go at some point to figure out why I can't boot my disk image with it.

[joevt]

Have to give your fork another go at some point to figure out why I can't boot my disk image with it.

You can post info in a new issue in my fork, or we can discuss in the dppc-help channel of the DingusPPC discord. Need the command line, info about the disk partitions, and maybe a copy of the nvram.bin file.

[fdanapfel]

You can post info in a new issue in my fork, or we can discuss in the dppc-help channel of the DingusPPC discord. Need the command line, info about the disk partitions, and maybe a copy of the nvram.bin file.

Fyi. your fork at https://github.com/joevt/dingusppc doesn't allow the creation of new issues. If you can enable this then I can provide the requested info there.

For various reasons I don't use discord, therefore I won't be able to have a discussion about this there.

[joevt]

Fyi. your fork at https://github.com/joevt/dingusppc doesn't allow the creation of new issues. If you can enable this then I can provide the requested info there.

Fixed.