Adobe PDFplugin problem: a follow-up
Adobe PDFplugin problem: a follow-up
A couple of readers (Mike Bobkiewicz and Edward Sanderson) suggested that the reported problem (and related ones such as -43 errors when printing from the driver) are due to the differences in the PrintingLib file for the Adobe driver vs. the LaserWriter driver (a general issue we have discussed before regarding previous versions of the drivers). Reinstalling one driver or the other and not switching between them will generally fix things (use the PrintingLib file from the LaserWriter driver if you intend to switch between drivers). [We have received some feedback that the PrintingLib file is now the same in both drivers, but I have not yet confirmed this.]
Update: Paul Berkowitz confirms: "AdobePS 8.6 does use Apple's PrintingLib 8.6.5 , and installs it where required (i.e., it replaces the earlier Adobe version of PrintingLib for Adobe and other upgraders, and leaves 8.6.5 in place if installing AdobePS for the first time from Mac OS 8.6). It also installs a new supplementary "Adobe PrintingLib" which has no conflicts and removes (its own) OEMClib (installed by PS 8.5.1) when upgrading, again without any problems. With this version, there should no longer be problems with Distiller or any of the Adobe applications which used PS 8.5.1 and the OEMClib."
On the matter of the plugin being unable to locate Distiller, Larry Rosenstein reports: "I found that the PDFplugin couldn't locate Acrobat Distiller unless it was on the boot volume. This was annoying because the plugin checks for Distiller each time you choose Page Setup or Print. I eventually moved Distiller to the boot volume and all was OK."
On another note, Robert Engstroem found that installing the Adobe driver fixed problems he was having printing to his Fiery X2 Xerox 5750 and Cyclone Colorbus printers via the LaserWriter driver.