NTLDR is missing

[SoundTheSurrender]

Alright this is a odd problem and I don't understand.

I have a soyo motherboard with ddr and a athlon 1800+ with a maxter 13 gig harddrive.

After windows copies files and restarts i get this error. I can't seem to pin point the problem. Anyone experience this figured out a way?

 

[Zugzwang152]

is this cloning a drive?

link

 

[SoundTheSurrender]

no, its all fresh installation.

 

[Zugzwang152]

what windows version?

 

[SoundTheSurrender]

windows 2000.

 

[Nocturnal]

Try fdisk /mbr. Possibly a virus infecting the master boot record.

 

[SoundTheSurrender]

how could a virus infect if its reformated though? I will try that fdisk command.

Thanks

 

[Zugzwang152]

i doubt it could be a virus. even if it was hooked up to a network (which it shouldn't be if it's not patched), windows hasn't even loaded yet, so there would be no network access since the NIC drivers wouldn't be loaded.

 

[Nocturnal]

I've experinced a virus that does attack the master boot record. Even after numerous formats without formatting the mbr it would come back and I'd get the NTLDR not found.

 

[Macros The Black]

If you can get a program that will zero out the drive... basically formatting the entire drive including the boot record. Almost 99% sure it's a boot record virus.

Also you could just copy NTLDR and NTDETECT onto a floppy and put that into the drive. Then you can boot up totally fine.

 

[SoundTheSurrender]

Originally posted by: Macros The Black
If you can get a program that will zero out the drive... basically formatting the entire drive including the boot record. Almost 99% sure it's a boot record virus.

Also you could just copy NTLDR and NTDETECT onto a floppy and put that into the drive. Then you can boot up totally fine.

I will try this again, but i was suprised.... When i put the harddrive on another computer to look at the contents, there was ntldr, and ntdetect! I'll try again though since i messed with it too much.

 

[imported_g33k]

You did set the hdd as primary boot drive right? If you still have it set to cd-rom it will give you this error.

 

[Eltano1]

Also, if you have a floppy inside the drive, it will give you that error. It happens to one of my users (her PC was shut down due to an storm) when the power came back, she rebooted the PC and got that error. She did not realized that it was a floppy inside the drive, after she removed the disk, everything was back to normal.