© 1998 Microsoft Corporation. All rights reserved.
Installation Notes contains vital information about installing Microsoft® Visual Studio™ 6.0 -- Development System for Windows and the Internet, and its family of development products. Information in this file may apply to all or a number of the products shipped in the Visual Studio suite. This Readme updates information provided in the MSDN Library Visual Studio 6.0 documentation.
Installation Notes is one of a "family" of Readmes shipped with the suite. All product Readme files reside at the root of Visual Studio compact disc 1. These Readme files (install.htm, plus several others called readmeXX.htm, where XX signifies a product) utilize current Web technology so users can find and view their information quickly. They may be viewed with a Web browser, such as Microsoft Internet Explorer 4, or in Notepad.
Note Be sure all headings in the table of contents are expanded when you search this Readme for a topic. In this way, you will know when the search finds the topic among the TOC headings.
Special Installation Instructions for Computers with Non-U.S. Versions of Microsoft Windows NT 4.0 and Microsoft Internet Explorer
Warning When Installing on Dual-Boot Computers
"Side-by-Side Installation": Installing Multiple Versions of Visual Studio 6.0 on the Same Computer
Installing Client Tools After Visual Studio 6.0 Is Installed
When the Installation Wizard Looks for A Web Publishing Wizard Disc
Running Standard or Server Setup When the Beta 2 Version of Microsoft Data Access Components 2.0 Is Already Installed
How to Contact Technical Support
Finding More Information on Non-Visual Studio Programs and Tools Shipped with the Visual Studio Suite
Minimum Requirements for Installation and Operation of Server-Side Components
Installing Server Components on Windows 95
Known Compatibility Issues with SQL Server 6.5 and Windows NT Option Pack 4.0
Installation Wizard May Not Restart After PWS Is Installed on Windows 95 Computers
Installing Server Components on Windows 95
The ODBC Custom Action Handler Malfunctions During Installation of Visual Studio 6.0 on a Clean Windows 95 Computer
Windows 95 Registry Size: 64 KB Limitation May Cause A Warning During Visual Studio Installation
Installing Microsoft FrontPage 98 Extensions on Some Windows 95 Computers
Special Installation Instructions for Computers with Non-U.S. Versions of Microsoft Windows NT 4.0 and Microsoft Internet Explorer
NEC PC 98 Installation Issue
Microsoft® Visual Studio™, Enterprise Edition
This section lists installation-related information on programs and files shipped with Visual Studio 6.0.
If you have a dual-boot computer and want to install and run Visual Studio programs with both operating systems, you must install these products into separate directories.
Installing a Visual Studio product, such as Visual C++ or Visual Basic, multiple times on the same directory can result in undefined behavior. Installing a product to the same location from each operating system is sometimes done to save disk space, but it will lead to problems and is not supported.
For example, if you install onto the same directory, you will not be able to fully uninstall the product from both systems. Uninstalling on one system may result in undefined behavior, including the removal of system files from the other system.
Visual Studio products with the same version and in the same language—Visual C++ and Visual Basic version 6.0 in English, for example—can be installed separately on the same workstation. Such installations are supported by Microsoft. The Visual Studio 6.0 Installation Wizard detects if other versions of the 6.0 product line have been installed on a developer's workstation.
Mixing different language versions, point releases, or product tiers on the same workstation is generally not supported. This means that the installation may fail, one or more of Visual Studio 6.0 products may not work even if the installation succeeds, or in the worst case you may not be able to uninstall any of the products completely.
If the Wizard generates a warning during installation, the safest course of action is to uninstall the Visual Studio 6.0 product before proceeding. The detection scheme checks for the following scenarios:
| Product | Supported Installation |
| Visual Basic | Install to two different locations |
| Visual C++ | [still checking] |
| Visual FoxPro | [still checking] |
| Visual InterDev | Install to the same location. You must reinstall after uninstalling one version. |
| Visual J++ | Install to the same location. You must reinstall after uninstalling one version. |
| Visual SourceSafe | [still checking] |
To install any of the following components, you must install them at the same time you install Visual Studio 6.0.
Use the following procedure to install any of the listed components after you have installed Visual Studio 6.0
When installing Visual Studio 6.0 or the Visual J++ Technology Preview 2, and you get a dialog box asking you to insert the Web Publishing Wizard disc, close the dialog box and proceed with the installation.
Neither Visual Studio nor Visual J++ ships a Web Publishing Wizard on a separate disc. Users may get this message when they are installing Visual Studio or Visual J++ to computers that have Temp directories set to removable drives, such as an IOMega's Jazz Drive.
After your Visual Studio or Visual J++ installation is complete, if you want to install the Web Publishing Wizard, do the following:
If you have already installed Microsoft Data Access Components 2.0 beta 2, which comes with Visual Studio, and you run the standard or server setup again, you may get the following error message:
File is installed and supports English. Currently, version number of filename is installed and supports English (United States). The software you are installing contains the same component, but it supports English (United States). Do you want the existing copy to be replaced?
This message is a known issue, and will not affect your setup. You may ignore the message and click either Yes or No to continue.
The online documentation includes complete information on how to get support and support options, including free support and online support. Click the MSDN Library Visual Studio 6.0 icon and open the Visual Studio Documentation. Support information is in Technical Support, under Getting Started with Visual Studio 6.0.
Note You must install MSDN to get the online documentation.
You also can look up support information on the web at http://www.microsoft.com/support. You can also call (425) 635-7012.
For more and specific information on SDKs and non-Visual Studio programs and tools, consult their readmes. Use the following table to locate the Readmes.
| Program/Tool | Readme File Name | Location |
| This table | is under | construction! |
| ??? | ??? | ??? |
| ??? | ??? | ??? |
| ??? | ??? | ??? |
| ??? | ??? | ??? |
This section lists installation issues identified for server-side components shipped with Visual Studio.
Consult the following table for information on operating system, browser, and other dependency requirements for installation and use of server-side components.
Table of Minimum Requirements for Installation of Server-Side Components
| Component | NT Server? | NT Workstation? | Windows 95/98? | Requires Microsoft Internet Explorer? | Other Dependencies? |
| Windows NT Option Pack 4.0 | NT Svr. | NT Workstation 4.0 SP3 | Limited on Win95 | None | |
| SQL Server 6.5 (DEV Edition) | NT Svr. | NT Workstation 3.51 + | Installs some tools on Windows 95 | No | None |
| SQL Server Debugging Service | NT Svr. 3.51 Sp5 or better | --- | --- | No | Needs SQL server 6.5 (SP3) |
| Visual SourceSafe Server Components | NT4 Svr. | NT Workstation 4 | Windows 95 | Yes. Version 4 for viewing HTML Help | None |
| Posting Acceptor (2.0) | NT4 Svr. | NT Workstation 4.0 SP3 | Windows 95 | --- | Install NTOP before PA 2.0 |
| Remote Machine Debugging (Script Debugging) | NT4 Svr. | NT Workstation | Windows 95 | Yes. Version 4 or later | None |
| Visual InterDev Server Components | NT4 Svr. | NT Workstation 4.0 SP3 | Windows 95 | Yes. Version 4 or later | Install NTOP, MDAC, FP Extensions before VIDSS |
| FrontPage Server Extensions | NT4 Svr. | NT Workstation 4.0 SP3 | Windows 95 | Yes. Version 4 or later | Install NTOP, MDAC before FP Extension |
| Fox ISAPI Samples and Extensions | --- | NO OS dependencies (samples) | --- | Any generic browser | None |
| Visual Studio Analyzer (VISTA) | Yes | NT Workstation 4.0 SP3 | Windows 95 (with DCOM update) | Yes. Only on W95 to get DCOM | None |
| Application Performance Explorer (APE) | NT4 Svr. | NT Workstation 4.0 SP3 | Windows 95 (with DCOM update) | Yes. Only on W95 to get DCOM | None |
| MDAC 2.0 Update | NT4 Svr. | NT Workstation 4.0 | Windows 95 | No | Install after NTOP and Before SNA |
| SNA server | NT4 Svr. | NT Workstation 4.0 | --- | No | Install after MDAC and MTS |
We recommend installing all server applications on computers running Windows NT.
Enterprise and Professional Editions of Visual Studio 6.0 products are packaged with a variety of Micosoft server applications specifically tailored for the Visual Studio developer. Most applications can be installed on either Windows 95 or Windows NT operating systems. We recommend installing all server applications on Windows NT, either Workstation or Server.
If you choose to set up servers on a Windows 95 the order of installation is important. On Windows 95 some applications must be installed before others for the installation to complete successfully and the product to work. Install the components in the following order:
If you install SQL Server 6.5 on a computer with Windows NT Option Pack 4.0 installed, some of your Design Time Controls (DTCs) may be overwritten.
If this happens, you will get an error message when you launch Microsoft Transaction Server (MTS). The message will instruct you to reinstall MTS.
To prevent this situation, install NT Option Pack after you install SQL Server.
Information in this section addresses issues on debugging and configuring computers for debugging services.
To use SQL Debugging services on a computer that has SQL Server 6.5 and Visual C++ 5.0 or higher installed, make sure that the Remote Automation (RA) configuration properties of the computer are set correctly.
To check RA configuration properties
Also, your SQL Debugging scenarios may not work if you run SQL Server as a service under the Local System account. You must select This Account and enter a valid account and password.
This section lists issues identified when Visual Studio 6.0 is installed on Windows 95 computers.
If you choose to install Personal Web Server (PWS) on a Windows 95 computer, the Installation Wizard may not resume correctly after the computer restarts. To proceed, start Setup.exe again from the first disc of your Visual Studio 6.0 CD set. The Installation Wizard automatically resumes setup at the correct point.
The ODBC Custom Action Handler (CAH) works when Visual Studio 6.0 is installed on a computer running Windows NT 4.0, or a computer with Windows 95 and Microsoft Internet Explorer 4.0. The ODBC CAH fails if Visual Studio is installed on a Windows 95 computer that does not have Microsoft Internet Explorer 4.0.
[Under Construction!]
When the Installation Wizard launches other client or server setups, the Wizard becomes invisible and waits until the component installation is complete. The Wizard then reappears, enabling the user to install another component.
When you install Microsoft FrontPage 98 extensions on some Windows 95 computers, the Installation Wizard may remain hidden for several minutes after the FrontPage setup is complete.
During the time that the Wizard is hidden, you cannot launch the setup program again. A second Installation Wizard will not start when the program detects that one is already running.
This section lists installation issues that may affect programs already installed on your computer.
The IISAM Exchange driver requires that Microsoft Exchange or Microsoft Outlook be fully installed on your computer prior to installation of Visual Studio. If neither is installed, the IISAM Exchange driver will not register correctly.
To manually correct the problem after you've installed Visual Studio 6.0, you can install Microsoft Exchange or Microsoft Outlook and then self-register the IISAM Exchange driver using this command line:
Regsrv32 msech35.dll
This section lists known setup issues related to computers with non-U.S. versions of Microsoft programs.
On NEC PC98's where the C drive is a floppy disk, if you get the error Cannot read drive \Device\Floppy0:, place a formatted floppy disk in the drive. Make sure that the drive door is closed and that the disk is properly formatted. Then, proceed with installation.
If you are installing this version of Visual Studio 6.0 on a non-U.S. version of Windows NT 4.0, you must first install the appropriate language version of Windows NT 4.0 Service Pack 3.
To install this version of Visual Studio 6.0 on a computer that uses an international version of Microsoft Internet Explorer, you must install the appropriate language version of Microsoft Internet Explorer.
The international versions of Windows NT 4.0 Service Pack 3 are available from these locations:
The international versions of Microsoft Internet Explorer 4.x are available from:
This section discusses all issues identified in Data Access SDK 2.0.
The Data Access SDK delivered with Visual Studio requires that the Microsoft Data Access components be installed prior to installing this SDK. Otherwise, when the SDK setup is run, you will get the message:
ODBC is not installed on this machine. If you continue, you will receive errors. Do you wish to continue anyway?
To resolve this, make sure that you have run the Visual Studio setup before installing the Data Access SDK.
You must update the catalog procedures if you plan to use SQL Server 6.5 or older with MDAC 2.0. See the SQL Server Driver Help file, drvssrv.hlp, for more information.
Typically, you will find drvssrv.hlp