Using Thunks with Windows 95 Printer Driver

Last reviewed: November 20, 1995
Article ID: Q133090

The information in this article applies to:

Microsoft Win32 Device Development Kit (DDK) for Windows 95, version 4.0

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.

Additional reference words: 4.00 win95
KBCategory: kbprg
KBSubcategory:

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 20, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.