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

 Last reviewed: April 3, 1996
Article ID: Q149460
The information in this article applies to:
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0

SYMPTOMS

The 16-bit Visual Basic setup program does not detect a previously installed 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.

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.

WORKAROUND

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.

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.

Additional reference words: 4.00 vb4win vb4all
KBCategory: kbbuglist
KBSubcategory: SetIns




THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 3, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.