Install Microsoft Visual Studio V6

  1. Go to the start button and selecting start | settings | Add/remove.
  2. Get the Visual Studio Enterprise DVD, disk 1. This is stored in the little white binder. Howver, there is a newer blue one (with the date January 2002) in the 2002 DVDs. This works better with Win2000.
  3. The wizard will want to know where the setup program is. In the latest DVD it is in directory \US\VS60EE\CD1. Note that there are other directories for others products like J++ that we'll install in the next step.
    1. It probably would not hurt to read the readme files.
    2. Somewhere in here it will give you the opportunity to specify the drive and directory where we want to install this stuff. The general rule of thumb is to leave the boot partition as empty as possible to accommodate those brain damaged devices and software that won't let you specify an installation directory. An example is our scanner and its software: it insists on using Drive C. Of course, on some machines where we have a single large partition this is not an issue.
    3. It then gives you a number of choices. Take the default of product. Come back later and install the other options.
      1. Accept the EULA agreement.
      2. Name = "Siegfried Heintze", company = SIGNITEK. 
      3. It comes back and asks where to install visual source safe (VSS). It says there is an old version in the WinOOP directory. I don't know how it ever got installed in WinOOP -- I definitely don't want it there.
      4. Specify these options
        1. Microsoft Visual Basic 6.0 (leave default of yes). It will prompt us to install the other stuff later.
        2. Developer studio (leave default of yes)
        3. VC++ runtime libraries
          1. In addition to the defaults, select CRT Source code if we have lots of disk space.
        4. VC++  MFC and Template Libraries
          1. MS Foundation Class Libraries
            1. Static libraries (yes unless we are short on disk space).
            2. Shared libraries (ALWAYS)
            3. Static libraries for Unicode (if we have gobs of  disk space, maybe. I'll probably never use them).
            4. Dynamic libraries for Unicode (if we have gobs of disk space, maybe. I'll probably never use them).
            5. Browser Database (yes, unless we are very short on disk space).
            6. Source code (yes, unless we are extremely short on disk space).
          2. MS Active Template libraries (yes)
        5. VC+ Build Tools (yes)
      5. Microsoft Visual Fox Pro (if we have gobs of disk space, yes. I've never used it).
      6. Microsoft Visual Interdev (ALWAYS)
        1. Client components (yes)
        2. Themes
          1. Base set (yes)
          2. Extended set (yes, if we have lots of disk space)
      7. Microsoft Visual Source Safe (yes -- I hope I learn how to use this some day).
      8. ActiveX (ALWAYS)
      9. Data Access
        1. ADO, RDS and OLE DB (ALWAYS)
        2. Micrsoft ODBC drivers
          1. MS SQL Server ODBC Driver (yes)
          2. Microsoft Oracle (yes)
          3. Microsoft Access (yes)
          4. Microsoft dBase (NO -- I don't have this product so I don't need a driver)
          5. Microsoft Excel (yes -- I have this as part of office -- I wonder if this driver also works for star office?)
          6. Microsoft FoxPro ODBC and Visual Foxpro (Only we are installing FoxPro too do we install these).
        3. Jet IISAM Drivers (Yes! I, might use these for tutorials).
          1. Jet IISAM Excel (yes)
          2. Jet IISAM Exchange (yes -- we can access our email as if it was a database).
          3. Jet IISAM Lotus 1-2-3 (no -- don't have that product)
          4. Jet IISAM Paradox (nope -- don't have it)
          5. Jet IISAM text (yes -- very useful for simplistic tutorials).
          6. Jet IISAM xbase Driver (nope -- I don't know what this is).
        4. Remote data objects and controls (ALWAYS)
        5. Data Environment (Yes. I wonder what this is? Its only 1MB).
      10. Enterprise tools (yes to all -- I need to learn what these are and how to use them)
        1. App Performance Explorer
        2. Repository (What is this?)
        3. Visual Component Mgr
        4. Visual Basic Enterprise Components
        5. VC++ Enterprise Tools 
        6. Microsoft Visual Modeler (this is an interesting diagramming tool for diagramming databases).
        7. Visual Studio Analyzer
      11. Graphics (yes to all, unless we are short on disk space).
      12. Tools
        1. API text viewer (yes -- could be handy)
        2. MFC Trace facility (yes -- I used it once a long time ago and might use it again.)
        3. Spy ++ (yes -- used for teaching)
        4. Win32 SDK tools (yes -- I wonder what these are.)
        5. OLE/COM object viewer (ALWAYS)
        6. Set installing EXE redistributable file (yes unless we are short  on disks space. I don't know what this is, but it looks very interesting and I should learn about it).
        7. ActiveX Control Test Control (ALWAYS -- I need this for teaching COM)
      13. Check register environment variables! Then I can work from the command line.
      14. We don't have any files of the old VSS database format. So if it asks whether to use the new format or the old, select new. Start at 12:05. End at 12:19.
    4. Now it says "Setup has installed an icon in the MS VC++ 6 Tools program group, that will allow you to install a subset of the Windows NT system symbols (.DBG) files from your VC++ CD-ROM. If the symbols are not installed the VC++ debugger is not always able to determine the context of called functions. For further application debugger, it is strongly recommended that you install these files. See Readme for more information." Be sure to do this! 
    5. Click OK at 12:22. Restart Windows at 12:25. Oh - great, windows explorer was hung. Kill it.
    6. Remember to be quick on dual booting machines or the might boot linux instead.
    7. Skip this step. The .dbg files are for NT 4 and not Win2000. 

      Now that we are rebooted (this takes forever at 12:25 I press ctrl-alt-del to login and am ready at 12:28), go back and install those debugging programs (that we read about a moment ago) by clicking the start menu. Hmm... I click on MS Visual Studio 6 Tools and I see Windows NT Symbols Setup. Click it!, Alternatively you can run c:\program files\Microsoft Visual Studio\Common\MSDEV98\Bin

      1. Select OK and leave the DVD in the slot. It does not work so you have to run c:\WinNT\explorer.exe and find it on the DVD at D:\US\VS60EE\CD1\VC98\DEBUG. 
      2. Now it says some of the symbol files cannot be located, do you want to continue. I guess so.
      3. Click typical unless we are really short on disk space. You only save 2MB on V6 by using minimal.
      4. Now it says "the version of USER32.DBG (and many others) does not match the corresponding dll on my machine. Do you want to copy it?" I think so (could it hurt?). 12:57.
      5. I copied them all and none match. This is probably because these files are for NT and not Win2000.
    8. Now the MSDN installation pops up. Install this later when we have the right CD.
    9. Now it comes back and wants to install "Other client tools". 
      1. There is only one option so I click the "install" button at 13:06. Wow, that fancy logo stick around a long time while the disk drive lights flash until 13:08.
      2. Now I click the "next" button.
      3. Click yes to agree to the EULA agreement.
      4. The user information already defaults to Siegfried Heintze and SIGNITEK.
      5. Install in the default location of c:\program files unless we are short on disk space on drive C.
      6. Click typical unless we are short on disk space.
      7. Click Next to add shortcuts at 13:11.
      8. Click finish and now it comes back to install "Other Client tools." Click "Next" and it gives us the following stuff to install. (does this ever end?) On Angel where we have lots of disk space, install everything (I guess).
        1. (Skip this one -- it installs a bunch of stuff for NT that was already installed on the Advanced Server). 

          Launch BackOffice Installation Wizard

          1. It comes back and wants the CD. I type d:\us\vs60ee\cd2 (the default was incorrect).
          2. Now we get a little display called Back Office Business Solutions. The default is complete. Click "Next"
          3. The following products will be installed:
            1. Windows NT Option Pack (I hope not)
            2. Hey, this stuff is already installed. Abandon this for Win2000 Advanced server. Continue for NT4 or other versions of Win2000 that have not previously installed this stuff.
        2. Visual Source Safe Server
          1. Server setup. Click continue.
          2. Write down the product ID somewhere.
          3. Select the default directory in C:\program files unless we are running short on the C partition (if so, install it on the D partition).
          4. Click the large button to install the server which "Creates a SHARED database (except when upgrading), and installs the Admin software plus the NetSetup program so users can install from the server. If you've installed the VSS6 Client, you can upgrade its db to shared". Remember to do that.
          5. Now it wants to restart again! OK, restart at 13:25. Remember to be fast with those dual boot systems and type "nt" into Lilo when it prompts for only a second.
        3. SNA Server (Skip this).

          What is this? I think it's IBM's System Network Architecture. I don't work with IBM main frames.

    10. Update environment variables with these values.

      This section has been moved.

    11. Install Visual J++
      1. Use the start button, select setup and Add/Remove programs. Click on CD or Floppy. 
      2. Specify D:\US\VS60EE\VJ60\SETUP.EXE (assuming drive D is the CDROM/DVD drive).
      3. Scroll thru the first portion of the readme file. On this one it warns about installing on top of prevoius installation. Take appropriate action (like removing the previous installation before proceeding).
      4. Accept the EULA agreement.
      5. It asks what we want to install. Take the default of Visual J++ 6 (or a later version, of course).
        1. Install Visual J++ 6. Click next.
          1. Click continue.
          2. Write down the product ID.
          3. Use the default folder of c:\program files\Microsoft Visual Studio\VJ98 unless we have a multiply partitioned system in which case select some other partition.
          4. Select custom
            1. Microsoft Visual J++
              1. MSVJ++ core files (yes -- default)
              2. Java Class library source code (always -- its only 1K)
              3. Project templates (yes -- default)
              4. Self-installing EXE redistributable files (yes, default)
            2. Data Access (see the options for Visual Studio)
            3. Graphics (select all if we have gobs of disk space. I'm not likely to use it -- but it might be nice to play with it and know its available).
            4. Professional Tools (yes -- all)
            5. Tools (yes - all) time = 14:55
          5. Restart windows again. time = 14:59. 
          6. After rebooting It will want to install MSDN, Cancel it.
        2. Now install server applications by running the same setup program we ran previously to install VJ++. Click default of Visual j++ which includes
          1. MS Data Access Components
          2. Remote machine debugging
          3. Front Page Server Extensions
          4. Posting Acceptor (2.0)
          5. Visual J++ Server
    12. Install MSDN. These DVD disks come about every three months, be sure to get the latest one. For some strange reason, it comes in a separate little opaque black case instead of a regular jewel case for CDs. If you are installing from CD's, the MSDN come in a jewel case that holds 3 or 4 disks.
      1. For MSDN library setup, select FULL for notebook computers that have a lot of space so we don't have to have the disks with us. For others, click Typical.
      2. Sure, put a short cut. Now it will take while. 
  4. Install the back office servers for Visual Interdev and Remote Machine debugging. This only applies for NT4 on the old disks. You should have already installed the server components if you are running that January 2002 blue DVD installation. The BackOffice installation won't run on Win2000.
    1. Hilight "launch back office installation wizard" and click the install button.
    2. We have no need for Foxpro.
    3. It would not let me install the SQL server stuff.
  5. Skip the installation of the Soap Toolkit for Visual Studio 6 at http://msdn.microsoft.com/net/default.asp#aspplus bye downloading directly from SOAP Toolkit for Visual Studio 6.0. This product stinks and no one knows how to use it.
  6. Install ActiveX Control Pad.

    Back to Win2000 Installation.

     
  7. Turn on Debugging for Visual Interdev
 

 

Send mail to webmaster@SIGNITEK.com with questions or comments about this web site.