=======================================================================
  README file for NetSoft NS/Midrange Bundle (TM) for AS/400 Access
                      Copyright 1996 NetSoft
=======================================================================
           
           
This file updates the following product:           
           
                NS/Midrange Bundle for AS/400 Access
                Version 2.01         
           
Although the information contained in this Readme file may not be in
your 6-page foldout or the product's online Help, the functions and/or
capabilities do exist in this version of the product.
           
You should keep a copy of this Readme file as a reference.  
           
Updated information in this Readme file includes the following:
           
1. Physical Link Special Requirements
2. Running 16-Bit APPC Applications Under Windows 95
3. Using NetSoft Dynamic Link Libraries  
4. Premature Installation Failure         
5. AnyNet PTF Requirements        
6. Known Problems           
           
-----------------------------------------------------------------------
           
           
                  Physical Link Special Requirements
                  ----------------------------------
           
           
The 802.2, NetWare for SAA and Microsoft SNA links have the following
special requirements:
           
           
802.2 LLC  (TOKEN RING OR ETHERNET)   
-----------------------------------  
In order to use the 802.2 LLC link type, you should have Microsoft's
32-bit DLC Protocol installed on your PC.  Previous versions of
NetSoft's NS/Router was capable of using 16-bit DLC protocols but this
capability has been removed in this version. 
          
NOTE: The Microsoft 32-bit DLC diskette included in this product is for
use with Windows 95 only and not with Windows NT.  Microsoft ships DLC
support with the Windows NT product, and those drivers should be used
in that environment.  The user should not install the NetSoft-supplied
Microsoft 32-bit DLC on Windows NT.  If you previously installed a beta
(included with NS/Elite v1.10) or any previous version of the 32-bit
driver, install the version included with this product (v4.10.990).
Read the readme file on the Microsoft 32-bit DLC diskette before
installing the new version.  
           
           
Installing Microsoft's 32-Bit DLC Protocol 
           
1.  From the Start menu, click Settings/Control Panel.
2.  From the Control Panel, click Network.     
3.  Click Add.           
4.  Select Protocol.           
5.  Click Add.           
6.  Click Have Disk.           
           
NOTE: If "Microsoft/RRC" is listed in the Manufacturer's list box,
select it before selecting the Have Disk button.     
           
7.  A dialog will appear that asks for an installation disk. Insert the
    diskette containing the 32-bit driver and specify d:\dir where d is
    the diskette drive and dir is the directory containing the driver
    files.           
8.  Select Browse to find the protocol. The program will search
    automatically for the appropriate file to install the protocol.
9.  Select OK and the install will begin.           
           
           
The 32-bit protocol will now be installed. If you installed NS/Elite
prior to having installed the 32-bit protocol, you will need to reboot
your PC before launching NS/Elite.
           
           
           
NETWARE FOR SAA           
---------------           
In order to use the NetWare for SAA server link, you must first have
installed:
           
- IPX/SPX transport protocol or           
- TCP/IP transport protocol.           
           
           
MICROSOFT SNA SERVER           
--------------------           
The Microsoft SNA Server Client software is installed by the NS/Elite
setup program. These same drivers can be installed under Windows 95 and
Windows NT 3.51. Alternatively, the Windows NT client found on the SNA
Server CD can be used instead of the version that ships with NS/Elite.
       

NETSOFT'S ELITE/400 LAN GATEWAY        
-------------------------------       
If you install this product on a PC that is currently using IPX/SPX
transport to connect to an Elite/400 LAN Gateway, you may
experience certain failures.  To resolve this problem, you must install
an updated gateway link driver so that you can connect to it when using
IPX/SPX transport.
    
An updated gateway link driver (LPX5XG6I.EXE) is available on the
NetSoft BBS under filename, LPX5X.ZIP, and in the DOS Products section
under the AS/400-Midrange Patches/Fixes heading on the following URL
(page) of the NetSoft website (www.netsoft.com):    

http://www.netsoft.com/products/patches.htm

    
To replace the driver, do the following:    
    
1. On the Elite/400 LAN gateway PC, rename the existing file with a
   .OLD extension.
2. Copy the new link driver to the Elite/400 LAN gateway install
   directory.
3. Quit and restart the gateway.    
    
The TCP/IP transport does not require this new driver; no upgrade is
needed.
    
Also, the following limitations apply to the Elite/400 LAN Gateway.
- Supports only 31 sessions per workstation.        
- Does not support incoming allocates.        
     
    
-----------------------------------------------------------------------
           
         Running 16-Bit APPC Applications Under Windows 95
         -------------------------------------------------
           
