Hi all,
http://support.microsoft.com/support/kb/articles/Q133/0/90.asp
A Windows 95 printer driver should only use thunks in calls to the
ABORTDOC, ENDDOC, NEWFRAME, NEXTBAND
and STARTDOC subfunctions of its Control() function.
If a Windows 95 printer driver thunks in any call other than a ABORTDOC,
ENDDOC, NEWFRAME, NEXTBAND or STARTDOC call, the Windows graphics device
interface (GDI) may become reentrant.
Because the GDI was never designed to be reentrant, the system may be left
in an unstable state or errors may occur. If the printer driver thunks or
yields, this causes the Win16Mutex system semaphore to be released and another
thread may enter the GDI.
I'm not sure whether this is related to our Win16 printer driver problem.
Does this provide any clue as to how we're allowed to solve our win16
printer driver deadlocks ?
This description smells to me as if Win95 doesn't have any form of
GDI object locking...
Andreas Mohr
