Topic: I Think 2.3b Is A Bad Design... (Read 88 times)

lookformeb · « **on:** March 01, 2004, 10:42:00 PM »

Exactly whats a bad design?? Bear with me while I explain this cause I'm tired...

You've got a 1mb TSOP essentially on a 2.3 lite, the same as the early version Xboxes. It's purpose is to hold a flash image a boot it, there's no compatability issue with the flash memory, how can their be? All it does is hold the image...

I honestly thing the issue here is possebly you are making a silly mistake in creating the image. We've all done it before...

lookformeb · « **Reply #1 on:** March 02, 2004, 08:16:00 AM »

As long as the chip boots solid, the rest is BIOS dependent, not chip.

duudfromnorway · « **Reply #2 on:** March 02, 2004, 08:34:00 AM »

jfxwave · « **Reply #3 on:** March 02, 2004, 03:14:00 PM »

Your correct about 4981, I have never had any problems with anything below 4974. Now all Im trying to do is add large disk support so I have to use 4979 or higher and thats when it doesnt boot. Maybe it has something to do with adding the large HD support on the chip. I am getting 3 more chips in this week so I will find out what happens with them. Im getting an external programmer as well. I read a lot about people having problems loading 4981 with the box and they got it working by flashing the chip with an external programmer.

Oh and i'm getting my friends box's - v1.1 and a 1.4 and i'm going to get this thing working or find out whats going on.

lookformeb · « **Reply #4 on:** March 02, 2004, 09:07:00 PM »

duudfromnorway · « **Reply #5 on:** March 03, 2004, 02:19:00 AM »

thanks!

jfxwave · « **Reply #6 on:** March 03, 2004, 07:57:00 PM »

Hi and thanks for the replies.
I have tried them all but just to make sure I just tried them again just now.
Tried x2_4977.bin, x2_4978.bin on bank 1/2 , 3/4 and 1/2/3/4. And they work.
Tried x2_4979.bin and x2_4981.bin on bank 1/2 , 3/4 and 1/2/3/4 and they do not work.
I even tried 4980 just for the hell of it and it didnt work.

Whats the different between 4978 and 4979?
The only thing I know of is the support for larger HD and I think IGR and LIVE.

Now with all the problems that 2.3b is having, either the chip doesnt handle something correct or there is something wrong with the bios. I dont hear that much about any chip lower then 2.3b so thats why I think its the chip.

HuddaDudda · « **Reply #7 on:** March 03, 2004, 08:41:00 PM »

Here is what I have and my issue:

Xbox v1.1
X2 2.3b Pro
200G HDD

My problem: Chip on or Off with OEM drive works perfectly fine. Chip on with Large HDD boots to Evox - Chip off sometimes will boot into M$ Dash sometimes get an Error 21 - When it does boot into M$Dash I can crash it by going into any of the areas (ie settings, memory, audio) with the pesky Error 21

Tried to fix by: Reformat the HDD - recopied all OEM files to NEW Large HDD, still problem occureds or Error 13 with 4981 Bios. Reflashed 4977 Bios now getting the spearatic Error 21 crashing in M$Dash. I tried also zero'ing the HDD in my computer and that hasnt done anything.

I do have another chip here. An XBIT - I see it has a pogo pin install available. I am going to remove the X2 2.3b Pro and install this chip and flash the different BIOS to see if that works. I bought my 2.3b PRO at system mods. Do they read these forums? If this chip turns out to just be pain trippin I wonder since we are all surely outside the 7 day return policy will they do anything anyway?

Also no one has mentioned this but I notice an I: partion on the HDD now. Is this from the 4981 BIOS? Could that be making the problems? Who else has this partion?

I do believe this issue is pretty similar to what everyone else is seeing. FRAGGING Xbox and strange Errors. I have seen a TON of posts with 2.3b's giving people errors now from XBoxes that WERE fine. I also see experenced installers like myself who have had XBoxs failing now for no apparent reason.

f.u. · « **Reply #8 on:** March 03, 2004, 09:43:00 PM »

Good to hear that if your machine gets a error 21, there is still a way out of it (even though its not fully understood). Partial use of the machine is better than no use which is my current situation.

HuddaDudda · « **Reply #9 on:** March 04, 2004, 04:28:00 PM »

I was wondering that same question - since system-mods only has a 7 day return on thier chips. How are we supposed to fix this in that time frame? Then to send it back and pay all their testing fees etc is crazy! Might as well just buy a new damn chip!

f.u. · « **Reply #10 on:** March 09, 2004, 08:29:00 PM »

n00bster · « **Reply #11 on:** March 10, 2004, 05:05:00 AM »

Author Topic: I Think 2.3b Is A Bad Design... (Read 88 times)