Jump to content


Photo

Xecutor 2 4981 Clarification


  • Please log in to reply
6 replies to this topic

#1 datapusher

datapusher

    X-S Member

  • Members
  • Pip
  • 70 posts

Posted 31 July 2004 - 12:05 AM

regarding flashing my bios.

i edited the 4981.06-fixed bios in XBTool to up the fan speed and change the colors.

I then made it 512k in X2 Bios Manager.

I am going to burn it on a cdrw named BIOS with nero and add the dummy.bin file as well.

Was this the correct procedure?

fyi the chip is an xecuter 2.3b lite

Also, in the usual place we look for things there is an info file saying there was an md5 fix and gives the numbers. Do I use those instaed of the md5 that xbtool gives me the option of using "copy to clipboard"

Thanks for your time

#2 Jordan_Hounsell

Jordan_Hounsell

    X-S Senior Member

  • Members
  • PipPip
  • 195 posts
  • Location:Ontario, Canada
  • Interests:Computer, Xbox, Hockey, & Biking
  • Xbox Version:v1.4

Posted 31 July 2004 - 12:10 AM

As far as I know you did everything right. If that doesn't work try making an xiso of the bios and then burn to the cdrw. I'm not sure about the md5 thingy though. Maybe it's just some kind of bug. Why don't you just get the new xecuter 4983's? Then you wont have to worry about that md5 shit.

#3 AlTheKiller

AlTheKiller

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,513 posts
  • Xbox Version:v1.3

Posted 31 July 2004 - 12:35 AM

because 4983.xx doesnt work w/ xbtool...

what exactly is the problem? or is there one? everything sounds fine to me, you dont need to make an xiso.

EDIT: forgot to say, you just put the md5 sum for the fixed bios in evox.ini so a label will show up instead of "unkown bios". if you arent using evox or dont care about the label, you dont have to worry about it.

Edited by AlTheKiller, 31 July 2004 - 12:37 AM.


#4 lordvader129

lordvader129

    He Who Posts Alot...

  • Head Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 17,743 posts
  • Gender:Male
  • Location:Chicago, USA
  • Xbox Version:v1.1
  • 360 version:v5.0 (360S - trinity)

Posted 31 July 2004 - 12:49 AM

rename dummy.bin to abc.bin, just so it gets burned before bios.bin (in alphabetical order)

#5 datapusher

datapusher

    X-S Member

  • Members
  • Pip
  • 70 posts

Posted 31 July 2004 - 01:57 AM

Thanks guys, no there is no problem so far. just wanted to make sure I did it correctly.

Now about the md5 thing.

When I open the fixed 4981 bios I get this md5 from xbtool:
0x06709990921ce7fa6687769437c54111

After I edit in xbtool and then change the size in X2 Bios Manager I get this if I check it in XBTool:
0x36208a4ccde7a374f2644b8f7e90258d

from fixed text file I found in the usual place:
0xca25c9b3721da8c96c4770515dbcda07

Just wondering which one I should put in evox.ini

Thanks all

note reburning dummy as abc.bin


#6 Strud1512

Strud1512

    X-S Hacker

  • Members
  • PipPipPipPipPipPip
  • 2,655 posts
  • Location:Wagga Wagga, NSW, Australia
  • Xbox Version:v1.1
  • 360 version:v1 (xenon)

Posted 31 July 2004 - 02:03 AM

QUOTE
Just wondering which one I should put in evox.ini

After you edit a bios in XBTool the MD5 is changed - use the one from XBTool for the 256kb version.

You would probably want to give it a different description in Evox.ini anyway:
eg. X24981 Fan 40% Blue (or whatever changes you made).

Edited by Strud1512, 31 July 2004 - 02:10 AM.


#7 datapusher

datapusher

    X-S Member

  • Members
  • Pip
  • 70 posts

Posted 31 July 2004 - 02:40 AM

Ok thanks...

so I am understanding that in my evox.ini I will use the one I get after it is edited in xbtool and then x2 bios manager and then re-opened in XBTool to get the md5.

Rom = "X2 4981.06 - Fixed Fan 50% Blue",0x36208a4ccde7a374f2644b8f7e90258d

Yeah it's blue... ha guess everyone makes it blue.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users