Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!usc!pollux.usc.edu!papa From: papa@pollux.usc.edu (Marco Papa) Newsgroups: comp.sys.amiga Subject: Re: Atalk III & Kermit Message-ID: <27412@usc.edu> Date: 8 Oct 90 06:04:30 GMT References: Sender: news@usc.edu Distribution: comp Organization: Felsina Software, Los Angeles, CA Lines: 26 Nntp-Posting-Host: pollux.usc.edu In article cimshop!davidm@uunet.UU.NET (David S. Masterson) writes: >I've been using Atalk III to connect to Vax/VMS and then using Kermit to >transfer files back and forth. Most of the time, its very reliable unless the >connection is very noisy (what else is new, right ;-). What I'd like to know, >though, is why the Transfer window on Atalk III typically reports the size of >the transferred file as 50% larger than the actual file's size. Any ideas? The built-in Kermit reports the bytes transfered including any encoding. This results in "more" bytes than the actual file size. Since Release 1.3, A-Talk III has included XPRKermit that I authored together with Steve Walton (hi, Steve! :-), and that we put in the public domain. If you don't have Release 1.3c, you can upgrade from Oxxi quite inexpensively. The XPR Kermit turns out to be MUCH more powerful than the built-in kermit: it supports 8-bit quoting, large packets, user definable options AND it displays the "correct" file size. The built-in kermit will eventually be dropped and deleted from the binary and we'll ship only with XPR-Kermit. Given the above, there is no reason for us to "fix" the built-in kermit. Note that there is NO loss in performance by using the external XPRkermit compared to the built-in kermit, while this is NOT true concerning XPR-Zmodem vs. built-in ZMODEM, and that's why we'll keep the built-in ZMODEM. -- Marco -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "Xerox sues somebody for copying?" -- David Letterman -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=