Re: Windows logon failure

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

OK, you asked for it:
1. Temporarily install the problem disk as a slave disk in
some other WinXP PC.
2. Find out the current drive letter for the bad disk's drive C:.
It could be D, E, F or whatever - I'll call it X:.
3. Run this command from a Command Prompt: mountvol.
4. Make a note of the volume label for drive X:. It looks like
so: Volume{58273200-dc6a-11d8-9d3a-806d6172696f. I'll call it Y.
5. Run regedit.exe.
6. Collapse the display so that you see only the five hives.
7. Single-click HKLM.
8. Click File / Load Hive
9. Type X:\windows\system32\config\system.
10. Type BadDisk when prompted.
11. Open HKLM, open BadDisk, then navigate to the highest
ControlSet number you have (usually 002 or 003).
12. Navigate to MountedDevices.
13. Locate the value Y in the right pane.
14. Make a note of the value data. It could be something like
25 e3 26 3e 00 7e. I'll call it Z.
15. Navigate down to DosDevices and locate Z. This is your
system drive assignment.
16. Rename its value to DosDevices\C: If drive letter C: is
used by some other value, rename that one first to make room.
17. Close the registry editor.
18. To add braces to your belt, copy X:\windows\system32\userinit.exe
to \windows\system32 on ***every*** other drive on the problem disk.
Make new folders if necessary.
19. Return the disk to its normal home.

If Steps 1..17 do not help then Step 18 probably will. And if you
survive the ordeal, post your result.


"ribs" <ribs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5864BD27-68C3-4632-BFAF-F9926825A978@xxxxxxxxxxxxxxxx
That doesn't seem to have helped. Can you tell me the tedious solution?

"Pegasus (MVP)" wrote:

Having two non-networked PCs makes it rather tedious
as it involves moving disks from one machine to the other.
Before going there I suggest you try this:
1. Boot the machine with a Win98 boot disk from
www.bootdisk.com.
2. Run this command: fdisk /mbr

This will reset the disk volume names, thus forcing
Windows to reassign the drive letters on the next
reboot. Sometimes it works, somtimes it does not.


"ribs" <ribs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7406363E-586E-4B52-BE65-E16FA5245EC4@xxxxxxxxxxxxxxxx
Err I just realized that could be interpreted 2 different ways; I
meant
case
b, I have other Windows XP PCs

"ribs" wrote:

Ah sorry I must have missed that one. I see it now. What was the
second
solution you mentioned, for pcs not networked?

"Pegasus (MVP)" wrote:


"ribs" <ribs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A7DA48F0-54B3-4F5A-B1C4-05AD0D670809@xxxxxxxxxxxxxxxx
I recently changed my default user input language from english
to
japanese
(using files already on my computer, not using my install disc)
and
of
course
was then asked to restart my computer. I did but when I got to
the
log on
screen, I found that I could not log on. That is to say, I
could
log on,
it
shows the "Loading your preferences..." message for about a half
second
and
then it returns me to the log on screen. It also turns off my
num
lock
for
some reason.

Here's some random weirdities about my system that may be
contributing to
the problem, although the ui language change is when the problem
started:

I have two HDDs but C: is my slave and F: is the master.
I reformatted both around 3-4 weeks ago.
That's all O can think about for now


Have a look at the thread "Login problem", posted in this
newsgroup about 47 hours ago.








.

Relevant Pages

  • Re: Can I boot of an XP System disk, nested in a logical volume
    ... I'll boot of Partition Magic or some other kind of magic and fix it that-a-way. ... It's been a long time since I messed with partitions like this, but in the back of my head I have this fragment about boring registry hands-on editing, 'derived Disk ID's' and the 'Master Boot Sector' -- that's S as in 'Senile'. ... One reason for the drive letter change on cloned drives is to keep the parent drive hooked up the first time the clone is booted, being that the clone has the same Mount Manager database, and being that the Mount Manager *always* respects drive letter assignments, it will see the parent drive and its valid disk signature and assign the C: drive letter to the original C: drive, so there will be no C: letter available for the clone. ...
    (microsoft.public.windowsxp.basics)
  • Re: HD not being read
    ... click Disk Management. ... Right-click the disk you want to initialize, ... Change Drive Letter and Paths. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Cloning windows 2000
    ... >> it has booted at least once and rebuilt its drive letter table. ... contents to this first partition. ... If you boot old-2K with the new drive in place and fresh partitions visible, ... old disk has that, so it might end up being 'H' or something else. ...
    (microsoft.public.win2000.general)
  • Re: Windows logon failure
    ... "Pegasus (MVP)" wrote: ... Temporarily install the problem disk as a slave disk in ... Find out the current drive letter for the bad disk's drive C:. ...
    (microsoft.public.windowsxp.general)
  • Re: Windows logon failure
    ... installed on it out of my computer and installing it on some other pc. ... Temporarily install the problem disk as a slave disk in ... Find out the current drive letter for the bad disk's drive C:. ... Navigate to MountedDevices. ...
    (microsoft.public.windowsxp.general)