Logon Help Needed

[Sturdy]

Hi all,

After a bout with operator head space, I have managed to make my dual-boot
W2k Pro box unbootable. Now when I try to logon, the logon dialog returns
after a few seconds. Oddly both OS present the same issue so it is likely
related to a common cause. Here is some additional info:

1) I had re-sized partitions on physical drive 0 when this happened (using
GPartEd). Somehow my old C: is now F:. The new C: is an old data drive (I.
No partitions were moved, just deleted or resized. I can boot into F: using a
modified boot.ini on a boot floppy but it comes back to the logon.

2) I also resized partions on drive 1 where both OS shared a swap file. One
OS is now reporting the swap file is too small before it comes back to the
logon dialog. Is it possible the swap file is now unreachable and causing the
issue? If so, how do I create a swap file if I can't logon?

3) Since logical drive F: is now on partition 0, is it possible I need a new
MBR or the partition flagged for boot? If so, how?

Over the years, I've done some partition editing without any major issue
until now. GPartEd appears to be a good editor and I don't think it is the
cause of this problem. W2k did run chkdsk after the resizing but no issues
were found. I am able to load the repair console from the original install
CD which may help.

Does anyone know how I can get passed the logon?

TIA and regards,
Sturdy

 

[Pegasus \(MVP\)]

"Sturdy" <Sturdy@discussions.microsoft.com> wrote in message
news:6335F2FF-C691-4A64-8A4E-6BCE67BDB01B@microsoft.com...
> Hi all,
>
> After a bout with operator head space, I have managed to make my dual-boot
> W2k Pro box unbootable. Now when I try to logon, the logon dialog returns
> after a few seconds. Oddly both OS present the same issue so it is likely
> related to a common cause. Here is some additional info:
>
> 1) I had re-sized partitions on physical drive 0 when this happened (using
> GPartEd). Somehow my old C: is now F:. The new C: is an old data drive
> (I.
> No partitions were moved, just deleted or resized. I can boot into F:
> using a
> modified boot.ini on a boot floppy but it comes back to the logon.
>
> 2) I also resized partions on drive 1 where both OS shared a swap file.
> One
> OS is now reporting the swap file is too small before it comes back to the
> logon dialog. Is it possible the swap file is now unreachable and causing
> the
> issue? If so, how do I create a swap file if I can't logon?
>
> 3) Since logical drive F: is now on partition 0, is it possible I need a
> new
> MBR or the partition flagged for boot? If so, how?
>
> Over the years, I've done some partition editing without any major issue
> until now. GPartEd appears to be a good editor and I don't think it is the
> cause of this problem. W2k did run chkdsk after the resizing but no issues
> were found. I am able to load the repair console from the original
> install
> CD which may help.
>
> Does anyone know how I can get passed the logon?
>
> TIA and regards,
> Sturdy

You have already provided the answer in your post: Your
drive letters are mixed up, which means that Windows can
no longer locate userinit.exe.

The cure is simple if the machine is networked, and not
so simple if it is not. What's yours?

 

[Sturdy]

Hi Pegasus,

Thanks for the quick response. I like simple! Yes, it is networked via wifi
but those drivers won't install until I can logon.

"Pegasus (MVP)" wrote:

>
> "Sturdy" <Sturdy@discussions.microsoft.com> wrote in message
> news:6335F2FF-C691-4A64-8A4E-6BCE67BDB01B@microsoft.com...
> > Hi all,
> >
> > After a bout with operator head space, I have managed to make my dual-boot
> > W2k Pro box unbootable. Now when I try to logon, the logon dialog returns
> > after a few seconds. Oddly both OS present the same issue so it is likely
> > related to a common cause. Here is some additional info:
> >
> > 1) I had re-sized partitions on physical drive 0 when this happened (using
> > GPartEd). Somehow my old C: is now F:. The new C: is an old data drive
> > (I.
> > No partitions were moved, just deleted or resized. I can boot into F:
> > using a
> > modified boot.ini on a boot floppy but it comes back to the logon.
> >
> > 2) I also resized partions on drive 1 where both OS shared a swap file.
> > One
> > OS is now reporting the swap file is too small before it comes back to the
> > logon dialog. Is it possible the swap file is now unreachable and causing
> > the
> > issue? If so, how do I create a swap file if I can't logon?
> >
> > 3) Since logical drive F: is now on partition 0, is it possible I need a
> > new
> > MBR or the partition flagged for boot? If so, how?
> >
> > Over the years, I've done some partition editing without any major issue
> > until now. GPartEd appears to be a good editor and I don't think it is the
> > cause of this problem. W2k did run chkdsk after the resizing but no issues
> > were found. I am able to load the repair console from the original
> > install
> > CD which may help.
> >
> > Does anyone know how I can get passed the logon?
> >
> > TIA and regards,
> > Sturdy
>
> You have already provided the answer in your post: Your
> drive letters are mixed up, which means that Windows can
> no longer locate userinit.exe.
>
> The cure is simple if the machine is networked, and not
> so simple if it is not. What's yours?
>
>
>

 

