Windows NT 3.0 SP1 Client Doesn't Correctly Install NLS files

 Last reviewed: December 4, 1997
Article ID: Q172145
The information in this article applies to:
  • Microsoft SNA Server, versions 3.0 and 3.0 SP1

SYMPTOMS

The SNA Server Windows NT 3.0 SP1 Client is does not correctly copy the SNANLS files or add the necessary registry settings during installation. Any Windows NT applications which make use of the SNA Server 3.0 SNANLS API character conversion functions will not work properly. This problem affects SNA Server-J client applications (such as the 3270 and 5250 applets, or AFTP), though it does not affect the English version of SNA Server client functions.

RESOLUTION

The client setup has been updated to correctly copy the NLS files and adds the required NLS registry settings.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SNA Server, versions 3.0 and 3.0 SP1.

A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.

Additional query words: Client NLS registry
Keywords : prodsna snasetup snawinnt kbbuglist
Version : 3.0 3.0sp1
Platform : winnt
Issue type : kbbug
Solution Type : kbfix kbpatch

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: December 4, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.