Tracy writes:

> The only terminal emulator I know of that has
>  a block on Control characers is QCTerm, which
>  has a toggle that processess ALL control
>  characters locally or remotely as desired.

QCTerm doesn't have a "block" on control characters. Rather, it has dual use
for them. You must choose which usage you want them to have. In the Terminal
pull-down menu, you can specify whether you want control characters to be sent
to the host (which, in the case of the CNTL-X discussed here, you do) or to be
processed locally.

If they're processed locally, they assume the now standard Windows functions.
For example, CNTL-X means "cut", CNTL-C means "copy" and CNTL-V means
"paste". In that regard QCTerm works much like a word processor, although one that's
actively communicating with a host processor.

But if they're being transmitted to the host, the control characters mean
whatever the host interprets them to mean and they have no local function.

One note on CNTL-X, to get the expected MPE action, you must not only specify
"transmit to host", you must also have QCTerm operated in "standard telnet"
mode. "Advanced telnet" depends on the terminal's ability to predict what
character will be returned by the host if you type something on the keyboard. In
MPE, the returned character is the same character that you typed -- with the
exception of CNTL-X. You type CNTL-X and three "!!!"s come back, thus breaking
the prediction.

This behavior is much more common in UNIX, thus advanced telnet-like modes of
communication can't be used in UNIX. You have to sit around and wait to see
what the host actually returns.

Bottom line:

If you want to use CNTL-X in QCTerm against MPE:

     o specify transmit control characters to host
     o operate in standard telnet mode

Wirt Atmar

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *