# HP 3000 Terminal Emulator: HP 700/92 and 2392A

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

### HP 3000 Terminal Emulator: HP 700/92 and 2392A in WND Terminal

Connect to an HP 3000 with HP 700/92 or 2392A terminal settings. Work at a character-mode prompt or use host-defined keys in a block form.


### Supported terminals and connections

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


| System | Terminal | Connection | Where it runs | Current scope | Release |
| --- | --- | --- | --- | --- | --- |
| [HP 3000 HP terminal emulation](https://wndsoftware.com/hp3000-terminal-emulator) | HP 700/92, HP 2392A | Telnet | Windows, Mac, Linux | Character and block forms, host-defined f1–f8 keys and basic identity/status behavior for HP 700/92 and 2392A. | v1.0.319 |

The HP 2392A profile answers common identity and status requests. The separate HP 700/94 profile is a limited common-form starting point; model-specific VPLUS behavior still needs a customer-host check.


### What the sample does

The simulated HP host accepts HELLO MGR.SYS and RUN ORDERS, then an order for A-100, quantity 7, for LONDON DEPOT.

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


### Connect to your host

Choose HP 3000 on the WND Terminal connect page, enter the host address and use the default Telnet port 23 unless your gateway has another port.

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

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 HP 3000 and HP 2392A 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 |
| --- | --- |
| Test both application modes | Start with the command prompt, then open the actual block-form application. A working HELLO prompt does not prove all forms will behave correctly. |
| Preserve host-defined keys | Record the function labels and the operation each key performs. Compare application navigation with the current terminal instead of relying on labels alone. |
| Check screen transitions | Use a read-only inquiry, an editable form and a validation-error path. Confirm fields and cursor position after each host response. |
| Choose the intended profile | HP 700/92 and 2392A settings are separate from the limited HP 700/94 profile. Select the profile required by the real application. |
| Verify peripheral dependencies | Bring examples of printing or other peripheral behavior your workflow requires. A successful software-host form is not proof of physical-device compatibility. |

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

Identify whether the application expects HP 700/92 or HP 2392A behavior before mapping the keyboard. Keep the existing host-defined function labels and the action sent by each key. Begin with a character-mode sign-on, move into a block form, edit more than one field, and use the application's normal submission key. A terminal label in the connection settings is only the beginning of this check; field selection and transmission must also match the application.


### When a screen or key behaves differently

For a failed form, record the selected model, the screen before submission, the fields changed and the exact host response. Compare cursor placement after both a successful operation and an application validation error. This helps distinguish a wrong profile or key map from a business rule enforced on the HP 3000. Keep printing and peripheral checks separate from the ordinary form test, especially if an existing workflow depends on physical-device status.


### Replacing an existing terminal client

An HP 3000 migration should retain a known working session while the new client is evaluated. Use the supplied software order example for a repeatable starting point, then test the application's actual commands and host-defined keys. The separate partial HP 700/94 profile has different limits; do not select it merely because its model number is newer. Document which profile was tested and the workflows that remain outside the agreed scope.

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


### Related terminal models

[HP 700/94 Terminal Emulator: Partial Profile](https://wndsoftware.com/hp-700-94-terminal-emulator) · [NonStop 6530 Terminal Emulator](https://wndsoftware.com/nonstop-terminal-emulator) · [Unisys T27 and UTS Terminal Emulator](https://wndsoftware.com/unisys-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.