How To Troubleshoot Visual Studio 6.0 Setup

Article translations Article translations
Article ID: 192392 - View products that this article applies to.
This article was previously published under Q192392
Expand all | Collapse all

SUMMARY

If you are experiencing difficulty when you set up the Visual Studio 6.0 components, there are some troubleshooting steps you can take to help identify and resolve problems. This article describes common troubleshooting steps that you can take.

MORE INFORMATION

  • Generate a log file during Setup. To do this, go to the Start menu and click Run. In the Run dialog box, type the following:
    <DRIVE>:\setup.exe /gc <PATH>\<FILENAME>
    where:

    <DRIVE> is the drive letter of the CD-ROM drive where the Visual Studio 6.0 setup CD is located.

    <PATH> is the path where you want the log file to be place (for example, C:\).

    <FILENAME> is the file name of the log you want Setup to generate (for example, vs6.log)

    Keep in mind that the file name must follow the 8.3 naming format, and that the path and file name are not in quotation marks.


  • If Setup fails, follow the steps in the ReadmeVI.htm for removing a previously installed beta version, even if a beta version was not installed. The registry entries and files are the same, so this step will help remove any partial setups of the released version.

  • Run setup and generate a log file as described in the first bullet, but deselect all of the components (select nothing). Setup might generate dialog boxes indicating that you are doing something expected, but it is OK. Let Setup run completely through.

  • After running the install described in the previous bullet (installing nothing), run Setup again (with a log file). Setup should start in maintenance mode that prompts you to re-install, add/remove components, or uninstall. When this dialog box appears, add one component at a time and test the installation after you install each component.

  • When you choose which components to install, start with components that are not related to the Internet and do not make any significant updates to system files. Avoid installing Visual J++, Visual Basic, Visual C++, and Visual InterDev. Start with Visual FoxPro or Visual SourceSafe. You can remove these programs later if you do not need them, but these programs change your system configuration the least.

  • If you are running setup multiple times it is a good idea to create a different log each time. For instance, start with vs6.log, then vs6_2.log, vs6_3.log, etc.

  • Another good troubleshooting step is to install the required system components first, before you run the Visual Studio 6.0 Setup. The main two components are Internet Explorer 4.0 Service Pack 1 and the Windows NT 4.0 Option Pack. The Windows NT 4.0 Option Pack is a dependency for many server components (see Install.htm), but if you do not plan to install any server components (such as the Visual InterDev Server Components) you do not need to install the Windows NT 4.0 Option Pack. It is recommended that you install these components from the Visual Studio 6.0 installation CDs.

    NOTE: This bullet does not apply to computers that are running Windows 2000.

Properties

Article ID: 192392 - Last Review: August 11, 2005 - Revision: 2.2
APPLIES TO
  • Microsoft Visual Studio 6.0 Enterprise Edition
  • Microsoft Visual InterDev 6.0 Standard Edition
  • Microsoft Visual C++ 6.0 Enterprise Edition
  • Microsoft Visual C++ 6.0 Professional Edition
  • Microsoft Visual C++, 32-bit Learning Edition 6.0
  • Microsoft Visual Basic 6.0 Learning Edition
  • Microsoft Visual Basic 6.0 Professional Edition
  • Microsoft Visual Basic 6.0 Enterprise Edition
  • Microsoft Visual J++ 6.0 Standard Edition
  • Microsoft Visual FoxPro 6.0 Professional Edition
  • Microsoft Visual SourceSafe 6.0 Standard Edition
Keywords: 
kbhowto kbvc600 kbvfp600 kbvisid600 kbvj600 kbssafe600 kbvs600 kbsetup kbgrpdsasp kbvbp600 KB192392

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com