Date   : Sat, 11 Jul 2009 09:29:48 +0100
From   : info@... (Sprow)
Subject: Master ethernet upgrade

In article <8B61DB745B124DA580F646F5FEFC3AF8@...>,
   Mark Haysman <jumbos.bazzar@...> wrote:
> > They're written to an "inf" file of the same base name.
> > So
> >  example        FFFF8023 FFFF0E00
> > would have a corresponding file
> >  example.inf
> > containing that data.
>
> The .inf files can get easily lost if dragged across PC 
> windows that don't show hidden files. 

I should add that the "inf" file doesn't have to be hidden, so if you
download a ZIP containing Elite from a games website and unzip it (where you
will find "inf" files inside), these will be picked up too.

>   example-!METADATA!FFFF1900FFFF0823
>
> I realise this then produces files that are not the same length as the 
> original, but if the software used to load and save them adds and removes 
> the data automatically, and when copied to an FS that stores it's own data 
> (DFS etc), the data is removed, and the file restored to normal by the 
> filesystem or utility doing the copying, then it's only ever in the longer 
> version with the data on the PC side of things.

It probably depends on what you use the system for:

If you only ever view files from the BBC side it doesn't matter how the
filenames get mangled when stored on the PC - the PC is just acting as a
remote harddisc. You could even just save everything in one big disc image
file and ignore the underlying FAT or NTFS or whatever.

If you plan to view files from the PC side then saving a file, it's more
natural to see directories full of conventional filenames so that a file
called "example" on the PC is listed as "example" on the BBC.

In article <090711005501@...>,
   Jonathan Graham Harston <jgh@...> wrote:
> > Where are the load/execute addresses stored on the Windows share?
>  
> They should be stored where-ever pre-existing Window shares such as
> LanManFS stores Acorn load/exec addresses.

The problem is RISC OS LanManFS doesn't save load/exec addresses, as RISC OS
long since deprecated them. What it does is append ",ttt" to the name where
ttt is the 3 nybble filetype.

So: 
 "example,feb"
would appear as 
 "example"
typed as an Obey file. Try as I might I can't squeeze 64 bits of load and
execution address into 3 nybbles in a compatible way,
Sprow.