Problem #2: There's a script that gets executed to determine whether or not to continue loading the ROM into RAM, or just puke all over itself. So there's still some digging, but at least I can test this on the new powerbook.
I accidentally changed the COMPATIBLE section of the chrp-boot section and bricked my install of 9.2.2 on my TiBook, but that should be easy to rectify.
If all goes according to plan, this *may* culminate in the remote possibility of using a XServe G4 to boot OS9 over firewire (if the onboard IDE chipset is indeed remarkably different, which I dont believe is the case). I've heard the MDD400 is similar to the XServe G4 1.0, so if anybody could look for a chip named PROMISE and tell me what the chip's ID number is, that'd help me determine if this is even feasible.
I accidentally changed the COMPATIBLE section of the chrp-boot section and bricked my install of 9.2.2 on my TiBook, but that should be easy to rectify.
If all goes according to plan, this *may* culminate in the remote possibility of using a XServe G4 to boot OS9 over firewire (if the onboard IDE chipset is indeed remarkably different, which I dont believe is the case). I've heard the MDD400 is similar to the XServe G4 1.0, so if anybody could look for a chip named PROMISE and tell me what the chip's ID number is, that'd help me determine if this is even feasible.