Print

[M3_DeL]

Fuck, Cheerio I spent 2 days on this.......I now have 3 people who had the same problem and when they flashed with a diff bios all was good.

I know my shit, I've done this enough times to know that what is happening is not normal.

Let me explain it to you again. I had put the new HD in and the evoX disk in (boom error 16) I stick the old drive in (No problems) I put the new HD in again (boom error 16)

Error 16 is a dashboard error.

something tells me that the BIOS is looking for stuff on the HD first.....

[M3_DeL]

More info on the two HD setups....did you use the default bios or did you flash it, and if you flashed it what bios EXACTLY ?

Im not worried about the chip, just the bios......the chip I used was the Matrix. I tried every mode and every jumper setting. so not quite sure what is going on

[equilibrium]

QUOTE

More info on the two HD setups....did you use the default bios or did you flash it, and if you flashed it what bios EXACTLY ? Im not worried about the chip, just the bios......the chip I used was the Matrix. I tried every mode and every jumper setting. so not quite sure what is going on

I've not flashed my bios on my chip at all so it's 'original'. I have a 1.1 PAL xbox with a phillips drive. I basicly installed the chip one day and then installed the new hdd and evox etc the next. So nothing was done to the BIOS on the chip.

[M3_DeL]

(First get on  MIRC) OK how could it be user end. The chances of that are slim as I was swaping HD's right and left, and everytime I put in the orig. HD it would boot the disk and then everytime I put in the new HD it was error 16. that would mean everytime I put in the new HD I would have to screw up and everytime I put the old HD I got everything right??? Not likely. I even flashed the chip a few times to verify it was a good bios....which it was cause it worked fine with the old HD.

Once I flashed the chip with the old Xecutor1 bios everything worked right away!!!!!!

[M3_DeL]

420247 what style of Xbox? 1.1?

[M3_DeL]

I wonder why this was happening with my buddies but not with a different bios?

[Perplexer]

QUOTE (Cheerio @ Jan 22 2003, 07:39 PM)

dude, 100's of people have used x2 bios. 100's. and 3 people have a problem.....it just looks alot like end user error -

User error  

I see where you're coming from, but take a look at some of my other posts, and you should get a pretty good idea that I know what I'm doing.  

I can't argue that this problem is affecting a very small percentage of people, but it IS happening, and seems to be affecting only those people with a specific 1.0 mainboard/4973 BIOS combination.

No combination of hard drives (I tried four, including the original), jumper settings, etc. would get past error 16, but once I flashed to a 4974 BIOS, *boom* booted up fine.  This seems to be the cure for everyone with the same hard-drive-swap-error-16 symptoms.

[M3_DeL]

QUOTE (xbox_freak!! @ Jan 22 2003, 05:50 PM)

QUOTE (M3_DeL @ Jan 21 2003, 08:59 PM) so you guys have installed a Brand new zeroed out drive with X2 bios on the chip? I have never had the problem like i did with the X2 Bios. Plese respond if you have installed a new Zeroed HD with X2 bios on it? The problem I ran it was it wasn't booting the evoX disk when I had the blank drive in, but when I put the oem back in it booted the disc fine!!!! if its a brand new drive no need for 0ing

brother I did that because i didn't know what else might be wrong?!?!?! So no one could say oh well you need to zero it out or anything!!!!!

[manekineko]

Yeah, I saw this same thing happen on my friend's xbox.  He switched to EvoX bios and problems disappeared.

[indotoonster]

M3, saw from your other thread that you worked around it by stepping down to the X1 BIOS -- glad you sorted it out. But it still is weird that it happened in the first place, no? Like someone commented, hundreds of people have succeeded without problems, only a few isolated users had this issue.

I'm wondering if it had anything to do with the modchip used. You used Matrix, I used Matrix. Could it possibly be a Matrix + X2 BIOS combination?

cheers,
indotoonster

[exstazi]

i have the same problem as you M3 Del...error 16 and its my orig hdd...i dont really know what to do now...

[xbox-fun]

But... i found out what was going wrong !!!

Before swapping to the new drive, my xbox was not connected to power outlet during some time. And when you try to run an xbox that was previously out of power, you are automatically directed to time and date setting screen, even if you have a CD inserted  

But with a brand new blank disk in, the box fail to find anything and go into error 16 !

So i just put back the original drive, set time and date, swap again to the new blank drive, and this time my CD boot fine  

I think there's no bios issue at all. Don't you ?

Hoping it can help...

See ya !

[bluespot]

 It seems that the Xecuter BIOS will throw that error once it attempts to boot to a nonexistent F: partition (such as the case with the original xbox HDD) without even checking it's other boot options.

So getting this error and want your box to boot again?  You need to connect a hard drive with a valid dash on the F: drive.  Borrow one from a friend  Boot it once to set the time, and then you can disconnect it and put in your new drive that needs partitioning etc.  Either that or you can solder in a 32 wire homebrew and boot your original Xbox HDD with an Evox BIOS

[indotoonster]

QUOTE (xbox-fun @ Jan 26 2003, 12:54 AM)

Hi there ! I had the same problem just a few days ago with X2 4974 on a PAL 1.1 box. I was very confused because i already had changed original drive by a 30GB one with no problem but this time i got error 16 when i wanted to put a brand new 120GB   But... i found out what was going wrong !!! Before swapping to the new drive, my xbox was not connected to power outlet during some time. And when you try to run an xbox that was previously out of power, you are automatically directed to time and date setting screen, even if you have a CD inserted   But with a brand new blank disk in, the box fail to find anything and go into error 16 ! So i just put back the original drive, set time and date, swap again to the new blank drive, and this time my CD boot fine   I think there's no bios issue at all. Don't you ? Hoping it can help... See ya !

xbox-fun, you genius!

it all makes sense now. yes, i think i had to set the time when i inserted my original HD again. very interesting. thanks for this, it's been worrying me for a while now.

cheers,
indotoonster

[weazil]

The whole part about setting the time is bs, I recently aquired an xbox that the hd died.  it doesn't spin up at all, its been unplugged from power for about 3 weeks.

M3_Del you are right evidently there is problems with some x2 bios's I was running 4974 Blue, and no hard drive would work, I either got error code 7 or 16 depending on the jumper settings. Saw your post and reflashed the bios to D6, and retried all the previous hd's that wouldn't work and they all came up fine.

Used Slayers disk to format / install. after up and running I deleted slayers stuff and put my original info on it. wanted to take the modchip out and just leave it as is but when modchip is disabled it gives error code 5 hd not locked.  When I tried to lock it, config magic reports hd unable to lock.  on both 13 gig drives i tried.... one wd and one maxtor.

any ideas on the locking part?