BUG: Visual C++ 1.5 Setup Does Not Set Up SHARE

Last reviewed: July 22, 1997
Article ID: Q116139
1.50 WINDOWS kbsetup kbbuglist

The information in this article applies to:

  • Microsoft Visual C++ for Windows, version 1.5

SYMPTOMS

The Setup program for Visual C++ for Windows, version 1.5, does not modify the AUTOEXEC.BAT file to include changes for the file SHARE.EXE; it also does not modify the SYSTEM.INI file to include changes for the file VSHARE.386. The Visual C++ command line tools, as well as Object Linking and Embedding (OLE) 2.0 compound file support, require file sharing to be enabled. Details for these requirements can be found on page 9 of the "Visual C++ Getting Started" manual. Symptoms of this may include a message stating "System resource exhausted" when you try to build an app from DOS (or a DOS box). This message does not occur if the SHARE parameters are set properly.

RESOLUTION

Under Windows for Workgroups, be sure that the line

   device=vshare.386

appears in the [386Enh] section of the SYSTEM.INI file in the \windows directory. Do not add the SHARE.EXE file to the AUTOEXEC.BAT file when running Windows for Workgroups.

Under Windows 3.1, it is necessary for the AUTOEXEC.BAT file to include the following line:

   SHARE /L:500 /F:5100

If SHARE is already installed, make sure that the /L:500 and /F:5100 options are properly set. The /L option sets the number of files that can be locked at one time; the default value is 20. The /F option allocates file space for the MS-DOS storage area used for file-sharing information. This value needs to be at least 5100.

NOTE: Windows, version 3.1, does not support the Windows for Workgroups vshare virtual device driver, so do not add a line for this to your SYSTEM.INI file.

When installing Visual C++ 1.5 under Windows NT, SHARE does not need to be installed in AUTOEXEC.BAT unless Visual C++ will be run under MS-DOS by means of a dual-boot configuration.

STATUS

Microsoft has confirmed this to be a bug with Visual C++ 1.5 for Windows. We are researching this bug and will post new information here in the Microsoft Knowledge Base as soon as it becomes available.


Additional reference words: 1.50
KBCategory: kbsetup kbbuglist
KBSubcategory: vc15setup
Keywords : kb16bitonly


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: July 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.