badassmaurice
Level 1 (0 points)

Q: Samsung C480W scan driver installation fails

Hi

I own a Macbook Air with MAC OS X Yosemite 10.10.5.

I have downloaded the Samsung SL-C480W Scan Driver for Mac OS X at this address.

Once unzipped, I have two folders :

MAC_ICDM

MAC_TWAIN

Each folder contains a .pkg file that I've tried to use by double clicking on it.

MAC_TWAIN : ScanThru.pkg

MAC_ICDM : ICDM.pkg

 

The installation process runs correctly, I enter my password when asked, but it finally ends with the following error message :

 

"The installation failed. The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance."

 

I have contacted Samsung Support which told me that I had to contact Apple for my issue.

 

I've try to download the driver again 2 ou 3 times, but the file seems OK.

 

When I go to "Printers and scanners" I can see my C480W printer, which prints fine by the way, but when I click "Scan" then "Open Scanner", I get an error message telling that the software for this scanner is not installed.

 

What could I do to understand what goes wrong ?

Thanks

MacBook Air, OS X Yosemite (10.10.5)

Posted on Aug 31, 2015 1:56 PM

Close
badassmaurice

Q: Samsung C480W scan driver installation fails

  • All replies
  • Helpful answers

  • by CompuSaver,

    CompuSaver CompuSaver Aug 22, 2016 3:52 PM in response to badassmaurice
    Level 1 (4 points)
    Aug 22, 2016 3:52 PM in response to badassmaurice

    I had this same problem with a SCX-3405W with the OS X 10.6 - 10.11 drivers from Samsungs Website.

    ICDM.pkg and ScanThru.pkg did not install.

     

    I'm pretty sure that bad install scripts are the reason.

    I tried installing from a different drive (in my case a USB memory stick) which never worked for ICDM.pkg or ScanThru.pkg. Then I copied the installers from the USB drive to the disk drive which booted OS X and the software should have been installed and it worked without any problem.

     

    But that took me several hours to find out, since I thought something different might have been the reason for this problem ...

     

    BTW, the PrintManager that is announced to work up to OS X 10.10 works nicely with OS X 10.11 too.