Greg asks:

> The obvious question arises from this: When is this functionality likely to
>  be available? (using  the Gregorian calendar rather than the Atmarian
>  calendar)

The new version (Version 0.96i) is now available for download at:

     http://aics-research.com/qcterm

Two new escape sequences have been defined:

     Esc%k0U - QCTerm is put into its default "killable" state.
     Esc%k1U - QCTerm becomes "unkillable", at least easily.

If QCTerm is in the unkillable state, (i) ALT+F4, (ii) the close box and
(iii) the exit command on the pull-down menu now all bring up an "Improper
Exit Warning" box, telling the user what to do. You may at that point either
exit the application gracefully or perform a hard reset to reset QCTerm's
internal "unkillable" flag.

If QCTerm is put into the unkillable state, you will notice that you cannot
change the connection settings either. Indeed, those entries in the
"Connection" pulldown menu will simply disappear. If however your telnet
connection should disappear or the host should go down, within 30 seconds or
so, QCTerm will recognize that failure and automatically put QCTerm back into
the normal, "killable" state. Unfortunately, we can't reliably do the same
thing for a serial connection.

I've written two programs in BASIC, KILLJOY and KILLME. Their complexity
level is rather low:

     KILLJOY
        10 PRINT '27"%k1U"

     KILLME
        10 PRINT '27"%k0U"

If you telnet to 67.41.4.238 and signon as:

     :hello demo.qcterm
     :basic

...you can then type either:

     >run killjoy

...to put QCTerm into an unkillable state, or type:

     >run killme

...to put QCTerm back into its normal state. This second command is obviously
what would be put into an application program near its normal exit.

Wirt Atmar

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