» 
NT LDR for Win98 users
For everyone's help - - Thanks!!
I got the NT LDR error message this afternoon trying to load some scanner software and was really sweating it because it is the server for my Roadrunner access. As I have this set up, my Win98 machine (an older HP) is the primary link to the cable and all other access from other computers is via wireless. So when the primary server goes down, so goes the high speed wireless link! Fortunately, I still had my old dial up modem working and logged onto Tech IMO just by doing a search on the NT LDR error message.
I had experienced all the same stuff you all told of and had gone through almost the entire thread on this error message. I got to the one about downloading a Win98 setup disk and this looked like a workable solution. I downloaded the setup disk to a floppy, had printed off roughly 20 of the various fixes, and was ready to go to work on my HP to fix this monster. In the process of inserting the floppy, I discovered that there was another floppy in the A drive. I pulled the floppy out, did another control, alt, delete, and "voilla", the system booted.
Further investigation showed that one of my sons had been downloading and installing a music studio software and forgot to remove the floppy before leaving the computer. Apparently, with that installation in the A drive, and my scanner installation software trying to reboot, created a situation that confused the boot software and prompted the message. Color me "red faced" from embarrassment. After 20+ years of working on computers as a user/developer, some of the most simple omissions can cause you boatloads of grief.
LESSON LEARNED: WHEN TRYING TO REBOOT, CHECK TO MAKE SURE ALL YOUR DRIVES ARE CLEAR, EVEN THE 3.5 FLOPPY'S.
I got lucky folks, but I'm pretty sure the solution below would have worked. I found out, as did others, that the NTLDR file was exactly where it was supposed to be. A command from another software was just directing the computer to look elsewhere.
GOOD LUCK!!
What DOES Work: Floppy Boot, using sys c: command
OMFG...
I wrote a huge reply with details and it was erased by this inane messege board... anyways...
Bovon, thanx for the reply, much appreciated. But...
I had no floppy drive on that PC. I guess you missed that part of my quandry, LOL. (None would be recognized, and it aint da cable). So...
I switched the Hard Drive into another PC, and used the floppy W98 boot diskette, then at the C:\> prompt I typed in:
sys c:
When it finished, it responded with:
System Transferred
And BAM no problems! The previous PC had a hardware problem that caused a big blue screen during W2K setup. After which my NTLDR error came up. I figure I may be able to replace this back into the original PC I was working on and it may work, LOL, nothing like working around some kind of critical error, huh? Was just getting this loaner PC going so I could work on another problem. I'll likely be back with a whole new set of problems. GOOD LUCK to you all.
What DID Work:
_Booting on a W98 Startup Diskette
_Typing sys c: at the prompt
What does NOT work but was suggested:
_ Just copying NTLDR onto the hard drive.
_ Reformatting
_ Reinstalling Windows
* these do NOT help so do not waste your time.
-TommyRay
|