|
Related Topics:
| have lost my taskbar and icons on startup - my computer boots normally but I have no taskbar or icons on my desktop. All that shows is my wallpaper image. appears to run normally, but I have to start with the task manager, and shut down the same way. Anybody know how I..
Remove/delete "My ebooks" and "My Music" icons - I don't use e-books and I don't use my computer to play music or store music on my computer. I have deleted the "My and "My icons from my personal profile and from the all users profile but they still return
Error Message - Recently I have noticed an error message when starting my computer. The message says has encounter and error and must What is this and how can it be What impact is it having on my computer?
Incoming email goes directly to Deleted Items? - After clearing the Windows XP of the ist recent worm, all incoming emails are going directly to Delete box. Did not happen before the worm. WHat is the problem and is there a
dcom - hi, keep getting an error did not register with dcom within required time out. any help would be i don't even know what that means. thanks, milt
|
|
|
Next: Configuration Manage: User account not loaded, settings gone
|
| Author |
Message |
External

Since: Aug 30, 2004 Posts: 239
|
(Msg. 1) Posted: Fri Mar 23, 2007 10:08 am
Post subject: Can not load NTLDR Archived from groups: microsoft>public>windowsxp>configuration_manage, others (more info?)
|
|
|
Hi
The win xp PC is coming with this message. We suspect there was a power
surge overnight. How can this be fixed?
Many Thanks
Regards |
|
| Back to top |
|
 |  |
External

Since: Sep 29, 2006 Posts: 172
|
(Msg. 2) Posted: Fri Mar 23, 2007 10:08 am
Post subject: RE: Can not load NTLDR [Login to view extended thread Info.] Archived from groups: microsoft>public>windowsxp>configuration_manage, others (more info?)
|
|
|
"John" wrote:
> Hi
>
> The win xp PC is coming with this message. We suspect there was a power
> surge overnight. How can this be fixed?
>
> Many Thanks
>
> Regards
Boot up with your CD in the CD ROM and when you presented with Windows Setup
Options:
1- Install Windows
2- Repair existing copy
3- Quit
Select 2 by Pressing R on your keyboard, on the Command Prompt type:
C:\Windows>CD.. Hit [Enter..] on your Keyboard
on the new Prompt type this:
C:\>
copy X:\i386\ntldr c:\ where X is the Drive Letter for your CD-Rom
copy X:\i386\ntdetect.com c:\ " " "
Please type one at a time click/Hit [Enter..]
You may need to rebuild your Boot.ini type this on the Prompt:
C:\>Boot.ini click Enter and you will see your Boot.ini you can Edit it or
if was intact leave as is, the boot.ini will look like this, be aware this
for XP Home so if you have XP pro:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /fastdetect
You will get Boot Identifier: Enter this " Microsoft Windows XP Home Edition"
Boot Loader: Enter this" /fastdetect"
When you finished type: reboot (I'm not sure if it is right you can Type ?
to get the list of commands and see if reboot is one) or Exit.
If still no joy try this link:
http://www.michaelstevenstech.com/XPrepairinstall.htm
HTH.
Please let us know.
Regards,
nass
===
www.nasstec.co.uk |
|
| Back to top |
|
 |  |
|
FreeComputerConsultant.co
|
External

Since: Feb 16, 2007 Posts: 8
|
(Msg. 3) Posted: Fri Mar 23, 2007 10:08 am
Post subject: Re: Can not load NTLDR [Login to view extended thread Info.] Archived from groups: microsoft>public>windowsxp>configuration_manage, others (more info?)
|
|
|
I had this on a client just the other day.
Use previously posted instructions to boot to command console (you may
want to consider installing cmdcons for next time)
run Chkdsk
If finds errors, that may fix it.
Reboot
www.FreeComputerConsultant.com
John wrote:
> Hi
>
> The win xp PC is coming with this message. We suspect there was a power
> surge overnight. How can this be fixed?
>
> Many Thanks
>
> Regards
>
> |
|
| Back to top |
|
 |  |
External