[Sturdy]

Pegasus,

After your hint, I was able to find KB article Q24931 which sounds like my
problem but I won't be able to try it until tonight. Thanks for the assist
and I'll let you know how this comes out.

Sturdy

"Pegasus (MVP)" wrote:

>
> "Sturdy" <Sturdy@discussions.microsoft.com> wrote in message
> news:6335F2FF-C691-4A64-8A4E-6BCE67BDB01B@microsoft.com...
> > Hi all,
> >
> > After a bout with operator head space, I have managed to make my dual-boot
> > W2k Pro box unbootable. Now when I try to logon, the logon dialog returns
> > after a few seconds. Oddly both OS present the same issue so it is likely
> > related to a common cause. Here is some additional info:
> >
> > 1) I had re-sized partitions on physical drive 0 when this happened (using
> > GPartEd). Somehow my old C: is now F:. The new C: is an old data drive
> > (I.
> > No partitions were moved, just deleted or resized. I can boot into F:
> > using a
> > modified boot.ini on a boot floppy but it comes back to the logon.
> >
> > 2) I also resized partions on drive 1 where both OS shared a swap file.
> > One
> > OS is now reporting the swap file is too small before it comes back to the
> > logon dialog. Is it possible the swap file is now unreachable and causing
> > the
> > issue? If so, how do I create a swap file if I can't logon?
> >
> > 3) Since logical drive F: is now on partition 0, is it possible I need a
> > new
> > MBR or the partition flagged for boot? If so, how?
> >
> > Over the years, I've done some partition editing without any major issue
> > until now. GPartEd appears to be a good editor and I don't think it is the
> > cause of this problem. W2k did run chkdsk after the resizing but no issues
> > were found. I am able to load the repair console from the original
> > install
> > CD which may help.
> >
> > Does anyone know how I can get passed the logon?
> >
> > TIA and regards,
> > Sturdy
>
> You have already provided the answer in your post: Your
> drive letters are mixed up, which means that Windows can
> no longer locate userinit.exe.
>
> The cure is simple if the machine is networked, and not
> so simple if it is not. What's yours?
>
>
>

 

[Sturdy]

Not so simple...ping does not reach the offending computer. Also cannot use
SET to change variables to true to allow mkdir. If this was the simple way, I
guess I'm ready to try the hard way -)

"Pegasus (MVP)" wrote:

