Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
My husband brought a new Western Digital 120 GB SATA hard drive as a gift for my birthday. I have a 40 GB Western Digital ATA drive as the primary master and two CD-RWs as primary and secondary slaves. The new drive came without drivers and there was no problem with the installation neither setting it up because the system inmediately recognized it as SATA DISK_0. I formatted it using the System Manager that comes with Windows XP. No problem except that the letter Windows assigned to it was F: (the next available). I even tested it copying some files from the old ATA and everything worked fine.
Next, I used the COPY DRIVE function in Norton Ghost 9.0. The process completed without trouble, so I shutdown, disconnected the ATA and booted again. To my surprise, Windows came normally until the login screen, then started to ask my password repeatedly. I have never had a password to access my computer! The only thing it lets is reboot or shutdown so I reconnected the old drive and booted to find that Windows can see the SATA and all the files that Ghost copied.
What did I do that was wrong? Thanks in advance.

Thanks, Rich Mentzel, for using your time trying to help me.
Of course, when partitioning I made myself sure that the only partition the disk has was active. Besides, the system starts well, it even reaches the login screen. This could not be possible at all with a non-active partition.
Thanks again.

I've seen this happen when the "SAM" file got corrupted, all of a sudden Windows will start asking for a passward.
As long as you can access the data by booting with your first disk, you can restore the five main system files that Windows needs to run from within the restore files on the disk with the damaged file system. They're named "System, software, default, security and sam" and they're found in "snap" folders in the "System volume information" folder.
I'll post back in a minute and give you a link for step by step instructions on how to do this. It will make a lot more sense then if I tried to explain it :)
Musky
If the voices inside my head paid rent, I'd be rich!

OK, Here's the link. It explains how to do the restore from the recovery counsel, but since you can access the drive that is having problems booting, you can do this from within windows. So read the article, but you can go right to the part that tells you where these backup files are (in the system information folder) and then you can just copy and paste them into the Windows\system32\config folder of that drive.
Windows won't let you do it with the drive that is currently in use as the "system" disk, but you can do it with what is, at the moment a slave drive.
Here's the site, sorry I can't provide a link but I'm not on my computer right now:
http://support.microsoft.com/default.aspx?scid=kb;en-us;q307545
Good Luck!
Musky
If the voices inside my head paid rent, I'd be rich!

Thanks, Musky, I got it and will proceed immediately. I'll post back later to let you know what I found. Thanks again.

Oops I misread the login screen for Windows XP screen, happens when you read too fast.
I have had this happen occasionally where I switched out a hard drive.
If you can get past the login screen by clicking in the box and entering nothing for password, Tweak-ui(XP Power Toys) can remove that by setting it for auto logon and doing the same thing with putting in no password.

Rich, the furthermost place I can reach when booting is the login screen. No way that I can get past there because if I try to trick it entering nothing as password the system always displays "Incorrect username, domain or password...etc, etc..." and the only two options left to choose from are Shutdown or Reboot.
Thanks very much anyway.

Musky:
I tried to do what you said copying the files directly from c: to f:, but I got the message: "Access denied: file is in use...". So I made a boot diskette using the formatting option in Windows Manager, created a batch file to copy from c:\windows\system32\config to f:\windows\system32\config, and booted from the diskette. A new surprise because now the system can't see neither the c: nor the f: disks.
All I wanted was to avoid having to install each and every program again, but I'm starting to think that I don't feel like pursuing Windows ghosts, so I'll install a fresh copy of Windows on the SATA disk and will forget about cloning disks for a while.
Again, thanks very much for your kind cooperation.

You actually didn't want to copy from C to F, as I said, Windows won't let you access system files while the system disk "C" is in use. You needed to try and copy the backup files on F to the F:\windows\system32\config folder.
Anyway, I hope you can work it out in whatever way works for you.
Musky
If the voices inside my head paid rent, I'd be rich!

I guess I am still back to wondering why Ghost didn't work I do it all the time, but I never use the copy drive, I restore an image file to a new drive and be careful to make sure you ask Ghost to make the drive active which you know, and restore the mbr and it works every time.
I wonder if there isn't a problem with "copy drive" because I was a beta tester for Ghost 10.0 which is not quite out yet, and Copy drive was deactivated. We were supposed to get it in the final version, but that never happened.

if you are having trouble with ghost another option you can try is to run the File and Settings Transfer wizard from your old hard drive (after a clean copy of xp installed on sata drive) store the file on the sata drive switch drives and run the file and settings transfer wizard again

I'm having the exact same problem. I ghosted my old 80G IDE drive using ghost 9.0 to a new 160G SATA drive and when I tried to boot it it went to the password screen and when I logged in the computer logged me back off immediately and took me back to the login screen.
Would really appreciate an answer to the problem also.
Wallace

Just wanted to let anyone reading this know...I had a similar problem with the restored Ghost image freezing in the middle of windows startup. I was able to correct the problem by booting up with the windows XP install disk and choosing the "Repair" option. After the repair, all of my programs and devices worked normally (although the "Repair" did remove many of the recent security patches, necessitating a quick trip to Windows Update to re-patch the OS). I hope this helps.

You need to refresh the master boot record.
See the Symantec article here:
http://service1.symantec.com/SUPPORT/powerquest.nsf/643c9edb8e8f93b788256ee00056a108/3417d7a0242f887f88257019005a30d9?OpenDocument&prod=Norton%20Ghost&ver=9.0&src=sg&pcode=ghost&svy=&csm=no

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |