BUG: 16-Bit Setup Does Not Detect a 32-Bit Installation
Article ID: 149460
Article Last Modified on 6/29/2004
APPLIES TO
- Microsoft Visual Basic 4.0 Standard Edition
- Microsoft Visual Basic 4.0 Professional Edition
- Microsoft Visual Basic 4.0 Professional Edition
- Microsoft Visual Basic 4.0 16-bit Enterprise Edition
- Microsoft Visual Basic 4.0 32-Bit Enterprise Edition
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.
Keywords: kbbug kbsetup kbpending KB149460