Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!agate!violet.berkeley.edu!ilan343
From: ilan343@violet.berkeley.edu (Geraldo Veiga)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Trouble with Telix Kermit
Keywords: n
Message-ID: <1991Jan13.222953.24375@agate.berkeley.edu>
Date: 13 Jan 91 22:29:53 GMT
References: <3129@mentor.cc.purdue.edu> <27977.2790e52f@nt.sait.edu.au> <1991Jan13.211741.6620@murdoch.acc.Virginia.EDU>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Organization: University of California, Berkeley
Lines: 20

In article <1991Jan13.211741.6620@murdoch.acc.Virginia.EDU> dmm0t@holmes.acc.Virginia.EDU (Dave Meyer) writes:
>
>My suggestion:  use a better kermit program.  I'm using the
>program mstibm.exe from watsun.cc.columbia.edu, under /kermit/bin.
>It's the latest release, and includes sliding windows, which is
>tremendously faster.  Also on watsun under /kermit/sw is the source
>for kermit with sliding windows, so you can compile it on your
>host machine.
>
How does this compare to other protocols like Ymodem an Zmodem?

I've recently switched from (old) kermit to zmodem for all my
micro-mainframe transfers.  It speeded up things by a factor of (at
least) 2.  The rzsz package (ftp'able from simtel20) compiled without
changes in every Unix machine I tried.   Combine this with Telix (under
DOS) or pcomm (under unix) and you are in business.

Can the new kermit can match zmodem in speed?  Also, I assume both
sides will have to be aware of the new kermit protocol.  How would you
make it work with existing DOS software like Telix or Procomm?