Knowledge Base |

# Terminal Files From 16-bit Windows May Not Maintain Settings

Article ID: 104984

Article Last Modified on 4/9/2004

APPLIES TO

- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Advanced Server 3.1

This article was previously published under Q104984

## 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: KB104984