Windows 3.1 won't boot
Robert Elmers
Jerry, I checked out what you sent, and it was okay.....
This is the full deal with this problem.
He had windows 3.1 installed and he did something to get corrupted
files. Upon trying to start windows, after DOS starts, the error:
you need to run the setup again C:\windows\system\vshare.386
the next one was:
a device file in Sys.ini is corrupt it maybe needed to run windows in
386 enhanced mode C:\Windows\system\ifsmgr.386.
Then windows came up and only the wallpaper showed. Couldn't reboot even
with the CNT-ALT-DEL command.
I tried putting in Win 3.11 for Workgroup and the errors disappeared but
the same results occurred.
I then re-installed Win 3.1 and again got the same errors. I could start
windows by WIN/S, but it still showed an error (don't recall what it
was)
I deleted the ifsmgr.386 file and the vshare.386 and again reinstalled
Win 3.1. This time the errors were basically the same but worded a bit
different.
You need to run the Setup program again
vshare.386
hit any key
You need to run the Setup program again
ifsmgr.386
hit any key
then the wall paper comes up again, but none of the program windows.
Hopefully you or someone else has an idea that might be causing this
problem shy of adding windows to a new directory....
Thanks for the first reply
Bob Elmers
Minneapolis
robt...@cris.com
Jerry Lippey/MVP
Bob, those two messages are due to lines like device=vshare.386 and
device=ifsmgr.386 in the [386Enh] section of SYSTEM.INI. You get the
message when either the files are not available or they are corrupt. You
can remove either message by placing a semi-colon in front of the
relevant line or removing the line itself.
VSHARE.386 is necessary for some applications when SHARE.EXE is not
loaded in a DOS boot file. IFSMGR.386 is used by WFWG to make 32-bit
file access work. Both the files and the SYSTEM.INI lines were installed
when Windows for Workgroups was installed.
At this point, I think if you want to go back to Windows 3.1, you should
start over.
If you want to try to make WFWG work, then I suggest you try a fresh
SYSTEM.INI and reinstall the applications over the present installations
to populate the new INI with the correct lines. Follow the instructions
in "WFWG: Creating a New SYSTEM.INI Without Third-Party Drivers":
http://www.microsoft.com/kb/articles/Q107/1/31.htm
I don't know what your problem was, of course. Since you did not post
your message as a reply to another, I don't have a thread to read. And
since you didn't quote the message to which you're responding, I don't
even know what I said about it. I don't have time to search the
newsgroup. If you reply to this, please use your news reader's Reply
feature.
-Jerry