Java 2 Standard Edition, Developer Bundle Installation Notes

Installation Instructions | Troubleshooting

In this procedure, you will run the self-installing executable to unpack and install the Java 2 SDK, Standard Edition, v1.3 and Forte for Java, Community Edition, v1.0.

The installation procedure has the following steps:

1. If necessary, concatenate the downloaded pieces together 
2. Check the download file size
3. Run the installer
4. Delete the downloaded file(s)
5. Update the PATH variable
6. Check the CLASSPATH variable
7. Where Do I Go From Here?
8. Uninstalling the Java 2 SDK and Forte for Java

If you have any difficulties, check the Troubleshooting section below or use this link to report an installation problem.

1. If necessary, concatenate the downloaded pieces together 

If you have downloaded the software in pieces
instead of a single bundle, do this step:

Steps to concatenate the disk size pieces together (below)

The final size should be the same as that given in the next step.

2. Check the download file size

If you saved the self-installing executable to disk without running it from the download page at the Java Software web site, or if you concatenated it from pieces in the previous step, check to see that you have the complete file:

j2sdk1_3_0-forte1_0-win.exe       42,596,461 bytes

3. Run the installer

The file j2sdk1_3_0-forte1_0-win.exe is installer. If you downloaded it instead of running it directly from the web site, double-click on the installer's icon. Then follow the instructions the installer provides. The installer will guide you first through installation of the Java 2 SDK.

Note: You cannot install Forte for Java over an existing Forte installation. You will need to first remove the existing installation or install this Forte for Java product in a different location.

Following that, you will be guided through the installation of the Forte for Java, Community Edition. At the end of the process, the Java 2 Runtime Environment will be installed. When the installation is complete, you can delete the download file to recover disk space.

Note: If you manually cancel out of the installation of Forte for Java before the installation finishes, the installer may nevertheless display a message saying that the "Forte setup was successful." In such a situation, the message is not correct and is caused by a bug in the installer.

If you already installed the documentation bundle, you should install the SDK in the same directory in which you installed the documentation. For example, if your documentation is installed at c:\jdk1.3\docs, make sure you install the Java 2 SDK at c:\jdk1.3. This will create the directory structure shown below. This step ensures that all of the SDK documentation's HTML links work properly.

Installed Directory Tree
After installing both the SDK software and documentation, the SDK directory will have the structure shown below. The docs directory is created when you install the SDK documentation bundle.

jdk1.3 ____________________|_______________________ | | | | | | | | | | | | | | | bin lib | | demo | docs | | | LICENSE | | | | jre | | COPYRIGHT | | __|__ | README | include | | README.html include-old bin lib

4. Delete the downloaded file(s) (Optional)

If you want to recover disk space, delete the file (or files) you downloaded.

5. Update the PATH variable

You can run the Java 2 SDK without setting the PATH variable, or you can optionally set it as a convenience.

Should I set the PATH variable?
Set the PATH variable if you want to be able to conveniently run the SDK executables (javac.exe, java.exe, javadoc.exe, etc.) from any directory without having to type the full path of the command. If you don't set the PATH variable, you need to specify the full path to the executable every time you run it, such as:

    C:> \jdk1.3\bin\javac MyClass.java

It's useful to set the PATH permanently so it will persist after rebooting.

How do I set the PATH permanently?
To set the PATH permanently, add the full path of the jdk1.3\bin directory to the PATH variable. Typically this full path looks something like C:\jdk1.3\bin. Set the PATH as follows, according to whether you are on Windows NT or Windows 95/98/2000.

Windows NT and Windows 2000 - To set the PATH permanently:

1. Start the Control Panel, select System, select Environment, and look for "Path" in the User Variables and System Variables. If you're not sure where to add the path, add it to the right end of the "Path" in the User Variables. A typical value for PATH is:

        C:\jdk1.3\bin 
   

   Capitalization doesn't matter. Click "Set", "OK" or "Apply".

   The PATH can be a series of directories separated by semi-colons (;). Microsoft Windows looks for programs in the PATH directories in order, from left to right. You should only have one bin directory for a Java SDK in the path at a time (those following the first are ignored), so if one is already present, you can update it to jdk1.3.

2. The new path takes effect in each new Command Prompt window you open after setting the PATH variable.

Windows 98, Windows 95 - To set the PATH permanently, open the AUTOEXEC.BAT file and add or change the PATH statement as follows:

1. Start the system editor. Choose "Start", "Run" and enter sysedit, then click OK. The system editor starts up with several windows showing. Go to the window that is displaying AUTOEXEC.BAT.

