Upgrading to Service Pack 4 or later
The best way to solve this problem is to install the latest
Visual Studio 6.0 Service Pack. That will update the C:\Program Files\Microsoft
Visual Studio\VB98\Wizards\PDWizard\Redist folder to contain the latest files.
Then you can use the PDW to rebuild the package. The Wizard uses the components
in this folder before the ones in the Windows\System or System32 folders, so
that when it generates the .inf file information, it uses these file version
numbers. This method has the advantage of automatically producing the correct
.inf file the first time (instead of requiring manual editing of them
afterwards, as mentioned in the following workarounds).
Manually updating the Redist folder
If you are using the PDW, you can also manually update the Visual
Basic Runtime and OLE files in the Redist folder:
- If you do not already have Extract.exe installed under your
system folder, get it from your Windows CD-ROM. You can find Extract.exe in
your Windows or Winnt folder or on your Windows 95, Windows 98, or Windows NT
installation CD-ROM or diskettes.)
Extract.exe is a command-line
utility. Therefore, it is used from an MS-DOS command prompt. To extract the
files within a cabinet file, be sure the Extract.exe utility is in the MS-DOS
path or copy the Extract utility to the same folder as the cabinet
file. - Download the latest Microsoft Visual Basic 6.0 run-time
components. The following
file is available for download from the Microsoft Download
Center:
Download the
VBRUN60.cab package now.
For additional information about how
to download Microsoft Support files, click the following article number to view
the article in the Microsoft Knowledge Base: 119591�
How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most
current virus-detection software that was available on the date that the file
was posted. The file is stored on security-enhanced servers that help to
prevent any unauthorized changes to the file.
Create a local folder called C:\VBRUN, and
then save the .cab file in this folder. - From a DOS prompt, navigate to the System32 folder:
cd C:\Winnt\System32
- To extract all the files in the .cab file located
extract.exe /a C:\Vbrun\Vbrun60.cab /l C:\Vbrun\
This extracts Vbrun60.exe from the .cab file.
For more
information on using the Extract.exe utility, type the following command at an
MS-DOS command prompt: extract.exe /?
See the "References" section of this article for information on
how to use Extract.exe. - Extract the contents of this self-extracting .exe file as
follows:
VBRUN60.EXE /C /T:"C:\VBRUN"
- Copy the extracted files to the Redist subfolder of the
folder in which Visual Basic is installed. By default, the path is
C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist
Be sure to copy the following files: Oleaut32.dll, Olepro32.dll,
Asycfilt.dll, Stdole2.tlb, Msvbvm60.dll, and Comcat.dll.
Manually correcting the .inf file
Another way to work around this problem is to change the
versioning inside the .inf file that is created by the PDW each time that you
create a new .cab file:
- Locate the .inf file in the support folder under the
package folder that is created by the PDW.
- Open the .inf file with Microsoft Notepad.
- Verify the file version of the following files with the
latest files that are distributed by Microsoft: Oleaut32.dll, Olepro32.dll,
Asycfilt.dll, Stdole2.tlb, Msvbvm60.dll, and Comcat.dll.
For the
latest Visual Basic 6 Service Pack, see the following article in the Microsoft
Knowledge Base:290887�
VBRun60sp6.exe installs Visual Basic 6.0 SP6 run-time files
- Save the .inf file.
- Run the .bat file that was created by the PDW to repackage
the .cab file again.