-
Notifications
You must be signed in to change notification settings - Fork 18
/
Copy pathINSTALL.HTM
799 lines (660 loc) · 48.9 KB
/
INSTALL.HTM
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<title>Installation Notes</title>
<META NAME="MS-HAID" CONTENT="install.htm">
</HEAD>
<BODY BGCOLOR="#FFFFFF" link="#0000FF" vlink="#660066" onclick="checkExpand()">
<font face="Verdana, Arial, Helvetica, sans-serif" size="2" color="#000000">
<!-------------------Scripting----------->
<script language="JSCRIPT">
function checkExpand( )
{
if ("" != event.srcElement.id)
{
var ch = event.srcElement.id + "Child";
var el = document.all[ch];
if (null != el)
{
el.style.display = "none" == el.style.display ? "" : "none";
if (el.style.display != "none")
event.returnValue=false;
}
}
}
</script>
<!-----------------Readme Intro------------------->
<h2><a name="geninstall">Installation Notes</a></h2>
<p>© 1998 Microsoft Corporation. All rights reserved.</p>
<P>Other product and company names herein may be the trademarks of their respective owners. </P>
<p><i>Installation Notes</i> 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 <i>MSDN Library Visual Studio 6.0</i> documentation.</p>
<p><i>Installation Notes</i> 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 readme<i>XX</i>.htm, where <i>XX</i> signifies a product) use 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.</p>
<h5><a class=ex href="#" title="Click to expand or collapse." id="PrintingInstructions">How do I print all the available Readme files at one time from Microsoft Internet Explorer?</a></h5>
<div id="PrintingInstructionsChild" onclick="cl_script_data" style="display:none">
<a name="#ieinstructions"></a>
<blockquote>
<ol>
<li>Open readme<i>XX</i>.htm, or install.htm, in Microsoft Internet Explorer.</li>
<li>On the <b>File</b> menu, click <b>Print</b>.</li>
<li>In the <b>Print</b> dialog box, set the printing options you want.</li>
<li>Select <b>Print all linked documents</b> and click <b>OK</b>.</li>
</ol>
</blockquote>
</div>
<!---------------TOC---------------------->
<p>
<h3>Contents</h3>
<blockquote><b>Note</b> 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.
</blockquote>
</p>
<!-------------------Section 1--------------->
<h5><a class=ex href="#" title="Click to expand or collapse." id="InformationonFilesandProgramsShippedwithVisualStudio">Installation Instructions for Visual Studio Programs</a></h5>
<div id="InformationonFilesandProgramsShippedwithVisualStudioChild">
<blockquote>
<a href="#releaseversionoverbeta">Installing Over Visual Studio Beta, Pre-Release, and Technical Preview Installations</a> </blockquote>
<blockquote>
<a href="#sidebysideinstallation">"Side by Side Installation": Installing Multiple Versions of Visual Studio 6.0 Products on the Same Computer</a> </blockquote>
<blockquote>
<a href="#installingondualbootcomputers">Warning When Installing on Dual-Boot Computers</a> </blockquote>
<blockquote>
<a href="#installationonsharedcddrive">Installing Visual Studio from a Shared CD Drive</a> </blockquote>
<blockquote>
<a href="#letiefinish">Let Microsoft Internet Explorer Setup Finish Before Proceeding with Visual Studio Installation</a> </blockquote>
<blockquote>
<a href="#ieinstallsoldmdacfiles">When Microsoft Internet Explorer Setup Installs Older Versions of MDAC Files</a> </blockquote>
<blockquote>
<a href="#nonusnt40">Special Installation Instructions for Computers with Non-U.S. Versions of Microsoft Windows NT 4.0 and Microsoft Internet Explorer</a> </blockquote>
<blockquote>
<a href="#localizediespneededforenglishvs">BiDi Systems Must Have Localized Version of Internet Explorer 4.0 SP 1 Before English Visual Studio 6.0 Is Installed</a> </blockquote>
<blockquote>
<a href="#webpublishingwizarddisc">When the Installation Wizard Looks for A Web Publishing Wizard Disc</a> </blockquote>
<blockquote>
<a href="#installingclienttoolsafterinstallingvs">Installing Client Tools and Server Components After Visual Studio 6.0 Products Are Installed</a> </blockquote>
<blockquote>
<a href="#howtocontacttechnicalsupport">How to Contact Technical Support</a></blockquote>
</div>
<p>
<!-----------------------Section 2------------------->
<h5><a class=ex href="#" title="Click to expand or collapse." id="ServerSideSetups">Installing Server-Side Components</a></h5>
<div id="ServerSideSetupsChild">
<blockquote>
<a href="#minimumreqsforserversideinstall">Minimum Requirements for Installation and Operation of Server-Side Components</a></blockquote>
<blockquote>
<a href="#setupalreadyrunning">"Setup Already Running" Message Shows Up During Installation of Server-Side Components</a></blockquote>
<blockquote>
<a href="#servercomponentsonwin95">Installing Server Components on Windows 95</a></blockquote>
<blockquote>
<a href="#sqlandwinntop">Known Compatibility Issues with SQL Server 6.5 and Windows NT Option Pack 4.0</a> </blockquote>
</div>
<p>
<!-----------------------Section 3------------------->
<h5><a class=ex href="#" title="Click to expand or collapse." id="configuringdebugging">Configuring for Debugging</a></h5>
<div id="configuringdebuggingChild">
<blockquote>
<a href="#iispatchforaspdebugging">For ASP Debugging, Install IIS Patch After Installing BackOffice</a> </blockquote>
<blockquote>
<a href="#sqldebuggingoncomputerswithsql65andvc5orhigher">Using SQL Debugging Services on a Computer with SQL Server 6.5 and Visual C++ 5.0 or Higher Installed</a> </blockquote>
</div>
<p>
<!----------------------Section 4------------------->
<h5><a class=ex href="#" title="Click to expand or collapse." id="RelatedtoWindows95Computers">Issues Specific to Windows 9<i>x</i> Computers</a></h5>
<div id="RelatedtoWindows95ComputersChild">
<blockquote>
<a href="#windows95registrysize">Windows 95 Registry Size: 64 KB Limitation May Cause A Warning During Visual Studio Installation</a></blockquote>
<blockquote>
<a href="#whenautologonisenabled">Disable Autologon Before Running Visual Studio 6.0 Setup</a></blockquote>
<blockquote>
<a href="#internetconnectiondialog">An Internet Connection Dialog Box May Appear at Startup of Windows or Other Applications</a></blockquote>
<blockquote>
<a href="#servercomponentsonwin95">Installing Server Components on Windows 95</a></blockquote>
<blockquote>
<a href="#iispatchforaspdebugging">For ASP Debugging on Windows 95/98 Computers, Install IIS Patch After Installing BackOffice</a> </blockquote>
<blockquote>
<a href="#resumingsetupafterinstallingpws">Installation Wizard May Not Restart After PWS Is Installed on Windows 95 Computers</a></blockquote>
<blockquote>
<a href="#frontpage98onwin95">Installing Microsoft FrontPage 98 Extensions on Some Windows 95 Computers</a></blockquote>
</div>
<p>
<!--------------------Section 5------------------------->
<h5><a class=ex href="#" title="Click to expand or collapse." id="RelatedtoOtherPrograms">Notes Impacting Other Installed Programs</a></h5>
<div id="RelatedtoOtherProgramsChild">
<blockquote>
<a href="#iisamexchangedriver">IISAM Exchange Driver Will Fail if Microsoft Exchange or Microsoft Outlook Is Not Already Installed</a> </blockquote>
</div>
<p>
<!-----------------------Section 6----------------------->
<h5><a class=ex href="#" title="Click to expand or collapse." id="ForComputerswithNonUSVersionsofMicrosoftPrograms">Issues Related to Computers with Non-U.S. Versions of Microsoft Programs</a></h5>
<div id="ForComputerswithNonUSVersionsofMicrosoftProgramsChild">
<blockquote>
<a href="#nonusnt40">Special Installation Instructions for Computers with Non-U.S. Versions of Microsoft Windows NT 4.0 and Microsoft Internet Explorer</a> </blockquote>
<blockquote>
<a href="#localizediespneededforenglishvs">BiDi Systems Must Have Localized Version of Internet Explorer 4.0 SP 1 Before English Visual Studio 6.0 Is Installed</a> </blockquote>
<blockquote>
<a href="#necpc98">NEC PC 98 Installation Issue</a></blockquote>
</div>
<!-----------------------SECTION 7-------------------->
<h5><a class=ex href="#" title="Click to expand or collapse." id="DASDK">Data Access SDK 2.0</a></h5>
<div id="DASDKChild">
<blockquote>
<a href="#installreq">Install Requirements</a></blockquote>
<blockquote>
<a href="#toinstallmdacsdk2">How to Install the Microsoft Data Access SDK 2.0</a></blockquote>
<blockquote>
<a href="#sql65orolderwithmdac2">Before Using SQL Server 6.5 or Older with MDAC 2.0
</a></blockquote>
<blockquote>
<a href="#ieinstallsoldmdacfiles">When Microsoft Internet Explorer Setup Installs Older Versions of MDAC Files</a> </blockquote>
</div>
<!------------------------->
<p>
<h5>To get information on general issues affecting the Visual Studio 6.0 suite, and you acquired the suite, go to the <a href="readmevs.htm" title="Jumps to the Visual Studio Readme (readmeVS.htm).">Microsoft® Visual Studio™</a> Readme.</h5></p>
<p>
<h5>For information on issues affecting the Enterprise Edition of Visual Studio 6.0, and you acquired this product, go to the <a href="readmeve.htm" title="Jumps to the VS Enterprise Edition Readme (readmeVE.htm).">Microsoft® Visual Studio™, Enterprise Edition</a> Readme.</h5></p>
<p>
<h5>For information on the Help system of the Visual Studio suite of products, go to <a href="readmeDN.htm" title="Jumps to readmeDN.htm">MSDN™, the Microsoft Developer Network</a> Readme.</h5></p>
<p>
<hr align=left color=black SIZE=1 width=640>
<!------------------------CONTENTS--------------------->
<!--SECTION 1-->
<h3>Installation Instructions for Visual Studio Programs</h3>
<p>This section lists installation-related information on programs and files shipped with Visual Studio 6.0.</p>
<!------------------------------------------------------>
<!--(Sec. 1) TOPIC 1-->
<h4><a name="releaseversionoverbeta">Installing Over Visual Studio Beta, Pre-Release, and Technical Preview Installations</a></h4>
<p>
Do not install the final release of Visual Studio 6.0 on computers that have pre-release, technical preview, or beta versions of any Visual Studio product. File copy targets and registration settings have evolved over the development cycle. Installing the final version on computers with a technology preview, pre-release, or other beta version can result in some final components not being installed, while the earlier beta version remain on the system. The outcome could be an unstable product or worse, an unstable system.</p>
<p>Reformat the hard disk and reinstall the operating system before returning a machine used as a beta test platform into the production environment.
</p>
<!------------------------------------------------------>
<!--(Sec. 1) TOPIC 2-->
<h4><a name="sidebysideinstallation">"Side by Side Installation": Installing Multiple Versions of Visual Studio 6.0 Products on the Same Computer</a></h4>
<p>
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.</p>
<p>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.</p>
<p>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:</p>
<ul><li>Users <b>installing different language versions</b> of the same product. For example, Japanese Visual Basic and English Visual Basic. Installation of certain combinations is supported.</li>
<p>
<table COLS=2 cellspacing="2" cellpadding="5" border="1" frame="below" rules="rows">
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2><b>Product</b></font></td>
<td><font face="verdana,arial,helvetica" SIZE=2><b>Supported Installation</b></font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Visual Basic</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Install to two different locations.</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Visual C++</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>No side-by-side installation is supported.</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Visual FoxPro</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Install to two different locations.</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Visual InterDev</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Install to the same location. You must reinstall after uninstalling one version.</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Visual J++</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Install to the same location. You must reinstall after uninstalling one version.</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Visual SourceSafe</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Install to the same location. You must reinstall after uninstalling one version.<p><b>Note</b> The UI language chosen when you run SourceSafe will be based on the system's language settings. If that language is not installed for SourceSafe, it will use English instead.</p></font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>MSDN</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Install to default directory.</font></td>
</tr>
</table>
<p>
<li>Users <b>installing different tiers of Visual Studio 6.0 products</b>. For example, Visual J++ Standard Edition and Visual InterDev Professional Edition. Installing different tiers of the same product on the same workstation is not supported.</li>
<p>
<li>Users <b>installing point releases</b>. Upgrading a later point release of Visual Studio over an earlier point release is supported. However, installing earlier versions over later versions is not supported.</li>
<p>
<li>Users <b>installing stand-alone versions of Visual Studio 6.0 products over the versions installed from Visual Studio 6.0 Professional or Enterprise</b>. For example, Visual FoxPro 6.0 over Visual Studio Professional 6.0. Installing a stand-alone version of the same language versions (English) of Visual Studio 6.0 products is supported. It is safe to install Visual FoxPro 6.0 (English) from the stand-alone version on a workstation that already has Visual Basic 6.0 installed from Visual Studio Professional Edition.</li>
</ul>
<!------------------------------------------------------>
<!--(Sec. 1) TOPIC 3-->
<h4><a name="installingondualbootcomputers">Warning When Installing on Dual-Boot Computers</a></h4>
<p>
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.</p>
<p>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.</p>
<p>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.</p>
<!------------------------------------------------------>
<!--(Sec. 1) TOPIC 4-->
<h4><a name="installationonsharedcddrive">Installing Visual Studio from a Shared CD Drive</a></h4>
<p>
If you are installing Visual Studio 6.0 from a shared compact disc drive, name the share with less than nine characters and with no embedded spaces in the name.</p>
<!------------------------------------------------------>
<!--(Sec. 1) TOPIC 5-->
<h4><a name="letiefinish">Let Microsoft Internet Explorer Setup Finish Before Proceeding with Visual Studio Installation</a></h4>
<p>
During Visual Studio setup, the Installation Wizard will install Internet Explorer 4.01 Service Pack (SP) 1. Near the end of the Internet Explorer setup, the Internet Explorer setup wizard will restart your computer. The Internet Explorer setup wizard will automatically restart and continue copying updated files and configuring your system.</p>
<p>On some computers, the Visual Studio Installation Wizard may also start while the Internet Explorer setup wizard is finishing this task. You must let the Internet Explorer setup wizard complete its processing before continuing with Visual Studio setup.</p>
<p>Specifically, it is vital that you do not continue with setup to the point of restarting the computer again. Restarting the computer during the final configuration phase of Internet Explorer will corrupt the Visual Studio setup. The Internet Explorer setup wizard shows progress indicators while in its final phase. When these progress indicators disappear, it is safe to proceed with the Visual Studio Installation Wizard.
</p>
<!------------------------------------------------------>
<!--(Sec. 1) TOPIC 6-->
<h4><a name="ieinstallsoldmdacfiles">When Microsoft Internet Explorer Setup Installs Older Versions of MDAC Files</a></h4>
<p>
The Microsoft Data Access (MDAC) files installed by Microsoft Internet Explorer 4.0 setup may be older than the MDAC files installed by Visual Studio 6.0 products. If you install Internet Explorer on a computer that already has Visual Studio 6.0, and you get a message asking you to confirm whether you want to install older versions of MDAC files, choose to keep the newer components currently on your computer.</p>
<!------------------------------------------------------>
<!--(Sec. 1) TOPIC 7-->
<h4><a name="webpublishingwizarddisc">When the Installation Wizard Looks for A Web Publishing Wizard Disc</a></h4>
<p>
When installing Visual Studio 6.0 or the Visual J++ Technology Preview 2, if you get a dialog box asking you to insert the Web Publishing Wizard disc, close the dialog box and proceed with the installation. </p>
<p>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++ on computers that have Temp directories set to removable drives, such as an Iomega Jaz drive.
</p>
<p>After your Visual Studio or Visual J++ installation is complete, if you want to install the Web Publishing Wizard, do the following:
</p>
<ol><li>Set your Temp environment variable to a directory on fixed media, such as your hard drive.</li>
<li>Run wpie15.exe from <i>[CD Drive:]</i> \setup of the compact disc.
</li>
<li>After Web Publishing Wizard setup is complete, reset your Temp environment variable directory to its previous directory, if necessary.</li>
</ol>
<!------------------------------------------------------>
<!--(Sec. 1) TOPIC 8-->
<h4><a name="installingclienttoolsafterinstallingvs">Installing Client Tools and Server Components After Visual Studio 6.0 Products Are Installed</a></h4>
<p>
The setup procedure is made up of several components. These components are not launched by <b>Add/Remove Programs</b> in the <b>Control Panel</b>. When you use <b>Add/Remove Programs</b>, you will only get to the portion of setup specific to the product installation.</p>
<p>To install any of the following tools, you must run the full setup.
</p>
<ul>
<li>Application Performance Explorer</li>
<li>Data Access Components 2.0</li>
<li>FrontPage 98</li>
<li>FrontPage 98 Server Extensions</li>
<li>InstallShield</li>
<li>NT Option Pack for Windows 95</li>
<li>Visual FoxPro Server Examples</li>
<li>Visual InterDev Server Components</li>
<li>Visual SourceSafe Server</li>
<li>Visual Studio Analyzer</li>
<li>MSDN</li>
</ul>
<p>To install any of the listed tools after you have installed any Visual Studio 6.0 products, run setup.exe from compact disc 1. This action will start the full setup in a "maintenance mode." You will have all of the options you had when you first installed the Visual Studio 6.0 product, but you will not have to go through all of the preliminary dialog boxes.
</p>
<!------------------------------------------------------>
<!--(Sec. 1) TOPIC 9-->
<h4><a name="howtocontacttechnicalsupport">How to Contact Technical Support</a></h4>
<p>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.</p>
<blockquote><b>Note</b> You must install MSDN to get the online documentation.</blockquote>
<p>You can look up support information on the Web at <a href="http://www.microsoft.com/support">http://www.microsoft.com/support</a>. In addition, you can call (425) 635-7012.
</p>
<hr align=left color=black SIZE=1 width=320>
<!------------->
<!--SECTION 2-->
<h3><a name="serversidesetups">Installing Server-Side Components</a></h3>
<p>This section lists installation issues identified for server-side components shipped with Visual Studio.</p>
<!------------------------------------------------------>
<!--(Sec. 2) TOPIC 1-->
<h4><a name="minimumreqsforserversideinstall">Minimum Requirements for Installation and Operation of Server-Side Components</a></h4>
<p>Consult the following table for information on operating system, browser, and other dependency requirements for installation and use of server-side components.</p>
<P><B>Table of Minimum Requirements for Installation of Server-Side Components</B></P>
<table cellspacing="1" cellpadding="5" border="1" rules="all" cols="6" frame="below">
<tr valign="top"></tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2><b>Component</b></font></td>
<td><font face="verdana,arial,helvetica" SIZE=2><b>NT Server</b></font></td>
<td><font face="verdana,arial,helvetica" SIZE=2><b>NT Workstation</b></font></td>
<td><font face="verdana,arial,helvetica" SIZE=2><b>Windows 95/98</b></font></td>
<td><font face="verdana,arial,helvetica" SIZE=2><b>Requires Microsoft Internet Explorer</b></font></td>
<td><font face="verdana,arial,helvetica" SIZE=2><b>Other Dependencies</b></font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Windows NT Option Pack 4.0</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Srvr.</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Workstation 4.0 SP3</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Limited on Win95</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2></font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>None</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>SQL Server 6.5 (DEV Edition)</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Srvr.</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Workstation 3.51 +</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Installs some tools on Windows 95</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>No</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>None</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>SQL Server Debugging Service</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Srvr. 3.51 Sp5 or better</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>---</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>---</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>No</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Needs SQL server 6.5 (SP3)</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Visual SourceSafe Server Components</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT4 Srvr.</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Workstation 4</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Windows 95</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Yes. Version 4 for viewing HTML Help</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>None</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Posting Acceptor (2.0)</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT4 Srvr.</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Workstation 4.0 SP3</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Windows 95</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>---</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Install NTOP before PA 2.0</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Remote Machine Debugging (Script Debugging)</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT4 Srvr.</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Workstation</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Windows 95</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Yes. Version 4 or later </font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>None</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Visual InterDev Server Components</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT4 Srvr.</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Workstation 4.0 SP3</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Windows 95</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Yes. Version 4 or later</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Install NTOP, MDAC, FP Extensions before VIDSS</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>FrontPage Server Extensions</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT4 Srvr.</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Workstation 4.0 SP3</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Windows 95</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Yes. Version 4 or later</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Install NTOP, MDAC before FP Extension</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Fox ISAPI Samples and Extensions</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>---</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NO OS dependencies (samples)</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>---</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Any generic browser</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>None</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Visual Studio Analyzer</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Yes</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Workstation 4.0 SP3</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Windows 95 (with DCOM update)</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Yes. Only on W95 to get DCOM</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>None</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>Application Performance Explorer</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT4 Srvr.</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Workstation 4.0 SP3</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Windows 95 (with DCOM update)</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Yes. Only on W95 to get DCOM</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>None</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>MDAC 2.0 Update</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT4 Srvr.</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Workstation 4.0</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Windows 95</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>No</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Install after NTOP and Before SNA</font></td>
</tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2>SNA server</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT4 Srvr.</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>NT Workstation 4.0</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>---</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>No</font></td>
<td><font face="verdana,arial,helvetica" SIZE=2>Install after MDAC and MTS</font></td>
</tr>
</table>
<!------------------------------------------------------>
<!--(Sec. 2) TOPIC 2-->
<h4><a name="setupalreadyrunning"></a>"Setup Already Running" Message Shows Up During Installation of Server-Side Components</h4>
<p>
When you install the Visual Studio 6.0 server-side components on a Windows NT server computer, using the Installation Wizard, you may encounter the message "Another copy of Setup is already running. Complete the other Setup or restart Windows."</p>
<p>
This situation typically occurs on slow computers where the Wizard timer runs out while waiting for an ACME setup to finish, and the Wizard starts the next setup.</p>
<p>Click <b>OK</b> in the message box. This action will tell the Wizard to terminate one of the conflicting processes and continue with the remaining installations. The summary page that is automatically generated at the end of setup will list the components, if any, that were not completely installed.</p>
<p>To install the specific component that failed, run setup wizard again.</p>
<!------------------------------------------------------>
<!--(Sec. 2) TOPIC 3-->
<h4><a name="servercomponentsonwin95"></a>Installing Server Components on Windows 95</h4>
<p><i>It is recommended that you install all server applications on computers running Windows NT.</i></p>
<p>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.</p>
<p> 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:
<ol><li>NT Option Pack</li>
<li>FrontPage 98 Server Extensions</li>
<li>Data Access Components 2.0</li>
<li>Visual InterDev Server Components</li>
<li>Application Performance Explorer</li>
<li>Visual Studio Analyzer</li>
</ol>
<ul><li>(Any Order) Visual SourceSafe Server</li>
<li>(Any Order) Visual FoxPro Server Samples</li>
</ul>
The Installation Wizard presents these options in the same order. Again, ordering is significant on Windows 95 only.
</p>
<p>For other issues relating to Windows 95 computers, go to <a href="#forwin95">Issues Specific to Windows 95 Computers</a></p>
<!------------------------------------------------------>
<!--(Sec. 2) TOPIC 4-->
<h4><a name="sqlandwinntop"></a>Known Compatibility Issues with SQL Server 6.5 and Windows NT Option Pack 4.0</h4>
<p>
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.</p>
<p>
If this happens, you will get an error message when you launch Microsoft Transaction Server (MTS). The message will instruct you to reinstall MTS.</p>
<p>To prevent this situation, install NT Option Pack after you install SQL Server.
<p>
<hr align=left color=black SIZE=1 width=320>
<!-------------------------------------------------------------->
<!--SECTION 3-->
<h3><a name="configuringdebugging">Configuring for Debugging</a></h3>
<p>Information in this section addresses issues on debugging and configuring computers for debugging services.</p>
<!------------------------------------------------------>
<!--(Sec. 3) TOPIC 1-->
<h4><a name="iispatchforaspdebugging">For ASP Debugging, Install IIS Patch After Installing BackOffice</a></h4>
<p>
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.</p>
<p>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.</p>
<p><b>To apply the IIS patch on Windows NT computers</b>
<ol>
<li>Run \IIS\WinNT\ASP2FIX1.exe from the installation disc.</li>
<p>
<table cellspacing="1" cellpadding="5" border="1" rules="all" frame="below">
<tr valign="top"></tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2><b>Product</b></font></td>
<td><font face="verdana,arial,helvetica" SIZE=2><b>Disc Location</b></font></td>
</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>
<li>Restart when prompted.</li>
</ol>
<p>
<p><b>To apply the IIS patch on Windows 9<i>x</i> computers</b>
<ol>
<li>Stop the Web server from the <b>Command Prompt</b>: Type <b>pws/stop</b> and press ENTER.</li>
<p>
<li>In the \<i><windows></i>\system\inetsrv directory, rename Asp.dll to Asp.old</li>
<p>
<li>From the \IIS\Win9<i>x</i>\ directory of the installation disc, copy Asp.dll and paste it to the \<i><windows></i>\system\inetsrv directory on your computer.</li>
<p>
<table cellspacing="1" cellpadding="5" border="1" rules="all" frame="below">
<tr valign="top"></tr>
<tr>
<td><font face="verdana,arial,helvetica" SIZE=2><b>Product</b></font></td>
<td><font face="verdana,arial,helvetica" SIZE=2><b>Disc Location</b></font></td>
</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> 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> 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 "autodial" or "autoconnect." You can turn off this behavior by setting the registry key EnableRemoteConnect to "N."
</p>
<p>To do this, create a text file "DisbleAutoConnect.reg" with exactly the following three lines:
</p>
<blockquote>REGEDIT4</blockquote>
<blockquote>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLE]</blockquote>
<blockquote>"EnableRemoteConnect"="N"</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, "EnableRemoteConnect.reg", with exactly the following 3 lines:
</p>
<blockquote>REGEDIT4</blockquote>
<blockquote>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLE]
</blockquote>
<blockquote>"EnableRemoteConnect"="Y"
</blockquote>
<p>Run "EnableAutoConnect.reg" to make the setting, and then run "DisbleAutoConnect.reg" 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/intlsp.asp</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>