xboxscene.org forums

OG Xbox Forums => Hardware Forums => General Hardware/Technical Chat => Topic started by: ytsejam on January 18, 2004, 05:36:00 PM

Title: Why Evox Reads That Bios Unknown?
Post by: ytsejam on January 18, 2004, 05:36:00 PM

I have been running xecuter 4980 bios with no problems.  Evox showed the bios under System Utils/Settings.  I added the hash entries.  I then edited the XBOX logo with XBtools and now bios shows up as unknown.  Any suggestions to get the bios to show up again?

Title: Why Evox Reads That Bios Unknown?
Post by: Xeero on January 18, 2004, 05:37:00 PM

Editing it changes the hash.  Add the new hash.

Title: Why Evox Reads That Bios Unknown?
Post by: ytsejam on January 18, 2004, 05:47:00 PM

Thanks, it's fixed.

Title: Why Evox Reads That Bios Unknown?
Post by: Strud1512 on January 20, 2004, 12:42:00 PM

You have to add the bios' hash entry into evox.ini before EvoX knows what it is by name.
See this thread for a complete list that can be pasted into your INI.

http://forums.xbox-s...ST&f=38&t=43437

Title: Why Evox Reads That Bios Unknown?
Post by: RapBoy on January 24, 2004, 09:39:00 AM

u have to put the codes for the bios in the evox.ini.
here this thread has all the codes and xplians it: http://forums.xbox-s...ST&f=38&t=43437

Title: Why Evox Reads That Bios Unknown?
Post by: duudfromnorway on February 01, 2004, 08:01:00 PM

try edit the rom in evox.ini with the latest bios, you get here

Title: Why Evox Reads That Bios Unknown?
Post by: duudfromnorway on February 09, 2004, 10:08:00 AM

you need to edit you rom list

here are some!
[BIOS]

