Date   : Mon, 13 Jul 2009 15:50:39 +0100
From   : jumbos.bazzar@... (Mark Haysman)
Subject: Master ethernet upgrade

> "Mark Haysman" wrote:
>> prefer to see the data stored at the end of a file, along with an 
>> identifier
>> string, for example...
>>
>> end of file-!METADATA!FFFF1900FFFF0823
>
> An NFS mounted on a Unix server stores the load/exec addresses as
> eight additional bytes at the end of the file:
>
> "If a Unix file has the extension ",lxa" then RISC OS NFS assumes
> it to be a RISC OS untyped file that it created. It uses the last 8
> bytes of the file to store the load and execution addresses. So, if
> they were:
>
> -------------------+--+--+--+--+--+--+--+--+
> Normal contents... |67|45|23|01|EF|CD|AB|89|
> -------------------+--+--+--+--+--+--+--+--+
>                   ^                       ^
>         Place where RISC OS     Place where Unix file
>               file ends               file ends
>
> the load address would be &01234567 and the execution address would
> be &89ABCDEF."
>
> TCP/IP Protocol Suite User Guide, p121
>
> Whatever method is used, it should be a pre-existing method so that
> files that are already copied onto the media can be accessed
> without special actions being needed.

So if I were to impliment this method on DataCentre for Drive 5 direct to 
USB saves, and get RamFS to add the .lxa extension with that data, that 
would be the most "compatible" way of doing it? Also, it would then 
recognise .lxa files and be able to read the data before loading the file 
into memory.

If that's the case I'll add functionality that to the next RamFS update.

Mark.