==============================================================
                   EXTRA! Personal Client 
                        Version 6.1
                           32-bit
                       Release Notes  
                         
==============================================================

Copyright 1996 by                        Attachmate Corporation
Attachmate Corporation                   February 1996
All rights reserved


This file contains late-breaking information pertaining to this 
release of EXTRA! Personal Client.

The following topics are covered in this file:

* New Connectivities		* System Requirements
  and Features

* Setup				* Network Setup

* Installing Over an Old	* Uninstall
  EXTRA! Personal Client			

* Registry Information

* Multiuser Login with		* True Type Fonts
  Windows NT

* Macro recording on		* EXTRA! Basic Macros
  asynchronous hosts

* Backward-compatibility with	* Microsoft SNA Server
  4.x EXTRA! Basic Macros

* Compact installation and	* Creating new sessions
  APPN

* APPN configurator and		* Connecting to PU2.1 or 
  Security			  PU 2.0 on the host

* Connecting via 802.2 (DLC)	* EXTRA! Personal Client
				  and Attachmate Gateway

* TCP/IP to Zip! Server		* Using SDLC or DFT
				  connectivities

* TN3270 connections and	* Windows 95 Ethernet support
  Microsoft Network		  and 802.2 connectivity

* DFT and Irma3 Coax hardware	* IrmaLAN via IPX/SPX to
				  ZIP! SNA Server

* Connecting to a Microsoft	* Migrating 802.2 (DLC)
  SNA Server			  configuration 

* Migrated SDLC sessions	* OLE Automation conflicts
				  with Visual Basic

* OLE Automation and		* Printer emulator
  WaitForCursor			  application error

* Printer emulator and session	* Renaming Navigation pages 
  configuration defaults

* Prompting for userid or	* Saving sessions and 
  password during Navigation	  creating layouts 

* Windows 95 and 84-key		* Font and window
  keyboards			  sizing

* LAT 1.0 and PATHWORKS		* Dual boot systems and
  V1.0 for Windows 95		  AUTOEXEC.BAT 
 


-------------------------------
New Connectivities and Features
-------------------------------

EXTRA! Personal Client 6.1 now supports the following
connectivities:

* IrmaLAN Banyan VINES connection

* ZIP! SNA via NetBIOS connection

* Cisco NCIA connection over TCP/IP

* SDLC and DFT connection for Windows NT

The following new features have been added to this version of
EXTRA! Personal Client:

* FT/Express Host-Initiated File Transfer

  Supports host-initiated file transfer during a CICS, CMS, or
  TSO host session.

  Note: In this release, there is no support for international
  or multiple files.

* Irma QuickGUI

  Allows you to enable QuickFields--a more Windows-like look for
  enterable fields in a display session.

* Silent Mode installation option

-------------------
System Requirements
-------------------

This product requires at least a 486/DX 33MHz PC running
Windows 95 or Windows NT 3.51, with 12 MB RAM for Windows 95
and 16 MB RAM for Windows NT.

-----
Setup
-----

To install, invoke the Setup program from the EXTRA! Personal 
Client 6.1 distribution media. Follow these steps to ensure the
proper operation of the installation:

1.  Close all other applications on your desktop. This will 
    ensure that no system-wide shared files are in use by the
    operating system during setup.

2.  Make sure the environment variable TEMP is assigned to a
    directory with read/write access and 1.5 MB of space.

3.  Run SETUP.EXE from the root directory of the CD.

Please note:

(a) The Setup program will copy some system-wide shared files 
    to the Windows system32 directory on systems running
    Windows NT. However, the new files will not replace old
    files until the system is rebooted. If there is a message
    at the end of the setup asking you to reboot, you should
    do so to enable the new system files. 

(b) If you cancel Setup before it has completed and choose 
    to exit, Setup will delete all EXTRA! Personal Client
    files and directories that are created.

(c) We recommend that you do not install this product to
    the root of any drive.

(d) In previous versions, EXTRA! Personal Client was installed
    to a Personal Program group in Windows NT Program Manager.
    For this version, the product icons are installed to a
    Common Program Group.

-------------
Network Setup
-------------

EXTRA! Personal Client supports shared installation to a network.

NOTE: If your users have Windows 95 on their workstations, you
need to install from a Windows 95 machine to the server. If your
users have Windows NT 3.51 on their workstations, you need
to install from a Windows NT machine to the server.  Failure
to follow these guidelines will cause problems for clients using 
a different operating system than what was used to perform the
Network Server setup.