#
ROM = "X2 4973 1.0 256k",0x94928743972d443385721e5b92e5f7fb
ROM = "X2 4973 1.0 256k",0x7137c693e67554b92873d3ec5cdbb1d8
ROM = "X2 4973 1.0 1mb",0x18ae3a651037c6ac8a7bb19497193c57
# Xecuter2 4973 v1.0 err bioses
ROM = "X2 4973 1.0 err blue 256k",0x2108e89c8af9dc599e968e36278731af
ROM = "X2 4973 1.0 err greyblack",0xf8ea175f240103b40a9012b75c2090b2
ROM = "X2 4973 1.0 err orange",0x1643553d1b7e3e0df44168ca3d921eb9
ROM = "X2 4973 1.0 err orange2",0x21f7fde45eef3a3ded4cea1df356f324
ROM = "X2 4973 1.0 err purple",0x1233c919bd2727c2ff4e6bb6f962fb78
ROM = "X2 4973 1.0 err purpleorange",0x6b76f248de4656ed32f401f6141f8a9c
ROM = "X2 4973 1.0 err purpleorange f",0x1264a52daa0e86466371370fd0790983
ROM = "X2 4973 1.0 err red 256k",0x20433436b4718d75c4999489d34d4802
ROM = "X2 4973 1.0 err redblue",0x30f54976e4d0bf9f4209d2abf6bc7fa5
ROM = "X2 4973 1.0 err white",0xb9a041e73582be89412ce9c3be0dc1b3
ROM = "X2 4973 1.0 err whitered",0xedc808af34f8594fbcfad20dc2dd79e9
# Xecuter2 4973 v1.0 xmas bioses
ROM = "X2 4973 1.0 XMAS err noani 256k",0x7c461eb216db48672e0675daf564ae6e
ROM = "X2 4973 1.0 XMAS err noani 512k",0xf51151c8206d9545f57bb2de8e895d18
ROM = "X2 4973 1.0 XMAS err noani 1MB",0x6f361492a12711a5dfa817907aad72a4
# Xecuter2 4973 v1.0 err noani bioses
ROM = "X2 4973 1.0 err noani 256k",0xf2f8c4e3fc29c847b0050a829832da0b
ROM = "X2 4973 1.0 err noani blue 256k",0x6f4e270ab1056a85d58377b9510a3eab
ROM = "X2 4973 1.0 err noani greyblack",0x9b451a9d461032502af5f6c80273f15a
ROM = "X2 4973 1.0 err noani orange",0x7b8911066591b9bfcb83d020dfc010bb
ROM = "X2 4973 1.0 err noani orange2",0x172bcb1cf9d2321a0b11ef90667f40ab
ROM = "X2 4973 1.0 err noani purple",0xfbdc76f603fb02bb72f0c7d7f6fbda04
ROM = "X2 4973 1.0 err noani purpleorange",0x56347f13fdacc2bfd233cfeb57885b72
ROM = "X2 4973 1.0 err noani red 256k",0x2321ea1b81934015855ebe89e0b7600c
ROM = "X2 4973 1.0 err noani redblue",0x658916109e8ab9ed3d3cf5f241c58b21
ROM = "X2 4973 1.0 err noani white",0xb479f510fbd88167d7e47ced230b41a9
ROM = "X2 4973 1.0 err noani whitered",0xeacb9df2b9c1222e06dfe6d5c94655f0
# Xecuter2 4973 v1.1 bioses
ROM = "X2 4973 1.1 256k",0xb4f9a0c9f363c49751268ed0bd4126e4
ROM = "X2 4973 1.1 256k",0xa154577a223e2de097195dae062a4f10
ROM = "X2 4973 1.1 512k",0x4fc144f5395dc3e59ef984a681c740ee
ROM = "X2 4973 1.1 4x256k",0xc92a29a5db0d7d43abe1ee750b35184b
ROM = "X2 4973 1.1 1mb",0xf6e885e88590c9aa625e3ca5f0744390
# Xecuter2 4974 bioses
ROM = "X2 4974",0x24bff933c4ee6178040ab4b4daf6c6a8
ROM = "X2 4974 blue",0xdefc13e707ae004def6faef030bf6fed
ROM = "X2 4974 blue e",0x3f350289c2ef5fce2576b4b3af215a7c
ROM = "X2 4974 blue f",0xbc30074e1676a9a21afd75f761bd7301
ROM = "X2 4974 red",0x475fde28d0aaeada9ebf932ce2c4beb9
ROM = "X2 4974 red e",0xe9f956274eaf50027984dbaeeeed4481
ROM = "X2 4974 red f",0x81f8db8d8c33cf15c1951b4c54aa1c23
# Xecuter2 4974 nologo bioses
ROM = "X2 4974 blue nologo",0x1a0c398cd2df743ee0431c620a228fe0
ROM = "X2 4974 blue nologo e",0x33e34aef14bacbb7da9b6af54dd5d299
ROM = "X2 4974 blue nologo f",0x38cdf647e913ab48c18c083e4772d4a5
ROM = "X2 4974 red nologo",0x2c968b5d7cb8301aaa8a3fff0bb3c716
ROM = "X2 4974 red nologo e",0x264ce8a8e2fb47e9e7e007c8bf773e07
ROM = "X2 4974 red nologo f",0x6797f132dd392553e7e5c7e191994a3d
# Xecuter2 4974 noani bioses
ROM = "X2 4974 noani",0x31afdc9df4577272f7006be1634fffc5
ROM = "X2 4974 noani e",0x7211257fe524c66b1f748d10aeb920d8
ROM = "X2 4974 noani f",0x5b812ddc682fdd464b8a60fca775d872
ROM = "X2 4974 noani blue",0xaa5fe4306525b8e951fbe0069022572e
ROM = "X2 4974 noani blue e",0xa3f571a3e0c6c5a60a2812c42a30f64d
ROM = "X2 4974 noani blue f",0xcbd70e3bcbf64305ccb8b2ee7ef362a7
# Xecuter2 4974 nologo noani bioses
ROM = "X2 4974 blue noani nologo",0xd87090c540b74bad1e1de6fc552b3ec2
ROM = "X2 4974 MultiVer blue noani nologo e",0x6a302e9de90d210662879f3a2b7535d5
# Xecuter2 4975
ROM = "X2 4975 256",0xFD4332F1A9973EB52CA196C70E35ECE0
ROM = "X2 4975 512",0x131C4CD30F54B4C3D81CB6277F697735
ROM = "X2 4975 1MB",0xE0B3933D0D29580CCEB2ED9D91861DBD
# Xecuter2 4976.02
Rom = "X2 4976.02 256",0x1e259481510639d69c8223f75bd79b9b
Rom = "X2 4976.02 512",0x0d7829378e5fd7d112c617d76cac31d7
Rom = "X2 4976.02 1MB",0x1e259481510639d69c8223f75bd79b9b
ROM = "X2 4976.02 DkBlue NoAni 256k",0x2d667670ef9493b0211a13ed3ce7fc02
ROM = "X2 4976.02 Orange noani 256k",0xd7cbaece6dae5df28a05326ad83d16b2
ROM = "X2 4976.02 Purple noani 256k",0xe8a202a7b3392a3a187cdee08f63e1e9
ROM = "X2 4976.02 Red noani 256k",0x52bd0523971bbe5671beedf9c9d314ab
ROM = "X2 4976.02 Silver noani 256k",0x5faf05479a8b0d45e6744af120e4b45c
ROM = "X2 4976.02 Yellow noani 256k",0x54cc7f3c042bea41278de529210411ba
ROM = "X2 4976.02.noani.nologo",0x547e27a3c0ec33b301725e7b76552b94
ROM = "X2 4976.02.blue.F.256k",0x08846888cdb3329f16e7483727f826cf
ROM = "X2 4976.02.blue-red.F.256k",0x46055fa98962c8089d6d292769fa2078
# Xecuter2 4977
ROM = "X2 4977",0x92987e26edd5833921c9b0e539ea091e
ROM = "X2 4977 Darker Blue",0xd612e7ee1f58a76298d67f39246a8d1c
ROM = "X2 4977 Blue",0xc4c2dcb8714c3a0d6cdb40213172f6e7
ROM = "X2 4977 Blue noani",0xc4c2dcb8714c3a0d6cdb40213172f6e7
ROM = "X2 4977 Gray",0x860746a3d229c8851e1f98d45fad546b
ROM = "X2 4977 Green",0xe853ca313e1e2d57418cf1759ae73f6b
ROM = "X2 4977 Green noani",0xe853ca313e1e2d57418cf1759ae73f6b
ROM = "X2 4977 Orange",0x9dbf36b33590b073e1b5f71f36438b12
ROM = "X2 4977 Purple",0x5888771b9c6308ea5433151cd277a033
ROM = "X2 4977 Red",0x00e4ac5dee193d2bcd14910c89732103
ROM = "X2 4977 Red/red noani",0xaacae34cf419053714b305cf8bdbd129
# Xecuter2 4978
ROM = "X2 4978",0x6e77d14a22f7235a2da3f67e809d1c6b
ROM = "X2 4978 IP = 192.168.0.9",0xd577c8c35720169b0f758c42dddbe18a
# Xecuter2 4978.BUG.FIX
ROM = "X2 4978.BUG.FIX",0xfccf1a68440e486e04c3ad605febef12
# Xecuter2 4978.FIXED.HACKED.LAUNCHER
ROM = "X2 4978.FIXED.HACKED.LAUNCHER 1.0",0x3341291f5030071e3cc8e8eb2ccccb4e
ROM = "X2 4978.FIXED.HACKED.LAUNCHER 1.0.1",0x36e14cf8ed82af2d6e1254bad307baba
# Xecuter2 4978.02
ROM = "X2 4978.02",0x23ed933c4ea395d1a7f30701f68a857d
# Xecuter2 4978.03
ROM = "X2 4978.03",0xe432af482dd624427fc3cf6ce2589489
# Xecuter2 4979.xx
ROM = "X2 4979.06",0x50fe679cbf3882aba9f7bd3d812b7f51
ROM = "X2 4979.06",0x56be0f0146d1a69c0f1e6fa9a9558394 #Repack
ROM = "X2 4979.67",0xf85d1d778ee80a3a9b5f57e4dedd13d3
# Xecuter2 4980.xx
ROM = "X2 4980.06",0xad9ee284ed92e2a9a4598ef79648b103
ROM = "X2 4980.67",0x86127dadc49f5b734d261ea3d971dff3
# Xecuter 2 4981.xx
ROM = "X2 4981.06",0xca25c9b3721da8c96c4770515dbcda07
ROM = "X2 4981.67",0xb6eb9fb7b79795c962b7f998ee4a8694
# EvoX Bios's
# EvoX 2.0
ROM = "EvoX 2.0",0x76fd88337b8d8c1f116f85f3984b98b6
ROM = "EvoX 2.0",0x8d32492e54d372ee50f2d8a056746343
# EvoX 2.1
ROM = "EvoX 2.1",0x99487615bb30670cb65993388fcf2a63
ROM = "EvoX 2.1",0x22122dd961146ab7a24d7ef82786f904
# EvoX 2.2
ROM = "EvoX 2.2",0x220ade778785cfc3c98bb5ea8bbd8608
ROM = "EvoX 2.2",0x5c8078113196d0186c06910a8f6f0201
# EvoX 2.3
ROM = "EvoX 2.3",0xd79bc87c2caa1a50dcc7016adf2ccc0a
ROM = "EvoX 2.3",0xaf5ddbd2aed33d494c9b87270cb51431
ROM = "EvoX 2.3 nologo",0x855EF706E264351B056124CB538BDF56
ROM = "EvoX 2.3 noani",0x92BB4AFBBCBF4CF7DC376418286A8930
ROM = "EvoX 2.3 fastani",0x9C0654469CC90C33A7D54AC79C374380
# EvoX 2.4
ROM = "EvoX 2.4",0xe3ce66b99957a92fdac40af951c3f1fd
ROM = "EvoX 2.4",0xd6908721df3f3d46f94754d341c2cf26
ROM = "EvoX 2.4 err nologo",0xE0109F21892D475D1DA1CBECC244C601
ROM = "EvoX 2.4 err noani",0xE03C7AF969933C821B4375E0D3DB6022
ROM = "EvoX 2.4 err ybox nologo",0x3E66E6832BC2C5D19C0637AEF00C7EDD
ROM = "EvoX 2.4 err ybox noani",0xD4CC70976EAE2D849627ADDC02997819
# EvoX 2.5
ROM = "EvoX 2.5.256k",0xa306077f8358287dde13c014c908294a
ROM = "EvoX 2.5 colormod err",0x688497922d63af6385c8e37e1c19eada
ROM = "EvoX 2.5 colormod err evox",0x097c581438c69de515a346d19a9d9c41
ROM = "EvoX 2.5 colormod err ybox",0xffdccddf7ddcf0adb0c2fc70752bc7a1
ROM = "EvoX 2.5 colormod err noani",0xe1bf3d54a5f347c01645d4ca713568a6
ROM = "EvoX 2.5 colormod err noani evox",0x48626499f85fbaf53a6dfe360f8cde2e
ROM = "EvoX 2.5 colormod err noani ybox",0x8bc27c5cbe5810b9c6a53c9d95b1de14
ROM = "EvoX 2.5 err noani nologo",0x1abc74b2b154160ffee366a8479bf7b7
ROM = "EvoX 2.5 err noani nologo evox",0xddf255f5d4f4f3912a419fe278116c2d
ROM = "EvoX 2.5 err noani nologo ybox",0x3f752e5381c9cc53d5df8c28f4d68f71
# EvoX 2.6
ROM = "EvoX 2.6",0xdd3de3542bff7b36cdb0dbe078c27fbe
ROM = "EvoX 2.6 err",0x6ec4d7dff4ea9761fe93311f0706c2e9
ROM = "EvoX 2.6 err blue",0xb926d7217becbe7a6fe50bf5d8c81704
ROM = "EvoX 2.6 err red",0xc2576469f86955cff6c69fd9f13736e0
ROM = "EvoX 2.6 err noani",0x2044fbe72f370f6ee08e8987356975ef
ROM = "EvoX 2.6 err noani blue",0x6a177b199c7451c15acf86e598b0e604
ROM = "EvoX 2.6 err noani red",0x6a177b199c7451c15acf86e598b0e604
# EvoX 2.6 EF
ROM = "EvoX 2.6 EjectFix",0x2e1ec59dc8c295b462d5bffa73feaecc
# EvoX 3.6
ROM = "EvoX 3.6",0xcb73b4914bb6c70b66e21377989726a0
# EvoX 3.6 EF
ROM = "EvoX 3.6 EjectFix",0xf754767b388ce7a08bf57304e24c9ae9
ROM = "EvoX 3.6 ef",0xf754767b388ce7a08bf57304e24c9ae9
# EvoX d.6
ROM = "EvoX D.6",0xc349c2b047a3d6c2de2e1c10185ecf86
ROM = "EvoD.6 red",0xef744b3cb11a616ca79177170f4841cd
ROM = "EvoD.6 red",0xa2d334ef382382eb1233aa95e9bb1bcd
ROM = "EvoD.6 blue",0x04788b6a2c0ae55a2670d162a71151dc
ROM = "EvoD.6 blue E",0xf21291e0f6c234bbbd1ad0e69bfc463d
ROM = "EvoD.6 blue F",0x6d963467af0a93fc636fae7f50e713c3
# EvoX d.6 EF
ROM = "EvoX D.6 EF",0x74c6235497f474bf88b54b3fc52a20b2
ROM = "Evox D.6EF blue",0x67ea6aa22a3b0e64b68912e41ef7d109
ROM = "Evox D.6EF blue E",0x5272c09256bdfb1cf94a75c11ea45c1d
ROM = "Evox D.6EF blue F",0x1764e6c46898a55c7c601d14bfb7dae8
ROM = "Evox D.6EF noani blue ",0xb2d87f04ef0486851998f35e87f0fb78
ROM = "Evox D.6EF noani blue E",0x1470758c30266c47c031da09aec4b46e
ROM = "Evox D.6EF noani red",0x39b989b3ba404b3a67d9d2ae11dc1c57
ROM = "Evox D.6EF noani red E",0xb63c6ef67db45cab00aad2b603541264
ROM = "Evox D.6EF red F",0xb283ba81df4ca67055331d6fd2893ca9
ROM = "Evox D.6EF noani blue",0xcd3158097fd98aa65ba271024fb6c23a
ROM = "Evox D.6EF noani blue E",0xfc1ae335b061e3a88d04d3bf18d8e55e
ROM = "Evox D.6EF noani red",0xa2d334ef382382eb1233aa95e9bb1bcd
ROM = "Evox D.6EF noani red E",0xa2d334ef382382eb1233aa95e9bb1bcd
# EvoX d.6 EF+ (includes media patch)
ROM = "Evox D.6EF+",0x738e892e7cb1bf90d836eb205b61a667
# EvoX M7
ROM = "EvoX M7",0x93db270779f5b964f50be075a5d5d2d2
ROM = "EvoX M7 ef",0xf0980189407abca8d1f8d823621beaf0
ROM = "EvoX M7 ef noani",= 0x79cb96f56c4e6d153bb57a1a7c62ebd0
# EvoX Other
ROM = "EvoX MatriX TSOP flash",0x6bcd8ee1f06d1c6d804b4c45000cfea4
# Dominion-X Bios's
# Dominion-X 0901
ROM = "Dominion-X 0901 F 256k",0x975d1d8bfc080bea86717f933406c9bb
ROM = "Dominion-X 0901 F 512k",0x975d1d8bfc080bea86717f933406c9bb
ROM = "Dominion-X 0901 F 1Mb",0x975d1d8bfc080bea86717f933406c9bb
ROM = "Dominion-X 0901 G 256k",0x2a6a12ca344fbe6c78effb7981c2a667
ROM = "Dominion-X 0901 G 512k",0x2a6a12ca344fbe6c78effb7981c2a667
ROM = "Dominion-X 0901 G 1Mb",0x2a6a12ca344fbe6c78effb7981c2a667
# BFM Bios's
ROM = "Original 3944 BFM 256k",0x3cfc2ac12b7d8ac87d91d501e1a38d17
ROM = "Original 4034 BFM 256k",0x314126a8c3039af83d1dda22832a2b62
ROM = "Original 4817 BFM 256k",0xe99a37193f8d8ce4f020c616e3861c36
ROM = "Original 5101 BFM 256k",0xd999658167ef1596eeeef951da1bc037
Rom = "X2 4976.02 BFM 256k",0xa94715ee92b7a514cc005ae1f872d493
Rom = "X2 4977 BFM 256k",0xe2fea058eb689a77d614b070a7440dd3
Rom = "X2 4978 BFM 256k",0xd31ae4029bc28fdb859912eb481025c7
Rom = "EvoX 2.6 BFM 1MB",0x865371aa03cc82456181a85ee57f416c
Rom = "EvoX 2.6EF BFM 256k",0x44599c136582a72c5bf5683532604ef3
Rom = "EvoX d.6 BFM 1MB",0x23abe8cf5de4d19cc30119dbf7531817
Rom = "EvoX d.6EF BFM 1MB",0x78e714331995fa8183ebd58d47dbf7e8
Rom = "Original DEBUG 5558 BFM 1MB",0x690eb6b5bb4a43c8ba8bda81dabb9e69
ROM = "TATX Dual Debug BFM",0xe2fea058eb689a77d614b070a7440dd3
# Retail Bios's
ROM = "Original 3944 1MB",0x542c62cb976a4993c8c5027dff9638ce
ROM = "Original 4034 1MB",0xF20CD7574BB4B2A69810B2E9F766A90
ROM = "Original 4132 1MB",0xcf36ad116e2404aff022533b07b11004
ROM = "Original 4817 256k",0xc3db66c8e212974afec6d6087ddbb8ef
ROM = "Original 5101 256k",0x769898e9682e1f5d065b5961460d03e6
# CPX Bios's
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 = "Complex 4627 v1.02 Debug",0x70D6F0B58D5A7EB84611B76225AD4E08
ROM = "Complex 4627 v1.02",0x70B54E6CD91F59D4932E7ED776F9267E
ROM = "Complex 4627 v1.03 Debug",0xB71494C46A6B3010C97AC040E4889DCE
ROM = "Complex 4627 v1.03",0x3D2C1A663C523F08389180A868B3D335
# Hacked/'Scene' Debug Bios's
ROM = "TATX Dual Debug",0xC998CA2882D14B430E8AAC0BC08B045A
ROM = "TATX Dual Debug VGA LameOne",0xe5049c482d96461cad1a245c374653ed
ROM = "Bluecop 4627 Debug",0x844ff9e0fc7f7bd01ec5e75b10aece62
# Xtender Bios's
ROM = "Xtender v1.0",0xE89B1A394E21D07E54864C229E9763F0
ROM = "Xtender v1.1",0x2D5E2953911D278AA38A273C0F6E0E41
ROM = "Xtender v1.3",0x96015F442D345A6FDC9915CAFCBC63A4
# X-ecuter 1
ROM = "X-ecuter",0x5D540DFBA44B8C7EE3826CBADFA04491
# Linux Bios's
ROM = "Linux v0.1 BL",0xa2146859548ea11d16f5c235aceb45e8
ROM = "Cromwell 1.8 256k",0xd5bc60eaf462ee1d697ae2853d93d933
ROM = "OzXBios (Cromwell) v1.26a 256k",0x6d62d25b98a8238748181b609cfb4ace
ROM = "OzXBios (Cromwell) v1.26a 1MB",0xe46ceeb049b1805f8042a58521f02f81
# Trapflag's Bios's (Same features as EvoX 2.2 with.... No ms logo, speeds boot time a bit.)
ROM = "Trapflags v1",0x80EE2CFBF7AF617BB42256B572AC6640
ROM = "Trapflags v2",0xAEE3AEA34AC62C823A165DB632A22709
# Pandora Bios (From the Pandora Modchip)
ROM = "Pandora",0xF8D2682275B2EA41EE213FFAAF2FC96A
ROM = "Pandora",0xC87A3FA22D7985B98689B1D9645C2822
# Others
ROM = "Xbox Rec CD Debug",0x3dde2f4a0b772f6619f30c151339b8b7
ROM = "Xbox Rec CD Retail",0x0716573694b60111fe24b834c3531c9d
ROM = "E-X Final 4034",0xE78262E21CE24644415D96D9DF6F64E4
ROM = "E-X Beta 4034",0xF9BA842542D980CB3186FA6EC55F9909
ROM = "E-X Beta2 4034",0x563830D746868117D5AD57AA67203CA2
ROM = "ALX2-RED",0x5355AA0F40396F68B2D9ED30BFF3BDA2
ROM = "ALX2-BLUE",0xFC16FA0620367B713CD47F8532B7F6BD
#

