Date : Wed, 25 Feb 1998 09:42:45 +0100
From : Robert Schmidt <rsc@...>
Subject: Re: __CATALOG__ files
Look at the contents of a __CATALOG__ file and then some *.inf files,
and you should be able to figure it out: each line in __CATALOG__ is
roughly equivalent to one *.inf.
Split __CATALOG__ into several *.inf files. The name of each "FILE.inf"
file corresponds to one "FILE" BBC file. Touch up the format a bit. For
example, the file name *inside* an *.inf file should have the directory
prefix, or "$." if the file is in the main directory.
In general, the basic format for an *.inf file is this:
<BBC file name> <load address> <exec address>
Addresses are in hex, with no pre- or postfixes.
Here's an example: a BASIC program has the BBC file name
"Amazing3DMaze". The file name with which this is represented in the
standard archive format is irrelevant, as the BBC file name is fully
specified in the corresponding *.inf file. So in your PC directory, you
might have it stored as "A3DMAZE". The *.inf file "A3DMAZE.inf" will
then contain:
$.Amazing3DMaze E00 8023
Spaces in file names are currently not catered for, I think, though it'd
seem natural to enclose the name in double quotes. E.g:
"$.Amazing 3D Maze" E00 8023
This might not be handled by the currently available utilities (Wouter's
bbcim, Tom's WSCONV) or Dave's emulator. Could any of you comment on
this?
The format supports other optional fields after <exec address> (all
numbers in hex as above):
<length>: size in bytes (for file verification)
<start sector>: permits more faithful reproduction of disk images
CRC=<value>: a CRC value calculated according to the algorithm given
in the AUG (for file verification)
OPT4=<value>: specifies the *OPT4,x value for a disk image: only
has effect in the *.inf file for the BBC file "!BOOT".
--
Robert Schmidt <rsc@... >
Software Developer / Vingmed Sound tel +47 67124237 fax +47 67124355
Private tel +47 22606076 WWW http://www.nvg.unit.no/~rsc
jeg lukker et oye og ser halvt
jeg lukker begge og ser alt -- seigmen