24 November, 1994
Simware, Inc.

Pointers for Installing and Using the Remote LAN Access (RLA) feature
---------------------------------------------------------------------

1. The amount of available DOS memory you have before loading Windows
   affects the number of applications you can have running in Windows.
   To maximize the amount of DOS memory available, the RLA.BAT file
   prefixes each call to load a driver with "LH".  This is a call to
   the DOS LOADHIGH command to load the driver in upper memory if
   possible.  If you are using another memory manager, these calls
   will have to be modified appropriately.

2. It is possible to free some DOS memory by using the "/D" option
   when loading IPXODI.  You may also want to try the "/A" option,
   which saves more memory but may cause certain LAN-based applications
   to hang.

3. Only attempt to run large applications from LAN drives if you are
   prepared to wait a while.  Even the fastest RLA connection is much
   slower than a local LAN connection.  If you're going to be using
   the application over RLA sessions often, it will improve performance
   to have it installed on your hard disk.

4. If you plan to run TCP/IP sessions over RLA, and aren't using the
   A2B TCP/IP stack, you must configure your TCP/IP stack for an
   ODI/Ethernet interface.  The DOS RLA drivers provide an ODI interface
   to the LAN over the async or X.25 connection.  Depending on the
   stack you're using, you might have to run the RLA.BAT file before
   configuring your stack.
   If you later decide to use TCP/IP to a SLIP or PPP server, the TCP/IP
   stack will have to be reconfigured to SLIP or PPP.  Remember to set it
   back to ODI before attempting to do TCP/IP over RLA again.

5. Copying a file from one LAN directory to another will result in the file
   being downloaded from the source directory over the connection and then
   uploaded again to the target directory.  There is no NCOPY equivalent.  
   Of course you can open a DOS box and run the NCOPY command from there.

6. Attempting to run a high speed RLA connection may cause problems if the
   client PC has an older model UART chip.  The 16550 buffered UART provides
   the best support for high speed connections.  Older models (8250 to 16450)
   may cause problems.
   Note that a 16550 UART is a *REQUIREMENT* on the RLA async gateway.

7. If you can't find an initialization string for your modem in Session Setup,
   try using a the string for a similar modem from the same manufacturer.  If
   this fails, try using the "Generic" string.

8. Some users may experiance a delay when exiting A2B after an RLA session,
   during which Windows appears to be locked up.  THIS IS NOT A HANG.  The delay
   should last no more than 30 seconds, and then Windows should be active.  We 
   are working on improving this.
