Boot-Not Complete

Probable you saw a message regarding LSASS. It's a core file for security and there are causes for failing during startup (corrupted DLLs, incorrect permissions, failed system patches, etc.).

Can you boot in Safe Mode? If so, try System Restore.

If you can't go there, do you have the windows XP CD ? What was the installed Service Pack number ?

Good Luck,

Cetin


Trying to unweave, unwind, unravel
And piece together the past and the future,

T. S. Eliot

Thanks Cetin, yes I have the CD but do not want to try a repair because the last time I tried that the set up said it couldn't load 'Driver cab.' probably because the Nvidia chipset drivers were stopping it.
Safe mode returns the same dialog box.
I have a parallel disk with XP which I am using, do you think I could export the LSASS file, or indeed the HK Current User? I am reticent about sending lumps of the registry accross in case there is a conflict and I lose the data.

Oh, I forgot to add I have Sp2. on XP Pro on two hard disks.

Paul, with the parallel instalation you can repair all the registry hives by using a restore point from the damaged windows installation.

Read the following MSKB article:

Q307545 ??How to recover from a corrupted registry that prevents Windows XP from starting?

In your case, it?s easier because you can do it when you boot from the good XP and make the changes to bad XP from windows explorer.

Take the article as a skeleton because you don?t need to boot to recovery console. In essence, the new procedure should be:

1. Begin with ?Part Two? and check out the C:\System Volume Information\_restore{D86480E3-73EF-47BC-A0EB-A81BE6EE3ED8}\RPxx\Snapshot (on damaged XP).

Note

xx are numbers. You can see the files dates in order to have a clue regarding the newest restore points.

After you?ll find a convenient restore point, complete part Two.

2. From the ?Part One?, just delete the files: system, software,config,sam,security,default (not from a command prompt, but from windows Explorer). The files are under the

c:\windows\system32\config

path of the damaged XP.

3. Part three?s equivalent it?s to copy the files from the tmp folder to

c:\windows\system32\config folder.

Let?s recap:

You find a convenient restore point from the damaged XP and prepare the registry hives to a tmp folder. Delete the registry hives from the bad XP and copy the prepared hives (extracted from the restore points of the damaged XP) to the corresponding path.

Restart PC and let it boot from the damaged XP instance and if you?re lucky, it can boot. Regarding the data files from the damaged hard drive, the above procedure should left them intact because you replaced only the registry hives. However, for your piece of mind, you can copy the data files to the second HDD first.


Good Luck,

Cetin


Trying to unweave, unwind, unravel
And piece together the past and the future,

T. S. Eliot

Thank you very much Cetin. I tried to replace the lsass.exe files from the good disk, while you were posting, but to no avail. I really apppreciate your time and effort in helping me with this. I want to try it very slowly and carefully tomorrow (it's 21.24 where I am) and will let you know how I get on. My determination is paramount! And I don't want to fail through fatigue.

? take it in baby steps. Once again, the previous procedure needs some restore points from the damaged XP. If you don't have them, the procedure won't work because it doesn't have the "stuff".

Yes, I see that you're in TFT + 8 Time Zone.

TFT (This Forum Time) it's PDT (Pacific Daylight Time). It does make sense for US guys, while for the rest of us the standard time it's GMT.

Good Luck,

Cetin


Trying to unweave, unwind, unravel
And piece together the past and the future,

T. S. Eliot

Thanks, Cetin, the trouble is I'm up to RP 107! Funnily enough, not all have 'snapshot' as a file/folder (I wonder why? Who decides on when snapshot is necessary?), I think I'd better sift through to find one recent enough with 'snapshot'. Chugging on . . .

The idea Paul is to pick one snapshot that has the 5 files:

_REGISTRY_USER_.DEFAULT
_REGISTRY_MACHINE_SECURITY
_REGISTRY_MACHINE_SOFTWARE
_REGISTRY_MACHINE_SYSTEM
_REGISTRY_MACHINE_SAM

As to why some snapshots don't have them, either Bill won't know. But he could ask his staff and don't expect to disclose this in public


Good Luck,

Cetin


Trying to unweave, unwind, unravel
And piece together the past and the future,