Path: utzoo!attcan!uunet!lll-winken!ames!ncar!tank!uwvax!astroatc!nicmad!madnix!aaron
From: aaron@madnix.UUCP (Aaron Avery)
Newsgroups: comp.sys.amiga
Subject: Re: Atalk III 1.0e
Message-ID: <405@madnix.UUCP>
Date: 17 Jan 89 07:15:03 GMT
References: <242@lakesys.UUCP> <00063@meph.UUCP> <14652@oberon.USC.EDU> <293@lakesys.UUCP> <470@infohh.rmi.de>
Reply-To: aaron@madnix.UUCP (Aaron Avery)
Organization: ASDG Incorporated
Lines: 19

In article <470@infohh.rmi.de> shimoda@infohh.rmi.de (Markus Schmidt) writes:
>with chopping. According to Chuck Forsberg you may pad either with NUL
>or CMP_EOF, and there is no reason for not using CMP_EOF when the last
>byte of the file is NUL. 
>Of course the receiver may only chop those PADs that match the last byte
>in the transfer and not mixed 00 and 1A.

This is the correct way to do it. This is how I've always done it. This,
however, still cannot deal with the file who's real length exactly fills the
last block. Then, if the last character or few characters are either NULL or
CPM_EOF, they will (incorrectly) get chopped. More people should just support
simple batch Ymodem. It's almost exactly the same as Xmodem (code wise), sends
the filename and length, and handles batch transfers.

-- 
Aaron Avery, ASDG Inc.         "A mime is a terrible thing to waste."
                                                             -- Robin Williams
ARPA: madnix!aaron@cs.wisc.edu   {uunet|ncoast}!marque!
UUCP:   {harvard|rutgers|ucbvax}!uwvax!astroatc!nicmad!madnix!aaron