Thanks Pegasus. I'll give this a try 09/08/2005 AM



"Pegasus \(MVP\)" <I.can@xxxxxxx> wrote in
news:#wrU7$NtFHA.2592@xxxxxxxxxxxxxxxxxxxx:

>
> "Lurker" <lurker@xxxxxxxxxxx> wrote in message
> news:I%YTe.312849$WN5.248778@xxxxxxxxxxxxxxxxxxxxxxxxx
>> "Pegasus \(MVP\)" <I.can@xxxxxxx> wrote in
>> news:eOzQRJHtFHA.3548@xxxxxxxxxxxxxxxxxxxx:
>> Thanks so much for your responses.
>>
>> The system has an OEM eMachines version of XP HOME with a three disk
>> set and does not allow for a repair. The machine is not networked, I
>> do have access to another XP desktop that is the PROFESSIONAL version
>> across the street.
>>
>> In examining the autoexec.bat file I see that it is using ghost to do
>> the re-imaging, and it issues a warning that all data will be lost.
>>
>> It's either a re-install or boot to the A: drive. When I boot to the
>> A: drive I cannot see or change directories to the A: drive. I'll
>> follow the links provided to see if there are any other avenues, or
>> if you bright folks figure out anything that may be helpful it would
>> be greatly appreciated.
>>
>> Thanks so much,
>>
>> JL
>> >
>> > This usually happens after some imaging operation, e.g. with Ghost,
>> > or when additional disks with WinXP on them are installed. It is
>> > caused by the system drive letter being incorrect, thus preventing
>> > WinXP from locating userinit.exe.
>> >
>> > The cure depends on your facilities. Is the machine networked?
>> > Do you have access to another WinXP desktop? See also here:
>> > http://support.microsoft.com/default.aspx?scid=kb;[LN];249321
>
> I'm afraid this is going to be rough ride, as you will have to modify
> the registry without having the benefit of a graphical user interface.
>
> Boot your machine with a floppy boot disk from
> http://home.eunet.no/~pnordahl/ntpasswd/bootdisk.html
> then do this:
>
> 1. Accept the suggested NT partition.
> 2. Accept the full path to the registry directory.
> 3. Type system when prompted
> 4. Type 9 (for Registry Editor)
> 5. Type ? (to see the available commands)
> 6. Type ls (to see the current keys)
> 7. Type cd MountedDevices (it's case-sensitive!)
> 8. Type ls (to see the current values)
> 9. Type dv \DosDevices\C:
> 10. Repeat steps 8 and 9 until you have deleted all values
> that look like this: \DosDevices\X: where X is any letter
> of the alphabet.
> 11. Type q {Enter}, then q {Enter} again
> You will be prompted to save or discard your changes.
>
> I expect that this will fix your problem.

Dude, thanks so much for your help. I'll give this a whirl this morning.
I've been pounding it hard on a network where the users are disabling the
firewall because it won't let them receive files from their buddies.
Sometimes USER is really a four letter word!

Thanks again to all who have responded with their helpful advice!

JL

.



Relevant Pages

  • Re: Thanks Pegasus. Ill give this a try 09/08/2005 AM
    ... >>> Thanks so much for your responses. ... >>> The system has an OEM eMachines version of XP HOME with a three disk ... >> Boot your machine with a floppy boot disk from ... Install a hardware firewall! ...
    (microsoft.public.windowsxp.general)
  • SUMMARY: Problem booting clone system
    ... I got about 15 responses. ... disk subsystem). ... actually installed on the new target system; ... > I keep getting the following boot errors. ...
    (SunManagers)
  • Re: Mirrored SCSI
    ... In this scenario the message and all responses are seen in all ... > install Windows 2003 onto scsi disk 2. ... > Boot the server with disk 2 and if all was well ... > re-constitute the mirror and have scsi 2 replciate over disk 1. ...
    (microsoft.public.win2000.setup_deployment)
  • Re: Mirrored SCSI
    ... In this scenario the message and all responses are seen in all ... > install Windows 2003 onto scsi disk 2. ... > Boot the server with disk 2 and if all was well ... > re-constitute the mirror and have scsi 2 replciate over disk 1. ...
    (microsoft.public.win2000.advanced_server)
  • Re: Mirrored SCSI
    ... In this scenario the message and all responses are seen in all ... > install Windows 2003 onto scsi disk 2. ... > Boot the server with disk 2 and if all was well ... > re-constitute the mirror and have scsi 2 replciate over disk 1. ...
    (microsoft.public.win2000.file_system)