Print

[xess]

Hi all,
   
     I have an xecuter 2.6 on a 1.6 box. I made up a 1mb Bios using X2bios Manager v2.3 with evox.m8.v16 on banks 1&2, x2.5035.v16plus on banks 3&4. I then ftp'd my bios to the hdd and flashed using the feature on the evox dash.

The 5035 works fine as usual. The evox bios will boot to the dash but wont let me launch games/apps/emulators etc, it just freezes.

Am I missing something simple here? I heard the evox bios is problematic as are the first two banks on the chip. Has anyone else had this problem? I really want the two bios's so I can boot to different dashboards.

Cheers

[_iffy]

Since you have an xecuter, i would recomend useing two 5035's. Just make the "big X" colours different.
xecuter bios' are better  for xecuters than evox bios'.

The problem with your m8, i would guess, would be the IGR. Make sure it's set to "more compatible" instead of "quick". Also dissable IGR in the evoxdash. <- when they're both are on, they both try to work.
Also i would use m8plus_1.6.bin instead of m8_1.6.bin. It's newer and the IGR is better.(apperently)

I would still recomend useing two 5035's for your situation. If the 5035's are set up differently (ie: boot order for dashboards)then they will have different hash's and would be different bios' when using X2bios Manager.


I would wait for someone else to confirm this before you go ahead though.

[xess]

I thought the evox.m8.plus1.6 was only for version 1.6b, thats why I used the evox.m8.1.6.

I like the idea of using the two 5035's tho, can any one else confirm I could make them boot to different dashboards using the bank selection switch? Any info on the set up would be great!

Also, when I got in from work tonight I booted up the xbox and deleted a game from the hdd using qwix, rebooted from the avalaunch dash and it started fragging! Would not start with either bios (Looks like I'm gonna have to reflash if I like it or not!) But what would make the Bios just disappear? I'm using Bios's that were supplied with AID, so I would think they are ok? What do you all think?

[_iffy]

first m8plus_1.6.bin is different from m8_1.6.bin

You might have deleted something you shouldn't have. Can you still cold boot a game disc with the chip on?

[xess]

Thanks for your input iffy

[xess]

Its started fragging again tonight. I'm not so sure its bios related tho because it does it with the chip disabled, and it does it with the hdd and dvd drive dis-connected. Does this not point to the eeprom?
I'm hoping it will suddenly just boot like last time, but im stuck for a cure to this fault

[_iffy]

read these...
<link>
<link>
<link>
go slow. It might be something simple and you might not need to do any of this stuff.
BTW- this is sounding less and less like a bios prob.


I know how this sounds but...

Check all your solder points. Look for a broken trace. Look for splatter which made a new bridge. That third link might be on to something.

[xess]

QUOTE(_iffy @ May 6 2006, 05:41 PM)

read these...
<link>
<link>
<link>
go slow. It might be something simple and you might not need to do any of this stuff.
BTW- this is sounding less and less like a bios prob.
I know how this sounds but...

Check all your solder points. Look for a broken trace. Look for splatter which made a new bridge. That third link might be on to something.

Thanks man.
I also have a thread running in the newbie forum for this fault since im sure its not a bios issue anymore.
I took it apart again and had to loosen off the xapt3r (I never soldered to the board) before I could eventually get it to reboot. Any body else had this happen with the xapt3r?
This seems to happen after being dis-connected from the mains for a couple of hours.