README.TXT: Patch 56 for SNA Server 2.0

• Microsoft SNA Server for Windows NT 2.0

SUMMARY

The following is the readme file that accompanies SNA Server 2.0 patch 56 (sna20.p56):

Note that this article reflects the text of a static document. Therefore, some of the information in this article may be outdated. For example, as of May 20, 1996, Microsoft no longer maintains support forums on CompuServe.

MORE INFORMATION

******************* Beginning of Readme *************************** Product: Microsoft SNA Server for Windows NT v2.0 Update: Patch #56 Status: Confirmed

PKZIP 2.04g format -- uncompress using the "-d" option.

Date: August 25, 1994

********************************************************** **** NOTE : Patch #52 files must be applied to the *****

****         Windows client machine first !!!        *****

Modules updated:

  SNA Server Windows 3.x client files:

 <winroot>\SYSTEM\NWCLI.DLL    08/10/94  12:44p  87,552
 <winroot>\SYSTEM\WDMOD.DLL    08/10/94  12:44p  60,928
 <winroot>\SYSTEM\WLOGTR.DLL   08/10/94  12:45p  12,464

 <snaroot>\WNAP.EXE            08/10/94  12:47p  38,400


  SNA Server Windows 3.x client files -- traced versions (debug only):

 \CLIENTS\WIN3X\TRACE\NWCLI.DLL  08/10/94  12:52p  71,107 (debug only)
 \CLIENTS\WIN3X\TRACE\WDMOD.DLL  08/10/94  12:50p 286,710 (debug only)
 \CLIENTS\WIN3X\TRACE\WNAP.EXE   08/10/94  12:53p 180,761 (debug only)

- 2512: WNAP fails to load on Netware connection number 256 or 512.

  Due to a restriction of the Netware interface that SNA Server uses,
  clients who happen to connect using Netware connection number 256
  or 512 will not be able to start WNAP due to "no network found"
  error.  This update uses a different mechanism to detect the
  presence of the Netware shell, rather than using the connection
  number (which is returned to SNA Server as connection #0).

  Allows the LogonUserName=<user> entry in the [wnap] section of
  WIN.INI to default the user id in the SNA Server client logon
  dialog.   Previously, SNA Server retrieved the user name based
  on the user's Netware connection number.  However, if the
  connection number exceeded 256, the wrong userid would appear
  in this logon dialog.

  When connecting over Netware IPX/SPX, the SNA Server client would
  occasionally not be notified of an SPX session error, causing the
  SNA application to hang.  This update assumes any SPX connection
  write error should be interpreted as an SPX connection failure,
  causing SNA Server to cancel any pending reads over that SPX
  connection.

  When running an APPC or CPIC program which accepts conversations
  over more than one TP name, the SNA Server client would incorrectly
  attempt to invoke another copy of the invokable TP rather than
  route the request to the outstanding receive_allocate or cmaccp
  call.

- On an SNA Server Windows 3.x client machine, stop the SNA Server

  client software and apply the following updated modules:

    save original copies of all files by renaming them to *.OLD

    copy all updates from Patch #52 to the SNA client machine
    (as documented in the Patch 52 readme file)

    copy all *.DLL files to the <winroot>\SYSTEM directory
    copy WNAP.EXE to the <snaroot> directory

    (save the TRACE versions for troubleshooting purposes, if required)


  NOTE: If you are using Attachmate Extra 4.0a, this version includes
     an older set of SNA Server Windows 3.x client files, which
     are copied to the \EXTRAWIN directory.  If applying this update
     to such a system, rename the following files in the \EXTRAWIN
     directory so they are not used:

     WNAP.EXE   -> WNAP.20
     WDMOD.DLL  -> WDMOD.20
     LMCLI.DLL  -> LMCLI.20
     NWCLI.DLL  -> NWCLI.20
     WLOGTR.DLL -> WLOGTR.20
     YMGR.DLL   -> YMGR.20

*********************** End of Readme *******************************

SNA Server 2.0 patches are located on:

1. Library #2 of the MSSNA Compuserve forum.

2. The Internet server under BUSSYS\SNASRVR\SUP-ED\FIXES\ (supported patches) OR on BUSSYS\SNASRVR\UNSUP-ED\FIXES\ (unsupported patches).