# SCO ANSI Terminal Emulator

Source: https://wndsoftware.com/sco-ansi-terminal-emulator

### SCO ANSI Terminal Emulator in WND Terminal

Select a SCO ANSI Telnet profile to inspect an OpenServer application screen with SCO color and PC-ROM glyph behavior.


### Supported terminals and connections

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


| System | Terminal | Connection | Where it runs | Current scope | Release |
| --- | --- | --- | --- | --- | --- |
| [SCO ANSI](https://wndsoftware.com/sco-ansi-terminal-emulator) | SCO ANSI subset | Telnet | Windows, Mac, Linux | SCO color, selected PC-ROM glyph and whole-screen clear behavior over Telnet. | v1.0.319 |

The current profile implements a documented subset, not the full SCO command set or a VT100 device identity.


### What the sample does

The software SCO host displays an order lookup using the implemented color, glyph and clear commands.

[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 scoansi. Check the application's keyboard setup and screen commands during a proof of value.

[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 SCO ANSI for OpenServer 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 |
| --- | --- |
| Select scoansi explicitly | Confirm the terminal-type setting expected by the OpenServer application. The current profile is not a claim of VT100 device identity. |
| Compare colors and glyphs | Use the order-lookup sample to inspect the implemented SCO color and PC-ROM glyph behavior, then test the same screen classes on the real host. |
| Exercise clearing and redraw | Move between a normal inquiry and an error response. Check that clear commands remove old content without losing labels or input fields. |
| Preserve the keyboard map | List the keys that trigger application navigation and confirm their host actions. A correct-looking form can still use an incompatible function-key sequence. |
| Validate the command subset | The profile implements a documented subset of SCO commands. Capture a reproducible screen or trace for application behavior outside the demonstrated sample. |

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

Choose scoansi when the host application expects SCO ANSI behavior. Preserve the current keyboard map and list the keys used for selection, editing and return. Test a color form and a screen containing PC-ROM glyphs, then submit a fictional inquiry. A successful VT100 connection does not establish that the same application will interpret SCO keyboard and screen controls correctly.


### When a screen or key behaves differently

Keep the profile, screen dimensions and the last host action with any display problem. Compare the first point at which the new screen differs from the working client, especially after a clear operation or a change in color or glyph presentation. If the keys perform the wrong action while the screen looks right, compare the actual configured sequences. Avoid changing host settings solely to make a generic terminal profile appear to work.


### Replacing an existing terminal client

The released SCO profile is a documented subset, not the full SCO command set and not a VT100 device identity. For an existing PowerTerm or other SCO-capable client, identify any commands outside that subset during evaluation. Use the software order-lookup host for a repeatable baseline, then test normal navigation, a rejected entry and cancellation in the real application. Retain the current client until each required workflow has a recorded result.

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


### Related terminal models

[AT386 Terminal Emulator: Partial Profile](https://wndsoftware.com/at386-terminal-emulator) · [BBS ANSI Terminal Emulator with CP437](https://wndsoftware.com/bbs-ansi-terminal-emulator) · [Wyse WY-50 and WY-60 Terminal Emulator](https://wndsoftware.com/wyse-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.