From: Spiro Trikaliotis (ml-cbmhackers_at_trikaliotis.net)
Date: 2005-11-08 09:16:57
Hello MV,
* On Mon, Nov 07, 2005 at 11:29:11PM +0100 MagerValp wrote:
> >>>>> "ST" == Spiro Trikaliotis <ml-cbmhackers@trikaliotis.net> writes:
> ST> in the 157x, there are other functions than in the 154x which are
> ST> table driven. These are much faster.
>
> The problem with table based routines are that they're hard to fit in
> the 1541's RAM - only 1.25k are available if you don't replace the
> 1541's kernal routines.
Yes, that's right. Anyway, silverdream did not tell us if he wants a
general solution or not, thus, I gave him something better.
Another thing to consider: It might be worth to transfer raw GCR data to
the C64/C128/whatever and do the decoding there. The disk can read in
the next track while the decoding is done on the computer. The overhead
of transferring more data (320 byte vs. 256 byte) might be less than the
time you gain by moving the decoding into the computer.
This scheme is also used with the "warp" routines of
SC/cbm4linux/cbm4win.
Regards,
Spiro.
--
Spiro R. Trikaliotis
http://www.trikaliotis.net/
http://cbm4win.sf.net/
Message was sent through the cbm-hackers mailing list
Archive generated by hypermail pre-2.1.8.