[EMAIL PROTECTED] wrote: > didn't it have 1 word, 2 bytes per sector: the file number in one byte ($f8 > = sector map, $fd = free, $ff = dead) plus the block number within the file > in the othe byte?
I can't remember :o( > > Note tpp, every file fragmented of necessity by the interleave factor > That begs the question of what one means by fragmented? I remember this. If I'm not mistaken the default interleave for floppies is three so when one bit of file has been read and processed the next bit *should* be arriving at the heads ready to be read. Now, a fragmented file will not have the 'next chunck' in the correct sectors as defined by the interleave, but will be elsewhere - hence, technically, fragmented. Simon N Goodwin (I thnk) did a fast loader as part of the DIY Toolkit (assuming that it was Simon) which allowed the changing of the interleave to speed up loading on faster systems. (Or something like that - note how accurate I'm being this morning!) > would be passing the read head...did it take into account "scatter"[1] > loading? Here we go again, scaning the Organic RAM for info that's not quite there, or may have parity errors, but : LOAD and SAVE load and saves files in order (ie SuperBasic files). SBYTES and LBYTES does the scatter loading. So the interleave is good for LOAD/SAVE but meaningless for SBYTES/LBYTES. (or is it the other way around?) I suspect I have got it right this time as a SuperBasic program being loaded would have each line parsed and tokenised whihc takes a bit of time. Cheers, Norman. _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
