Print

[Ubergeek]

The problem that some people get with X2 crashing the box if the network cable is plugged in is a pain in the ass

If you have this problem do the following FIRST !

1) Make sure your bios is not 4x the same image (or 2x with x2 lite)

2) Try the original X2 bios AND ALSO a color hacked version that you made YOURSELF with xbtool (use xbins for all the original sources)

3) Disable BOTH evox IGR and X2 IGR

4) Test with X2 4974 - note any changes

5) 4977 Blue Noani is supposed to fix this or many - try this too ("X2 4977 Blue", 0xc4c2dcb8714c3a0d6cdb40213172f6e7)

6) Disable ALL network protocols except TCP / IP

Also in this thread there are MANY people who have fixed their setup - most of the time it was PC network issues - you may find the solution somewhere here: http://forums.xbox-scene.com/index.php?act...38&t=66706&st=0


If none of the above works for you then you may be able to help us (to help you)

We need to know the following (please be ACCURATE)

1) Type of hack used (modchip / tsop / exploit)

2) Motherboard / MCPX version / dashboard used / bios version

3) Your windows Network protocol setup

4) EXACT description of crash


Please only use this thread if you either fixed your crashing problem with the first 6 tips - or if you still have problems and want to offer some help in a technical manner

pls dont flood the thread with questions or non-technical posts

Don't forget if you solve your crashing problem - post about it here with details to help others

Thanks

This post has been edited by Ubergeek: Sep 2 2003, 10:32 PM

[Knocks]

I used to have this problem.  My Xbox would crash when launching homebrew applications and demos (but not games) from Evox with the network cable plugged in 5 times out of 10, and unplugging the network cable would completely solve the problem.

Then I switched to MXM and the problem disappeared.  Nothing crashed, not a single time.  The exact description of the past problem is as follows:

1) Hack used:  Phoenix BIOS Loader with 4977 BIOS at first, then flashed TSOP with 4977 (crashes continued ever after I flashed the tsop and discontinued using the Phoenix loader)

2) Xbox 1.1, Original Kernel 1.00.4817.01, original dashboard 4920

3) DHCP

4) A typical example of a crash would be launching one of Xport's emulators, and the Xbox would freeze at the intro splash screen.


Hope this helps.

This post has been edited by Knocks: Sep 2 2003, 11:30 PM

[sck]

1) modchip x2.2 lite

2) v1.1 / ? / evox 1.8.3752 / 4977 and 4976.02

