WinME problem

[DoctorReno]

A friends computer has ME on it. When he attempts to boot from the HD he gets the the error message, "NTLDR Missing Press any key to restart", which, when done, just brings up the same error message.

What gives here? I thought that ME was the last of the DOS based OS's and I don't understand the NT error.

Any help will be appreciated

[PresterJohn]

that message shouldn't appear on a ME machine. did this machine ever have w2k or xp set up on the drive?

Try 'FDISK /MBR' from a 9X or ME bootdisk.

[elroy]

Ran a search on Google with your eror message and every hit refers to Windows 2000. You must have something left over from another installation or ???

[DoctorReno]

According to my friend this is the HP factory install of ME.... never had or been close to an install of 2K or XP. He bought it new and I know he wouldn't attempt to install an OS.
I pulled the drive and put it in one of my machines as a slave and looked at files and it appears to be ME. It's definately FAT and not NTFS.
When I try to boot it on my machine I also get the NTLDR missing error.

EvilRick, I will try your suggestion.

When you put it in your machine, did it ask to upgrade the disk or anything like that? It probably just wrote to the MBR on your behalf.

[DoctorReno]

Rick, nope... it just posted, BIOS detected the drive as the new master, and went straight to the error message when it started to bootfrom the HD. No upgrading of any sort.

You put it in your machine AFTER it gave the NTLDR error ?.
Anyway, FDISKing the MBR will get rid of any NT boot loader files and replace w/ a basic MBR that should work for any 9X or ME install.

Are you sure they didn't try to install XP and exited out before it was done? Just sounds too odd that all of the sudden it would give the NTLDR error.

[DoctorReno]

Rick, it first started the NTLDR error on his machine. He dosen't own a copy of 2k or XP or NT. He hates computers and won't touch one unless he absolutely has to and ABSOLUTELY wouldn't attempt to install an OS. He'll only check his email if you call him and bitch that he's not reading his mail.

Moving on, when I pulled the drive and put it in my machine I put it in as as the primary slave drive so I could simply access the drive and look at the contents. I saw nothing but ME in the system files etc.
I THEN switched the jumpers and made his drive the primary master (my drive was totally disconnected) and I got the NTLDR error.
I'm in total agreement with everybody here that the NTLDR missing error is totally out of context and tried to express that in my original post. I'm wondering if it has something to do with the HP factory install of ME since apparently some machines could be ordered with 2k at the time.

FYI this is an HP Pavillion 6740C that is totally stock off the shelf and the case has never been cracked open until today.

Gremlins . . . they always seem to come around Christmas. Happend back in the 80's, then again in the 90's. Guess they come around every decade.