Java 2 SDK, Standard Edition, Installation Notes

System Requirements

The Java 2 SDK is intended for use on Microsoft Windows 95, 98 (1st or 2nd edition), NT 4.0 with Service Pack 5, ME, XP Home, XP Professional, 2000 Professional, 2000 Server, or 2000 Advanced Server operating systems running on Intel hardware. In non-English locales, the only edition of Microsoft Windows 2000 tested with this release is the Professional edition.

A Pentium 166MHz or faster processor with at least 32 megabytes of physical RAM is required to run graphically based applications. Forty-eight megabytes of RAM is recommended for applets running within a browser using the Java Plug-in product. Running with less memory may cause disk swapping which has a severe effect on performance. Very large programs may require more RAM for adequate performance.

You should have 70 megabytes of free disk space before attempting to install the Java 2 SDK software.

Installation Instructions

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, you may be asked to reboot your system. To continue using these instructions after rebooting, either print them now or use your Web browser's history function to get back to this page.

If you have any difficulties, see the Troubleshooting section at the end of this document.

Note: For any lines on this page containing the following notation, you must substitute the appropriate update version number for the notation.

<version number>

For example, if you are downloading the installer for update 1.4.0_01, the following file name:

j2sdk-1_4_0_<version number>-windows-i586.exe

would become:

j2sdk-1_4_0_01-windows-i586.exe

1. Check the download file size

If you save the self-installing executable to disk without running it from the download page at the Java Software web site, 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. Uninstall any Prior Version of the Java 2 SDK

If you have previously installed another version of the Java 2 SDK, uninstall it. Use the Microsoft Windows Add/Remove Programs utility, accessible from the Control Panel (Start --> Settings --> Control Panel).

3. Run the Java 2 SDK installer

Note -- you must have administrative permissions in order to install the Java 2 SDK on Microsoft Windows 2000 and XP.

The file j2sdk-1_4_0_<version number>-windows-i586.exe is the Java 2 SDK 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. When done with the installation, you can delete the download file to recover disk space.

Installed Directory Tree

The Java 2 SDK has the directory structure shown below.




             j2sdk1.4.0_<version number>
  ____________________|___________________
 |    |    |    |    |   |     |      |   |
 |    |    |    |   bin lib    |    demo  |
 |    |    | LICENSE |   |     |         jre
 |    | COPYRIGHT              |        __|__
 |  README                  include    |     |
README.html                           bin   lib

In addition, the Java Plug-in product and Java Web Start product will automatically be installed. Look for a Java Web Start icon on your desktop. There will also be an entry for Java Web Start in the Start --> Programs menu.

4. Delete the downloaded file (Optional)

If you want to recover disk space, delete the file (or files) you originally 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 Java 2 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:> \j2sdk1.4.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 j2sdk1.4.0_<version number>\bin directory to the PATH variable. Typically this full path looks something like C:\j2sdk1.4.0_<version number>\bin. Set the PATH as follows, according to whether you are on Microsoft Windows NT or 95/98/2000/ME.

Microsoft Windows NT, 2000, and XP - To set the PATH permanently:

  1. Choose Start, Settings, Control Panel, and double-click System. On Microsoft Windows NT, select the Environment tab; on Microsoft Windows 2000 select the Advanced tab and then Environment Variables. 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:\j2sdk1.4.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 j2sdk1.4.0_<version number>\bin.
  2. The new path takes effect in each new Command Prompt window you open after setting the PATH variable.

Microsoft Windows 98 and 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: (this is shown on two lines because of its length, but should really be on one line) 
    
                
PATH C:\WINDOWS;C:\WINDOWS\COMMAND
 ; C:\J2SDK1.4.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 j2sdk1.4.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

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

6. Start using the Java 2 SDK!

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.

If you are new to developing and running programs in the Java programming language, see The Java Tutorial online for some guidance. Note especially the tutorial trails under the heading Trails Covering the Basics.

7. Uninstalling the Java 2 SDK

If you should ever want to uninstall the Java 2 SDK, use the "Add/Remove Programs" utility in the Microsoft Windows Control Panel. As an alternative method, if you still have the j2sdk-1_4_0_<version number>-windows-i586.exe file that you used to install the Java 2 SDK, you can double click on it to launch an uninstall program.

