Print

[Morglum]

I had it locking up with Evo-X and network cable in, but EVERYONE thats ever had this before just removed the cable and it fixed it, i cant see how just a handful of you are still getting this. I seem to recall the Evo-X team knew this was a bug in their software, though i might be wrong.

[SirHexx]

[Morglum]

When i had this prob it was connecting through a router, but unplugging the cable, turning evo-x igr off in all places and using x2 igr seem to have fixed it perfectly.

[nufan]

QUOTE (SirHexx @ Jun 20 2003, 03:31 PM)

I Have a question for all who has this Prob...  Do you guys connect your box through a router or hub?...or through a crossover cable..... cuz i'm thinking that maybe you might want to focus on some firewall/port settings..since this seems to only happen when the box is connected to network (from what i understand) . cuz i have evox 1.8.3285 and X2 4976.02 bios and everything is as smooth as silk....  sorry if i'm off base, just thought i'd throw my 2 cents in .... its probably all its worth.

yeah i connect via a router, but have also tried with a crossover cable direct from xbox to PC, it did fix it for a while but then the problems came back so yeah i guess thats not the cause either, nice constructive input though thanx

[underthebridge]

hmm I use a router... I never tried crossover, but I highly doubt the problem would disappear if I did. It's kind of hard to believe that some people experience no problems at all, considering that the same shit happens on v1.0, v1.1, and probably also 1.2 .. I'm trying to think whether PAL or NTSC xbox would make a difference? dunno, my expertise is not high on this.

Morglum, let me ask you this: Where you ever able to get it working WITH the cable plugged? because that is what we're shooting for

[Morglum]

QUOTE (nufan @ Jun 20 2003, 05:18 AM)

QUOTE (Morglum @ Jun 20 2003, 03:30 PM) I had it locking up with Evo-X and network cable in, but EVERYONE thats ever had this before just removed the cable and it fixed it, i cant see how just a handful of you are still getting this. I seem to recall the Evo-X team knew this was a bug in their software, though i might be wrong. how thick are you? YES removing the cable DOES fix it, clap clap well done, you're only about 6 months behind the times. The problem is when you are trying to play online then you NEED the network cable in, get it? Yes its fine to take the cable out and have IGR working fine as it should, and this is what happens, but it doesnt help for trying to play over xbconnect for example, where you obviously need the network cable to be plugged in to be able to play online so yes, you're a genious, unplug the cable, but thats not exactly an issue. sorry to be so fired up but this IS a geniune problem some of us are having and these uninformed comments made by ppl who think we are just complaining are getting rather tedious.

LOL, all i have to say to you is what a fucking wanker. Welcome to my retarded fag list.

[robg]

I had all these problems with lockups.  I changed to the Avalaunch dashboard and have not had a lock up since.  I can now access games online and use my network shares in media player flawlessly.

[X-ace]

QUOTE (underthebridge @ Jun 18 2003, 06:40 PM)

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... Features can come later, please fix the bugs for now.

Let's remember that Team executer puts out free BIOSes for our consumption.

Therefore we don't really have the right to demand anything, but based on the number of requests, I'm guessing this should be pretty high on the agenda.

I have a 1.0 myself, but given that percentagewise we are an ever dwindling number, it only makes sense to try to figure out what the network issue is. On the business side having the BIOS work will ultimately increase sales/distribution, so I think that we will see a solution at some point.

As a sidenote; it does not make it easier to fix anything just because a lot of people have the issue. However, it might help developers prioritize.

So, for now the word is Please.

[Ubergeek]

ive already posted on this before so here goes again

first of all to the guy who says ppl have a right to bitch - well no you dont. The bios iss free and is done out of our own time and for fun.

secondly to the guy who says it will increase x2 mod sales and distribution. No it wont as the mod is a gem with whatever bios you use.

OK now to the issue - ive never ever seen this happen. I have several boxes connected to a LAN and they never lock up.

i'm not denying some of you have problems but its a minority - so its down to a particular kind of setup.

There is NOTHING in the kernel source that can cause this I can assure you - its been looked at a hundred times

I would love to duplicate this but I cant - so there is nothing I can do about it.

If I could duplicate this shit i'd know what it was - and I bet your as its nothing to do with the bios itself but perhaps a mix of bios / hardware / dashboard

to say "well it works with evox" well i have ppl also say it DOESNT work for them with evox - and only evox themselves could answer questions about theeir ftp code - but again they'd think the same as me - it works for 99% of you - sso sorry to the 1% who have problems.

