I have installed Win3.11 over win 3.1 onto an old 486. I went through setup just fine, etc. Now when I reboot my computer, it goes thru the config.sys (no problem) then the autoexec.bat.....PROBLEM! There are error messages that occur in this order, all suggesting to go thru windows setup again, and that a device file in my system.ini file may be corrupted. Here they are... C:\SFT\WINDOWS\SYSTEM\vshare.386 ....ifsmgr.386 vwc ....vnetsup.386 ....vredir.386 ....ne2000.386 ....nwlink.386 ....nwnblink.386 ....netbeui.386 I figured out a way to bypass these (CTRL + C) and at the prompt, I started windows with win/s command. Then I got these messages: "Could not find: NETAPI.DLL" "Could not find: PMSPL.DLL" Please give me any feedback that you can. Thank you very much. wmd

Dont really understand the problem however if you hit F8 near the end of the diagnostics the prog prompts you to confirm each command by deduction you should be able to work out what is wrong,by the way a working autoexec.bat can be just 4 or 5 lines long

Dave the snake is wrong! He's probably thinking of Win9x versions. The F8 feature didn't exist in Windows 3.1. Maybe it did appear in DOS6.22, but if so it certainly didn't involve Windows drivers. To help you out further I would like you to answer a question. Have you ever had a network card or similar in your computer? One way to remove the messages could then be to run winsetup from within Windows (File/run in Porgram manager). On network choose none and click OK. If the message still are there after a reboot edit the system.ini and find the rows DEVICE=vshare.386 DEVICE=vnsetup.386 .... Add a semi-colon on the beginning of each row. Change all rows which HAVE ERROR MESSAGES and NO OTHER. ;DEVICE=vshare.386 ;DEVICE=vnsetup.386 .... Now your errors should be gone. If you actually had a network card now is the time to (try to) re-install it. Good luck!

Nitro2k01 why do you ask if he has installed a network card in his computer?? I have a similar problem...