Windows XP Users login error

D

Derek Mak

I tried to restore but when I type copy F:\RegistryBackup\*.*
F:\windows\system32\config, it give the error message " The system cannot
find the path specified"

If I type "Copy F:\RegistryBackup F:\windows\system32\config then it will
appeal
" Overwrite f:\RegistryBackup?" If I enter then "1 file(s) copied"

Not sure whether I do a proper backup of the RegistryBackup bec I follow
your instruction "Copy F:\windows\system32\config\*.* to F:\RegistryBackup"
When I do the backup.

Anything can resolve?
 
P

Pegasus \(MVP\)

Derek Mak said:
I tried to restore but when I type copy F:\RegistryBackup\*.*
F:\windows\system32\config, it give the error message " The system cannot
find the path specified"

If I type "Copy F:\RegistryBackup F:\windows\system32\config then it will
appeal
" Overwrite f:\RegistryBackup?" If I enter then "1 file(s) copied"

Not sure whether I do a proper backup of the RegistryBackup bec I follow
your instruction "Copy F:\windows\system32\config\*.* to
F:\RegistryBackup"
When I do the backup.

Anything can resolve?

My previous instructions, before you changed the registry, ran like this:
1. Connect the 80 GB disk as a slave disk.
2. Boot the machine with your 500 GB disk.
3. Copy F:\windows\system32\config\*.* to F:\RegistryBackup.
4. Check that the registry files copied in Step2 are really backed up.

From your report I gain the impression that in Step 3 you did not copy the
"Config" folder to the "RegistryBackup" folder and that you skipped Step 4
that required you to check the existence of the backed up registry files. In
other words, "F:\RegistryBackup" is now one single file instead of a folder
containing half a dozen registry files.

If this is correct then my fail-safe plan to have a full backup of all
registry files failed. You must now manually undo the registry change that
you previously performed. It requires the same technique as explained in the
previously quoted link at http://windowsxp.mvps.org/peboot.htm. To protect
yourself against further damage you MUST begin by backing up the existing
registry files and you MUST check that the backed up files exist. Skipping
either of these steps is likely to cause you further problems.

Alternatively, if you feel that you're getting into deep water then you
might decide that it's time to cut your losses and drop the installation on
your 80 GByte disk altogether.
 
D

Derek Mak

I managed to restore back the 80GB RegistryBackup, this command will not
backup all the files (Copy F:\windows\system32\config\*.* to
F:\RegistryBackupwe) unless you have to create a directory first called
RegistryBackup then the command will work and can be backup all the files.

I am going to try the following steps again. The only thing I am not sure is
step 10 - "disconnect the 500GB disk". Currently what I do is I will shutdown
the PCs, open up the box and plug out the cable (SATA Disk) then I boot up
the pcs with only the 80MB Disk.

Is this the correct way to disconnect the disk, any "command" or software
that I can use without opening the PCs and plug out the cable.
 
P

Pegasus \(MVP\)

See below.

Derek Mak said:
I managed to restore back the 80GB RegistryBackup, this command will not
backup all the files (Copy F:\windows\system32\config\*.* to
F:\RegistryBackupwe) unless you have to create a directory first called
RegistryBackup then the command will work and can be backup all the files.
*** The phrase "Copy F:\windows\system32\config\*.* to F:\RegistryBackupwe"
*** was never meant to be a command - the word "to" would throw up
*** an error straight away. If you want a command then here it is:
*** xcopy F:\windows\system32\config\*.* F:\RegistryBackupwe\
*** Your method of first creating the target folder is just as effective.
I am going to try the following steps again. The only thing I am not sure
is
step 10 - "disconnect the 500GB disk". Currently what I do is I will
shutdown
the PCs, open up the box and plug out the cable (SATA Disk) then I boot up
the pcs with only the 80MB Disk.

Is this the correct way to disconnect the disk, any "command" or software
that I can use without opening the PCs and plug out the cable.
*** This depends on your BIOS. Some have a facility to activate
*** or deactivate a SATA disk.

*** An overall comment: Since my method failed to deliver, it is
*** likely that a repeat run will fail in the same way. On the other
*** hand you will be able to experiment without risking much because
*** you should now have a fairly simple recovery mechnism.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top