<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Tue, 28 Oct 2003 08:20:03 -0800
From   : Angus Duggan <angus.duggan@...>
Subject: Re: XFER v4 problem

BBC Micro writes:
>Bob,
>
>Ok, I was a while getting back but here are my
>findings:
>
>Somewhere below is the  XFER code that reads the inf
>file, It says you need NAME LOAD EXEC LENGTH ( OPT4 |
>ATTR | TYPE )

I'm afraid some of that syntax is my doing. The original XFer only supported
locaked/not locked. I added ATTR to use the complete OSFILE attributes, in
case the DFS supported them. For some reason that seemed to make sense at the
time, I used CRC32 instead of the existing CRC to decrease collision rates.

ISTR there was an ambiguity in parsing that made it not quite possible to
support all of the old formats.

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