README.TXT: Patch 38 for SNA Server 2.0

 Last reviewed: April 17, 1997
Article ID: Q114065
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, version 2.0

SUMMARY

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

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 #38 Status: Confirmed

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

- Includes Patch #3, #8, 26, 32, 33

Date: March 18, 1994

Modules updated: 

   \CLIENTS\MSDOS\LMBASE.EXE  03/11/94  04:36p 39046
   \CLIENTS\MSDOS\NWBASE.EXE  03/11/94  04:34p 40996
   \CLIENTS\MSDOS\TRACE\LMBASE.EXE  03/11/94  04:43p 72940 (debug version)
   \CLIENTS\MSDOS\TRACE\NWBASE.EXE  03/11/94  04:40p 77022 (debug version)

   \CLIENTS\WIN3X\NWCLI.DLL   03/11/94  04:27p 12112
   \CLIENTS\WIN3X\WNAP.EXE    03/11/94  04:28p 38400
   \CLIENTS\WIN3X\TRACE\NWCLI.DLL  03/11/94  04:30p  69824 (debug version)
   \CLIENTS\WIN3X\TRACE\WNAP.EXE   03/11/94  04:31p 180533 (debug version)

   \SYSTEM\SNABASE.EXE  03/11/94  04:23p  158720
   \SYSTEM\SNADMOD.DLL  03/11/94  04:22p  493568
   \SYSTEM\SNANW.DLL    03/11/94  04:22p  347648
Date: March 18, 1994

Bugs fixed:

2065 Problem accessing "Otherservers" from a Netware client.

The "otherservers" option allows an SNA Server client to gain an SNA session through SNA Servers which are not in the primary domain that the client is accessing (this option is described in the SNA Server 2.0 readme.txt file). However, this wasn't working correctly from an SNA Server client running over Netware.

1988 Only the first invokable TP will start on Windows 3.x (Patch 33)

Due to a WIN.INI parsing problem within the SNA Server Windows 3.x client, only the first invokable APPC TP on Windows was being registered with the client software. Any additional invokable TP's were not being registered, and would never be started.

XXXX The 3270 EIS sepdcrec call doesn't return if no network present 

      (Patch 33)
This error is not visible to the user, who only observes an error dialog if no network is present (and is allowed to continue as usual). While the user is not aware of this, a 3270 emulation vendor will observe that their call to sepdcrec doesn't return. This update corrects this so that the sepdcrec call does return when no network is present.

1987 IBM PC's shared folders hang when accessing through Windows (Patch 32)

When running the SNA Server MS-DOS router over IPX, with IBM PC Support shared folders, a machine hang can occur when accessing an AS/400 drive from Windows file manager.

1918 Trap when internal tracing is active, and DLOAD error occurs 

      (Patch 26)
When SNA Server internal tracing is activated on "SNA Applications" on a Windows NT machine, and a APPC dynamic load (DLOAD) request fails, an application exception occurs.

1945 Mishandling of parameters passed to an Invokable TP (Patch 26)

Parameters specified for the invokable TP (within the Parameters subkey of the Windows NT service) were not being passed correctly to the invokable TP when automatically started by SNA Server.

1737 RECEIVE_ALLOCATE on APPC service TP name never attaches (Patch #3)

1755 Server spins in tight loop if it can't access config file (Patch #8)

Update Procedure:

- On the server, stop the SnaBase service and apply the following updated 

  modules:

     copy \SYSTEM\SNABASE.EXE to the server's <snaroot>\SYSTEM directory
     copy \SYSTEM\SNADMOD.DLL to the server's <snaroot>\SYSTEM directory
     copy \SYSTEM\SNANW.DLL   to the server's <snaroot>\SYSTEM directory
- On a Windows 3.x client machine (running over Netware), stop the SNA 
  Server client software and apply the following updated modules:

     copy \CLIENTS\WIN3X\NWCLI.DLL to the <winroot>\SYSTEM directory
     copy \CLIENTS\WIN3X\WNAP.EXE to the <snaroot> directory

     (save the debug versions for troubleshooting purposes, if required)
- On an MS-DOS client machine (running over Netware), stop the SNA Server 
  client software and apply the following updated modules:

     copy \CLIENTS\MSDOS\LMBASE.EXE to <snaroot> directory
     copy \CLIENTS\MSDOS\NWBASE.EXE to the <snaroot> directory

     (save the debug versions for troubleshooting purposes, if required)
- Restart the server and client software

*********************** 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).

Additional query words: prodsna
Keywords : kbnetwork ntdistrib
Version : 2.0
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.