Windows XP will now begin installing. No user intervention is necessary. It will complete approximately in 20 to 30 Minutes. During installation, the Regional and Language Options window will appear. There is no changes are necessary. Just Click Next. After completing all installation windows will reboot automatically and the Windows XP Home screen will appear.
How to repair Windows XP by commands? Go To Solution. Regards, Nicke. About Nicke Baker. Questions 0. Answers Best Answers Vote Up 0 Vote Down.
Hi Master Blaster, I have seen a site that provides the step by step procedure on how to repair windows XP using command. About Goram Ian. Questions 1. Best Answer. The first thing is that why windows XP repairing occurs? Because system files are missing or corrupted. After crawling through the MSKB, Experts Exchange, MSDN and sundry websites all extolling the virtues of a solution to these problems, I only found one that worked, and it has been reliably serving me for the better part of two weeks on seventeen PCs to date.
The process is simple: Get to the Windows Recovery Console for your particular Windows installation, navigate to the root letter of your installation C: in most cases , issue eight commands, and reboot.
Amongst the files it fixes are:. Let us now begin with a step-by-step instruction for correcting these issues. INI file. Briefly, BOOT. To do this, we will issue three commands in this step:. INI file and corrects a litany of common Windows errors. This step verifies the integrity of the hard drive containing the Windows XP installation. No screenshot necessary here! Let it proceed; it could take in excess of 30 minutes on slower computers, when this is finished move on to the seventh and final step.
This last step also requires no screenshot. This writes a new boot sector to the hard drive and cleans up all the loose ends we created by rebuilding the BOOT.
INI file and the system files. Keep in mind that this solution is only designed to resolve the issues introduced in the preface if the cause is unrelated to spyware and viruses; while I have had significant luck with rebuilding heavily-infected systems in the method I have described, it is not guaranteed.
Icrontic — Home of the Big Beef Burrito since , fool. Sign In Become an Icrontian. Howdy, Stranger! Sign In Register. Configuring your computer to boot from CD is outside of the scope of this document, but if you are having trouble, consult Google for assistance. Am going to try the instructions outlined here but I have a q Don't want to do anything yet since I'm scared it will further exacerbate the prob.
Make sure any hard disk drives are powered on and properly connected to your computer, and that any disk-related hardware configuration is correct. This may involve running a manufacturer-supplied diagnostic or setup program. Setup cannot continue. To quit setup, press F3. Great help, thanks. After that i type "1".
Now instead of going to the command prompt , i get the Blue screen of death.. C: is nearly always the HDD. Your HDD might be toast and not detectable, but perhaps someone else could chime in if I am incorrect. Ensure that all the plugs are in the right spot and try the steps again. If you get the same result or hear any clicking, then the HDD is toast.
Vipin: Glad to hear it worked for you therain: That sounds like it is trying to mount parts of your registry that are then making the command prompt bomb out.
Not sure what to do there without using a boot disc that can do offline registry fixing and I'm not going to be able to discuss that because we only support and recommend legal actions here.
Still have the BSOD. Thanks a lot for the procedure To fix this I had to edit my boot. Just wanted to let people know that they might need to do some additional work not mentioned in this article. Elhassan It works just like a charm. Your article saves my day. Thank you a lot. Will report back with the results! How can I recover that functionality? That command returns "The parameter is not valid.
Shame On You! I hope you haven't led too many people into screwing their computers into oblivion, like most of the other Geek Squad wanabees have, already. This is true in Windows Some Command Line Interpreters might need "aattrib -r -s -h" without the quotes instead of "attrib -rsh" without the quotes to clear all the flags.
Summarily blowing away the boot. The people adding multi boot sequences should be tech-savvy enough to figure out the problem on there own or at least be able to google until they find an answer As far as a "multiboot environment" that's going to be pretty rare considering any PC, no matter what it is will always run better with a single OS rather then 2 or more Ehhh I dont know how valid this is. Maybe partially true, as in the "inner" OSs, those farther in on the disk, will be "slower" but that is only marginally so and if you are using a SSD, I would think that there would be zero performance degradation.
If you're using XP Pro and you have forgotten your admin password, you could reset it. I don't see the point in running multi OS's on one system unless it's a server. To do this, run the following command instead:. The scan results will be shown after this process is finished. This means that you do not have any missing or corrupted system files. Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS. To view the detail information about the system file scan and restoration, go to How to view details of the System File Checker process.
Windows Resource Protection found corrupt files but was unable to fix some of them. To repair the corrupted files manually, view details of the System File Checker process to find the corrupted file, and then manually replace the corrupted file with a known good copy of the file.
Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
To do this, click Start , type Command Prompt or cmd in the Search box, right-click Command Prompt , and then click Run as administrator. To view the details that included in the CBS. Log file, you can copy the information to the Sfcdetails. To do this, follow these steps:. Note The Sfcdetails. The file includes information about files that were not repaired by the System File Checker tool.
Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool. How to manually replace a corrupted system file with a known good copy of the file.
0コメント