For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
VBRun60sp6.exe installs the following core files that are included with Visual Studio 6.0 Service Pack 6. These files are the base dependencies for any component or application that is created in Visual Basic 6.0:
|Asycfilt.dll||2.40.4275.1||144 KB (147,728 bytes)|
|Comcat.dll||4.71.1460.1||21.7 KB (22,288 bytes)|
|Msvbvm60.dll||220.127.116.11||1.32 MB (1,386,496 bytes)|
|Oleaut32.dll||2.40.4275.1||584 KB (598,288 bytes)|
|Olepro32.dll||5.0.4275.1||160 KB (164,112 bytes)|
|Stdole2.tlb||2.40.4275.1||17.5 KB (17,920 bytes)|
VBRun60sp6.exe also installs the following files. These files are supporting files for the VBRun60sp6.exe self-extracting file:
|Advpack.dll||4.71.1015.0||73.2 KB (74,960 bytes)|
|Vbrun60.inf||Not Applicable||1.04 KB (1,069 bytes)|
|W95inf16.dll||4.71.704.0||2.21 KB (2,272 bytes)|
|W95inf32.dll||18.104.22.168||4.5 KB (4,608 bytes)|
For information about the command-line arguments that are available for VBRun60sp6.exe, type the following at a command line:
For additional information about command-line arguments for this file, click the following article number to view the article in the Microsoft Knowledge Base:
Do I need the VBRun60sp6.exe file?The VBRun60sp6.exe file is not intended to replace the Package and Deployment Wizard (PDW) for distributing Visual Basic applications. For example, if your application includes components such as ActiveX controls or DLLs, use the PDW or a third-party setup package for distribution. However, if your Visual Basic application depends on only the files that are included in the VBRun60sp6.exe file, you can distribute your application by providing the executable (.exe) file and VBRun60sp6.exe to end users.
To determine whether your application requires additional files for distribution, you can use the PDW to create a set of setup files as a test. When the PDW creates a setup package, the PDW also creates a Setup.lst file. Open the Setup.lst file in a text editor such as Notepad. If the [Setup1 Files] section of the Setup.lst file contains only your .exe file, end users should be able to run your application after they run the VBRun60sp6.exe file to install the core run-time files. However, if the [Setup1 Files] section contains multiple files, consider using the PDW or a third-party setup package for distribution.
In addition to distributing simple executables, you can also use the VBRun60sp6.exe file for the following:
- To minimize the size of Internet downloads of Visual Basic applications.
By running the Vbrun60sp6.exe file ahead of time, users can download your application from the Web faster.
- As a troubleshooting step when an installation of Visual Basic or a Visual Basic application fails.
If Setup fails with an error message that mentions one of the core files, or if registration of a component fails during Setup, the core files on the target computer might be mismatched. If the versions of the files in the VBRun60sp6.exe file are newer than the versions on the target computer, you might resolve the problem by running the VBRun60sp6.exe file before you run Setup.
On the Visual Studio 6.0 Professional CDs, the VBRun60.cab file is located in the same relative path on Disk 2. On the Visual Studio 6.0 Enterprise CDs, it is located on Disk 3.
Note The version of the VBRun60sp6.exe file that is included in this Knowledge Base article is different from the one on the installation CD. The version that is included in this article is the latest version. This version is included with Visual Studio 6.0 Service Pack 6.
You can use the Extract utility to extract the VBRun60.exe file from the VBRun60.cab cabinet file. The Extract.exe file is located in your Windows folder or on your installation CD for Microsoft Windows 95, Windows 98, or Windows NT. At an MS-DOS command prompt, run the following command to extract the file in the cabinet file into the current directory:
Article ID: 290887 - Last Review: Sep 22, 2011 - Revision: 1