• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

ntldr has gone missing......again. ~~found it!!~~

P

Pilsnerpete

Platinum Member
Sweet file that lets xp work, please tell me where to find you. Would it help if I said "I need you"?
If anyone sees my file, please...let me know.

Actually, I'm working on a machine I built for a girl I know and it misses the ntldr. Is there a way to recover from my blunders? I reinstalled THE XP into a different directory which will hereto and thenceforth be known as "C:\windoze." Original C:\windows won't allow me to access the admin username of the old install. What should I do?
 
This is happening to my parents computer all the time!! I just pop in the windows cd, let up boot up, then go through the repair process and it works fine after that. 😕
 
i usually just do repair when that happens. like if you install win98 on the computer it will do that
 
the fvckin xp anomaly. I need to get this thing fixed...without reinstalling. Can I modify any files to point to c:windows instead of the other?
 
Originally posted by: ReelC00L
Make sure the power cord is plugged in!
Click to expand...

LOL, and the power bar turned on 🙂

Had a user call that her machine shut off on her. Turns out the power bar switch was pushed by a foot reset that she had, and she turn to answer the phone, poof off went the computer. And she need me to figure this out for her...
 
Originally posted by: Bootprint
Originally posted by: ReelC00L
Make sure the power cord is plugged in!
Click to expand...

LOL, and the power bar turned on 🙂

Had a user call that her machine shut off on her. Turns out the power bar switch was pushed by a foot reset that she had, and she turn to answer the phone, poof off went the computer. And she need me to figure this out for her...
Click to expand...
Power bars taste nasty! I like Clif bars.
 
Take out all the PCI cards except the video card and reboot and see what happens. From experience a bad PCI card can cause the NTLDR error. Try it.
 
I wasn't up to fixing it last night as I had about 10 or 11 too many Foster's. That also happens to be my excuse for posting this in OT!!

Got it up and running by making the boot.ini file point to "c:\windows" (original) instead of "c:\windoze" (new install). Simple, yet effective. If you try this, make sure you use a username different from the one in the original install.

BTW, I did locate the file, and also a few of it's friends. They were having a party in the Recycle Bin!!:beer::beer:😀:beer::beer:My friend wanted to do some spring cleaning and she started at the root of C:!!!!! The casualties were config.sys, io.sys, msdos.sys, autoexec.bat, ntdetect.com, ntldr, boot.ini, and pagefile.sys.

I hid the new ones promptly.😉
Thanks for your help guys!
 
Originally posted by: Pilsnerpete
I wasn't up to fixing it last night as I had about 10 or 11 too many Foster's. That also happens to be my excuse for posting this in OT!!

Got it up and running by making the boot.ini file point to "c:\windows" (original) instead of "c:\windoze" (new install). Simple, yet effective. If you try this, make sure you use a username different from the one in the original install.

BTW, I did locate the file, and also a few of it's friends. They were having a party in the Recycle Bin!!:beer::beer:😀:beer::beer:My friend wanted to do some spring cleaning and she started at the root of C:!!!!! The casualties were config.sys, io.sys, msdos.sys, autoexec.bat, ntdetect.com, ntldr, boot.ini, and pagefile.sys.

I hid the new ones promptly.😉
Thanks for your help guys!
Click to expand...


That is a big party..... :beer:

 
Originally posted by: Pilsnerpete
I wasn't up to fixing it last night as I had about 10 or 11 too many Foster's. That also happens to be my excuse for posting this in OT!!

Got it up and running by making the boot.ini file point to "c:\windows" (original) instead of "c:\windoze" (new install). Simple, yet effective. If you try this, make sure you use a username different from the one in the original install.

BTW, I did locate the file, and also a few of it's friends. They were having a party in the Recycle Bin!!:beer::beer:😀:beer::beer:My friend wanted to do some spring cleaning and she started at the root of C:!!!!! The casualties were config.sys, io.sys, msdos.sys, autoexec.bat, ntdetect.com, ntldr, boot.ini, and pagefile.sys.

I hid the new ones promptly.😉
Thanks for your help guys!
Click to expand...

Yes, it always is in the last place you look, isn't it?
 
Originally posted by: ReelC00L
Originally posted by: Pilsnerpete
I wasn't up to fixing it last night as I had about 10 or 11 too many Foster's. That also happens to be my excuse for posting this in OT!!

Got it up and running by making the boot.ini file point to "c:\windows" (original) instead of "c:\windoze" (new install). Simple, yet effective. If you try this, make sure you use a username different from the one in the original install.

BTW, I did locate the file, and also a few of it's friends. They were having a party in the Recycle Bin!!:beer::beer:😀:beer::beer:My friend wanted to do some spring cleaning and she started at the root of C:!!!!! The casualties were config.sys, io.sys, msdos.sys, autoexec.bat, ntdetect.com, ntldr, boot.ini, and pagefile.sys.

I hid the new ones promptly.😉
Thanks for your help guys!
Click to expand...

Yes, it always is in the last place you look, isn't it?
Click to expand...
Only because you stop looking for something once you find it. 😛
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top