Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84 chuqui version 1.7 9/23/84; site nsc.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!nsc!nessus
From: nessus@nsc.UUCP (Kchula-Rrit)
Newsgroups: net.micro
Subject: HELP! My printer locks up!
Message-ID: <2641@nsc.UUCP>
Date: Fri, 26-Apr-85 17:52:19 EST
Article-I.D.: nsc.2641
Posted: Fri Apr 26 17:52:19 1985
Date-Received: Sat, 27-Apr-85 07:48:47 EST
Distribution: na
Organization: The Patriarchy of Kzin, Kzin
Lines: 31

*** REPLACE THIS LINE WITH KZINTI SCRIPT ***

     I have a problem with a Integral Data Systems IDS-440 "Paper Tiger"
printer.  My old printer driver(BASIC PEEKs and POKEs) worked fine with this
printer.  I sent the data to the parallel port and toggled the strobe, then
waited 100ms for each character.  This worked fine but was/is S-L-O-W.

     Then I decided to use the BUSY signal provided by the printer and avoid the
time delay.  I checked BUSY and if it was high, then I would wait until it went
low.  The printer prints on recieving a line feed or carriage return, otherwise
it collects the data in a buffer.  My printer has a 2K buffer in it.  I tried
printing a file with the new driver, with good results and, of course much
faster.  In my "BUSY wait" loop, there is a "waiting..." message to indicate
that BUSY is active.  I never saw the message in normal operation, so far
so good...

     The next thing I did was to send a LARGE(4000) number of characters to the
printer without sending a line feed or carriage return to see if BUSY really
worked, or if my BASIC was too slow to catch it.  Well, nothing happened for
about 30 seconds, then the computer printed the "BUSY wait" message.  Fine,
except that BUSY never went away!!  I aborted the program and tried to send data
to the printer by hand by PEEKing and POKing.  After sending a few carriage
returns and line feeds and still getting no response from the printer and
nothing printed, I had to cycle the power on the printer to get it out the
"endless loop"

     Does anyone out there know of a fix for this bug/mis-feature?  For now,
I hope I don't fill the buffer again...

			     Kchula-Rrit
			     !menlo70!nsc!nessus