Topic: Crashes With Xecuter 2 4976.02? (Read 973 times)

X-ace · « **Reply #45 on:** May 21, 2003, 02:51:00 AM »

Well, it sounds to me that for testing purposes, I would start by
+ setting static IP

if does not work by itself, try
+ unhooking the network cable

How many people have tried this and with what results?

ybaig123 · « **Reply #46 on:** May 21, 2003, 03:57:00 AM »

setting static ip doesnt help for me...unplugging network cable i think does...i just need to have my box running a little longer to know for sure

ybaig123 · « **Reply #47 on:** May 21, 2003, 11:48:00 AM »

could it have anything to do with the fact that my c: / e: drives are backups of drives off a 1.0 xbox and i'm using this shit on a 1.1?

B@se · « **Reply #48 on:** May 21, 2003, 01:06:00 PM »

yo redrum, if you want the xbox etc. to have static ip's do you you have to set this in the evox.ini or set it up in the router for example?

(I think i had my xbox's ip set to static in the evox.ini in the beginning, but then xbox live wouldn't connect)

X-ace · « **Reply #49 on:** May 21, 2003, 01:09:00 PM »

it's in the ini
static IP = yes

see earlier in this thread for examples

redrum374 · « **Reply #50 on:** May 21, 2003, 07:40:00 PM »

(I think i had my xbox's ip set to static in the evox.ini in the beginning, but then xbox live wouldn't connect) ?
B@SE what do you mean by xbox live? You cant use xbox live on backed up games or use xbox live from evox. Your msdash takes care of all that. Evox doesnt have anything to do with xbox live settings.

ybaig123 · « **Reply #51 on:** May 21, 2003, 08:20:00 PM »

fuck it... i guess i gotta live with this freezing shit...cuz that static ip stuff doesnt make a difference for me

Scubix · « **Reply #52 on:** May 22, 2003, 03:08:00 AM »

My guess its the bios (4976.02) or the evo-x, or the combination of them as my probs started after flashing the x2lite bios. I havent had enuf time to test older bioses or evo-x versions, but i will soon

ps: i have a v1.1

X-ace · « **Reply #53 on:** May 22, 2003, 03:52:00 AM »

well,
unplugging the network canle may not be asolution for all, but if that works at least it is an indication of where the problem is.

ybaig123 · « **Reply #54 on:** May 22, 2003, 04:04:00 PM »

fuck this...its gotta be the chip....fucking executor...nothing else can explain this...network cable and all......and i doubt system-mods will take returns...so i guess i just got a shitty chip

ybaig123 · « **Reply #55 on:** May 23, 2003, 12:52:00 AM »

B@se mine is pretty much exactly as yours

X-ace · « **Reply #56 on:** May 23, 2003, 04:54:00 AM »

Sounds like the advice is to pull out the network cord when you play games then
(until someone figures this out)

bucko · « **Reply #57 on:** May 23, 2003, 10:53:00 AM »

Could be fragmentation. All those needles spinning accroos 120gig drive to find that certain file to load the game might be the cause of the crashes, the games wern't designed to run on such fragmeneted drives.

bucko · « **Reply #58 on:** May 23, 2003, 12:31:00 PM »

Na I was trying to Isolate the problem because I don't think it's a network issue.

ybaig123 · « **Reply #59 on:** May 23, 2003, 06:05:00 PM »

if someone can solve this problem for me (and give info that fixes it... ie: no more freezing)....i give them a free xbox (unmodded) w/ controller and all

Author Topic: Crashes With Xecuter 2 4976.02? (Read 973 times)