I have tried everything I can to get my new scanner back on line. During a scan I had to force quit on my Mac OS 10.4.2 system while using the scanner driver---- now I get an error message to stop a DiMAGE Scan software--- can't fine any running, so Uninstalled and reinstalled--- same message--- it prevents any entry to its software. Apple said its Minolta problem--- No help from two calls to Minolta. Suggestions greatly appreciated. If I can't solve, would buying Silverfast AI 6 work even though I can't open 5400 II software ? Steve Z
This may not be applicable, but I work at a newspaper and have a lot of experience with scanners - albeit on Windows machines. These scanners will work just fine for a while, then suddenly stop working. No TWAIN drivers, no software response, no nothing.
The solution? Unplug the scanner's power, and plug it back in again. This makes the OS pick it up again and everything's fine again for a while. An inelegant solution, but it works for us. Hope it's of some use to you.
Lasersoft SilverFast Ai6 I find is preferable and in some ways more reliable running my Minolta 5400 II scanner. However the kind of lock-up you described sounds like it could be due to a communication problem between your Mac and the scanner. If your scanner is connected through a hub or a secondary USB plug, you might try connecting to a USB connector directly on your system.
That's a very good point, David. A scanner draws a lot of power and would almost certainly overload even a powered hub. Like a printer, a scanner should be plugged directly into its own USB port on your computer.
Does Vuescan recognize the scanner? It's a universal driver that works with most flatbed and dedicated film scanners that supposedly pulls out more detail than the manufacturer's drivers.
I have the Dimage Scan 5400,and had similar problems.
In my case the culprits were two files - 'MFSLibinit' and 'MFSButtonCheck'
- which stayed on the system after an abnormal shutdown.
With the computer AND scanner hardware switched on,loading the software driver generates these files in the Dimage parent and the software load then fails with the message 'other dimage software in use'.
Switching the scanner off, deleting these files, re-activating the software driver, then switching the scanner on, results in a successful software startup.
I now adopt the following workflow which seems to avoid the problem :
Leave scanner turned OFF
Load Dimage software, and when error message that the system could not confirm the scanner connection appears, switch the scanner ON and proceed as normal.