From: "Alex Oleynikov" Newsgroups: comp.os.msdos.djgpp References: <36F74B8910ED2E4AB98A2E8829085F151740 AT email2k DOT compuweigh DOT com> <1026239617 DOT 616997 AT queeg DOT ludd DOT luth DOT se> <1026501851 DOT 402445 AT queeg DOT ludd DOT luth DOT se> Subject: Re: Stderr redirection problems Lines: 26 X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: Date: Fri, 12 Jul 2002 21:11:01 GMT NNTP-Posting-Host: 68.15.54.9 X-Complaints-To: abuse AT cox DOT net X-Trace: news2.east.cox.net 1026508261 68.15.54.9 (Fri, 12 Jul 2002 17:11:01 EDT) NNTP-Posting-Date: Fri, 12 Jul 2002 17:11:01 EDT Organization: Cox Communications To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Martin Str|mberg" wrote in message news:1026501851 DOT 402445 AT queeg DOT ludd DOT luth DOT se... > Alex Oleynikov 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... I am not sure that I am familiar with this tool. Can you please send me a link to a web-page describing what it is and how it can be used. Thanks, Alex