<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Thu, 26 Feb 1998 16:57:57 +0100
From   : Robert Schmidt <rsc@...>
Subject: Re: __CATALOG__ files

> Spaces aren't handled in my conversion utilities at least, and not in my
> emulator, because the original Beeb didn't support them either. Actually I
> cheat a bit here, because they could be handled fine, but by sticking
> closely to the BBC I make things easier for myself and am able to say it's
> a good thing ;-)

Hmmm... I seem to recall that files on tape could have spaces.  I am, of
course, unable to verify this... :)  DFS file names were more limited
than those on tape: specifically the maximum length was shorter, and
files on tape could very well have the same name.

Which brings me to a field I forgot to mention:

NEXT=<file>

This specifies the name of the next file (dumped from tape).  Some tape
programs load their parts by using CHAIN "" or "*RUN" - which doesn't
work on DFS.  The NEXT-field at least tries to give an indication as tho
the sequence in which files were found on the tape.  But it is useless
if files have the same BBC names...  NEXT should somehow point to the
correct "*.inf" file, I guess.
 
> Isn't the CRC field now obsolete?

Not that I know of... it was always optional in the first place, and
Wouter liked having it so that he could verify correctness of files
transferred from his BBC.  That said, I tried arguing against it... :)

Also, Wouter specified the field

LOCKED (shorthand "L" permitted)

for ... uhmmm... locked files.


--
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


<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>