Wyse WY-50 and WY-60 Terminal Emulator in WND Terminal
Open a Telnet session with a selectable WY-50, WY-50+ or WY-60 profile and check the application's screens and keys.
Supported terminals and connections
On a small screen, swipe the table to read all columns.
| System | Terminal | Connection | Where it runs | Current scope | Release |
|---|---|---|---|---|---|
| Wyse WY-50, WY-50+ and WY-60 | WY-50, WY-50+, WY-60 | Telnet | Windows, Mac, Linux | 24×80 Wyse cursor, protected-text and key behavior; model-specific page memory over Telnet. | v1.0.319 |
The current profiles focus on 24×80 screens. 132-column layouts, split windows, printers and block sends need a customer-host check.
What the sample does
The software Wyse host draws a protected account inquiry and returns a lookup result. Page examples exercise WY-60 and WY-50+ page memory.
Download the compatibility lab (Python 3 and WND Terminal required)
Connect to your host
Choose Wyse, select WY-50, WY-50+ or WY-60, then enter the host address and port. Confirm the terminal-type value expected by the host.
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 for supported source formats; the connection type alone does not prove that an old profile or macro can be imported.
Test your exact terminal model.
Bring the connection settings and screens your team uses. We will agree on the workflow to prove during a free two-to-four-week proof of value.
Check Wyse WY-50, WY-50+ and WY-60 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 exact model | Select WY-50, WY-50+ or WY-60 according to the application. Preserve the existing terminal-type setting and key map for comparison. |
| Check protected fields | Run an inquiry and an editable screen. Confirm the cursor reaches the intended fields and that protected labels remain unchanged. |
| Test page-memory behavior | Use the supplied WY-50+ or WY-60 page example, then repeat the page-changing workflow your host application uses. |
| Check the required width | Current profiles focus on 24 by 80 screens. A wide layout or split window needs a specific compatibility check. |
| Include dependent functions | Bring representative printer and block-send workflows. Successful screen drawing alone does not validate those application dependencies. |
Bring the host address, selected terminal type, keyboard map and the steps that reproduce a problem to a proof of value. Distinguish a simulated sample from a customer-host result in the test record. See supported systems and profile limits for the current release scope.
Keyboard and host workflow
Select WY-50, WY-50+ or WY-60 according to the existing host configuration. Those names should not be used interchangeably simply because an initial screen is readable. Keep the key map and test the application's ordinary navigation, field entry, submission and return path. Include a screen with attributes or line drawing so the comparison checks presentation as well as the text of a successful inquiry.
When a screen or key behaves differently
For an incorrect redraw, preserve the chosen Wyse model and the exact sequence of host screens that produces it. Check whether the failure follows a clear operation, cursor movement or a particular attribute change. Use a small fictional record so the application team can reproduce the problem. If the old workstation depends on printing, programmable keys or a less common control sequence, list that requirement explicitly rather than assuming it follows from the Wyse name.
Replacing an existing terminal client
When replacing a Wyse-capable PowerTerm, ZOC or other terminal client, compare the actual profile and application behavior rather than the vendor's entire feature list. WND Terminal's software-host sample provides a bounded display and submission test. Extend that check with your application's validation and cancellation paths. Keep the known working session available until the required key sequences and screens have been proved on the real host.
Keyboard-map documentation · Specialty terminal configuration and limits
Related terminal models
VT Terminal Emulator for UNIX and Linux · SCO ANSI Terminal Emulator · IBM 3151 Terminal Emulator
Use the supported-systems index to compare released profiles and limits. The emulator evaluation checklist covers the broader deployment decision.