Topic: Evox Checksum Table For Hacked Bios's (Read 36 times)

Pandoriaantje · « **Reply #16 on:** October 13, 2002, 12:09:00 PM »

The evo2.5 checksum doesn't seem to be working.
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?

erexx · « **Reply #17 on:** October 13, 2002, 12:40:00 PM »

Please Create one of the 1meg image and see if it matches the one provided.
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

Pandoriaantje · « **Reply #18 on:** October 14, 2002, 10:35:00 AM »

i got this one from the 1meg file:

0x5AD8E13005FA3E3383227C4BDB0AD85F

Pandoriaantje · « **Reply #19 on:** October 14, 2002, 10:48:00 AM »

still detects a 2.4 bios

Pandoriaantje · « **Reply #20 on:** October 15, 2002, 03:45:00 PM »

ne way i can modify this so the evoxdash detects a evo2.5 bios?

Pandoriaantje · « **Reply #21 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?

Pandoriaantje · « **Reply #22 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?

erexx · « **Reply #23 on:** October 20, 2002, 05:42:00 AM »

I cant answer your question.
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.

Pandoriaantje · « **Reply #24 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)

s_lipowitz · « **Reply #25 on:** October 23, 2002, 05:03:00 PM »

Yes... just put it in the [BIOS] section

HOT_DOG · « **Reply #26 on:** October 24, 2002, 03:44:00 AM »

Author Topic: Evox Checksum Table For Hacked Bios's (Read 36 times)