FIX: VB 3.0 Setup Wizard Error: Sharing Violation

 Last reviewed: October 30, 1997
Article ID: Q102478
3.00 WINDOWS kbtool kbbuglist kbfile

The information in this article applies to:

- Standard and Professional Editions of Microsoft Visual Basic 

  programming system for Windows, version 3.0

SYMPTOMS

The error message "Sharing Violation on drive C:" is displayed during the compression stage when using the Setup Wizard tool included with Visual Basic version 3.0 for Windows.

CAUSE

This is caused by the combination of the file sharing utility SHARE.EXE, the compression utility COMPRESS.EXE, and the Setup Wizard tool SETUPWIZ.EXE. The problem occurs when the compression utility tries to open the files SETUPKIT.DLL, VBRUN300.DLL, COMMDLG.DLL, or CMDIALOG.VBX.

This problem does not occur when running under Windows for Workgroups version 3.1 in Enhanced mode, because Windows for Workgroups version 3.1 does not use the file sharing utility SHARE.EXE. It uses its own file sharing utility (VSHARE.386).

WORKAROUND

If you need to use the file sharing utility SHARE.EXE, copy SETUPKIT.DLL, VBRUN300.DLL, COMMDLG.DLL, and CMDIALOG.VBX from the \WINDOWS\SYSTEM directory to the directory where the SETUPWIZ.EXE file is located. Then the SETUPWIZ.EXE and COMPRESS.EXE program will not try to use the same files at the same time. Set the Read-Only attribute of all four files, regardless of their actual location.

If you are running Windows in 386 Enhanced mode, you can also workaround the problem by using the VSHARE.386 virtual device driver rather then the MS-DOS SHARE.EXE program.

To obtain the VSHARE.386 driver, download WW1000.EXE, a self-extracting file, on these services:

  • Microsoft's World Wide Web site on the Internet 

          On the www.microsoft.com home page, click the Support icon
      Click Knowledge Base, and select the product
      Enter kbfile WW100.EXE, and click GO!
      Open the article, and click the button to download the file
  • Internet (anonymous FTP) 

          ftp ftp.microsoft.com
      Change to the Softlib/Mslfiles folder
      Get WW100.EXE
  • The Microsoft Network 

          On the Edit menu, click Go To, and then click Other Location
      Type "mssupport" (without the quotation marks)
      Double-click the MS Software Library icon
      Find the appropriate product area
      Locate and Download WW100.EXE
  • Microsoft Download Service (MSDL) 

          Dial (206) 936-6735 to connect to MSDL
      Download WW100.EXE

For additional information about downloading, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q119591
   TITLE     : How to Obtain Microsoft Support Files from Online Services
If you are unable to access the sources listed above, you can have the driver mailed to you by calling Microsoft Technical Support Monday through Friday, 6:00 a.m. to 6:00 p.m. Pacific time at (206) 637-7098. Ask for Application Note identification number WW1000.EXE. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, go to the Microsoft Web site http://www.microsoft.com/worldwide/default.htm

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This problem has been corrected in Visual Basic version 4.0.

Additional reference words: buglist3.00 3.00 fixlist4.00
KBCategory: kbtool kbbuglist kbfile
KBSubcategory: TlsSetWiz
Keywords : TlsSetWiz kbbuglist kbfile kbtool
Version : 3.00
Platform : WINDOWS
Solution Type : kbfix

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