Canon Lide 20 Scanner

Discussion in 'General Mac Discussion' started by djcbboy, Feb 28, 2005.

  1. djcbboy macrumors newbie

    Joined:
    May 12, 2004
    Location:
    Florida
    #1
    I have an iMac G4. Whenever I install the software for my Canon Lide 20 scanner my Imac does not sleep. This happens even when i unplug the scanner. Has anyone encountered this and been able to solve the problem?
     
  2. Sly macrumors 6502

    Sly

    Joined:
    Nov 30, 2003
    Location:
    Airstrip One
    #2
    I have the same Lide 20 scanner running fine with my imac G4. In general I stay away from 90% of peripheral manufactures instal software, OSX just doesn't need it. Bin the disks & uninstall the software! You can import scans straight in to most photo editing software, I can confirm it definitely works with Photoshop straight out the box. You may also be able to use image capture found in Applications though I haven't tried it. If you are doing any sort of image or photo manipulation (non professional) I can thoroughly recommend you get Photoshop elements which which will import from your scanner and is more than powerful enough for most tasks. Elements 2 is now V. cheap on ebay now 3 is out.
     
  3. ftaok macrumors 601

    ftaok

    Joined:
    Jan 23, 2002
    Location:
    East Coast
    #3
    djcbboy,

    I have a Canon LiDE 30 scanner and have a similar problem. If the scanner is plugged into my iBook, it will sleep when the inactivity reaches the prescribed time. However, if the scanner is not plugged in, it won't sleep unless I physically close the lid.

    The problem is that there are 2 processes that are loaded up on every restart that prevent the Mac from sleeping. If you run Process Viewer, you'll see the two processes. They are N067U_Button Manager and N124U_ Button Manager. I force quit them both and my iBook will sleep fine.

    Of course, the next time I restart, they will start-up again. I tried turning them off from the Login Items, but they still show up. So I just do the force quit and leave it at that.

    BTW, I'm on 10.2.8, but this has been happening since 10.2.
     

Share This Page