BUG: Incorrect Edition Starts in Different Operating Systems
Article ID: 153059
Article Last Modified on 6/24/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 Q153059
SYMPTOMS
A dual-boot system with Windows for Workgroups and Windows NT has the
Enterprise Edition installed while the system is running Windows NT. The
system is rebooted under Windows for Workgroups and the Enterprise Edition
is installed in the same Visual Basic directory using the Reinstall option.
Upon starting Visual Basic under Windows for Workgroups, the Startup
windows indicate that the Standard edition is starting. The Standard
Edition of Visual Basic is 32-bit only.
CAUSE
The Reinstall option of the Setup program does not reregister files if the
files are on the system.
RESOLUTION
Rename or delete the file vb4stp16.stf and reinstall the Enterprise Edition
under both operating systems. This file is located in the default Visual
Basic directory. Deleting or renaming this file will cause the files to be
correctly registered during the reinstallation.
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 KB153059