Post by: erexx on September 28, 2002, 05:06:00 PM
its a small world
Post by: erexx on September 28, 2002, 09:51:00 PM
Answered my own question.
Add all or just yours to the evox.ini
For those that care here you go:
"The new Evox will use these checksums to identify which bios you are currently running (for those that don't already know)
ROM = "Original 3944",0x542C62CB976A4993C8C5027DFF9638CE
ROM = "Original 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "EvoX 2.0",0x76fd88337b8d8c1f116f85f3984b98b6
ROM = "EvoX 2.1",0x99487615bb30670cb65993388fcf2a63
ROM = "EvoX 2.2",0x220ade778785cfc3c98bb5ea8bbd8608
ROM = "EvoX 2.3",0x057C9D0480FD498C91081DF50DD1F6DD
ROM = "EvoX 2.3 no logos",0x855EF706E264351B056124CB538BDF56
ROM = "EvoX 2.3 no ani",0x92BB4AFBBCBF4CF7DC376418286A8930
ROM = "EvoX 2.3 fast ani",0x9C0654469CC90C33A7D54AC79C374380
ROM = "EvoX 2.4",0xe3ce66b99957a92fdac40af951c3f1fd
ROM = "CPX v1.02",0x70B54E6CD91F59D4932E7ED776F9267E
ROM = "CPX v1.02 no logo",0xA993FCC9D41FAE1C7AB7759077CC77BF
ROM = "CPX v1.02 no ani",0x3621FE90ED6438DFA9E57897B0631E2D
ROM = "Trapflags v1",0x80EE2CFBF7AF617BB42256B572AC6640
ROM = "Trapflags v2",0xAEE3AEA34AC62C823A165DB632A22709
ROM = "Pandora",0xF8D2682275B2EA41EE213FFAAF2FC96A
ROM = "Xtender v1.0",0xE89B1A394E21D07E54864C229E9763F0
ROM = "Xtender v1.1",0x2D5E2953911D278AA38A273C0F6E0E41
ROM = "Xtender v1.3",0x96015F442D345A6FDC9915CAFCBC63A4
ROM = "X-ecuter",0x5D540DFBA44B8C7EE3826CBADFA04491
ROM = "E-X Final 4034",0xE78262E21CE24644415D96D9DF6F64E4
ROM = "E-X Beta 4034",0xF9BA842542D980CB3186FA6EC55F9909
ROM = "E-X Beta2 4034",0x563830D746868117D5AD57AA67203CA2
ROM = "CPX v1.02 Debug",0x8E5C811CCC3C6875FD90C4D0ED6A8ABF
ROM = "CPX 1.02 Debug no ani",0xAC65F68F2706235A578FE1C5FB1E41B1
ROM = "EvoX 2.4 err no logo",0xE0109F21892D475D1DA1CBECC244C601
ROM = "EvoX 2.4 err no ani",0xE03C7AF969933C821B4375E0D3DB6022
ROM = "EvoX 2.4 err ybox nl",0x3E66E6832BC2C5D19C0637AEF00C7EDD
ROM = "EvoX 2.4 err ybox na",0xD4CC70976EAE2D849627ADDC02997819
ROM = "Pandora",0xC87A3FA22D7985B98689B1D9645C2822
ROM = "Bluecop 4627 Debug",0x844ff9e0fc7f7bd01ec5e75b10aece62
ROM = "CPX 4034",0xcf36ad116e2404aff022533b07b11004
ROM = "CPX v1.0 Debug",0xfd1ac8ba0033df93e2da2a23009272e4
ROM = "CPX v1.0",0x4132e24c64b7a8d4ea34ff448051e923
ROM = "CPX v1.02 kina",0x84efef3ee91ac320dab4778881108938
ROM = "Linux v0.1 BL",0xa2146859548ea11d16f5c235aceb45e8
ROM = "Xbox Rec CD Debug",0x3dde2f4a0b772f6619f30c151339b8b7
ROM = "Xbox Rec CD Retail",0x0716573694b60111fe24b834c3531c9d
ROM = "EvoX 2.5 colormod err",0x688497922D63AF6385C8E37E1C19EADA
ROM = "EvoX 2.5 color err evox",0x097C581438C69DE515A346D19A9D9C41
ROM = "EvoX 2.5 color err no ani",0xE1BF3D54A5F347C01645D4CA713568A6
ROM = "EvoX 2.5 cm err na evox",0x48626499F85FBAF53A6DFE360F8CDE2E
ROM = "EvoX 2.5 cm err na ybox",0x8BC27C5CBE5810B9C6A53C9D95B1DE14
ROM = "EvoX 2.5 color err ybox",0xFFDCCDDF7DDCF0ADB0C2FC70752BC7A1
ROM = "EvoX 2.5 err na nl",0x1ABC74B2B154160FFEE366A8479BF7B7
ROM = "EvoX 2.5 err na nl evox",0xDDF255F5D4F4F3912A419FE278116C2D
ROM = "EvoX 2.5 err na nl ybox",0x3F752E5381C9CC53D5DF8C28F4D68F71
There will be no checksums for the multibios releases as they would only show checksums of whatever the last chunk is. And that doesn't tell us anything. Look for updated checksums when we have an EvoX that checksums the entire 8mbit instead of just the first 2mbit.
And for those that haven't figured it out, cm=colormod err=error screen, na=no ani, nl=no logos."
List compiled by ROMRacer
http://www.xboxhacke...951;hl=checksum
Post by: Pandoriaantje on October 02, 2002, 01:37:00 PM
Post by: kanchke on October 03, 2002, 11:58:00 AM
Or am I just talking bull$#!7 here ?
correct me if wrong pls (without the flaming part then
)
Post by: erexx on October 03, 2002, 02:34:00 PM
some mods that are flash upgradable ie.. the Xodus are 256k only
and the PC-Bioxx is 1Mb
In any case the bios can be split or merged for the type of rom/mod used
anyone care to post the crc for the "patched" Evox2.5 bios please do!
Post by: Pandoriaantje on October 03, 2002, 03:17:00 PM
ROM = "EvoX 2.5",0xA306077F8358287DDE13C014C908294A
send any feedback please if it's not correct (i've just made it myself, haven't tested it)
Post by: erexx on October 03, 2002, 08:16:00 PM
Could someone else please verify?
Post by: MrEs on October 03, 2002, 09:02:00 PM
ROM = "CPX 4034",0xcf36ad116e2404aff022533b07b11004
also there are 2 pandor ones?!?!
the one that erexx gave and one that teknojiz gave...
it IS possible that they are both right... can anybody confirm this?
ROM = "Pandora",0xF8D2682275B2EA41EE213FFAAF2FC96A
ROM = "Pandora",0xC87A3FA22D7985B98689B1D9645C2822
Post by: erexx on October 03, 2002, 09:11:00 PM
Some one(s) still need to verify EvoX 2.5 and the Pandora CRC.
Also let's keep one final list.
It would be easy to edit one list every time a new one gets posted and or confirmed....
Or maybe not this looks like a headache
teknojiz do you want to be the editor?
Post by: BLazeD on October 06, 2002, 01:19:00 AM
Post by: teknojiz on October 06, 2002, 11:03:00 AM
ROM = "EvoX 2.5",0xA306077F8358287DDE13C014C908294A
I'm making a final bios list now and double checking the pandora.
Post by: teknojiz on October 06, 2002, 11:33:00 AM
Added CPX v1.03
Moved CPX 4034
I'm still looking into the pandora crc's.
ROM = "Original 3944",0x542C62CB976A4993C8C5027DFF9638CE
ROM = "Original 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "EvoX 2.0",0x76fd88337b8d8c1f116f85f3984b98b6
ROM = "EvoX 2.1",0x99487615bb30670cb65993388fcf2a63
ROM = "EvoX 2.2",0x220ade778785cfc3c98bb5ea8bbd8608
ROM = "EvoX 2.3",0x057C9D0480FD498C91081DF50DD1F6DD
ROM = "EvoX 2.3 no logos",0x855EF706E264351B056124CB538BDF56
ROM = "EvoX 2.3 no ani",0x92BB4AFBBCBF4CF7DC376418286A8930
ROM = "EvoX 2.3 fast ani",0x9C0654469CC90C33A7D54AC79C374380
ROM = "EvoX 2.4",0xe3ce66b99957a92fdac40af951c3f1fd
ROM = "EvoX 2.4 err no logo",0xE0109F21892D475D1DA1CBECC244C601
ROM = "EvoX 2.4 err no ani",0xE03C7AF969933C821B4375E0D3DB6022
ROM = "EvoX 2.4 err ybox nl",0x3E66E6832BC2C5D19C0637AEF00C7EDD
ROM = "EvoX 2.4 err ybox na",0xD4CC70976EAE2D849627ADDC02997819
ROM = "EvoX 2.5",0xA306077F8358287DDE13C014C908294A
ROM = "EvoX 2.5 colormod err",0x688497922D63AF6385C8E37E1C19EADA
ROM = "EvoX 2.5 color err evox",0x097C581438C69DE515A346D19A9D9C41
ROM = "EvoX 2.5 color err no ani",0xE1BF3D54A5F347C01645D4CA713568A6
ROM = "EvoX 2.5 cm err na evox",0x48626499F85FBAF53A6DFE360F8CDE2E
ROM = "EvoX 2.5 cm err na ybox",0x8BC27C5CBE5810B9C6A53C9D95B1DE14
ROM = "EvoX 2.5 color err ybox",0xFFDCCDDF7DDCF0ADB0C2FC70752BC7A1
ROM = "EvoX 2.5 err na nl",0x1ABC74B2B154160FFEE366A8479BF7B7
ROM = "EvoX 2.5 err na nl evox",0xDDF255F5D4F4F3912A419FE278116C2D
ROM = "EvoX 2.5 err na nl ybox",0x3F752E5381C9CC53D5DF8C28F4D68F71
ROM = "CPX 4034",0xcf36ad116e2404aff022533b07b11004
ROM = "CPX v1.0 Debug",0xfd1ac8ba0033df93e2da2a23009272e4
ROM = "CPX v1.0",0x4132e24c64b7a8d4ea34ff448051e923
ROM = "CPX v1.02 Debug",0x8E5C811CCC3C6875FD90C4D0ED6A8ABF
ROM = "CPX v1.02 Debug no ani",0xAC65F68F2706235A578FE1C5FB1E41B1
ROM = "CPX v1.02",0x70B54E6CD91F59D4932E7ED776F9267E
ROM = "CPX v1.02 kina",0x84efef3ee91ac320dab4778881108938
ROM = "CPX v1.02 no logo",0xA993FCC9D41FAE1C7AB7759077CC77BF
ROM = "CPX v1.02 no ani",0x3621FE90ED6438DFA9E57897B0631E2D
ROM = "CPX v1.03 Debug",0xB701B33BD1281E9541970AD9112161C6
ROM = "CPX v1.03",0x21445C6F28FCA7285B0F167EA770D1E5
ROM = "Trapflags v1",0x80EE2CFBF7AF617BB42256B572AC6640
ROM = "Trapflags v2",0xAEE3AEA34AC62C823A165DB632A22709
ROM = "Pandora",0xC87A3FA22D7985B98689B1D9645C2822
ROM = "Xtender v1.0",0xE89B1A394E21D07E54864C229E9763F0
ROM = "Xtender v1.1",0x2D5E2953911D278AA38A273C0F6E0E41
ROM = "Xtender v1.3",0x96015F442D345A6FDC9915CAFCBC63A4
ROM = "X-ecuter",0x5D540DFBA44B8C7EE3826CBADFA04491
ROM = "E-X Final 4034",0xE78262E21CE24644415D96D9DF6F64E4
ROM = "E-X Beta 4034",0xF9BA842542D980CB3186FA6EC55F9909
ROM = "E-X Beta2 4034",0x563830D746868117D5AD57AA67203CA2
ROM = "Bluecop 4627 Debug",0x844ff9e0fc7f7bd01ec5e75b10aece62
ROM = "Linux v0.1 BL",0xa2146859548ea11d16f5c235aceb45e8
ROM = "Xbox Rec CD Debug",0x3dde2f4a0b772f6619f30c151339b8b7
ROM = "Xbox Rec CD Retail",0x0716573694b60111fe24b834c3531c9d
Post by: erexx on October 06, 2002, 12:49:00 PM
Post by: opjose on October 06, 2002, 06:47:00 PM
What are?
ROM = "Bluecop 4627 Debug"
ROM = "Xbox Rec CD Debug"
ROM = "Xbox Rec CD Retail"
I've seen all but these three.
Post by: teknojiz on October 06, 2002, 09:07:00 PM
ROM = "Xbox Rec CD Retail"
These are the bios's on the XDK Recovery CD
ROM = "Bluecop 4627 Debug"
I believe Bluecop was a homebrew release, but dont quote me on that.
Post by: erexx on October 07, 2002, 01:15:00 PM
Post by: Pandoriaantje on October 13, 2002, 12:09:00 PM
maybe it's the fact that my bios is a 1024k file (pcbioxx)?
so when i do a check of the bios with "bios checker 2.01" it reports "Genuine bios found! <<<evolutionX 2.5>>>" but in the evox dash it reports 2.4.
when i split the file up the firts three files are reported as evo 2.4 by bios checker and the last file is the 2.5 bios.
What could be wrong here?
Should i create a checksum of the whole file?
Post by: erexx on October 13, 2002, 12:40:00 PM
Also the EvoX 2.5 bios is the Evox2.4 bios with one minor change.
The EvoX 2.5 Bios is not an "official" Evox bios
Post by: Pandoriaantje on October 14, 2002, 10:35:00 AM
0x5AD8E13005FA3E3383227C4BDB0AD85F
Post by: Pandoriaantje on October 14, 2002, 10:48:00 AM
still detects a 2.4 bios
Post by: Pandoriaantje on October 15, 2002, 03:45:00 PM
Post by: Pandoriaantje on October 18, 2002, 09:55:00 AM
| QUOTE (MrEs @ Oct 15 2002, 01:45 AM) |
| sounds like your 1 meg bios is a MULTIBIOS version, it has 2.4 at the start of the bios (first 256k) but 2.5 at the end of the bios (last 256k) or vice versa |
Well if i split it up the last file is the evo2.5; so the dash should report the versin of the last chunk wich is the evo2.5 (i've split it up and made a chacksum on the mast file wich is reported by bioschecker as the 2.5 bios and it muches the one in the checksum list above).
so detecting the last chunk doesn't work.
i've made a checksum of the whole 1mb file, the dash didn't report it.
so detecting the 1mb file also doesn't work.
and if it is a multi bios why does bios checker report: "Genuine bios found! <<<evolutionX 2.5>>>" then?
maybe i should split the files, tkae the last one (the 2.5) and copy that one into a 1mb file?? but then bioschecker reports 4 chunks of 2.5 bios and doesn't report it as a Genuine bios.
but that doesn't really mather does it?
Post by: Pandoriaantje on October 20, 2002, 05:25:00 AM
| QUOTE (Pandoriaantje @ Oct 18 2002, 03:55 PM) |
maybe i should split the files, tkae the last one (the 2.5) and copy that one into a 1mb file?? but then bioschecker reports 4 chunks of 2.5 bios and doesn't report it as a Genuine bios. but that doesn't really mather does it? |
Nobody can answer this?
Post by: erexx on October 20, 2002, 05:42:00 AM
I do know that the new Evox is checking the
MD5 hashing on first 256K section of bios instead of last section.
I dont understand how a bios checksum gets generated with the fanCbox Utility.
I do know is that once I make a change to a generic Evox2.5 1024 bios image.
I cannot make anymore changes to that newly generated image with fanCbox.
FanCbox will not recognized it.
I get a different MD5 key with each change.
Post by: Pandoriaantje on October 22, 2002, 01:58:00 PM
| QUOTE (erexx @ Oct 20 2002, 11:42 AM) |
| I do know that the new Evox is checking the MD5 hashing on first 256K section of bios instead of last section. |
So that's where the problem is, the original 2.5 has 3 chunks of 2.4 in the beginning and the last one is the 2.5 (that is if you split the 1meg file up).
So compiling a 1meg bios from 4 chunks of 2.5 256k bios images should do the trick i guess.
i'll try it out once i get my 2nd pc back up. (don't have a parallel port on my pc to flash it with)
Post by: s_lipowitz on October 23, 2002, 05:03:00 PM
Post by: HOT_DOG on October 24, 2002, 03:44:00 AM
