Altering permissions of SilverFast and Lasersoft, Photoshop plug-ins folder (Import/export) to root:admin 777 does not seem to help.
there's no need for changing permissions with 6.4.x release versions of SilverFast.
We tested a couple of network distributed setups and couldn't find a problem like the one described by you.
Perform 1 scan [...] "Cannot send Command<Set Window>"
[...] will result in "Scanner not found" error. [...] turn off scanner , wait 10 seconds, turn on scanner, open Photoshop CS, continue scanning.
If a communications problem with a device occurs, and the device is thus set into an undefined status, it's always a good idea to reset that device.
(1) You can set the place of the scratch volume and folder yourself: > Options > General.
But unless your user folders are quite small, having them on a network drive won't harm.
(1)+(2) If you aren't using options that generate multiple files (such as iSRD
, multi-sampling) there won't be any scratch files created.
(2) As you described it, you are actually talking about how Photoshop handle files, not SilverFast.
(3) How? If there'd be a memory leak, memory would be slowly, but steadily become occupied. Then swapping to disk would occur. If disk is full, system will no longer function properly, and may have a communications problem with the scanner, because it can no longer allocate memory resources.
I doubt this is what you experience.
But what makes you think of a memory leak and how does it interfere with scanner communication in your opinion?
It seems I can crash SilverFast by not saving 2 files and performing or interrupting a third scan.
So you are importing two images into Photoshop and don't save them yet. Then you start another scan, but cancel it. For whatever reason, SilverFast crashes or seems to crash for you.
Please note that with certain scanners you cannot expect a scanning software to become immediately available for further commands if you'd cancel an operation like a scan. E.g. it might well be that SilverFast still waits for a change to send the cancel command to the scanner via the driver SDK, but there hadn't come an opportunity yet, because from the manner in which the SDK had been programmed it perhaps doesn't offer to send commands like such at any given point of time to the scanner.
Then the "crash" actually it just impatience. However, force-quitting the app will probably render the scanner into undefined status, as well as blocking Photoshop that's still waiting for an reaction from the plug-in software.
I mean "Cannot send Command<>" is findable in the code.
But it doesn't tell why the scanner wasn't able to execute the command given in that particular situation. I am afraid things aren't that easy as you picture them here...
- Manager Technical Support, LaserSoft Imaging AG -