[sane-devel] Duplex ADF, purchasable models
On Sunday 17 September 2006 16:39, Alex Perry wrote: Does someone have any suggestions of SANE supported scanners ... * ?still available for purchase * ?with supported duplex ADF I am very happy with my Avision 220 - works great with SANE - scans true 40 ppm duplex - paper feed hasn't failed a single time yet - very small footprint - reasonable price Horst
[sane-devel] invalid argument
I have a Brother MFC 210C on Ubuntu Dapper which I installed using http://ubuntuforums.org/showthread.php?t=105703 . Everything was working great (both printing and scanning using xsane) but somehow the scanning has stopped working. I tried uninstalling things and reinstalling, but nothing has changed. What happens is: xsane starts fine (which indicates that the scanner is recognized OK), but when I click on Scan, I get Failed to start scanner: Invalid argument. Any ideas?
[sane-devel] invalid argument
Exactly the same problem with my Canon Lide 60, but unfortunately no solution so far. I should say that scanning never really worked 'great', there were some minor issues in the past that I could only scan a limited number of pages (most times only one) until I got 'invalid argument' but however, disconnecting an reconnecting always helped what enabled me to scan at all. For some months now, I directly get 'Invalid argument' the first time I want to scan and I can unplug and plug the usb cable as often as I like, without any effect. Help is appreciated! Pascal Tzadik Vanderhoof schrieb: I have a Brother MFC 210C on Ubuntu Dapper which I installed using http://ubuntuforums.org/showthread.php?t=105703 . Everything was working great (both printing and scanning using xsane) but somehow the scanning has stopped working. I tried uninstalling things and reinstalling, but nothing has changed. What happens is: xsane starts fine (which indicates that the scanner is recognized OK), but when I click on Scan, I get Failed to start scanner: Invalid argument. Any ideas?
[sane-devel] signal handling by libsane and backends
On Friday 15 September 2006 16:12, Ryan Reading wrote: On 9/15/06, Gerhard Jaeger gerh...@gjaeger.de wrote: On Thursday 14 September 2006 13:30, Wittawat Yamwong wrote: Hi, On Thursday 14 September 2006 09:09, Gerhard Jaeger wrote: On Tuesday 12 September 2006 04:02, Ryan Reading wrote: The sane library and/or its backends don't seem to clean up after themselves by restoring signal handlers and/or signal masks. [...] And yes, I think you are right. Grep for sigaction or signal function calls within the backend directory and you'll see, that no backend saves the old sigmasks or handlers for restoring. I think, it is OK if the backend modifies sigmasks and/or installs signal handlers in the _child_ process but doesn't restore them. On the other hand, as Ryan mentioned, it will probably cause problems if you do it in the parent process and do not take special care of old sigmasks and signal handlers. Even sanei_thread does not restore the tweaked masks/handlers. Workaround could be to get the settings before calling any sane function and to do the restore stuff on your own. This should be documented somewhere, maybe in PROBLEMS? Nope, I think it should be fixed... I digged a little deeper to sanei_thread and the only points, where we fiddle with signals is SIGPIPE and SIGUSR2 (only for __APPLE__ __MACH__) SIGPIPE will be restored SIGUSR2 not, which is IMHO not critical So the point to fix are inside the backends. If someone could provide a testcase, this could be easily fixed. Gerhard Thanks for the quick replies. (My bad on the HTML... I have no idea why I was even using hotmail). I agree that the handlers in the child process are not a big deal. The particular backend that I was using was plustek. It specifically sets a SIGCHLD handler. I think SIGALRM is affected in other backends. Anyway, I could put together a test case that exhibits the problem if needed. In what form should a test case be in to most useful? Where could I look for an example? I didn't see any code in the testsuite dir in the source tree. The plustek backend, that's what I expected ;) I'm the maintainer of this piece of code, so when returning from holiday, I'll try to fix that issue. Gerhard
[sane-devel] hp scanjet 8290
Is hp scanjet 8290 unsupported? I would like to connect it to a HP B2600 running hp-ux 11.11. - Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060918/594c6a74/attachment.htm From bert...@sikken.nl Mon Sep 18 16:26:01 2006 From: bert...@sikken.nl (Bertrik Sikken) Date: Mon Sep 18 16:26:35 2006 Subject: [sane-devel] hp scanjet 8290 In-Reply-To: 20060918135149.82670.qm...@web54007.mail.yahoo.com References: 20060918135149.82670.qm...@web54007.mail.yahoo.com Message-ID: 450ec899.3060...@sikken.nl -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tera Holler wrote: Is hp scanjet 8290 unsupported? I would like to connect it to a HP B2600 running hp-ux 11.11. I have no practical experience with this scanner, but the sane-project.org backend search engine says: http://www.sane-project.org/cgi-bin/driver.pl?manu=model=8290bus=anyv=p= Bertrik -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFDsiZETD6mlrWxPURAkW9AJ9cOXJGLSxy9wSZ7hARoKaW/+3E2ACfXdN1 FhbqS2D1KPq6z/tOEYBZusU= =pfrr -END PGP SIGNATURE-
[sane-devel] (no subject)
how do i fix this email me at msax...@hotmail.com thanks mark -- next part -- root@msa-desktop:/home/msa# make making depend in include make[1]: Entering directory `/home/msa/include' make[1]: Nothing to be done for `depend'. make[1]: Leaving directory `/home/msa/include' making depend in lib make[1]: Entering directory `/home/msa/lib' makedepend -I. -I../include *.c 2/dev/null make[1]: Leaving directory `/home/msa/lib' making depend in sanei make[1]: Entering directory `/home/msa/sanei' makedepend -I. -I../include *.c 2/dev/null make[1]: Leaving directory `/home/msa/sanei' making depend in backend make[1]: Entering directory `/home/msa/backend' makedepend -I. -I/home/msa/Desktop/sane-backends-1.0.18/backend -I../include -I/ho me/msa/Desktop/sane-backends-1.0.18/include *.c 2/dev/null makedepend -a -o.lo -I. -I/home/msa/Desktop/sane-backends-1.0.18/backend -I../incl ude -I/home/msa/Desktop/sane-backends-1.0.18/include *.c 2/dev/null make[1]: Leaving directory `/home/msa/backend' making depend in frontend make[1]: Entering directory `/home/msa/frontend' makedepend -I. -I/home/msa/Desktop/sane-backends-1.0.18/frontend -I../include -I/h ome/msa/Desktop/sane-backends-1.0.18/include -I/usr/local/include *.c 2/dev/null make[1]: Leaving directory `/home/msa/frontend' making depend in tools make[1]: Entering directory `/home/msa/tools' makedepend -I. -I/home/msa/Desktop/sane-backends-1.0.18/tools -I../include -I/home /msa/Desktop/sane-backends-1.0.18/include *.c 2/dev/null make[1]: Leaving directory `/home/msa/tools' making depend in doc make[1]: Entering directory `/home/msa/doc' make[1]: Nothing to be done for `depend'. make[1]: Leaving directory `/home/msa/doc' making depend in po make[1]: Entering directory `/home/msa/po' make[1]: Nothing to be done for `depend'. make[1]: Leaving directory `/home/msa/po' making all in include make[1]: Entering directory `/home/msa/include' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/msa/include' making all in lib make[1]: Entering directory `/home/msa/lib' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/msa/lib' making all in sanei make[1]: Entering directory `/home/msa/sanei' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/msa/sanei' making all in backend make[1]: Entering directory `/home/msa/backend' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/msa/backend' making all in frontend make[1]: Entering directory `/home/msa/frontend' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/msa/frontend' making all in tools make[1]: Entering directory `/home/msa/tools' gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I/home/msa/Desktop/sane-backends-1.0.1 8/tools -I../include -I/home/msa/Desktop/sane-backends-1.0.18/include -D_REENTRANT -I/usr/include/gphoto2 -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_S ANE_DATA_DIR=/usr/local/share -DPATH_SANE_LOCK_DIR= -DV_MAJOR=1 -DV_ MINOR=0 ../backend/umax_pp_low.c -o ../backend/umax_pp_low.o \ -DBACKEND_NAME=umax_pp_low gcc: ../backend/umax_pp_low.c: No such file or directory gcc: no input files make[1]: *** [../backend/umax_pp_low.o] Error 1 make[1]: Leaving directory `/home/msa/tools' make: *** [all-recursive] Error 1 root@msa-desktop:/home/msa#
[sane-devel] Annoying Out of MEmory Error...
Hi, I own a Acer Flatbed scanner (620 ST) which I use rarely. So I can not exactly tell you, when this error started to occur on my computer. # scanimage scanimage: sane_start: Out of memory Does anybody have an idea, what the heck is going wrong, or how to get rid of that problem? Can you provide a debug log for the scan session? I.e. run SANE_DEBUG_SNAPSCAN=255 scanimage 2debug.log and send me the log file. Another important information is the type of SCSI card you're using. /Oliver
[sane-devel] scanjet 4370
Hi, On advise of Bertrik Sikken, I installed the hp3900 backend. At that time it didn't do anything, but the (new) scanner turned out to be broken. Despite getting a new one, xsane doesn't recognize any scanner. However, sane-find-scanner DOES recognize it: found USB scanner (vendor=0x03f0 [hewlett packard], product=0x4105 [hp scanjet], chip=RTS8822L-01H) at libusb:003:006 So, what could or should be the next step to using it? (Apart from getting a real backend for productID 0x4105). Thanks, Huub
