ntldr renamed

[bob]

I was working at my pc when I saw a message flash that the system was
shutting down. when I restarted I got the error "ntldr is missing
press ctl alt delete".I was able to boot from the xp install disk and
get to a command prompt. the ntldr file had been renamed to _ntldr.
Once I renamed it I was able to restart okay. Seems like a virus to me
but we have office scan updated daily and ran on every pc daily. Does
anyone know the source of this event or how I might prevent or prepare
for it. Could it be a developing hardware problem ? How would I make a
bootable disk in case I dont have acess to the install disk? Its
usually locked away. Thanks for reading

 

[Pegasus \(MVP\)]

I was working at my pc when I saw a message flash that the system was
shutting down. when I restarted I got the error "ntldr is missing
press ctl alt delete".I was able to boot from the xp install disk and
get to a command prompt. the ntldr file had been renamed to _ntldr.
Once I renamed it I was able to restart okay. Seems like a virus to me
but we have office scan updated daily and ran on every pc daily. Does
anyone know the source of this event or how I might prevent or prepare
for it. Could it be a developing hardware problem ? How would I make a
bootable disk in case I dont have acess to the install disk? Its
usually locked away. Thanks for reading

It is virtually impossible that a hardware problem causes this
sort of thing. I suspect malware.

You can make a WinXP boot disk like so:
- Format a floppy disk on your WinXP PC.
- Copy these hidden files to the floppy disk:
c:\ntldr
c:\ntdetect.com
c:\boot.ini

Now boot the machine with this diskette. It will
take a little longer at the beginning but it will work!

 

[cyphrbob]

I was working at my pc when I saw a message flash that the system was
shutting down. when I restarted I got the error "ntldr is missing
press ctl alt delete".I was able to boot from the xp install disk and
get to a command prompt. the ntldr file had been renamed to _ntldr.
Once I renamed it I was able to restart okay. Seems like a virus to me
but we have office scan updated daily and ran on every pc daily. Does
anyone know the source of this event or how I might prevent or prepare
for it. Could it be a developing hardware problem ? How would I make a
bootable disk in case I dont have acess to the install disk? Its
usually locked away. Thanks for reading

Thanks. yes duh, when I googled this error I got some stuff about a
corrupted file etc or faulty drive controller. But the fact that it
was renamed would rule out hardware. I just have to find out where it
is coming from.