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 prohibited
> > as we still have the GDI lock on the DC (that we just created for that
> > purpose).
> >
> > Call gdi32.157: CreateICA(405a6483 "PCL5EMS",405a6474 "HP LaserJet 5M",405a648b
>"LPT1:",00000000) ret=7cb84f86 fs=008f
> >
> > Any idea what to do here ?
>
> I'm afraid there is no good solution, short of redefining the GDI
> driver interface to not call the DC functions with the GDI lock
> held. It may be easier to forget about running Win16 printer
> drivers... (does anybody really use this anyway?)
You don't really want to propose this, do you ? ;)
So every time we've got an incredibly stupid locking problem,
we are supposed to give up major functionality, just like...
poooooff.. that's it ! ?
I'm pretty sure that several people still use Win16 drivers,
as PSDRV support is still a bit weak (I never got it to run so far,
but didn't try too hard either).
So would there be a "solid" solution, other than just giving up on
Win16 drivers completely ?
Or in other words: what would need to be done in order to make it work again ?
Andreas Mohr
