Print

[underthebridge]

1.1 Xbox NTSC, X2.1 Lite
Evox 3752 - with the three IGRs disabled
Xecuter2 bios 4977, no animation

When I have the network cable plugged in and I launch an app using Evox, it runs fine.... however, upon choosing "Exit to Dashboard" in the app or using IGR, the box freezes on a Black Screen.

When I unplug the network cable, everything works flawlessly.

I isolated the problem to be stemming from the Network connection. Whether this is BIOS-related or Evox-related, I don't know. However, judging from the overwhelming number of problems experienced by users of X2 4976/77 BIOS, I am betting it IS from the BIOS.

Team Xecuter, this bug has plagued us since 4976, will you fix it please? It's hard to believe that it has been hanging around for so many months.

And btw, I don't see why it's hard to fix if so many people have encountered it. Right now it is happening mainly with v1.1 NTSC xbox, I believe. The 1.0 dudes haven't had any problems from what I've read...

Everyone with the same or similar problem, please post here.

EDIT: I GOT MINE TO WORK, HERE'S SOME THINGS FOR YOU TRY:

- If your modchip has more than one switchable bank, flash it with more than one Xecuter bios.
I used Bank 1 - 4977 Blue nonani (512K),    Bank 2 - 4977 noani (normal).

- Try the color bioses. So far people have had luck with red noani and blue noani.

- Make sure to use X2BM (Xecuter2 BIOS Manager)

- Try using flash utility in Evox, rather than OzxChip flasher.

So far I think the problem seems to point more to the flashing method.
Thanks to all for help

This post has been edited by underthebridge: Sep 4 2003, 03:47 AM

[kapkorn]

i have the smae problem on both bios. same as you said



xbox 1.1
x2 lite plus
4977 bios
evox

[nufan]

theres an entire thread dedicated to this guys.

but i too have a v1.1 console with the same problem, however mines a PAL xbox.

and also i downgraded to the 4975 bios and it still does it, so its not just the 4976/4977 bios like you said.

but yeah it is damn annoying, its sweet just to take the network cable out during normal play so u get no freezes/IGR works fine, however the problem is trying to play online, most of the time i cant use xbconnect because it locks up when i try connect/some1 tries to connect to me, because obviously you need the network cable plugged in for online play.

anyway a fix would be nice, but its been ages now so we could be dreaming, seems to be a problem which its cause is hard to find, making it hard to fix.

This post has been edited by nufan: Jun 18 2003, 07:19 PM

[wildcard]

not just 1.1.  me and 2 other friends all have 1.0.  we all have this problem using 4976.02 bios.

[underthebridge]

I really hope ubergeek reads this... So it's happening on various xboxes, not just 1.1 . There were some people that claimed they don't get this problem -- we still don't know what the condition is for it to not occur...

This post has been edited by underthebridge: Jun 19 2003, 12:02 AM

[Pobbe]

Pretty shure that Ubergeek said on a forum-thread that it was an Evox-related bug, not bios. Try downgrading to 1.8.3285 and see if it helps. Also try disabling IGR in evox, seems like that fixes some problems ppl are having!

[nufan]

QUOTE (Pobbe @ Jun 19 2003, 02:59 PM)

Pretty shure that Ubergeek said on a forum-thread that it was an Evox-related bug, not bios. Try downgrading to 1.8.3285 and see if it helps. Also try disabling IGR in evox, seems like that fixes some problems ppl are having!

lol you don't think we've tried this? tried several evoX versions including this 'stable' one with no luck. I can't even load avalaunch with cable plugged in it just freezes. So yes, the problems not that simple, oh and evoX IGR? well duh thats the first thing i tried, have tried all combo's too (all 3 evox ones off, both evox and x2 bios IGR off, etc. etc.)

[underthebridge]

QUOTE (nufan @ Jun 19 2003, 04:39 AM)

