From: utzoo!decvax!harpo!npois!ucbvax!info-terms Newsgroups: fa.info-terms Title: Re: Ann Arbor Ambassador termcaps Article-I.D.: ucbvax.7612 Posted: Thu Jun 10 19:58:33 1982 Received: Fri Jun 11 06:22:30 1982 >From teklabs!tekid!clives@Berkeley Thu Jun 10 19:57:37 1982 Hi Mark - Still haven't gotten confirmation that one of the mailing addresses is getting through to you. However, apparently one person connected to berkeley did get the termcaps, and sent me a note, which I enclose along with my reply. *************** Forwarded ************************** From: teklabs!ucbvax!mclure Date: Tue 8 Jun 1982 at 0153 Date: 8 Jun 82 0:44-PDT From: mclure at SRI-UNIX To: teklabs!tekid!clives at berkeley, mark at berkeley Subject: Tek Ambassador Termcap entry: caution Since I liked the description of your Ambassador changes, I went ahead and tried a test version of Termcap incorporating the new version. Unfortunately, they seem to be grossly buggy. The Ambassador termcap version from Rand (and Berkeley's) worked perfectly with our local Emacs look-a-like Elle. The Tektronix version does lots of strange things. For one, it causes the screen to spazz when the init and cursor addressing initialization strings are sent. Second, and more serious, it does weird things with control keys! For example, the command ^N in Elle means go to next line. In the other Termcap descriptions of the Ambassador this simple command worked properly in Elle. However, now it merely causes Elle to beep. There are a number of other control characters that seem to have been disabled, ^X, ^Z, ^P, etc. I withdrew back to the previous Termcap we had (Rand's) and all is working properly again. I recommend caution with this Ambassador description. It seems to have problems. **************** My reply ****************** To: teklabs!ucbvax!mclure,teklabs!ucbcad!csvax:mark Subject: Re: Tek Ambassador Termcap entry: caution In-reply-to: Your message of Tue 8 Jun 1982 at 0153, 8 Jun 82 0:44-PDT. -------- Howdy - Thanks for your comments. Wonder what the difficulty is? Many programs in regular use here exercise all the things you've had problems with. In particular, I have a copy of the CMU-Jim Gosling emacs up here which works fine. We have about 20 Ann Arbors on line at the moment, no problems. I'm thinking that the "spazzing" you mention is the important clue. That's certainly not normal operation. Such a thing could happen, along with all else you describe, if there was a comm problem. We once had a port multiplexer here which didn't really like long full-speed bursts sent through it, for instance. The terminal init sequence for this termcap is 110 characters long. I'd like to hear further if you find a cause. And would you please pass this on to mark? I got a rejection notice from a ucb mailer daemon about the return address on his original net article, and don't know a sure good one yet. Clive Steward