If you get an error that NTLDR is not found during bootup,
If you have FAT32 partitions, it is much simpler than with NTFS.
Just boot with a Win98 floppy and copy the NTLDR or NTDETECT.COM files
from the i386 directory to the root of the C:\ drive.
For NTFS:
1.. Insert and boot from your WindowsXP CD.
2.. At the first R=Repair option, press the R key
3.. Press the number that corresponds to the correct location for the
installation of Windows you want to repair.
Typically this will be #1
4.. Enter in the administrator password when requested
5.. Enter in the following commands (X: is replaced by the actual drive
letter that is assigned to the CD ROM drive.
COPY X:\i386\NTLDR C\:
COPY X:\i386\NTDETECT.COM C:\
6.. Take out the CD ROM and type exit
and take the side cover off and make sure the hard drive
is spooling up properly. Any tell-tale clicking noises
coming from the HD would seem to indicate that it is
fried. In all of my years of tech experience, I found
that 99% of the NTLDR error messages had to do with a
dead hard drive instead of the file being missing. No
functioning hard drive=no ntldr file available.
and take the side cover off and make sure the hard drive
is spooling up properly. Any tell-tale clicking noises
coming from the HD would seem to indicate that it is
fried. In all of my years of tech experience, I found
that 99% of the NTLDR error messages had to do with a
dead hard drive instead of the file being missing. No
functioning hard drive=no ntldr file available.
Hi Ron and thanks for the reply. I have been reading as much as I can find
and have found that this MS error report means just about as much as
anyother which is just about nothing accurate. I may or may not have a bad
hard drive. I may or may not have need for complete install of OS. I may
only need to restore boot sectors. Everything seems to be operating fine on
we go until the next MS blunder. I appreciate all your years of experience
but I think this it an XP problem that not many can educate themselves for
as the rules keep changing. At least the error reporting does anyway.
KBA# 320397, however Microsoft points you to your OEM and mine DELL does not
know what I'm talking about and when I point them to MKB they say they
cannot access it because of virus problems(yea right) Microsoft makes no
reference to this file anywhere else on their site.
What happen to mine is something placed 10000 files in my root dir.pushing
NTLDR to the 2nd allocation index, even after you delete the files and
recopy the file to the root dir. your sys can't find it. I think Bcupdate2
utility fixes this if only I could find out where to get it.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
