Finally got around to Reinstalling a fresh 9.2.2 and still couldn't get my G4 500dp to boot from a CD... Had downloaded DieHard's Bootable CD so I wound up copying that to a portable firewire drive and using it from there to install. Anyway I've got a fresh 9.2.2 on there now! Still has me wondering about CD boot thing though...
i think the only logical conclusion is that the mac os rom 10.2.1 is incompatible with the Dual processor 7400 powerpc chip systems
see my timeline i constructed here:
http://www.oldschooldaw.com/forums/index.php?topic=389.0July 19, 2000 *** these models have 4 ram slots / 3 pci slots + gigabit ethernet
Mac Server G4 450 DP (Gigabit) *MYSTIC 9.0.4 (untill January 9, 2001)
Mac Server G4 500 DP (Gigabit) *MYSTIC 9.0.4 (untill January 9, 2001) *high end model*
Power Macintosh G4 400 (Gigabit) *MYSTIC 9.0.4 (untill January 9, 2001)
Power Macintosh G4 450 DP (Gigabit) *MYSTIC 9.0.4 (untill January 9, 2001)
Power Macintosh G4 500 DP (Gigabit) *MYSTIC 9.0.4 (untill January 9, 2001) *high end model*
Power Macintosh G4 450 Cube 9.0.4 (untill July 3, 2001)
Power Macintosh G4 500 Cube 9.0.4 (untill July 3, 2001)
these systems belong to the "gigabit/mystic" family which has documented incompatibilities with other mac os installations
like i said earlier using an install from these systems on an earler sawtooth motherboard would result in system instability/crashes...
there was some sort of difference with the motherboards from these systems.. my findings were that the oem version of mac os 9.0.4 shipped with these systems was tuned specifically for these motherboards.
theres a document here
http://support.apple.com/kb/TA22055 that details which mac os rom was intended by apple to be used with which machines with which version of mac os
which claims :
Your computer must have the appropriate Mac OS ROM file for the version of Mac OS that is installed. Using the wrong Mac OS ROM file can cause the computer to behave unpredictably and may even prevent it from starting up.
it also lists the mac os rom shipped with these "MP" multiprocessor g4 machines from summer 2000 as mac os rom v4.9.1:
Mac OS 9.0.4 installed on Power Mac G4 MP (Summer 2000)
(CPU software 2.3) 4.9.1
notice that the 9.2.2 update is listed as
Mac OS 9.2.2 Update Mac OS ROM v8.7
it sucks that this chart doesnt list the sawtooth, or the older systems specifically /w 9.2.2 but i think that the logic is that
these systems were supposed to be upgraded with the updates, from their original install of 9.0.4 which would leave them with the 8.7 updated mac os rom.
notice also that the official mac os rom document from apple lists A LARGE NUMBER of different version mac os rom files for mac os 9.0.4
specifically, a different mac os rom version for the "multiprocessor" machines... which leads me to believe.. if the mac os rom files were meant to be
"All encompassing" + "Catchall" then why the FUCK did they have to make so many different versions?


this doesnt make sense... if they could have
had one file work for all of the different hardware.. then why didnt they make this a whole lot simpler? the reason is they couldnt... there are hardware differences to account for, perhaps they could have coded 1 file with all the code for all the machines but this was a feat that they didnt accomplish.. or perhaps theres size limitations of the file.. who knows why but the evidence is clear that they could not accomplish a universal mac os rom.... so this leasds me to the question to those that believe that the 10.2.1 rom is "good for all"... what logic are u basing this on??? for me the evidence is clear... this is not the case..
Mac OS 9.0.4 Retail/Software Update 3.7
Mac OS 9.0.4 installed on iMac (Summer 2000) 4.6.1
Mac OS 9.0.4 installed on Power Mac G4 (Summer 2000) 4.6.1
Mac OS 9.0.4 installed on Power Mac G4 MP (Summer 2000) (CPU software 2.3) 4.9.1
Mac OS 9.0.4 installed on Power Mac G4 (Gigabit Ethernet) 4.9.1
Mac OS 9.0.4 installed on Power Mac G4 Cube (CPU software 2.4) 5.2.1
Mac OS 9.0.4 installed on iBook (Summer 2000) (CPU software 2.5) 5.3.1
Mac OS 9.0.4 installed on Power Mac G4 (with Radeon) (CPU software 2.6) 5.5.1
we last discussed the versions of mac os roms in the "Cd copy" thread here:
http://macos9lives.com/smforum/index.php?topic=1918.0i think its possible that the system u have would perform better if u substitute the mac os rom v10.2.1 with the v8.7 file
you can either just substitute the file or start from scratch with the machine specific version of 9.0.4 originally shipped with your specific mac and then use the updates to get to 9.2.2
i have the updates hosted in a single 177mb file on my mediafire account: normal versions
http://www.mediafire.com/download/mnr89qn6q580nuk/Mac_os_9_Updates.smi.binor the international versions
http://www.mediafire.com/download/wuax8aohuk2i7gw/Mac_os_9_Z-Updates.smi.bini also think that the perspective that the "highest version is best" does not apply to the mac os rom .. and that the files have been specifically tuned for specific hardware/system differences... it is possible that the mac os rom 10.2.1 contains specific code for a multitude of machines/versions
but its also possible that they lost sight of 'best performance' of older systems as they focused more on the quicksilvers + mdds
the 10.2.1 rom originates from an install from an MDD machine. this is a radically different system then the gigabit machines from July 19, 2000
when we remember these systems use an entirely different processor (with no on-chip 256k cache) + an entirely different motherboard (also designation as powermac3,3) it doesnt seem so far fetched does it?
see the powermac g4 chart:
http://macos9lives.com/smforum/index.php?topic=578.0we can argue personal opinions back and forth but
theres one simple way to find out.. for someone to swap out the mac os rom 10.2.1 for the mac os 9.2.2 update rom version 8.7 on the "universal" cd installer and see if it boots mrhappys' DP 500 *from cd*while the install may work once installed via a firewire drive or however mrhappy has installed to work around his cd problem.. it may be that the mac os rom is
responsible for the multiprocessor summer 2000 system not booting from the cd.