<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Mon, 13 Jul 2009 20:33:01 +0100
From   : jumbos.bazzar@... (Mark Haysman)
Subject: Master ethernet upgrade

>> 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?
>
> No, because that's just how RISC OS NFS might do it. For a USB stick,
> which
> I assume is FAT formatted, would be read by RISC OS' DOSFS which stores
> filetypes in a reserved field (which Windows usually zeros) and also can't
> fit the full 64 bit load/exec addresses into the native catalogue format.
> It
> also wouldn't take any special action on a filename ending in ",lxa",
> Sprow.

The only other bits I have access to are the Time Stamp. That only gives 32
bits of data, and while the modified access Stamp gives another 32 bits,
that can get messed up by an access to the file, so I think that's out.

Unless you (or someone!) can think of another way of doing it without using
a .INF file, I'll probably go with using a custom extension and adding the
metadata to the end, as it seems the neatest way of doing it. I can always
cook up a basic program to generate the metadata from .INF file and vice
versa if compatiblilty becomes necessary.

Mark.

PS. Apologies for hijacking your thread and going off topic! 
<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>