install.htm

msdn帮助文档；由于文件太大

</tr>
<tr>
    <td><font face="verdana,arial,helvetica" SIZE=2>Visual Studio, Professional Edition</font></td>
    <td><font face="verdana,arial,helvetica" SIZE=2>CD#2</font></td>
</tr>
<tr>
    <td><font face="verdana,arial,helvetica" SIZE=2>Visual Studio, Enterprise Edition</font></td>
    <td><font face="verdana,arial,helvetica" SIZE=2>CD#3</font></td>
</tr>
<tr>
    <td><font face="verdana,arial,helvetica" SIZE=2>Visual InterDev</font></td>
    <td><font face="verdana,arial,helvetica" SIZE=2>CD#1</font></td>
</tr>
</table>
</p>
<p>
<li>Return to the <b>Command Prompt</b> and restart the Web server: Type <b>pws/start</b> and press ENTER.</li>
</ol>


          <!------------------------------------------------------>
          <!--(Sec. 3) TOPIC 2-->

<h4><a name="sqldebuggingoncomputerswithsql65andvc5orhigher">Using SQL Debugging Services on a Computer with SQL Server 6.5 and Visual C++ 5.0 or Higher Installed</a></h4>
<p>
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.</p>
<p><b>To check RA configuration properties</b>
<ol> 
<li>Run dcomcnfg.exe.
<li>Select Remote Automation CLSID_StubMarhsaler.
<li>Click <b>Properties</b>.
<li>In the <b>Identity</b> tab, select Interactive User.
</ol>
<p>Also, your SQL Debugging scenarios may not work if you run SQL Server as a service under the Local System account. You must select <b>This Account</b> and enter a valid account and password.
</p>
<hr align=left color=black SIZE=1 width=320>
<!--------------------------------------------------------->
<!--SECTION 4-->

<h3><a name="forwin95">Issues Specific to Windows 9<i>x</i> Computers</a></h3>

<p>This section lists issues identified when Visual Studio 6.0 is installed on Windows 95 or Windows 98 computers.</p>

          <!------------------------------------------------------>
          <!--(Sec. 4) TOPIC 1-->

<h4><a name="windows95registrysize">Windows 95 Registry Size: 64 KB Limitation May Cause A Warning During Visual Studio Installation</a></h4>
<p>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.</p>
<p>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.</p>
<p>Additionally, you can uninstall programs you no longer use by utilizing the Add/Remove Programs from the Control Panel. The registry keys used exclusively by those programs will then be deleted.</p>
<p>To save further on registry space used by programs you intend to keep, uninstall, then reinstall these programs to shorter installation paths.</p>
<p>Consider using the RegClean utility, designed to clean up unnecessary entries in your registry. For more information and a download link, go to <a href="http://support.microsoft.com/support/kb/articles/q147/7/69.asp">http://support.microsoft.com/support/kb/articles/q147/7/69.asp</a></p>
<p><b>Note</b>&nbsp;&nbsp;&nbsp;On Windows NT Workstations and Servers, Visual Studio setup will automatically resize the registry.
</p>
<p></p>

          <!------------------------------------------------------>
          <!--(Sec. 4) TOPIC 2-->

<h4><a name="whenautologonisenabled">Disable Autologon Before Running Visual Studio 6.0 Setup</a></h4>
<p>Visual Studio setup may fail on Windows 95 computers configured with Autologon.</p>
<p>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 found at <a href="http://support.microsoft.com/support/kb/articles/q141/8/58.asp">http://support.microsoft.com/support/kb/articles/q141/8/58.asp</a>.</p><blockquote><b>Note</b>&nbsp;&nbsp;&nbsp;This article contains several additional steps that may not be relevant on your system.
</blockquote>
<p>If you installed Visual Studio products on a Windows 95 computer configured with Autologon, and setup failed, repeat your setup steps with Autologon disabled.</p>

          <!------------------------------------------------------>
          <!--(Sec. 4) TOPIC 3-->

<h4><a name="internetconnectiondialog">An Internet Connection Dialog Box May Appear at Startup of Windows or Other Applications</a></h4>
<p>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 &#34;autodial&#34; or &#34;autoconnect.&#34; You can turn off this behavior by setting the registry key EnableRemoteConnect to &#34;N.&#34;
</p>
<p>To do this, create a text file &#34;DisbleAutoConnect.reg&#34; with exactly the following three lines:
</p>
<blockquote>REGEDIT4</blockquote>
<blockquote>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLE]</blockquote>
<blockquote>&#34;EnableRemoteConnect&#34;=&#34;N&#34;</blockquote>
<p>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 (see <a href="http://support.microsoft.com/support/kb/articles/Q177/3/94.asp">http://support.microsoft.com/support/kb/articles/Q177/3/94.asp</a>).
</p>
<p>If there are instances when you need to have remote connections enabled, create a second REG file, &#34;EnableRemoteConnect.reg&#34;, with exactly the following 3 lines:
</p>
<blockquote>REGEDIT4</blockquote>
<blockquote>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLE]
</blockquote>
<blockquote>&#34;EnableRemoteConnect&#34;=&#34;Y&#34;
</blockquote>
<p>Run &#34;EnableAutoConnect.reg&#34; to make the setting, and then run &#34;DisbleAutoConnect.reg&#34; to disable it when autoconnect is no longer needed.</p>

          <!------------------------------------------------------>
          <!--(Sec. 4) TOPIC 4-->

