When I put win32s on my windows 3.1 system, it complained about share.exe not being loaded in autoexec.bat. Further, the win32s installer said that it cannot function properly without share.exe
But every program that required win32s ( a few sierra programs) seems to function fine without me loading share.exe
Don't know, but programs like MS Office, who have to keep track of changes made to documents by multiple users may need it.
Also, I believe since Windows for Workgroups 3.11 that share.exe is nolonger required.
It got replaced by a VXD or DLL file (have to check).
"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel
1 2INTRODUCTION 3------------ 4 5The WW1000 disk included with this Application Note contains 6VSHARE.386 version 3.11.0.402. This version of VSHARE.386 is 7compatible with Microsoft Windows version 3.1 and Windows for 8Workgroups versions 3.1 and 3.11. 9 10 NOTE: Microsoft Office versions 4.2 and 4.3 install version 11 3.11.0.401 of VSHARE.386. 12 13The version of VSHARE.386 included with this Application Note differs 14from the version included with Windows for Workgroups 3.11 (version 153.11.0.300) in the following ways: 16 17 - The version of VSHARE.386 included with this Application Note 18 supports Windows version 3.1. 19 20 - The version of VSHARE.386 included with this Application Note 21 corrects a problem than can cause Windows for Workgroups 3.11 to 22 stop responding (hang) when you start your computer. 23 24USING VSHARE.386 25---------------- 26 27If you are using applications that support OLE 2.0, you must run 28either SHARE.EXE or VSHARE.386. VSHARE.386 eliminates the need to run 29SHARE.EXE when you run Windows 3.1 or Windows for Workgroups in 386 30enhanced mode. If you run Windows 3.1 in standard mode, you must run 31SHARE.EXE. If you run applications that are not compatible with 32SHARE.EXE and you are running Windows 3.1 in 386 enhanced mode, the 33applications may work with VSHARE.386 instead of SHARE.EXE. 34 35
it will work with any Windows 3.1x version (workgroup or not)
I wasn't aware of a Win 3.1 compatible vshare.386 file.
This update may saves quite a bit of conventional memory (no more share.exe).
"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel