# VT Terminal Emulator for UNIX and Linux

Source: https://wndsoftware.com/vt-terminal-emulator

### VT Terminal Emulator for UNIX and Linux in WND Terminal

Connect over SSH or Telnet with VT100, VT220, VT320 and xterm-style terminal behavior. Keep your shell and full-screen applications in the WND Terminal workspace.


### Supported terminals and connections

On a small screen, swipe the table to read all columns.


| System | Terminal | Connection | Where it runs | Current scope | Release |
| --- | --- | --- | --- | --- | --- |
| [UNIX, Linux and VT applications](https://wndsoftware.com/vt-terminal-emulator) | VT100, VT220, VT320, xterm-compatible | SSH, Telnet | Windows, Mac, Linux, browser gateway | Character sessions with VT keys, colors and scrollback. | v1.0.299 |

The selected TERM name describes the host negotiation. Check the VT guide for implemented model behavior before selecting a later DEC or other terminal model.


### How VT behavior is checked

The VT reference suite exercises cursor movement, editing, character sets and full-screen applications against independent software terminals.


### Connect to your host

Select UNIX / Linux (SSH) or VT (Telnet), enter the host address and select the terminal type your application expects.

[Read the connection guide](https://wndsoftware.com/docs/vt-sessions)

Check your chosen VT model and host application during a proof of value. Browser gateway sessions need validation in your deployment.


### Move an existing session

Bring the host address, port, terminal type, key assignments and macros used by your team. Create a WND Terminal connection with the settings above, then run the actual screens and keys your application uses. Check the [session import guide](https://wndsoftware.com/docs/import-other-emulators) for supported source formats; the connection type alone does not prove that an old profile or macro can be imported.


### Keyboard and host workflow

Match the terminal profile to the application's TERM expectation, then test the keys used in its full-screen interface. A shell prompt alone does not exercise cursor movement, editing or keypad behavior. Include a screen that scrolls, an editable form, function-key navigation and a return to the original application state. Compare Backspace, Delete and the application's exit keys with the working session instead of assuming the desktop keyboard sends the same sequences.


### When a screen or key behaves differently

When a screen becomes misaligned, preserve the negotiated terminal type, connection mode, window dimensions and the operation that caused the redraw. Check character sets and cursor controls before treating a visual problem as a host failure. For SSH, also distinguish authentication and connection configuration from terminal display behavior. A later DEC model name does not imply that every feature of that physical terminal is implemented.


### Replacing an existing terminal client

The combined VT guide retains sections for VT52, VT102 and the partial VT420 and VT520 profiles so applications can be evaluated against the selected model. Printer functions, extra character sets and dual-session requirements need their own checks where the profile excludes them. For a PuTTY or another VT-client migration, bring the existing connection and keyboard settings. Test the actual full-screen applications after the basic connection succeeds.

[Keyboard-map documentation](https://wndsoftware.com/docs/keyboard-maps) · [Specialty terminal configuration and limits](https://wndsoftware.com/docs/other-terminals)


### Related terminal models

[Wyse WY-50 and WY-60 Terminal Emulator](https://wndsoftware.com/wyse-terminal-emulator) · [SCO ANSI Terminal Emulator](https://wndsoftware.com/sco-ansi-terminal-emulator) · [IBM 3151 Terminal Emulator](https://wndsoftware.com/ibm-3151-terminal-emulator)

Use the [supported-systems index](https://wndsoftware.com/supported-systems) to compare released profiles and limits. The [emulator evaluation checklist](https://wndsoftware.com/emulator) covers the broader deployment decision.


### Choose the DEC terminal profile your application expects

A terminal name does not establish full hardware compatibility. Match the host configuration, screen controls and keys, then test the actual application.


#### VT52

Open a Telnet session with VT52 cursor controls, keypad behavior and terminal identification. Check your application's screens in a proof of value.

Choose VT (Telnet), enter the host and port, and select vt52. Use the VT52 profile when the application expects that model.

The software inventory host displays a BOLT lookup with VT52 direct cursor addressing and graphics mode. It does not require DEC hardware.

Some original VT52 raster glyphs use close one-cell Unicode substitutes. Verify glyph-sensitive screens, printer behavior and host-specific keys with the actual application.


#### VT102

Select a VT102 Telnet profile for applications that check terminal identity and use line and character editing.

Choose VT (Telnet), enter the host and port, and select vt102. The profile responds to a primary device-attributes request as VT102.

The software inventory host checks the VT102 identity reply, accepts a BOLT lookup and returns an inventory screen.

The sample does not exercise printer-port commands or physical printer status. Check those and any host-specific keyboard rules during the proof of value.


#### VT420

Select an explicit VT420 Telnet profile for a first application walkthrough. The current subset handles device identity and same-level conformance requests.

Choose VT (Telnet), enter the host and port, and select vt420. Bring the existing terminal settings to a proof of value for comparison.

The software inventory host checks VT420 identity and conformance reply bytes before displaying a usable inventory screen.

This is a partial profile. Printer port, downloadable fonts, user-defined keys, dual sessions and additional character sets are outside the current subset.


#### VT520

Select an explicit VT520 Telnet profile for a first application walkthrough. The current subset handles device identity, conformance and shared VT screen behavior.

Choose VT (Telnet), enter the host and port, and select vt520. Check the host's required character sets and keyboard settings in a proof of value.

The software inventory host checks VT520 identity and conformance reply bytes before displaying a usable inventory screen.

This is a partial profile. Printer and keyboard options, extra character sets and dual sessions are outside the current subset.

[VT and SSH configuration guide](https://wndsoftware.com/docs/vt-sessions) · [Software-host samples](https://wndsoftware.com/downloads/wnd-model-samples.zip)