ACC: Running MS-DOS SHARE with Windows for Workgroups

Last reviewed: April 2, 1997
Article ID: Q88914
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1, 2.0

SUMMARY

Novice: Requires knowledge of the user interface on single-user computers.

If you are running a regular version of Microsoft Windows 3.x (not Windows for Workgroups or Windows NT) during the installation of Microsoft Access version 1.0 or 1.1, Setup automatically inserts the following MS-DOS command in the AUTOEXEC.BAT file:

   <MS-DOS directory>\SHARE.EXE /L:500

If you are running Windows for Workgroups, we recommend that you not load this SHARE command.

MORE INFORMATION

Microsoft Access versions 1.0 and 1.1

Setup automatically detects Windows for Workgroups and does not install SHARE if Windows for Workgroups is found.

Windows for Workgroups has its own sharing mechanism (VSHARE.386), which is loaded with Windows by a SYSTEM.INI file entry. VSHARE.386 is intended as a replacement for SHARE.EXE.

SHARE.EXE is dependent on the number of locks specified by the /L: parameter, with a default of 20. VSHARE.386, on the other hand, allocates the number of locks dynamically.

Because VSHARE.386 is a 386 enhanced mode virtual device driver (VxD), it contains features that improve file sharing when running in 386 enhanced mode. Because it was designed to work with Windows for Workgroups, VSHARE.386 has greater usability features than SHARE.EXE, especially regarding access control.

If SHARE.EXE is loaded and you start Windows for Workgroups in 386 enhanced mode, VSHARE.386 takes over file sharing control until you exit Windows. If you usually run Windows for Workgroups in 386 enhanced mode, you may not need to run SHARE.EXE at all, saving you 5K or more of conventional memory. The number of locks available is especially important if you are using your Windows for Workgroups computer as a network server.

Microsoft Access version 2.0

Microsoft Access version 2.0 will install VSHARE.386 instead of modifying the AUTOEXEC.BAT file to load SHARE.EXE. If you are already loading SHARE.EXE in the AUTOEXEC.BAT file, Microsoft Access will leave the line in the AUTOEXEC.BAT file alone, but will still install VSHARE.386. When you enter 386 enhanced mode, VSHARE.386 will take over from SHARE.EXE.


Additional query words: wfw
Keywords : kbsetup StpNet
Version : 1.0 1.1 2.0
Platform : WINDOWS
Hardware : x86
Issue type : kbinfo


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.