Well, you are missing the critical difference between the (2) teams, in terms of the bios.
EvoX releases a HACKED version of the MS Bios. That is why they got it out so quick. They simply dump the MS Bios from a 1.6, apply their hacks, and they are done.
X-Ecuter does not do that. Their bios is a lot more complex than that. They do a lot more than just hack the MS Bios, including tons of original coding.
As EvoX had already released the "hacked" 1.6 bios, why would X-Ecuter do the same? That wouldn't make sense. Instead they will take their time and deliver us yet another outstanding X2 Bios, this time with 1.6 support
got it
This post has been edited by smokeingit on Oct 15 2004, 06:05 AM
I'm really lost. I'm trying to get Avalaunch to run on my 1.6 version xbox. I've got the m8_16 evox bios installed. However, I cannot get the avalaunch to run unless I rename it to xboxdash.xbe. For obvious reasons, I do not want to do this. I cannot get XBtool to even OPEN this file, much less edit it. Is there any way I can get the m8_16 bios to run something other than xboxdash.xbe??? Thanks a lot for the help -- I've looked for hours. :blink:
LMAO. You clearly dont know what the hell you're talking about Kafluke.
awsmsteve, xbtool wont edit the M8 BIOS. Evtool however
will edit the M8 BIOS though.
Download it
HERE.
Yeah, I know.... he he. I found that program after I posted last night. I'm glad that its available. Sorry, showing my noobness again!
if you want it to load avalanch you have to rename it to evoxdash.xbe not xboxdash.xbe
that is the boot order.
Actually thats not true either. Like Morglum said, if you use EVtool you can change the boot order too. EVTool is exactly like xbtool but for the evox bios's
I must be missing something about using EVTool. I, too, have the Xecuter 2.6 modchip with a 1.6 Xbox. I have used the X2 Bios Manager to create a bios image with FlashBIOS in bank 1 and Evox M8 v1.6 in bank 2, and everything is hunky-dory.
Now I realize that my current BIOS doesn't have In Game Reset, so I open up m8_16.bin in EVTool, then click "Save As...", call it m8_16_with_igr.bin. Now, when I try to open this file in the X2 Bios Manager, the file is just ignored, leaving 2 empty slots. It seems that the file output by EVTool isn't recognized by X2 Bios Manager.
Am I skipping a step when I edit the BIOS using EVTool? Maybe something involving packing and unpacking?
Thanks for the help!
That's weird, make sure you have the latest version of x2bm. If you do, maybe try an older version?
X2BM v1.1 will open my M8_16 saved from EVTool just fine...I can't tell if there is a problem, and I'm a little bit afraid to flash this onto my XBox. Can anyone tell me if there is an issue here I should know about before I try it out?