No "Fiery Features" with latest driver from Canon only "Printer features".

Question

Level 1

8 points

No "Fiery Features" with latest driver from Canon only "Printer features".

No "Fiery Features" with latest driver from Canon only "Printer features". iRC5235's using 'OSX installer PKG'. Installation completes successfully. Can successfully add the printer(s). Just cannot access the "Fiery Features" just "Printer Features". Other users are working fine. The driver is "Canon iR-ADV C5200s-B2 PSV10US". Already have removed, restarted and reinstalled numerous times - no progress. It should be noted that this user may print to the devices, just cannot access any of the "Fiery features" which are desired. Any thoughts? Thank you in advance for your assistance.

iMac, Mac OS X (10.7.5)

Posted on Sep 26, 2013 9:24 AM

Reply

Answer 1

PAHU

Level 6

16,723 points

Sep 26, 2013 9:56 PM in response to BirasCreek

If the user is only getting Printer Features, then it would suggest that the wrong PPD is being selected when the printer is being added. For example, the PPD's for the internal Canon board will show Printer Features in print dialog. So while you mention the B2 driver is being used, are you sure it was selected when the print queue was created?

To check, you can open System Information (Applications > Utilities) and select Printers in the left column. Then in the top right pane, select the iR ADV C5235 with the B2 attached. The bottom right pane will give information about the print queue. The entry PPD will show which PPD is being used and it should show as you have shown above, ie "Canon iR-ADV C5200s-B2 PSV10US".

If the correct PPD was selected then another possible cause is a problem with the Fiery Features plugin. Via Finder, navigate to

/Library/Printers/Canon/PS3/PDEs/EF005626

and check that you have the file "EF005626(FF).plugin". This is the Fiery Feature plugin. If it is present, then maybe this user is having access issues to this folder/plugin.

Reply

Answer 2

BirasCreek Author

Level 1

8 points

Sep 30, 2013 10:19 AM in response to PAHU

Thank you Pahu. By running an uninstall from the effected Mac, restarting and re-running the install again from scratch (a third time), this problem was resolved.

Reply