Discussion Locked

corrupt C:\windows\system32\config\

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

i have an error loading winxp
corrupt file in C:\windows\system32\config\
file names are default & system
i have had to install windows in a dual boot atmos because of a quick repair situation, so my boot options are 1 = windows, 2= windows2
these are my directories on the c drive
i cannot access the windows2 directory in dos
i need someone with experience in repairing the file system in msdos mode

5 replies

by orpheum

sorry it took so long to rate. I actually had to replace the hd. after dwlding the hitatchi diagnostic from ibm's site, i was informed that my disk had a crap-load of damaged sectors which were allowing me to write(when reinstalling winxp) but not read (hence the error in locating these specifically located bootfiles. recovery console was no use either. i refused to return the damaged one to ibm tho. they can bite me.
In conclusion, I had serious hardware damage ( most probably from the over 200 time i've installed o/s's on this sucker since late '99, not to mention some rather heavy virus/malware code attacks (pretty much all of the American non-email strains)

by wcp

Boot to Recovery Console and run ?CHKDSK C: /R? without the quotes. C is the drive of Windows 1 and you need to replace the letter if necessary. I have used this with great successes.

If this does not work, try Answer 1.

by orpheum

sorry it took so long to rate. I actually had to replace the hd. after dwlding the hitatchi diagnostic from ibm's site, i was informed that my disk had a crap-load of damaged sectors which were allowing me to write(when reinstalling winxp) but not read (hence the error in locating these specifically located bootfiles. recovery console was no use either. i refused to return the damaged one to ibm tho. they can bite me.
In conclusion, I had serious hardware damage ( most probably from the over 200 time i've installed o/s's on this sucker since late '99, not to mention some rather heavy virus/malware code attacks (pretty much all of the American non-email strains)

This discussion is closed to new replies.