Back in February my wife used a flash drive from work with my Dell Dimension 4100 which I had upgraded by adding 256 MB of RAM and by installing Windows XP. The flash drive crashed the computer which announced a missing or corrupt file C:\WINDOWS\system32\config\system.
I discovered MS Knowledge Base, specifically Article 307545, and was able I to restore the Dell to more or less the condition it was in previously.
Recently this Dell again crashed in a way that seemed to indicate the presence of malware; no flash drive was involved. I was running AVG Free and Spyblaster and was using Spybot and Adaware regularly to check for malware. As I started the computer intent on finding a specific file, I noticed that it seemed slow and that the AVG symbol was not lit up in the tray. Then it crashed and began to restart. I could not load XP either normally or in safe mode. In the course of several restart efforts I once got a blue screen very briefly indicating a corrupted registry file whose name I didn’t catch. On this basis I decided to run the batch files I used last February as set out in the KB Article 307545 How to recover from a corrupted registry that prevents Windows XP from starting.
Unfortunately I forgot that the first batch, regcopy1, contained commands that might cause problems as I had already run them on this computer. Here is regcopy1:
md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak
delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default
copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default
In any event, I started recovery console, ran regcopy1 and got these undesirable results. I paraphrase:
First line- File/folder already exists
2d through 6th line- System can’t find file specified
7th through 11th line- Error during directory enumeration
12th through 16th line- File could not be copied
I was able to check the contents of the system32, tmp and repairs folders which contained expected files and nothing new. I was unable to check the system32\config folder because of “error during directory enumeration”. I am now at a loss. I had hoped to get into safe mode, run some virus checks and Hijackthis, and then send the results to you folks. Do I have options left or should I turn my attention to reformatting the HD and a fresh XP installation?
wesbton
I discovered MS Knowledge Base, specifically Article 307545, and was able I to restore the Dell to more or less the condition it was in previously.
Recently this Dell again crashed in a way that seemed to indicate the presence of malware; no flash drive was involved. I was running AVG Free and Spyblaster and was using Spybot and Adaware regularly to check for malware. As I started the computer intent on finding a specific file, I noticed that it seemed slow and that the AVG symbol was not lit up in the tray. Then it crashed and began to restart. I could not load XP either normally or in safe mode. In the course of several restart efforts I once got a blue screen very briefly indicating a corrupted registry file whose name I didn’t catch. On this basis I decided to run the batch files I used last February as set out in the KB Article 307545 How to recover from a corrupted registry that prevents Windows XP from starting.
Unfortunately I forgot that the first batch, regcopy1, contained commands that might cause problems as I had already run them on this computer. Here is regcopy1:
md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak
delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default
copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default
In any event, I started recovery console, ran regcopy1 and got these undesirable results. I paraphrase:
First line- File/folder already exists
2d through 6th line- System can’t find file specified
7th through 11th line- Error during directory enumeration
12th through 16th line- File could not be copied
I was able to check the contents of the system32, tmp and repairs folders which contained expected files and nothing new. I was unable to check the system32\config folder because of “error during directory enumeration”. I am now at a loss. I had hoped to get into safe mode, run some virus checks and Hijackthis, and then send the results to you folks. Do I have options left or should I turn my attention to reformatting the HD and a fresh XP installation?
wesbton