3) TCP/IP w/ DHCP (however freezes occur when no PC's are turned on)

4) On first boot of the day (or after xbox has been off for a while), trying to launch an app that has network functions (eg. XBMP, XPort's emus) will cause a freeze on the evox loading screen, or right after the application finish launching. However, if I decide to first launch an app that has no network function, it will subsequently freeze upon return to evox main menu always at the same exact time: approx 3 secs. Reboot of the xbox causes no further freezing whatsoever for both cases.

I will try the dominionx bios to see if it stops the freezing like some others have mentioned.

This post has been edited by sck: Sep 2 2003, 11:37 PM

[miracl]

Hmm,used to have this problem aswell..

After playing games,and then doing and IGR or return to dash in som programs,it would return to Evox,and then hang..
Xbmp would hang after maybe 5mins of movie playback.
Streaming Shoutcast in xbmp worked maybe 2 out of 10 times..

I never have any problem with the network cable unplugged,then the xbox worked fine,never any hangups..

But the problem,in my opinion,is the SNTP thing in the evox.ini,this service uses tcp port 123,wich is disabled in most routers/firwalls,since it's under port 1024,i read that some guy got this problem after buying a new router.so this seems likely to me..
It seems as if the xbox cant get any time update over SNTP,and then hangs.probably cos the return signal from the SNTP server dosn't get any further than the router/firewall.,i just disabled the sntp,and told evox to use local xbox clock..
That's the solution for me.

Think people should try to disable sntp in evox..
And feedback please..

But ofcourse i may be wrong,just saying this worked for me..

Xbox specs:
Xecuter 2 Lite
V1.1,evox 1.8.3752 ,xecuter 4973/4973
TCP/IP,static ip

Edit: My evox clock settings

JumpToMsDash   = Yes
JumpIfNoLink   = Yes
Use24      = Yes
SwapDate   = No
#SNTP_Server   = 194.137.39.68

This works for me atleast..

This post has been edited by miracl: Sep 3 2003, 12:42 AM

[m3talslug]

I'm having this problem.  With the network cable plugged in I get this crash 90% of the time.  

I'm using evox 1.8.3752.  I've disabled IGR, I have an Xecutor 2.0 pro.  I've reflashed it with 4x 4977 just for test purposes and tried this on every 256k bank.

I will be able to boot to the evox dashboard 99% of the time.  When I access apps like MS Dash, any of Xport's emulators, XBMP, etc it will crash.  The only thing these apps seem to have in common is that they are network capable.  When I play games some work and some don't.

All these problems disapear when I have the network cable unplugged.

I thought it was the mod chip but think I tried the audio exploit and I still see the exact same symptoms

I have a version 1.2 xbox.  I have evoX on DHCP.  I've tried with static and applications seem to freeze less frequently on static.

I'm using an NT4 server as my DHCP server.  It configures DHCP clients with the following info:

IP
Subnet
Gateway
DNS
WINS
SNTP
48 hour lease periods

I have no solutions for this problem but to unplug your network cable.  I don't know whether this is a problem with EvoX or the Bios I'm using.  <-- I'm also too goddamned lazy to narrow it down
by playing around with different bioses or dashboards.

*EDIT*  Someone mentioned disabling the SNTP server in EvoX.  I assume that means "Jump to MS Dash" in the "Clock" section.  I set that to Yes and removed the IP address in the SNTP section.  <-- still crashes

[nancy_kerrigan]

Im using X2 bios 4976.02, Xbox Version 1.0, TSOP flashed (i think - theres no modchip left inside). EvoX IGR's off, X2 IGR's left on. Static IP setup pointing to a NT4 DNS server (winroute NAT).

I can get this problem to happen anytime I launch any network apps or games from EvoX (wolfenstien, bruteforce, Xbmp 2.4 etc). Basically the game will load, get through title screens etc then hang. Xbmp2.4 will hang 99% of the time when trying to access relax shares on my PC.

I solved this by running Avalaunch from my EvoX menu whenever I need to run a network based app or game and everything works fine now. Xbmp very, very rarely crashes and all games like Wolf and Bruteforce work fine 100% of the time.

This error used to happen when i was using the EvoXD6 bios too by the way...

[m3talslug]

In light of seeing a post about switching to MXM and having all the problems disappear, I decided to give it a try.  Low and behold, I've tested running several of Xports emus and XBMP and everything works so far.

Looks like I'm switching to MXM!!

I'll post an update if I experience a crash.  Great job Ben Jeremy.

[Alkaline]

I have the same problem you guys are experiencing. Many times evox does not boot.  I'm using x2 4977 red no ani. I have 2 xboxes, on one I have x2 4977 blue no ani and it works fine, perfect boot everytime. My biggest grips are for the xbox with red no ani is:

CRASHES, a lot games play fine but xbmp never works properly, and no matter what I try I can't get it to connect to relax server.

ALSO BIG PROBLEM:
every time I start evox, then turn xbox and turn modchip off via switch I have to re-configure my network settings! seems like everytime I start evox it messes up my xbox's settings and I have to go in and change them back. E.g. on live, I have to go in and change the settings from manual to automatic even though I originally saved them to automatic. Seems like evox keeps changing them to manual somehow, I don't know how but its doing it.

I'm gonna try the x2 4977 blue thats on my xbox no.2 as it seems to work no with no problems.

this is with a 256k cheapmod b.t.w.

This post has been edited by Alkaline: Sep 3 2003, 01:36 AM

[underthebridge]

I did some tests and I narrowed down the problem to the arrangement of bioses on the .bin file flashed, or some problem with the creation of the flash file. In other words, the bug is supposedly not coming from the actual X2 bios.

I tried flashing my X2.1 Lite multiple times with
Bank 1 - 4977 noani
Bank 2 - 4977 noani
Bank 3 - 4997 blue noani
Bank 4 - 4977 blue noani

This ALWAYS produced no problems with each flash, and it is what I have currently.

Now when I tried 4977 blue noani with normal 4997, both of these were getting stuck. This leads me to believe that the problem arises from a certain combination or order of the bioses in the file to be flashed, not the actual bios. So maybe it's X2BM that has the bug...

This post has been edited by underthebridge: Sep 3 2003, 02:24 AM

[BCIcdrz]

would this effect happen when games ether dont start or just lock up, I get this problem alot, i got reg 4977 bios on a cheapmod

[m3talslug]

I'll say it again,

This is not a bios problem!!  This is a problem with the EvoX Dash

Switch to a dashboard like MXM and you'll see that this problem never happens.

This post has been edited by m3talslug: Sep 3 2003, 04:03 AM

[sck]

The only reason this thread was created was because some people claimed that the new dominion-x bios, which was just evox d6 modified caused the network problems to go away. Well, I just got finished testing the dominion-x bios myself and it does NOT solve the network freeze problem. Unless someone else can claim 100% that it solved their freezing problems, I believe it still remains a dash related issue.

[nufan]

i used to long have this problem, i featured ALOT in that thread.

I tried everything, every combo's of bios's etc...

all i can say is that switching to avalaunch fixed this problem. When i ran avalaunch as an app it didnt fix it as obviously evox was still running.

MAKE AVALAUNCH OR SOME OTHER DASH OR DEFAULT IF YOU HAVE THIS PROBLEM AND CHANCES ARE IT WILL BE FIXED

However, for the record, here are my specs etc... as this problem still does happen if i was to have evoX as my default dashboard.

1) Xecuter 2 LITE