QUOTE (Pobbe @ Jun 19 2003, 02:59 PM) Pretty shure that Ubergeek said on a forum-thread that it was an Evox-related bug, not bios. Try downgrading to 1.8.3285 and see if it helps. Also try disabling IGR in evox, seems like that fixes some problems ppl are having! lol you don't think we've tried this? tried several evoX versions including this 'stable' one with no luck. I can't even load avalaunch with cable plugged in it just freezes. So yes, the problems not that simple, oh and evoX IGR? well duh thats the first thing i tried, have tried all combo's too (all 3 evox ones off, both evox and x2 bios IGR off, etc. etc.)

I am getting problems with Avalaunch also, I can get in but it freezes when launching an app... of course this is with the network cable plugged.

[john316]

The easiest fix (not meaning to sound sarcastic) is to flash your modchip with the Evo-X bios  

[Morglum]

QUOTE (john316 @ Jun 19 2003, 01:43 PM)

The easiest fix (not meaning to sound sarcastic) is to flash your modchip with the Evo-X bios

But the Evo-X BIOS sucks, and lets be honest, it DOES suck.

If this really is an X2 BIOS bug, as soon as Team Xecuter know about it (which by now im sure they do) there will be a fix in a matter of days, so just unplug the damn cable for now and stop being a bunch of whinging babies  

[mrRobinson]

its definitley something the bios can fix.  I never had the problem running D6.ef with any evox, etc. and as soon as i go to 4976.02 i got the freezes with net cable plugged in.

[nufan]

QUOTE (Morglum @ Jun 20 2003, 12:59 AM)

But the Evo-X BIOS sucks, and lets be honest, it DOES suck. If this really is an X2 BIOS bug, as soon as Team Xecuter know about it (which by now im sure they do) there will be a fix in a matter of days, so just unplug the damn cable for now and stop being a bunch of whinging babies  <_<

yeah that really helps when you want to play online doesnt it? fuckin idiot, if the thread doesnt affect you then fuck off and ignore it. As for now theres quite a few of us with the problem just trying to get it out there and compare specs etc.. to try identify the problem. Theres no whinging involved you idiot. I've brought it to the x2 teams attention a long time ago and they have said they don't know, so we're trying to identify the problem further.

This post has been edited by nufan: Jun 19 2003, 07:17 PM

[underthebridge]

QUOTE (Morglum @ Jun 19 2003, 01:59 PM)

QUOTE (john316 @ Jun 19 2003, 01:43 PM) The easiest fix (not meaning to sound sarcastic) is to flash your modchip with the Evo-X bios  But the Evo-X BIOS sucks, and lets be honest, it DOES suck. If this really is an X2 BIOS bug, as soon as Team Xecuter know about it (which by now im sure they do) there will be a fix in a matter of days, so just unplug the damn cable for now and stop being a bunch of whinging babies

First of all, the reason we are "whinging" is because until now there is no fix, and the problem has still been there for months.

Morglum, if you're not getting any freezes or enjoy unplugging the network cable every time, then GOOD 4 U(if you can't help then be quiet). However there are people (including myself) who are greatly annoyed by this bug, and it seems to take forever to get fixed.

I hope that Ubergeek and team can become more active in this

[Morglum]

You guys must listen to the Prodigy or something, coz babies got a temper  

[wildcard]

QUOTE

If this really is an X2 BIOS bug, as soon as Team Xecuter know about it (which by now im sure they do) there will be a fix in a matter of days, so just unplug the damn cable for now and stop being a bunch of whinging babies

if this problem just recently occured and we wanted a quick fix, i can understand your comments.  this problem has been ONGOING for not days, but MONTHS!  it seems like team xecutor is ignoring them from their comments on their forums.  i think we have a right to bitch.  i tried ALL attempts to fix this.  i am using evox 3285, all IGR offm etc, etc   they ALL dont work.  i had 0, zero, nada problem like this with the D6 bios.  so apparently, problem seems to lie with the bios or compatibility issues with evox