<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Thu, 25 Jun 2009 18:15:35 +0100
From   : michael.firth@... (Firth,MJC,Michael,DMJ R)
Subject: Finding file information from .zips

The Unix 'nspark' utility seems to put the load / execute addresses in to 
a RiscOS script file if it finds these in a .ZIP. It should be relatively
straightforward to either post-process this file to generate .INF files,
or change the 'nspark' sources to make it generate these instead.

I presume the DOS version does this too, but the version I have seems to
be a 16-bit app, and gets upset by long filenames.

It would seem to me easier to convert an existing ZIP utility to generate
.INF files if it finds the extra information, than to add full ZIP functionality
to (A)DFS-Explorer.

I agree it would be simpler if PCs, Unix and MacOS could natively understand
BBC/RiscOS file information, but they don't.

Unfortunately RiscOS seems to be a dying platform (there is only one new
hardware option available that will run it natively), so I think it is unlikely
that many people would move to it for Internet use if it isn't already their
main platform.

Regards

Michael

-----Original Message-----
From: Andy Ford <acorn@...>
Sent: 24 June 2009 13:11
To: bbc-micro@... <bbc-micro@...>
Subject: [BBC-Micro] Finding file information from .zips

Just a very quick question. I "know" this has been answered before 
(sorry) but I am unable to find it to familiarise myself.

Basically, if you grab a .zip containing a few files and then extract 
the .zip on Windows, although the files are present attempting to add 
them to either ADFS / DFS explorer or BBC explorer, there is no 
information (load and exec addresses etc)

A good example of what I mean is one of these two .zips

www.mdfsnet.f9.co.uk/Mirror/Archive/Acorn/ (for my specific case the

[The entire original message is not included]
<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>