Microsoft KB Archive/287453

= Best practice installation methods for Visual Studio 6.0 =

Article ID: 287453

Article Last Modified on 8/14/2007

-

APPLIES TO


 * Microsoft Visual Studio 6.0 Enterprise Edition
 * Microsoft Visual Basic 6.0 Professional Edition
 * Microsoft Visual Basic 6.0 Learning Edition
 * Microsoft Visual C++ 6.0 Enterprise Edition
 * Microsoft Visual C++ 6.0 Professional Edition
 * Microsoft Visual C++ 6.0 Standard Edition
 * Microsoft Visual FoxPro 6.0 Professional Edition
 * Microsoft Visual InterDev 6.0 Standard Edition
 * Microsoft Visual J++ 6.0 Standard Edition
 * Microsoft Visual SourceSafe 6.0 Standard Edition
 * MSDN 2003 Universal Edition

-



This article was previously published under Q287453





For a Microsoft Visual Studio .NET version of this article, see 319714.



SUMMARY
Many setup and installation problems can be avoided by using best practice installation methods. While these steps may not address specific problems or error messages, they significantly reduce the possibility of problems that can occur while installing products made by Microsoft or other software suppliers. Past success without using these methods is no guarantee of future success. These best practice methods are recommended for all installations, including service packs as well as non-Microsoft products. While these best practice methods might not be necessary in all cases, they reduce the potential for problems.



Windows 95, Windows 98, or Windows Millennium Edition (Me) operating system:
For more information on best practices for installing a product on the Windows 95, Windows 98, or Windows Me operating system, review the Readme file(s) that are included with the product.  Clear the system temporary folder (C:\Windows\Temp). Stop all applications, particularly monitoring programs such as anti-virus programs. To do this, follow these steps:  Press CTRL+ALT+DEL to open the Close Program dialog box. Select each application in turn and click End Task (with the exception of Explorer, which is the shell for Windows). </ol>

NOTE: Windows Me has a System Restore feature, which returns the system to its pre-installation state if you establish a restore point prior to an installation. To establish a restore point, follow these steps:
 * 1) On the Start menu, point to Programs, point to Accessories, point to System Tools, and then click System Restore.
 * 2) Select Create a restore point and follow the prompts to create a restore point.

If you need to return the system to its pre-installation state, follow these steps:
 * 1) On the Start menu, point to Programs, point to Accessories, point to System Tools, and then click System Restore.
 * 2) Select Restore my computer to an earlier time and follow the prompts.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

267952 Description of PCHealth in Windows Millennium Edition (Me)

Windows NT 4.0 or Windows 2000 operating system:
For more information on best practices for installing a product on the Windows NT 4.0 or Windows 2000 operating system, review the Readme file(s) that are included with the product.
 * 1) Log on using the Local Administrator account (the default is Administrator). The domain that is selected must match the computer name.

NOTE: The Local Administrator account is not the same as a user account that has administrator rights. The Local Administrator account is the system account that is used to set up the operating system.
 * 1) Clear the system temporary folder.

For Windows NT 4.0, this folder is :\Temp.

For Windows 2000, this folder is usually :\Documents and Settings\<%userprofile%>\Local Settings\Temp, but it may be :\Winnt\Profiles\<%userprofile>\Local Settings\Temp.
 * 1) Stop all unneeded services, particularly monitoring and anti-virus programs.

Additional Steps
Most installations will be successful if you use just the best practice methods; however, on rare instances, additional steps may be required. If you encounter problems that are due to previous program installations or system drivers that are interacting with the installation process, see the Microsoft Knowledge Base articles that are listed in the &quot;References&quot; section.

<div class="references_section">