Print

[zbuffer]

I'm having the issue where I used the patch through Craxtion, for my Brute Force HD Backup, and it always freezes during the loading screen... same spot everytime..
Is the conclusion that there is nothing to fix this??

[psxweb]

i've seen that you are a lot to have this prob
i'm mounting modchip every day and i've seen that all these network software are freesing on a cold boot
with evox but if you put avalaunch or nexgen you'll don't have the prob

I'ts not an hardware prob but a simple bug in the evox network i 'think

[cyberbadboy]

Had some trouble like that, all i did was unplug my connections inside the xbox (yellow power cable for the cd rom) hooked everything back up and (No more freezing) it works fine, so my statement is to make sure ur everything is put back the way you found it.

[slidellsimba2]

i deleted any xbox dashes i want using including the original one and i dont get lockups anymore

just some advice maybe it was something minor that i changed too but i doubt it

[007_xbox]

cYtr0x, i know exactly what your talking about, both me and my brother own an XBOX, 1.1 and get the same lockups. As you said, its entirely random the lockups. My mate however recently purchased a 1.2, and belive it or not, no lockups!! We havn't once seen it lockup yet after 2 weeks a playing games/XBMP and evox. As i said in my previous post, when this happens, deleting the E/tdata/0face007/system.bin file seems to temporarly fix this problem. I spoke to a couple of people about this problem before, and they said this problem only arose when the x2 bios became multi (1.0 and 1.1). Any one with any advancements, please post!!

[cYtr0x]

Thx for the response.

Interesting that the 1.2 units don't display the same symptoms as the 1.1 units (this reinforces the belief that the x2pro hardware itself is not to blame). I will agree with you that perhaps the problem relates to the bios itself ... but if that's the case, I have to question the EvoXd6 bios too.  Perhaps multiversion bios's really aren't completely finished for the 1.1 xb0x ... however, for the timebeing this remains (in my mind) unproven.  As for the file you suggested deleting, it is not present on this 1.1 xb0x - so it would seem to not be an issue.  As such, I have continued testing...

Overheating theory:
As stated before, indeed the 1.1 box does probably have more uncirculated air that the 1.0 model due to the unpresent heatsink fan.  The addition of a larger drive seeking over more area would also introduce some additional heat. I decided that venting some of that heat could easily be accomplished by removing the cover (I did this last night before a syslink halo match between the two boxes).  After doing so the xb0x worked flawlessly all night and today... until...

Networking buggyness:
Wakeboarding Extreme and UFC Tapout and Halo all ran fine on the 1.1 xb0x today throughout quite a bit of testing.  No lockups booting games, after IGR (I have it re-enabled via the x2 bios since disabling it was not a solution), during gameplay or within EvoX.  As s00n as I turned on the 1.0 xb0x (which had been off all day), halo locked up on the 1.1 xb0x.  Subsequent attempts to begin a system link game between the two boxes resulted in repeated lockups of the 1.1 b0x.  This does NOT occur in the same place each time - sometimes it's in Evox, other times its occurs in game after boot and yet other times this occurs when trying to begin a system link game (again very inconsistent and non-reproducable at times) Immediately following this observation, I was able to play other non-systemlink games on the 1.1 xb0x without any lockups whatsoever.  Also bear in mind that Halo worked PERFELCTLY last night with NO variables changed from then to now.  At one point, I turned the 1.0 xb0x off and the 1.1 box quit locking in halo - then as s00n as I turned the 1.0 b0x on again, the 1.1 locked IMMEDIATELY.  As you can see, some of the findings are conflicting.  However, I still have some troubleshooting avenues to explore - because IF it works sometimes, then it should be reproducable or isolatable (or so logic dictates).

I find myself asking ... "is it all co-incidence?"  I have spent several years troubleshooting extremely technical and sensitive technology  for a living .. but this issue has had me fooled for quite some time now.  Why did syslink halo work flawlessly last night and lock like mad today when nothing had been changed?  I feel confident in saying it has nothing to do with overheating at this point.  I will continue examining the network setup bugginess theory and possibly try a few other bios images.   I'll check in again s00n...

-cYtr0x-

[007_xbox]

QUOTE

you know, my friend had problems with his xbox locking up. all he did to fix it was go over his soldering job and move to the alternate d0. problem solved.

Im gonna giv this a go, see if it makes a difference.

[cYtr0x]

Yeah - I saw that, thanks!  It's worth checking out at this point, so  I may give that a go as well...

... Let me know how that works out for you.

-cYtr0x-

[mrRobinson]

i know it makes no sense but my problem was fixed when i went from the 4976.02 normal to the 4976.02_color_noani
its easy to test at least to see if it helps, before you rip your box open again.

[nufan]

we used to play it heaps so im gonna flash my bios back and see if that helps, although if i go back too far i will have to start patching games or something i guess.

at least we have given specs and let people know, the x2 team seems to be ignoring this problem i guess because they dont know how to fix it. At least bringing it to their attention like this may make them try and fix it.

Its an annoying problem and i wish i could fix it cause xbconnect kicks ass and i miss it

[wildcard]

does anyone know if bios 4977 fixes this problem?

from mine and my friends experience, it seems like we have isolated this problem the bios.

both of us have used D6 bios prior, never had any freezes.  updated to 4976.02 bios, then all the problems with freezes, especially on XBMP 2.4.  disabled all IGR helped but still freezed with network cable in.  network cable out, i get no freeze.  my friend flashed back to the old 4975 bios and he says he get alot less freezes.  if this new bios does not relieve the freezing problem, im go back to 4975.

[nufan]

really frustrating its such a random problem, on occasions IGR + connecting to others using xbconnect will be fine (note: it is 100% whenever network cable is UNPLUGGED) but most of the time IGR + connecting using xbconnect still causes freezing. Sad how x. team cant identify it so they can fix it with a bios might have to go back to 4975 myself, although bios's after this have really added nothing anyway except small things such as disabling x2 IGR. (which isnt the problem anyway)

[nufan]

BTW im running the older 3285 evoX dash since its meant to be more stable.

[robg]

I have changed to the Avalaunch dashboard and all my lockups have now stopped.  My Xbox would always lock up in XBOX Media Player 2.4 with the Evox dashboard when I tried to access my network share.  Now I am using the Avalaunch dashboard I have no problems at all with the lockups.  Admittedly, Avalaunch is still very much in its beta stages at the moment but appears to be getting updated quite often, unlike the Evox dashboard.  I don't think I will be changing back to Evox, Avalaunch is my dashboard of choice now.

[vampire.de]

I tried and tried... no way, anytime I used the XBMP with ReLaX, the XBOX stopped and crashes....
Without the patchcabel... no problem at all....
Today I tried another thing...
I changed the IP's for DNS in the network-section of evox.ini and config-xml of XBMP....
Before changing I used the IP of my SMC Router/Gateway for DNS. Now I use the real DNS-IP of my ISP....and -quiet please- no more problems.... everything works....

Here my configuration:
Pal-XBOX 1.1
120GB Samsung
Samsung DVD
LPC v3.0
X2 Bios v4976.02 256kb multi
Evox v1.8.3752
XBMP 2.4 06-14-03
ReLaX 0.76 Pre.
static IP

vampire