xboxscene.org forums

Pages: 1 ... 4 5 [6] 7 8 ... 10

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

Meep

  • Archived User
  • Newbie
  • *
  • Posts: 5
Crashes With Xecuter 2 4976.02?
« Reply #75 on: May 30, 2003, 06:25:00 PM »

ok. I haven't played with changing bios's for a long time. an hour ago my v1 box had the X2 version 1 bios, on a 29 homebrew. I've never had a single problem with freezing.

I just installed the latest 4976.02 bios. guess what, it's freezing. Definitely a bios problem, nothing else.

No big deal, props to X for constantly trying to improve their bioses. I hope this helps.
Logged

robg

  • Archived User
  • Newbie
  • *
  • Posts: 29
Crashes With Xecuter 2 4976.02?
« Reply #76 on: May 31, 2003, 01:20:00 AM »

My specs

Xbox version-1.1
Modchip- Matirix
Evox version-1.83285
Bios- 4976.02 xecuter
Relax is running
Using a static IP.
All IGR's are off and also have the IGR disable file on drive E:.


My setup occasionally crashes under Media Player 2.4 but I have noticed it always crashes everytime when I try to go back to the evox dashboard from the Super Nintendo emulator.  When I unplug the network cable and carry out the same procedure it does not crash.
Logged

mrRobinson

  • Archived User
  • Hero Member
  • *
  • Posts: 1321
Crashes With Xecuter 2 4976.02?
« Reply #77 on: May 31, 2003, 01:50:00 PM »

I've posted earlier in this thread, but my problem is only a lock up during boot where it won't load the dash but then if i eject the drive it'll reset and load.  So i'm creating a new topic Crashes with Xecuter 2 4976.02 (during boot) and will post what i've done so far to debug this (and seems to be fixed) **for now**
Logged

Baal

  • Archived User
  • Newbie
  • *
  • Posts: 31
Crashes With Xecuter 2 4976.02?
« Reply #78 on: June 01, 2003, 02:14:00 AM »

Ok dunno if this thread is good but my problem is quite the same.

my config first.
Xbox v1
Executer2+pogopin
Bios: ...tried many x2 bios.
Nothing on HD


