Charles Duffy wrote:
> One regression: Button detection no longer works. I can switch between
> the two drivers -- startbutton follows whether the "scan" button is
> pressed on the original driver but not the experimental one.
Looking at the logs with SANE_DEBUG_FUJITSU=255:
We have found 1 but
Hi,
> result is here:
> http://rmrmg.com/jaroslav/scanner-debug/SANE_DEBUG_SNAPSCAN_255-xsa
>ne.log
According to the log the scanner is correctly identified. The margins
of the transparency range should be set correctly.
> however, I've got strange issues. Sometimes after turning on the
> scann
kriko wrote:
> However, I can scan as root (xsane, kooka...). Is this permission
> issue? What permission should I set to scanner device and how.
There is some discussion of this in http://www.sane-project.org/README.linux
Hi!
I upgraded my kernel to 2.6.15.4 and my scanner doesn't work anymore.
However:
kriko@linux:~> sane-find-scanner
# No SCSI scanners found. If you expected something different, make sure
that
# you have loaded a SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x04b8, produc
Hi,
On 2006-02-20 12:52, sofian.t...@xuite.net wrote:
> I was trying to write the driver for linux, and I ve got problem when
> I try to make in fedora core 4 , the error message :
> ../../include/sane/sanei_backend.h: error : previous declaration of
> sane status sane_1000_init(Sane_Int*, void(*)
*This message was transferred with a trial version of CommuniGate(r) Pro*
One regression: Button detection no longer works. I can switch between
the two drivers -- startbutton follows whether the "scan" button is
pressed on the original driver but not the experimental one.
yes- i have found that 200dpi lineart is the largest letter-sized scan you
can do at fullspeed with usb 1.x. At resolutions/depths higher than that,
you end up waiting for scan data after the paper has left the scanner.
so- our app just happens to scan at 200dpi lineart :)
watch the sane list f
*This message was transferred with a trial version of CommuniGate(r) Pro*
Good news: It works! I just wasn't being patient enough earlier -- when
I turned on the debug output this morning, it became clear that the
scanner had in fact *not* locked up partway through the scan, but that
it was simp
://www.kaitimmer.de
"Information ist schnell. Wahrheit braucht Zeit."
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :
http://lists.alioth.debian.org/piper