NOTE: Network Setup will not support IBM OS/2 LAN Server
version 3.0.

To install to a network, first perform the server setup:

1. Execute NETSETUP.EXE from the root directory of the CD.

2. Select your destination drive and your setup options.

3. NETSETUP will copy all EXTRA! Personal Client system and
   client setup files to your selected network server
   destination.  In the network server destination, there will
   be a SUMMARY.LOG file that contains the options you selected
   during the Network server setup.

4. If you want to have customized Sessions and Schemes, create
   them on your network server location before the client
   setup.  When the client setup is performed, all of your
   customized Sessions will be installed to the 
   client workstations. After you have made all the
   customization to your settings and schemes on the
   server, notify your network users to invoke NETSETUP.EXE,
   not SETUP.EXE to perform the Client-based installation. 
   Notice that the changes you made on the server will
   affect all the client users. If you make new changes after
   client installations, you will need to notify your network
   users to perform Client-based installation again.


5. If you are installing on Windows 95, look for the
   following:

	-- An entry on the Network Administrator's Start
	   Menu called "EXTRA! Personal Client - 32-bit". 
           The only item contained there is the EXTRA!
           Personal Client README.
	
	-- In the Add/Remove programs there will be an
	   entry titled "EXTRA! Personal Client 32". This 
           is where you would uninstall the server-based
           install of EXTRA! Personal Client.

   If you are installing on Windows NT 3.51, look for the 
   following:

	-- Creation of a "EXTRA! Personal Client 32-bit
           (Common)" Program Group.  This group will
           contain two icons: "README File" and "Uninstall
           Server-based EXTRA! Personal Client 32".  This
           is where you would uninstall the server-based
           install of EXTRA! Personal Client.

NOTE: If a user does not have write access to a server
installation of EXTRA! Personal Client (that is, network
rights for the server drive), the user will get a message
saying that the security file cannot be found when EXTRA! 
Personal Client is launched from the client.

There are two ways to correct this:

1. Give the user write access to the server.

2. Move the security file (default.esf) from the server to
   the client installation. In the registry, point to the
   security file on the client. The registry key is

   HKEY_LOCAL_MACHINE\SOFTWARE\ATTACHMATE\EXTRA!\
     SECURITY\SECURITYFILE

   Change the value of this key to point to default.esf on
   the client.


Next, perform the Client Setup:

1.  Execute NETSETUP.EXE from the server setup destination.
    For example, if the Administrator performed a Server Setup
    to the server \\MS\APPS in the path \programs\E!PC, the 
    client would perform a "File Run..." of the string

	\\MS\APPS\programs\E!PC\NETSETUP.EXE

2.  The client setup contains:
	-- Welcome screen
	-- Software License Agreement screen
	-- User Registration Information and Confirm
           Registration
	-- Select Installation Destination for EXTRA! Personal
	   Client - 32-bit
	-- Attachmate Forum on Microsoft Network Option
	-- Setup Summary
	-- Confirm Selections

3.  At the conclusion of client setup, the only EXTRA! Personal
    Client files that will be copied to the client workstation are 
    Sessions, Schemes, macro directories, and a file needed for
    Uninstall. A SUMMARY.LOG file will also be generated for both
    the Server and Client.  All EXTRA! Personal Client system files 
    will remain on the network server and the client will access
    them from the server.

NOTE: If APPN is the only server install option, \Profiles and
\Templates will not be copied to the client.

---------------------------------------------
Installing Over an Old EXTRA! Personal Client
---------------------------------------------

If you are installing EXTRA! over EXTRA! Personal Client 6.0 or
6.1, you must re-install all of the components that were
installed originally. For example, if you previously installed
all host types in 6.0, and you only used 3270, you should still
re-install all host types.  If you do not, some files grom your
original installation may not be compatible with files from your
current installation.

If you exit Setup during an overinstall, registry entries for the
old EXTRA! will be removed and will not be rewritten. You must
perform a clean install to rewrite the correct registry entries.  

---------
Uninstall
---------

To remove the product from a Windows 95 machine:

1.  Exit all EXTRA! Personal Client sessions and close all
    other applications.

2.  Run the Add/Remove Utility from the Windows 95 Control
    Panel.

3.  Select EXTRA! Personal Client to remove the installed
    product.

