Canon IR C5870U driver

Question

Level 1

9 points

Canon IR C5870U driver

My network at work has an IR C5870U, which vanished when I installed SL. Trying to add it now, I can enter the IP and "select software", which gives me the C5870. (Not sure whether the U is significant.) Then when I try to print, I get an error message: "The printer software was installed incorrectly. Please reinstall the printer’s software or contact the manufacturer for assistance."

Here's the wildcard, though: If I select "Generic PostScript Printer," it prints just fine... on 11 x 17 paper. This also happens to a friend at work who's running OSX without SL.

Suggestions, anybody?

Macbook Pro, Mac OS X (10.6)

Posted on Sep 8, 2009 11:03 AM

Reply

Answer 1

PAHU

Level 6

16,705 points

Sep 8, 2009 7:10 PM in response to J M H

The error message that you see occurs when using the imagePASS G1 (EFI - Fiery) print driver. Some other postings on this forum have indicated they have resolved this message by changing the ownership on the Fiery files. In testing I haven't been as successful to our iRC5185 with H1 so I have only been able to print to this machine using the Generic PostScript, which prints fine but doesn't give any finishing features or allow A3 as a paper size. Knowing this limitation I haven't let any of my Mac users install 10.6 yet so we're still printing fine with 10.5.8.

With regards to the friend who is not running SL, not sure if you meant he was getting the same error message with 10.5.x which is unusual. Or if you meant he was also able to print using Generic PostScript, which will work with any version of OS X.

Pahu

Reply

Answer 2

J M H Author

Level 1

9 points

Sep 9, 2009 7:31 AM in response to PAHU

Both Mac users in our office, me with SL and my friend without, are having the issue of only being able to print on 11 x 17. Mine does this only when using the generic driver; when attempting to use the real driver nothing works at all.

Reply

Answer 3

J M H Author

Level 1

9 points

Sep 11, 2009 8:28 AM in response to J M H

Got this fixed, strangely enough, by just downloading the pre-SL drivers and manually selecting the right one. Looks like that should work for me and my friend.

Reply