______________________________________________________________________

IBM RUNTIME ENVIRONMENT FOR WINDOWS(R), JAVA(TM) TECHNOLOGY EDITION, 
VERSION 1.1.8 - PRODUCT README
______________________________________________________________________

The IBM Runtime Environment for Windows(R), Java(TM) Technology 
Edition, Version 1.1.8 (Runtime Environment) is based on Sun 
Microsystems' Java 1.1.8 maintenance level and provides the Sun 
Microsystems, Inc. Java Environment on:

  Windows 95
  Windows 98
  Windows NT(R) 4.0

The Runtime Environment is provided as either: 

  o  A self-extracting InstallShield executable file 
     (ibm-jre-n118p-win32-x86.exe) 
  o  A ZIP file 
     (ibm-jre-n118p-win32-x86.zip)

The IBM build and version number can be obtained by typing the 
following at a DOS prompt:

  jre -d
______________________________________________________________________
CONTENTS

1.0  OVERVIEW
1.1  Files Included with the Runtime Environment
1.2  The just-in-time (JIT) Compiler
1.3  Installation Considerations
1.4  Java Programs and Native Method Interfaces
1.5  The Java Virtual Machine Profiling Interface

2.0  UNATTENDED INSTALLATION
2.1  Uninstallation Language Considerations

3.0  INVOKING THE RUNTIME ENVIRONMENT

4.0  REDISTRIBUTION REQUIREMENTS
4.1  Definition of Required and Optional Files
4.2  Files Required for Redistribution   
4.3  Optional Files for Redistribution  
  
5.0  THE JAVA RUNTIME INTERPRETER

6.0  EURO SYMBOL SUPPORT
6.1  Platform Support
6.2  Unicode Support
6.3  Collation of Currency Symbols

7.0  RUNTIME EXAMPLE

8.0  INSTALLING YOUR APPLICATION ON A USER'S SYSTEM

9.0  RUNTIME DOCUMENTATION

10.0  GLOSSARY

11.0  NOTICES

12.0  TRADEMARKS 


1.0  OVERVIEW
______________________________________________________________________

The Runtime Environment contains the required subset of classes to 
create a Java runtime environment and to run Java programs. It also
contains the Java Virtual Machine (JVM), Java core classes, and 
supporting files. The Runtime Environment does not contain all the 
classes found in the Java Developer Kit. 

1.1  Files Included with the Runtime Environment
______________________________________________________________________

The Runtime Environment includes non-debuggable .dll files plus 
classes from the IBM Developer Kit for Windows(R), Java(TM) 
Technology Edition, Version 1.1.8 (Developer Kit) software to 
support a program at runtime. The Runtime Environment does not include 
any of the development tools, such as appletviewer or javac, or 
classes that would pertain only to a development system.

See the "Redistribution Requirements" section for a complete list of
files.

1.2  The just-in-time (JIT) Compiler
______________________________________________________________________

The Runtime Environment includes the JIT compiler (ibmjitc.dll), 
which is enabled by default. To disable the JIT, type the following 
at a DOS prompt:

  jre -nojit MyClass

To verify whether or not the JIT is enabled, type the following at 
a DOS prompt:
  
  jre -d

If a JIT is in use, the following message is displayed:

  compiler = enabled: ibmjitc

If no JIT is in use, the following message is displayed:

  compiler = disabled

The Runtime Environment also uses the java.compiler property to 
determine JIT usage and ignores the JAVA_COMPILER environment 
variable.

1.3  Installation Considerations
______________________________________________________________________

The self-extracting InstallShield executable file copies jre.exe 
and jrew.exe into the Windows directory. If a version of 
jre.exe or jrew.exe currently exists in the Windows directory, you 
are prompted to overwrite the existing version with the current 
version. Installing these files into the Windows directory makes 
the Runtime Environment the default Java for the system.

1.4  Java Programs and Native Method Interfaces
______________________________________________________________________