4.  The Add/Remove Utility deletes only files and directories
    installed or created during setup.  You must manually
    delete or remove any files or directories created after
    setup.  If you cannot delete any old files, reboot your
    system and try again.

NOTES:  (a) Do not run the Uninstall executable (UNINSTALL.EXE)
	included with the product.

	(b) Uninstall will not remove the EXTRA! Personal 
        Client directory from the PATH statement in
        AUTOEXEC.BAT.  You must delete this yourself.


To remove the product from a Windows NT machine:

1.  Exit all EXTRA! Personal Client sessions and close all
    other applications.

2.  Select and run the Uninstall icon from the EXTRA! Personal
    Client program group (UNINSTALL.EXE).  Do not use the File
    Run command.

3.  Uninstall deletes only files and directories installed or
    created during setup.  You must manually delete or remove
    any files or directories created after setup.  If you
    cannot delete any old files, reboot your system and try
    again.

NOTES:  (a) If you have installed hardware adapters for SDLC
	or DFT, you must remove these adapters using the
	Control	Panel before you uninstall the product.

	(b) Uninstall will not remove the EXTRA! Personal 
        Client directory from the PATH statement in
        AUTOEXEC.BAT.  You must delete this yourself.


--------------------
Registry Information
--------------------

You can find registry values created by EXTRA! Personal 
Client during installation in HKEY_CURRENT_USER\Software\
Attachmate\EXTRA!\6.1\UserInfo.

Also, a value can be found in HKEY_CURRENT_USER\Software\
Attachmate\EXTRA! called CurrentVersion. This value
indicates the current version of the software (6.1).


----------------------------------------------------------
Multiuser Login with Windows NT 
-----------------------------------------------------------

Since EXTRA! Personal Client is installed to a Common Program
Group, many different users can run the software using a
different user ID than the person who installed it.

The user who installs the product must first run SETREG2, 
select his/her user ID as the source, and select ".default"
as the destination.  This copies all registry settings from
HKEY_USERS\<userid> to HKEY_USERS\.default.

---------------
True Type Fonts
---------------

True Type Fonts are not supported in this release.

-------------------------------------
Macro recording on asynchronous hosts
-------------------------------------

The macro recorder automatically inserts WaitHostQuiet 
statements after every SendKeys operation. For asynchronous
hosts, the default Wait time may be too long. This
can easily be modified. For example, to wait for only
two seconds (rather than the default five), change all
the WaitHostQuiet statements to wait for a specific
user-defined timeout value and define that value at the
start of the macro. Then, when you want to change the 
value of the Wait time, you only have to make the change
in one place.

For example:

WaitValue = 2000 'define this once at start of macro
...
...
  WaitHostQuiet (WaitValue) 'change each WaitHostQuiet
statement to wait for this user-defined time.

-------------------
EXTRA! Basic Macros
-------------------

All EXTRA! Basic macros from all clients run on a single
thread. Therefore, when one client's macro displays a
dialog box, all other macros are temporarily suspended.

---------------------------------------------------
Backward-compatibility with 4.x EXTRA! Basic macros
---------------------------------------------------

The following 4.x EXTRA! Basic functions are not supported
in this release:

AllowUpdates		
BlockUpdates
GetFieldLength 		
GetFieldPosition	
GetKeystroke		
GetLayoutName
GetParameter
GetStringFromField
OpenLayout
PenSelect
ResetSystem
RunEXTRAMacro		
SearchField
SendStringToField
SessionOff		
SessionOn
SetParameter
StartKeystrokeIntercept
StopKeystrokeIntercept

More information on backward-compatibility can be found in
the EXTRA!.EBH header file that is installed in your Macros
subdirectory. This header file can also be used as an 
example of how to upgrade your existing macros to use OLE
Automation. The EPC_OLE.HLP help file also provides detailed
information on using OLE Automation.

-------------------------
Microsoft SNA Server
-------------------------

NetSoft is the default APPC router for an AS/400 connection. To
configure an AS/400 session with Microsoft SNA Server, you must
run the setup program using the Custom option instead of 
the Typical option. Specify the SNA Server as your APPC router.

-----------------------------
Compact Installation and APPN
-----------------------------

If you want to use DLC (802.2), SDLC, Cisco NCIA, or DFT
connectivities with a compact install, you must also select the
APPN node along with IBM Mainframe during installation. This
will install all necessary components.

---------------------
Creating New Sessions
---------------------

