Date   : Fri, 20 Aug 2004 23:02:30 +0100
From   : Tim Fardell <tim.fardell@...>
Subject: Re: XFER file without an INF file?

Angus Duggan wrote:
> 
> 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.

Hmmm. I couldn't get XFER to take the file without ATTR - it said
something like "error reading attributes from inf file" or somesuch
(sorry - can't remember the exact message). But maybe that was just me
doing something wrong :-)

I wonder if there is such a thing as an automatic tool that can create
the INF file for a file? E.g., you tell it what type of file it is (e.g.
a BASIC program) and it creates the INF file for you? 

BTW, XFER is a *fantastically* useful tool! I really don't know what
we'd do without it! Thanks Angus!