RELEASE NOTES
                           OpenNT Release 2.0
                               May 5, 1997


CONTENTS
 * Introduction
 * Installation
 * Upgrading from OpenNT 1.1 or OpenNT 2.0 BETA
 * Documentation
 * Notes and Known Problems
    - Microsoft Resource Kit POSIX Binaries
    - Directory Names with Spaces
    - Microsoft Visual C/C++ 5.0
    - Multiprocessor Systems
    - PgUp & PgDn in Vi
    - Log File Error in Vi
    - OpenNT Telnet Server
    - OpenNT X11 Server
    - Network File Systems
    - #define opennt
    - xblackjack Crashing (OpenNTiF)
    - cc vs. c89
    - GCC Support
    - Documentation Update
 * Comments, Please

INTRODUCTION:

Thank you for purchasing OpenNT Release 2.0.  OpenNT 2.0
supports considerable new functionality: sockets, shared
memory, full job control, more utilities, tape drive access,
and X11R5 utilities and libraries.  Please see the "Getting Started"
booklet for instructions on how to install OpenNT 2.0, and on 
getting started with the shells and software development kits.
Getting Started is available in the pubs directory of the
distribution as GETSTART.PDF and GETSTART.DOC. The .DOC
file can be read with WordPad.

This file contains new information and updates to the other
documentation.

INSTALLATION:

Instructions on installing OpenNT 2.0 are in the "Getting
Started" booklet, with these additional notes:

NOTE: If you are installing onto a remote drive, the drive
must be mounted as a drive letter.  A UNC name is not enough
-- if you try to specify a UNC name, the install program
returns a message that it can't find the archive.

NOTE: Make sure that the directory displayed in the
confirmation page is the same directory you selected,
especially if you chose to install at the root of a drive
letter.

Before you can install, you need a license key
(either a demonstration key or a purchased key).
Keys are available from Softway Systems.

To get a demo key, call or fax the Softway Systems office,
or send e-mail to demo@opennt.com. See below for contact
info.

If you are upgrading from OpenNT 1.1 or the OpenNT 2.0 BETA:

 * Back up any modified files such as
   $OPENNT_ROOT/etc/profile.lcl

 * UNINSTALL the earlier release before installing
   OpenNT 2.0

Then proceed with the installation as described in the
"Getting Started" book.


DOCUMENTATION:

All of the documentation is provided in Adobe Acrobat's
Portable Document Format (PDF) files, and is installed by
selecting the OpenNT PDF Publications option at install
time. See the "Getting Started" booklet for more details.

You must have the Adobe Acrobat 3.0 reader to read the PDF
files.  A copy has been provided on the CD-ROM.

NOTES AND KNOWN PROBLEMS AND SOLUTIONS:

Microsoft Resource Kit POSIX Binaries:
   POSIX subsystem binaries from the Microsoft Resource Kit
   do not run with the OpenNT subsystem.  Ensure that they
   are not in your PATH.

Microsoft Visual C/C++ 5.0:
   The default installation path ("\Program Files") contains
   a space.  We strongly recommend installing MSVC50 so the
   path does not contain spaces.  See 'Directory Names with Spaces'.

Directory Names with Spaces:
   Some programs (such as Microsoft Visual C/C++ 5.0)
   install by default in a directory whose name contains
   spaces (such as "\Program Files").  Quoting these
   directory names in shell scripts (for example, in the
   PATH variable) can be difficult to do correctly.

   If possible, avoid using directory names that include
   spaces in the PATH environment variable.  The ksh and csh
   startup files quote the PATH properly, but other existing
   shell scripts that examine the PATH may need to be
   altered once the PATH contains spaces.

