Xref: utzoo comp.unix.xenix:7178 comp.unix.questions:15752 Path: utzoo!attcan!uunet!cs.utexas.edu!csd4.csd.uwm.edu!bionet!agate!ucbvax!ucdavis!deneb.ucdavis.edu!cck From: cck@deneb.ucdavis.edu (Earl H. Kinmonth) Newsgroups: comp.unix.xenix,comp.unix.questions Subject: Re: Looking for a xfer protocol (source preferred) usable with cu. Message-ID: <5144@ucdavis.ucdavis.edu> Date: 18 Aug 89 03:17:51 GMT References: <951@lakesys.UUCP> <63@nstar.UUCP> <787@eecea.eece.ksu.edu> Sender: uucp@ucdavis.ucdavis.edu Reply-To: cck@deneb.ucdavis.edu (Earl H. Kinmonth) Organization: University of California, Davis Lines: 15 [request for cu with file transfer protocol.] >Why not just use ckermit. One reason, is that ckermit on Vax hosts is a CPU pig. If you are paying for time, zmodem can be much less expensive to run (roughly 50 percent on UCD Vax 11/750s). zmodem also appears to handle binary files with less overhead and somewhat higher transfer rates. >line sharing scheme. Also, on my system ckermit writes screens much faster >than cu. My experience too. You can have the best of both worlds. zmodem can be run from ckermit on your local machine with the ! command. In fact zmodem can be run from with mskermit as well; I do it often.