# AT386 Terminal Emulator: Partial Profile

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

### AT386 Terminal Emulator: Partial Profile in WND Terminal

Select an AT386 Telnet profile to try an older UNIX application workflow with documented function-key bytes.


### Supported terminals and connections

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


| System | Terminal | Connection | Where it runs | Current scope | Release |
| --- | --- | --- | --- | --- | --- |
| [AT386 partial profile](https://wndsoftware.com/at386-terminal-emulator) | AT386 (partial) | Telnet | Windows, Mac, Linux | AT386 terminal type and documented F1–F10/shifted key bytes with shared ANSI screen behavior over Telnet. | v1.0.319 |

This is a function-key and shared ANSI-screen starting point. Additional character sets, keys, display modes, remapping and printers require a customer-host check.


### What the sample does

The software invoice host opens a queue when F5 sends the expected AT386 key sequence.

[Download the compatibility lab](https://wndsoftware.com/downloads/wnd-model-samples.zip) (Python 3 and WND Terminal required)


### Connect to your host

Choose VT (Telnet), enter the host and port, and select at386. Compare your existing key map with the application's real workflow.

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

The software-host examples let you try these workflows now. WND Software checks your application workflows during a proof of value and addresses compatibility differences found.


### 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.


### Check AT386 for older UNIX applications against your application

Keep a working session profile and a repeatable test case. Compare what the application receives as well as what the terminal draws. Use the software-host examples as a starting point, then record the results on the actual host before a rollout.

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


| Application check | What to verify |
| --- | --- |
| Match the function-key map | The invoice sample opens its queue when F5 sends the expected AT386 sequence. Compare the real application’s required bytes with the current client. |
| Confirm the host terminal type | Select at386 and record the host environment’s terminal setting. A profile label does not guarantee compatibility with every older UNIX application. |
| Test a complete workflow | Open an inquiry, change a screen and return using the host keys. Include a validation-error path so redraw and cursor handling are exercised. |
| Record display requirements | The current profile is a shared ANSI-screen and function-key starting point. Additional character sets and display modes require a customer-host check. |
| Inventory peripheral behavior | Bring examples of remapping and printer workflows if used. They are not established by the sample’s successful function-key action. |

Bring the host address, selected terminal type, keyboard map and the steps that reproduce a problem to a [proof of value](https://wndsoftware.com/proof-of-value). Distinguish a simulated sample from a customer-host result in the test record. See [supported systems and profile limits](https://wndsoftware.com/supported-systems) for the current release scope.


### Keyboard and host workflow

Select AT386 deliberately when the application expects that profile. Record the working client's key map and compare a complete inquiry from entry to return, including a validation-error screen. Verify what the host receives for navigation and submission instead of judging compatibility only from the appearance of the first form. Keep the application's expected terminal identity with the connection settings.


### When a screen or key behaves differently

A partial terminal profile can display ordinary text while missing a control that a later application screen uses. Preserve the operation that triggers the difference, the selected profile and a fictional reproduction. Compare cursor movement and screen clearing before assigning the issue to the host application. A test of one form should not be presented as proof of all AT386 keyboard, printer or display behavior.


### Replacing an existing terminal client

The AT386 profile is a limited starting point for the documented software-host workflow. Review its current limits in the supported-systems index and the other-terminals guide before replacing an existing client. Bring the legacy terminal settings and a short list of the screens users need every day. Prove those screens and their error paths on the customer host, and keep the previous client available for any behavior outside the tested subset.

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


### Related terminal models

[SCO ANSI Terminal Emulator](https://wndsoftware.com/sco-ansi-terminal-emulator) · [BBS ANSI Terminal Emulator with CP437](https://wndsoftware.com/bbs-ansi-terminal-emulator) · [VT Terminal Emulator for UNIX and Linux](https://wndsoftware.com/vt-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.