In response to an obviously large number of requests that QCTerm NOT support
the new user CTRL+Alpha key sequences that a lot of Windows-based, end-user-
oriented programs are now supporting, we've put a mode switch into QCTerm that
allows you to choose which mode you would prefer to work in.

If you are in the mode where CTRL+S means "Save File", which we call user
mode, you can now press CTRL+H. Doing that will flip a mode switch such that
all further CTRL+Alpha key presses are transmitted on to the host without
local (QCTerm) interpretation. From that point on, any CTRL+S sequence that is
pressed will be sent on to the host, as an XOFF character.

The user is given indication that the Transmit Control Characters mode has
been selected by a change in the color of the text written in the
communications panel at the bottom of QCTerm's screen. It will now appear
bright blue.

To return to the user (Process Control Characters Locally) mode, press
CTRL+Shift+F12. The text in the communications panel returns to black. When in
this mode, the newer PC-standard meanings return (i.e., CTRL+A means "Select
All", CTRL+C is "Copy", CTRL+V is "Paste", etc.).

This version of QCTerm is still marked as Version 0.5, but updated to today's
date. A number of internal changes and corrections have been put into this
version of QCTerm, but we didn't feel enough forward process has been made to
quite yet up the version number.

All of QCTerm's documentation on the web has been changed to reflect these
changes. The newest version of QCTerm can be downloaded from:

     http://aics-research.com/qcterm

As always, your comments are both encouraged and very much appreciated.

Wirt Atmar


PS: As an additional note that might help alleviate future confusion, pressing
the CTRL+S (XOFF)/CTRL+Q (XON) keys does not have any effect on data flow on
the HP3000 when the connection mode is Telnet. The XOFF/XON protocol is not
part of the HP3000's Telnet implementation (and truth be told, it isn't
particularly common for any Telnet implementation, although an RFC for such
flow control does exist).