Does win98 support ntfs?
I know people have had this problem before but this is a little different.
I reformatted my drive a few days ago and started getting this message when I tried to reinstall windows.....So I reformatted again.....still having the problem...the thing that really confuses me though is I can take it outa my car and hook it up to my desktop pc (as a slave drive) and install windows with no problem then I can run windows off of it with now problem....but if I hook it up as a master/single drive (to the same computer) it goes back to the ntldr missing.... but make it a slave again and everything runs fine?
anyone have any ideas?? I don't want to go buy a new HD but I've been playing around with it for a few days to no avail. if I can find my windows 98 disk I'm going to try installing that and then just updating....but I just moved and am 95% sure I trashed the disk thinking that I'd never need it again
Doesnt look like it does, the ms support site has a section on going back to win98 and tells you to format in fat32Originally Posted by stuseed
hook it up to your desktop pc and use disk management to un-assign the drive letter of the drive that won't boot (d: or e: or whatever it is). then try reconnecting the drive in the car.
if you ever need a bootdisk, you can always check bootdisk.com
Originally Posted by tiburonputer
I think this is the important bit. You have installed the OS on a slave drive.
The boot loader is on the master drive.
When you boot in this configuration the system looks at the master drive, finds boot loader, then jumps to the salve drive for the actual OS.
when you make this drive the master, there is no bootloader, therefore it cannot boot hence the NTLDR is missing error message.
Make this a master drive, boot from the XP (w2K) CD and install windows.
I had this problem last week and put the XP disk in and booted to recovery console and rebuilt the MBR on the drive with the OS and it worked fine after that.
Dont tell me to shut up, I'm Rick James ******!!!
I know this thread is 2 weeks out but thought I would throw in my 2 cents since I just had this problem this weekend using Drive Image to upgrade to a bigger drive. I had to do the following commands from the windows recovery console
copy g:\i386\ntldr c:\
copy g:\i386\ntdetect.com c:\
g is the drive letter that your windows disk is loaded into, change that to what ever drive you have the disk loaded into. This fixed my problem as well as some system hang up at the log on screen where the system would not go any further thant he welcome announcement. When you do FixMBR the system will give you a scary your gonna ruin your drive message, just hit yes and pray for teh best.