Java programs that use the Native Method Interface (originally 
defined in Sun's JDK 1.0) are supported by the IBM Runtime 
Environment only when they are compiled by the Developer Kit. Java 
programs that use the Sun recommended way of calling native code, 
Java Native Interface (JNI), introduced in Sun's JDK 1.1, are 
supported by the IBM Runtime Environment.

1.5  The Java Virtual Machine Profiling Interface
______________________________________________________________________

This release contains a partial implementation of the Java Virtual 
Machine Profiling Interface (JVMPI) defined by Sun. For further 
information on the implementation, see the following IBM Web site:
 
 http://www.ibm.com/java/jdk/118/jvmpi.html

2.0  UNATTENDED INSTALLATION
______________________________________________________________________

To complete an unattended installation, you must first create a 
response file (setup.iss) that records the choices made during 
installation (also known as an interactive installation). To 
create a response file while running the installation, type the 
following at a DOS prompt:

  ibm-jre-n118p-win32-x86.exe -r -f%TEMP%\xxx\setup.ins

  Note:  
      
         o  There are no spaces after -f. 
         o  For %TEMP% substitute the system's TEMP environment 
            variable. 
         o  To determine the directory of the TEMP environment 
            variable, type SET at a DOS prompt. 
         o  xxx specifies the preferred language variable.

Depending on the platform you are using, a response file (setup.iss) 
will be created in one of the following directories: 

  o  Windows 95/98   C:\Windows 
  o  Windows NT      C:\Winnt 

  Where C is the boot drive. 
 
  Note:  If the following message occurs during an interactive 
         installation: 

         Another Java Runtime Environment is currently 
         installed as the System JVM. Select Yes to overwrite 
         this version or No to exit this installation.
              
         Select No and exit from the installation. Go to the Windows
         system directory and delete the following two files: 

           o  jre.exe
           o  jrew.exe

         After you have deleted the files, restart the interactive 
         installation using the command listed at the beginning of 
         this section.

Once you have created the setup.iss response file, copy it to either 
the C:\Windows or the C:\Winnt directory in the system on which you 
would like to run the unattended install. After you have copied the 
file to the correct system and directory, type the following at a 
DOS prompt: 

  ibm-jre-n118p-win32-x86.exe -s -f%TEMP%\english\setup.ins -f1c:\Windows\setup.iss -f2c:\setup.log

  Note:  In the command listed above, use the C:\Windows directory for 
         Windows 95 and 98 systems and C:\Winnt for Windows NT systems. 
         There are no spaces after -f, -f1, or -f2. The -f1 flag 
         specifies the name and location of the response file. The 
         -f2 flag specifies the name and location of the log file. 

If the installation is successful, the log file will contain 
"ResultCode=0"

2.1  Uninstallation Language Considerations
______________________________________________________________________

The uninstall for an unattended installation is done by using the 
"Add/Remove Programs" icon in the control panel. The language used
during uninstallation is the same as the language chosen during 
installation. (See the example in the "Unattended Installation" 
section.) If you prefer a different language for uninstallation, 
the following languages are available:

  Simplified Chinese       C:\temp\chi_simp
  Traditional Chinese      C:\temp\chi_trad
  French                   C:\temp\french
  German                   C:\temp\german
  Italian                  C:\temp\italian
  Japanese                 C:\temp\japanese
  Korean                   C:\temp\korean
  Brazilian Portuguese     C:\temp\portbrzl
  Spanish                  C:\temp\spanish
  Swedish                  C:\temp\swedish

  C:\temp is the directory defined by the system's TEMP environment 
  variable. 

To use one of the above languages during uninstall, replace the 
language variable in the specified path. 

3.0  INVOKING THE RUNTIME ENVIRONMENT
______________________________________________________________________

The Runtime Environment can be invoked from the DOS prompt by 
using the jre tool. (See the "The Java Runtime Interpreter" section.) 
The jre tool will ignore the CLASSPATH environment variable. Use 
the -cp option to specify an application's CLASSPATH.

The Runtime Environment generates a Java home directory using the 
location of the executable; however, if the proper directory 
structure is not found, it refers to the registry to find the Java 
home directory. This allows for applications to embed the Runtime 
Environment within their directory structure and ensure that the 
Java home directory will always be resolved within the application 
directory. 

4.0  REDISTRIBUTION REQUIREMENTS
______________________________________________________________________

The following sections describe the redistribution requirements.

4.1  Definition of Required and Optional Files
______________________________________________________________________

The files that make up the Runtime Environment are divided into two 
categories, required and optional.  The files that are marked 
"optional" in this README do not need to be included in the 
redistribution of the Runtime Environment with the licensee's program. 
Most of the optional files provide localization support for languages.

The term "required" means licensees that distribute the runtime
must include those files with their program, whether or not their
program ever uses those files. Those files are a required part of
the Java platform.

The Runtime Environment includes the bin and lib directories and 
both must reside in the same directory. This directory is 
<runtime-dir>.In the following lists, all paths are relative to 
the <runtime-dir> directory. <runtime-dir> is where the Runtime 
Environment was installed.

4.2  Files Required for Redistribution
______________________________________________________________________

The bin directory contains these executable files and native 
libraries:

  jre.exe             Java runtime executable file
  jrew.exe            Java runtime executable file, no console
                      window
  rmiregistry.exe     rmiregistry executable file
  ibmjitc.dll         IBM JIT compiler
  javai.dll           Java runtime native code library
  JdbcOdbc.dll        Native code support for sun.jdbc
  jpeg.dll            Native code support for sun.jpeg
  math.dll            Native code support for java.math
  mmedia.dll          Native code support for sun.audio
  net.dll             Native code support for java.net
  sysresource.dll     Native code support for 
                      sun.net.www.protocol
  winawt.dll          Native code support for sun.awt
  zip.dll             Native code support for java.util.zip
   
Note:  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:

         o  Windows 95:  windows\system
         o  Windows 98:  windows98\system
         o  Windows NT:  winnt\system32  

The lib directory contains the classes and property files:

  lib\rt.jar                    Java runtime core classes
  lib\content-types.properties  MIME-type properties
  lib\awt.properties            properties for key events for java.awt
  lib\font.properties           font properties for java.awt
  lib\serialver.properties      serialization properties
  lib\security\java.security    properties for java.security

4.3  Optional Files for Redistribution
______________________________________________________________________

The following files are optional:

  bin\javakey.exe               javakey executable
  lib\i18n.jar                  I18N character conversion classes from 
                                sun.io
  lib\font.properties.ar        AWT font properties for Arabic locale
  lib\font.properties.be        AWT font properties for Byelorussian 
                                locale
  lib\font.properties.bg        AWT font properties for Bulgarian locale
  lib\font.properties.cs        AWT font properties for Czech locale
  lib\font.properties.el        AWT font properties for Greek locale
  lib\font.properties.et        AWT font properties for Estonian locale
  lib\font.properties.hr        AWT font properties for Croatian locale
  lib\font.properties.hu        AWT font properties for Hungarian locale
  lib\font.properties.iw        AWT font properties for Hebrew locale
  lib\font.properties.ja        AWT font properties for Japanese locale
  lib\font.properties.ko        AWT font properties for Korean locale
  lib\font.properties.lt        AWT font properties for Lithuanian locale
  lib\font.properties.lv        AWT font properties for Latvian locale
  lib\font.properties.mk        AWT font properties for Macedonian locale
  lib\font.properties.pl        AWT font properties for Polish locale
  lib\font.properties.ro        AWT font properties for Romanian locale
  lib\font.properties.s2        AWT font properties for Serb locale
  lib\font.properties.sk        AWT font properties for Slovak locale
  lib\font.properties.sl        AWT font properties for Slovene locale
  lib\font.properties.ru        AWT font properties for Russian locale
  lib\font.properties.th        AWT font properties for Thai locale
  lib\font.properties.tr        AWT font properties for Turkish locale
  lib\font.properties.uk        AWT font properties for Ukrainian locale
  lib\font.properties.yu        AWT font properties for Serbo-Croatian 
                                locale
  lib\font.properties.zh_TW     AWT font properties for Traditional
                                Chinese locale
  lib\font.properties.zh        AWT font properties for Simplified 
                                Chinese locale
  lib\math.jar                  IBM Enhanced Big Decimal support
   
5.0  THE JAVA RUNTIME INTERPRETER
______________________________________________________________________

The jre tool invokes the Java Runtime Interpreter for executing Java
applications. The syntax for starting the jre tool is as follows:

  jre [ options ] classname <args>

The classname argument is the name of the class file to be
executed. Any arguments to be passed to the class must be placed
after the classname on the DOS prompt.

An alternative for the jre tool, jrew, is available. The jrew 
tool is identical to the jre tool, except that a console window is 
not invoked. The syntax for starting the jrew tool is as follows:

  jrew [ options ] classname <args>

The jre tool will ignore the CLASSPATH environment variable. Use 
the -cp option to specify an application's CLASSPATH.

Options for the jre tool are as follows:

  -classpath path       Specifies the path that the jre tool uses 
                        to look up classes. Overrides the default 
                        CLASSPATH.

  -cp path              Places the specified path to the default
                        CLASSPATH that the jre tool uses to look 
                        up classes.

  -help                 Print a usage message.

  -mx x                 Sets the maximum size of the memory 
                        allocation pool (the garbage collected heap) 
                        to x. The default is 16 megabytes of memory. 
                        x must be greater than or equal to 1000 bytes.

  -ms x                 Sets the startup size of the memory allocation
                        pool (the garbage collected heap) to x. The
                        default is 1 megabyte of memory. x must be
                        greater than 1000 bytes.

  -maxe<size>           Sets the maximum size of each expansion to the 
                        heap when more memory is required. For 
                        example:
 
                          jre -maxe2097152 MyClass

  -mine<size>           Sets the minimum size of each expansion of the 
                        heap. Also sets the minimum size of free 
                        object space in the heap. For example: 

                          jre -mine1048576 MyClass 

  -maxf<float>          Sets the approximate percentage of maximum 
                        free heap. For example: 

                          jre -maxf0.60 MyClass

  -minf<float>          Sets the approximate percentage of minimum 
                        free space in the heap to give control over 
                        the rate of preallocation performed when 
                        heap space is expanded. For example: 

                          jre -minf0.35 MyClass

  -noasyncgc            Turns off asynchronous garbage collection. 
                        When activated, no garbage collection takes 
                        place unless it is explicitly called or the 
                        program runs out of memory.

  -noclassgc            Turns off garbage collection of Java classes.
                        By default, the Java interpreter reclaims 
                        space for unused Java classes during garbage 
                        collection.

  -nojit                Turns off the just-in-time bytecode
                        compiler. The virtual machine directly
                        interprets bytecodes, without converting them
                        to native code.

  -ss x                 Sets the maximum stack size that can be used 
                        by C code in a thread to x. The default units 
                        for x are bytes. The value of x must be 
                        greater than or equal to 1000 bytes.

  -oss x                Sets the maximum stack size that can be used 
                        by Java code in a thread to x. The default 
                        units for x are bytes. The value of x must be 
                        greater than or equal to 1000 bytes.

  -v, verbose           Causes the jre tool to print a message to stdout 
                        each time a class file is loaded.

  -verify               Performs byte-code verification on the class
                        file. However, java -verify does not perform 
                        a full verification in all situations. Any 
                        code path that is not actually executed by 
                        the interpreter is not verified. Therefore, 
                        java -verify cannot be relied upon to certify 
                        class files unless all code paths in the class 
                        file are actually run.

  -verifyremote         Runs the verifier on all code that is loaded
                        into the system by a classloader. verifyremote
                        is the default for the interpreter.

  -noverify             Turns verification off.

  -verbosegc            Causes the garbage collector to print out
                        messages whenever it frees memory.

  -DpropName=value      Defines a property value. propName is the name
                        of the property whose value you want to change
                        and value is the value to change it to. For
                        example, the command

                          java -Dawt.button.color=green ... 

                        sets the value of the property 
                        awt.button.color to "green."

6.0  EURO SYMBOL SUPPORT
______________________________________________________________________

In order to take advantage of the euro symbol support, the operating 
system must support the euro symbol. The following sections give 
further information on euro symbol support.

6.1  Platform Support
______________________________________________________________________

Information on Microsoft's support can be found at the following 
Web sites:

  Windows 95       http://www.microsoft.com/Windows/Euro.asp 

  Windows 98       Contains codepage support for the euro, 
                   appropriate fonts and keyboards drivers. 

  Windows NT 4.0   Service Packs 4 and 5 contain support for the 
                   euro can be found at the following Web site:

                     http://www.microsoft.com/support/winnt/default.htm                

The encoded Windows core fonts that contain euro support are Times 
New Roman, Courier New, and Arial.

If you need to change your keyboard layout or input locale (see 
Regional Settings or Keyboard on the Control Panel), you should do 
this before installing the appropriate euro product update. The 
Microsoft Euro Currency Symbol FAQ Web page details the keyboard 
layouts that support the euro. If your input locale is EN English 
(United States), use US-International rather than US as the 
keyboard layout. You can then use the key combination right 'ALT' 
key and 5 to enter a euro character.

The Windows code pages that include or will include the euro are:

 1250 Central/Eastern European
 1251 Cyrillic
 1252 Western Europe
 1253 Greek
 1254 Turkish
 1255 Hebrew
 1256 Arabic
 1257 Baltic
 1258 Vietnamese
 874  Thai

Note:  The default converter for Western European locales is Cp1252,  
       because Cp1252 supports the euro.

6.2  Unicode Support
______________________________________________________________________

The Unicode character for the euro is u'20ac'.

6.3  Collation of Currency Symbols
______________________________________________________________________

Collation of currency symbols traditionally follows the English 
collation order of the symbol name. Thus 'cent' is followed by 
'dollar'. According to this scheme, the euro symbol will sort 
immediately following the dollar and dong currency symbols and before 
the French franc.

7.0  RUNTIME EXAMPLE
______________________________________________________________________

The following Sun Web page may contain a "Hello World" example that 
you can download. The example demonstrates how to create a simple 
Java application that runs on and is bundled with the Java Runtime 
Environment. You can find the example at: 

  http://java.sun.com/products/jdk/1.1/jre/example/

The example shows how to make a simple, seamless transition
from developing an application with a Developer Kit, to deploying it 
with the more lightweight Runtime Environment.

8.0  INSTALLING YOUR APPLICATION ON A USER'S SYSTEM
______________________________________________________________________

Once you have developed your product and are ready to ship, you will 
need to install your product onto an individual user's system, to 
configure the user's system to support your software, and configure 
the runtime environment. 

If you use the Runtime Environment, you must make sure that your
installation procedure does not overwrite an existing installation. 
(Unless the existing Java Runtime Environment is an older version.)

One way to redistribute the Runtime Environment is to include 
the executable file in your software package. You can then have 
your installation program run the executable file or instruct 
the user to install the Runtime Environment before installing 
the rest of your package.

A more sophisticated approach is to install the Runtime Environment 
on your own system, then copy the files you need into your 
installation set. If you choose this approach, you must include all 
the files listed as "required" in the "Files Required for 
Redistribution" section. The Runtime Environment software can 
only be redistributed if all "required" files are included. In 
effect, when you ship your application, it has its own copy of the 
Runtime Environment.

If you use this approach, do not try to emulate the installation steps
performed by the Runtime Environment installer.

  Note:  The installation program records program information in 
         the Windows Registry. This registry information includes the 
         software version that you should compare with the 
         Runtime Environment version in your software package.

9.0  RUNTIME DOCUMENTATION
______________________________________________________________________

Runtime documentation is any documentation that end users might need 
after they have installed a Java program that runs on the Runtime 
Environment.

IBM supplies the following runtime documentation:

  o  Each property file contains comments that describe what the
     file is useful for and how to modify it.

  o  awt.properties file - KeyEvent uses this file to print out 
     properties of key events, usually for debugging purposes. 
     
10.0  GLOSSARY
______________________________________________________________________

  MIME            An industry standard character encoding.

  Bytecode        Compiled Java code.		

  Garbage 
  Collected Heap  A heap that is asynchronously freed when not in use.

  <args>          An industry standard way of describing inputs such 
                  as DOS prompt arguments or parameters to an 
                  Application Program Interface (API). 

11.0  NOTICES
______________________________________________________________________

This edition applies to the IBM Runtime Environment for Windows(R), 
Java(TM) Technology Edition, version 1.1.8 and to all subsequent 
releases and modifications until otherwise indicated in new editions.

Copyright International Business Machines Corporation 1997. All 
rights reserved. 
  
Note to U.S. GovernmentUsers Restricted Rights --Use, duplication 
or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 
  
Consult your local IBM representative for information on the products 
and services currently available in your area. Any reference to an IBM 
product, program, or service is not intended to state or imply that 
only that IBM product, program, or service may be used. Any 
functionally equivalent product, program, or service that does not 
infringe any IBM intellectual property right may be used instead. 
However, it is the users responsibility to evaluate and verify the 
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject 
matter in this document. The furnishing of this document does not give 
you any license to these patents. You can send license inquiries, in 
writing, to: 

  IBM Director of Licensing
  IBM Corporation
  North Castle Drive
  Armonk, NY  10504-1758>
  U.S.A.

For license inquiries regarding double-byte (DBCS) information, 
contact the IBM Intellectual Property Department in your country or 
send inquiries, in writing, to: 

  IBM World Trade Asia Corporation Licensing
  2-31 Roppongi 3-chome, Minato-ku
  Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any
other country where such provisions are inconsistent with local law:

  INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS 
  PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER 
  EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE 
  IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR 
  FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow 
  disclaimer of express or implied warranties in certain 
  transactions, therefore, this statement may not apply to you.  

This information could include technical inaccuracies or
typographical errors.  Changes are periodically made to the
information herein; these changes will be incorporated in new editions
of the information.  IBM may make improvements and/or changes in the
product(s) and/or the program(s) described in this information at any
time without notice.  

Any references in this information to non-IBM Web sites are provided 
for convenience only and do not in any manner serve as an endorsement 
of those Web sites. The materials at those Web sites are not part of 
the materials for this IBM product and use of those Web sites is at 
your own risk.

IBM may use or distribute any of the information you supply in any 
way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it 
for the purpose of enabling (i) the exchange of information between 
independently created programs and other programs (including this one) 
and (ii) the mutual use of the information which has been exchanged, 
should contact:

  JTCMAIL@uk.ibm.com
  [Hursley Java Technology Center (JTC) contact] 
  
Such information may be available, subject to appropriate terms and 
conditions, including in some cases, payment of a fee.  

The licensed program described in this document and all licensed 
material available for it are provided by IBM under terms of the 
IBM Customer Agreement, IBM International Program License Agreement 
or any equivalent agreement between us. 

Any performance data contained herein was determined in a controlled 
environment. Therefore, the results obtained in other operating 
environments may vary significantly. Some measurements may have been 
made on development-level systems and there is no guarantee that these
measurements will be the same on generally available systems. 
Furthermore, some measurement may have been estimated through
extrapolation. Actual results may vary.  Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the
suppliers of those products, their published announcements or other
publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other
claims related to non-IBM products.  Questions on the capabilities of
non-IBM products should be addressed to the suppliers of those
products.  

All statements regarding IBMs future direction or intent are subject 
to change or withdrawal without notice, and represent goals and 
objectives only. 

All IBM prices shown are IBMs suggested retail prices, are current 
and are subject to change without notice.  Dealer prices may vary.

COPYRIGHT LICENSE: 

This information contains sample application programs in source
language, which illustrate programming techniques on various
operating platforms. You may copy, modify, and distribute these
sample programs in any form without payment to IBM, for the purposes
of developing, using, marketing or distributing application programs
conforming to the application programming interface for the operating
platform for which the sample programs are written. 

These examples have not been thoroughly tested under all conditions.  
IBM, therefore, cannot guarantee or imply reliability, 
serviceability, or function of these programs. You may copy, modify, 
and distribute these sample programs in any form without payment 
to IBM for the purposes of developing, using, marketing, or 
distributing application programs conforming to IBM's application 
programming interfaces. 

12.0  TRADEMARKS
______________________________________________________________________

IBM is a trademark of International Business Machines Corporation in 
the U.S., or other countries, or both:

Java is a trademark of Sun Microsystems, Inc. in the U.S.
and other countries.  The Java technology is owned and exclusively
licensed by Sun Microsystems, Inc.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks 
of Microsoft Corporation in the United States, other countries, or 
both. 

Other company, product, and service names may be trademarks or
service marks of others.

Copyright (c) 1997, 1999 Sun Microsystems, Inc.
901 San Antonio Rd., Palo Alto, CA 94303 USA.
All rights reserved.

(c) Copyright IBM Corporation 1999, All rights reserved.
______________________________________________________________________

END-OF-README-FILE
______________________________________________________________________
