My thanks to Nick Costandi in France for making the following
available to me. Note: I've downloaded it, but not yet tried it out!
 
Martin Knapp
 
====================================================================
 
 
>X-Sender: [log in to unmask]
>Mime-Version: 1.0
>Date:         Thu, 19 Oct 1995 13:14:05 -0400
>Reply-To: Eric Schubert <[log in to unmask]>
>Sender: HP-3000 Systems Discussion <[log in to unmask]>
>From: Eric Schubert <[log in to unmask]>
>Subject:      NQtelnet inbound freeware server (MPE 5.0 update)
>To: Multiple recipients of list HP3000-L <[log in to unmask]>
>Status: RO
>
>FYI:
>
> I added code to NQtelnet to ignore Posix interrupts on HPSELECT
calls
>(status -91) that popped up on MPE 5.0 systems.  This is not a
problem on
>4.0 systems.
>
>These are still MPE sources and binaries (only -D_SOCKET_SOURCE
defined).
>They should run on a 4.0 system.
>
>FTP site:  opus.admin.utc.edu /pub/hp3000-l
>------------------------------------------
>nqteldoc.txt     (about file, etc.)
>nqtelnet.ftp     (uncompressed binary)
>nqtelnet.z       (Unix compressed binary)
>nqtelnet.zip     (do pc UNZIP; then upload w/WRQ transfer attributes
checked)
>nqtunpac.txt     (command file to unpack programs on the 3000 host)
>
>NQTunpac contains the expected CHECKSUM for uhaul.  This method
guarantees
>correct delivery of sources/binaries.
>
>BTW,
>
>I've had a lot of people try NQtelnet over the last months.
>
>THESE DON'T WORK:
>  Applications using terminal LDEV numbers in FOPEN's don't work
(why is
>this pratice sooo widespread?).
>
>THESE DO WORK:
>  Applications using $stdin/$stdlist non-vplus terminal I/O usually
work
>(needed to split I/O between a pair of message files).
>
>NQtelnet provides (some) VT100 terminal emulation WITHIN THE SERVER.
 This
>means applications that do simple HP2392A terminal escape codes,
such as:
>
>  home/clear, page up/down
>  inverse video,
>  half bright,
>  blinking,
>  absolute cursor postioning
>
>LOOK the SAME as their HP term counterpart on a dumb freeware
Internet VT100
>telnet client.
>
>Don't think HP 3000 inbound telnet will solve your Internet access
problems.
>Be prepared to buy into HP2392A terminal telnet clients (and
distribute them
>to users) when inbound HP telnet arrives (good luck trying to do
this on the
>Internet!)  or buy into application specific VT100 translation
software or
>write your own.  I guess ported stuff wouldn't matter.
>
>I still think if HP offered a basic set of HP terminal code
translations
>from the HP2392A set to the *ANSI STANDARD* set within their (yet to
beta)
>inbound telnet server - it would make the 3000 a more viable option
to be
>used both on the Internet and HP terminals with existing character
based
>applications.  I do this now in NQtelnet.  How?
>
>Because built into TELNET protocol you can ask the client in a
_standard_
>way "what is your term type?"  For example, NQtelnet checks client
termtype
>and switches on/off VT100 emulation (in the server).  Try the test
program
>included with the package on both an "hpterm"  or "vt100" client.
You'll
>see what I mean.
>
>Of course it will take CPU.  Make it an option.
>----------------------------------------------------------------
>Eric J. Schubert                    Senior Data Base Analyst
>Office of Information Technologies  Univ of Notre Dame, IN USA
>(219) 631-7306                      http://www.nd.edu/~eschuber
>