Install XP on top of itself

[jackslap]

I am afraid installing xp over itself might be my only solution to a "missing KnownDll" error that I get upon boot up.

I do not have the recovery console as an option from my Nlite version of XP64 so I'm out of luck. I don't have my original "Un-Nlited" version anymore, so I guess I can't use the recovery console route.

I also found out that I can't use UBCDFW or BartPE because I have xp64 and they arent compatable.

I know that you can install windows over itself, but I'm afraid to try. I boot up off my CD and go through the process of letting it detect my SATA drives, it gets to the part about installing windows on the selected partition (C:, which is the existing windows install), I was scared to press "keep current file system in tact" for fear that it might mess up my data. But I pressed it anyway and the littel red meter comes up very similar to when you ARE formatting a partition, so I quickly switched the machine off thinking that I might kill my data if I let it continue.

I never got to a screen that said something like "version of windows already detected on partion" or "install as repair". Should I have let the meter finish it's job? Would I have eventually got to the appropriate screen, or was I about to screw up? I'm desperate...

[Guest]

You can still get to the recovery console on an nlited disk by pressing F10 when the F6 prompt appears.

I believe when you install over an install only the windows folder is deleted. Profile folders are renamed to Administrator.001 or something. I'm not 100% sure on this as I haven't done it but I once redid my sisters PC and it had 3 profile folders from re-installations.

Anyways, always keep your data on a separate partition.

[jackslap]

K, got the RC working by creating a new Nlite version. Didn't think I could but it worked. I have the RC up and running but I've read bad things about trying to use fixboot or fixmbr. Are they safe?

[Guest]

That's not going to fix your missing KnownDll error. For what it's worth, I have used those commands a few times with no ill effects but depending on your drive setup there's always a chance something could go wrong.

[jackslap]

Good to know that won't fix it so I won't mess with it. But not good to know. What gives? How can I fix this thing?

Can I boot up from a different disk with bootable XP32 (cause UBCDFW and BartPE don't work with XP64) and then use a certain application to fix the problems on the C: drive?

If so, what application checks for and will repair or replace a missing dll?

[Guest]

You said you made a new nlite version. Can you make one with unattended, prompt repair? That should give you the repair option when you are at the partition screen.

[jackslap]

Yeah, I got that working but you said it wouldn't fix my problem and so I didn't do it for fear I'd ruin my data.

Should I just do the "over" install. If so, is there a step by step so I don't screw up. I've fresh installed windows many times, but never an "over" install or repair install. I was just afraid that when that meter came up saying that windows was inspecting the partitions, that I might erase something.

[Guest]

A repair install will only copy over systems files and stuff. That's what you should try. After the repair you should reapply any hotfixes that are not integrated into the CD.