I have a question about Do I still need CONFIG.SYS and AUTOEXEC.BAT?:

I have XP and it just crashed. When restarted I get a message that says \WINDOWS\SYSTEM32\CONFIG SYSTEM is missing or corrupt. The computer then stops responding. How can XP not use CONFIG SYSTEM if I'm getting this message and how do i fix it.

[Reply or follow-up to this message]

no, they are not necessary for a standard winxp installation.


On Wednesday, September 25, 2002 at 10:54 am, Tom wrote:
>I have a question about Do
>I still need CONFIG.SYS and AUTOEXEC.BAT?:

>
>I have XP and it just crashed. When restarted I get a message that says \WINDOWS\SYSTEM32\CONFIG
>SYSTEM is missing or corrupt. The computer then stops responding.
>
>How can XP not use CONFIG SYSTEM if I'm getting this message and how do i fix it.

[Reply or follow-up to this message]

Should go without saying that a file called "system" (no extension) in a directory 
called Config is not the same as a file called config.sys.  (Config.sys, BTW, is 
replaced by config.nt in XP.)

In any case, you probably have to do a repair/re-installation from the XP CD to repair 
this file and run windows again. 






On Wednesday, September 25, 2002 at 10:54 am, Tom wrote:
>I have a question about Do 
>I still need CONFIG.SYS and AUTOEXEC.BAT?:

>
>I have XP and it just crashed.  When restarted I get a message that says \WINDOWS\SYSTEM32\CONFIG 
>SYSTEM  is missing or corrupt.  The computer then stops responding.
>
>How can XP not use CONFIG SYSTEM if I'm getting this message and how do i fix it.

[Reply or follow-up to this message]

Just booted to Safe Mode with Command Prompt to see if I could look at this file. 
 It's about the third or fourth file windows loads (ntoskrnl.exe being first).  Can't 
copy or view it.

There may be a way to fix this using Recovery Console.  But whatever you do, you 
will have to do it from the XP CD.






On Thursday, September 26, 2002 at 12:30 am, j frangquist wrote:
>Should go without saying that a file called "system" (no extension) in a directory 
>called Config is not the same as a file called config.sys.  (Config.sys, BTW, is 
>replaced by config.nt in XP.)
>
>In any case, you probably have to do a repair/re-installation from the XP CD to 
repair 
>this file and run windows again. 
>
>



[Reply or follow-up to this message]

I have this problem as well. I refferred to this article: Microsoft Knowledge Base Article - 307545 at : http://support.microsoft.com/default.aspx?scid=kb;en-us;307545 That took care of the problem for me...at least until the next reboot. I've read a lot about this issue and it appears that for many people the afore metnioned solution is a permanant fix, but for many others, the error occurs over and over. Unfortunately, I'm in the latter group, which apparently means there is some sort of hardware issue (RAM, Motherboard, ?). Hopefully this will not be a recurring issue for you. The first time I experienced this error, I reformatted all hardrives and reinstalled xp and all software and proceeded to update. Afew days after, I experienced the same issue and did it all over again. Most recently, I used the above article to fix the problem, but I got the same error messege within the same day. From what I've read, this means that I have a hardware issue and/or possibly a problem with the settings in the bios. However, until recently the computer had worked fine and no changes have been made to the bios that I'm aware of. If anyone has any ideas what to try next, please respond. Tim


On Thursday, September 26, 2002 at 12:30 am, jagged ben wrote:
>
>Should go without saying that a file called "system" (no extension) in a directory
>called Config is not the same as a file called config.sys. (Config.sys, BTW, is
>replaced by config.nt in XP.)
>
>In any case, you probably have to do a repair/re-installation from the XP CD to repair
>this file and run windows again.
>
>

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum