==============================================================================
		Readme file for NetSoft Router
		     Copyright 1995 NetSoft
==============================================================================

This file updates the following product:

	     NetSoft NS/Router (R)
	     Version 4.12

The information contained in this Readme file may not be in 
your manual, but the functions and/or capabilities do exist in this
software version of NS/Router.  You should keep a copy of this 
Readme file with your manual.

The following is a summary of the updated information in this 
Readme file:

	  1.  Directory Structure and Files
	  2.  Microsoft SNA Server Special Requirements
	  3.  Eicon Gateway Special Requirements
	  4.  Twinax Link Special Requirements
	  5.  802.2 Link Special Requirements
	  6.  NetWare for SAA Physical Link now supports TCP/IP 
	      and Multiple Gateways
	  7.  PC Support V2R3 and Net ID Recognition
	  8.  Microsoft DLC for Windows for Workgroups 
	      Configuration Program (and how it affects Ethernet 
	      destination adapter addresses)
	  9.  Translation Table File OPEN Error
          10. Disabling the NS/Router Trace Option
          11. Bypassing the "Close NS/Router" Dialog Box
          12. Using the Novell Login User ID as PC Location Name 
	      with Elite/400
          13. Using the Novell Login User ID as PC Location Name 
	      with Netware
          14. Multiple 802.2 PU Support
          15. Elite/400 LAN Gateway MAXDATA must equal 1033
          16. Twinax Link RcvPacingLimit must equal 1
          17. How Setup affects your system (Virtual Device Driver 
	      Paths)
          18. Improving file transfers with 802.2 Connections
	  19. Special Requirements for Async
	

			Directory Structure and Files
			-----------------------------

The Router Setup program creates a default directory structure for 
all the files as indicated below.This is the default directory 
structure; your directory structure may vary depending upon the 
installation paths you have selected.

C:\RALLY!\NSROUTER (contains all the NS/Router and NS/Router Configurator 
files)

------------------------------------------------------------------------------
		
		 Microsoft SNA Server Special Requirements
		 -----------------------------------------

When you select the Microsoft SNA Server link, the Link Information
group box is empty and the Change... button is disabled (dimmed).
There is no link information dialog box because all link (and 
session) information is configured on the Microsoft SNA Server 
itself.

The Microsoft SNA Server physical link requires that a LAN adapter
be installed in your workstation. Communications over the Local 
Area Network (LAN) are accomplished through Microsoft's LAN Manager
 (Netbeui)
network software or Novell's NetWare (IPX/SPX) to the host. You must
have the current version of the required software for this link type
as follows:

  -  Microsoft LAN Manager (Netbeui) version 2.0C or later and
     Microsoft SNA Server version 2.0 or later.

  -  Novell NetWare (IPX/SPX) version 3.11 or later and Microsoft
     SNA Server version 2.0 or later.

When you use the Microsoft SNA Server physical link, you must install
the appropriate client software from the SNA server onto your workstation
before you can successfully communicate with the SNA Server. This
procedure is presented in summary form below.

For more detailed information, refer to your "Microsoft SNA Server
Installation Guide". It is assumed that you have already successfully
installed and configured your SNA Server.

