Three words...

Shelnutt2 · Apr 13, 2006

"NTLDR is Missing"

I never! never! want to read those words again.

I'm just wondering how many of you out there actually save your system (windows install) when this happens? The three times that this has happened, the copying the files from the XP cd does not solve the problem and I end up having to format and start over.

sno.lcn · Apr 13, 2006

I don't recall having any luck recovering my system after seeing that either. But then agian it has usually been from me doing something stupid and wasn't too worried about having to reload anyway.

Gnufsh · Apr 13, 2006

Did you try running fixboot and fixmbr from the recovery console?

edit: changed . to ? because I don't know the differnece between a statement and a question.

brickout · Apr 13, 2006

I've gotten it twice, and neither time would the repair from cd work...

Couldn't recopy that file, either.

Shelnutt2 · Apr 13, 2006

Gnufsh said:
Did you try running fixboot and fixmbr from the recovery console?

edit: changed . to ? because I don't know the differnece between a statement and a question.

Gnufsh you n00b at grammar

.

I tried

Code:

copy E: i386ntldr C:
copy E: i386ntdetect.com C:

That is what, after a search here, I came up with to do.

I then tried to repair windows, it would get stuck.

So format and now I'm running lightning fast again..for the moment..

habbajabba · Apr 13, 2006

http://tinyempire.com/notes/ntldrismissing.htm
have not had the pleasure of using it however

sno.lcn · Apr 13, 2006

Nice find. I wonder how well it works.

jcw122 · Apr 13, 2006

So far I've found the recovery console to be absolutely useless, a waste of my time.

I now have a backup HDD for all my important files, forget repairing Windows.

El<(')>Maxi · Apr 13, 2006

Seen this when overclocked too far from BIOS, lowering settings always fixed it for me in that scenario.

fabulouscoops · Apr 13, 2006

I fixed this error once by just re-checking my HDD cables. One was loose so I re attached it and rebooted and everything went back to normal.

habbajabba · Apr 13, 2006

the file must have got stuck in the cable-lol

Cheator · Apr 13, 2006

Yeah i've recovered 3 or 4 times. Trouble is i forget how to recover every time. It doesn't happen often enough

Gnufsh · Apr 13, 2006

jcw122 said:
So far I've found the recovery console to be absolutely useless, a waste of my time.

I now have a backup HDD for all my important files, forget repairing Windows.

I've managed to use it to fix a couple things.

Captain Newbie · Apr 14, 2006

Shelnutt2 said:
"NTLDR is Missing"

I never! never! want to read those words again.

I'm just wondering how many of you out there actually save your system (windows install) when this happens? The three times that this has happened, the copying the files from the XP cd does not solve the problem and I end up having to format and start over.

Usually my response to it is "Ah **** it" as I reach for the install disc.

anon1 · Apr 14, 2006

Shelnutt2 said:
"NTLDR is Missing"

I never! never! want to read those words again.

I'm just wondering how many of you out there actually save your system (windows install) when this happens? The three times that this has happened, the copying the files from the XP cd does not solve the problem and I end up having to format and start over.

Eh, it has only happened to me once, and I just copied it back over. After that, it worked fine, until I blew away the system, and installed Linux.

madman22 · Apr 14, 2006

for me, if i had a bootabe CD in the drive, it would detect NTLDR and boot windows, but if i didnt have a bootable cd in the drive, windows was a no go, so i had to put in a new cd drive so i wouldnt have to switch cds all the time.

i tried the recovery console and messed around with which HDD the bios sees first, i dont remember what i did, but after a lot of trouble shooting, that message finally went away.

Gnufsh · Apr 14, 2006

If you have a problem like that, you might want to set the bios do delay the ide detection by a couple seconds and see if that helps.

Layback Bear · Apr 30, 2006

Had the problem once and it was caused by Nortons GO BACK with 2 hard drives on IDE cables. On the phone with nortons and got document ID 20010926111363307 and fixed the problem for a while. It took for ever. I solved the problem by giving away the two hd's and instlling 1hd sata.

Three words...

Shelnutt2

Overclockers Team Content Editor

sno.lcn

Senior2 Member

Gnufsh

Senior Member

brickout

Member

Shelnutt2

Overclockers Team Content Editor

habbajabba

Member

sno.lcn

Senior2 Member

jcw122

Member

El<(')>Maxi

Blank Senior Member

fabulouscoops

Member

habbajabba

Member

Cheator

Member

Gnufsh

Senior Member

Captain Newbie

Senior Django-loving Member

anon1

Member

madman22

Member

Gnufsh

Senior Member

Layback Bear

Member

Similar threads