From: "Alex Oleynikov" Newsgroups: comp.os.msdos.djgpp Subject: GRX printing library Lines: 19 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: <4etO8.17654$hF5.636479@news2.east.cox.net> Date: Fri, 14 Jun 2002 21:28:32 GMT NNTP-Posting-Host: 68.15.54.9 X-Complaints-To: abuse AT cox DOT net X-Trace: news2.east.cox.net 1024090112 68.15.54.9 (Fri, 14 Jun 2002 17:28:32 EDT) NNTP-Posting-Date: Fri, 14 Jun 2002 17:28:32 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 Hi everybody, I've got a question on using the printing library which comes as a contributed package to the GRX library. It looks like when this printing library is used it invalidates the current device driver of the GRX and creates a new "memory" driver to do printing. The simple program to test printing that comes with the library works OK, since there are no other programs using GRX at that moment, but if you try to invoke printing routines from a GUI environment residing on GRX it immediately crashes (I use MGUI with VESA driver, but I think any other GUI would behave similarly, when its primary driver is gone). Is there a way to have multiple device drivers in GRX simultaneously , so using one does not affect others? Thanks for any advices. Alex