Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!mucs!mccuts!zlsiial
From: zlsiial@uts.mcc.ac.uk (A.V. Le Blanc)
Newsgroups: comp.sys.hp
Subject: qterm -- identifying terminals
Message-ID: <2378@mccuts.uts.mcc.ac.uk>
Date: 20 Feb 91 11:24:25 GMT
Reply-To: zlsiial@cms.mcc.ac.uk (A.V. Le Blanc)
Organization: Computing Centre, Univeristy of Manchester, UK
Lines: 29

Recently on this list someone mentioned the qterm program,
available as unix/util/qterm.tar.Z from lut.fi.  This program
reads a data base in /usr/local/lib and tries to identify the
terminal type.

The data base identifies NCSA telnet and MS-Kermit terminals
correctly as it is configured.  I found that by adding the
following two lines at the end of the data base

^[*s^	9000/340^J	300h	HP bit-mapped display terminal
^[*s^	X-hpterm^J	hpterm	HP X-windows terminal

I can thus identify the two other most widely used terminals on
our system.  Unfortunately there is a snag.  (Isn't there
always?)  We have 9 HP 700/92 terminals which we use as
monitors on the file servers of 9 of our clusters.  This
terminal is, of course, not identified by the data base as
it stands.  Moreover, either the ESC-*s^ or the ESC-Z sequence
causes the 700/92 to lock its keyboard, which can be released
only -- as far as I know -- by pressing RESET.

1)  Is there any code that the 700/92 should be sent to identify
itself?  What does it respond?

2)  Why is the keyboard locking?  Can qterm be convinced to
unlock it?

				A. V. Le Blanc
				ZLSIIAL@uk.ac.mcc.cms


Brought to you by Super Global Mega Corp .com