Re: Not possible to send two disk drive commands after each other

From: Spiro Trikaliotis (trik-news_at_gmx.de)
Date: 2004-02-08 14:35:05

* On Sun, Feb 08, 2004 at 02:03:47PM +0100 Christian Johansson wrote:
 
> Thank you for the information. I didn't know that the PRINT# command does
> that. As I wrote I found that I didn't need to send two commands directly
> after each other (the B-P command is superfluous if you always read or write
> 256 bytes, i.e. one complete block at a time) but I will test it if I get
> the time.

Just to be sure, I had a look again at the C64 BASIC and KERNAL.

PRINT# is at $AA80, which calls $AA86 (CMD) and then performs a CLRCH
($ABB5).

CMD itself "runs" into the PRINT routine ($AAA0), while $ABB5 calls
$FFCC. $FFCC (CLRCH of the KERNAL) calls UNLISTEN if the previous device
number for output was bigger than 3 (at $F339), and UNTALK if the
previous device number for input was bigger than 3 ($F340).

So, I have confirmed that the kernal really does do send a UNLISTEN. ;-)

Spiro.

-- 
Spiro R. Trikaliotis
http://www.trikaliotis.net/

       Message was sent through the cbm-hackers mailing list

Archive generated by hypermail pre-2.1.8.