See supported System Configurations for information about supported platforms, operating systems, desktop managers, and browsers.
The minimum physical RAM is required to run graphically based applications. More RAM is recommended for applets running within a browser using the Java Plugin. 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.
This installation requires Windows Installer 2.0 to be on your machine. For more details, see the Troubleshooting the Installation section .
For the amount of disk space required, see Windows Disk Space Requirements.
In this procedure, you will run the self-installing executable to unpack and install the JDK software bundle. As part of the JDK, this installation includes an option to include the public Java Runtime Environment. (The JDK also contains a private JRE for use only by its tools.)
Troubleshooting - If you have any difficulties, see the Troubleshooting section at the end of this document.
If you save the self-installing executable to disk without running it from the download page at the 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. Run the JDK installer
3. If you want to run Netscape 7.x, Mozilla 1.x, or Firefox 1.x with Java Plugin, do this:
You can run the JDK without setting the PATH variable, or you can optionally set it as a convenience.
Your computer system should now be ready to use the JDK. In this step, you'll run some simple commands to make sure it is working properly.
If you should ever want to uninstall the JDK, use the "Add/Remove Programs" utility in the Microsoft Windows Control Panel.
jre/bin/client/jvm.dll (on x86)The path to the Java HotSpot Server VM is:
jre/bin/server/jvm.dll (on x86)The corresponding locations in the Java SE Runtime Environment begin with jre1.6.0 instead of jre. The Exact VM and Classic VM are no longer part of the JDK, and existing code that uses the Invocation API to launch an application based on old paths to the Exact or Classic VMs will not work.
Troubleshooting the Installation
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.