Installing a Client Running Windows Version 3.1
-----------------------------------------------
In order to install the client software on your workstation, you must
specify an installation source; either a disk (the "Windows v.3.x
Client Disk" that is shipped with your Microsoft SNA Server),
or a network share where the SNA Server directories and files reside.
You can then execute Setup to install the client files. The CLIENTS
share, used by the client to install the SNA Server client software,
was created on the primary server when the SNA server software was
initally installed. A default installation path is provided; however,
you can change this default to specify another directory. By default,
Setup installs the client files in a directory called C:\SNA.

During installation, you must also specify whether the server(s) that
the client will be communicating with are in the local or remote domains.
Local indicates that the primary server containing the configuration
file is located on the same network domain as the client. If the server
resides on a different domain, indicate that the server is remote
and specify the primary server name and, optionally the backup server
name.

Setup client software is located in the Microsoft SNA Server home
directory on the primary server. Setup installs the required Microsoft
SNA Server files and directories onto your workstation and modifies
the system files as required.

Before beginning the installation, have on hand the interrupt value
from your network card and know whether your workstation is local
(on the same domain as the server) or remote (on a different domain
form the server). If remote, you must provide the names of the SNA
servers in the domain.

Installation Instructions
-------------------------
This procedure is presented in summary form below. For more detailed
information, refer to your "Microsoft SNA Server Installation Guide."

To install an a client running Windows version 3.1:

1. At the workstation on which you are installing the
client software, close any Windows version 3.1 system applications
that are running.

2. To install from disk, skip this step and proceed
with step 3. To install over the network, establish a connection to
the CLIENTS share on the server from which you will install the client
software and then type the following and press Enter.

  net use x: \\servername\clients

where x represents the unused logical drive on the computer on which
you are installing the client software and servername is the name
of the server from which you are installing the client software.

From the Windows Program Manager File menu, choose Run. In the Command
Line box, type the following command to start the client Setup program:

   x:\win3x\setup

An introductory Setup dialog box appears.

3. To install from disk (the "Windows v.3.x Client
Disk" that is shipped with your Microsoft SNA Server), put Disk
1 in drive A, type the following command and press Enter:

  a:\setup

An introductory Setup dialog box appears.

Choose the Help button to get assistance any time you are using a
dialog box. When you do, Setup displays a text box explaining the
choices you have at that point and the procedure to complete the dialog
box.

4. Choose the Continue button.

If you are installing from disk, the Client/Server Selection dialog
box appears. If you are installing over the network, the Installation
Path dialog box appears. Continue with step 6.

5. From the Client/Server Selection dialog box, choose
the Client button.

The Installation Path dialog box appears.

6. To accept the default path, choose the Continue button.

To change the path, delete the default path, type the new path, and
then choose the Continue button.If Setup detects more than one network
operating system on your workstation, the Network Operating Systems
screen appears. If you have only one network operating system on your
workstation, the SNA Server Location dialog box appears. Continue
with step 9.

7. In the Select Network Operating System dialog box,
select either the Microsoft Networking or Novell Netware option button,
or both.

8. Choose the Continue button.If you selected the Novell
Netware option button, in the Netware Domain Name dialog box, type
the NetWare domain name, and then choose the Continue button.<R>

The SNA Server Location dialog box appears.

9. To specify the location of the SNA servers in the
domain: For SNA servers in the local domain, choose the Continue button.For
SNA servers in the remote domain: Under the SNA Server Domain, select
the Remote Domain option button.In the Primary Server box, type the
name of the primary server for the remote client.If you choose to
designate a backup server, in the Backup Server box, type the name
of the backup server.Choose the Continue button.

10. SNA Server installs the necessary files.   When installation
is complete, the SNA Client Setup Finished dialog box appears.

11. Choose the Exit button. The SNA Server Client program
group appears in the Windows Program Manager   window.

SnaBase
-------
SnaBase is the fundamental component in an SNA server network. It
must be running before any other SNA component can start. It is the
"eyes" and "ears" into the domain of servers. SnaBase
must be loaded in order for your workstation to communicate with the
SNA Server.

When you install the client on your workstation the setup program
adds a line to your AUTOEXEC.BAT file which will automatically load
SnaBase (which builds a list of available services in the domain and
allows your workstation to connect to the server) when you boot your computer.

For more detailed information, refer to your "Microsoft SNA Server
Installation Guide."

------------------------------------------------------------------------------

		   Eicon Gateway Special Requirements
		   ----------------------------------

Before you configure and start the NS/Router you must have successfully:

1.  Installed Version 3 Release 1 or later of the Eicon Gateway.
    Refer to the "SNA Gateway Reference Guide" and "SNA LAN Gateway DOS
    and OS/2 Server Operator's Guide" that come with the product for
    detailed instructions on how to configure the gateway.

2.  Installed the following client software on your workstation:
    APPC Application Subsystem for Windows Version 1.01 or later. This
    software should have been provided or purchased at the time you 
    purchased your Eicon SNA Gateway. Refer to the "APPC Application 
    Subsystem for Windows System Administrator's Guide" that comes with
    the product for detailed instructions on how to install and configure
    the client software. This software allows you to configure and manage
    APPC LU 6.2 application resources (PUs, LUs, Modes, etc.) running on
    your Eicon SNA Gateway.

When you start the NS/Router and select the Eicon SNA Gateway physical
link, the Link Information group box is empty and the Change... button
is disabled (dimmed). There is no link information dialog box because
all link (and session) information is configured on the Eicon SNA
Gateway itself.

NOTE: You cannot run the client software for the Microsoft SNA Server 
at the same time you are running the client software for the Eicon 
SNA Gateway. This is because they both share the same API name.

The following brief summary is supplied for your convenience and outlines
the steps you need to complete to install and configure the Eicon Gateway
and the APPC Subsystem as listed above. This summary is meant to be a
companion to the information provided in the Eicon manuals cited above,
NOT a replacement.

Summary of Instructions
-----------------------

Eicon SNA Gateway side:
1.  Configure EICON Card: Run ECCARD CONFIG to configure your Eicon card 
    for an SNA Gateway. You must select the APPC/LU 6.2 protocol.
2.  Configure NODE: Run ECSNA CONFIG to configure NODE information. You
    must configure the node as a 3270 node. The Node Name must be
    matched by the APPC Subsystem Node configuration on the client side.
    Independent LU support must be set to YES. You must configure the
    Maximum Number of Logical Units to 000 and set all LU Allocations 
    to N (not used) on the LU Configuration screen.
3.  Configure Server: Run ECLANCFG to configure the server name, LAN
    protocol and software Interrupt used (SC or SA)
4.  Sample Gateway load batch file:
	
        ECBIOS START /Int SA
	ECCARD START
	ECLAN START SERVER
	ECSNA START /N EICONGW

Workstation side:
1.  Install ECLAN client software at the workstation (DOS software).
2.  Install the APPC Subsystem software (see above) on the client or
    workstation (Windows software). The APPC group will be created.
3.  Run the Console program under Windows at the APPC group. Configure
    the Nodes, Local LUs, Modes and Remote LU sections. It is recommended
    that you check the "Already Defined" checkbox if all node parameters have
    already been configured on the Gateway; otherwise, the Node name must
    match the Node Name configured on the Eicon Gateway exactly. The 
    Gateway name must match the Sever name configured on the Gateway 
    exactly.
4.  Configure the following on the NS/Router Configurator main screen
    Local LUs Alias and name are configured on the NS/Router Configurator
    main screen under PC Location Name. Add Mode QPCSUPP with session
    limit of 32. Remote LU Alias and Name are configured as AS/400
    System Names.  Mode name must be QPCSUPP.
5.  At DOS, run ECLAN CFG to configure client name, LAN protocol used,
    software interrupt used (Int 5C or 5A).
6.  Make sure the SYSTEM.INI file contains the [Ehn386] section contains
    the following:
	device=path\VNABIOS.386
	NAHeapSize=52
    (note that the path is where VNABIOS.386 is installed, which is normally
    at c:\windows\system.
7.  At DOS, sample.client load batch file: (must load TSR before Windows)
	ECLAN START CLIENT
	ECLAN USE / SNAME EICONGW
    (note that EICONGW should be the name of the configured gateway).
8.  Start Windows.
9.  Load the APPC Subsystem by double clicking on the Console icon.
10. Double click on the Workstation icon in the Navigator window to reveal
    the APPC Subsystem icon. Select the APPC Subsystem icon and then
    click on the Start button to start the APPC Subsystem.
11. At this point you can start the NS/Router.

------------------------------------------------------------------------------

		       Twinax Link Special Requirements
		       --------------------------------

You must install the twinax adapter handler supplied by the manufacturer
of your twinax card. (If you are using an IBM adapter handler,
make sure that you use E5250AH.COM for an ISA type card
and WSEAH.COM for a Micro Channel type card).

You must also load a TSR (Terminate and Stay Resident) program before
you start Windows.

The TSR program is used by the emulator to access the adapter interface
software (e.g., IBM LAN Support Program) more efficiently than Windows when
a DOS application is running. The TSR is copied into your NS/Router
installation directory when you install the NS/Router (default NSROUTER).

The syntax for the TSR program command line is:

     NSTWINAX [nn] | /M /U /?

The software interrupt to use is specified by "nn" which is
a hex value from 60h to 6Fh. If "nn" is not specified, NSTWINAX
examines the interrupt range and uses the first unused interrupt.
If "nn" is specified, NSTWINAX uses that interrupt regardless
of the interrupt's availability.

The default Maxdata is 4105 and cannot be changed.

The /M argument is used to specify that the maximum memory allocation
(the maximum amount of memory buffers) are to be used. This option
should be used when you are connecting three or more sessions. If
you are running two sessions or less and you want to conserve the
memory usage, you do not need to specify the /M argument.

The /U argument is used to unload the NSTWINAX program from memory.
If used, it should be the only argument specified on the command line.

The /? argument is used to display a list of valid arguments for the
NSTWINAX command line.

The Twinax TSR needs to be loaded before starting Windows and any software.
DO NOT unload NSTWINAX from a DOS window running under Windows or
you will cause memory problems and unpredictable results may occur.

When setting up your environment, perform the following memory management
steps to prevent Windows from interfering with the twinax address:

1. Add the following statement to your CONFIG.SYS file:

    DEVICE=C:\DOS\HIMEM.SYS

2.  Exclude the twinaxial adapter RAM address range from EMM386
by adding the following statement to your CONFIG.SYS file:

    DEVICE=C:\DOS\EMM386.EXE X=CC00-CCFF

    where CC00-CCFF is the twinax adapter address range.

3.  Add the "EMMExclude" statement to your SYSTEM.INI file under the [386Enh]
section header and set the value to the same range that you exclude in the
EMM386 statement in your CONFIG.SYS file (for example, EMMExclude=CC00-CCFF).
If you exclude more than one range in EMM386, add multiple EMMExclude
statements to SYSTEM.INI.
------------------------------------------------------------------------------

		     802.2 Link Special Requirments
		     ------------------------------

If you are running Windows in Standard mode, you must load a TSR (Terminate
and Stay Resident) program before you start Windows. (If you are running
in 386 Enhanced mode, you do NOT need to load the TSR. A virtual device
driver is automatically loaded instead)

The program is used by the emulator to access the adapter interface software
(e.g., IBM LAN Support Program) more efficiently than Windows when
a DOS application is running. The 802.2 TSR is copied
into your NS/Router installation directory when you install the NS/Router.

The syntax for the TSR program is:

   NS8022 [ [nn] [MAXDATA=x] [L=#] | /U

The software interrupt to use is specified by "nn," which is
a hex value from 60h to 6Fh. If "nn" is not specified, NS8022
examines the interrupt range and uses the first unused interrupt.
If "nn" is specified, NS8022 uses that interrupt regardless
of the interrupt's availability.

The MAXDATA value to support is specified by "x,"
which can be 265, 521, 1033, 1929 or 2042. The value specified must
be equal to or greater than the MAXDATA value that you configured
in the Router Configurator in the 802.2 LLC Link Driver
Advanced Options dialog box (default 1033). If "x" is not
specified, the default value of 1033 is used.

The additional memory required by the TSR program is dependent upon
the MAXDATA value specified on the command line, as shown below:

MAXDATA          Memory
-------          ------
265               25K
521               27K
1033              30K (default)
1929              37K
2042              38K

The number of link stations (PUs) you will be using is specified
by #, which must be greater than or equal to the number of
PUs that you defined in your router configuration file. If # is not
specified, the default of 1 is used.

The /U argument is used to unload the NS8022 program
from memory. If used, it should be the only argument specified on
the command line.

The 802.2 TSR (NS8022.EXE) needs to be loaded before starting Windows
and any software. DO NOT unload NS8022 from a DOS window running under
Windows or you will cause memory problems and unpredictable results may
occur.

------------------------------------------------------------------------------

   NetWare for SAA Physical Link Now Supports TCP/IP and Multiple Gateways
   -----------------------------------------------------------------------

The NetWare for SAA physical link now supports TCP/IP and multiple gateways.
Refer to the extensive online help for information on how to configure
the TCP/IP and multiple gateways.


If using the NS/Router with Netware for SAA Version 1.3B and above, you
must use the Novell LAN Workplace TCP/IP stack if connecting to the SAA
Gateway via the TCP/IP TLI protocol. 

-------------------------------------------------------------------------------

		   PC Support V2R3 and Net ID Recognition
		   --------------------------------------

If you have used Version 2 Release 3 of the PC Support install program to
configure single or multiple PUs definitions and no Net IDs were specified
for AS/400 systems, PC Support assumes they are blank and issues the blank
Net ID when the PCS router is started. However, when NS/Router configurator
imports this blank Net ID condition, NS/Router assumes the Net IDs are
"APPN" and may not work until you change the following lines in your
NS/Router configuration file (*.RTR) under each and every [PartnerLUn]
section (where n is a number) as follows:

Change:

PartLUNetName=APPN

To:

PartLUNetName=

If you do not change these lines, you may receive an error status code
(1500-0003-00000004) and you will not be able to make a successful
connection.

If you are connecting two different AS/400s on two different networks you
must list the network name under each [PartnerLUn] section. The following
example uses an AS/400 system named NS400B10 ont NET1 and AS/400 system
named NS400F10 on NET2:

[PartnerLUn]
PartLUAlias=NS400B10
PartLUNetName=NET1

[PartnerLUn]
PartLUAlias=NS400F10
PartLUNetName=NET2

------------------------------------------------------------------------------

       Microsoft DLC for Windows for Workgroups Configuration Program
       --------------------------------------------------------------

The NS/Router Configuration 802.2 Destination Adapter address defaults
to a non-reversed 802.2 address (as opposed to an Ethernet bit-reversed
address).

If you use an Ethernet adapter to attach to your network, you can have the
NS/Router Configurator convert your adapter address so that it will
be properly recognized by your network by selecting the Use Converted
Address check box on the Add 802.2 LLC Destination Adapter screen.
This conversion may be necessary because the address transmitted will
be bit reversed before it is received.

If you are using the Microsoft DLC for Windows for Workgroups configuration
program you do not need to use a converted address because the Swap
protocol parameter, which is enabled by default, performs bit-swapping
when Microsoft DLC is bound to an Ethernet driver.

-----------------------------------------------------------------------------

		  Translation Table File OPEN error
		  ---------------------------------

You may encounter the following error message when you attempt to open a
router configuration file (.RTR) that was created in a version of NS/Router
configurator earlier than 4.1 (which has support for multiple languages).

   "Translation table file OPEN error.
    File name: `d:\path\xxxxx\xxxxx.map'
    Load with internal translation table?

  where d\path is the drive and path where the product was installed and
  xxxx is the name of the file

This is caused by the fact that versions before 4.1 used a type G default
translation table. Because a default translation table was used, the
"TranslateTable=" entry in the router configuration file under the
[Workstation] heading was left blank or the specified Translation Table
or path is no longer valid.

In order to use an older router configuration file with NS/Router version 4.1,
the TranslateTable= entry must now specify one of the several different
translation tables that are available for use. To accomplish this, perform
the following steps:

1. From the NS/Router Configurator main window, open the router configuration
   file that you want to use.

2. Click on the Preferences button. This will take you to the Preferences
   dialog box.

3. Select the Host\PC Code Page drop-down list box and click on the
   type of translation file you wish to use. You can use the default
   translation table (the first one listed) but you must still actually
   drop it down and click on it in order for the changes in the router
   configuration file to take effect.

4. Choose OK

5. Use the File:Save menu option to save the modified router configuration
   file.

The error message should not re-occur.


NOTE: If you created your own customized translation table called, for
      example, `mytable' and modified the TranslateTable= entry so that
      it read TranslateTable=[d:\path\]mytable, you should not receive
      any error messages and NS/Router will continue to use your
      customized translation table.

------------------------------------
Disabling the NS/Router Trace Option
------------------------------------
To disable the Trace option on both the NS/Router Status bar and
the File: Diagnostics menu, locate the [E400RTR] section header of
your router configuration file and modify the following keyword:

   DisableTrace=1

To reinstate the Trace option, change the 1 back to a zero (0).

Save the modified Router file (.RTR)

------------------------------------------
Bypassing the "Close NS/Router" Dialog Box
------------------------------------------
The NS/Router, by default, displays a "Close NS/Router" dialog box
when you attempt to close the router when there are still active
connections to AS/400 systems. You must respond to this dialog by
choosing either OK or Cancel.

If you want to bypass the "Close NS/Router" dialog box, locate the
[E400RTR] section header of the router file and modify the
following keyword:

   HardClose=0 to HardClose=1

To reinstate the dialog box, change the 1 back to a zero (0).

Save the modified Router (.RTR) file.

-----------------------------------------------------------------
Using the Novell Login User ID as PC Location Name with Elite/400
-----------------------------------------------------------------
Gateway Link
------------
If you are using the Elite/400 GW as your physical link and the
IPX/SPX workstation to gateway link, you can elect to use the
first eight characters of the NetWare Login User ID as the Location
Name in the PC Information group box on the main NS/Router
Configurator screen. NOTE: The first character of the NetWare
User ID must be a letter.

-------------------------------------------------------------------
Using the Novell Login User ID as the PC Location Name with NetWare
-------------------------------------------------------------------
for SAA
-------
If you are using the NetWare for SAA as your physical link and you
are using the IPX/SPX transport protocol, you can elect to use the
first eight characters of the NetWare Login User ID as the Location
Name in the PC Information group box on the main NS/Router
Configurator screen. NOTE: The first character of the NetWare
User ID must be a letter.

-------------------------
MULTIPLE 802.2 PU SUPPORT
-------------------------

The maximum 802.2 connections (link stations) is dependent upon the
MAXDATA size specified in the Router Configuration file that you
are using.

If MAXDATA is configured for less than 1033, the maximum number
of PUs that can be supported is 10.
If MAXDATA is configured for 1033 or greater, the maximum number
of PUs that can be supported is 6.

If you are using the VNS8022.386, 802.2 Virtual device driver
-------------------------------------------------------------
The number of link stations that you specified in the Router
Configuration file must also be specified in the SYSTEM.INI file
by typing the following lines under the [VNS8022.386] heading:

	Maxdata=nnnn
	MaxLinkStation=#

where nnnn must be equal to or greater than the MAXDATA value that
you configured in the Router Configurator in the 802.2 LLC Link
Driver Advanced Options dialog box (default 1033). If nnnn is not
specified, the default value of 1033 is used.

where # is the number of link stations. This number must be greater
than or equal to the number of link stations you specified in the
Router Configuration file. If MAXDATA is configured for less than
1033, the maximum number of PUs that can be supported is 10. If
MAXDATA is configured for 1033 or greater, the maximum number of
PUs that can be supported is 6. If # is not specified, the default
value of 1 is used.

Also see the NOTE ON ENVIRONMENT SETTINGS section.

If you are using the NS8022.EXE, 802.2 TSR
------------------------------------------
The number of link stations that you specified in the Router
Configuration file must also be specified on the DOS command
line when you load the TSR.
For example:

	NS8022 maxdata=nnnn L=#
	
Where nnnn must be equal to or greater than the MAXDATA value that
you configured in the Router Configurator in the 802.2 LLC Link
Driver Advanced Options dialog box (default 1033). If nnnn is not
specified, the default value of 1033 is used.

Where # is a number that is equal to or greater than the number of
link stations (PUs) that you will be using as defined in your
router configuration file. If MAXDATA is configured for less than
1033, the maximum number of PUs that can be supported is 10. If
MAXDATA is configured for 1033 or greater, the maximum number of
PUs that can be supported is 6. If # is not specified, the default
value of 1 is used.

Note on Environment Settings
----------------------------
You must also set up the correct environment for the extra link
stations that you have added:

Examples for a few of the most common environments are provided
below. Refer to your Network documentation for complete details.

IBM LAN Support Program
If you are using the IBM LAN Support Program, you must add the
necessary parameters to the appropriate driver in your CONFIG.SYS
file. The affected driver is the DXMT0MOD.SYS. The extra stations
parameter (EST=nn) must be equal to or greater than the number of
link stations (PUs) that you configure in your router configuration
file. Additionally, if you are using another application that
requires a SAP, you might also need to modify the extra SAPs
parameter (ES=nn) for an additional SAP. Refer to your IBM LAN
Support Network documentation for detailed information.

Novell NetWare Shells
If you are using the Novell NetWare Shell program IPXODI, you must
modify the shell program configuration file NET.CFG.  Under the
LANSUP section modify the "Stations nn" line so that nn is a number
equal to or greater than the number of link stations (PUs) that you
configure in your router configuration file.  Additionally, if you
are using another application that requires a SAP, you might also
need to modify the extra SAPs nn parameter for an additional SAP.
Refer to your Novell NetWare documentation for detailed
information.

Microsoft DLC for Windows for Workgroups
If you are using Microsoft DLC for Windows for Workgroups
configuration program, the default settings for SAPS (3) and
Stations (20) (located on the Microsoft DLC Configuration dialog
box in the Advanced Protocol Settings group box) will normally
work, but if you must change the number of stations, remember that
you need 1 station per PU in addition to the other stations used
by your network (usually 2). Refer to the Windows for Workgroups
Resource Kit for detailed information.

---------------------------------------------
ELITE/400 LAN GATEWAY MAXDATA MUST EQUAL 1033
---------------------------------------------

The Elite/400 LAN Gateway link MAXDATA defaults to 1929 and the
NS/Router configurator MAXDATA defaults to 1033. This can cause
several problems such as: when a long frame is sent to the AS/400
it will be truncated, when a shared folder file is copied error
messages will be encountered and the workstation link will be
dropped, when file transfer upload operations are attempted error
messages will be generated (e.g., function=06, return code=5400,
operating system error, etc.).

To resolve this conflict, you must change the Elite/400 LAN Gateway
MAXDATA from the default 1929 to 1033 on the command line in the
Elite/400 Gateway batch file that is created when you exit the
configuration program. The command line used in the example below
would be used for an 802.2 link:

L8XGX /3 RX_MAXDATA=1033 TX_MAXDATA=1033

For details, refer to your Elite/400 LAN Gateway manual.


Additionally, certain adapter and IPX settings on the Elite/400
Gateway can create problems when file transfer upload and shared
folders copy operations are attempted. The cause of these problems
is that the Gateway TR adapter is opened by IPX with a default MAX
frame size of 1144 causing the Gateway link to the AS/400 to be
dropped and reestablished and issuing various generic error
messages. The following solutions should be implemented.

If the Elite/400 Gateway to AS/400 link is 802.2 token ring, IBM
LAN Support Program or equivalent must be used. The token ring
adapter must be opened with a transmit MAXDATA size of at least
1929. This can be achieved by performing the following steps:

1.  If the IBM LAN support program NetBIOS driver DXMT0MOD.SYS the
    following     should be specified in the CONFIG.SYS file:

    DXMT0MOD.SYS DS=1944 EST=Y ES=Y ST=? S=? C=? N=?

    where "?" values can be found in your NetSoft GCP User's Guide,
    depending on the number of workstations supported; Y is 1 if
    IPX is not used and 2 if IPX is used.

2.  If DXMT0MOD.SYS is not used and IPX is used to open the
    adapter, you must specify:

    IPX o,tbz=2048

    or for ODI IPX driver in the NET.CFG:

    Link Driver LANSUP
      MAX FRAME SIZE 2048

Additionally, the controller description on the AS/400 must be
set to:

SWITCHED DISCONNECT=*NO

for both SDLC and token ring connections; otherwise, the AS/400
will periodically drop the link to the gateway if there are no
outstanding sessions with any workstation.

---------------------------------------
TWINAX LINK RcvPacingLimit MUST EQUAL 1
---------------------------------------

If you created a router configuration file (*.RTR) with version
4.01 or earlier of the NS/Router configurator, the RcvPacingLimit
value was automatically set to 7 for all links.

If you are using the Twinax link, note that it can only support a
RcvPacingLimit of 1.

To resolve this problem, manually modify the following line under
both [ModeProfile#] sections (where # is a number) in the router
configuration file (*.RTR):

RcvPacingLimit=1

or you can re-create the router configuration file using version
4.02 or later of the NS/Router configurator, which now
automatically sets the RcvPacingLimit to 1 for Twinax links.

-----------------------------------------------------------
HOW SETUP AFFECTS Your System (Virtual Device Driver Paths)
-----------------------------------------------------------

In addition to the entries that the setup program makes in the
WIN.INI file (see your NS/Router manual for details) the setup
program also makes the following entries in your SYSTEM.INI file
under the [386Enh] section heading (depending on the links that
you chose to install):

DEVICE=C:\RALLY!\NSROUTER\VNS8022.386    (virtual device driver
					  for the 802.2 link)
DEVICE=C:\RALLY!\NSROUTER\VNSAINTD.386   (virtual device driver
					  for the SDLC link)

------------------------------------------------
IMPROVING FILE TRANSFERS WITH 802.2 CONNECTIONS
-----------------------------------------------

When using the NS/Router with an 802.2 connection, large file
transfers may time out and terminate after approximately 4 minutes.
To correct this and provide better and more consistent file
transfer performance,  you must change the value of RcvPacingLimit
from 7 to 4.  RcvPacingLimit is located in the .rtr configuration
file, and may be edited using a basic text editor.

If you have any further questions on file transfers, please
contact Attachmate Customer Support for assistance.

---------------------------------------
Special Requirements for the Async Link
---------------------------------------

The Async link supports COM serial ports based on the 8250 chip; 
however, High Performance third party serial cards and drivers 
may not be compatible.

NOTE: A 16550 UART chip is required for reliable communications
when using a line speed of 9600bps or higher. You must add the
following entry to the SYSTEM.INI file under the [386EHN] section: 
COMnFIFO=0, where n is the number of the COM port that you are using.
This is done so that the FIFO buffer of the COM port is disabled.

=====================================================================
		End of Readme file  for NS/Router.
=====================================================================