Discussion Locked

"File creation error" at Win 95 startup

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Running Win 95 4.00.950a on a 166 Mhz Pentium, I get a message "File creation error" at startup, and end at the C:> prompt of Win 95 DOS. If I enter 'autoexec' my autoexec.bat file is processed, and Win 95 starts OK. I thought I saw a fix or memo on the M-S site, but a search for 'file creation error' turns up no relevant information. Can anyone give a reference to further information, or direct help?

13 replies

by mkelley

Possibly Windows is having difficulty with the swap file. Set the swap file to zero, do a scandisk and defrag, and then set the swap file back to automatic and reboot. You can also try to rem out any entries in your autoexec.bat and win.ini files for starting any but the most necessary devices and programs. Then unrem each one until you see the error again. Good Luck !!

by guildt

just a thought but I've had trouble with the path before. I know that you are not suppose to need one with 95 however at startup I have seen it need c:\windows and c:\windows\command. My trouble was with it not being able to find win.com and it would spit you out to DOS.

by antsoair

Are you using a Config.sys file? If Windows starts up after typing in autoexec.bat then something could be failing before it is processed. Have you stepped through the startup process using F8?

by gary

check Q178151, looks like maybe the incorrect version of win.com. Get correct bootdisk for your version, OSR1/OSR2/OSR2.1/OSR2.5 and boot off this, sys your drive and hold thumbs :-)

by javierrosado

I have seen this problem very often when the McAfee Anti-Virus is installed. When windows 95 is starting -up one of the first things it does in the autoexec.bat is calling the viruscan app to scan the most critical files along with the boot sectors, etc... It is this application the one causing trouble, since when removed the problem goes away.

This discussion is closed to new replies.