Path: utzoo!attcan!uunet!lll-winken!lll-ncis!oodis01!uplherc!wicat!meph!gsarff
From: gsarff@meph.UUCP (Gary Sarff)
Newsgroups: comp.sys.amiga
Subject: Re: Atalk III 1.0e
Message-ID: <00063@meph.UUCP>
Date: 23 Dec 88 17:52:03 GMT
References: <242@lakesys.UUCP>
Organization: WICAT Systems Inc. Orem, Utah (Engineering-R & D)
Lines: 30

In article <242@lakesys.UUCP> mikes@lakesys.UUCP (Mike Shawaluk) writes:
>In article <14049@oberon.USC.EDU> papa@pollux.usc.edu (Marco Papa) writes:
>>
>1. CHOP
>-------
>When chopping files (Transfer Auto Chop On), a temporary copy of the file 
>is made. Therefore, you should "save" the file on a disk with a number of 
>free bytes larger than twice the size of the file to receive.  The same 
>is true when transferring to a RAM disk.

What? Comm and most other term programs I have seen don't need twice the
space of a file free on disk to do autochopping.  Just look at the block
received at the end of file and scan backwards and only write out non-pad
bytes to the disk.  The way Atalk III is doing it, someone with only floppies
won't be able to download large files, and amiga is getting larger files 
all the time on bbs's and public networks as people make big animations and
such.  This sounds strange.


------------------------------------------------------------------------
"Those whom the gods would destroy, they first make mad"
He who steals my core-dump, steals trash