README.TXT: Patch 52 for SNA Server 2.0Last reviewed: April 24, 1996Article ID: Q118412 |
The information in this article applies to:
The following is the README.TXT file that accompanies SNA Server 2.0 patch 52 (SNA20.P52): 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 #52 Status: Confirmed PKZIP 2.04g format -- uncompress using the "-d" option. Date: July 15, 1994 Modules updated:
SNA Server Windows 3.x client files: <winroot>\SYSTEM\WINAPPC.DLL 07/05/94 03:07p 77,685 <winroot>\SYSTEM\WINCSV.DLL 07/05/94 03:12p 36,707 <winroot>\SYSTEM\WINRUI.DLL 07/05/94 03:14p 37,480 <winroot>\SYSTEM\LMCLI.DLL 07/05/94 01:43p 9,776 <winroot>\SYSTEM\NWCLI.DLL 07/05/94 01:44p 12,112 <winroot>\SYSTEM\WINMGT.DLL 07/05/94 03:16p 31,543 <winroot>\SYSTEM\WDMOD.DLL 07/05/94 01:38p 60,928 <winroot>\SYSTEM\YMGR.DLL 07/05/94 01:45p 1,808 <winroot>\SYSTEM\WINTRC.DLL 07/05/94 01:48p 38,400 <winroot>\SYSTEM\WLOGTR.DLL 07/05/94 01:42p 87,552 <snaroot>\WNAP.EXE 07/05/94 01:47p 38,400 <snaroot>\WPOPUP.EXE 07/05/94 01:55p 11,248 SNA Server Windows 3.x client files -- traced versions (debug only): \CLIENTS\WIN3X\TRACE\LMCLI.DLL 07/05/94 02:01p 59,906 (debug only) \CLIENTS\WIN3X\TRACE\NWCLI.DLL 07/05/94 02:02p 69,848 (debug only) \CLIENTS\WIN3X\TRACE\WDMOD.DLL 07/05/94 01:55p 286,670 (debug only) \CLIENTS\WIN3X\TRACE\WNAP.EXE 07/05/94 02:09p 180,617 (debug only)Bugs fixed: 2425 Windows 3.x FMI tracing problem w/Attachmate 4.0a. When enabling 3270 message tracing (FMI) on a Windows 3.x client running Attachmate Extra, the trace data would overwrite the display and stop logging when the 3270 session is used.
2065 Problem accessing "Otherservers" from a Netware client (Patch 38, Windows 3.x platform only, though requires server components from Patch #38 to work)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.
Update Procedure: - 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 *.DLL files to the <winroot>\SYSTEM directory copy all *.EXE files to the <snaroot> directory (save the debug 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- Restart the SNA client software *********************** End of Readme ******************************* SNA Server 2.0 patches are located on:
|
Additional reference words: prodsna 2.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |