From:	Martin Str|mberg <ams AT speedy DOT ludd DOT luth DOT se>
Subject:	Re: Stderr redirection problems
Newsgroups:	comp.os.msdos.djgpp
References:	<36F74B8910ED2E4AB98A2E8829085F151740 AT email2k DOT compuweigh DOT com> <1026239617 DOT 616997 AT queeg DOT ludd DOT luth DOT se> <BBHW8.42743$%%2 DOT 1977894 AT news2 DOT east DOT cox DOT net> <agn0ie$a41$1 AT antares DOT lu DOT erisoft DOT se> <bPFX8.63227$%%2 DOT 2645173 AT news2 DOT east DOT cox DOT net>
User-Agent:	tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (NetBSD/1.5_BETA (alpha))
Message-ID:	<1026501851.402445@queeg.ludd.luth.se>
Cache-Post-Path:	queeg.ludd.luth.se!unknown AT speedy DOT ludd DOT luth DOT se
X-Cache:	nntpcache 2.4.0b5 (see http://www.nntpcache.org/)
Date:	12 Jul 2002 19:24:11 GMT
Lines:	18
NNTP-Posting-Date:	12 Jul 2002 19:24:11 GMT
NNTP-Posting-Host:	queeg.ludd.luth.se
X-Trace:	1026501851 news.luth.se 465 130.240.16.109
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Alex Oleynikov <alex AT compuweigh DOT com> wrote:
:> Ok. How about adding a file system extension (FSEXT) that handles the
:> device (say you name it "my_prn") and then you open it and fprintf()
:> as usual to it. In the extension you use the serial comm. library
:> (which name I've forgotten right now) and detect if something goes
:> wrong and set errno accordingly and return -1?

: As I said before, I have to know precisely when something happens with the
: printer and what exactly has happened. For that matter I need a
: bi-directional communication with the printer, since it is capable of
: returning its own status information back to the program on request.

Yes. And that's what you should do in the FSEXT...


Right,

						MartinS

- Raw text -