X2 5032 Config Editor

jasmine1

Junior Member
Apr 15, 2005
13
0
Here's an x2config.ini editor for the 5032. Added FTP support so that the settings can be sent straight to the box without saving first.(Gives me a problem sending the first time with ZoneAlarm, though I don't know why!) Still allows patching of the LBA48 Mode and can create a 1024k(1meg) bios for those who need it. I found no bugs but all feedback is appreciated. Make sure to have VB6 runtimes installed.

Here's the evox.ini sigs for the 5032 bios:

Rom = "X2 5032 vOld",0xa47668b5365f10d7dc5f5310f89098a3
Rom = "X2 5032 v16plus",0x20734e290550230cf3106d4afe8b12e1


jasmine1
 

dandoon

Junior Member
Nov 11, 2003
13
0
I dont know if its me or not but when i take the MD5 from x2bm2.3 its not working and when i look at the ini file at CURRENT= its not the same so i copy the current and put it in Rom = "X2 5032 vOld" and its works... the same thing with 5031 bios and the MD5 published in the forums.
 

Big_Whoopin

VIP Member
Jan 29, 2004
811
0
SE Pennsylvania, USA
dandoon, I haven't looked up why but it appears EvoX is pulling the hash in some other way. See my post here- http://www.teamxecuter.com/forums/showthread.php?t=30488&page=2&pp=10#post123423 The post was in regards to 5031 but I'm seeing the same thing with 5032 and EvoX. What the dash reports is not the MD5 hash I get on my PC. It looks to me to be an EvoX thing and if I feel like figuring it out I'm going to approach it from that angle.

I did confirm that unlike when you would change logo colors in the 4xxx series bios, if you change your ini it does not change what EvoX decides to find as a hash. Or at least it didn't the one time I tested it... which admitedly isn't very thurough.

-Whoopin'

Edit- that "same thing" I'm seeing is EvoX screw the hash... not the dash path problem that was the main body of the linked post. Just to clarify! (opens mouth, inserts foot.)
 
Last edited:

LoUiS

Noob Account
Jan 5, 2004
6
0
Aix la Chapelle
Hi jasmine1,

jasmine1 said:
Here's the evox.ini sigs for the 5032 bios:

Rom = "X2 5032 vOld",0xa47668b5365f10d7dc5f5310f89098a3
Rom = "X2 5032 v16plus",0x20734e290550230cf3106d4afe8b12e1

jasmine1
thanks for you ini Editor. I have also some problems to get the correct md5 checksum. How did you get the results you posted above? What are the differences, when i generate the md5 on my WinXP? I'd like to understand what i am doing wrong.


Thanks
LoUiS
 
Last edited:

dandoon

Junior Member
Nov 11, 2003
13
0
Big_Whoopin: I just know when i take the hash from CURRENT= i see in EVOX the BIOS name and when i take if from x2bm2.3 not i check 5032 and 5031 bios
 

jasmine1

Junior Member
Apr 15, 2005
13
0
MD5 Hash

EvoX only looks at the first 256k of the bios for the MD5 hash. If you split the bios with a file splitter into two 262,144 byte files and then get the MD5 from the first half, you will see the above MD5 values. DO NOT FLASH YOUR TSOP OR MOD WITH THE SPLIT FILE!!!

jasmine1
 

Big_Whoopin

VIP Member
Jan 29, 2004
811
0
SE Pennsylvania, USA
Cool, thanks jasmine1. Maybe if I spent some time around EvoX forums I may have picked this up, but I'm just enjoying myself too much here. :D Wonder it they'll ever switch it up or provide an option to toggle. Couldn't figure out just what I was missing but now I know.

So help me, if someone quotes GI Joe well I'll just... er, I'll call their sister an unrequested silly thing!

-Whoopin'
Bizarre mode is on!
 

LoUiS

Noob Account
Jan 5, 2004
6
0
Aix la Chapelle
jasmine1 said:
EvoX only looks at the first 256k of the bios for the MD5 hash. If you split the bios with a file splitter into two 262,144 byte files and then get the MD5 from the first half, you will see the above MD5 values. DO NOT FLASH YOUR TSOP OR MOD WITH THE SPLIT FILE!!!

jasmine1
Hi Jasmine1,

thank you very much for your answer, now i understand. :)


Ciao
LoUiS
 

Big_Whoopin

VIP Member
Jan 29, 2004
811
0
SE Pennsylvania, USA
For me at least, EvoX is my backup dash and Ava is my primary. I'm considering moving to XBMC but for the time I'm pleased with Avalaunch. EvoX mostly just sits there collecting digital dust, but I'll crack it out when trying out new bios releases. :) It's old and done, but since I don't d**k with it I know that it's gonna work if I need it.

-Whoopin'
 

snackpants

Noob Account
May 6, 2005
2
0
So is Avalaunch the dash of choice these days? I never really liked the interface, Evox just seemed simple.