Hello
ok, I think I'm stuck! Bought a new IDE disk drive to update my Dads PC (Dell P4). Thought I would just hook it up and use Ghost to clone from old disk to new. However I have a problem. The old drive won't boot into Windows. The errors are corrupt Boot.ini, then missing or corrupt Hal.dll, and also lsass.exe password problem. The lsass problem won't let me log into the drive in XP Recovery Console (my dad didn't have any passwords on his PC so why lsass.exe is an issue don't know). The drive is happy as a slave and I can see all the files, but can;t clone as I would be copying all the corrupt XP boot files as well. Checked jumper settings, they fine, also have run chkdsk /r from command prompt in windows, no problems there but I don't know how to deal with the booting problems or admin password prob.
I 'd rather not pass my Dads PC back to him saying "Heres your PC - your new disk is in but you'll have to reinstall all your old programs..." Can anyone help? As I said the drive is happy hooked up as a Slave.
Thanks
Nick
Full Version: Disk Won't Boot - (happy as Slave though)
Hi Nick, welcome to SAF,
Changing a HD to another may mess with your registry keys... I had an issue when my old drive C died, and I installed the D drive as master. Had to change all registry keys, and it took me 8 hours...
Also, registry uses the hardware configuration to work, so, I suppose you'll need to reinstall Windows on top. This will preserve your data, but will read your (old) registry settings and transfer them to the new machine... and this is a bad thing to do.
Disk clones that refers to another machine hardware may not work.
I recommend you to:
1 - Reinstall all motherboard, chipset, video and monitor drivers;
2 - Reinstall Windows on top of itself, using the cloned HD as target drive.
Note that, if some registry keys on the image/clone are read by the new/on top install, you'll get some troubles to fix it.
This advice is at your own risk, as I never had this issue before, just trying the logical thing to do.
Chris
Changing a HD to another may mess with your registry keys... I had an issue when my old drive C died, and I installed the D drive as master. Had to change all registry keys, and it took me 8 hours...
Also, registry uses the hardware configuration to work, so, I suppose you'll need to reinstall Windows on top. This will preserve your data, but will read your (old) registry settings and transfer them to the new machine... and this is a bad thing to do.
Disk clones that refers to another machine hardware may not work.
I recommend you to:
1 - Reinstall all motherboard, chipset, video and monitor drivers;
2 - Reinstall Windows on top of itself, using the cloned HD as target drive.
Note that, if some registry keys on the image/clone are read by the new/on top install, you'll get some troubles to fix it.
This advice is at your own risk, as I never had this issue before, just trying the logical thing to do.
Chris
Hi there,
although I am not sure if this is going to work but it is just an idea.
I would make sure if all the files/folders arent hidden or copy all the files using command prompt and use the command xcopy.
e.g.
first of all open the command prompt and then go to the drive that you are going to copy the files from.
c:\>xcopy *.* /s d:\ and then press enter
where d:\ stands for the disk that you are copying the files into.
let us know if it works.
Ahmed
although I am not sure if this is going to work but it is just an idea.
I would make sure if all the files/folders arent hidden or copy all the files using command prompt and use the command xcopy.
e.g.
first of all open the command prompt and then go to the drive that you are going to copy the files from.
c:\>xcopy *.* /s d:\ and then press enter
where d:\ stands for the disk that you are copying the files into.
let us know if it works.
Ahmed
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.