5 Appendix A: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

  • Windows Server 2008 operating system

  • Windows 7 operating system

  • Windows Server 2008 R2 operating system

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

  • Windows 10 operating system

  • Windows Server 2016 operating system

  • Windows Server operating system

  • Windows Server 2019 operating system

  • Windows Server 2022 operating system

  • Windows 11 operating system

  • Windows Server 2025 operating system

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2: When implementing Telnet VTNT Terminal Type Format on Windows, implementers can take advantage of Windows Console APIs such as ReadConsoleOutput () API and WriteConsoleOutput() to read and write to the console screen buffer. For more information, see [MSDN-CONSOLES]. Windows also has an implementation of the console screen buffer (see [MSDN-CSB]).

<2> Section 2.1.1:  Windows Telnet Server fills the Char field with Unicode UTF-16 characters.

<3> Section 2.2: Windows Telnet server expects a client to fill this field with virtual key codes that are compatible with the keyboard installed on the server. Virtual key codes for each of the keyboard keys are specified in section 2.2.1. Implementations of Telnet VTNT Terminal Type Format on Windows can use the Windows ReadConsoleInput() API, which returns a structure compatible with the INPUT_RECORD structure, with all fields including wVirtualKeyCode filled in.

<4> Section 2.2: Windows Telnet server expects a client to fill this field with the scan code. An implementation on Windows can use the ReadConsoleInput() API, which returns a structure compatible with the INPUT_RECORD structure, with all fields including wVirtualScanCode filled with the scan code of the key pressed.

<5> Section 2.2: Windows Telnet client uses Unicode characters to fill this field.