Microsoft KB Archive/217094

= INFO: Visual Studio 6.0 Installation Notes Part 4 of 7- Issues Specific to Windows 9x Computers =

Article ID: 217094

Article Last Modified on 8/15/2005

-

APPLIES TO


 * Microsoft Visual Studio 6.0 Enterprise Edition

-



This article was previously published under Q217094



SUMMARY
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 Microsoft Developer Network (MSDN) Library Visual Studio 6.0 documentation.

The entire Installation Notes are in the file, Install.htm. This file is installed during setup in the Visual Studio 6.0 directory. Please see the "References" section for other parts of the Installation Notes.



MORE INFORMATION
This article lists issues identified when Visual Studio 6.0 is installed on Windows 95 or Windows 98 computers. The following topics are in this article:
 * Windows 95 Registry Size: 64 KB Limitation May Cause A Warning During Visual Studio Installation


 * Disable Autologon Before Running Visual Studio 6.0 Setup


 * An Internet Connection Dialog Box May Appear at Startup of Windows or Other Applications


 * Installing Server Components on Windows 95


 * For ASP Debugging on Windows 95/98 Computers, Install IIS Patch After Installing BackOffice


 * Installation Wizard May Not Restart After PWS Is Installed on Windows 95 Computers


 * Installing Microsoft FrontPage 98 Extensions on Some Windows 95 Computers

Windows 95 Registry Size: 64 KB Limitation May Cause A Warning During Visual Studio Installation
A 64-KB limitation in the size of the SharedDLL key in the Windows 95 system registry may generate a warning that appears when you install Visual Studio 6.0.

Before continuing with setup, you should shorten the install path where you plan to install Visual Studio 6.0, reducing the amount of registry space required.

Additionally, you can uninstall programs you no longer use by utilizing the Add/Remove Programs from Control Panel. The registry keys used exclusively by those programs will then be deleted.

To save further on registry space used by programs you intend to keep, uninstall, then reinstall these programs to shorter installation paths.

NOTE: On Windows NT Workstations and Servers, Visual Studio setup will automatically resize the registry.

Disable Autologon Before Running Visual Studio 6.0 Setup
Visual Studio setup may fail on Windows 95 computers configured with Autologon.

Before you install Visual Studio 6.0 or any of its products on a Windows 95 computer with Autologon enabled, turn off Autologon by following the instructions from the following article in the Microsoft Knowledge Base:

141858 No Windowsor Network Logon Dialog Box at Startup

NOTE: This article contains several additional steps that may not be relevant on your system. If you installed Visual Studio products on a Windows 95 computer configured with Autologon, and setup failed, repeat your setup steps with Autologon disabled.

An Internet Connection Dialog Box May Appear at Startup of Windows or Other Applications
If remote connections are enabled in Windows 95 or Windows 98, the system may try to initiate an Internet connection at Windows startup or at the start of many applications. This behavior is sometimes called "autodial" or "autoconnect." You can turn off this behavior by setting the registry key EnableRemoteConnect to "N."

To do this, create a text file "DisbleAutoConnect.reg" with exactly the following three lines:

REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLE] "EnableRemoteConnect"="N"

Changing this setting to disable remote connections should not prevent any of your normal Internet activities, and this setting is the default for most systems. However, enabling remote connections is necessary for some features of DCOM. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

177394 HOWTO:Troubleshoot Run-Time Error '429' in DCOM Applications

If there are instances when you need to have remote connections enabled, create a second REG file, "EnableRemoteConnect.reg", with exactly the following 3 lines: REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLE] "EnableRemoteConnect"="Y" Run "EnableAutoConnect.reg" to make the setting, and then run "DisbleAutoConnect.reg" to disable it when autoconnect is no longer needed.

Installing Server Components on Windows 95
It is recommended that you install all server applications on computers running Windows NT.

Enterprise and Professional Editions of Visual Studio 6.0 products are packaged with a variety of Microsoft 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 computer, 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:

NT Option Pack

FrontPage 98 Server Extensions

Data Access Components 2.0

Visual InterDev Server Components

Application Performance Explorer

Visual Studio Analyzer

(Any Order) Visual SourceSafe Server

(Any Order) Visual FoxPro Server Samples

The Installation Wizard presents these options in the same order. Again, ordering is significant on Windows 95 only.

For other issues relating to Windows 95 computers, go to Issues Specific to Windows 95 Computers.

For ASP Debugging, Install IIS Patch After Installing BackOffice
Internet Information Server (IIS) has a patch that fixes problems related to debugging Active Server Pages (ASP) from Visual InterDev. This patch also fixes a Windows 95/98 problem in which changes to the Global.asa would not be reflected in your application (such as adding, changing, or removing data connections) until you stopped and restarted your Web server.

To ensure that ASP debugging works properly, or to address the Windows 95/98 issue, apply the patch after the BackOffice Installation Wizard has finished.

To apply the IIS patch on Windows NT computers:  Run \IIS\WinNT\ASP2FIX1.exe from the installation disc. Product Disc Location:

Visual Studio, Professional Edition CD#2

Visual Studio, Enterprise Edition CD#3

Visual InterDev CD#1

 Restart when prompted.

To apply the IIS patch on Windows 9x computers:  Stop the Web server from the command prompt: Type pws/stop and press ENTER. In the \ \system\inetsrv directory, rename Asp.dll to Asp.old. From the \IIS\Win9x\ directory of the installation disc, copy Asp.dll and paste it to the \ \system\inetsrv directory on your computer. Product disc location:

Visual Studio, Professional Edition CD#2

Visual Studio, Enterprise Edition CD#3

Visual InterDev CD#1

 Return to the command prompt and restart the Web server: Type pws/start and press ENTER.</li></ol>

Installation Wizard May Not Restart After PWS 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.

Installing Microsoft FrontPage 98 Extensions on Some Windows 95 Computers
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.

While 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.

<div class="references_section">