[Coco] Printing from DW

[Kandur]

The winner is the KISS principle again. :)
> Sounds like a lot of mucking around. Not worth the trouble.
> I'll just use VCC to do the print.
> Nick

Kandur

Saturday, October 25, 2014, 7:55:26 PM, you wrote:
> On 26/10/2014 12:14 PM, Gene Heskett wrote:
>> A wee bit perhaps. ;-)

>> I have some bash scripts in use here, that take what I send to the /p that
>> is setup in the bootfile as a drivewire channel.  In drivewire, I have it
>> intercept that data and write it to a file, raw just like the coco sent
>> it.

>> One of the accessories to the script is a setup of inotifywait, one of
>> linux's handier little utils, watching the location directory drivewire
>> saves the file in.  When a file is closed, complete IOW, inotifywait sends
>> my script a message containing the hashed name of the new file.  My script
>> then scans the old jobs directory, deletes the oldest of 25 files, renames
>> the just saved file according to my bookkeeping scheme, and saves it in a
>> second scratch directory, then issues an
>> "lp -dBROTHEHL2140 new name of file".

>> Cups then processes the text, rendering it for that printer and sending it
>> back down the cable to a hub on the coco3 desk which has this printer
>> sitting on the top shelf.  Its a B&W laser, costs about a 100 $ bill, does
>> 19 pages a minute, and its warming up the drum about 5 seconds after I get
>> my prompt back on the coco from having typed "list filename >/p".

>> Fastest printer I've ever had on my coco's, and since its a 600 dpi
>> printer, none of the butt ugly 7x9 dot matrix fonts. Beautiful output, 10x
>> faster than ever before.  Music to these old eyes.

>> There's some earlier versions of what I am running on my web page, but I
>> need to replace them with a tarball containing the latest versions.  In
>> the meantime, you bash hackers can fix whats there to do it your way if
>> you'd like.



> Sounds like a lot of mucking around. Not worth the trouble.

> I'll just use VCC to do the print.

> Nick