Multiprocessor Systems: 
   Earlier releases of the OpenNT subsystem did not work on
   multiprocessor systems.  Microsoft acknowledged this as a
   problem in the NT system (Microsoft defect ID #61390).
   Windows NT 4.0 Service Pack 3 (SP3) fixes that defect.
   If you have a multiprocessor system, you should install
   SP3.

Windows NT 4.0 Service Pack 3:
   Windows NT 4.0 Service Pack 3 (SP3) fixes a defect that
   now allows the OpenNT subsystem to work properly on a
   multiprocessor system.  SP3 also fixes a problem with
   large 'find' commands that use the -exec operand.  When
   Microsoft makes it available, it should be downloadable
   from the Microsoft web site at this URL:
      http://www.microsoft.com/msdownload/default.asp#sup

   If you cannot install SP3, please see the discussion in
   the Tech Note, "Running OpenNT on MP Systems without
   Service Pack 3" on the OpenNT website.

PgUp & PgDn Keys in Vi:
   In an xterm or a telnet session, the PgUp and PgDn keys
   do not work correctly in vi.  Control-B and Control-F
   work correctly to move back one screen and forward one
   screen.

Log File Error in Vi:
   When the temporary directory (TMPDIR) points to a FAT
   file system, vi responds to the :n and :e commands with
   "Error: Log file: No such file or directory." The
   workaround is to point TMPDIR at a directory on an NTFS
   file system.

OpenNT Telnet Server:
   The new telnetd program *replaces* the old OpenNT Telnet
   Server program.  Both programs cannot run at the same
   time; before running the OpenNT Release 2.0 telnetd, you
   must uninstall the OpenNT Telnet Server that came with
   previous releases of OpenNT, including the OpenNT 2.0
   beta release.

OpenNT X11 Server:
   Users who want to run the X11 Server for the first time
   should first run the OpenNT X11 Server Control Panel (in
   the OpenNT X11 Server folder).  This will ensure that all
   the configuration files are set up correctly for that
   user.  The warnings regarding FONTPATH can be ignored.

   There is a known problem with the OpenNT X11 Server on
   Windows NT 4.0.  The Performance Tuning utility is
   normally run upon starting the X11 Server for the first
   time.  Subsequent executions of the X11 Server should not
   rerun the Performance Tuning utility again.  This works
   correctly for the user that installed the X11 Server.
   For other users, occasionally the Performance Tuning
   utility will get run every time the X11 Server starts.
   To overcome this, copy the file XOFT.CFG in the
   C:\OPENNT\USR\X11R6\SERVER directory to each of the
   subdirectories named USERDB.XXX, where XXX is a number.
   This will prevent the Performance Tuning utility from
   being run every time.

Network File Systems:
   OpenNT 2.0 does not fully support SAMBA, Netware,
   Clearcase or NFS file systems.  Check the OpenNT web site
   (http://www.opennt.com/) for information.

cc vs. c89:
   The c89 compiler interface is used to compile in an
   ISO/ANSI C environment.  Cc is used to compile in a
   historical UNIX environment.  In the ISO environment, you
   must use -D to explicitly enable feature test macros to
   make visible any non C standard identifiers and symbols.
   For instance, the _ALL_SOURCE macro is used in the OpenNT
   SDK to allow all identifiers and symbols supported by
   OpenNT to be made visible.  The cc program automatically
   defines _ALL_SOURCE for you.

#define opennt:
   In previous versions of OpenNT, the macro 'opennt' was
   being automatically defined by the compiler interfaces cc
   and c89.  This macro was made available to indicate that
   the compilation was being performed in an OpenNT
   environment.  This macro name has been renamed to
   '__OPENNT' to avoid namespace conflicts with the ISO and
   ANSI standards.  Any previously ported source code using
   this macro (ie.  #ifdef opennt) should be changed.
   Alternatively the option -Dopennt can be used when
   invoking the compiler interface programs (such as in
   your Makefile).

xblackjack Crashing (OpenNTiF):
   Some Motif applications such as xblackjack crash when they
   try to set a dialog box title. To avoid this, set the
   environment variable XNLSPATH; for example, in the
   KornShell:
     $ export XNLSPATH=${OPENNT_ROOT}/usr/X11R5/lib/X11/nls

GCC Support:
   Support for GCC is planned and should be available soon.
   Check the OpenNT web site (http://www.opennt.com/) for
   information.

Documentation Update:
   Several new terminal descriptions (in terminfo and
   termcap) did not make it into the OpenNT Commands and
   Utilities User's Guide.  These new descriptions have
   names ending in -nti, such as opennt-nti and
   opennt-60-nti.  These new terminal descriptions have the
   ti/te capability (terminalinitialization/terminal end)
   codes turned off.

   If your TERM is set to a -nti value, programs such as vi
   and more will no longer save the screen when you start
   the program and restore it when you quit.


SAMPLE APPLICATIONS:

For sample applications such as Apache, see the OpenNT Tool
Warehouse at:
   http://www.softway.com/OpenNT/tw/tw.htm


COMMENTS, PLEASE:

We encourage comments and suggestions.  To send comments,
suggestions, questions, or problems about OpenNT 2.0 please
send e-mail to: support@softway.com

Please include your name, a phone number where you can be
reached, and a return e-mail address if it is not the same
as that from which you sent the e-mail, along with your
comments and problem reports.

We can also be reached at +1 415 896 0708 by phone during
Pacific Coast business hours.  For news, please keep an eye
on our web site:

		   http://www.OpenNT.com