>
> "Sturdy" <Sturdy@discussions.microsoft.com> wrote in message
> news:6335F2FF-C691-4A64-8A4E-6BCE67BDB01B@microsoft.com...
> > Hi all,
> >
> > After a bout with operator head space, I have managed to make my dual-boot
> > W2k Pro box unbootable. Now when I try to logon, the logon dialog returns
> > after a few seconds. Oddly both OS present the same issue so it is likely
> > related to a common cause. Here is some additional info:
> >
> > 1) I had re-sized partitions on physical drive 0 when this happened (using
> > GPartEd). Somehow my old C: is now F:. The new C: is an old data drive
> > (I.
> > No partitions were moved, just deleted or resized. I can boot into F:
> > using a
> > modified boot.ini on a boot floppy but it comes back to the logon.
> >
> > 2) I also resized partions on drive 1 where both OS shared a swap file.
> > One
> > OS is now reporting the swap file is too small before it comes back to the
> > logon dialog. Is it possible the swap file is now unreachable and causing
> > the
> > issue? If so, how do I create a swap file if I can't logon?
> >
> > 3) Since logical drive F: is now on partition 0, is it possible I need a
> > new
> > MBR or the partition flagged for boot? If so, how?
> >
> > Over the years, I've done some partition editing without any major issue
> > until now. GPartEd appears to be a good editor and I don't think it is the
> > cause of this problem. W2k did run chkdsk after the resizing but no issues
> > were found. I am able to load the repair console from the original
> > install
> > CD which may help.
> >
> > Does anyone know how I can get passed the logon?
> >
> > TIA and regards,
> > Sturdy
>
> You have already provided the answer in your post: Your
> drive letters are mixed up, which means that Windows can
> no longer locate userinit.exe.
>
> The cure is simple if the machine is networked, and not
> so simple if it is not. What's yours?
>
>
>

 

[Pegasus \(MVP\)]

Ping won't solve anything but editing the registry of the
problem machine remotely will. Try this:
1. Log on under "administrator" at a networked PC.
2. Run this command from a Command Prompt:
psexec \\aaa.bbb.ccc.ddd cmd
(replace aaa.bbb etc. with the correct IP address
or the NetBIOS name of the problem PC.
3. Make a note of the drive letter you get.
4. Exit back to the networked PC.
5. Run regedit, then open the registry of the problem PC.
6. Navigate to HKLM\SYSTEM\MountedDevices
7. Delete \DosDevices\C:
8. Rename \DosDevices\X: to \DosDevices\C:, where
X: is the drive letter you found in Step 3.
9. Use shutdown.exe to reboot the problem PC.
You can download psexec.exe from www.sysinternals.com.


"Sturdy" <Sturdy@discussions.microsoft.com> wrote in message
news:60379614-65BE-467A-B7D3-587FB9B7E0DC@microsoft.com...
> Not so simple...ping does not reach the offending computer. Also cannot
> use
> SET to change variables to true to allow mkdir. If this was the simple
> way, I
> guess I'm ready to try the hard way -)
>
> "Pegasus (MVP)" wrote:
>
>>
>> "Sturdy" <Sturdy@discussions.microsoft.com> wrote in message
>> news:6335F2FF-C691-4A64-8A4E-6BCE67BDB01B@microsoft.com...
>> > Hi all,
>> >
>> > After a bout with operator head space, I have managed to make my
>> > dual-boot
>> > W2k Pro box unbootable. Now when I try to logon, the logon dialog
>> > returns
>> > after a few seconds. Oddly both OS present the same issue so it is
>> > likely
>> > related to a common cause. Here is some additional info:
>> >
>> > 1) I had re-sized partitions on physical drive 0 when this happened
>> > (using
>> > GPartEd). Somehow my old C: is now F:. The new C: is an old data drive
>> > (I.
>> > No partitions were moved, just deleted or resized. I can boot into F:
>> > using a
>> > modified boot.ini on a boot floppy but it comes back to the logon.
>> >
>> > 2) I also resized partions on drive 1 where both OS shared a swap file.
>> > One
>> > OS is now reporting the swap file is too small before it comes back to
>> > the
>> > logon dialog. Is it possible the swap file is now unreachable and
>> > causing
>> > the
>> > issue? If so, how do I create a swap file if I can't logon?
>> >
>> > 3) Since logical drive F: is now on partition 0, is it possible I need
>> > a
>> > new
>> > MBR or the partition flagged for boot? If so, how?
>> >
>> > Over the years, I've done some partition editing without any major
>> > issue
>> > until now. GPartEd appears to be a good editor and I don't think it is
>> > the
>> > cause of this problem. W2k did run chkdsk after the resizing but no
>> > issues
>> > were found. I am able to load the repair console from the original
>> > install
>> > CD which may help.
>> >
>> > Does anyone know how I can get passed the logon?
>> >
>> > TIA and regards,
>> > Sturdy
>>
>> You have already provided the answer in your post: Your
>> drive letters are mixed up, which means that Windows can
>> no longer locate userinit.exe.
>>
>> The cure is simple if the machine is networked, and not
>> so simple if it is not. What's yours?
>>
>>
>>

 

[Sturdy]

WHOOOPEEEE...it works! Thanks, Pegasus. I had a little trouble getting logged
on thru regedit until I realized the admin account name and pwd needed to be
the same on each box. Problem resolved and back in business. Much appreciated.

Sturdy

"Pegasus (MVP)" wrote:

> Ping won't solve anything but editing the registry of the
> problem machine remotely will. Try this:
> 1. Log on under "administrator" at a networked PC.
> 2. Run this command from a Command Prompt:
> psexec \\aaa.bbb.ccc.ddd cmd
> (replace aaa.bbb etc. with the correct IP address
> or the NetBIOS name of the problem PC.
> 3. Make a note of the drive letter you get.
> 4. Exit back to the networked PC.
> 5. Run regedit, then open the registry of the problem PC.
> 6. Navigate to HKLM\SYSTEM\MountedDevices
> 7. Delete \DosDevices\C:
> 8. Rename \DosDevices\X: to \DosDevices\C:, where
> X: is the drive letter you found in Step 3.
> 9. Use shutdown.exe to reboot the problem PC.
> You can download psexec.exe from www.sysinternals.com.
>
>
> "Sturdy" <Sturdy@discussions.microsoft.com> wrote in message
> news:60379614-65BE-467A-B7D3-587FB9B7E0DC@microsoft.com...
> > Not so simple...ping does not reach the offending computer. Also cannot
> > use
> > SET to change variables to true to allow mkdir. If this was the simple
> > way, I
> > guess I'm ready to try the hard way -)
> >
> > "Pegasus (MVP)" wrote:
> >
> >>
> >> "Sturdy" <Sturdy@discussions.microsoft.com> wrote in message
> >> news:6335F2FF-C691-4A64-8A4E-6BCE67BDB01B@microsoft.com...
> >> > Hi all,
> >> >
> >> > After a bout with operator head space, I have managed to make my
> >> > dual-boot
> >> > W2k Pro box unbootable. Now when I try to logon, the logon dialog
> >> > returns
> >> > after a few seconds. Oddly both OS present the same issue so it is
> >> > likely
> >> > related to a common cause. Here is some additional info:
> >> >
> >> > 1) I had re-sized partitions on physical drive 0 when this happened
> >> > (using
> >> > GPartEd). Somehow my old C: is now F:. The new C: is an old data drive
> >> > (I.
> >> > No partitions were moved, just deleted or resized. I can boot into F:
> >> > using a
> >> > modified boot.ini on a boot floppy but it comes back to the logon.
> >> >
> >> > 2) I also resized partions on drive 1 where both OS shared a swap file.
> >> > One
> >> > OS is now reporting the swap file is too small before it comes back to
> >> > the
> >> > logon dialog. Is it possible the swap file is now unreachable and
> >> > causing
> >> > the
> >> > issue? If so, how do I create a swap file if I can't logon?
> >> >
> >> > 3) Since logical drive F: is now on partition 0, is it possible I need
> >> > a
> >> > new
> >> > MBR or the partition flagged for boot? If so, how?
> >> >
> >> > Over the years, I've done some partition editing without any major
> >> > issue
> >> > until now. GPartEd appears to be a good editor and I don't think it is
> >> > the
> >> > cause of this problem. W2k did run chkdsk after the resizing but no
> >> > issues
> >> > were found. I am able to load the repair console from the original
> >> > install
> >> > CD which may help.
> >> >
> >> > Does anyone know how I can get passed the logon?
> >> >
> >> > TIA and regards,
> >> > Sturdy
> >>
> >> You have already provided the answer in your post: Your
> >> drive letters are mixed up, which means that Windows can
> >> no longer locate userinit.exe.
> >>
> >> The cure is simple if the machine is networked, and not
> >> so simple if it is not. What's yours?
> >>
> >>
> >>
>
>
>

 

[Pegasus \(MVP\)]

Glad it worked for you - thanks for the feedback.


