From: senelson AT yahoo DOT com (naniboujou)
Newsgroups: comp.os.msdos.djgpp
Subject: Stuck with buffered I/O when using biosprint with Windows 2000
Date: 30 Jan 2003 10:34:36 -0800
Organization: http://groups.google.com/
Lines: 12
Message-ID: <3af4482.0301301034.3e40636f@posting.google.com>
NNTP-Posting-Host: 64.154.14.115
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1043951676 11496 127.0.0.1 (30 Jan 2003 18:34:36 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: 30 Jan 2003 18:34:36 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I want to use the low level "biosprint()" control of the printer port
with Windows 2000. It looks like calling the function with command 0
to write data results in a buffered transfer. The only ways I have
discovered to actually move it to the port are: (1)Exit from the
Command window altogether, or (2)Execute a port reset (command 1). I
obviously don't want to do (1), because I have further interaction
with the port in mind after the write. If I try approach (2) and
excecute a port reset after every data transfer, one or more
additional strobes with unwanted data are also sent out and are
unexpectedly captured by my external hardware. Is there a way to flush
this port buffer, and not mess up my intended data stream? Or should I
be using some other form of low level I/O to the printer port?