2) used all evoX dash's and all x2 bios's

3) connected to router, tried DHCP and STATIC

4) happens if network cable plugged in and using evoX dashboard. Will happen after every IGR and also sometimes at random times during games. Also happens everytime Windows media player plays a movie (within first minute of movie) Also happens when trying to play online (xbc xlink etc..) when you try connect to some1 or some1 tries to connect to you.

To the ppl who are trying to fix this: i guess its something evoX does different to other dashboards ?

This post has been edited by nufan: Sep 3 2003, 04:26 AM

[TechJosh]

I was having a similar problem, and the solution presented itself when I read the changelog to the latest version of xbtool...

QUOTE

1.0.8b7 LBA48 not fully tested! Use this at your own risk! The kernel ID engine rewritten. It should be much more precise, but please report unrecognized or misrecognized kernels. X scale patcher removed. There was an issue with the X scale patch which could cause some BIOSes to hang. May be added back later if anyone wants it. This has been a long standing issue, but no one reported it as a bug. I just happened to discover it while redoing the kernel ID engine. Since it could lead to a frag, I decided to do this release now rather than later. Tested BFM versions of all BIOSes, but not fully tested with all possible options.

I did a custom job on the x2 4977 on xbins with this latest version of xbtool and it worked fine... first time in ages (actually, I found that the bfm bios packaged with a Morden's audio hack installer worked too, but I thought that it was different because it was a bfm bios...).

I think that the problem is not with the bios, dashboard, or network cable, but was merely more visble with certain combinations of them when the bios was edited using older versions of xbtool.  I could be wrong, but at this point I don't care.  Im just happy mine is working .  Hope this helps everyone else having similar problems.

[Troed]

QUOTE (Ubergeek @ Sep 2 2003, 10:34 PM)

The problem that some people get with X2 crashing the box if the network cable is plugged in is a pain in the ass

Oh boy.

*) It's got something to do with EvoX
*) It never happens on v1.0 Xboxes, only 1.1 and upwards
*) The most likely application to freeze is xcommander

... those are my findings. In all cases I've seen this I've been running X-ecuter 4976.02 or 4977. Sometimes switching bios has helped on that particular box, but not on others.

I don't envy the person trying to track this one down ...