
                                README

                    The Java(tm) Runtime Environment
                                JRE 1.2
                          


This Java Runtime Environment (JRE) implements the Java 1.2 platform.
The JRE contains the software necessary to run programs written in the
Java progamming language. The JRE is not a development environment. To
obtain development tools for the Java programming language and the Java
platform, download the Java Development Kit from the Java Software web
site at http://java.sun.com/. A Japanese version of this README is on 
the Java Software website at 
http://java.sun.com/products/jdk/1.2/ja/jre/README

The JRE includes a launcher program which can be used to run 
applications on the Java virtual machine. The launcher program in this 
release is "java". This is a general-purpose launcher program and is 
the same launcher program that is included in the Java Development Kit. 
Documentation for the "java" launcher tool is included in the Java 
Development Kit.

On Win32, the JRE now includes the Java Plug-in product, which enables
support for the complete Java 1.2 platform on recent releases of
Netscape Navigator and Microsoft Internet Explorer. When you install
the JRE, you can install the Plugin as well. For more information, 
including information about the Java Plug-in for Solaris, see
the Plug-in web page at http://java.sun.com/products/plugin/.

The Win32 version of the JRE includes a Symantec JIT compiler,
Copyright (c) 1996-1998 by Symantec Corporation. All rights reserved.

=======================================================================
                 Deploying Java Applications with the JRE
=======================================================================

A Java application, unlike a Java applet, cannot rely on a web browser 
for installation and runtime services. When you deploy a Java 
application, your software bundle will probably consist of the 
following parts: 

            Your own class, resource, and data files. 
            A runtime environment. 
            An installation procedure or program. 

You already have the first part, of course. The remainder of this
document covers the other two parts. 

-----------------------------------------------------------------------
Runtime Environment
-----------------------------------------------------------------------

To run your application, a user needs a Java virtual machine, the Java 
platform core classes, and various support programs and files. This 
collection of software is known as a runtime environment. 

The JDK software can serve as a runtime environment. However, you 
probably can't assume your users have the JDK software installed, and 
your JDK software license doesn't allow you to redistribute JDK 
software files. 

To solve this problem, Sun provides this Java Runtime Environment (JRE) 
as a free, redistributable runtime environment, available for Win32 and 
Solaris systems. (The JRE should not be confused with the JDK 
software's own "private", non-redistributable version of the runtime 
environment housed in the jdk1.2/jre directory.)  

The Win32 versions comes with a built-in installation program
suitable for end-users. Solaris versions require the developer to
provide installation support. 

The Java Runtime Environment for Win32 is available both with and 
without international support. The non-international version is much 
smaller, but is suitable only for English-speaking users. 

The final step in the deployment process occurs when the software is 
installed on individual user system. Installation consists of copying 
software onto the user's system, then configuring the user's system to 
support that software. 

This step includes installing and configuring the runtime environment. 
If you use the Java Runtime Environment, you must make sure that your 
installation procedure never overwrites an existing installation, unless 
the existing Java Runtime Environment is an older version. 

The Win32 version of the Java Runtime Environment is distributed as a 
self-installing executable. A simple way to redistribute the Java 
Runtime Environment is to include this executable in your software 
bundle. You can then have your installation program run the executable, 
or simply instruct the user to install the Java Runtime Environment 
before installing the rest of your bundle. 

The Windows Java Runtime Environment now includes Java Plug-in software, 
which enables Netscape Navigator and Microsoft Internet Explorer to 
support the Java 1.2 platform. To develop applets that use Java Plug-in 
software, see the Java Plug-in product page on the Java Software web 
site:

     http://java.sun.com/products/plugin/

You can also find information about the Java Plug-in for Solaris on 
this web page.

The Win32 installation program records program information in the 
Windows Registry. This registry information includes the software 
version, which you should compare with the Java Runtime Environment 
version in your software bundle. For more information, refer to the 
Java Runtime Environment Notes for Developers on the Java Software web 
site:

     http://java.sun.com/products/jdk/1.2/runtime.html 

A more sophisticated approach is to install the Java Runtime
Environment on your own system, then copy the files you need into your 
own installation set for redistribution. If you choose this approach, 
you must include all files described below as "required" in the 
"Redistrubition of the JRE" section of this README. The Java Runtime
Environment software can only be redistributed if all "required" files 
are included. See the LICENSE file for specifics. 

If you use this approach, do not try to emulate the installation steps 
performed by the Java Runtime Environment installer. You might "break" 
an existing Java Runtime Environment installation by missing a new or 
undocumented installation step. Instead, you should include the Java 
Runtime Environment files in your own application directory. In 
effect, your application has its own "private" copy of the Java Runtime 
Environment. 

-----------------------------------------------------------------------
Winsock Deployment
-----------------------------------------------------------------------

