I flashed my bios to a later version because mine were really old and right away it started saying NTLDR is missing. I went into the bios and messed around for a while and then saved and exited and then windows actually loaded up. Then I had to restart it and it said NTLDR is missing again. Now I can't get it to load up again. I put in the XP disc and replaced the ntldr and ntdetect.com files but it didn't fix it. What should I do?

Hi Johnny,

So sorry about the delay in answering your post.

Before we get any farther, I want to make sure that we are talking apples and apples. You said:
I take that to mean you flashed a newer bios to your PC.

If that is correct please;
Post the exact make and model of your MOBO
The BIOS version that you are using and the version you had previously

This problem can happen if one or more of the following Windows boot files are missing or damaged as well:
Ntldr
Ntdetect.com
Boot.ini

Since you have already replaced the Ntldr and Ntdetect.com files, perhaps your Boot.ini file has become corrupt. Can you please also post the contents of your Boot.ini from MSCONFIG?

Looking forward to your reply,

TTFN

LGW

I think johnny is saying that he can no longer boot into Windows. If that is the case then he won't be able to see msconfig.

Can you confirm plz johnny

My mistake Hengis, thank you for pointing that out. As you will not be able to go to MSCONFIG, can you please post the other information, and we will look at the BIOS before attempting to get your boot.ini file replaced/repaired.

Also, can you please be more specific as to what you "messed around with," in your BIOS?

Looking forward to your reply,

TTFN

LGW

Johnny 5 is alive!

How's it going?
This could be as simple to solve as booting from your windows xp cd into the recovery console and once you're in type
FIXBOOT
and
FIXMBR

then try rebooting.

Edit:

Oops I didn't notice that you've apparently already done that. Last time I encountered that problem I ended up having to retire my system drive. I hope that's not the case. In the recovery console try running CHKDSK to find out if you have some recoverable bad sectors. I'm just hoping that you don't have a physically damaged boot sector like I had.