README.TXT: Patch 45 for SNA Server 2.0

Last reviewed: April 17, 1997
Article ID: Q115385

The information in this article applies to:
  • Microsoft SNA Server for Windows NT, version 2.0

The following is the README.TXT file that accompanies SNA Server 2.0 patch 45 (SNA20.P45):

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.

******************* Beginning of Readme ***************************

Product: Microsoft SNA Server for Windows NT v2.0 Update: Patch #45 (includes patch 4, 28, 31) Status: Confirmed

PKZIP 2.04g format

Date: May 24, 1994

Modules updated:

<snaroot>\SYSTEM\IBMSYNC.SYS   05/20/94  02:13p  51,200
<snaroot>\SYSTEM\IBMSDLC.DLL   05/20/94  02:16p  75,776
<snaroot>\SYSTEM\IBMX25.DLL    05/20/94  02:20p 122,368
<snaroot>\SYSTEM\HWSETUP\IBMX25\IBMSYNC.SYS (same as above) <snaroot>\SYSTEM\HWSETUP\IBMX25\IBMX25.DLL (same as above) <snaroot>\SYSTEM\HWSETUP\IBMSDLC\IBMSYNC.SYS (same as above) <snaroot>\SYSTEM\HWSETUP\IBMSDLC\IBMSDLC.DLL (same as above)

Bugs fixed:

1780 Some MCA-bus machines may hang when activating SDLC

When using the IBM Multiprotocol (MCA-bus SDLC) Adapter, certain machines may hang when activating an SNA Server SDLC connection. This hang has been observed on an IBM PS/2 Model 95 and NCR 3410. When using an IBM Model 95, this fix should be applied and the SDLC_1 arbitration level setting for the adapter (set using the reference diskette) should be set to 0.

1928 SDLC connection may drop unexpectedly.

Fix reliability problems which could cause the SDLC connection to drop unexpectedly. Under heavy stress, the link service was receiving SDLC data which it believed to be invalid, causing the connection to be dropped. This update corrects a problem in the way the link service was accepting data from the adapter.

2184 SNALINK service exception using DCA ISCA adapter

If an SDLC device driver returned an error to the link service, SNALINK treated this as a fatal error leading to an Int 3 (causing an application exception). Instead, such a condition is now considered to be recoverable, so an outage will be logged in the application event log and processing will continue.

1665 Fix to allow 2nd MPAA adapter (MPAA2) to work

When using the IBM Multiprotocol adapter (MCA-bus SDLC card), SNA Server would only support the first adapter (MPAA1) in the machine. With this fix, SNA Server now supports both adapters.

XXXX Fix to allow ibmsdlc/ibmx25 to run on Windows NT 3.5.

Due to a change in Windows NT 3.5 (codename Daytona), the SNA Server 2.0 ibmsdlc and ibmx25 link services do not initialize properly, causing these links to fail.

1580 SDLC performs excessive logging on failure conditions.

Certain errors (such as ibmsync initialization failures and some SDLC link service outages) were causing multiple errors to be reported to the server, and to the event log.

1986 Relax X.25 negotiation timer when SNA Server is primary (patch 31)

When SNA Server is primary on an X.25 connection, turn off the timer when receiving an open station, allowing a QSNRM to always be transmitted.

1983 Support Microgate SDLC adapter at 56KB (Patch 28)

The SNA Server IBM SDLC device driver now supports the Microgate SDLC adapters (models USA, MG96, MG144 and DSA, for both ISA-bus and Microchannel bus). Tested at speeds up to 56KB. This adapter is compatible with the IBM SDLC/MPAA adapter.

1738 IBM X.25 link service does not accept 8 character device name

      (Patch #4)

Any SDLC device driver which exports an 8 character device driver name will not work with the SNA Server X.25 link service. This problem was originally found when using the DCA ISCA driver when communicating over the SNA Server X.25 link service.

Update Procedure:

- Copy the new modules over the existing versions in the above SNA Server directory locations. Note: The files located in the <snaroot>\SYSTEM directory are placed there by SNA Server setup (copied from the HWSETUP directory), when this link type is installed. Be sure to copy them to the HWSETUP directory so that the updated link support will be used, if the link service is removed and added using SNA Server setup.

- Restart the server to load the new IBMSYNC.SYS driver.

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

SNA Server 2.0 patches are located on:

  • Library #2 of the MSSNA Compuserve forum.
  • 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.