Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!uupsi!ncs.dnd.ca!rutgers!columbia!cunixf!cunixb.cc.columbia.edu!kgs
From: kgs@cunixb.cc.columbia.edu (Kok G Sang)
Newsgroups: comp.sys.apple
Subject: Re: Zmodem's in ProTERM  (was:Re: 4k-Xmodem)
Message-ID: <1990Feb27.182648.23839@cunixf.cc.columbia.edu>
Date: 27 Feb 90 18:26:48 GMT
References: <300.infoapple.net@pro-generic> <2311@ultb.isc.rit.edu> <6862@ucdavis.ucdavis.edu>
Sender: usenet@cunixf.cc.columbia.edu (The Network News)
Reply-To: kgs@cunixb.cc.columbia.edu (Kok G Sang)
Organization: Columbia University
Lines: 15

In article <6862@ucdavis.ucdavis.edu> unknown@ucscb.UCSC.EDU (The Unknown User) writes:

>But Les Barstow is wrong.  ProTERM, God's gift to terminal programs (if there
>was a such thing as a God), has Zmodem! I've heard it's basically useless
>unless you're using a GS and downloading straight to a RAMDISK... but it
>might work downloading to a RAMDISK on pre GSes too..  [btw: Ascii Express
>holds a distant second in my book]


I don't believe ProTERM's Zmodem protocol is the actual thing.  From what I 
heard, it doesn't allow you to resume transfer once a transfer has been 
aborted, i.e., continue transfer from where it last aborted w/o having to 
re-send the whole file.

-Kok