Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!microsoft!kentsu
From: kentsu@microsoft.UUCP (Kent SULLIVAN)
Newsgroups: comp.sys.cbm
Subject: Re: terminal progs?
Message-ID: <57108@microsoft.UUCP>
Date: 31 Aug 90 18:47:31 GMT
References: <16200012@col.hp.com>
Reply-To: kentsu@microsoft.UUCP (Kent SULLIVAN)
Organization: Microsoft Corp., Redmond WA
Lines: 41

In article <16200012@col.hp.com> warren@col.hp.com (Warren Tustin) writes:
[..]
>
>Must Features:
>  1200 baud, X-modem, A terminal protocal that can send a '|' (vertical bar)
>  for unix interfacing.  C64 mode is fine but how fast can you go (baud rate)?
>
>Wants:
>  2400 & greater baud, Y/Z modem, VT52/100 emulation, 40 or 80 columns on
>  my 128 (so I don't have to squint!).
>
>I have or can get the following via ftp/other  and was wondering if you have
>used any of these and what they can do:
>
>    novaterm9, cbtermx.x, desterm102, nova128v1p4, teleterm128, crabterm
>    runterm128 (can type this in)

I would definitely recommend DesTerm 128 v2.0.  Version 2.0 is brand new and
is very full-featured.  In a commercial package, I would definitely recommend
Dialogue 128.  Both of these packages now support the SwiftLink-232 high-speed
serial interface from Dr. Evil Labs, so baud rates up through 38,400 are
possible.

Both packages have comprehensive script languages, VT-52/100 emulation and
a variety of protocols.  Dialogue also supports the CompuServe B protocol,
which DesTerm doesn't (at least currently--there is a provision to add in an
additional protocol module).  Neither package has Z-modem.

DesTerm v2 is very new and hasn't made the rounds yet to all of the usual
archive sites.  It will soon be available on GEnie, CIS, and Q-Link, and
should start showing up other places as well.

By the way, a new version of NovaTerm has just been released: 9.1.  It fixes
numerous bugs and adds support for the SwiftLink, plus 80-col ANSI graphics,
complete documentation, and other things.

Kent Sullivan
Microsoft Corporation

The opinions expressed in this article are my own and do not necessarily
reflect those of my employer.