Tutorial written by : Taran

1. The BIOS that you would like to have a CRC on should be 256k. If you have a 512k or 1 MEG BIOS you will need to reduce the size. To cut a BIOS in to pieces I would suggest downloading the file splitting tool from: JR Split File: http://www.spadixbd.com/freetools/jsplit.htm
Run the jsplit.exe file you downloaded select your BIOS to split, destination directory for the split files, Custom Size for Bytes per flie and finally put in 262144 for the size in bytes.

2. Use the dos executable named md5.exe from ( http://www.fourmilab.ch/md5/ ).
To use this app put MD5.EXE in the same directory as the 256k BIOS you want the CRC number on. Drop to a COMMAND prompt and type: md5.exe "bios name.bin"

3. Take the 32 character string that was output from MD5.exe and put it in your evox.ini file. Put the string under the other "ROM =" lines. Make your new INI entry look like theirs. Start your new line in the INI with ROM = then in quotes put a description 32 CHARACTERS MAX, then put a comma a "0x" followed by your CRC string. and example of this would be: (note the 0x) ROM = "EvoX 2.1", 0x99487615bb30670cb65993388fcf2a63

NOTES

a. If you are using a MultiBoot BIOS when EvolutionX detects your BIOS it only looks at the first 256k of the chip. Another words even if your booted using BIOS2 (A18 grounded) it will show you what is flashed on BIOS1.

b. If you go WAY above the 32 character limit on the ROM CRC description it will hang your Xbox during boot. They you have the fun of fixing a busted Xbox (I was able to boot a DVD with EVO on it when I found this problem hit me).

This tutorials was put together by Taran...
(thanks to all the other tutorials and people on IRC for the help)

Here are a few BIOS CRC's I have ready for EvoX:
------------------------------------------------
ROM = "Complex 4627 v1.02 Debug",0x70D6F0B58D5A7EB84611B76225AD4E08
ROM = "Complex 4627 v1.02",0x70B54E6CD91F59D4932E7ED776F9267E
ROM = "EliteX version 1.0 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "EliteX version 1.1 beta 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "EliteX version 1.1 final 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "EvoX V2.0",0x76FD88337B8D8C1F116F85F3984B98B6
ROM = "EvoX V2.1",0x99487615BB30670CB65993388FCF2A63
ROM = "EvoX V2.2 No Logo",0x220ADE778785CFC3C98BB5EA8BBD8608
ROM = "EvoX V2.2",0x220ADE778785CFC3C98BB5EA8BBD8608
ROM = "EvoX v2.3 Fast Animation",0x220ADE778785CFC3C98BB5EA8BBD8608
ROM = "EvoX v2.3 No Animation",0x92BB4AFBBCBF4CF7DC376418286A8930
ROM = "EvoX v2.3 No Logo",0x855EF706E264351B056124CB538BDF56
ROM = "EvoX V2.3",0x220ADE778785CFC3C98BB5EA8BBD8608
ROM = "EvoX v2.4 No Animation",0xE3CE66B99957A92FDAC40AF951C3F1FD
ROM = "EvoX V2.4",0xE3CE66B99957A92FDAC40AF951C3F1FD
ROM = "EvoX V2.4 err noani",0xE03C7AF969933C821B4375E0D3DB6022
ROM = "EvoX V2.4 err noani nologo",0xE0109F21892D475D1DA1CBECC244C601
ROM = "EvoX V2.4 err noani nologo ybox",0x3E66E6832BC2C5D19C0637AEF00C7EDD
ROM = "EvoX V2.4 err noani ybox",0xD4CC70976EAE2D849627ADDC02997819
ROM = "EvoX V2.4 err ybox",0x6B1EA5E0B1691C4E0B759AE26B4554A3
ROM = "EvoX V2.5 colormod err",0x688497922D63AF6385C8E37E1C19EADA
ROM = "EvoX V2.5 colormod err evox",0x097C581438C69DE515A346D19A9D9C41
ROM = "EvoX V2.5 colormod err noani",0xE1BF3D54A5F347C01645D4CA713568A6
ROM = "EvoX V2.5 colormod err noani evox",0x48626499F85FBAF53A6DFE360F8CDE2E
ROM = "EvoX V2.5 colormod err noani ybox",0x8BC27C5CBE5810B9C6A53C9D95B1DE14
ROM = "EvoX V2.5.colormod.err.ybox",0xFFDCCDDF7DDCF0ADB0C2FC70752BC7A1
ROM = "EvoX V2.5 err noani nologo",0x1ABC74B2B154160FFEE366A8479BF7B7
ROM = "EvoX V2.5.err.noani.nologo.ex",0xDDF255F5D4F4F3912A419FE278116C2D
ROM = "EvoX V2.5 err noani nologo yx",0x3F752E5381C9CC53D5DF8C28F4D68F71
ROM = "X-Ecuter",0x5D540DFBA44B8C7EE3826CBADFA04491
ROM = "Xbox Original 3944",0x542C62CB976A4993C8C5027DFF9638CE
ROM = "Xbox Original 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "Xtender V1.0",0xE89B1A394E21D07E54864C229E9763F0
ROM = "Xtender V1.1",0x542C62CB976A4993C8C5027DFF9638CE