Re: Linux 2.0 with Mustek ScanExpress 12000 SP

a.bolsch@ic.ac.uk
Sun, 14 Feb 1999 13:59:39 +0000 (GMT)

If this is the problem I'm thinking of I'm afraid I don't know a completely
reliable solution. That problem is due to the poor implementation of
handshaking in the scanner's firmware. If you kill *any* other application
before scanning (mind cron jobs and network activity!) and have a plenty
of RAM the problem should not appear, at least not for resolutions <=300dpi.

You might also try to add a call to mlock (locking all memory requested
by the backend) in the backend at the beginning of reader_process.
But don't forget to unlock the memory after end of scan. For details
see the man page of mlock. I didn't add that to the distributed backend
because it requires the process to run as root which is probably a very
bad idea in general. However, if all else fails ...


--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com