Title: Why Evox Reads That Bios Unknown?
Post by: lordvader129 on February 09, 2004, 10:17:00 AM

also if you make any changes (boot sequence, colormods, etc) the bios will have a new hash that youll have to add yourself to the .ini

easiest thing is to look right under all the bios where it says "Current = " then copy the hash and paste it into a new ROM definition

Title: Why Evox Reads That Bios Unknown?
Post by: heinrich on February 09, 2004, 10:39:00 AM

QUOTE (dewmonger @ Feb 9 2004, 03:08 PM)

In order to get evox to recognize the bios, you have to edit the evox.ini file to include all the known bios available.  The current evox.ini files only show the evox bios, not the X2 or other bios.  There is actually some lengthy text that you have to add (too much for me to list in this post).  If you do a search for evox.ini bios detection, you can cut and paste that info onto your current evox.ini and it will then show your current bios.

You don't need the whole list, you can just have the 1 that matches your current = line.  

This is all explained in the pinned topic in the bios forum...

Title: Why Evox Reads That Bios Unknown?
Post by: heinrich on February 09, 2004, 10:42:00 AM

QUOTE (damianek @ Feb 9 2004, 03:41 PM)

exectly where do i put that line?

in evox.ini...
there are already several there.

Title: Why Evox Reads That Bios Unknown?
Post by: Xeero on October 22, 2003, 07:32:00 PM

