New Epson scanner DRIVING ME UP THE FUCKING WALL!
Posted: 2006-01-22 05:19am
Here's the situation: I buy a new Epson Perfection 3590 flatbed/film scanner for my iMac. This is replacing a HP piece of shit scanner/printer combo which unaccountably stopped working because it and the computer weren't talking to one another.
I get it out of the box. Install the drivers. Hook up the scanner to a USB four-port hub connector. Plug in the scanner. The applicaton fires up and it scans with no problem whatsoever —AT FIRST.
I leave for about sixteen hours or so. Decide to do some more scans when I return, so I fire up EpsonScan and —nothing. The scanning arm just shunts into ready position while the computer displays a "scanner warming up, please wait" dialogue box —and nothing. The control window just comes back up as if a scan had been done when nothing at all happened.
Tried switching USB connections —nothing. Tried connecting directly to the USB ports on the computer itself —nothing. Repeatedly restarted both scanner and computer —nothing. Even went so far as to completely uninstall the drivers, disconnect the scanner from both power and USB, then reinstalled the software, repeated the step-by-step connection procedure and —NOTHING. The fucking thing just sits there not talking to the computer. Every once in a while, I get an error message stating that the scanner could not be started, that there is a communication problem, and get dumped into the singularly unhelpful troubleshooting menu which typically is worse than useless for all the "information" it offers.
Brand new scanner right out of the motherfucking box and it gets itself stuck in some sort of loop barely a day into use. Epson is supposed to be a good scanner; there's no bad buzz about the Perfection 3590 from what I've read. And this is Mac, not a Windows machine, which means you don't expect to actually run into this sort of bullshit aggravation with a new piece of equipment. The only thing I've done before trying scans was to load on a CD labelmaking programme, but that shouldn't have been enough to alter the system to the point where the scanner would be rendered nonresponsive to its own drivers. Especially not on a Mac.
It can't be the USB ports or hub —everthing else works when plugged into them. Can't be the USB cable —it's brand-new with the scanner. It's definitely not a memory problem —the computer's still got plenty to burn. Can't be a software conflict, or the thing shouldn't have worked in the first place. Never had this kind of trouble with a peripheral device before. Never.
I get it out of the box. Install the drivers. Hook up the scanner to a USB four-port hub connector. Plug in the scanner. The applicaton fires up and it scans with no problem whatsoever —AT FIRST.
I leave for about sixteen hours or so. Decide to do some more scans when I return, so I fire up EpsonScan and —nothing. The scanning arm just shunts into ready position while the computer displays a "scanner warming up, please wait" dialogue box —and nothing. The control window just comes back up as if a scan had been done when nothing at all happened.
Tried switching USB connections —nothing. Tried connecting directly to the USB ports on the computer itself —nothing. Repeatedly restarted both scanner and computer —nothing. Even went so far as to completely uninstall the drivers, disconnect the scanner from both power and USB, then reinstalled the software, repeated the step-by-step connection procedure and —NOTHING. The fucking thing just sits there not talking to the computer. Every once in a while, I get an error message stating that the scanner could not be started, that there is a communication problem, and get dumped into the singularly unhelpful troubleshooting menu which typically is worse than useless for all the "information" it offers.
Brand new scanner right out of the motherfucking box and it gets itself stuck in some sort of loop barely a day into use. Epson is supposed to be a good scanner; there's no bad buzz about the Perfection 3590 from what I've read. And this is Mac, not a Windows machine, which means you don't expect to actually run into this sort of bullshit aggravation with a new piece of equipment. The only thing I've done before trying scans was to load on a CD labelmaking programme, but that shouldn't have been enough to alter the system to the point where the scanner would be rendered nonresponsive to its own drivers. Especially not on a Mac.
It can't be the USB ports or hub —everthing else works when plugged into them. Can't be the USB cable —it's brand-new with the scanner. It's definitely not a memory problem —the computer's still got plenty to burn. Can't be a software conflict, or the thing shouldn't have worked in the first place. Never had this kind of trouble with a peripheral device before. Never.