Path: utzoo!attcan!uunet!cs.utexas.edu!news-server.csri.toronto.edu!utgpu!watserv1!watdragon!rose!sbnicol
From: sbnicol@rose.waterloo.edu (Scott Nicol)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Procomm - - Something Bet
Message-ID: <22599@watdragon.waterloo.edu>
Date: 28 Mar 90 16:45:11 GMT
References: <90032502290027@masnet.uucp> <1990Mar25.200722.27200@uncecs.edu> <1990Mar27.092917.15420@uwasa.fi>
Sender: daemon@watdragon.waterloo.edu
Organization: University of Waterloo
Lines: 19

In article <1990Mar27.092917.15420@uwasa.fi> ts@uwasa.fi (Timo Salmi LASK) writes:
>In article <1990Mar25.200722.27200@uncecs.edu> mvolo@uncecs.edu (Michael R. Volow) writes:
>>I'm also considering switching from Procomm+ to Telix because of the
>>internal Zmodem (although the next Procomm+ version may have this).
>>Does Telix allow big packet Kermit or Super Kermit?
>
>No, neither Telix nor Procomm allow long Kermit packages. 

   But Telix allows you to define external protocals.  I wrote
a couple of scripts to interface mskermit (3.00) with Telix.  Then,
all you have to do is setup kermit (in the mskermit.ini file) to
do large-packet transfers.  Downloading works transparently, uploading
is almost transparent (you have to enter "s filename" within kermit,
and then "q" when the transfer is complete).

- Scott
Email: sbnicol@rose.waterloo.edu  -or- ...!uunet!watmath!rose!sbnicol
SlowMail: 546 FallingBrook Dr., Waterloo, Ont., Canada, N2L 4N4.
Phone: (519) 725-1980