Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!ssbell!mcmi!unocss!ho@fergvax.unl.edu
From: ho@fergvax.unl.edu (Tiny Bubbles...)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Best communication program for the PC
Message-ID: <1369@unocss..unl.edu>
Date: 8 Jan 90 19:23:24 GMT
References: <28848.25a7897c@drunivac.uucp>
Sender: root@unocss..unl.edu
Reply-To: ho@fergvax.unl.edu
Lines: 22

From article <28848.25a7897c@drunivac.uucp>, by pcoen@drunivac.uucp (Paul Coen):
> In article <1990Jan7.002029.14315@csusac.csus.edu>, scott@csusac.csus.edu (L. Scott Emmons) writes:
>> 
>> He must be using a _very_ old version.  Every version of Telix I've tried (in
>> the last 2 years) has worked _Perfectly_ on all flavors of UNIX and curses we
> 
> Well, Telix 3.11 (I think it was 3.11, it might've been 3.10) had very 
> poor VT100 emulation for Vax/VMS systems.  It just can't handle many 
> of VMS's SMG routines for screen drawing.  MS-Kermit does this very 

I think the main problem with Telix before (before 3.12, that is) was the 
lack of proper cursor-key mapping.  I've tried 3.12 with VMS, and it now
seems to work fine.

I have found that MS-Kermit has a plethora of drawbacks which make it 
unsuitable for beginning users.  It reminds me a lot of ZComm.  Both are
very good and extremely powerful communications packages.  But both have a
user interface that makes DOS seem like a beginner's dream system.
---
        ... Michael Ho, University of Nebraska
Internet: ho@hoss.unl.edu               USnail:  115 Nebraska Union
                                                 Lincoln, NE 68588-0461