"Sturdy" <Sturdy@discussions.microsoft.com> wrote in message
news:BF1F1C9C-89F8-47AA-BAA5-A30C5D378A3D@microsoft.com...
> WHOOOPEEEE...it works! Thanks, Pegasus. I had a little trouble getting
> logged
> on thru regedit until I realized the admin account name and pwd needed to
> be
> the same on each box. Problem resolved and back in business. Much
> appreciated.
>
> Sturdy
>
> "Pegasus (MVP)" wrote:
>
>> Ping won't solve anything but editing the registry of the
>> problem machine remotely will. Try this:
>> 1. Log on under "administrator" at a networked PC.
>> 2. Run this command from a Command Prompt:
>> psexec \\aaa.bbb.ccc.ddd cmd
>> (replace aaa.bbb etc. with the correct IP address
>> or the NetBIOS name of the problem PC.
>> 3. Make a note of the drive letter you get.
>> 4. Exit back to the networked PC.
>> 5. Run regedit, then open the registry of the problem PC.
>> 6. Navigate to HKLM\SYSTEM\MountedDevices
>> 7. Delete \DosDevices\C:
>> 8. Rename \DosDevices\X: to \DosDevices\C:, where
>> X: is the drive letter you found in Step 3.
>> 9. Use shutdown.exe to reboot the problem PC.
>> You can download psexec.exe from www.sysinternals.com.
>>
>>
>> "Sturdy" <Sturdy@discussions.microsoft.com> wrote in message
>> news:60379614-65BE-467A-B7D3-587FB9B7E0DC@microsoft.com...
>> > Not so simple...ping does not reach the offending computer. Also cannot
>> > use
>> > SET to change variables to true to allow mkdir. If this was the simple
>> > way, I
>> > guess I'm ready to try the hard way -)
>> >
>> > "Pegasus (MVP)" wrote:
>> >
>> >>
>> >> "Sturdy" <Sturdy@discussions.microsoft.com> wrote in message
>> >> news:6335F2FF-C691-4A64-8A4E-6BCE67BDB01B@microsoft.com...
>> >> > Hi all,
>> >> >
>> >> > After a bout with operator head space, I have managed to make my
>> >> > dual-boot
>> >> > W2k Pro box unbootable. Now when I try to logon, the logon dialog
>> >> > returns
>> >> > after a few seconds. Oddly both OS present the same issue so it is
>> >> > likely
>> >> > related to a common cause. Here is some additional info:
>> >> >
>> >> > 1) I had re-sized partitions on physical drive 0 when this happened
>> >> > (using
>> >> > GPartEd). Somehow my old C: is now F:. The new C: is an old data
>> >> > drive
>> >> > (I.
>> >> > No partitions were moved, just deleted or resized. I can boot into
>> >> > F:
>> >> > using a
>> >> > modified boot.ini on a boot floppy but it comes back to the logon.
>> >> >
>> >> > 2) I also resized partions on drive 1 where both OS shared a swap
>> >> > file.
>> >> > One
>> >> > OS is now reporting the swap file is too small before it comes back
>> >> > to
>> >> > the
>> >> > logon dialog. Is it possible the swap file is now unreachable and
>> >> > causing
>> >> > the
>> >> > issue? If so, how do I create a swap file if I can't logon?
>> >> >
>> >> > 3) Since logical drive F: is now on partition 0, is it possible I
>> >> > need
>> >> > a
>> >> > new
>> >> > MBR or the partition flagged for boot? If so, how?
>> >> >
>> >> > Over the years, I've done some partition editing without any major
>> >> > issue
>> >> > until now. GPartEd appears to be a good editor and I don't think it
>> >> > is
>> >> > the
>> >> > cause of this problem. W2k did run chkdsk after the resizing but no
>> >> > issues
>> >> > were found. I am able to load the repair console from the original
>> >> > install
>> >> > CD which may help.
>> >> >
>> >> > Does anyone know how I can get passed the logon?
>> >> >
>> >> > TIA and regards,
>> >> > Sturdy
>> >>
>> >> You have already provided the answer in your post: Your
>> >> drive letters are mixed up, which means that Windows can
>> >> no longer locate userinit.exe.
>> >>
>> >> The cure is simple if the machine is networked, and not
>> >> so simple if it is not. What's yours?
>> >>
>> >>
>> >>
>>
>>
>>