Post by: SlaYer on November 19, 2002, 10:52:00 PM
security)The 2 BIOS types are from the EvolutionX and Xecuter2.
Those of you that will now try to use them will notice that the skins which used to show you what bios type/version you have just show "Unknown".
The reason is that the EvoX dashboard uses an MD5 calculation on the first 256K of the bios and then compares it to the "ROM" entries in the "evox.ini" file on the root of the "C" drive. If there is a match it displays whatever name corresponds to that MD5 code on the same line.
Since even that latest EvoX Dashboard (v1.8.2812) still looks only at the first 256K of the bios, if you have a 1MB or 512K you need to split it before attempting to read the MD5 value.
============= End Background Info ==============
Well, to make things esier I have compilied a small list of the MD5 values and all you need to do is just add these lines to the [BIOS] section of your evox.ini file to add recognition, like so:
[BIOS]
ROM = "EvoX 2.6",0xdd3de3542bff7b36cdb0dbe078c27fbe
ROM = "EvoX 2.6 Ej Fix",0x2e1ec59dc8c295b462d5bffa73feaecc
ROM = "EvoX 3.6",cb73b4914bb6c70b66e21377989726a0
ROM = "EvoX 3.6 Ej Fix",0xf754767b388ce7a08bf57304e24c9ae9
ROM = "Xecuter2 1.0",0x8ed3428fd664a999914c40702bf4126c
ROM = "Xecuter2 1.1",0xd040bb919beb57222f2e7bdd3137ba94
NOTE: Do not delete the existing ROM entries, just insert these new lines anywhere next to the others.
Hope this helps out.
Enjoy!
See my last post for the rest of the codes for the "hacked" versions of Xecuter2 v1.0 !!!
Post by: SlaYer on November 19, 2002, 11:36:00 PM
| QUOTE (WickedEast @ Nov 20 2002, 06:29 AM) |
| Great! Thanks for the info. One question (I was never able to figure this out): if Evox determines the BIOS ROM by comparing the MD5 of the BIOS and the ROM entry, then what is the "current" entry used for? |
You're most welcome WickedEast. Glad you found the info usefull. I will also post the MD5 codes of the "colormod & noani hack for X-ecuter2 bios" released by Gallymimu as soon as I get them
To answer your question, the latest EvoX Dash (v1.8.2812) will automatically create the "Current" entry at the very bottom of [BIOS] to try to help you out. The idea is that you can then manually create the "ROM" entry if you think you know what bios you're using but did not give it a name. Otherwise it will still show "Unknown"
So in a sense you can just take the value of the "Current", place a description and add it to your list.
Good catch.
Post by: SlaYer on November 20, 2002, 12:22:00 AM
Post by: SlaYer on November 20, 2002, 05:14:00 AM
[BIOS]
ROM = "Xctr2 v1 E na blu",0xb9c981c01653db282437fea40f3757aa
ROM = "Xctr2 v1 F na blu",0x1b27c7a7c5ea50043a54cb1c22a14a98
ROM = "Xctr2 v1 na blu",0x23f0867c60846e20272ce9e33bdd7121
ROM = "Xctr2 v1 na",0x98fd3f4ba71e593a47f0409abc77abea
ROM = "Xctr2 v1 E na",0x40cf68929ec1807b56f66fbe8f97dc40
ROM = "Xctr2 v1 F na",0x8144977d633402d6fbff3b5516d6b3d0
ROM = "Xctr2 v1 E",0xa8c225b0f80ee87e80c2b3d8f588b158
ROM = "Xctr2 v1 F",0xff43ba5ba464fb3b6c3fddb880a029d0
I have already tested them and all seems to work perfectly.
Enjoy!
Post by: phantazma1 on November 20, 2002, 09:21:00 AM
Post by: Sheytan on November 23, 2002, 05:25:00 AM
Post by: Katonta on November 23, 2002, 10:48:00 AM