perhaps you could posst more speccfic data as opposed to bitching at each other or complaining ?

[Ubergeek]

QUOTE (wildcard @ Jun 20 2003, 04:25 AM)

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

we're not ignoring and no you dont have a right to bitch about shit

sure you wwont get problem with D6 - as they coded the dash also - if they wish to share their code than peerhaps we can fix that buggy shit for them

X2 bios is WAY BEYOND D6 in terms of complexity

If this is such a huge issue for you - this is what you have a switchable mod for - to use different bios's

You guys are a tiny minority and its difficult when its like this - if EVERYONE had the problem (inc me) i could perhaps do something about it

When posting - be constructive

Version of console
Version of Bios
Version of dash
Dash boots from X drive
Mod Hardware Used
Net cable used
Hub / Crossover Used
OS Used on PC
Exact point of crash
Whether tested success if net cable unplugged

Help us to help you

[X-ace]

As to whether more mod chips would be sold, that was a pure economics argument. The more benefit you derive from a product, the higher demand is. If there is only a minority who get this issue, then of course this wouldn't impact much. My original point was that I have been getting something for free, as have most here, and poeple would do well by remembering that instead of bitching. (didn't mean to upset by mere academic musings).

As to Nufan's last post; if it is only IGR that freezes, then I would say this is a very minor thing. Just don't use IGR. (IGR works for me about 50% of the time, and i don't really care.) I know it is far from the couch to the console, but... On the other hand, a lot of people appear to get these freezes even without using IGR, but always when connected to a network. That would be more serious.

I do NOT have this problem (yet), but have been puzzled by the problem since Istarted encountering people who had a bout a month ot two ago.

[mrRobinson]

Version of console 1.0
Version of Bios have used D6.ef with no problems then 4976.02 would freeze then 4976.02_red_noani is fixed again
Version of dash have tried 3752 and 3285, and freezes with 4976.02, doesn't freeze with the red_noani
Dash boots from X drive C
Mod Hardware Used xecuter 2: pro
Net cable used standard "straight through" cable
Hub / Crossover Used Sometimes to a linksys hub, sometimes to a linksys WET11, sometimes xover cable to pc.  freezes with all.
OS Used on PC Windows XP Professional
Exact point of crash For me it happened 90% of the time during boot when the x logo shows up on the screen and then it shows Xecuter2 in white text at the bottom.  It would just freeze there.  If i ejected the drive it would then continue to boot.  with the red_noani bios no such hang occurs.
Whether tested success if net cable unplugged with net cable unplugged, every configuration listed above worked fine.

There is another topic where I asked some questions maybe Ubergeek could please answer, or attempt to...

oh and of course there is this topic where there are quite a few constructive posts mixed in as well.

[Ubergeek]

QUOTE (mrRobinson @ Jun 21 2003, 04:11 PM)

freezes with 4976.02, doesn't freeze with the red_noani

mmm this is interesting

can those of you with problems test this yourselves and offer some feedback - thanks

[mrRobinson]

QUOTE

mrRobinson kapkorn you have 4976.02? my problem was just a hang during boot but when i loaded a color bios it seems to have fixed it (or with network unplugged). can you try a color bios just so we can differentiate between a problem during boot and problem during game? Unplugging network cable fixes both but wondering if color bios will fix yours. kapkorn Posted: Jun 2 2003, 01:03 PM sure give me an exact file name of one of the bios that worked for you i will try it after work yes i am using the .02 bios post back and i will try it after work mrRobinson Posted: Jun 2 2003, 01:56 PM ok this worked: 4976.02_Red_Noani_256k.bin whereas this did NOT: Xecuter2_4976.02_MultiVer_256k.bin kapkorn Posted: Jun 2 2003, 07:26 PM must be that one bios from xbins. i got the red color from another source and it works fine now (note i had to use IGR filedisabled also, but it was on the other also) mrRobinson Posted: Jun 2 2003, 08:26 PM really? wow. so the question is... is it a bad .bin from xbins... or can/does the normal 4976.02 suffer from some bug that the color noani's sidestep??

[nufan]

all i did was disable DHCP on my router (i thought i had done this before, but my mate came over and sorted out my network)

anyways so now its static, i set the IP and it WAS going sweet as, but this morning its back to freezing :|

im actually getting a new switch because the hub built into my m1122 router is only 10mbps making transfers slow, so if it still freezes with the new switch im at a loss as to what the problem could be, will report back as usual

The problem seems to get "fixed" when u muck around with settings (ie, when i turned DHCP off)  however it always seems to come back (for those of us affected by this plague )