At any one time the computer only has one PDF printer application on it and the others are cleared out, exactly as suggested, so I don't think it's the Three Stooges effect.
Typically, when I'm testing a new PDF printer application, I'll start with a fresh reinstall of the OS, to hopefully ensure there are no conflicts between present and prior drivers. Of course, they always work great in the office, but once they go out the door, the troubles begin.
Once the driver is installed on a fresh OS, what would cause it to become corrupted? Maybe that's the issue I need to prevent.
Main Topics
Browse All Topics





by: WiReDNeTPosted on 2009-01-23 at 14:54:57ID: 23453892
It "might" be that the printer drivers are corrupt, so you can first delete all the printers then go into the:
DRIVERS\W3 2X86
"Start" > "Settings" > "Printers and Faxes" > "File" > "Server Properties" > "Drivers" tab > and remove all the printer drivers here.
After doing this, go into this folder and cut and paste the files into a temp folder removing them:
C:\WINDOWS\SYSTEM32\SPOOL\
Sometimes if you try and delete them, it'll tell you that they are in use so moving them usually does the trick.
After doing this, you will need to reinstall all the printer drivers including the Adobe ones.
Another possibility, is that since you have several applications( "We've used CutePDF, doPDF, MagicPDF and BullZip PDF") all trying to intercept the call to print a PDF, that it might create the problem you are describing. So completely( folders and registry entries) removing all these apps along with the above steps might be needed.