In order to provide compatibility and allow you to run your existing
16-bit Windows 3.1 APPC applications under Windows 95, NetSoft has
provided a way for you to replace the standard EHNAPPC.DLL and
EHNRTRW.DLL 16-bit in/16-bit out modules with new modules that will
accept 16-bit application calls and convert them to 32-bit mode.  These
new modules have the same names as the standard modules (EHNAPPC.DLL
and EHNRTRW.DLL).  You are prompted to make this decision during the
product installation process.
          
If you choose to install the new 16-bit in/32-bit out modules, the
installation program copies the new modules into the Windows 95
system directory.  If the old modules are NetSoft modules, they are
saved with an extension of .16B.  If the old modules are other than
NetSoft modules, they are saved with an extension of .OLD.  The new
16-bit in/32-bit out modules only communicate with the NetSoft 32-bit
NS/Router.  If you are using another router, do not choose to install
the new 16-bit in/32-bit out modules.
           
           
-----------------------------------------------------------------------
           
              Using NetSoft Dynamic Link Libraries
              ------------------------------------ 
           
If you develop Dynamic Link Libraries that call NetSoft DLLs (or DLLs
from any other party), in order to avoid any potential access
violations during termination processing, you should observe the
following about how the operating system manages DLLs in Win32.
        
There generally are two ways that a process can unload a DLL from its
address space:
- by calling FreeLibrary, or        
- by calling ExitProcess        
        
FreeLibrary is called explicitly from within your application.
ExitProcess can either be called explicitly by your application or
implicitly (when the primary thread of the process returns or a console
process receives a Ctrl+C or Ctrl+Break signal).  FreeLibrary can only
be called for a DLL that is linked to dynamically (using LoadLibrary
and GetProcAddress).  When a DLL is linked to statically (i.e., with an
import library), generally the DLL can only be unloaded by calling
ExitProcess.
        
FreeLibrary causes a single DLL to be unloaded, whereas ExitProcess
unloads each and every DLL loaded by the process, in no particular
order.  For example, let's say that DLL (A) loads another DLL (B).  If
DLL A gets unloaded by FreeLibrary, it can still call DLL B in its
termination processing.  If DLL A gets unloaded by ExitProcess, it can
not rely on DLL B still being loaded, and attempting to call it could
cause an invalid page fault.
        
To avoid this situation, the programmer must use the verb
EHNAPPC_Cleanup.  When the user loads and unloads the E32APPC.DLL
library multiply times in the application or if the user uses the
static link library option, the EHNAPPC_Cleanup verb must be called for
every unload library operation before ending the application.  The user
SHOULD NOT call EHNAPPC_Cleanup to clean up E32APPC.DLL when the
application is in the DLL_PROCESS_DETACH part of a DLL, because the
needed supporting modules are already unloaded by the system.
        
        
                 Premature Installation Failure
                 ------------------------------
        
If you experience premature failure during an NS/Elite product
installation process, your computer may contain some files and registry
entries that require removal before you run setup again.
        
To remove all parts of an NS/Elite product manually, follow these
steps:
           
1.  Inside the Windows 95 Control Panel, double click on the
    Add/Remove Programs icon.  In the Add/Remove Programs dialog,
    highlight the NS/Elite product to be removed and then click on the
    Add/Remove button (or double click on the NS/Elite product to be
    removed).  After the uninstall is complete (note the result at the
    bottom of the dialog), click OK and then OK again to exit the
    uninstall and the Control Panel.  If uninstall does not work, you
    will have to remove the registry entry that causes the product to
    be listed in the Add/Remove Programs software list.  Step 3 below
    will address this item.
        
2.  Manually delete the NetSoft directory and all of its folders/files
    using Explorer or File Manager.  Manually delete the NetSoft fonts
    under the \windows\fonts subdirectory.  Also, delete the NS Elite
    folder (subdirectory) under \windows\startmenu (or
    startm~1)\programs, and delete the NS/Elite-related desktop folders
    under \windows\desktop.
        
    WARNING! ONLY EXPERIENCED SYSTEM ADMINISTRATORS SHOULD PERFORM THE
    NEXT TWO STEPS REGARDING REGISTRY EDITING, AND IT SHOULD BE DONE
    ONLY WITH GREAT CAUTION.  EDITING THE REGISTRY CAN CORRUPT YOUR
    OPERATING SYSTEM ENVIRONMENT.         
        
3.  Under the Start menu, click Run and type "regedit" in the dialog
    field ("regedt32" for Windows NT), and click OK. The registry
    editor will be launched.  The user should then double click on
    HKEY_CURRENT_USER, and then double click on the word Software.  If
    a NetSoft item appears in the subsequent list, then the user
    should highlight that item, click Edit and then click Delete.
    After confirmation, that item will be removed.  The User should
    then double click the HKEY_LOCAL_MACHINE and then click SOFTWARE.
    If a NetSoft item appears in the subsequent list, then the user
    should highlight that item, click Edit and then click Delete.
    After confirmation, that item will be removed.   Also, remove the
    application name in the following branch of the HKEY_LOCAL_MACHINE
    key:  SOFTWARE, Microsoft, Windows, Current Version, Uninstall.
           