You have X2 4976.02.  It says unknown because you don't have the corresponding MD5 hash in your evox.ini.

Title: Why Evox Reads That Bios Unknown?
Post by: Exobex on October 24, 2003, 07:52:00 AM

If you don't know the MD5 hash, load a copy of the BIOS into XBtool, it'll tell you at the top of the window.  You can then paste this into your evox.ini, adding in the extra bits to put the line in the correct format (look at the other BIOS entries in evox.ini and you'll see what I mean).

Title: Why Evox Reads That Bios Unknown?
Post by: bucko on October 31, 2003, 08:31:00 AM

You don't have the MD5 Sum for the bios in the Evolution X dashboard. There's a pinned topic for MD5 sums in the bioses forum I believe.

Title: Why Evox Reads That Bios Unknown?
Post by: JonDante on October 31, 2003, 08:58:00 AM

Bucko, I think he is talking about from the programmer.  I am pretty sure he is not at the Evox dash level yet.  So the sum is not relevant at this point.

When my programmer comes and I play with flashing, I should understand the errors of the programmer a little better.

JD

Title: Why Evox Reads That Bios Unknown?
Post by: bucko on October 31, 2003, 10:34:00 AM

I need lessons in reading.

Title: Why Evox Reads That Bios Unknown?
Post by: shanafan on October 31, 2003, 08:44:00 PM

http://forums.xbox-s...ST&f=38&t=43437

You need to add the hash value for your BIOS in evox.ini

Title: Why Evox Reads That Bios Unknown?
Post by: jaysoccer7c on November 15, 2003, 11:26:00 AM

add it

Title: Why Evox Reads That Bios Unknown?
Post by: error21 on November 15, 2003, 11:26:00 AM

QUOTE

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....ools/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

or just use a program like xbtool load the bios that your useing and it will say something like "copy md5 to clipboard"
then open up your evox.ini and add it in somewhere in the middle...

Title: Why Evox Reads That Bios Unknown?
Post by: TheButcherJB on November 15, 2003, 12:01:00 PM

Edited and added. Thanks guys

Title: Why Evox Reads That Bios Unknown?
Post by: Kernal on November 30, 2003, 01:27:00 AM

Title: Why Evox Reads That Bios Unknown?
Post by: muggs on November 30, 2003, 03:27:00 AM

What did you do I have the same problem.

muggs

Title: Why Evox Reads That Bios Unknown?
Post by: denright on November 30, 2003, 08:50:00 AM

Everywere i look i get Bios Unknown

If i have a check on my bios in my evox skin it says bios unknown and when i run bois checker agian bios unknown

any ideas??

Title: Why Evox Reads That Bios Unknown?
Post by: Strud1512 on November 30, 2003, 05:38:00 PM

You have to add an MD5 identification string for your bios in Evox.ini

eg
ROM = "X2 4979.06",0x56be0f0146d1a69c0f1e6fa9a9558394

See this thread for a mostly complete list of MD5 strings:
http://forums.xbox-s...ST&f=38&t=43437

(or you can use X2 Bios Manager to generate your own MD5)

And you probably have an older version of Bios Checker that does not recognise newer bios versions.

Title: Why Evox Reads That Bios Unknown?
Post by: *picard* on December 09, 2003, 10:00:00 PM

my evos is displaying unknow as bios.  what do i have to do to have it show what version i have?

Title: Why Evox Reads That Bios Unknown?
Post by: DeTr0iT on December 09, 2003, 10:13:00 PM

It won't..

Title: Why Evox Reads That Bios Unknown?
Post by: chelrob on December 09, 2003, 10:28:00 PM

Find the line in your .ini that says current and copy and paste it to a descriptive line about your BIOS.  Look at the dozens that are already there for the syntax.

Title: Why Evox Reads That Bios Unknown?
Post by: Strud1512 on December 09, 2003, 11:42:00 PM

QUOTE (*picard* @ Dec 10 2003, 08:00 AM)

my evos is displaying unknow as bios.  what do i have to do to have it show what version i have?

Edit your EVOX.INI, add the "ROM = ..." line that matches your bios.
Read this thread for that info:
http://forums.xbox-s...ST&f=38&t=43437

Title: Why Evox Reads That Bios Unknown?
Post by: polarz on December 10, 2003, 01:13:00 PM

Load the bios with XBtool to get it's md5 sum.

Title: Why Evox Reads That Bios Unknown?
Post by: chelrob on December 10, 2003, 01:16:00 PM

Or look in your evox.ini for "current"

Title: Why Evox Reads That Bios Unknown?
Post by: thewickedjester on December 11, 2003, 06:41:00 AM

there is also a program in the downloads section that will identify your bios for you

Title: Why Evox Reads That Bios Unknown?
Post by: one2i on December 11, 2003, 10:32:00 PM

QUOTE (*picard* @ Dec 10 2003, 07:59 AM)

my evos is displaying unknow as bios.  what do i have to do to have it show what version i have?

You can read this nice tutorial here: click here and carefully read the section on Flash BIOS. In it the author explains how evox recognizes your bios and how to add your own. Good luck.

Title: Why Evox Reads That Bios Unknown?
Post by: lookformeb on December 12, 2003, 08:09:00 AM

QUOTE (polarz @ Dec 10 2003, 05:13 PM)

Load the bios with XBtool to get it's md5 sum.

^ do that ^