[Coco] Printing from Disk Extended Color Basic (via Drivewire)

[Bill Pierce]

Robert, setting the hi-speed would be normal for DW4 communication on the Coco 3 as that is needed to get the 115k baud. Hence why the DW HDBDOS is ALWAYS in hi-speed.
To keep it lo-speed, just set the dw4 server for a Coco 2 instead as that uses half the baud rate :-)
(and/or use the Coco 2 HDBDOS)

 

 


Bill Pierce
"Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull

 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
Global Moderator for TRS-80/Tandy Color Computer Forums
http://www.tandycoco.com/forum/

E-Mail: ooogalapasooo at aol.com


 

 

-----Original Message-----
From: Robert Gault <robert.gault at att.net>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Fri, Dec 23, 2016 3:18 pm
Subject: Re: [Coco] Printing from Disk Extended Color Basic (via Drivewire)

Arthur Flexser wrote:> On Fri, Dec 23, 2016 at 8:46 AM, Robert Gault <robert.gault at att.net> wrote:>>> Arthur Flexser wrote:>>>>> Robert, it is true that Basic resets the value in $6F to zero when screen>>> output (like printing OK) is required.  But I'm reasonably sure (though>>> it's been a long time) that if you include the DIR command on the same>>> line>>> as a poke to $6F, the value will remain throughout the execution of the>>> DIR.>>>>>> In fact, you could extend the command with POKE&H6F,&HFE:DIR:PRINT>>> FREE(0);" Free grans" to cause the amount of free space left on the disk>>> to>>> print out below the directory.>>>>>> Art>>>>>>>> I tried that with my original ml code and it did not work as the Coco>> froze per the OP's email. It failed for LLIST and also PRINT #-2. It did>> work with VCC using its own printer routines and probably would work with a>> Coco and attached printer.>>>>>> Robert>>>> Perhaps it would work if you poked the printer routine to knock out the> check for whether the printer is ready that is done before each character> is printed?  Or, are you bypassing the original print routine entirely?>> Art>Art,I place at $A2BF (start of the line printer code) a JMP Main. There is also at $A30A (print to screen) a JMP TstChg so that I flush the DW4 print buffer if necessary.The entire ROM printer routine is bypassed.As an update, I have been able to alter my code so that the DW HDBDOS ROM is not required. You can write to Drivewire with a standard disk ROM.Of some interest, I had to set the Coco clock to the fast rate $FFD9 before sending to DW4 and back to slow $FFD8 after flushing the DW4 buffer.Robert-- Coco mailing listCoco at maltedmedia.comhttps://pairlist5.pair.net/mailman/listinfo/coco