Date   : Fri, 20 Aug 2004 10:52:55 -0700
From   : Angus Duggan <angus.duggan@...>
Subject: Re: XFER file without an INF file?

Tim Fardell writes:
>FORMAT.TXT is actually rather badly wrong on this - it says the only two
>compulsory values are LOAD and EXEC. You actually need to include LENGTH, ATTR
>and TYPE to get it accepted by XFER - the last two of which are not even
>documented. 
>
>Finally ended up with the following, after some fiddling: 
>
>$.BAR ffff0e00 ffff802b 001050 ATTR=0 TYPE=1

Hmm, yes, XFer 4 could do with better documentation. The values are exactly
as specified for OSFILE operations in the Advanced User Guide. So ATTR is the
read/write/execute/delete attributes, of which "L" is a short form for
readable but not deletable, and TYPE is either 1 for files, or 2 for
directories (on filing systems that support them). XFer 4 does not make
assumptions about the filing system supported for file transfer operations,
only when transferring disc images.

The shows that OPT4, ATTR, and TYPE keys are optional, however load, exec,
and length are required. There isn't any reason why length shouldn't be made
optional, it could be queried from the file.

a.