Print-friendly Version

Installation Notes

Java 2 SDK, Standard Edition, Version 1.3.0
for Microsoft Windows 95 / 98 / 2000 / NT 4.0 / ME
(Intel Platform)

Installation Instructions | Troubleshooting

In this procedure, you will run the self-installing executable to unpack and install the Java 2 SDK software bundle.

Note: After the Java 2 SDK software has been installed in step 2, you will be asked to reboot your system, which completes the registry modifications needed to deinstall the SDK later. To continue using these instructions after rebooting, either use your web browser to print these instructions now or use your browser's history function to get back to this page and then continue with step 3.

The installation procedure has the following steps:

1. Check the download file size
2. Run the SDK installer, if not already run
3. Delete the downloaded file(s) (Optional)
4. Update the PATH variable
5. Check the CLASSPATH variable
6. Start using the SDK tools!
7. Where Do I Go From Here?
8. Uninstalling the Java 2 SDK

If you have any difficulties, see the Troubleshooting section at the end of this document or use this link to report an installation problem.

       <version number>

      j2sdk-1_3_0_<version number>-win.exe 

      j2sdk-1_3_0_03-win.exe 

Before you download a file, notice that its byte size is provided on the download page. Once the download has completed, check that you have downloaded the full, uncorrupted software file.

2. Run the SDK installer, if not already run

The file j2sdk-1_3_0_<version number>-win.exe is the SDK installer. If you downloaded it instead of running it directly from the web site, double-click on the installer's icon in whatever directory you've installed it on your computer. Then follow the instructions the installer provides. When done with the installation, you can delete the download file to recover disk space.

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.0_<version number> ____________________|___________________ | | | | | | | | | | | | | | bin lib | | demo | | | | LICENSE | | | | jre | | COPYRIGHT | | __|__ | README | include | | README.html include-old bin lib

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

You can run the Java 2 SDK just fine 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.0_<version number>\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.0_<version number>\bin directory to the PATH variable. Typically this full path looks something like C:\jdk1.3.0_<version number>\bin. Set the PATH as follows, according to whether you are on Windows NT or Windows 95/98/2000/ME.

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

1. Choose Settings, Control Panel, and select System. On Windows NT, select the Environment tab; on Windows 2000 select the Advanced tab. 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.0_<version number>\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.0_<version number>.

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.0_<version number>\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.0_<version number>.

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
   

Windows ME - To set the PATH permanently:

From the start menu, choose programs, accessories, system tools, and system information. This brings up a window titled "Microsoft Help and Support". From here, choose the tools menu, then select the system configuration utility. Click the environment tab, select PATH and press the edit button. Now add the SDK to your path as described in step b above. After you've added the location of the SDK to your PATH, save the changes and reboot your machine when prompted.

5. Check the CLASSPATH variable

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 fine 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.

6. Start using the SDK tools!

Your computer system should now be ready to use the Java 2 SDK. In this step, you'll run some simple commands to make sure it is working properly.

You start the compiler, interpreter, or other tool by typing its name into the Command Prompt window, generally with a filename as an argument. The SDK development tools need to be run from the command line and have no GUI interfaces (except AppletViewer). Double-clicking a tool's file icon, such as java.exe, will not do anything useful. To get started, open the DOS Prompt window (on 95 or 98) or Command Prompt window (on NT or 2000) if you haven't already done so.

You can specify the path to a tool either by typing the path in front of the tool each time, or by adding the path to the system as in the previous step. The following assumes the SDK is installed at C:\jdk1.3.0_<version number> and you have set the path variable. (If you have not, add "C:\jdk1.3.0_<version number>\bin" ahead of the javac and appletviewer commands.)

Compiling a Java class - You use the Java bytecode compiler, javac.exe, to compile applications and applets that you write. Suppose, for example, that you have written an application in a file named MyApp.java. To run the compiler on your file, go to the prompt window and execute this:

       C:> javac MyApp.java

See the next section for a link to the Hello World examples.

Running Applets - You can run applets in AppletViewer. Here's an example:

• Use cd to change to the TicTacToe directory that contains the html file example1.html that embeds an applet:
  

  C:> cd \jdk1.3.0_<version number>\demo\applets\TicTacToe
  

• Run AppletViewer with the html file:

  C:> appletviewer example1.html
  

  This example lets you interactively play Tic-Tac-Toe.

Refer to the Troubleshooting section below if you have problems running the SDK.

At this point, you will probably want to install the documenation bundle, if you have not already done so. Although you can use the SDK tools without installing the documentation, it makes sense to do so if you are going to do any extensive work. You can get the SDK documentation bundle from the 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. See also the Java Plug-in enhancements documenation for information about new Java Plug-in features in J2SE 1.3.0.
• 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

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 from the list and click the "Add/Remove..." button.

Below are some tips for working around problems that are sometimes seen during or following an installation. 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 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 on the download page. If they don't match, try downloading the bundle again.

• 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.

• Creating Source Files in Notepad - In Microsoft Windows, when you create a new file in Microsoft Notepad and then save it for the first time, Notepad normally adds the .txt extension to the filename. Therefore, a file you name Test.java is saved as Test.java.txt. It's important to note that you cannot see the .txt extension unless you turn on the viewing of file extensions (in Windows Explorer, uncheck "Hide file extensions for known file types" under Folder Options). To prevent the .txt extension, enclose the filename in quotation marks, such as "Test.java", when typing it into the Save As dialog box.

  On the other hand, Microsoft WordPad does not add a file extension if you provide one -- you must save the file as "Text Document".