Terminal Files From 16-bit Windows May Not Maintain Settings

Last reviewed: May 9, 1997
Article ID: Q104984

The information in this article applies to:

Microsoft Windows NT operating system version 3.1
Microsoft Windows NT Advanced Server version 3.1

SYMPTOMS

When you use Terminal files (.TRM) created from 16-bit Windows 3.0 or 3.1 in Windows NT, some settings may be altered.

Windows NT may alter the settings for the Data Bits and Connector. The settings for the Baud Rate, Stop Bits, Flow Control, Parity, Parity Check, and Carrier Detect should be maintained correctly.

For example, if the Data Bits were set to 8 and the Connector was set to COM2, Windows NT may alter the Data Bits to 6 and attempt to set the Connector to Telnet, which will cause the following error message:

   Terminal failed to open the telnet session. Please use
   the services option in control panel to make sure that the
   telnet service is started.

RESOLUTION

To eliminate any possible problems or error messages, double check the settings for the Terminal file in Windows NT and then save it with Windows NT Terminal.

Additional query words: prodnt
Keywords : kbtool nt16ap ntutil
Version : 3.1
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: May 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.