Since: Mar 23, 2007 Posts: 19
|
(Msg. 4) Posted: Fri Mar 23, 2007 10:08 am
Post subject: Re: Can not load NTLDR [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"John" wrote:
> The win xp PC is coming with this message. We suspect
> there was a power surge overnight. How can this be fixed?
Do you have more than one hard drive? The BIOS's
hard drive boot order may have changed, putting a
different hard drive at the head of the list.
*TimDaniels* |
|
| Back to top |
|
 |  |
External

Since: Aug 30, 2004 Posts: 239
|
(Msg. 5) Posted: Fri Mar 23, 2007 3:35 pm
Post subject: Re: Can not load NTLDR [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
Sorry for being naive but what is cmdcons?
Thanks
Regards
"FreeComputerConsultant.com" <none.RemoveThis@none.com> wrote in message
news:OlUlPZVbHHA.4832@TK2MSFTNGP02.phx.gbl...
>I had this on a client just the other day.
>
> Use previously posted instructions to boot to command console (you may
> want to consider installing cmdcons for next time)
>
> run Chkdsk
>
> If finds errors, that may fix it.
>
> Reboot
>
> www.FreeComputerConsultant.com
>
> John wrote:
>> Hi
>>
>> The win xp PC is coming with this message. We suspect there was a power
>> surge overnight. How can this be fixed?
>>
>> Many Thanks
>>
>> Regards |
|
| Back to top |
|
 |  |
External

Since: Mar 23, 2007 Posts: 9
|
(Msg. 6) Posted: Fri Mar 23, 2007 11:59 pm
Post subject: Re: Can not load NTLDR [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
You might want to check the disk setting in your BIOS. Had the same thing
happen & it turned out the hard drive parameters were corrupted.
On Fri, 23 Mar 2007 10:08:06 -0000, "John" <John.DeleteThis@nospam.infovis.co.uk> wrote:
>Hi
>
>The win xp PC is coming with this message. We suspect there was a power
>surge overnight. How can this be fixed?
>
>Many Thanks
>
>Regards
>
--
Australia isn't "down under", it's "off to one side"!
stanblaz.DeleteThis@netspace.net.au
www.cobracat.com (home of the Australian Cobra Catamaran)
www.parkdaleyc.com (where most of them sail)
http://groups.yahoo.com/group/cobra-cat/ |
|
| Back to top |
|
 |  |
External

Since: Mar 24, 2007 Posts: 33
|
(Msg. 7) Posted: Sat Mar 24, 2007 1:42 am
Post subject: Re: Can not load NTLDR [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
|
|
| Back to top |
|
 |  |
External

Since: Mar 24, 2007 Posts: 1
|
(Msg. 8) Posted: Sat Mar 24, 2007 9:25 am
Post subject: Re: Can not load NTLDR [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
John
First follow Nass's suggestion. Still you are facing the problem then
do the following.
If the mother board battery is weak then sometimes bios wo'nt detect
your harddisk. Then also you face the problem of cannot load NTLDR.
Try to replace battery.
http://technodata.blogspot.com |
|
| Back to top |
|
 |  |
|
FreeComputerConsultant.co
|
External

Since: Feb 16, 2007 Posts: 8
|
(Msg. 9) Posted: Mon Mar 26, 2007 8:40 am
Post subject: Re: Can not load NTLDR [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
Command console.
Install it with the /cmdcons switch - gives you the boot option of the
command console for system repairs.
Same as booting from CD and selecting repair, just a whole lot more
convenient.
I normally copy the i386 directory to C: when setting up new PC's, so
it's available.
then:
C:
Cd \i386
Winnt32 /cmdcons
John wrote:
> Sorry for being naive but what is cmdcons?
>
> Thanks
>
> Regards
>
> "FreeComputerConsultant.com" <none.RemoveThis@none.com> wrote in message
> news:OlUlPZVbHHA.4832@TK2MSFTNGP02.phx.gbl...
>> I had this on a client just the other day.
>>
>> Use previously posted instructions to boot to command console (you may
>> want to consider installing cmdcons for next time)
>>
>> run Chkdsk
>>
>> If finds errors, that may fix it.
>>
>> Reboot
>>
>> www.FreeComputerConsultant.com
>>
>> John wrote:
>>> Hi
>>>
>>> The win xp PC is coming with this message. We suspect there was a power
>>> surge overnight. How can this be fixed?
>>>
>>> Many Thanks
>>>
>>> Regards
>
> |
|
| Back to top |
|
 |  |
External

Since: Feb 13, 2007 Posts: 107
|
(Msg. 10) Posted: Mon Mar 26, 2007 5:44 pm
Post subject: Re: Can not load NTLDR [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"FreeComputerConsultant.com" <none.TakeThisOut@none.com> wrote
> Command console.
>
> Install it with the /cmdcons switch - gives you the boot option of the
> command console for system repairs.
>
> Same as booting from CD and selecting repair, just a whole lot more
> convenient.
>
> I normally copy the i386 directory to C: when setting up new PC's, so it's
> available.
>
> then:
>
> C:
> Cd \i386
> Winnt32 /cmdcons
> John wrote:
>> Sorry for being naive but what is cmdcons?
>> "FreeComputerConsultant.com" <none.TakeThisOut@none.com> wrote
>>> I had this on a client just the other day.
>>>
>>> Use previously posted instructions to boot to command console (you may
>>> want to consider installing cmdcons for next time)
>>>
>>> run Chkdsk
>>>
>>> If finds errors, that may fix it.
>>>
>>> Reboot
>>>
>>> www.FreeComputerConsultant.com
>>>
>>> John wrote:
>>>> Hi
>>>>
>>>> The win xp PC is coming with this message. We suspect there was a power
>>>> surge overnight. How can this be fixed?
You mean Recovery Console, eh?
--
Rock [MS-MVP User/Shell] |
|
| Back to top |
|
 |  |
|
FreeComputerConsultant.co
|
External

Since: Feb 16, 2007 Posts: 8
|
(Msg. 11) Posted: Tue Mar 27, 2007 7:52 am
Post subject: Re: Can not load NTLDR [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
Yep. I guess I always refer to it as command console. More authoritative
ring to it - less desperation!
Old dog, new tricks, you know.
Rock wrote:
> "FreeComputerConsultant.com" <none.TakeThisOut@none.com> wrote
>> Command console.
>>
>> Install it with the /cmdcons switch - gives you the boot option of the
>> command console for system repairs.
>>
>> Same as booting from CD and selecting repair, just a whole lot more
>> convenient.
>>
>> I normally copy the i386 directory to C: when setting up new PC's, so
>> it's available.
>>
>> then:
>>
>> C:
>> Cd \i386
>> Winnt32 /cmdcons
>
>> John wrote:
>>> Sorry for being naive but what is cmdcons?
>
>>> "FreeComputerConsultant.com" <none.TakeThisOut@none.com> wrote
>>>> I had this on a client just the other day.
>>>>
>>>> Use previously posted instructions to boot to command console (you
>>>> may want to consider installing cmdcons for next time)
>>>>
>>>> run Chkdsk
>>>>
>>>> If finds errors, that may fix it.
>>>>
>>>> Reboot
>>>>
>>>> www.FreeComputerConsultant.com
>>>>
>>>> John wrote:
>>>>> Hi
>>>>>
>>>>> The win xp PC is coming with this message. We suspect there was a
>>>>> power surge overnight. How can this be fixed?
>
> You mean Recovery Console, eh?
> |
|
| Back to top |
|
 |  |
External

Since: Mar 13, 2005 Posts: 24
|
(Msg. 12) Posted: Wed Mar 28, 2007 12:12 am
Post subject: Re: Can not load NTLDR [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
Original poster wrote...
>>>>> The win xp PC is coming with this message. We suspect there was a power
>>>>> surge overnight. How can this be fixed?
It really disturbs me that so far, not one poster has considered WHY
the NTLDR file "just disappeared", nor considered the possibility of
hardware damage from the spike, such as a damaged HD, or significant
corruption of the file system. It's all been taking the request at
face value, advocating recovery-unsafe steps that write to disk.
A "no NTLDR" message implies that an NT boot loader is not finding
C:\NTLDR, and that can happen if:
1) HD boots OK, MBR OK, PBR OK, file system not OK
To see that message from a HD boot, would imply successful passing
through MBR, partition table and PBR logic - so that steps to write a
new MBR or PBR are unlikely to be relevant.
Why would \NTLDR vanish? It's hardly ever written to, so a simple
"bad exit" doesn't explain this. If the HD is booting at all, then
you HAVE to consider the likelyhood of significant file system damage,
if not physical HD damage.
Under those circumstances, the first priority is not getting Windows
to boot, as Windows *always* writes to the file system and is thus
fundamentally unsafe when the file system or HD is at risk.
The first priority is to evacuate the data from the HD, then attempt
to preserve the installation, then verify RAM, physical HD, and file
system quality (in that order) and only then, bother with Windows.
2) PC is booting from an NT-formatted diskette
Even though it's impossible to boot the whole of NT off a 1.44M
diskette, nonetheless NT creates "find NTLDR and boot it" boot code on
diskettes that it formats.
If such a diskette is left in the system at boot, and CMOS boot order
boots diskette before HD (as is usually the duhfault) you see this.
Surges and lumpy power often reset CMOS settings and NVRAM, so the
only "happy ending" I'd count on here is that:
- the PC normally boots HD before diskette
- an NT-formatted diskette has been forgotten in the drive
- the surge or whatever blew CMOS back to duhfaults
- now the PC attempts to boot the diskette, and fails as above
3) PC is booting the wrong HD
If there's a HD left in the system that has an NT/XP etc. installation
ftrom another PC, then this would typically present as follows:
- the NT/XP/etc. installation attempts to boot
- the boot process fails with a STOP (BSoD) error
- if duuuuhfault settings, will auto-reboot endlessly
However, if an old NT/XP/etc. installation was deleted from a HD,
leaving the original PBR (Partition Boot Record) in place, then you
will get exactly this scenario; the attempt to boot NT/XP/etc. fails
long before any OS code "big enough" to STOP/BSoD is found.
Once again, loss of CMOS settings from a power glitch can cause this
pattern, especially where the new HD is S-ATA and the old HD is IDE.
The duhfault BIOS boot order is usually IDE before S-ATA.
Note a scenario not listed here, is CMOS corruption such that the HD
is not found and thus not booted. This would not give rise to the
decribed failure pattern because BIOS has no awareness of OSs and
files such as NTLDR.
>------------ ----- ---- --- -- - - - -
The most accurate diagnostic instrument
in medicine is the Retrospectoscope
>------------ ----- ---- --- -- - - - - |
|
| Back to top |
|
 |  |
|