BUG: Print Processors Will Not Be Deleted with DeletePrintPro

Last reviewed: June 11, 1996
Article ID: Q151887
The information in this article applies to:
  • Microsoft Win32 Device Driver Kit (DDK)for Windows 95, version 4.0

SYMPTOMS

Under Win95, the Win32 API DeletePrintProcessor function will not remove the print processor from the list of installed print processors or remove the print processor from the \WINDOWS\SYSTEM directory.

CAUSE

Win95's DeletePrintProcessor() does nothing but return TRUE. The print processor that was to be deleted will still show up when the Win32 API EnumPrintProcessors function is called. Also, the print processor .DLL will still be in the \WINDOWS\SYSTEM directory.

RESOLUTION

The bug has been reported and will not be fixed until the next OPK release of Windows 95. There are a couple of workarounds to removing the print processor .DLL file. One method to remove the print processor .DLL is to boot Win95 with the spooler not running (e.g. boot with no printer shared, and print folder not open). Another method is to shut down Win95 and go to a MS-DOS session and delete the print processor .DLL from the \WINDOWS\SYSTEM directory.

STATUS

Microsoft has confirmed this to be a problem 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: 4.00 spool subsystem
KBCategory: kbprg kbprint kbbuglist
KBSubcategory: DDKPRNT



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: June 11, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.