Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84; site rduxb.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!rduxb!lra
From: lra@rduxb.UUCP (Lonnie R. Abelbeck, AT&T Bell Labs)
Newsgroups: net.micro.mac
Subject: VersaTerm-HP and macput/macget
Message-ID: <382@rduxb.UUCP>
Date: Thu, 11-Apr-85 23:11:33 EST
Article-I.D.: rduxb.382
Posted: Thu Apr 11 23:11:33 1985
Date-Received: Sat, 13-Apr-85 03:44:53 EST
Organization: AT&T Bell Laboratories, Reading, PA
Lines: 25

[]

I am just about finished with "VersaTerm-HP", good-ole VersaTerm with the
VT100 emulation replaced with an HP 2621+ emulation, ENQ/ACK handshake, local
editing, etc...

There is a problem with "Mac XModem" (macput/macget) though when you
are emulating a HP262X.  The <ESC>a sequence tells VT100 VersaTerm to
start Receiving a file... BUT an HP2621 does an "absolute cursor sense"
when it sees an <ESC>a, so we need another sequence:

   I propose,    <ESC>?     . Since this means that macput/macget needs to
be modified, I hope that we can do this once an for all.  A grep of our
termcap says that only the Concepts use this sequence, as well as the <ESC>a.
So I hope <ESC>? will be "safe" choice.

Currently I do a getenv() in macput/macget and test the TERM variable to
decide on either an 'a' or '?'.  On other systems a flag might be used, or
just a seperate program.

If anyone has a better suggestion of a sacred sequence, please let me know,
or else I will go ahead with the <ESC>?.

Lonnie Abelbeck
ihnp4!rduxb!lra