We recommend that you use the New Session Wizard to 
create new sessions and specify connectivities prior
to using the APPN Configurator to add peer 
connectivities.

------------------------------
APPN Configurator and Security
------------------------------

In the APPN Configurator, the User ID and Password for TP
Security are written in ASCII text to the .xcp file and are
viewable. To prevent this, turn on the hidden attribute
to the default.xcp file if TP Security is being used.  This 
security information will be encoded in a subsequent release.

-------------------------------
APPN Security and 3270 Sessions
-------------------------------

If your 802.2 DLC link connects to the SSCP session, but 
the session gets a sense code as soon as you log on, you may
need to change settings.  EXTRA! Personal Client 6.1 connects 
to the host as a PU2.1 in the default setting.  If APPN 
security is turned on at the mainframe, you need to change 
your local Network ID and CP Name.  You can change this with 
the APPN Configurator by editing the "Local Node" entry in 
your active configuration.

----------------------------------------
Connecting to PU2.1 or PU2.0 on the Host
----------------------------------------

Currently, our DLC (802.2) direct connect configuration is
set to negotiate either PU2.1 or PU2.0. This will function
properly with most VTAM configurations, but with older
VTAM/NCP configurations you may have to disable our
XID negotiation. To disable XID negotiation, load the
current configuration (Open Active in Nodecfg) and
change the link 'Back Level XID' to 'Back_Level_0'.
Remember that no negotiation will occur with this
setting. All frame sizes must be configured correctly
or a frame may be rejected by the system 802.2 device
driver. This will result in the PU being deactivated
and a 510 error on the OIA.

--------------------------
Connecting via 802.2 (DLC)
--------------------------

To use the 802.2 (DLC) connection with Windows 95, you must
use the 32-bit DLC drivers which are now in release candidate
stage from Microsoft. When these drivers are officially 
released, Attachmate will provide them to you upon request.

---------------------------------------------
EXTRA! Personal Client and Attachmate Gateway
---------------------------------------------

EXTRA! Personal Client will only connect via IPX/SPX to
ZIP! SNA Server 4.20 and higher. If you are using the 
Attachmate Gateway 3.10, a patch is available to allow 
you to use EXTRA! Personal Client.  Please contact 
Attachmate Customer Support to obtain the patch.

---------------------
TCP/IP to ZIP! Server
---------------------

You will be unable to connect GAP TCP via LANBroadcast for 
Windows NT & Windows 95 unless both the gateway and the 
workstation are on the same ring.

-----------------------------
Using SDLC or DFT Connections
-----------------------------

If you are using an SDLC or DFT connection, you will need to
install the hardware information files (.INF) located in the
base subdirectory where EXTRA! Personal Client 6.1 was
installed on your machine.

To copy these files using Windows 95:
  
1.  From the Control Panel, select Add New Hardware.

2.  Follow the instructions given by the Add New Hardware
    Wizard.

3.  When prompted, enter the path to the EXTRA! Personal 
    Client subdirectory and click OK.

To copy these files using Windows NT:

1.  From the Control Panel, run either the SDLC or the DFT
    applet.

    The applets will install the files and configure your 
    hardware automatically.

2.  For the changes to take effect, reboot your computer.

----------------------------------------
TN3270 Connections and Microsoft Network
----------------------------------------

If you are using a TN3270 connection and are also using the
Microsoft Network, you may experience problems when loading
a TN3270 session. The MSN dialog may appear during the 
connection process.

To avoid this problem, in Control Panel, select the 
Internet icon. Deselect the Use AutoDial option. This will
prevent the dialog from appearing when loading a session.

--------------------------------------------------
Windows 95 Ethernet Support and 802.2 Connectivity
--------------------------------------------------

When connecting a Windows 95 end node via Ethernet
802.2 connectivity to another EXTRA! Personal Client
end node (either Windows 95 or Windows NT), use a
zero XID (Block ID=000, PUID=00000). Configure the link
station NOT to activate at startup. Start the link
station manually using Node Manager. The first attempt
will fail with the message "Link Deactivated". The
second attempt will succeed. If the link station is
configured to activate at startup, a "Start Link Failed"
message will be generated during the Node Activation
process. Clear the error messages by clicking OK. The
link station should then activate automatically.

If you do not send a zero XID, XID negotiation 
errors will prevent the link from activating. If you
are connecting to a network node, the XID 
negotiation errors will not occur and both zero 
and non-zero XID's can be sent.