If your application uses the networking classes, it may not run 
reliably under Winsock 1.1. If your networking application must support 
Windows 95, which includes Winsock 1.1, you will want to include a 
Winsock 2.0 install in your installation procedure. (Windows NT 4.0 and 
Windows 98 include Winsock 2.0.) To provide Winsock 2.0, you need the 
Microsoft Windows Sockets 2.0 Software Development Kit. This free 
software can be downloaded from the following addresses: 

    http://www.microsoft.com/win32dev/netwrk/winsock2/ws295sdk.html
    ftp://ftp.microsoft.com/bussys/WinSock/winsock2/



=======================================================================
                      Redistribution of this JRE
=======================================================================
In this document, the term "vendors" refers to licensees, developers, 
and independent software vendors (ISVs) who license and distribute the 
JRE with their programs.

Vendors may not redistribute this JRE except in the limited 
circumstances described in the JRE Binary Code License agreement, 
contained in the LICENSE file in the JRE download bundle.  The license 
is also on the JavaSoft website at 

  http://java.sun.com/products/jdk/1.2/jre/LICENSE

Vendors must follow the terms of the JRE Binary Code License agreement  
which include, among others:

 - Redistribution is allowed only with applets or applications that are 
   clearly identified to users as pre-release versions that are for 
   evaluation purposes only and not for computing operations of a
   critical nature.

 - Arbitrary subsetting of the JRE is not allowed. See the section 
   below entitled "Required vs. Optional Files" for those files that 
   may be optionally omitted from redistributions of the JRE. 

 - You must include in your product's license the provisions called 
   out in the JRE Binary Code license.

-----------------------------------------------------------------------
Required vs. Optional Files
-----------------------------------------------------------------------
Licensees must follow the terms of the accompanying LICENSE.  
The files that make up the JRE are divided into two categories:
required and optional.  To paraphrase the license, files that 
are marked "optional" here do not need to be included in 
redistributions of the JRE with the licensee's program.  

The following sections contain lists of the JRE files, for both Windows 
and Solaris platforms, that may optionally be redistributed with 
the JRE.  All files not in these lists of optional files must be 
included in redistributions of the JRE.

The JRE includes the bin and lib directories which both must
reside in the same directory, called <runtime-dir> in the lists below.
All paths are relative to the <runtime-dir> directory.

Note that in the case of the Windows JRE, the native code C runtime 
library, msvcrt.dll, is located in the Windows system directory. The 
location of this directory varies on different operating systems, but 
is usually

   - winnt\system32 on Windows NT
   - windows98\system on Windows 98
   - windows\system on Windows 95

This file should be included in redistributions of the Windows JRE.

-----------------------------------------------------------------------
Win32 Optional Files and Directories
-----------------------------------------------------------------------
All font properties files in the lib directory other than the default 
lib\font.properties file are optional, and vendors may choose not to 
include them in redistributions of the JRE. In addition, the following 
may be optionally excluded from redistributions:

bin\beans.ocx		      
   Plugin ActiveX control
lib\jaws.jar		      
   Plugin classes
lib\i18n.jar                  
   Character conversion classes and all other locale support
lib\ext\                      
   Directory containing extension jar files
bin\symcjit.dll               
   JIT compiler
bin\rmid.exe
   Java RMI Activation System Daemon
bin\rmiregistry.exe
   Java Remote Object Registry
bin\tnameserv.exe
   Java IDL Name Server
bin\keytool.exe
   Key and Certificate Management Tool
bin\policytool.exe
   Policy File Creation and Management Tool


-----------------------------------------------------------------------
Solaris Optional Files and Directories
-----------------------------------------------------------------------
The directory <sys> varies depending on the hardware architecture 
implementation.  It will be either sparc or i386. The Solaris JRE 
ships with support for both green threads and native threads. Files 
providing this support are in the directories lib/<sys>/green_threads 
and lib/<sys>/native_threads respectively.  Although at least one of 
these directories and its contents must be included in redistributions 
of the JRE, vendors do not have to include both. 

All font properties files in the lib directory other than the default 
lib/font.properties file for Solaris 2.6 and the default 
lib/font.properties.5.5.1 file for Solaris 2.5.1 are optional, and 
vendors may choose not to include them in redistributions of the JRE. 
In addition, the following may be optionally excluded from 
redistributions:

lib/i18n.jar                  
   Character conversion classes and all other locale support
lib/<sys>/libsunwjit.so       
   JIT compiler
lib/ext/                      
   Directory containing extension jar files
bin/rmid
   Java RMI Activation System Daemon
bin/rmiregistry
   Java Remote Object Registry
bin/tnameserv
   Java IDL Name Server
bin/keytool
   Key and Certificate Management Tool
bin/policytool
   Policy File Creation and Management Tool

-----------------------------------------------------------------------
Copyright (c) 1998 Sun Microsystems(tm), Inc.
901 San Antonio Road, Palo Alto, CA 94303-4900
All rights reserved.

