Using Win16 printer drivers is not so stupid, as
somebody said.
In fact, it can be used to allow "winprinters" that
have no Linux
Drivers (like Lexmark Z11, Lexmark Z31,Lexmark 51,
a lot of HP
printers, etc) to print in Linux;when that
support works fine, we'll
can use wine to create an
On Tue, Dec 12, 2000 at 05:49:14PM -0800, Alexandre Julliard wrote:
Andreas Mohr [EMAIL PROTECTED] writes:
Then the program tries to do a pCreateDC call for that DC.
In this case it's a *Win16* printer driver, unfortunately.
That leads to a lockup as we need to enter Win16Lock, which is
Andreas Mohr [EMAIL PROTECTED] writes:
So every time we've got an incredibly stupid locking problem,
we are supposed to give up major functionality, just like...
poff.. that's it ! ?
The stupid locking problem is that Win16 code is not thread-safe; go
complain to Microsoft. If the choice
Andreas Mohr [EMAIL PROTECTED] writes:
Then the program tries to do a pCreateDC call for that DC.
In this case it's a *Win16* printer driver, unfortunately.
That leads to a lockup as we need to enter Win16Lock, which is prohibited
as we still have the GDI lock on the DC (that we just created
Hi all,
*sigh*
Once again...
My program calls CreateICA, which calls CreateDCA - CreateDC16.
In CreateDC16, we do a DC_AllocDC, which does a GDI_AllocObject
(GDI lock gets acquired).
Then the program tries to do a pCreateDC call for that DC.
In this case it's a *Win16* printer driver,
