Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!sm.unisys.com!csun!solaria!ecphssrw@robin.csun.edu
From: ecphssrw@robin.csun.edu (Stephen Walton)
Newsgroups: comp.sys.amiga.tech
Subject: Re: ARP with 1.3
Message-ID: <638@solaria.csun.edu>
Date: 2 Apr 89 01:09:36 GMT
References: <6472@dayton.UUCP> <16432@cup.portal.com>
Sender: ecphssrw@solaria.csun.edu
Reply-To: ecphssrw@robin.csun.edu (Stephen Walton)
Distribution: usa
Organization: California State Univ., Northridge
Lines: 18
In-reply-to: FelineGrace@cup.portal.com (Dana B Bourgeois)

In article <16432@cup.portal.com>, FelineGrace@cup (Dana B Bourgeois) writes:
>
>Here is what I use [with 1.3 from ARP 1.2]:
>
>ARP List, Protect, and Copy don't handle the new protection bits.
>

In addition to this, which may seem fairly minor, ARP Copy also doesn't
work with files written to PIPE:.  Apparently, it has a test inside like
if (input-file-size < my-buffer-size)
    copy input-file-size bytes from input to output

Since the input-file-size returned by PIPE: is always 4096, ARP Copy
copies the first 4096 bytes from a PIPE: file and quits.
--
Stephen Walton, Dept. of Physics & Astronomy, Cal State Univ. Northridge
RCKG01M@CALSTATE.BITNET       ecphssrw@afws.csun.edu
swalton@solar.stanford.edu    ...!csun!afws.csun.edu!ecphssrw