Microsoft KB Archive/102478

{|
 * width="100%"|

-

The information in this article applies to:


 * Microsoft Visual Basic Standard and Professional Editions 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).

RESOLUTION
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.

MORE INFORMATION
The following file is available for download from the Microsoft Software Library:

"WW1000.EXE" For more information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base: "Q119591 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 query words: kbfile

Keywords : kbVBp300bug kbVBp400fix kbGrpVB TlsSetWiz

Version : 3.00

Platform : WINDOWS

Issue type :
 * }