-
September 12th, 2008, 12:08 PM
#1
Repairing Windows XP in Eight Commands
Repairing Windows XP in Eight Commands
http://icrontic.com/articles/repair_windows_xp
Amongst the files it fixes are:
Windows Hardware Abstraction Layer (HAL)
Corrupt registry hives (\\WINDOWS\\SYSTEM32\\CONFIG\\xxxxxx)
Invalid BOOT.INI files
A corrupt NTOSKRNL.EXE
A missing NT Loader (NTLDR)
I found that article quite enlightning.
-
September 12th, 2008, 02:06 PM
#2
Originally Posted by Train
Repairing Windows XP in Eight Commands
http://icrontic.com/articles/repair_windows_xp
Amongst the files it fixes are:
Windows Hardware Abstraction Layer (HAL)
Corrupt registry hives (\\WINDOWS\\SYSTEM32\\CONFIG\\xxxxxx)
Invalid BOOT.INI files
A corrupt NTOSKRNL.EXE
A missing NT Loader (NTLDR)
I found that article quite enlightning.
I have to say that I found it utterly terrifying.
-
September 12th, 2008, 09:31 PM
#3
Interesting. I'll have to try it on some "victim".
-
September 13th, 2008, 12:34 AM
#4
Originally Posted by Broni
Interesting. I'll have to try it on some "victim".
Dos / Dos like commands are not that hard to deal with.
-
September 13th, 2008, 12:38 AM
#5
Sure thing. I just wanna see, how effective this procedure is, because those listed errors are usually a huge headache.
-
September 13th, 2008, 12:43 AM
#6
Headache is right!
But if it works, it would sure beat a clean install all to pieces.
-
September 13th, 2008, 06:45 AM
#7
http://icrontic.com/articles/repair_windows_xp/page2
- cd ..
- attrib -h c:\boot.ini
- attrib -s c:\boot.ini
- attrib -r c:\boot.ini
- del boot.ini
- bootcfg /rebuild
- chkdsk /r /f
- fixboot
You should be able to do the exact same thing with 5 commands:- cd /d c:\
- del /a:rsh boot.ini
- bootcfg /rebuild
- chkdsk /f
- fixboot
Comments:- cd /d c:\ = Moves you from ANY drive:\directory to the root of drive C:
- del /a:rsh boot.ini = Forces deletion of the boot.ini file, (in spite of its Read-only, System and Hidden attributes).
- bootcfg /rebuild = (same command)
- chkdsk /r = The "/r" parameter also implies "/f"
- fixboot = (same command)
-
September 13th, 2008, 10:55 AM
#8
-
September 13th, 2008, 02:29 PM
#9
No problem.
-
September 14th, 2008, 05:32 AM
#10
very useful article for future problems
bookmarked.
thanks!
ASUS P5Q-E (1306 BIOS)
Intel Core 2 Extreme QX9650 @ 3400 MHz (8 x 425)
G Skill F2-8500CL5 4 GB DDR2-1066 (5-5-5-15 @ 400 MHz)
GeForce 7950 GX2 (1024 MB)
Hardisks Total Size 1863.0 GB
Monitor LG L1970HR
Microsoft Windows XP Professional x64 Edition
-
September 15th, 2008, 08:56 AM
#11
When I first saw this thread, I was intrigued as to how recreating the boot.ini file and the boot record, was going to correct a missing or corrupt registry hive or corrupt NTOSKRNL or missing NTLDR, but thought that I'd wait for the error to happen, so this procedure could be suggested.
Then, I had a power "blip", the PC shut down and on rebooting it got the error about a missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM.
So, dragged out my Recovery Console CD, booted to it, ran through the commands and as I suspected, the procedure doesn't have a hope of correcting a missing registry hive. In my case, the entire \Config folder was corrupt, and chkdsk turned it into a "FOUND.000" file!
(And, btw, the cd /d c:\ and chkdsk /f commands are not valid from the recovery console.)
But, the good news is that I found a recovery procedure that is easier than the MS one noted above.
I used BartPE to boot with, recreated the \Config folder, found my System Recovery Folders and copied the backed up hives into \Config, renamed them appropriately and successfully rebooted.
Last edited by WhitPhil; September 15th, 2008 at 09:00 AM.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|