Re: Windows logon failure

Oops I accidentally hit that this answered my question. My bad. Anyway I'm
almost about to kill myself because according to my friend's PC, My disk's
file system is raw. I'm assuming I need to sell my soul to a data recovery
specialist now? or something like that? The Computer Management tool claims
that my 80 GB HD has 1 74.something GB partition and 1 500-something GB
partition unallocated. Please tell me there's something I can do? I need
the computer for just two more weeks before it can be as broke as it wants to
be. ;( I'm close to hysteria...

"Pegasus (MVP)" wrote:

Yes. And report to the trauma ward at your hospital when
finished.


"ribs" <ribs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ED473471-1228-4694-A4B5-932FABE8BD1C@xxxxxxxxxxxxxxxx
Ok, so just so I'm clear, I should be taking the drive that has windows
installed on it out of my computer and installing it on some other pc.
After
that I find out what letter its been assigned (x) and use that letter to
do
X:> mountvol in cmd? and then do the rest of the stuff?

"Pegasus (MVP)" wrote:

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: Windows logon failure
    ... "Pegasus (MVP)" wrote: ... disk problem all along and that some files or the registry ... a Repair installation over the top of the existing installation. ...
    (microsoft.public.windowsxp.general)
  • Re: Log in problems
    ... Pegasus (MVP) wrote: ... True, but getting into a stolen laptop is child's play anyway, even ... its disk, put it into a 2.5" USB disk case and connect that case to ...
    (microsoft.public.win2000.general)
  • Re: Upgrade Internal Hard Drive
    ... Thank yoy Pegasus for respondin. ... "Pegasus (MVP)" wrote: ... disk and that Word and Outlook now fail to run. ... "This patch package could not be opened. ...
    (microsoft.public.windowsxp.general)
  • Re: Windows logon failure
    ... I put the disk back on my machine and it still booted ... "Pegasus (MVP)" wrote: ... implies that you have destroyed your Windows installation. ...
    (microsoft.public.windowsxp.general)
  • Re: change drive letter assigments for system partitions
    ... > Pegasus (MVP) wrote: ... >> If this does not work then you may have to seize ownership ... >> Did you manage to change your boot drive letter to C:? ... > Everything worked thank you Pegasus! ...
    (microsoft.public.windowsxp.general)
Loading