Troubleshooting the Installation

Below are some tips for working around problems that are sometimes seen during or following an installation.

  • When attempting to uninstall J2SE 1.4.0_01, if you see a message like the following: 
    

Unhandled Exception error of 0x80040703, and description of: Failed to find
dll function:ActPanel.IsJava2Netscape6Default.

    You may need to manually uninstall the J2RE 1.4.0_01. To do so, follow these steps:

    • Go to Control Panel; select Java Plug-in. Click on the Browsers tab. Uncheck both IE and Netscape6.
    • Remove the directory in which you placed the J2RE. For example, remove C:\Program Files\Java\j2re1.4.0_01.
    • Remove the following files from the Microsoft Windows system directory:
      • plugincpl140_01.cpl
      • java.exe
      • javaw.exe

      The default Windows system directory is as listed below. (It could have been set to a different directory when Windows was installed.)

      • On Microsoft Windows XP, the Windows system directory is:

        C:\windows\system32 or C:\WINNT\system32

      • On Microsoft Windows NT and 2000:

        C:\WINNT\system32

      • On Microsoft Windows 98 and ME:

        C:\windows\system

      • Remove the following Registry Keys: (The second key path shown here should be on one line but runs to a second line because of its length.)
        • HKEY_LOCAL_MACHINE/software/Javasoft/Java Runtime Environment/1.4.0_01
        • HKEY_LOCAL_MACHINE/software/microsoft/windows/currentversion/uninstall/ {7CF31609-270B-11D6-9445-000102308676}

        Do this by going to Start -> Run and execute "regedit". Go to each key shown above and delete it. The second key should have the "DisplayName" of "Java 2 Runtime Environment, SE v.1.4.0_01".

    • If you see the following error message 
      

    Unhandled Exception
    Error: 0x80070725
    Description: Incompatible version of the RPC stub.
    Setup will now terminate.

      This error is caused by library file incompatibilities. For example, version 3.50 of Oleaut32.dll causes this error if it is installed on any operating system other than Windows XP.

      For instructions on resolving this problem, see

      "Incompatible Version of the RPC Stub" Error Message with the InstallShield Program

      If you run the repair executable, when it prompts you to overwrite newer files, make sure to click YES for each file (do not select "No" or "No to All").
    • If you get an error about one of the following during InstallShield setup:
      • Error extracting support files. A typical error message is An Installation support file could not be installed. The filename, directory or volume label syntax is incorrect.
      • Error installing Ikernel.exe (0x any number)
      • Access is denied
      • Error loading Type Library/DLL

      These errors could be caused by a known problem with InstallShield. See the InstallShield web site for a discussion of this problem with possible solutions:

      http://community.flexera.com/t5/custom/page/page-id/ChooseCommunity

    • If you see the following error message: 
      

The InstallShield engine (iKernel.exe) could not be launched.
Error loading type library/DLL

      This message probably indicates that system file Stdole32.tlb is missing from your computer. You can obtain this file from the Microsoft web site.

    • If you see the following error message on Microsoft 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 Microsoft Windows 2000.

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

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

      • Open the MS-DOS shell (Windows/Start/Programs/MS-DOS Prompt)
      • Right-click on the title bar
      • Select Properties
      • Choose the Program tab
      • Push the Advanced button
      • Make sure the item "Prevent MS-DOS-based programs from detecting Windows" is unchecked
      • Select OK
      • Select OK again
      • Exit the MS-DOS shell
      • Restart your computer.
    • Winsock Issues
      The Java 2 SDK requires but does not include the Microsoft Winsock 2.0 library. It is extremely likely that your system already has Winsock 2.0 or later. However, it is possible that some Microsoft Windows 95 systems have an older version of Winsock.

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

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

Installation Notes

Java 2 SDK, Standard Edition
Version 1.4.0
Microsoft Windows 95 / 98 / 2000 / ME / XP / NT 4.0

Oracle Java Archive link

Oracle is reviewing the Sun product roadmap and will provide guidance to customers in accordance with Oracle's standard product communication policies. Any resulting features and timing of release of such features as determined by Oracle's review of roadmaps, are at the sole discretion of Oracle. All product roadmap information, whether communicated by Sun Microsystems or by Oracle, does not represent a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. It is intended for information purposes only, and may not be incorporated into any contract.