<h4><a name="resumingsetupafterinstallingpws">Installation Wizard May Not Restart After PWS Is Installed on Windows 95 Computers</a></h4>
<p>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.</p>

          <!------------------------------------------------------>
          <!--(Sec. 4) TOPIC 5-->

<h4><a name="frontpage98onwin95">Installing Microsoft FrontPage 98 Extensions on Some Windows 95 Computers</a></h4>
<p>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.</p>
<p>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.
</p>
<p>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.</p>

<hr align=left color=black SIZE=1 width=320>
<!--------------------------------------------------------->
<!--SECTION 5-->

<h3><a name="vs6andothers">Notes Impacting Other Installed Programs</a></h3>

<p>This section lists installation issues that may affect programs already installed on your computer.</p>

          <!------------------------------------------------------>
          <!--(Sec. 5) TOPIC 1-->

<h4><a name="iisamexchangedriver">IISAM Exchange Driver Will Fail if Microsoft Exchange or Microsoft Outlook Is Not Already Installed</a></h4>
<p>
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 be self-registered.</p>
<p>
To correct the problem after you've installed Visual Studio 6.0, you can install Microsoft Exchange or Microsoft Outlook and then manually self-register the IISAM Exchange driver using this command line:</p>
<font face="Courier" size=2>Regsrv32 msexch35.dll</font>
<p>
<p></p>
<hr align=left color=black SIZE=1 width=320>
<!-------------------------------------------------------------->
<!--SECTION 6-->

<h3><a name="fornonusversions">Issues Related to Computers with Non-U.S. Versions of Microsoft Programs</a></h3>

<p>This section lists known setup issues related to computers with non-U.S. versions of Microsoft programs.</p>

          <!------------------------------------------------------>
          <!--(Sec. 6) TOPIC 1-->

<h4><a name="nonusnt40">Special Installation Instructions for Computers with Non-U.S. Versions of Microsoft Windows NT 4.0 and Microsoft Internet Explorer</a></h4>
<p>
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.</p>
<p> 
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. </p>
<p>The international versions of Windows NT 4.0 Service Pack 3 are available from these locations:</p>
<li>
<a href="ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes">ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes</a></li> 
<li>
<a href="http://www.microsoft.com/support/winnt/intlsp.asp">http://www.microsoft.com/support/winnt</a></li>
<p>The international versions of Microsoft Internet Explorer 4.<i>x</i> are available from:</p>
<li>
<a href="http://www.microsoft.com/ie/download/">http://www.microsoft.com/ie/download/</a></li>
<p>
          <!------------------------------------------------------>
          <!--(Sec. 6) TOPIC 2-->

<h4><a name="localizediespneededforenglishvs">BiDi Systems Must Have Localized Version of Internet Explorer 4.0 SP 1 Before English Visual Studio 6.0 Is Installed</a></h4>
<p>
Before installing the English version of Visual Studio 6.0 on a system that is configured with a bidirectional (BiDi) character set, such as Hebrew or Arabic, you first must install the localized version of Microsoft Internet Explorer 4.01 Service Pack 1.
</p>
<p>The international versions of Microsoft Internet Explorer 4.x are available from:
</p>
<li>
<a href="http://www.microsoft.com/ie/download/">http://www.microsoft.com/ie/download/</a></li>
<p>
          <!------------------------------------------------------>
          <!--(Sec. 6) TOPIC 3-->

<h4><a name="necpc98">NEC PC 98 Installation Issue</a></h4>
<p>On NEC PC98's where the C drive is a floppy disk, if you get the error <i>Cannot read drive \Device\Floppy0:</i>, 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.</p>

<hr align=left color=black SIZE=1 width=320>
<!--------------------------------------------------------->
<!--SECTION 7-->

<h3><a name="dasdkissues">Data Access SDK 2.0</a></h3>

<p>This section discusses all issues identified in Data Access SDK 2.0.</p>
          <!------------------------------------------------------>
          <!--(Sec. 7) TOPIC 1-->

<h4><a name="installreq">Install Requirements</a></h4>
<p>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:</p>
<blockquote>ODBC is not installed on this machine.  If you continue, you will receive errors.  Do you wish to continue anyway?</blockquote>
<p>To resolve this, make sure that you have run the Visual Studio setup before installing the Data Access SDK.</p>

          <!------------------------------------------------------>
          <!--(Sec. 7) TOPIC 2-->

<h4><a name="toinstallmdacsdk2">How to Install the Microsoft Data Access SDK 2.0</a></h4>
<p>The Microsoft Data Access SDK 2.0 can be installed by running the file DASDK.exe from the \dasdk directory on disc 2.</p>
<p>The SDK includes Microsoft Data Access Components samples, and further information and tools for ODBC and OLE DB developers.</p>

          <!------------------------------------------------------>
          <!--(Sec. 7) TOPIC 3-->

<h4><a name="sql65orolderwithmdac2">Before Using SQL Server 6.5 or Older with MDAC 2.0</a></h4>
<p>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, drvssrvr.hlp, for more information.</p>
<p>Typically, you will find drvssrvr.hlp</p>
<ul><li>On NT systems: \winnt\system32</li>
<li>On Windows 95: \windows\system</li></ul>


</FONT></BODY>
</HTML>