4.  Click Edit and Find in the Registry drop-down menus and search for
    NETSOFT.TTF.  In the same location, delete three fonts:
    NETSOFT.FON, NETSOFT.TTF and NSOIA.TTF.  Exit the registry editor.
        
        
-----------------------------------------------------------------------
           
                     AnyNet PTF Requirements   
                     -----------------------        
        
In order to use the AnyNet link, users must have the cumulative PTF
tape #C6016 or later installed on their V3R1 AS/400.  Ensure that
you've followed the instructions with this cumulative tape as they are
simple but lengthy.
        
           
-----------------------------------------------------------------------
           
                         Known Problems 
                         --------------

Display Autologon
-----------------
If your display logon screen has been customized to eliminate the
Program/Procedure, Menu and Current Library options, NS/Elite's
Autologon functions may compromise the security of your host signon
procedures.  In effect, users could conceivably logon to data areas for
which they do not have rights.

This can be resolved by changing the parameter, LMTCPB, to *yes in the
user's profile.  If the user then uses the Autologon function, the
following error message appears when NS/Elite Display is launched:

Initial program or procedure cannot be specified.


Shared Access Limitations          
-------------------------          
NS/Elite v.2.01 does not currently support users who want to install
both this product and NetSoft NS/Elite mainframe products in a shared
network environment.  The Shared Installation versions of this and
other NS/Elite products require separate installation subdirectories.
The installation process, when it discovers a currently installed
NS/Elite product, automatically copies files into the same directory
structure as the already installed product.
          
          
TCP/IP Application Errors in NDIS          
---------------------------------          
If you experience application error problems when doing a fast connect-
disconnect with TCP/IP links over NDIS stacks, installation of the
Windows 95 Service Pack has been known to resolve the problem.
           
           
UNINSTALLATION DIFFICULTIES    
---------------------------    
When NS/Folders is installed and the PC is rebooted, the Network
Provider loads the following NS/Folders modules:  SFOLDER.EXE,
NSADMIN.EXE, PUMAP.EXE, and EVENTSRV.EXE.  When doing an uninstall on
any NS/Elite product, the uninstallation program cannot unload these
files because Folders registry keys are locked and cannot be removed.
    
The next reboot of the PC will not work and PC may hang. To resolve
this, the user must delete the following registry value and key:
    
[HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\control    
\\NetworkProvider\\Order]"NSNP32"=""    
    
[HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\NSNP32]
    
    
           
LIMITATIONS OF NS/FOLDERS V2.01     
-------------------------------     
The following limitations exist in this version of NS/Folders:
- You can't launch an application (32- or 16-bit) by double-clicking on
  an associated folders document.
- You can't run a 32-bit application located on an NS/Folders drive.
- You can't open a file from the Microsoft Office 95 toolbar (it
  attempts to launch Microsoft Word 7.x with a working directory of the
  folders drive).  Everything works OK if you launch Word 7.x first and
  then open the file.
- You can't map a drive to a folder when 16-bit drivers are being used
  or the PC is in 16-bit compatibility mode.
- You can't use Windows 95-style long filenames.
- You must map a drive to the shared folder on the host before you can
  copy files to and from that shared folder.
 
 
Application Failure Related to Computer Name       
--------------------------------------------       
Any product, including this NetSoft product, that uses OLE to launch a
local server will fail if you have used an "@" sign in your Computer
Name.  If you experience such failures, change your Computer Name by
doing the following:
       
Windows 95       
       
1.  Click Control Panel from the Start Menu.       
2.  Click Network.       
3.  On the Network sheet, click Identification.       
4.  Change the entry in the Computer Name text box.       
5.  Click OK.       
       
Windows NT       
       
1.  Double-click Control Panel in the Main program group.
2.  Double-click Network.       
3.  In the Network Settings dialog box, click Change next to the
    Computer Name entry.       
4.  Change the entry.       
5.  Click OK.       


SNA Server Password Dialog Box
------------------------------
If you click Cancel on the Password dialog box while launching a
display session linked to a Windows NT SNA Server, the PC may lock up.
This is an SNA Server Client problem, which has been fixed by Microsoft
and will be available in Service Pack 2.  Also, you may be able to
download the updated module (SNAKRNL.DLL) from Microsoft before that
service pack is released.


Co-existence with Client Access
-------------------------------
We strongly recommend that you remove Client Access before installing
this version of NS/Elite.  Support of common components becomes
extremely problematic between NetSoft and IBM.

         
***********************************************************************
                        End of ReadMe file 
***********************************************************************
