Article ID: 248887 - View products that this article applies to.
This article was previously published under Q248887
When attempting to install a Microsoft Visual Basic 3.0 application onto a target computer where a Microsoft Visual Basic 6.0 application is installed, one or more error messages are displayed and the installation fails. The specific errors may vary, but can include the following:
Invalid command-line parameters. Unable to continue.
Also, the window displaying the message, "Initializing Setup ..." may be left on the screen. If this is the case, you must use Task Manager to kill the "SETUP.EXE" task.
Setup was not completed successfully.
This problem occurs because distributions created using the Visual Basic 6.0 Package and Deployment Wizard (PDW) leave behind some files, including Setup1.exe. When a Visual Basic 3.0 distribution package finds a copy of Setup1.exe on the target system, it will use it instead of overwriting it with it's own copy of Setup1.exe. The Visual Basic 3.0 Setup cannot use the Visual Basic 6.0 version of Setup1.exe and it fails with the preceding error(s).
NOTE: Other application installations can also leave behind a file called Setup1.exe, causing the same problem.
To avoid this problem, delete the Setup1.exe file that is left on the target system before running the Visual Basic 3.0 setup.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Visual Basic 6.0 typically leaves Setup1.exe in the operating system folder, (that is, C:\Windows) but it may also be found in a Temp folder.
Steps to Reproduce Behavior
Steps to Resolve Problem
Article ID: 248887 - Last Review: December 12, 2003 - Revision: 2.0