BUG: GDI Assertion Failure in PostScript Driver

 Last reviewed: August 29, 1995
Article ID: Q135843
The information in this article applies to:
  • Microsoft Win32 Device Development Kit (DDK) for Windows NT, version 3.51

SYMPTOMS

The sample PostScript printer driver does not load as built with the Windows NT DDK version 3.51. When you test the driver from Notepad the following error occurs: 

   Cannot access your printer.
   Be sure that your printer is connected properly and use Control Panel
   to verify that the printer is configured properly.
A checked build of the driver gives the following messages in WinDbg/WinDbgRm: 

   "GDI Assertion Failure: PSCRIPT!GetFont: Couldn't find font resource."
   "GDI Assertion Failure: PSCRIPT!DrvEnablePDEV:  GetFont failed."
   "Module Unload: C:\WINNT351\SYSTEM32\SPOOL\DRIVERS\W32X86\1\PSCRIPT.DLL"

RESOLUTION

Add the following lines to the SOURCES file for the driver:

DLLENTRY=PSDLLInitProc SUBSYSTEM_VERSION=3.50

The first flag makes the pscript DLL initializing entry point visible to the system. The second flag, which is optional, disables some new options in the linker so that the resulting driver can be run on a version 3.5 system.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: 3.51
KBCategory: kbprg kbbuglist
KBSubcategory: ntddkprnt

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: August 29, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.