Ok by some weeks i'm experiencing strange hangs on of xbox...it occurs at boot, during loading the game, while playing and load a part of game and so on.
If i press the eject button it will Boot 2 times and FRAG!!!!!
If i disable the chip it will boot normally with MS bios.
Well i was forced to reflash bios and all goes well...but sometimes (just now) also if i -newly - flesh the bios (now i'm trying 4974) i get boot 2 times and FRAG.

Can be the UDF format the cause of those strange problems (also before i used menux and now i'm using craxtion)? (a DVD with Splinter cell and Outlawgolf gives  me this problem 2 time in 2 days).....
But how can the bios be fucked by these loock ups?

- Pogo pin is not misallined.......i chechek the first time when got this problem and reallined it, but when the 2nd time got that problem, with refleshing of bios all went good -


EDIT - rofl.....now i tried to flash the bios the 2nd time and it says " no x2 found!" 1 min before i was able to flash it :|
Logged

ybaig123

  • Archived User
  • Jr. Member
  • *
  • Posts: 90
Crashes With Xecuter 2 4976.02?
« Reply #79 on: June 01, 2003, 10:38:00 AM »

seems like your problem is way outta this league man
Logged

mrRobinson

  • Archived User
  • Hero Member
  • *
  • Posts: 1321
Crashes With Xecuter 2 4976.02?
« Reply #80 on: June 02, 2003, 06:04:00 AM »

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.
Logged

mrRobinson

  • Archived User
  • Hero Member
  • *
  • Posts: 1321
Crashes With Xecuter 2 4976.02?
« Reply #81 on: June 02, 2003, 09:56:00 AM »

ok this worked:
4976.02_Red_Noani_256k.bin

whereas this did NOT:
Xecuter2_4976.02_MultiVer_256k.bin
Logged

mrRobinson

  • Archived User
  • Hero Member
  • *
  • Posts: 1321
Crashes With Xecuter 2 4976.02?
« Reply #82 on: June 02, 2003, 04:26:00 PM »

QUOTE
Few questions: (possibly for Ubergeek):
Does the noani change or affect in any way the way the xbox loads its networking stack? It seems like if the network can come "up" before or during the logo screen it will then load the dash, otherwise it just sits there (waiting for the net to initialize?).

The other thing i was going to try is to take my 3285 exox to the 3752. In the 3752 evox.ini there were two extra lines in the network section that i don't have in my .ini with 3285 and they are


SkipIfNoLink = No
SetupDelay = 10


I was thinking if these values were messed with it would get it to work. But right now my problem is resolved with the red noani bios so i don't want to go messing with the dash just yet (and i read about bugs with it anyway)

I know MsSplitch had same issue so if can confirm same fix??
Logged

micleeso

  • Archived User
  • Newbie
  • *
  • Posts: 3
Crashes With Xecuter 2 4976.02?
« Reply #83 on: June 04, 2003, 07:03:00 PM »

After reading this thread from the beginning to the end, and working with my own analysis using logic and isolation. By method of elimination I have concluded my research with the following results.

Everyone has the same issue "network communications - crashes the Xbox".  And I have been experiencing the same phenomena. We need to isolate which part of network portion is broken? TCP/IP stack, bios or dashboard? Is it part of the new copy protection circumvents?  Who, what, where, when, and how is this going to be resolved? Simply following a method and coming to a definite conclusion is the only direction a logic answer will follow..
Logged

micleeso

  • Archived User
  • Newbie
  • *
  • Posts: 3
Crashes With Xecuter 2 4976.02?
« Reply #84 on: June 04, 2003, 07:10:00 PM »

My current experiment

Many people point to outside network issue such as DHCP. It's proven not related to outside services due to method of elimination.

I have tried the older dashboard from evox and not one crash. Load up the new one and it crashes. So I updated my bios with new evox dashboard, it crashes. Back up to older dashboard it is stable.

I add a direction to my logic, network communications with in evox.

My specs for review (Variables)

Xbox ver. 1.0
120 WD 7200 8MB Cache
Bios x2 4976.02 512k
evox dash 1.8.3752
XBMP build 13 May 2003 20:30
with linksys BEFW11S4 router using wire with wireless module enabled. DHCP disabled.

Evox dash settings
network: static
setup network: yes
no DNS entered
setup delay:
skip setp if No link: yes
xbox hardware info: 00000003 A3 B2
Kernel Version: 1.00.4976.02
FTP: No
Telnet:no
RDTools:No
Clock: Jump to MS Dash:No
Jump if No link: Yes
24Hour: No
SwapDate: Yes
SNTP:216.244.192.3
misc:
Dash ver. 1.8.3753
fahrenheit:No
Auto Launch Games:No
Auto Launch DVD:No
Auto Launch Audio:No
Use F Drive:Yes
In Game Reset:Yes
Use Items.txt:No
Screen Saver:5
Shade Level:95
Logged

micleeso

  • Archived User
  • Newbie
  • *
  • Posts: 3
Crashes With Xecuter 2 4976.02?
« Reply #85 on: June 04, 2003, 07:33:00 PM »

Since my direction has pointed to evox I am posting on evox board as well for your info.

http://www.valholl.org/forums/ under EvolutionX Forum Index -> Support -> Lock-up Issues.
Logged

X-ace

  • Archived User
  • Sr. Member
  • *
  • Posts: 283
Crashes With Xecuter 2 4976.02?
« Reply #86 on: June 05, 2003, 10:38:00 AM »

Some people have reported success by setting the IP Settings in XBMP to STATIC.

try this and see if it works.

(or try using XBMP as a dash.)
Logged

LiquidFusion

  • Archived User
  • Newbie
  • *
  • Posts: 4
Crashes With Xecuter 2 4976.02?
« Reply #87 on: June 05, 2003, 12:48:00 PM »

UPDATE:  over a crossover cable only freezes too.

EDIT:  ok here's another weird thing.  x1.1 doesn't even have to be looking for clients to join.  It can just be in the start menu.  

EDIT2:  OK WHAT THE FUCK!?!??!?

ok i finally fixed it.

so we had an idea about trying to join a game while x1.1 was in a game that doesn't have system link.  So we tryed it with blinx.  I was in the menu and he tried to join a brute force game, nothing happened to mine.  So i did a IGR reset and booted up wolfenstien, a system link game.  Was in the main menu and he tried to join and nothing happened.  So i tried to host a system link game and then he tried to join and again no freezing.  I did another IGR and booted up brute force, and we're currently playing squad deathmatch.  I'm afraid to turn off my xbox for fear that i can't play brute force mp again.
Logged

mrRobinson

  • Archived User
  • Hero Member
  • *
  • Posts: 1321
Crashes With Xecuter 2 4976.02?
« Reply #88 on: June 05, 2003, 02:08:00 PM »

QUOTE (micleeso @ Jun 4 2003, 11:03 PM)
After reading this thread from the beginning to the end, and working with my own analysis using logic and isolation. By method of elimination I have concluded my research with the following results.

Everyone has the same issue "network communications - crashes the Xbox".  And I have been experiencing the same phenomena. We need to isolate which part of network portion is broken? TCP/IP stack, bios or dashboard? Is it part of the new copy protection circumvents?  Who, what, where, when, and how is this going to be resolved? Simply following a method and coming to a definite conclusion is the only direction a logic answer will follow..

Well kapkorn and I both fixed it by loading a 4976 noani bios as opposed to the normal one.  It seems to me whether or not it is a "bios problem" it is definatley something that can be fixed in the bios.  Especially since i never had the problem when i was running D6.ejectfix.  But I posted all this before...
Logged

chong

  • Archived User
  • Newbie
  • *
  • Posts: 2
Crashes With Xecuter 2 4976.02?
« Reply #89 on: June 06, 2003, 04:52:00 PM »

which pins do u keep and remove from the xecuter 2? i cant flash, it says flash not wrtiable.
Logged
Pages: 1 ... 4 5 [6] 7 8 ... 10