3 Replies Latest reply: Mar 24, 2012 4:48 PM by PAHU
DMerz Level 1 Level 1 (20 points)

Hello All,

 

I thought I would start a new thread since my first one was answered.  The old thread is at:  https://discussions.apple.com/message/17757734#17757734

 

 

Well, I went a couple weeks ok with the Scanner and Image Capture.  And then kaput, it doesn't work.  I thought about it some and it seemed to stop working after I did Software Update on March 17th, 2012.  In that update was a "Digital Camera Raw 3.1.0" update.  Which makes me very suspicious.

 

Here is the error I get when I open Image Capture:

 

Canon_Scanner_Image_Capture_Fail.jpg

 

So, it recognizes the scanner but can't do anything in Image Capture or the with the scanner buttons.

 

I ran Software Update again, just to see if there was a new updated scanner driver but nothing came up.

 

Any ideas?  I really want to avoid using the manufacturer's SW drivers etc.

 

Thanks in advance for the help!


MacBook Pro, Mac OS X (10.6.8), 2.4 GHz Intel Core 2 Duo, 4 GB Ram, 250 GB HD
  • 1. Re: Scanner And Image Capture Problem
    PAHU Level 6 Level 6 (14,520 points)

    Check the scan lock button on the bottom of the scanner. If this is locked it will generate the message you show. Note also that if it is set to lock, after moving it to unlock, you will have to unplug the USB cable and reconnect so that the scanner to do its little startup routine.

     

    If it is not the lock button then please reply.

  • 2. Re: Scanner And Image Capture Problem
    DMerz Level 1 Level 1 (20 points)

    PAHU,

     

    I feel like a complete idiot.  It was exactly the lock button.  The last time I finished using it, I locked it.  I totally forgot about it and I never thought of that being the problem to check.

     

    I really appreciate your help and thanks to you, I'm back and scanning!

     

    DMerz

  • 3. Re: Scanner And Image Capture Problem
    PAHU Level 6 Level 6 (14,520 points)

    Good to read that the lock was the culprit because I once had a postee with this error before and it wasn't the lock and the fix was very tedious.