Topic: 2.3b Lite + - Getting Error Code 16 (Read 100 times)

para[android] · « **on:** April 16, 2004, 01:21:00 PM »

Lock the drive.

subdigital · « **Reply #1 on:** April 19, 2004, 08:46:00 AM »

you shouldn't have to lock the drive for it to work.

You have to lock the drive if you plan to use it with original bios.

if you have flashed the chip correctly you need to make sure that you have the right files on the new hd for it to boot correctly.

Please elaborate on how you installed the HD (software-wise). This will help us troubleshoot your problem.

*EDIT* doh!

I'm an idiot, maybe I should learn to read. Yes you must lock the drive if the chip is disabled because MS bios will not load unless it is locked. I am not experienced with this, but I know you can use configmagic to lock it. Check the forums and tutorials for details. With the modchip enabled you should be able to boot without locking the drive.

para[android] · « **Reply #2 on:** April 20, 2004, 06:33:00 AM »

OK, this is a different situation than I thought you were in. You really need to b detailed in your posts. You do need to lock your drive to have it boot with the modchip disabled, but your not going to be able to do that until after you get a dash and some apps installed, so ignore that for the meantime.

1. You said in your first post you flashed the bios. What bios?

2. In your last post you said cromwell is still coming up. Try switching banks, if that doesn't work, your flash didn't take, and you have to get that worked out.

3. You install Slayers with the chip enabled.

Before you can install slayers though, you are going to have to be able to boot up tp a hacked bios (xecuter or evox bios). What bios did you flash with originally?

para[android] · « **Reply #3 on:** April 20, 2004, 08:55:00 AM »

4983 is good.

xbins on efnet (irc)

oxjeremy334 · « **Reply #4 on:** April 20, 2004, 12:41:00 PM »

Use configmagic to lock the hdd, and then see what happens.

para[android] · « **Reply #5 on:** April 20, 2004, 03:14:00 PM »

oxjeremy334 · « **Reply #6 on:** April 20, 2004, 03:56:00 PM »

Uhhh...he says that he is not getting the dash to load...but he has nothing on the hdd. He wants to load slayer's, so I am guessing that the 80gb is not even formatted in the first place, also meaning, there is no dash on there to boot to in the first place.

para[android] · « **Reply #7 on:** April 21, 2004, 08:36:00 AM »

benfica · « **Reply #8 on:** April 22, 2004, 08:19:00 AM »

What's the link to the "hacked" bios? Is it by using IRC?
Thanks

para[android] · « **Reply #9 on:** April 22, 2004, 09:28:00 AM »

oxjeremy334 · « **Reply #10 on:** April 26, 2004, 08:34:00 PM »

That would probably be a negative on my part, but are you going to just put that bios on slayer's in place of the other one?

benfica · « **Reply #11 on:** April 27, 2004, 08:20:00 AM »

I'd put that bios on the mod and then boot up with slayer's to see if that would be the problem...I may not have a "hacked" bios...
What are the correct steps to getting 4983 bios?

Author Topic: 2.3b Lite + - Getting Error Code 16 (Read 100 times)