---------------------------
DFT and Irma3 Coax Hardware
---------------------------

If you are using a DFT connection with Irma3 Coax
hardware, you will need to download the microcode
that came with the hardware before you run the
client software. The downloaded microcode should
match how the hardware was installed through the
.INF process, either Irma in PJ Mode, or Irma
in IBM Mode.

-------------------------------------
IrmaLAN via IPX/SPX to ZIP! SNA Server
--------------------------------------

If you are using IrmaLAN via IPX/SPX to a ZIP!
SNA server, you can only open one session at
a time.


------------------------------------
Connecting to a Microsoft SNA Server
------------------------------------

In order to connect to a Microsoft SNA Server,
you need to install the SNA Server Client to
your workstation. If you need to obtain the 
client, we have provided a copy of the latest
release.

-----------------------------------
Migrating 802.2 (DLC) Configuration
-----------------------------------

After you migrate your 802.2 (DLC) configuration,
you must change the Activation-Type entry in the 
DFTLINK section of the default.xcp file from "YES"
to "NO". For example:

[Define_LS 3]
...
...
LS_Name=DFTLINK
...
...
Activation_Type=NO
...
...

----------------------
Migrated SDLC sessions
----------------------

If you have migrated an SDLC session, it will
not be automatically activated at startup. In 
order to activate the session automatically,
do the following:

1.  Start EXTRA! Personal Client.

2.  Choose "Open an existing session".

3.  Open your migrated SDLC session.

4.  Choose Options\Settings\Connection\Session.

5.  Select the "Activate on Startup" box and click
    Apply.

6.  Exit your session.

When you restart the session, the SDLC connection will
be automatically activated.

----------------------------------------------
OLE Automation Conflicts with Visual Basic
----------------------------------------------

Because of a conflict with some keywords in
Visual Basic, you must put brackets around the
EXTRA! Personal Client Delete and Close method
when calling these methods in Visual Basic.

For example:

Dim EXTRA as Object, Sessions As Object, Sess As Object
Dim Screen as Object

Set EXTRA = CreateObject("EXTRA.System")
Set Sessions = EXTRA.Sessions
Set Sess = Sessions.Item(1)
Set Screen = Sess.Screen
Screen.[Delete]
Sess.[Close]

--------------------------------
OLE Automation and WaitForCursor
--------------------------------

There is a known problem with WaitForCursor where it will
wait and then return False if the cursor is already in the
desired location.  

Given a Sess object for the current session, and a desired
row%, col% location, the code which will remedy this
problem is as follows:

rc% = True
If Sess.Screen.Row <> row% Or Sess.Screen.Col <> col%
  rc = WaitForCursor(row%, col%)
End If
'rc% now contains the correct results of the Wait condition.

----------------------------------
Printer Emulator Application Error
----------------------------------

An application error occurs if an attempt to enter
the printer emulator's configuration utility when
no printer has been configured in Windows.

Therefore, before choosing Options\Settings\Printer
or Options\Session Type\Device Type from your
session menu, connect a printer through the
Windows NT Print Manager or the Windows 95 Printers
folder.

---------------------------------------------------
Printer Emulator and Session Configuration Defaults
---------------------------------------------------

The printer emulator may generate unexpected or undesirable
output when the session configuration defaults are used.

The default settings prepared for an EXTRA! Personal
Client printer session were chosen with the intent of
meeting the needs of the largest set of users. However,
it may be necessary for you to edit those settings so
they will more accurately reflect your printing 
environment before you obtain the desired results.
You can access and edit the settings by selecting
Settings from the Options menu in the printer session
window.

Examples of this unexpected output and their cause include:

*  Printed text is word-wrapped to the next line, thereby
   extending the contents for one page to a second. This
   is caused by a default check in the Word Wrapping
   checkbox on the configurator's General property page.

*  Setting for margin, font size, lines per page, page
   orientation, or other options appear to have been ignored.
   This is most likely a result of the Honor Host Formatting
   radio button on the LU1/LU4 Property page having been
   selected by default.


-------------------------
Renaming Navigation Pages
-------------------------

The advanced editing functions of Navigations do not recognize
spaces or special characters as part of a valid page name. We
recommend that you do not use spaces or special characters
when renaming navigation pages.


----------------------------------------------------
Prompting for a Userid or Password During Navigation
----------------------------------------------------

