Hi,
I've tried the rom verification utitlity but no luck - it reports ROM checksum error and also unindentified rom (although that's not surprising, as the 9700 is not on the list.!)
I've also compared all the ROM dumps I have using FileBuddy. There are 3 for each utility. Each utility's ROM dumps are indetical, so I'm sure that I have a good copy taken with each one.
Apart from the utility that took 4mb - the other 2 which took 3mb dumps - are also identical.
I suggest that the ROM checksum in PowerMacs only validates the Mac OS Toolbox portion and skips the hardware-specific 1MB ROM code. This is because in order to get to to loading the Toolbox the hardware must already be initialised using the 1MB section for this.
Anyway, I guess the real issue is trying to find out on the original ROM simm how much information is contained, and if there is any padding.
From Tattletech (running on the booted PEX) the following information was obtained - which suggests that the 3mb file is the correct size - and also a clue to at what address this part of the rom starts:
I added the ROM checksum information to the code for the ROM Checker:
and then tried it again on one of the 3mb files - which it correctly identified:
So, despite the ROM checksumming failing, I think that the files are good - as the checksum code reported by tattletech on the booted pex matches the information in the dumped rom file.
I also ran the checksumming on the 4mb file - which was also correctly idenitfied. Comparing (using TextWrangler) the 3mb and 4mb files the 4mb is identical to the 3mb file but has extra information at the end. I suggest that this could be the 1mb from the flash chips which it has managed to read - as perhaps all of this is loaded on the live system - much as was suggested that many rom utils only read a 3mb - apart from CopyRom (which wouldn't run on the PEX) and apparently rom grabber. This could also tie-in to the theory about in a normal mac rom 3mb being the toolbox and 1mb being hardware/model-specific.
All files are at: http://www.jkalittle.co.uk/jkalittle.co.uk/digibarn.zip
One final point could be to compare the digibarn flash chips and search for this within the 4mb rom dump - to see if this indeed apended. I'm not sure how to do this.
James.
I've tried the rom verification utitlity but no luck - it reports ROM checksum error and also unindentified rom (although that's not surprising, as the 9700 is not on the list.!)
I've also compared all the ROM dumps I have using FileBuddy. There are 3 for each utility. Each utility's ROM dumps are indetical, so I'm sure that I have a good copy taken with each one.
Apart from the utility that took 4mb - the other 2 which took 3mb dumps - are also identical.
I suggest that the ROM checksum in PowerMacs only validates the Mac OS Toolbox portion and skips the hardware-specific 1MB ROM code. This is because in order to get to to loading the Toolbox the hardware must already be initialised using the 1MB section for this.
Anyway, I guess the real issue is trying to find out on the original ROM simm how much information is contained, and if there is any padding.
From Tattletech (running on the booted PEX) the following information was obtained - which suggests that the 3mb file is the correct size - and also a clue to at what address this part of the rom starts:
Code:
• ROM :
◊ ROM Size = 3,145,728 Bytes
◊ ROM Version = $77D (125)
+ ROM is 32 Bit Clean = Yes
◊ ROM Sub-Version = $39F1
◊ ROM CheckSum = $46001F1B
◊ ROM Start = $FFC00000
◊ MacOS Boot-ROM Name = [None]
+ MacOS Boot-ROM Version = [NA]
+ MacOS Boot-ROM Date = [NA]
+ MacOS Boot-ROM File Version = [NA]
Code:
// Source 3: Tattletech running on PEX
case 0x46001F1B: cout << " PowerMac 9700"; break;
Code:
Macintosh-2:~ test$ /Volumes/1TB/Documents/PEX_ROMS/MacROMChecksum/build/Release/MacROMChecksum /Volumes/1TB/Documents/PEX_ROMS/Digibarn/SIMM/GetRom/ROM\ 01
ROM Length: 3 MiB
ROM Checksum FAILED.
This is a PowerMac 9700 ROM.I also ran the checksumming on the 4mb file - which was also correctly idenitfied. Comparing (using TextWrangler) the 3mb and 4mb files the 4mb is identical to the 3mb file but has extra information at the end. I suggest that this could be the 1mb from the flash chips which it has managed to read - as perhaps all of this is loaded on the live system - much as was suggested that many rom utils only read a 3mb - apart from CopyRom (which wouldn't run on the PEX) and apparently rom grabber. This could also tie-in to the theory about in a normal mac rom 3mb being the toolbox and 1mb being hardware/model-specific.
All files are at: http://www.jkalittle.co.uk/jkalittle.co.uk/digibarn.zip
One final point could be to compare the digibarn flash chips and search for this within the 4mb rom dump - to see if this indeed apended. I'm not sure how to do this.
James.