what files will i need to repair my windows xp install says files where lost that it needed to run properly

What do you exactly mean? It gives you this error when you are working within windows or when you are trying to install windows of the CD?

both it will just pop up at any given time. i already have windows installed

Boot from with your XP CD in the CDrom and press if prompted, select Boot from CD. Make sure your bios is set to boot from CDrom first.

HERE (http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/proddocs/recovery_run_console.asp) is the M$ site to setting it up.

A list of Recovery Console commands is available HERE (http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/proddocs/recovery_console_cmds.asp).

Why waste time in the recovery console? The system is booting, he's getting into windows, and the error is intermittent. He doesn't need to use the recovery console... (And you didn't even tell him what he would need to do with it).

System File protection is probable running and trying to automatically recover some missing\damaged files but it can't find the "safe" versions of those files from the original \i386 installation directory.

Bill, insert the original install CD. Open a command-prompt and enter the command "SFC /scannow" (without quotes).

Originally posted by QWERTY
........ He doesn't need to use the recovery console...
(And you didn't even tell him what he would need to do with it).

I'm just about to tell you what to with it though!
You obviously didn't click on the links I supplied or else you would've seen that it contained step by step instructions as well as an overview and commands.

ANYONE could follow these instructions.
Well, almost anyone. You still need to click on the link, so I guess it's not much help to you after all.
You need to leave the keyboard ocassionally and use the mouse. :laugh:

Your solution works in recovery console, so your argument is self defeating.
The whole idea of forums is that people post their solutions, and Windows almost always has more than one workaround or method for the same problem.

What are we supposed to do, wait and hope you log in, or email you with our suggestions to problems posted and get the QHQL assurance?

Insomiac, all you did was throw someone a list of commands but didn't tell him what he actually needs to do with them. It was useless unless he already knew what to do. (If he knew what to do, he wouldn't have to ask in the first place) Like most of your posts, your answer only gives the illusion of being usefull but in reality it provided no real help. (Either that or you try some very lame attempt at humour)

Yes, the recovery console could have fixed his problem but if he doesn't know what specific command(s) he actually needs to type into the console he could have done more damage or just sat there staring at the cursor. The SFC /scannow command will repair a majority of all missing Windows file errors automatically and is the first thing to try in this case...

You've openedly admitted numerous times that you don't even run Windows XP. Just the blind leading the blind...

Originally posted by QWERTY
Yes, the recovery console could have fixed his problem but if he doesn't know what specific command(s) he actually needs to type into the console ...........

That's why I placed the link titled "A list of Recovery Console commands is available HERE", straight under the other one.

The recovery console is a much more useful feature to learn, and although you have never bothered to read those links and commands, it tells you exactly what you need to do.


Why waste time in the recovery console?

Simple. It would have fixed his problem as you admitted, and secondly,
it's a handy utility to learn.
You could've offered another solution as well, rather than stating one is useless and yours is the only way.

Like most of your posts, your answer only gives the illusion of being usefull but in reality it provided no real help.

Like this one you placed on the same DAY (http://www.cdrom-guide.com/forums/showthread.php?s=&threadid=256044).

Originally posted by Insomniac
That's why I placed the link titled "A list of Recovery Console commands is available HERE", straight under the other one.

The recovery console is a much more useful feature to learn, and although you have never bothered to read those links and commands, it tells you exactly what you need to do...


I did read the links, did you? Theres a list of console command and their discriptions. There's no step by step, no guide on exactly what he would need to do. Do you assume everyone can figure how to stop there missing Windows file error from there?
It analogous to a doctor handing his patient the scapel and assuming he can perform the surgery himself.



Why waste time in the recovery console?

Simple. It would have fixed his problem as you admitted, and secondly,
it's a handy utility to learn.
You could've offered another solution as well, rather than stating one is useless and yours is the only way.

Like most of your posts, your answer only gives the illusion of being usefull but in reality it provided no real help.

He didn't want an education, he wanted a solution which you really didn't give to him. Nor would it have been simple for him. Since you still run Windows 98, how would you know how handy the recovery console really is? It's often the last resort on a non-booting system, not the first option on a otherwise functional XP system. Remember that the next time you recommend the recovery console.


Like this one you placed on the same DAY (http://www.cdrom-guide.com/forums/showthread.php?s=&threadid=256044).

Now your just getting pathetic...

There's absolutely NO reason for this to get to this point! The founder of the thread, BILL YATES, hasn't even given enough information yet to argue about it! Please wait for him/her to reply before going off on a rant. Thank you. ;)