When recording pages, all keystrokes, including userids
and passwords, are stored in the Navigation Path File. 
You can avoid storing this sensitive data by configuring the 
navigation engine to prompt for this information during playback.
This is done by editing the path that was recording by EXTRA!,
and inserting a user prompt.

To edit the path, do the following:

1.  Record the pages in your host application, including your
    logon screen.

2.  Select Global Preferences from the Options menu in your
    display session.

3.  Under the General tab, make sure the option Expand Page 
    Settings dialog box is checked on, and click OK.

4.  Select Page Settings from the Tools menu.

5.  Click on the Advanced tab.

6.  Click the Edit Paths button.

7.  Double-click on the words Direct paths in recording.
    You will see a list of all the pairs of pages in your host
    application that are linked together.

8.  Look for the pair that shows your logon screen on the left 
    and the screen that follows the logon screen on the right.
    For example, if you named your logon screen 'TSO Logon', and
    the screen that follows that is named 'Ready Prompt', look
    for the pair TSO Logon   >   Ready Prompt.  

9.  Double-click on that pair.  On the left side of the dialog
    box, you will see a list of terminal keys, and on the right 
    side you will see a box labeled 'Key entries in path'. The 
    Key Entries in path will list the keystrokes recorded to
    move from your logon screen to the next screen.  You may see 
    your userid and password listed in this box. You can edit
    this list of keystrokes so that, instead of having your
    userid and password sent automatically, you will be prompted
    for them.

10. Click on the line in the 'Key entries in path' box that 
    contains your userid or password.  (If your userid and
    password are both on the same line, highlight that line.)

11. Click the Delete button.  Your password will no longer be
    listed.

12. You now need to add a command to prompt the user for a
    password. Click the check box on the left side of the dialog
    box labeled 'Prompt User for Input'. Below that, you will
    see the words 'USER-INPUT-PROMPT' appear in the Edit Entry
    box.  

13. Delete the words 'USER-INPUT-PROMPT' from the Edit Entry
    box, and instead type in the prompt that you want to appear,
    such as 'Please enter your password:'. If you do not want to
    have your keystrokes displayed  when you type them, as in
    the case of a password, put the tilde character (~) at the
    beginning of the prompt.  This character will not be
    displayed, but it tells EXTRA! to display asterisks (*)
    instead of the actual characters that are typed.

14. Click the insert button.  

15. You can follow the same procedure for any other data that
    you wish to prompt for instead of storing it in the
    navigation file.

16. Click the OK button to exit and save your changes.

Now, when you navigate to a page or bookmark, you will be
prompted to enter a password when you reach the logon screen.
The navigation will pause until the data is entered, and then
send the data to the current cursor location before continuing
on to the next screen in the navigation path.

-----------------------------------
Saving Sessions and Creating Layouts
------------------------------------

You must save your session before you create a layout.
If you do not save the session first, the layout will
not run.


------------------------------
Windows 95 and 84-key Keyboard
------------------------------

If you are running EXTRA! Personal Client on Windows 95
and have an 84-key keyboard, you must go into the
system registry of Windows 95 and change the keyboard 
entry to key84.  This does not apply to Windows NT 3.51.


----------------------
Font and Window Sizing
----------------------

When a session with an autosized font and a
non-autosized window is viewed in windowed mode,
the font will not grow or shrink to fit the
window when a screen model switch occurs. You
can force the font to resize by maximizing and 
restoring the session window.

If you are using an autosized window and a
non-autosized font, and select a font size
that will produce a screen larger than the
physical display can contain, the session 
window will be sized to fill the entire display.
It will not include scrollbars. You can
force the scrollbars to appear by disabling
window autosizing.


------------------------------------------------------
LAT 1.0 and PATHWORKS V1.0 for Windows 95
------------------------------------------------------

PATHWORKS V1.0 for Windows 95 containing 
LAT 1.0 will not reliably support
more than one session.  Digital Equipment
Corporation will be releasing a patch
for LAT (1.0a) that will support more than one
session. Contact Digital Equipment Corporation
for more information on the patch.


----------------------------------
Dual Boot Systems and AUTOEXEC.BAT
----------------------------------

If your PC is configured for dual boot of the operating
system, setup may have trouble updating the path of your
AUTOEXEC.BAT file correctly. After setup is completed,
be sure to verify that the path statement points to
the correct partition.


------------------
END OF README.TXT
------------------