2. Look for the PATH statement. (If you don't have one, add one.) If you're not sure where to add the path, add it to the right end of the PATH. For example, in the following PATH statement, we have added the bin directory at the right end:

   PATH C:\WINDOWS;C:\WINDOWS\COMMAND;C:\JDK1.3\BIN 
   

   Capitalization doesn't matter. The PATH can be a series of directories separated by semi-colons (;). Microsoft Windows searches for programs in the PATH directories in order, from left to right. You should only have one bin directory for a Java SDK in the path at a time (those following the first are ignored), so if one is already present, you can update it to jdk1.3.

3. To make the path take effect in the current Command Prompt window, execute the following:

         C:> c:\autoexec.bat
   

   To find out the current value of your PATH, to see if it took effect, at the command prompt, type:

         C:> path
   

The CLASSPATH variable is one way to tell applications written in the Java programming language (including the SDK tools) where to look for user classes. (The -classpath command-line switch is the preferred way.) If your machine does not have the CLASSPATH variable set, you can ignore the rest of this step. To check this, run the set command from the DOS prompt:

  C:> set

If CLASSPATH does not appear in the list of settings, it is not set. If your CLASSPATH variable is set to some value, you may want to clean up your CLASSPATH settings, so read on.

Should I modify the CLASSPATH variable?
The Java 2 SDK will work even if CLASSPATH is set for an earlier version of the SDK software, as long as it contains the current directory ".". However, if your CLASSPATH contains classes.zip (which was only in JDK 1.0.x and JDK 1.1.x), and you don't plan to continue using those earlier versions, you can remove that setting from the CLASSPATH now. In any case, if CLASSPATH is set, it should include the current directory -- this makes it possible to compile and then run classes in the current directory.

How do I modify the CLASSPATH?
Use the same procedure you used for the PATH variable in the previous step and either:

• Remove the CLASSPATH environment variable entirely.
  With Java 2 SDK, the default value is ".", the current directory. To include any user classes, use the -classpath command line switch instead with java, javac, javadoc and other tools. This is the recommended approach because it doesn't force one CLASSPATH for all applications.
  -OR-
• If you have applications that require CLASSPATH be set, keep those required user classes in CLASSPATH and include the current directory "." If you're no longer using JDK 1.1.x, remove classes.zip.

For more information, see Setting the class path.

7. Where Do I Go From Here?

At this point, you will probably want to install the SDK documentation bundle, if you have not already done so. You can get the SDK documentation bundle from the documentation download page.

You can also go to:

• README -- For a general introduction to the Java 2 SDK
• Hello World application and Hello World applet -- To write and compile a simple class, guided by the Java Tutorial.
• Documentation for the SDK tools -- For descriptions of the SDK tools you used in the previous step to test the installation, as well as the other SDK tools. This version is on the web site. After you install the documentation bundle, the same document is available at jdk1.3\docs\tooldocs\tools.html.
• Java 2 SDK Documentation -- For a guide to the Java 2 SDK documents. This version is on the web site. After you install the documentation bundle, the same document is available at jdk1.3\docs\index.html.
• Java Plug-in website -- If you installed this plug-in, both Internet Explorer and Netscape Navigator will use this plug-in when encountering HTML pages with special <OBJECT> and <EMBED> tags that invoke it. For details on how to configure your HTML pages, click the Java Plug-in link above, then click "Documentation" and "Java Plug-In HTML Specification".

8. Uninstalling the Java 2 SDK and Forte for Java

If you should ever want to uninstall the Java 2 SDK, go to the Start menu and select Settings, then select Control Panel. In the Control Panel, open the Add/Remove Programs utility. You will be presented with a list of software that you can uninstall. Simply choose the Java 2 SDK or Forte for Java product from the list and click the "Add/Remove..." button.

Note for Windows 2000 users: The Forte for Java product will not have an entry in the Add/Remove Programs list on Windows 2000. The files for the Forte for Java product must be deleted manually on Windows 2000.

This procedure requires having enough disk space for all the individual pieces plus an equal amount for the resulting self-extracting archive.

After you download all the files:

Note: On Windows 95/98, this command is too long to execute at the DOS Prompt. You should instead create a batch file, say jdk.bat and copy this command into it. Then execute jdk.bat to connect the pieces.

• Execute the following command to "copy" each of the pieces into a single file. (You might need to copy this command into a batch file to make the line fit and run it or rename the pieces into very short names, for example C:\> copy /b 1+2+3+...+31 j2sdk1_3_0-forte1_0-win.exe )

  C:\> copy /b j2sdk1_3_0-forte1_0-win-aa.exe + j2sdk1_3_0-forte1_0-win-ab.exe + j2sdk1_3_0-forte1_0-win-ac.exe + j2sdk1_3_0-forte1_0-win-ad.exe + j2sdk1_3_0-forte1_0-win-ae.exe + j2sdk1_3_0-forte1_0-win-af.exe + j2sdk1_3_0-forte1_0-win-ag.exe + j2sdk1_3_0-forte1_0-win-ah.exe + j2sdk1_3_0-forte1_0-win-ai.exe + j2sdk1_3_0-forte1_0-win-aj.exe + j2sdk1_3_0-forte1_0-win-ak.exe + j2sdk1_3_0-forte1_0-win-al.exe + j2sdk1_3_0-forte1_0-win-am.exe + j2sdk1_3_0-forte1_0-win-an.exe + j2sdk1_3_0-forte1_0-win-ao.exe + j2sdk1_3_0-forte1_0-win-ap.exe + j2sdk1_3_0-forte1_0-win-aq.exe + j2sdk1_3_0-forte1_0-win-ar.exe + j2sdk1_3_0-forte1_0-win-as.exe + j2sdk1_3_0-forte1_0-win-at.exe + j2sdk1_3_0-forte1_0-win-au.exe + j2sdk1_3_0-forte1_0-win-av.exe + j2sdk1_3_0-forte1_0-win-aw.exe + j2sdk1_3_0-forte1_0-win-ax.exe + j2sdk1_3_0-forte1_0-win-ay.exe + j2sdk1_3_0-forte1_0-win-az.exe + j2sdk1_3_0-forte1_0-win-ba.exe + j2sdk1_3_0-forte1_0-win-bb.exe + j2sdk1_3_0-forte1_0-win-bc.exe + j2sdk1_3_0-forte1_0-win-bd.exe + j2sdk1_3_0-forte1_0-win-be.exe j2sdk1_3_0-forte1_0-win.exe

  
  

  The resulting file is a self-extracting InstallShield setup program. Check that its size is the same as is given in the next step.

• Then, run the InstallShield setup program by double-clicking on its icon, or by executing the following command:

  C:\> j2sdk1_3_0-forte1_0-win.exe
  

Below are some tips for working around problems that are sometimes seen during or following an installation of the Java 2 SDK. For more troubleshooting information, see the Java FAQ.

• If you see the following error message on Windows 2000

     config.nt. The system file is not suitable for running MS-DOS 
     and Microsoft Windows Applications.
  

  it indicates a problem with the %SystemRoot%\System32\COMMAND.COM file that has been seen on some installations of Windows 2000. If you encounter this error message when you try to launch the installer, consult the Microsoft web site at

     http://support.microsoft.com/support/kb/articles/Q142/2/71.asp
  

  for information about resolving the problem.

• If you see the following error message

     corrupt cabinet file
  

  then the file you have downloaded is corrupted. (A cabinet file contains compressed application, data, resource and DLL files.) Check its file size against the expected file size listed in these instructions. If they don't match, try downloading the bundle again. Remember, if you have downloaded the disk-size pieces, you need to concatenate the pieces together before running the InstallShield setup program.

• If you see the following error message

     net.socketException: errno = 10047
  

  -or-

     Unsupported version of Windows Socket API
  

  check which TCP/IP drivers you have installed. The AppletViewer supports only the Microsoft TCP/IP drivers included with Windows 95. If you are using third-party drivers (e.g., Trumpet Winsock), you'll need to change over to the native Microsoft TCP/IP drivers if you want to load applets over the network.

• If you see the following error message

     System Error during Decompression
  

  then you might not have enough space on the disk that contains your TEMP directory.

• If you see the following error message

     This program cannot be run in DOS mode.
  

  then do the following:
  1. Open the MS-DOS shell (Windows/Start/Programs/MS-DOS Prompt)
     
  2. Right-click on the title bar
     
  3. Select Properties
  4. Choose the Program tab
  5. Push the Advanced button
  6. Make sure the item "Prevent MS-DOS-based programs from detecting Windows" is unchecked
  7. Select OK
  8. Select OK again
  9. Exit the MS-DOS shell
  10. Restart your computer.

• If the AppletViewer does not load applets
  then you might try the following:
  1. set HOMEDRIVE=c:
     set HOMEPATH=\
     and restart the AppletViewer (in the same Command Prompt window)
  2. set HOME=c:\
     and restart the AppletViewer (in the same Command Prompt window)

  If none of these work, try:

      java -verbose sun.applet.AppletViewer
  

  This lists the classes that are being loaded. From this output, you can determine which class the AppletViewer is trying to load and where it's trying to load it from. Check to make sure that the class exists and is not corrupted in some way.

• Appletviewer locks up
  This happens with NT Workstation 4.0, update 3, where the DISPLAY is configured for "true color". The appletviewer (and perhaps other entities) will lock up by running and then freezing the system consuming 100% CPU.
  To "test" this run the "java -verbose sun.applet.AppletView" and notice that it locks up when it tries to run the MTookit.class.
• Winsock Issues
  The Java 2 SDK does not include Microsoft Winsock 2.0. It is extremely likely that your system already has Winsock 2.0. Windows NT 4.0, Windows 2000, and Windows 98 come with Winsock 2.0. Windows 95 comes with Winsock 1.1 or 1.2, but most Windows 95 systems have been upgraded to Winsock 2.0 by now.

  To check which version of Winsock you have, search for "winsock.dll". Then choose "Properties" from the File menu and click the Version tab.

  Microsoft provides a free software bundle, the Microsoft Windows Sockets 2.0 Software Development Kit, that includes Winsock 2.0. Even if you don't need to upgrade your own system, you may want to obtain this kit so you can deploy network applications on Windows 95 systems. For more information, see the Java 2 Runtime Environment README.

To report a bug or to request a feature for the Java 2 SDK, please checkout http://java.sun.com/cgi-bin/bugreport.cgi.

To submit comments or suggestions about the Java 2 SDK, please send mail to the most appropriate engineering team from the list at Java Software email addresses.