BUG: 16-Bit Setup Does Not Detect a 32-Bit Installation (149460)



The information in this article applies to:

  • Microsoft Visual Basic Standard Edition, 32-bit, for Windows 4.0
  • Microsoft Visual Basic Professional Edition, 16-bit, for Windows 4.0
  • Microsoft Visual Basic Professional Edition, 32-bit, for Windows 4.0
  • Microsoft Visual Basic Enterprise Edition, 16-bit, for Windows 4.0
  • Microsoft Visual Basic Enterprise Edition, 32-bit, for Windows 4.0

This article was previously published under Q149460

SYMPTOMS

The 16-bit Visual Basic setup program does not detect a previously installed 32-bit Visual Basic installation.

CAUSE

The 16-bit setup program does not detect a directory with a long file name, and therefore cannot find the 32-bit Visual Basic installation.

RESOLUTION

Select the Custom option for the 16-bit Visual Basic setup program and select the short file name version of the directory containing the 32-bit Visual Basic installation.

STATUS

Microsoft has confirmed this to be an issue in the Microsoft products listed at the beginning of this article. Microsoft is researching this issue and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Install the 32-bit version of Visual Basic into the default directory. The default directory is C:\Program Files\Microsoft Visual Basic.
  2. Install the 16-bit version of Visual Basic. Note that the setup program recommends C:\VB as the default directory instead of the directory containing the 32-bit Visual Basic installation.

Modification Type:MajorLast Reviewed:6/29/2004
Keywords:kbBug kbpending kbsetup KB149460