4 Replies Latest reply: Oct 6, 2012 12:13 PM by DMerz
DMerz Level 1 Level 1 (20 points)

Running OS X v10.8.2 on mid-2010 MacBook Pro.


Have a Canon CanoScan LiDE210 which is working fine with 10.8.2.


Just saw on the Apple download page (October 4th, 2012):  Canon Printer Drivers v2.10 for OS X


Clicked to: "For information about supported printer models, see: http://support.apple.com/kb/HT3669#canon "  where the LiDE210 is listed. 


However, it says:



Canon CanoScan LiDE 210 *1.5.0s



On my MacBook, under "System Information", I have:


Canon CanoScan LiDE210.jpg


And the Canon Website lists the current driver as:


ICA Driver Ver.1.5.1t (OS X 10.6/10.7/10.8)

File Name: misd-mac-1_5_1t.dmg


So, do I get the Apple download (v 1.5.0s) or stay where I am at v 1.5.1?  It seems that the Apple download is a earlier version of the driver...



MacBook Pro, OS X Mountain Lion (10.8.2), 2.4 GHz Intel Core 2 Duo, 4 GB Ram, 250 GB HD
  • keg55 Level 5 Level 5 (7,030 points)

    Your decision. I have not had any issues with the OS X updates to my Canon MP560 printer. And it's listed in the link you provided. It's still working fine using the v2.10 update.

  • DMerz Level 1 Level 1 (20 points)

    Yup, if it ain't broke don't fix it....  (what I mean is it's working with the driver I have now so probably best to leave it alone).  But good to know that v2.10 didn't cause you problems.



  • VikingOSX Level 6 Level 6 (12,160 points)

    The 1.5.1t driver was from July, not October. Yes, the Oct 4 driver is 1.5.0s. It also may mean that the 1.5.1t has issues and they fell back to the 1.5.0s driver.


    Send an email to the Canon Lido 210 product team and ask which driver to use.

  • DMerz Level 1 Level 1 (20 points)

    Ok, worth a try. 


    I used it the other day with v1.5.1 that is installed on my MacBook and had no problems.  But I just today downloaded the "OS X Mountain Lion 10.8.2 Supplemental Update" and haven't tried the scanner again.  So need to do that.  Both updates were released on Oct. 4.  Don't know if that's just coincidence or they had to update the scanner driver to be compatible with the 10.8.2 Supplemental Update?