[sane-devel] Formulardaten
If anyone is interested, here is a translation. Peter Rossmann (via cgi-mailer) wrote: Hier mein Problem ich brauche f?r meinen Flachbett Scanner canon 5000F den Treiber f?r Linux Open Suse 10.2 Here is my problem. I need Linux OpenSuse 10.2 drivers for my flatbed Canon 5000F scanner. Der scanner wird zwar angezeigt aber gibt keinen Treiber The scanner was admittedly reported, but with no drivers. Ausserdem br?uchte ich auch die software. Besides, I would like software as well. Wie und wo kann ich das bekommen How and where can I get them (the software/drivers) ?ber eine Nachricht w?rde ich mich freuen. It would please me to get good news. Hugh
[sane-devel] [ANNOUNCE] Native Wine32 SANE available for testing
On 06/07/07, Ilia Sotnikov wrote: Also, you need to use winsock2.h header (and, of course -lws2_32 during link stage) because of Windows specific declarations (eg. WSAStartup(), the call without which any Winsock call would fail). That is: ./configure LIBS=-lws2_32, right? I cannot seem to get past compiling parts of sanei, after reducing the backends/makefile to build net and dll. I have everything that is listed in the readme.windows. I'll try starting everything again. Hugh
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: '' 2. Manufacturer (e.g. Mustek): '' 3. Model name (e.g. ScanExpress 1200UB): '' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '' 6. Product id (e.g. 0x0002): '' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): ''
[sane-devel] (no subject)
Hello, sorry for my poor english. I have a problem with a Fujitsu FI-5220C Scanner. If I scan from the adf unit, everything is OK and works fine. The scan is made and the return code in the shell is zero (0). But if i scan from the flatbed unit, the page is scanned and stored, but i get an error message and the return code in the shell is one (1). I get the same error either using the debian etch packages or using the compiled cvs-source. This is, what I see: markus at hydorn 1064 export SANE_DEBUG_FUJITSU=5 markus at hydorn 1065 /usr/local/packages/sane-cvs/bin/scanadf -L; echo; /usr/local/packages/sane-cvs/bin/scanadf --source Flatbed --mode Color -o /tmp/test-1-flatbed-000%d.pnm; echo $? [sanei_debug] Setting debug level of fujitsu to 5. [fujitsu] sane_init: fujitsu backend 1.0.49, from sane-backends 1.0.18-cvs device `fujitsu:libusb:001:011' is a FUJITSU fi-5220Cdj scanner [sanei_debug] Setting debug level of fujitsu to 5. [fujitsu] sane_init: fujitsu backend 1.0.49, from sane-backends 1.0.18-cvs Scanned document /tmp/test-1-flatbed-0001.pnm [fujitsu] sense_handler: start [fujitsu] Sense=0x5, ASC=0x26, ASCQ=00, EOM=1, ILI=0, info= [fujitsu] Illegal request: invalid field in parm list [fujitsu] Offending byte is 00 [fujitsu] sane_start: ERROR: cannot start_scan scanadf: sane_start: Invalid argument Invalid argument Scanned 1 pages 1 markus at hydorn 1066 Can anybody help me? Markus -- -- Markus Haberkorn mail : Markus_Haberkorn at genua.de Gesellschaft f?r UNIX- und tel. : +49 (89) 991950-134 Netzwerkadministration mbH fax. : +49 (89) 991950-999 Domagkstrasse 7www : http://www.genua.de D-85551 Kirchheim --
[sane-devel] (no subject)
On 7/10/07, Markus Haberkorn Markus_Haberkorn at genua.de wrote: Hello, sorry for my poor english. your english is much better than my german :) I have a problem with a Fujitsu FI-5220C Scanner. If I scan from the adf unit, everything is OK and works fine. The scan is made and the return code in the shell is zero (0). ok. But if i scan from the flatbed unit, the page is scanned and stored, but i get an error message and the return code in the shell is one (1). I get the same error either using the debian etch packages or using the compiled cvs-source. hmm, many possible reasons for this (the biggest being that i dont have a flatbed model to test with :) This is, what I see: markus at hydorn 1064 export SANE_DEBUG_FUJITSU=5 markus at hydorn 1065 /usr/local/packages/sane-cvs/bin/scanadf -L; echo; /usr/local/packages/sane-cvs/bin/scanadf --source Flatbed --mode Color -o /tmp/test-1-flatbed-000%d.pnm; echo $? [sanei_debug] Setting debug level of fujitsu to 5. [fujitsu] sane_init: fujitsu backend 1.0.49, from sane-backends 1.0.18-cvs device `fujitsu:libusb:001:011' is a FUJITSU fi-5220Cdj scanner [sanei_debug] Setting debug level of fujitsu to 5. [fujitsu] sane_init: fujitsu backend 1.0.49, from sane-backends 1.0.18-cvs Scanned document /tmp/test-1-flatbed-0001.pnm [fujitsu] sense_handler: start [fujitsu] Sense=0x5, ASC=0x26, ASCQ=00, EOM=1, ILI=0, info= [fujitsu] Illegal request: invalid field in parm list [fujitsu] Offending byte is 00 [fujitsu] sane_start: ERROR: cannot start_scan scanadf: sane_start: Invalid argument Invalid argument get a debug log at level 30 instead, and send that to me directly instead of this mailing list. also please give the name of your OS. allan -- The truth is an offense, but not a sin
[sane-devel] SANE_FRAME_JPEG support
for those that are not subscribed to sane-commit, i will forward part of a mail, and describe my recent changes... -- Forwarded message -- Modified: ChangeLog backend/fujitsu-scsi.h backend/fujitsu.c backend/fujitsu.h frontend/scanimage.c include/sane/sane.h * backend/fujitsu.[ch], backend/fujitsu-scsi.h: update to v1.0.50, add JPEG support, usb command sending and scan params cleanups * include/sane/sane.h: add SANE_FRAME_JPEG * frontend/scanimage.c: dont crash on unknown frame types + ChangeLog |7 backend/fujitsu-scsi.h | 19 backend/fujitsu.c | 1037 ++- backend/fujitsu.h | 32 + frontend/scanimage.c | 11 include/sane/sane.h|3 6 files changed, 823 insertions(+), 286 deletions(-) Diff URLs: http://alioth.debian.org/plugins/scmcvs/cvsweb.php/sane-backends/ChangeLog.diff?f=hcvsroot=saner1=1.3080r2=1.3081 http://alioth.debian.org/plugins/scmcvs/cvsweb.php/sane-backends/backend/fujitsu-scsi.h.diff?f=hcvsroot=saner1=1.19r2=1.20 http://alioth.debian.org/plugins/scmcvs/cvsweb.php/sane-backends/backend/fujitsu.c.diff?f=hcvsroot=saner1=1.61r2=1.62 http://alioth.debian.org/plugins/scmcvs/cvsweb.php/sane-backends/backend/fujitsu.h.diff?f=hcvsroot=saner1=1.31r2=1.32 http://alioth.debian.org/plugins/scmcvs/cvsweb.php/sane-backends/frontend/scanimage.c.diff?f=hcvsroot=saner1=1.43r2=1.44 http://alioth.debian.org/plugins/scmcvs/cvsweb.php/sane-backends/include/sane/sane.h.diff?f=hcvsroot=saner1=1.6r2=1.7 -- End Forwarded message -- hopefully those Urls will come thru ok. The changes to the fujitsu backend to support hardware jpeg were more extensive than i would like, but the changes to sane.h and scanimage were actually quite small. basically, sane.h just got SANE_FRAME_JPEG added to an enum. scanimage had a fixed-size array of string names for each frametype, and was using that array in two places to print informational messages. if it got a frame type that was off the end of the array, bang! so, i just added JPEG to the end of the array. then, just to be sure this would not bite the next programmer, i added a little ternary test any time we look in that array. instead of walking off the end, we print Unknown. my observations: if a backend sends a 'standard' frame type like RGB, and then sends a jpeg (or other unknown) frame, a proper tiff or pnm header and data will be written, and the additional frame will be appended, corrupting the image. if a backend sends those in reverse order, there will be no tiff/pnm header, because scanimage only sends those on the first frame of a known type. the data will consist of all the frames in order received. I would like to get some opinions about more complex scanimage modifications before i move on to scanadf. namely, should scanimage ignore these new frame-types, instead of putting them in the output? in that case, it would require another format option besides the ones we have now (tif/pnm) perhaps 'raw'? i personally would find a raw option useful for debugging the standard frame types too... comments? allan -- The truth is an offense, but not a sin
[sane-devel] SANE_FRAME_JPEG support
lines deleted On Tue, 2007-07-10 at 13:38 -0400, m. allan noah wrote: -- End Forwarded message -- hopefully those Urls will come thru ok. The changes to the fujitsu backend to support hardware jpeg were more extensive than i would like, but the changes to sane.h and scanimage were actually quite small. basically, sane.h just got SANE_FRAME_JPEG added to an enum. scanimage had a fixed-size array of string names for each frametype, and was using that array in two places to print informational messages. if it got a frame type that was off the end of the array, bang! so, i just added JPEG to the end of the array. then, just to be sure this would not bite the next programmer, i added a little ternary test any time we look in that array. instead of walking off the end, we print Unknown. my observations: if a backend sends a 'standard' frame type like RGB, and then sends a jpeg (or other unknown) frame, a proper tiff or pnm header and data will be written, and the additional frame will be appended, corrupting the image. if a backend sends those in reverse order, there will be no tiff/pnm header, because scanimage only sends those on the first frame of a known type. the data will consist of all the frames in order received. I would like to get some opinions about more complex scanimage modifications before i move on to scanadf. namely, should scanimage ignore these new frame-types, instead of putting them in the output? in that case, it would require another format option besides the ones we have now (tif/pnm) perhaps 'raw'? i personally would find a raw option useful for debugging the standard frame types too... comments? allan -- The truth is an offense, but not a sin I agree, adding a raw mode is useful for debugging. -- m.vr.gr. Gerard Klaver
