[sane-devel] Canon MF8360cdn
Hello, I'm trying to scan with a Canon MF8360cdn. He is supported in the PIXMA manpage. I see that it is found, but no scanner is output afterwards. $ env SANE_DEBUG_BJNP="5" scanimage --help [sanei_debug] Setting debug level of bjnp to 5. [bjnp] sanei_bjnp_find_devices, pixma backend version: 0.17.37 [bjnp] sanei_bjnp_find_devices: No devices specified in configuration file. [bjnp] sanei_bjnp_find_devices: Added all configured scanners, now do auto detection... [bjnp] prepare_socket: lo is not a valid IPv4 interface, skipping... [bjnp] prepare_socket: enp2s0 is IPv4 capable, sending broadcast, socket = 36 [bjnp] prepare_socket: virbr0 is IPv4 capable, sending broadcast, socket = 37 [bjnp] prepare_socket: virbr1 is IPv4 capable, sending broadcast, socket = 38 [bjnp] prepare_socket: lxcbr0 is IPv4 capable, sending broadcast, socket = 39 [bjnp] sanei_bjnp_find_devices: Select returned, time left 0.499983 [bjnp] sanei_find_devices: Discover response: [bjnp] :4d 46 4e 50 82 01 00 00 00 00 00 00 00 00 00 10 [bjnp] 0010:00 01 80 00 06 04 88 87 17 0d 8a 7a 00 00 00 00 [bjnp] get_scanner_name: Forward lookup for mf8300c.bodomos.lan succeeded, using as hostname [bjnp] bjnp_allocate_device(mfnp://mf8300c.bodomos.lan:8610/timeout=1000) 0 [bjnp] get_scanner_name: Forward lookup for mf8300c.bodomos.lan succeeded, using as hostname [bjnp] setup_udp_socket: Setting up a UDP socket, dest: 192.168.178.131 port 8610 [bjnp] bjnp_get_scanner_mac_address: Discover response: [bjnp] :4d 46 4e 50 82 01 00 00 00 00 00 00 00 00 00 10 [bjnp] 0010:00 01 80 00 06 04 88 87 17 0d 8a 7a 00 00 00 00 [bjnp] bjnp_allocate_device: Scanner not yet in our list, added it: mf8300c.bodomos.lan:8610 [bjnp] get_scanner_id: Get scanner identity [bjnp] :4d 46 4e 50 02 30 00 00 00 01 00 00 00 00 00 00 [bjnp] setup_udp_socket: Setting up a UDP socket, dest: 192.168.178.131 port 8610 [bjnp] get_scanner_id: scanner identity: [bjnp] :4d 46 4e 50 82 30 00 00 00 01 00 00 00 00 00 56 [bjnp] 0010:4d 46 47 3a 43 41 4e 4f 4e 3b 43 4d 44 3a 4d 46 [bjnp] 0020:4e 50 31 2c 4d 75 6c 74 69 50 41 53 53 20 32 2e [bjnp] 0030:31 3b 4d 44 4c 3a 4d 46 38 33 30 30 43 20 53 65 [bjnp] 0040:72 69 65 73 3b 43 4c 53 3a 49 4d 47 3b 44 45 53 [bjnp] 0050:3a 43 61 6e 6f 6e 20 4d 46 38 33 30 30 43 20 53 [bjnp] 0060:65 72 69 65 73 3b [bjnp] get_scanner_id: Scanner identity string = MFG:CANON;CMD:MFNP1,MultiPASS 2.1;MDL:MF8300C Series;CLS:IMG;DES:Canon MF8300C Series; - length = 86 [bjnp] get_scanner_id: Scanner model = MF8300C Series [bjnp] add_scanner: New scanner added: mfnp://mf8300c.bodomos.lan:8610/timeout=1000, serial mf8300c, mac address: 8887170d8a7a. [bjnp] sanei_find_devices: Discover response: [bjnp] :42 4a 4e 50 02 01 00 00 00 00 00 00 00 00 00 00 [bjnp] sanei_bjnp_find_devices: Select returned, time left 0.46 [bjnp] sanei_find_devices: Discover response: [bjnp] :4d 46 4e 50 82 01 00 00 00 00 00 00 00 00 00 10 [bjnp] 0010:00 01 80 00 06 04 88 87 17 0d 8a 7a 00 00 00 00 [bjnp] get_scanner_name: Forward lookup for mf8300c.bodomos.lan succeeded, using as hostname [bjnp] bjnp_allocate_device(mfnp://mf8300c.bodomos.lan:8610/timeout=1000) 1 [bjnp] get_scanner_name: Forward lookup for mf8300c.bodomos.lan succeeded, using as hostname [bjnp] setup_udp_socket: Setting up a UDP socket, dest: 192.168.178.131 port 8610 [bjnp] bjnp_get_scanner_mac_address: Discover response: [bjnp] :4d 46 4e 50 82 01 00 00 00 00 00 00 00 00 00 10 [bjnp] 0010:00 01 80 00 06 04 88 87 17 0d 8a 7a 00 00 00 00 [bjnp] add_scanner: Scanner at mfnp://mf8300c.bodomos.lan:8610/timeout=1000 was added before, good! [bjnp] sanei_find_devices: Discover response: [bjnp] :42 4a 4e 50 02 01 00 00 00 00 00 00 00 00 00 00 [bjnp] sanei_find_devices: scanner discovery finished... scanimage: no SANE devices found Thanks Con -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Udev Absolutely Required Or Not?
Hello, Sane will not detect my usb scanners with kernels 3.5 and up due to the elimination of usbfs. IOW, libusb cannot read/write to usb scanners with the recent kernels. Udev is the method always described in the documents to get usb scanners recognized. However, I have never used udev and I would rather avoid the use of udev (or any equivalent). Is udev an *absolute* requirement for kernels 3.5+ or is there some other way to get usb scanners to function with Sane? Currently, to avoid udev, I boot into kernel-3.4.68 when I need to make scans, but I would rather not have to do this. IMHO, an absolute requirement for udev would be a poor decision for Sane. Linux, and all OSS, is about freedom of choice and I am sure that many want to choose *not* to use udev. Frank Peters
[sane-devel] Samsung CLX-318x MFP-series
Hi, the Samsung CLX-318x MFP-series is currently not supported. Can I help adding support for this device ? I'm especially interested in scanning over network. I have a CLX-3185FW (wireless + cable network support) for testing. Regards, Frank Sch?fer
[sane-devel] Samsung CLX-318x MFP-series
Hi Jon, Am 07.04.2012 15:12, schrieb Jon Chambers: Hi Frank On Saturday 07 April 2012, Frank Sch?fer wrote: the Samsung CLX-318x MFP-series is currently not supported. Can I help adding support for this device ? I'm especially interested in scanning over network. I have a CLX-3185FW (wireless + cable network support) for testing. As an initial experiment you might try this (perl) driver http://www.jon.demon.co.uk/dell1600n-net-scan/ originally written as part of the research for the SANE dell1600n_net driver. Other people subsequently submitted help/code supporting other similar protocols, including some Samsung ones. Thanks, but unfortunately it doesn't work. Even if it does not work then have a look through captured network packet data of a scan looking for strings beginning std-scan- which would suggest a similar protocol. I don't have much experience in network sniffing, but looking at the Wireshark logs it seems that ports 9400 (sec-t4net-srv) and 9401 (sec-t4net-clt) are involved. Google talks about Samsung Twain for Network ... Frank If either of above the above show promise then you might use the source of both the perl driver above and the SANE dell1600n_net plugin as a starting point. cheers, Jon
[sane-devel] New Genius CP-SF600 troubles
I had been using a Genius CP-SF600 (gt68xx) with sane without any problems. Actually, it worked very well. Recently I bought a new CP-SF600, and it's pretty clear that something is different inside of it. On the outside, it just looks like they changed the USB connector from an regular B to a mini-B connector. The USB VID/PID is the same on both versions. My hope was to figure out the difference between this version and the previous one and submit a patch back. However, I'm running into a lot of trouble and was wondering if anyone had any pointers. Here's what I know: The following is a grayscale scan that I made with the Windows driver: http://dl.dropbox.com/u/37770195/scaninwindows.png and here's what I get with sane: http://dl.dropbox.com/u/37770195/sane.png It seems like a lot of code still works in sane, since I get a recognizable image. The image looks like it was delta encoded, but that doesn't make sense to me. I'm not that familiar with scanner technology and I wonder whether any of you had seen anything like this before. The other difference that I've seen between sane and the Windows driver is that sane uses the cism216.fw firmware and the new Windows driver uses cism603.fw. I tried having sane use cism603.fw, but just received a blank white scan. I then used a USB sniffer to see what Windows was sending for the AFE parameters, but it looked like it was just sending zeros. I tried the same change on the sane side without any luck. Perhaps least encouraging was that when I used a USB sniffer to see what the raw form of the Windows scan looked like, it looked similar to the image above. My conclusion from this was that the cism216.fw firmware might be ok, but that the new scanner required different post-processing than the old one. Any pointers would be appreciated since it would be nice to get this scanner working again. Thanks, Frank -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20111017/5f2c91f8/attachment.html
[sane-devel] HP Scanjet 6300c I/O Errors with high resolution
I have a HP Scanjet6300c. sane-utils are the Version, that comes with Debian Lenny (1.0.19-23). I get an I/O error every time I use the scanimage withe the option --resolution 1200 (to be exact any resolution higher than 600). Using scanimage without option works any time and configuration Sometimes even seg Fault errors. I could replicate this indebendent from: - the hardeware (tried 4 different computers and two scanners of the same model) - with and without the dumb-read option in the hp.conf file - on SCSI and USB interface - (on a Suse 9.2 Machine) Is there any hope to have this corrected when using sane-backends 1.0.20 ? And if, can I install the back-ends only, with the frontends still old version? Could I deliver any additional information, that might help to solve the Problem? Thanks Frank
[sane-devel] support for genesys gl841 based scanners i.e. Canon Lide 80
Hi folks, i do own a Canon Lide 80 scanner. Because this model is currently unsupported (and surely all GL841 based ones) I thought about start developing by myself. But before I'll try to get started with developing (it will be my first devel-project), I have to ask what's the matter that this USB chip is still unsupported? Is it so difficult to get sane running with this chip? Or wasn't it developed, yet because of low demand? Best Regards, Frank
[sane-devel] Scanning for fax - resolution problem
Frank Millman wrote: Hi all I have got a scanner and fax modem working perfectly on Windows. I am trying to move them over to a new Fedora 10 server, using sane (scanimage version 1.0.19) and hylafax+ (version 5.2.8). I am battling with getting a suitable tiff file for faxing. Well, after all that, it turns out that there is a much easier solution. I got the necessary push from Lee Howard of Hylafax, who wrote the following - I've not met a scanner that didn't do what I needed to scan appropriately for faxing. Sometimes it took a bit to get the settings right. Make sure you're scanning at 200 dpi and monochrome. Then try adjusting the contrast and brightness settings. You'll eventually find a happy setting. According to 'scanimage -h', both brightness and contrast are configurable on my scanner. In practice, if I try to vary contrast, I get the message 'attempted to set inactive option contrast'. I don't know why. No matter, I experimented with brightness, and got very acceptable results, when combined with --mode=LineArt and --resolution=200. The resulting images are small and fax much quicker as well - about 45 seconds. I found that, depending on the clarity of the original document, different settings of brightness were required for optimum results. Unfortunately the xsane front end does not allow easy adjustment of this - it does not even display the brightness setting if you select LineArt. I may have to write my own front end, but I think the effort will be worth it in the long run. Thanks again for all the assistance. Frank
[sane-devel] Scanning for fax - resolution problem
Frank Millman wrote: Hi all I have got a scanner and fax modem working perfectly on Windows. I am trying to move them over to a new Fedora 10 server, using sane (scanimage version 1.0.19) and hylafax+ (version 5.2.8). I am battling with getting a suitable tiff file for faxing. Thanks to all for the replies. I will save some bandwidth and respond to them all here ... [allan] I dont think 'resolution' is the word you are looking for here, perhaps quality? can you describe the problem a bit more? A block of solid blue comes out as a patterned block of black and white dots. A solid line comes out as a dotted line. i think your best bet is to scan at 200 dpi (or 204 if your scanner will do it), and then pass the file thru something like convert to crop or pad it to the right width instead of scaling it. This agrees with the advice I got from the hylafax list. Unfortunately I found myself out of my depth with all the options in ImageMagick. However, I did get some other suggestions which seem promising - see below. [Giuseppe] Is your fax really able to transmit grey images? No, hylafax converts the image to monochrome first. Apparently it uses Ghostscript to do this, and this is where the loss in quality comes from. I suggest you to scan in black and white and/or to increase dpi. (Increased dpi will probably help when hylafax will convert your image to black and white.) I tried scanning in black and white (--mode=LineArt), but it gives a poor result. Most of the light-blue lines disappear altogether. Maybe a better scanner would give a higher quality, I don't know. Increasing dpi did not help, I am afraid. [Jeremy] Have you tried scanning your document using my bscan bash script? Thanks very much for this, Jeremy, it looks interesting. Unfortunately I could not get it to run - it complained about not finding 'gamma4scanimage'. As I got some promising suggestions from the hylafax list I did not pursue it, but I do appreciate your assistance. I got this suggestion from Lee Howard on hylafax - Because you're using HylaFAX+ you have certain script features available already. You can improve the dithering behaviors greatly by putting this into /var/spool/hylafax/etc/FaxModify: DITHERING=libtiff-fs I don't understand it, but it works. The downside is that it produces an output file that is more than double the size, and therefore take more than twice as long to transmit. I am following up one other possibility, but if that does not prove worthwhile, I will stick with this suggestion. I must say that there is a lot more to scanning and faxing than I had realised. I am used to using Windows, where you install the driver and it just works. Nevertheless, it is good to know that there are so many people out there willing to help. I shall persevere until I get it working properly. Many thanks to all. Frank
[sane-devel] Scanning for fax - resolution problem
Hi all I have got a scanner and fax modem working perfectly on Windows. I am trying to move them over to a new Fedora 10 server, using sane (scanimage version 1.0.19) and hylafax+ (version 5.2.8). I am battling with getting a suitable tiff file for faxing. The scanner is detected as a Plustec OpticPro U24. The test page I am trying to fax is an A4 pre-printed form, where the printing is light-blue on white, and the form is completed in handwriting. Windows has no problem in scanning and faxing this form. Initially I did this - scanimage --mode Gray --resolution 200 --format tiff -x 215 -y 297 | sendfax -n -m -d 1234567 It worked, but the fax came out on the other side with poor resolution. Then I tried writing the image to a file, using - scanimage --mode Gray --resolution 200 --format tiff -x 215 -y 297 /home/frank/test.tif The size of the file created is 3.9mb. If I then do the following - sendfax -n -m -d 1234567 /home/frank/test.tif it sends the fax ok, but with the same problem. I enquired on the hylafax list, and got the following response - My guess is that the image isn't right for direct FAX (T.30) sending, and the ghostscript middle-man is the culprit. You can see the tiff2fax command executed in syslog if you turn up faxq logging, and running it by hand (and with -x) will show you the GS running to squash the bad-sized tiff to the right-sized tiff (and then you can verify that it's the GS making the right-sized tiff look bad). I did this, and can confirm that, using the tiff file of 3.9mb as input, tiff2fax creates a tiff file with a size of 140kb, with the bad resolution. I also got the following suggestion - Another option would by to try and get SANE to scan to the right format, I think your best bet is to try and get it to match: Horizontal: RES of 204(pi), 1728 pixels wide *exactly* Vertial:RES of 196(pi), variable length (as long as your receiver accepts it, otherwise around 2150 - 2300 pixels for letter/A4 I tried scanimage with lower resolutions, but that resulted in an image with a very dark background, virtually unreadable. I tried scanimage with --mode LineArt, which worked, but the scan lost a lot of detail, so that is not a solution. I don't know what else to try. Any suggestions will be much appreciated. Thanks Frank Millman
[sane-devel] I have achieved ADF duplex scan
I have a suggestion concerning the duplex function using the SANE-Backends-1.0.19 : on my hp5590, it writes recto and verso on the same page, and they are upside down. Being on the same page, I cannot use a tool like pdtfk to rotate the part I want. The suggestion would be to write them on separate pages. Another improvement would be to have a parameter for choosing longside or shortside binding, so as to force rotation of everyother page or not. The ultimate improvement would be to ocr the pages to rotate them whenever necessary, a costly improvement that would not bring that much to the two other options. Frank
[sane-devel] Sane ADF Duplex parameters
Hello, I am using a HP5590. I just discover that sane handles it, and even better than then native hp soft, the duplex function operating correctly whereas it does not with the hp soft. This is FANTASTIC, great job. I have a question : the pages are scanned upside down with the duplex option, which means it seems to assume the pages are binded on the short side. Is there a way to set a parameter to choose long side or short side, so as to have each other page rotated if necessary ? Or, is there the option not to have the two sides of the page on the same image ? Many thanks -- Frank Billot 05?04'03 E - 43?59'06 N
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
Hello Andrej, Ralph sent me his code in April but went silent since then. I've attached what he send me, so you (or someone else) can start from there. Regards, Frank. -- next part -- A non-text attachment was scrubbed... Name: teco3.tgz Type: application/x-compressed Size: 14932 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080611/7b95f26b/attachment.bin
[sane-devel] SANE 1.1.0 Release discussion
6. Common debugging bitmask: 1 major errors 2 minor errors 4 function start/stop msgs 8 function detail msg 16 SANE_OPTION processing msgs 32 calibration msgs 64 outgoing command dump 128 incoming data dump help me fix that... Should these need to be bitmasks ? I think most backends are using levels instead.
[sane-devel] SANE 1.1.0 Release discussion
6. Common debugging bitmask: 1 major errors 2 minor errors 4 function start/stop msgs 8 function detail msg 16 SANE_OPTION processing msgs 32 calibration msgs 64 outgoing command dump 128 incoming data dump help me fix that... Should these need to be bitmasks ? I think most backends are using levels instead. Bitmasks are more complicated to use for a normal user, while a level is pretty simple.
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
m. allan noah wrote: On 4/3/08, Gerard Klaver gerard at gkall.hobby.nl wrote: On Thu, 2008-04-03 at 14:56 +0200, Ralph D. Ungermann wrote: On Wed, Mar 5, 2008 at 8:41 AM, Ralph D. Ungermann wrote: I'm about to adapt the teco3 backend to the VM6552. My question: Is there still any public interest in backends for such old scanners? m. allan noah wrote: though there may not be much interest, we will accept patches if you get it working and it compiles cleanly. we might even make you maintainer of the code if you are not careful :) My scanner now runs fine! But unfortunately, it turned out to be not a patch, but a major rewrite (with 30% less lines). I presume, that my backend also solves major issues for the other supported scanners, chiefly with color scans and responsiveness (to cancel). But I have no way to test it for other teco models, and I don't want to fool millions of happy teco3 users. If there is anybody else out there using backend teco1, teco2, or teco3, I'm willing to unify and maintain that driver. But now I sit idle, until somebody googles and finds this email... Meanwhile: Anyone here need help coding or reviewing his code? -- ralph Hello Ralph, I am the maintainer of the teco2 backend, if you have a link (or send a zip file with data to mailbox) to your backend i can have a look and add improvements to the teco2 backend. http://gkall.hobby.nl/scanner.html PS. Frank Zago is the maintainer for the teco1 and teco3 backend. -- m.vr.gr. Gerard Klaver Gerard- Sorry, I thought these backends were all unmaintained. I stand corrected. Can you say how similar the protocol is on all these machines? Is it reasonable to combine the backends? No. There is 3 backends for a reason. I could take a look at Ralph's code and make sure it's indeed different than the other scanners. In that case the best solution would be to create a teco4 backend. And since I don't have any scanner left I don't think it's a good idea to patch an existing backend besides fixing obvious bugs. Regards, Frank.
[sane-devel] How to avoid gcc warnings
jazz_johnson at verizon.net a ?crit :
On Tuesday 20 November 2007, Mattias Ellert wrote:
20 nov 2007 kl. 12.32 skrev Volker Grabsch:
On Mon, Nov 19, 2007 at 11:36:20AM -0500, m. allan noah wrote:
ok, lets start by saying that lots of other sane backends produce
warnings, and i am probably running a newer version of gcc than you,
so it's not a requirement that we remove all of them. it's just a pet
peev of mine.
1. if you put a little 'arg = arg;' line in the function, gcc will
shutup about the param.
I'd rather recommend:
(void)arg;
because this command has no action. ('arg = arg;' is an assigment)
This solution also works better for 'const' arguments.
You can also leave the parameter unnamed in the declaration:
sense_handler (int scsi_fd, u_char * result, void*)
This will also get rid of the warning.
Mattias
Leaving out the parameter name gives me an error:
In file included from hs2p.c:95:
hs2p-scsi.c: In function 'sense_handler':
hs2p-scsi.c:384: error: parameter name omitted
make[1]: *** [hs2p.lo] Error 1
make[1]: Leaving directory `/var/tmp/portage/sane-backends-1.0.18/backend'
make: *** [all-recursive] Error 1
You can use __sane_unused__ :
sane_init (SANE_Int * version_code, SANE_Auth_Callback __sane_unused__
authorize)
Or use UNUSEDARG (grep sources for that one)
Frank
[sane-devel] [Fwd: Re: Panasonic KVSS905C SCSI driver]
Hello, Julien BLACHE a ?crit : Jeff Breidenbach jeff at jab.org wrote: Hi, I've been told about a standalone driver for some Panasonic high-speed scanners, see details at the URL below: Can you make sure the SANE team is aware of this Panasonic KV-SS905C SCSI driver? Thanks. http://code.google.com/p/kvss905c/ I'm told it works well but doesn't support all the features (yet?), quality is good and reliability is good too. Maybe someone will be interested in turning that driver into a SANE backend ? I looked at the code. It's a basic scsi scanner driver. It should take a couple hours work to make a backend, starting from the existing matsushita driver. The only problem IMHO is the license, and the testing. And when I see how simple these scanners are, I don't understand Panasonic's need for an NDA. Frank.
[sane-devel] Panasonic KVSS905C SCSI driver
Julien BLACHE a ?crit : Frank Zago frank at zago.net wrote: Hi, I looked at the code. It a basic scsi scanner driver. It should take a couple hours work to make a backend, starting from the existing matsushita driver. The only problem IMHO is the license, and the testing. Apache 2.0, indeed, the license sucks big time ... If someone wants to do the work, may be he can get Google to relicense the code. But the license only covers the code, not the knowledge you can gain by reading it. Well, the code is so basic it's going to be a cut and paste. I don't know how close these scanners are from the ones supported by the matsushita backend already, so ... AFAICT, the work flow is the same. But some of the SCSI commands used are more recent, and the window format is different. That's why a new driver should be written instead of using the existing one. And when I see how simple these scanners are, I don't understand Panasonic's need for an NDA. Big companies and their NDAs ... Precious IP that anyone why a scsi analyser can reverse in less than a day. Frank.
[sane-devel] Panasonic KVSS905C SCSI driver
Julien BLACHE a ?crit : Frank Zago sane at zago.net wrote: Hi, Apache 2.0, indeed, the license sucks big time ... If someone wants to do the work, may be he can get Google to relicense the code. It's only hosted on Google Code, which provides hosting services ala sf.net, it's not written by Google :) Here's one header : // Copyright 2007 Google Inc. All Rights Reserved. // Author: agl at imperialviolet.org (Adam Langley) // // Copyright (C) 2007 Google Inc.
[sane-devel] [ANNOUNCE] New SANE backend 'hp5590' for HP ScanJet%0A%095550/5590/7650
I have downloaded alioth.debian.org/frs/download.php/1669/sane-backends-1.0.18.tar.gz, not being sure it is the backends cvs. However, having followed the installation procedure, it does not recognize the hp5590 (no SANE devices found). There is no trace of backend dedicated to the 5590, either in the gunzip produced 'sane-backends-1.0.18' directory or in the /usr/lib/sane. the /sane-backends-1.0.18/tools/edve/libsane.rules do mention the hp5590 as usb device, so it maybe means that it is embedded in something else, so that one should not expect a specific backend file ? Maybe the solution lies in this note : # To run a script when your device is plugged in, add RUN=/path/to/script # to the appropriate rule. but I would not know how to use it or if a script could be used do make the rule active. In case, I added 'usb 0x03f0 0x1705' in /etc/sane/d/hp.conf, with no effect. Yet, the scanner appears in lsubs as 'Bus 003 Device 003: ID 03f0:1705 Hewlett-Packard' and sane-find-scanner gives 'found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1705 [hp scanjet scanner]) at libusb:003:003'. It is not a matter of permission, scanimage -L gives no result under root either, even after 'chmod a+rw /proc/bus/usb/003/003'. I have suppressed a prior version of sane and reinstalled, with no success. Any clue ? Thanks Le Fri, 06 Jul 2007 19:56:10 +0200, m. allan noah kitno455 at gmail.com a ?crit: hp5590 backend has already been added to sane backends cvs, so just check that out- you dont need the diff. allan On 7/6/07, Frank Billot frank.billot at neuf.fr wrote: the bin produces a syntax error : ./sane-backends-hp5590-cvs070411.diff-0001.bin: 2: Syntax error: ) unexpected is there a gz version of sane-backends-hp5590-cvs070411.diff.gz available somewhere or is the problem not a version matter ? thanks -- Frank Billot
[sane-devel] [ANNOUNCE] New SANE backend 'hp5590' for HP ScanJet%0A%095550/5590/7650
the bin produces a syntax error : ./sane-backends-hp5590-cvs070411.diff-0001.bin: 2: Syntax error: ) unexpected is there a gz version of sane-backends-hp5590-cvs070411.diff.gz available somewhere or is the problem not a version matter ? thanks Frank Billot
[sane-devel] SANE2, time for a decision
Hello Alessandro Zummo, Hello sane developers, Some weeks ago I introduced (once again) the discussion about SANE future. Now is time to take action. The situation is that we have coders willing to implement the SANE2 standard (whatever this will be) for a bunch of backends but are missing the people required to revamp sanei, the build system and the frontends. The standard itself is not complete, but this is something that can be fixed. However, we already have lost too much time in this limbo. Not even a decade :) I would like to run a poll (suggestions for good poll web sites are accepted) asking user and devs what they think about the SANE future. The poll options will be: - Reopen development on SANE1 - Fork SANE1 - Wait SANE2 indefinitely Or evolve a fork of SANE1 into SANE2. I will gladly accept suggestions for other options as long as they are credible. i.e. Develop SANE2 will not be accepted unless it includes a list of developers that are going to make it happen. I'm sorry for being a bit rough, but time is passing by and we need to go somewhere. All it takes is a motivated person. I can provide a some of my time to help, but I cannot commit to much. I have found an e-mail I wrote a few years back, which remains so true to me: http://lists.alioth.debian.org/pipermail/sane-devel/2003-August/008482.html Frank.
[sane-devel] Umax 2000P
Hello all I am trying to get a Umax 2000p scanner to work with my Ubuntu installation. So far no luck - I keep getting an error message which seems to indicate the SANE frontend or maybe the backends were not compiled with an option. This is the error: frank@ubuntu:~$ xsane [umax_pp_low] sanei_umax_pp_InitPort cannot use direct hardware access [umax_pp_low] if not compiled with --enable-parport-directio In googling the problem it seems there are 2 ways of accessing the parallel port directly or through ppdev. However when I load that module (sudo modprobe ppdev) I am no further ahead. I also tried downloading the sources and compiling but when it came to compiling the front end it failed because it seems to think the backends have not been compiled, when in fact they have been. I am using Ubuntu Dapper and Edgy but both distributions give me the same error. Is it possible to use a Debian distros files ? Is there any other way to resolve this ? Thanks -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061230/6db005ba/attachment.pgp From m...@gmx.net Sun Dec 31 14:40:56 2006 From: m...@gmx.net (Maximilian Fabricius) Date: Sun Dec 31 14:41:04 2006 Subject: [sane-devel] Plustek Optic Slim 2420 Message-ID: 88b277e60612310540q167702fcwcd81d7322e46f...@mail.gmail.com Hi all, I have been working on trying to get the OpticSlim 2420 to work. Is disassembled the scanner (hardware) and made pictures. they may be found here http://rosa.physik.tu-berlin.de/~mxhf/OS2420/ They are fairly high resolution ~1MB per image so that you can see all details. lease excuse the German on the navigation bar. From this I learned that the scanner has a GL842 chip (not GL841). The GL842 seems to be very similar to the 841 though as a quick scan through the data sheet revealed. So far I cloned the ST24 section in genesys_gl841 and I got as far as being able to execute tstbackend -l0 without getting an error. I had to comment the Init_Devices lines 4990-4993 in genesys_gl841.c. I am somewhat stuck now. Starting scanimage results in strange noise from the scanner. Does anybody have more information? On the protocol maybe? From USB snoopy I found that there are some USB control messages which are not documented yet:0x8c 0x8e ...Any ideas? Finally Plustek agreed to provide me with infrmation if I singn their NDA (non disclosure agreement). Do you have any feeling about that? Is that standard? Do I sell my soul? Max
[sane-devel] SANE2 commitment
Alessandro Zummo wrote: On Sun, 17 Dec 2006 15:02:19 +0100 Jochen Eisinger joc...@penguin-breeder.org wrote: Hi, Alessandro Zummo wrote: I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) I'm quite surprised to hear there is a sane2 standard - at least one that we can easily start to implement. I don't think it's a good idea to start hacking something before it's clear we have a standard that will support us for the next few years. you're right. my idea is to rally up some developers and then define the standard. only then we should start hacking. however, defining the standard without the developers will not lead us to anything useful. some people has committed the time necessary to port to sane2 the first bunch of drivers. we are currently missing coders for - all of sanei/* (i'll take sanei_tcp) - the build system (configure, makefile et al) - X11 frontends I believe the right approach is to fork the existing tree and start fixing and adding functionalities to it. That way you'll keep something that works all the time, saving many headaches. As or for the sane2 standard, it's only just a piece of paper right now. Coding should determine what will stay and what will go away, not the opposite (cathedral vs bazaar). Frank.
[sane-devel] SANE2 commitment
Alessandro Zummo wrote: Hello developers, since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. I'm willing to port the epson driver to sane2, help porting the coolscan driver and handle the command line frontend. I think Giuseppe Sacco has showed interest to do coolscan bits. A friend of mine, Stefano Merlo, has committed himself to the canon driver. I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) I can port mine. Frank.
[sane-devel] SANE2 commitment
Alessandro Zummo wrote: On Sun, 17 Dec 2006 19:33:51 +0100 Frank Zago fr...@zago.net wrote: some people has committed the time necessary to port to sane2 the first bunch of drivers. we are currently missing coders for - all of sanei/* (i'll take sanei_tcp) - the build system (configure, makefile et al) - X11 frontends I believe the right approach is to fork the existing tree and start fixing and adding functionalities to it. That way you'll keep something that works all the time, saving many headaches. As or for the sane2 standard, it's only just a piece of paper right now. Coding should determine what will stay and what will go away, not the opposite (cathedral vs bazaar). so you're saying to declare current sane as stable, fork it and add features to the new tree, making it morphing into something that will be the next sane? Yes. I think sane1 can evolve into sane2 step by step so as to keep a working tree.
[sane-devel] Saving to the Last Directory?
Hi, Does a method currently exist to save the image in whatever directory I last saved an image in, instead of one set directory for all? I mean, other than starting with the directory set in Preferences and moving throughout the file system? Thanx. You say tomater, I zader matermorts. -- Coach Z, Homestarrunner.com -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061017/bb849d47/attachment.html From jkds...@gmail.com Tue Oct 17 21:57:50 2006 From: jkds...@gmail.com (JKD) Date: Tue Oct 17 21:58:13 2006 Subject: [sane-devel] HP 4370 In-Reply-To: 4534e042.4050...@macdialup.com References: 4534e042.4050...@macdialup.com Message-ID: 20061017215750.ga7...@jkdsoftware.dyndns.org El Tue, 17 de Oct de 2006, a las 06:53:06AM -0700, Dean Loros dijo: I'm still getting a black scan from the 4370--is there a more current driver? Last version of hp3900 driver (0.70 ) supports your device in resolutions lower than 1200dpi. Jonathan Bravo
[sane-devel] Descreening Utility For SANE
Hello, For any list members that are interested in making high-quality scans of halftone material from books and publications, I will now report on a free utility that may be of great use. High resolution scans (600 dpi) of material that was originally printed with the halftone process will generally preserve the annoying and distracting halftone pattern. Some scanners may offer a descreening option to ameliorate this pattern, but most do not. The SANE software also has no descreening provisions. One alternative would be to load a scanned image into the GIMP and then employ the fourier plug-in to remove the low frequency spatial components. Although this method can give excellent results, its use is cumbersome and very time consuming as each image must be processed manually. What is needed is an automatic approach. After some Internet searching, I did discover an automatic tool that will effectively eliminate the halftone pattern from high resolution scans. The source code, which is free and without restrictions, is available here: http://www.picturel.com/halftone/ In conjunction with the SANE package, this utility can produce very fine results. However, there are a few limitations. The code is relatively old (ca. 1998), and can handle only 8-bit images. Also, the utility is meant for grayscale images only. (Because of the nature of color halftoning, decomposing an image into its red, green, and blue channels, followed by descreening and recombining, will give poor results.) However, if these limitations are not that important to you, then by all means you should give this utility a try. The code compiles on 32-bit Linux. (It will compile on x86_64 but will not execute successfully. It apparently is not 64-bit clean.) Perhaps the SANE developers would like to give this code an evaluation for possible inclusion into SANE. Regards, Frank Peters Detroit, Michigan USA
[sane-devel] old Agfa DuoScan / Floating point exception
Daniel Bauer wrote: Am Sonntag, 16. April 2006 16:17 schrieb Frank Zago: ... You should then be able to do the same (failing) test again and get the same results. not exactly, the differences are: - the scanner is not detected anymore from a user prompt now (I've read about that somewhere and will search again later, I guess this is not the main problem) - as root the floating point exception doesn't appear anymore, but the sanner is found twice: . addendum: when I add the device-name: scanimage --device-name=microtek:/dev/sg0 then the floating point exception appears same as before (scanimage --device-name=snapscan:/dev/sg0 gives: scanimage: open of device snapscan:/dev/sg0 failed: Error during device I/O ) regards Daniel Before changing the code, set SANE_DEBUG_MICROTEK to 128 (type export SANE_DEBUG_MICROTEK=128 under your shell) and redo your test. That will give more information. In particular get_scan_status() doesn't seems to return the correct information, which leads to linewidth being 0. Frank.
[sane-devel] old Agfa DuoScan / Floating point exception
Daniel Bauer wrote: Am Sonntag, 16. April 2006 13:11 schrieb Frank Zago: Hello Daniel, Hi Frank thanks for looking at my problem! As indicated by the trace you provided, the crash happenned at line 4017 in microtek.c: s-max_scsi_lines = SCSI_BUFF_SIZE / (s-pixel_bpl + s-header_bpl); I now get a first idea of what all those messages mean... So this is a division by 0. Which probably means that both s-pixel_bpl and s-header_bpl are 0. Looking at the other traces, it looks like your scanner could be supported. But you'll have to recompile the microtek backend to add more traces to understand why these values are not set. Do you know how to do that ? Unfortunately not. Do you know a bit of C ? No, but I'm not afraid of it. I am willing to learn and try, but I guess I'd need quite a lot of guiding thru the necessary steps. So, if you feel up to help me, I'll be glad to take the opportunity, of course... (I have some programming skills from earlier times (COBOL) and know some script languages (php4, JavaScript), however no object oriented languages, but at least the basic understandings are given, I guess.) First you have to uninstall sane-backend. Something such as rpm -e --nodeps sane-backends should do. Then download the sane-backends from sane-project.org. Untar in a suitable place, then type the usual ./configure, make and as root make install. You should then be able to do the same (failing) test again and get the same results. After that we can move to the next stage. Frank.
[sane-devel] old Agfa DuoScan / Floating point exception
Hello Daniel, As indicated by the trace you provided, the crash happenned at line 4017 in microtek.c: s-max_scsi_lines = SCSI_BUFF_SIZE / (s-pixel_bpl + s-header_bpl); So this is a division by 0. Which probably means that both s-pixel_bpl and s-header_bpl are 0. Looking at the other traces, it looks like your scanner could be supported. But you'll have to recompile the microtek backend to add more traces to understand why these values are not set. Do you know how to do that ? Do you know a bit of C ? Regards, Frank.
[sane-devel] [patch] sane-canon: Endian inverted data when scanning 48bbp raw mode pnm, little endian architectures only
+#if defined(WORDS_BIGENDIAN)
for (p = buf; p buf + nread; p++)
{
b = *p;
*p++ = *(p + 1);
*p = b;
}
+#endif
}
Why not use htons() which should be a little more efficient?
[sane-devel] mustek_usb2 backend ready for inclusion in CVS -- please test!
Henning Meier-Geinitz wrote: Hi, On Sat, Oct 01, 2005 at 10:52:51PM +0200, s...@zago.net wrote: This code is in dire need of de-windowsification. Eg this kind of non portable code: typedef unsigned long UINT, DWORD, *LPDWORD; Unfortunately you are right. The code has been created by Mustek based on their Windows source code. I'll see what size these types really need. I'm pretty sure that unsigned int is ok for all of them. These types are 32 bits on all modern windows (including their 64 bits versions). The idea is to keep the SANE and Windows driver as close as possible to eachother to enable the Mustek people to add more scanners easier. On the other hand I already had to change a lot of stuff like their split in separate libraries. If mustek intend to provide new code drops that's going to be painful. Couldn't you keep these files insulated from the rest of Sane? There's also some global variables that should be moved somewhere else (m_bDSOpen, ...) While I also think it's better to don't use global variables for all the scanner states, changing this requires a lot more effort. Also it makes the backend again more different to the Windows driver. I'm not sure yet if that's worth the effort. Unless I'm mistaken, these variables can go into the sane handle. Frank.
[sane-devel] Lexmark X1100 backend available
Hi Fred, Good job. I have a few remarks about the the code: - option are prefixed by LXK_ (eg LXK_OPT_SCAN_SIZE). Backends usually don't use a prefix. - size_list[] doesn't have A4 and other standard formats. You can get some values at http://www.cl.cam.ac.uk/~mgk25/iso-paper.html - in sane_start(), sane_read(), and probably other, you check whether the handle is a valid one. While this is correct I think it's overkill. The frontend should be trusted. - bytes_read in sane_read() should be a long instead of ssize_t to avoid a cast. - in lexmark-x1000.c, there 6 global variables (transfer_buffer, ...). They should be per scanner instance. Same thing with at least eof, x_dpi and y_dpi in lexmark.c. - shouldnt the lexmark copyright be in lexmark-x1000.c too? - unless you intend to add more code to read_buffer_is_empty(), get rid of it. - you could replace scan-size with SANE_NAME_PAPER_SIZE which is already used by 2 other backends. I also get the following warnings when I compile (target is x86_64): lexmark-x1100.c:59:1: warning: BACKEND_NAME redefined command line:10:1: warning: this is the location of the previous definition lexmark-x1100.c: In function `x1100_read_scan_data': lexmark-x1100.c:2359: warning: unsigned int format, different type arg (arg 3) lexmark-x1100.c:2360: warning: unsigned int format, different type arg (arg 3) lexmark-x1100.c:2361: warning: cast from pointer to integer of different size lexmark-x1100.c:2395: warning: unsigned int format, different type arg (arg 3) lexmark-x1100.c:2396: warning: unsigned int format, different type arg (arg 3) lexmark-x1100.c: In function `read_buffer_bytes_available': lexmark-x1100.c:2728: warning: comparison between signed and unsigned Regards, Frank.
[sane-devel] [sane-avision] scan area on hp 7400c
Hi, I just recently bought a hp scanjet 7400c. Scanning is possible, but I always get colored colums at the left side of the document. I tried sane-backends 1.0.15 as well as 1.0.10 (the one shipped with) on SuSE linux 9.0, i586. The scanner is attached to an adaptec 2940 scsi adapter, the kernel is 2.4.21-99 If I can help debugging, please tell me how to do it. Bye, Frank
[sane-devel] good adf scanners
Jens Gulden wrote: Brad Barnett schrieb: Does anyone have any suggestions for a well supported ADF scanner, under Linux? The SANE support list doesn't specify such things in the summary, which makes it more difficult to pick a good one.. Any tales of success and words of wonder are welcome! See the thread Good office scanners with ADF support? just one week ago on this list. Some scanners in the Panasonic KV-SS serie are also well supported. I don't have any pending problems for the backend, and I know some people are using it :) These are nice and reliable scanners, and used ones can be bought for quite cheap on ebay. Frank.
[sane-devel] Canoscan 5200F
Your scanner doesn't seem to be supported. http://sane-project.org/unsupported/canon-5200f.html
[sane-devel] unpaper default parameter - empty output bug
Hi Jens, Jens Gulden wrote: Peter Fales schrieb: Now that's wierd. I was using a privately built copy of unpaper, but I just unpacked the tarball and get the same results with the prebuilt binary! I just reproduced the problem on one remote Intel machine I have access to. Try to compile without any optimization (no -Ox), this was the only way for me to get a usable executable for that machine. Does it help for you? (I am using gcc 3.3.5 on Debian.) Jens Compile unpaper with the -Wall options and fix all the warnings. It will show there's a few bug (uninitialized variables for instance). gcc -Wall -O1 -g3 unpaper.c -o unpaper -lm Once it's done, run valgrind on it and fix the bugs it finds. valgrind --tool=memcheck unpaper tst.pgm tst2.pgm Frank.
[sane-devel] [patch] fix SANE_Device
Mattias Ellert wrote: Frank Zago wrote: SO? Is anyone for or against this patch? This patch introduces SANE backend internal definitions in the public sane.h header. Backend internal definitions should be in the sanei_*.h headers. If you really want different definitions of the structs internally in the backends these should be in a sanei_*.h header not in the public header. Alas, the backends are including the public header, so that's not possible.
[sane-devel] [patch] fix SANE_Device
Frank Zago wrote:
=20
The SANE standard defines the comunication between frontend and backen=
d.
It does not define any structs that shall be internally used by the
frontend or backend.
I think the clean appoach is that the backend handles the texts intern=
al
as non const strings and only creats the SANE_Device struct to return
the data to the frontend. The SANE_Device struct is defined for the
purpose to transfer the data from the backend to the frontend as const
chars. When the backend has to use non const definitions then it is no=
t
allowed to use the SANE_Device struct so it has to use it=C2=B4s own d=
ata
types and not the one of the SANE standard.
Oliver
=20
=20
So, in that case what about the patch in attachment.
=20
I've also changed the internal definition of SANE_Option_Descriptor for=
=20
the same reason. It breaks about 5 backends, but they can all be easil=
y=20
fixed by hand by removing a few const. I'd say that the current=20
definition of SANE_Device and SANE_Option_Descriptor and created an ugl=
y=20
cascade of unnecessary casts and consts in all the backends.
=20
Frank.
=20
=20
=20
---=
-
=20
Index: include/sane/sane.h
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/sane/sane-backends/include/sane/sane.h,v
retrieving revision 1.6
diff -u -3 -p -B -b -u -r1.6 sane.h
--- include/sane/sane.h 13 Nov 2004 20:29:14 - 1.6
+++ include/sane/sane.h 14 Nov 2004 18:59:03 -
@@ -92,6 +92,16 @@ typedef enum
}
SANE_Unit;
=20
+#ifdef BACKEND_NAME
+typedef struct
+ {
+SANE_String name;/* unique device name */
+SANE_String vendor; /* device vendor string */
+SANE_String model; /* device model name */
+SANE_String type;/* device type (e.g., flatbed scanner) */
+ }
+SANE_Device;
+#else
typedef struct
{
SANE_String_Const name; /* unique device name */
@@ -100,6 +110,7 @@ typedef struct
SANE_String_Const type; /* device type (e.g., flatbed scanner) *=
/
}
SANE_Device;
+#endif
=20
#define SANE_CAP_SOFT_SELECT (1 0)
#define SANE_CAP_HARD_SELECT (1 1)
@@ -134,6 +145,28 @@ typedef struct
}
SANE_Range;
=20
+#ifdef BACKEND_NAME
+typedef struct
+ {
+SANE_String name;/* name of this option (command-line name) */
+SANE_String title; /* title of this option (single-line) */
+SANE_String desc;/* description of this option (multi-line) */
+SANE_Value_Type type;/* how are values interpreted? */
+SANE_Unit unit; /* what is the (physical) unit? */
+SANE_Int size;
+SANE_Int cap;/* capabilities */
+
+SANE_Constraint_Type constraint_type;
+union
+ {
+ SANE_String *string_list; /* NULL-terminated list */
+ SANE_Word *word_list; /* first element is list-length */
+ SANE_Range *range;
+ }
+constraint;
+ }
+SANE_Option_Descriptor;
+#else
typedef struct
{
SANE_String_Const name; /* name of this option (command-line name)=
*/
@@ -154,6 +187,7 @@ typedef struct
constraint;
}
SANE_Option_Descriptor;
+#endif
=20
typedef enum
{
SO? Is anyone for or against this patch?
[sane-devel] [patch] fix SANE_Device
This is a multi-part message in MIME format. --020906070304060802060600 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ms-smtp-04.texas.rr.com id iAEJ34J5003498 =20 The SANE standard defines the comunication between frontend and backend. It does not define any structs that shall be internally used by the frontend or backend. =20 I think the clean appoach is that the backend handles the texts interna= l as non const strings and only creats the SANE_Device struct to return the data to the frontend. The SANE_Device struct is defined for the purpose to transfer the data from the backend to the frontend as const chars. When the backend has to use non const definitions then it is not allowed to use the SANE_Device struct so it has to use it=C2=B4s own da= ta types and not the one of the SANE standard. =20 Oliver So, in that case what about the patch in attachment. I've also changed the internal definition of SANE_Option_Descriptor for t= he same=20 reason. It breaks about 5 backends, but they can all be easily fixed by= hand=20 by removing a few const. I'd say that the current definition of SANE_Devi= ce and=20 SANE_Option_Descriptor and created an ugly cascade of unnecessary casts a= nd=20 consts in all the backends. Frank. --020906070304060802060600 Content-Type: text/plain; name=sane.diff.part32 Content-Disposition: inline; filename=sane.diff.part32 Content-Transfer-Encoding: base64 SW5kZXg6IGluY2x1ZGUvc2FuZS9zYW5lLmgKPT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTogL2N2 c3Jvb3Qvc2FuZS9zYW5lLWJhY2tlbmRzL2luY2x1ZGUvc2FuZS9zYW5lLmgsdgpyZXRyaWV2 aW5nIHJldmlzaW9uIDEuNgpkaWZmIC11IC0zIC1wIC1CIC1iIC11IC1yMS42IHNhbmUuaAot LS0gaW5jbHVkZS9zYW5lL3NhbmUuaAkxMyBOb3YgMjAwNCAyMDoyOToxNCAtMDAwMAkxLjYK KysrIGluY2x1ZGUvc2FuZS9zYW5lLmgJMTQgTm92IDIwMDQgMTg6NTk6MDMgLTAwMDAKQEAg LTkyLDYgKzkyLDE2IEBAIHR5cGVkZWYgZW51bQogICB9CiBTQU5FX1VuaXQ7CiAKKyNpZmRl ZiBCQUNLRU5EX05BTUUKK3R5cGVkZWYgc3RydWN0CisgIHsKKyAgICBTQU5FX1N0cmluZyBu YW1lOwkvKiB1bmlxdWUgZGV2aWNlIG5hbWUgKi8KKyAgICBTQU5FX1N0cmluZyB2ZW5kb3I7 CS8qIGRldmljZSB2ZW5kb3Igc3RyaW5nICovCisgICAgU0FORV9TdHJpbmcgbW9kZWw7CS8q IGRldmljZSBtb2RlbCBuYW1lICovCisgICAgU0FORV9TdHJpbmcgdHlwZTsJLyogZGV2aWNl IHR5cGUgKGUuZy4sICJmbGF0YmVkIHNjYW5uZXIiKSAqLworICB9CitTQU5FX0RldmljZTsK KyNlbHNlCiB0eXBlZGVmIHN0cnVjdAogICB7CiAgICAgU0FORV9TdHJpbmdfQ29uc3QgbmFt ZTsJLyogdW5pcXVlIGRldmljZSBuYW1lICovCkBAIC0xMDAsNiArMTEwLDcgQEAgdHlwZWRl ZiBzdHJ1Y3QKICAgICBTQU5FX1N0cmluZ19Db25zdCB0eXBlOwkvKiBkZXZpY2UgdHlwZSAo ZS5nLiwgImZsYXRiZWQgc2Nhbm5lciIpICovCiAgIH0KIFNBTkVfRGV2aWNlOworI2VuZGlm CiAKICNkZWZpbmUgU0FORV9DQVBfU09GVF9TRUxFQ1QJCSgxIDw8IDApCiAjZGVmaW5lIFNB TkVfQ0FQX0hBUkRfU0VMRUNUCQkoMSA8PCAxKQpAQCAtMTM0LDYgKzE0NSwyOCBAQCB0eXBl ZGVmIHN0cnVjdAogICB9CiBTQU5FX1JhbmdlOwogCisjaWZkZWYgQkFDS0VORF9OQU1FCit0 eXBlZGVmIHN0cnVjdAorICB7CisgICAgU0FORV9TdHJpbmcgbmFtZTsJLyogbmFtZSBvZiB0 aGlzIG9wdGlvbiAoY29tbWFuZC1saW5lIG5hbWUpICovCisgICAgU0FORV9TdHJpbmcgdGl0 bGU7CS8qIHRpdGxlIG9mIHRoaXMgb3B0aW9uIChzaW5nbGUtbGluZSkgKi8KKyAgICBTQU5F X1N0cmluZyBkZXNjOwkvKiBkZXNjcmlwdGlvbiBvZiB0aGlzIG9wdGlvbiAobXVsdGktbGlu ZSkgKi8KKyAgICBTQU5FX1ZhbHVlX1R5cGUgdHlwZTsJLyogaG93IGFyZSB2YWx1ZXMgaW50 ZXJwcmV0ZWQ/ICovCisgICAgU0FORV9Vbml0IHVuaXQ7CQkvKiB3aGF0IGlzIHRoZSAocGh5 c2ljYWwpIHVuaXQ/ICovCisgICAgU0FORV9JbnQgc2l6ZTsKKyAgICBTQU5FX0ludCBjYXA7 CQkvKiBjYXBhYmlsaXRpZXMgKi8KKworICAgIFNBTkVfQ29uc3RyYWludF9UeXBlIGNvbnN0 cmFpbnRfdHlwZTsKKyAgICB1bmlvbgorICAgICAgeworCVNBTkVfU3RyaW5nICpzdHJpbmdf bGlzdDsJLyogTlVMTC10ZXJtaW5hdGVkIGxpc3QgKi8KKwlTQU5FX1dvcmQgKndvcmRfbGlz dDsJLyogZmlyc3QgZWxlbWVudCBpcyBsaXN0LWxlbmd0aCAqLworCVNBTkVfUmFuZ2UgKnJh bmdlOworICAgICAgfQorICAgIGNvbnN0cmFpbnQ7CisgIH0KK1NBTkVfT3B0aW9uX0Rlc2Ny aXB0b3I7CisjZWxzZQogdHlwZWRlZiBzdHJ1Y3QKICAgewogICAgIFNBTkVfU3RyaW5nX0Nv bnN0IG5hbWU7CS8qIG5hbWUgb2YgdGhpcyBvcHRpb24gKGNvbW1hbmQtbGluZSBuYW1lKSAq LwpAQCAtMTU0LDYgKzE4Nyw3IEBAIHR5cGVkZWYgc3RydWN0CiAgICAgY29uc3RyYWludDsK ICAgfQogU0FORV9PcHRpb25fRGVzY3JpcHRvcjsKKyNlbmRpZgogCiB0eXBlZGVmIGVudW0K ICAgewo= --020906070304060802060600--
[sane-devel] [patch] v4l fix for 64 bits platforms
This is a multi-part message in MIME format.
--010607050104040304090109
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
--010607050104040304090109
Content-Type: text/plain;
name=sane.diff.part30
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename=sane.diff.part30
--- backend/v4l.c 30 May 2004 13:48:40 - 1.16
+++ backend/v4l.c 13 Nov 2004 19:34:18 -
@@ -986,7 +986,7 @@ sane_start (SANE_Handle handle)
s-mbuf.size, s-mbuf.frames, s-mbuf.offsets[0]);
buffer =
mmap (0, s-mbuf.size, PROT_READ | PROT_WRITE, MAP_SHARED, s-fd, 0);
- if ((int) buffer == -1)
+ if (buffer == (void *)-1)
{
DBG (1, sane_start: mmap failed: %s\n, strerror (errno));
return SANE_STATUS_IO_ERROR;
--010607050104040304090109--
[sane-devel] [patch] fix SANE_Device
This is a multi-part message in MIME format.
--020303030609050904070206
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
This patch removes the const from the name strings in SANE_Device.
I didn't commit it because it might breaks stuff. However, I believe the new
definition is actually correct. On my tree, the number of warnings drop from
137
to 94. It also introduces a few more warnings, but these can be fixed too.
If no one objects, I will commit it in a few days.
Frank.
--020303030609050904070206
Content-Type: text/plain;
name=sane1.diff
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename=sane1.diff
Index: include/sane/sane.h
===
RCS file: /cvsroot/sane/sane-backends/include/sane/sane.h,v
retrieving revision 1.5
diff -u -3 -p -B -b -u -r1.5 sane.h
--- include/sane/sane.h 13 Nov 2004 19:04:44 - 1.5
+++ include/sane/sane.h 13 Nov 2004 19:21:31 -
@@ -110,10 +110,10 @@ SANE_Unit;
typedef struct
{
-SANE_String_Const name;/* unique device name */
-SANE_String_Const vendor; /* device vendor string */
-SANE_String_Const model; /* device model name */
-SANE_String_Const type;/* device type (e.g., flatbed scanner) */
+SANE_String name; /* unique device name */
+SANE_String vendor;/* device vendor string */
+SANE_String model; /* device model name */
+SANE_String type; /* device type (e.g., flatbed scanner) */
}
SANE_Device;
--020303030609050904070206--
[sane-devel] Re: [sane-commit] CVS update: sane-backends/include/sane
Wouldn't that better fit to sanei_backend.h? I think we shouldn't export such helper macros to all the frontends. Yes, of course. I'll fix that right away.
[sane-devel] [patch] fix SANE_Device
Henning Meier-Geinitz wrote: Hi, On Sat, Nov 13, 2004 at 01:28:16PM -0600, Frank Zago wrote: This patch removes the const from the name strings in SANE_Device. I didn't commit it because it might breaks stuff. Be careful. SANE-Device is part of the SANE standard, so that would need to be changed also. However, I believe the new definition is actually correct. I guess the idea was that the strings shouldn't be changed after the SANE-Device pointer is returned to the frontend. Thsi behaviour should be made clear in the doc. To me, const means something else. Since this patch makes the variable from const to non-const, I don't think it will break anything. As far as I can see the trouble results from doing things like sane.name = strdup (...) and freeing those in sane_exit(). That is correct. I think it's clear from the use of that field that the const creates more trouble than it solves.
[sane-devel] Question on SCSI Scanner in M$
Dieter Jurzitza wrote: Dear Frank, thank you for your fast reply. Here you go with a new file scan.log. What makes me wonder is the fact that sane tries to open /dev/scanner and is alway saying this interface does not exist - what is right, indeed. I tried to start scanimage with scanimage -d h0b0t5l0 but scanimage says then that this device does not exist. Hence, I do not know. The logfile has been generated exactly as recommended in the microtec2 - manpage. Maybe you can solve things ... My driver for the AHA2940 comes with M$ - and Adaptec does not offer an alternative, therefore I think this is what I can get. Many many thanks for your efforts! take care [microtek2] [readimagestatus] [microtek2] 28,00,83,00,00,00,00,00,00,00, [microtek2] sane_get_parameters: handle=0x10033558, params=0x226e50 [microtek2] sane_get_parameters: format=1, last_frame=1, lines=56 [microtek2] sane_get_parameters: depth=8, ppl=283, bpl=849 [microtek2] sane_read: handle=0x10033558, buf=0x226e70, maxlen=32768 [microtek2] reader_process: ms=0x10033558 [microtek2] reader_process: transferlength=32604, lines=38, linelength=858, real_bpl=849, srcbuf=0x10042198 [microtek2] scsi_read_image: ms=0x10033558, buffer=0x10042198 [microtek2] scsi_read_image: transferlength=32604 [microtek2] [readimagecmd] [microtek2] 28,00,00,00,00,00,00,7f,5c,00, [sanei_scsi] sanei_scsi_cmd2: DeviceIoControl() failed: 6 [microtek2] scsi_read_image: 'Error during device I/O' [microtek2] sane_read: read 0 bytes - EOF [microtek2] cleanup_scanner: ms=0x10033558, ms-sfd=460 DeviceIoControl says invalid handle. I think somehow that last read command hosed the adapter or the scanner. Do you have the possibility to recompile sane?
[sane-devel] [patch] fix SANE_Device
Oliver Rauch wrote: Am Sam, 2004-11-13 um 21.26 schrieb Frank Zago: I guess the idea was that the strings shouldn't be changed after the SANE-Device pointer is returned to the frontend. Thsi behaviour should be made clear in the doc. To me, const means something else. Since this patch makes the variable from const to non-const, I don't think it will break anything. As far as I can see the trouble results from doing things like sane.name = strdup (...) and freeing those in sane_exit(). That is correct. I think it's clear from the use of that field that the const creates more trouble than it solves. Hello Henning, hello Frank, I think the const should not be changed because of two reasons: 1) It makes sense to define it as const in the standard because the frontend should not change anything in the struct that is returned by the backend 2) It is part of the sane standard and it makes a lot of problems to change the standard definitions May be we need a second definition without the const in some cases, but the struct that is returned by the backend should contain const strings. So when it is necessary then the routine that needs any non const strings has to create its own struct definition. May be this second (non const) definition can be put in a helper file (sanei_???.h). Oliver So what about having an external definition for frontends, and one internal for backends?
[sane-devel] canon_pp does not work
HW = Dell Dimension 2400 Using FreeBSD 5.2.1, Libieee1284 0.2.8 (compiled from source) I've tried no port, ppi0, lpt0, 0x378, etc. Taken the printer off the chain, etc. tried force-nibble. nada - no click no beep no lamp, nada output from boot in messages: ep 7 08:44:10 thurston kernel: ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 1 on acpi0 Sep 7 08:44:10 thurston kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/ NIBBLE) in COMPATIBLE mode Sep 7 08:44:10 thurston kernel: ppc0: FIFO with 16/16/8 bytes threshold Sep 7 08:44:10 thurston kernel: ppbus0: Parallel port bus on ppc0 Sep 7 08:44:10 thurston kernel: lpt0: Printer on ppbus0 Sep 7 08:44:10 thurston kernel: lpt0: Interrupt-driven port Sep 7 08:44:10 thurston kernel: ppi0: Parallel I/O on ppbus0 output of scan image: [canon_pp] detect_mode: Opening port 0x378 [canon_pp] detect_mode: Claiming port. [canon_pp] detect_mode: Port supports ECP-S. [canon_pp] detect_mode: Using ECP-S Mode [canon_pp] sane_init: initialise [canon_pp] Scanner not ready (0xf). Attempting to reset... [canon_pp] Timeout: Reset 2 response 1 (0x07 in 0x1f) - Status = 0x0f [canon_pp] Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status = 0x0f [canon_pp] Timeout: Scanner wakeup reply 2 (0x03 in 0x1f) - Status = 0x0f [canon_pp] Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status = 0x0f [canon_pp] Timeout: Scanner wakeup reply 2 (0x03 in 0x1f) - Status = 0x0f [canon_pp] Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status = 0x0f [canon_pp] Timeout: Scanner wakeup reply 2 (0x03 in 0x1f) - Status = 0x0f [canon_pp] Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status = 0x0f [canon_pp] Timeout: Scanner wakeup reply 2 (0x03 in 0x1f) - Status = 0x0f [canon_pp] Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status = 0x0f [canon_pp] Timeout: Reply 2 (0x0c in 0x1f) - Status = 0x0f [canon_pp] initialise: could not wake scanner [canon_pp] sane_init: 1 initialise [canon_pp] sane_init: Couldn't contact scanner on port 0x378. Probably no scanner there?
[sane-devel] canon_pp problem - can't init scanner arg! [fdipr...@comcast.net]
On 09/04/04 18:38:14, Frank DiPrete wrote: Hello - I have sane-backends running, compiled with libieee1284 and trying to use a canon fb620p scanner without any success. FreeBSD 5.2.1 running sane-backends 1.0.12 Here's the output of scanimage in debug mode: thurston# scanimage [sanei_debug] Setting debug level of canon_pp to 100. [canon_pp] sane_init(0xbfbfe69c, 0x80491d0): Canon Parallel SANE Backend $Revision: 1.10 $ [canon_pp] sane_init: ieee1284_find_ports [canon_pp] sane_init: 0 ieee1284_find_ports [canon_pp] sane_init: 3 parallel port(s) found. [canon_pp] sane_init: port 0x278 [canon_pp] init_device [canon_pp] init_device: [configuring options] [canon_pp] init_device: configuring opt: num_options [canon_pp] init_device: configuring opt: resolution [canon_pp] init_device: configuring opt: colour mode [canon_pp] init_device: configuring opt: bit depth [canon_pp] init_device: configuring opt: tl-x [canon_pp] init_device: configuring opt: tl-y [canon_pp] init_device: configuring opt: br-x [canon_pp] init_device: configuring opt: br-y [canon_pp] init_device: configuring opt: calibrate [canon_pp] init_device: done opts [canon_pp] init_device [canon_pp] sane_init: port 0x378 [canon_pp] init_device [canon_pp] init_device: [configuring options] [canon_pp] init_device: configuring opt: num_options [canon_pp] init_device: configuring opt: resolution [canon_pp] init_device: configuring opt: colour mode [canon_pp] init_device: configuring opt: bit depth [canon_pp] init_device: configuring opt: tl-x [canon_pp] init_device: configuring opt: tl-y [canon_pp] init_device: configuring opt: br-x [canon_pp] init_device: configuring opt: br-y [canon_pp] init_device: configuring opt: calibrate [canon_pp] init_device: done opts [canon_pp] init_device [canon_pp] sane_init: port 0x3bc [canon_pp] init_device [canon_pp] init_device: [configuring options] [canon_pp] init_device: configuring opt: num_options [canon_pp] init_device: configuring opt: resolution [canon_pp] init_device: configuring opt: colour mode [canon_pp] init_device: configuring opt: bit depth [canon_pp] init_device: configuring opt: tl-x [canon_pp] init_device: configuring opt: tl-y [canon_pp] init_device: configuring opt: br-x [canon_pp] init_device: configuring opt: br-y [canon_pp] init_device: configuring opt: calibrate [canon_pp] init_device: done opts [canon_pp] init_device [canon_pp] sane_init: # Define which port to use if one isn't specified - you should only have [canon_pp] sane_init: # one of these lines! [canon_pp] sane_init: # This is the default port to be used - others will be detected [canon_pp] sane_init: ieee1284 lpt0 [canon_pp] sane_init: Successfully parsed default scanner. [canon_pp] sane_init: [canon_pp] sane_init: [canon_pp] sane_init: # Define the location of our pixel weight file, can begin with ~/ if needed. [canon_pp] sane_init: # You can have as many of these as you like - lines with ports that don't exist [canon_pp] sane_init: [canon_pp] sane_init: # will be ignored. [canon_pp] sane_init: # [canon_pp] sane_init: # Parameters are: [canon_pp] sane_init: # calibrate /path/to/calibration-file port-name [canon_pp] sane_init: # [canon_pp] sane_init: # The format of port-name is dependant on your OS version. [canon_pp] sane_init: # [canon_pp] sane_init: # If a file isn't speficied, the default name will be [canon_pp] sane_init: # ~/.sane/canon_pp-calibration-[port-name] [canon_pp] sane_init: [canon_pp] sane_init: calibrate ~/.sane/canon_pp-calibration-pp0 lpt0 [canon_pp] sane_init: calibrate line, calibrate ~/.sane/canon_pp- calibration-pp0 lpt0 [canon_pp] sane_init: calibrate line is for unknown port! [canon_pp] sane_init: [canon_pp] sane_init: # calibrate /etc/sane/my_calibration parport1 [canon_pp] sane_init: [canon_pp] sane_init: [canon_pp] sane_init: # Enable the next line if you're having trouble with ECP mode such as I/O [canon_pp] sane_init: # errors. Nibble mode is slower, but more reliable. [canon_pp] sane_init: [canon_pp] sane_init: force_nibble [canon_pp] sane_init: force_nibble requested. [canon_pp] sane_init: [canon_pp] sane_init: # Set a default initialisation mode for each port. Valid modes are: [canon_pp] sane_init: # AUTO (attempts to automatically detect by trying both methods) [canon_pp] sane_init: # FB620P (10101010 style.. also works for FB320P) [canon_pp] sane_init: # FB630P (11001100 style.. also works for FB330P, N340P, N640P) [canon_pp] sane_init: [canon_pp] sane_init: #init_mode AUTO parport0 [canon_pp] sane_init: init_mode FB620P lpt0 [canon_pp] sane_init: init_mode line is for unknown port! [canon_pp] sane_init: # init_mode FB630P parport0 [canon_pp] detect_mode: Opening port 0x3bc [canon_pp] detect_mode: Claiming port. [canon_pp] detect_mode: Port supports ECP-S. [canon_pp] detect_mode: Using ECP-S Mode [canon_pp] detect_mode: Nibble mode force in effect. [canon_pp] sane_init: initialise [canon_pp] Scanner not ready (0xf). Attempting to reset
[sane-devel] Need help with reverse engineering Microtek Scanmaker 5600
Personnaly, I prefer sniff-usb (http://benoit.papillault.free.fr/usbsnoop/). IMO USBSnoopy Pro is a pita to use.
[sane-devel] FW: Other new info
Henning Meier-Geinitz wrote: Hi, On Fri, Jul 23, 2004 at 12:56:29AM -0500, Frank Zago wrote: Your scanner uses isochronous pipes to communicate. libusb does not yet support isochronous transfers. Are you sure? I may be wrong but I think the iso endpoints in his logs are from a completely different device. Bye, Henning Yes, you're right. I looked at the first email, and it didn't contain the scanner, so I assumed the one with iso pipes was the scanner. Looking more closely at the second shows the scaner is there. Unfortunately that doesn't change the fact that the chipset is not recognized :( Frank.
[sane-devel] FW: Other new info
Hi, Humm... I made some proofs ... I found several differences between my sane-find-scanner -v -v executed in root or by my usual user As you can see in the 2 outputs I have pasted you forward, when i execute the command from my user the output gives an ipotethic chip for the device, with no name of manufacturer or peripheral, instead, if I do the command from root, he gives me the names of the different peripherals, canon canoscan included, but he doesn't tell me anything 'bout the chip. Another try I did was to look into my hardware browser, installed in X, and I found something else. It puts between the system peripherals a peripheral which it calls canon Canoscan, with an unknown tag at the driver voice. canon Canoscan is reported by the device itself, as most usb devices do. a cat /proc/bus/usb/devices will show you the same info. Same for driver. Your scanner uses isochronous pipes to communicate. libusb does not yet support isochronous transfers. The old kernel driver didn't either (AFAIK). Conclusion: there is no driver yet for your scanner. Now if you're really brave, there is a patch for libusb floating around to support isochronous pipes. You can start a project to support your scanner. A few people have done that, so it's possible. Henning has written a few web pages on that subject. Sorry. Frank.
[sane-devel] [Canoscan5000f] news.
Then, after, i think, some updates of the system (including SANE ?) I got something else...a GL660 Chip is maybe present. (See attached file found_thibault.txt) The other genesys chipsets don't use isochronous endpoints. So I doubt your scanner is based any gl chipset.. Frank.
[sane-devel] Plustek OpticPro 12000T not recognized by SANE (plustek_pp backend)
Hi there, After discussing on the Sane-IRC-Channel and trying everything out, I was sent to this mailing list with my problem: My Plustek OpticPro 12000T (parallel port) scanner is not recognized by scanimage (not even running as root), although it is supposed to be supported by the plustek_pp backend. As far as I can tell, all configuration settings are set correct. Here is a link, where you can find all configuration and some diagnostic data: http://www.nomorepasting.com/paste.php?pasteID=16398 If you want me to post this data directly to this list, just tell me. Just thought, this is more efficient than sending it to all people. If you need any more info, I am happy to supply it. Thanks for any help on getting this scanner working, Frank
[sane-devel] Chinon DS-3000
I have a working linux interface program and propose to make a sane backend for this scanner. Do you have the source? Is is a scsi or parallel scanner? Frank.
[sane-devel] hp3670
Mickael Profeta wrote: Hi I did not give news since a long time, sorry but I had others things to do... (find a job...) I try the genesys backend for this scanner, I attach the modifications to make it recognise and the output of scanimage with debug, if it can help... And YES! the motor moves, ok just 1 cm, but it is the first step ;) I put some logs of sane-find-scanner and scanimage here: http://www.alezan.org/hp3670/ scanimage.3670.gz and sane-find-scanner.3670.gz Cheers Mike Applied. Frank.
[sane-devel] Umax Astra 4000U
Henning Meier-Geinitz wrote: Hi, Please reply to the list and not only to me. May be someone with admin right could fix the reply-to: field of this mailing list? Frank.
[sane-devel] Re: Need simple help from Windows Users for xsane-win32
Subject: [sane-devel] Need simple help from Windows Users for xsane-win32 From: Oliver Rauch oliver.ra...@rauch-domain.de Date: 17 May 2004 00:49:32 +0200 To: sane-devel sane-devel@lists.alioth.debian.org Open the command line (Start-execute, enter: command.com) and enter the command set in the command line. Then you get a list of environment variables. My WinMe setup C:\set COMSPEC=C:\WINDOWS\COMMAND.COM PROMPT=$p$g TEMP=C:\WINDOWS\TEMP TMP=C:\WINDOWS\TEMP PATH=C:\WINDOWS\SYSTEM;C:\;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\Program Files\Mts winbootdir=C:\WINDOWS windir=C:\WINDOWS BLASTER=A220 I5 D1 T4 P330 CMDLINE=doskey /insert Please check if the following environment variables are defined and if then please tell me how they are defined: USERPROFILE SYSTEMROOT TMP TEMP PROGRAMFILES APPDATA Oliver -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- Regards Frank fr...@snapafun.co.nz Whether big or small, any challenge requires the same commitment. -- Outgoing mail is certified Virus Free. Checked by AVG Anti-Virus (http://www.grisoft.com). Version: 7.0.240 / Virus Database: 262.10.1 - Release Date: 16/05/2004
[sane-devel] sane-sp15c and Fujitsu 620c: Help needed for plumbing backend to frontend
Garrick Sitongia wrote: The brightness and contrast levels are presently not supported by the=20 sp15c backend. These are presently hardcoded at 128. But I was able to=20 get it working in the hardware by adding scanf statements in sp15c.c.= =20 Scanimage stops and I can enter numbers for brightness and contrast eac= h=20 time I run scanimage. =20 scanf(%d, c);/* my code */ =3D c; dev-threshold =3D 128; scanf(%d, c);/* my code */ dev-contrast =3D c; =20 How instead do I pass these numbers to the backend from scanimage? Wher= e=20 scanimage would get them the usual way from command line args? =20 Garrick =20 _ FREE pop-up blocking with the new MSN Toolbar =96 get it now!=20 http://toolbar.msn.com/go/onm00200415ave/direct/01/ =20 =20 It seems that the backend has these options, but they are de-activated al= most=20 all the time. In sane_control_option(), see all the lines like scanner-opt[OPT_BRIGHTNESS].cap =3D SANE_CAP_INACTIVE; This tells the frontend not to offer the option. You can change some to scanner-opt[OPT_BRIGHTNESS].cap =3D ~SANE_CAP_INACTIVE; to activate them. Then, if the option is active, use the value with dev-brightness =3D scanner-val[OPT_BRIGHTNESS].w; Hope that helps, Frank.
[sane-devel] sane-sp15c and Fujitsu 620c ADF double-page feed
Garrick Sitongia wrote: When I put many docs in the ADF, sane will scan the 1st, eject it, then it will feed the next straight through without scanning it, scan the 3rd, feed the 4th through, scan the 5th, etc. How do we get it to stop scanning only every other document? I have done this: export SANE_DEBUG_SP15C=25 then scanimage --mode 8-bit --format=tiff --resolution 240 --y-resolution 240 --source ADF --batch -y 270 It seems to eject the odd pages when doing a sp15c_object_discharge. May be this particular scanner is doing it by itself. A shot in the dark: in sp15c_free_scanner(), remove the following lines: ret = sp15c_object_discharge (s); if (ret) return ret; recompile sane and try again. (I know nothing about that scanner, and I'm not the maintainer of that backend). Frank.
[sane-devel] hp2300c
Sanjay Chigurupati wrote: Does that mean HP 2400c and HP 2300c are supported by the latest cvs version of Sane? NO. sane-find-scanner might be able to tell whether this scanner is based on a gl646. There is no backend for that scanner. Frank.
[sane-devel] Question on Genesys backend
Sanjay Chigurupati wrote: Hi, Please correct me if I am wrong. This is my understanding: 1) genesys.conf defines the vendor id and , (usb address ?) Yes. 2) genesys_low.c is the low level implementation for the scanner with genesys_low.c being the header file for it Yes. 3) genesys.c is the high level implementation for the scanner with genesys.h being the header for it. Yes. But this backend doesn't do much (see Henning's page for details). It cannot even do a full scan at any resolution. Frank.
[sane-devel] hp2300c
Sanjay Chigurupati wrote: Does that mean the Genesys backend is incomplete? Well ... yes. But at least it's started. Frank.
[sane-devel] Segmentation Fault Encountered when Using FrontEnds with my Backend
I am trying to develop an all-in-one driver for a Lexmark X5150 AIO machine. The folks from Lexmark hasn't developed a SANE backend for any of their scanner yet that is why I am working on it. Setting debug level to 128 still has the output of segmentation fault. The technique I use to develop new backends is to use scanimage, linked staticly only with my backend, and everything compiled with -g3. It doesn't take long to compile/link; I don't have to install anything and I know it's using the correct code. And if it crashes, I get a nice core I can analyze with gdb. Frank.
[sane-devel] hp2300c
So can sane-find-scanner really talkt to the scanner after that change? Can I see the output of sane-find-scanner -v -v after the change, please? Bye, Henning Yes, it can. Looking at the usb traces, it looks like it is very close, if not identical, to a gl646. The registers used are the same, and the method to access them is very similar to that of the gl640. It seems there is at least 3 hp usb scanners (3670, 3690, 2400) that have a close chip. I'm only sure about the 3670 since that's the only one I found usb traces. Is it possible you set up a cvs tree for backends development (not specific to a particular backend) and a mailing list for people interrested in the GL scanner-on-chip dev? I don't want to use SF, and it would be better on alioth anyway. If you don't mind, I'd also like to see what code you have written for the gl646. Frank. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Invalid argument) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Invalid argument) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try modprobe sg. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed
[sane-devel] On the 2300C chipset
Jason Anderson wrote: From what I have seen over the past few days, we may have actually found out which chipset the 2300C actually is. However, if it is the GL, what now? Is there code to access the chipset and to actually make the scanner respond? Well, sort of. I've started a backend for it: http://www.zago.net/sane/gl646/gl646.c http://www.zago.net/sane/gl646/gl646.h It does a couple checks and initializes the scanner. I expect to fill the blanks by looking at the doc and the logs. Right now, it looks like the driver gives the scan parameters by writing to the scanner DRAM. The format still looks like a pile of junk data, but eventually we'll get there. If you're interrested, hp2300_scanner_init() correspond to the urbs 5 to 24 when one plugs the scanner. Frank.
[sane-devel] windows port of sane
Henning Meier-Geinitz wrote: +sane-backends will not compile out of the box. You need to follow the following steps: + +- edit configure.in and put all the AC_CONFIG_FILES entry in one line. Would it help to use AC_CONFIG_FILES three times? I don't know. + edit acinclude.m4 and remove everything from libtool (about 170kb) That's because the libtool that comes with cygwin is newer (or just different)? I don't know either. I had a lot of trouble with that file and everything started working once I removed it. They seem to be from the same version of libtool though. +- edit backend/Makefile.in, and add -no-undefined before the -version-info parameter (twice). What about checking for windows in configure.in and setting the variable @NO_UNDEFINED@ based on that check and calling libtool with that variable in the Makefile? I was thinking about adding a @LIBTOOL_EXTRA_FLAGS@ field for that. --- sane-backends-1.0.12.org/backend/Makefile.in2003-05-13 04:39:50.0 -0500 +++ sane-backends-1.0.12/backend/Makefile.in2003-09-21 21:19:38.0 -0500 @@ -155,7 +155,7 @@ libsane-%.la: %.lo %-s.lo $(EXTRA) $(LIBOBJS) @$(LIBTOOL) $(MLINK) $(CC) -export-dynamic -o $@ $($*_LIBS) \ - $(LDFLAGS) $(BACKENDLIBS) $^ -rpath $(libsanedir) \ + $(LDFLAGS) $(BACKENDLIBS) $^ -rpath $(libsanedir) -no-undefined \ -version-info $(V_MAJOR):$(V_REV):$(V_MINOR) $(DYNAMIC_FLAG) Can -no-undefined be harmful on other platforms? I've read the docs but it looks like I don't really understand what it does :-/ Neither do I. It just doesn't work with it :) Otherwise I haven't found anything that may harm non-Windows system so it's ok for me. I haven't applied the patch, however. Could you add some lines to to README.windows about only SCSI supported? README and Makefile.in must be updated, too. Why Makefile.in? Frank.
[sane-devel] HP PSC 1210
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo list, I have a big problem with my new device hp psc 1210 - this is a 3-in-1-device (printer, scanner and can make copies ;)) My problem is the scanner - printer works fine. I've read the manual and see that I must use HPOJ (in the CVS version). I have done so, but it doesn't work. I don't know what to do now, please help me. My configuration: - OS: Debian GNU/Linux [Woody 3.0r1] - SANE: sane_1.0.11-2_i386.deb - libUSB: libusb-0.1-4_0.1.7-2_i386.deb - Kernel: 2.4.20 - HPOJ 0.9 - hp-backend: 1.01 *So* now my configs file looks like: # cat nano /usr/local/etc/sane.d/hp.conf usb HP option dumb-read /dev/usb/scanner option connect-device /dev/usbscanner option connect-device # cat /usr/local/etc/sane.d/dll.conf hp hpoj ... # sane-find-scanner found USB scanner (UNKNOWN vendor and product) at device dev/usb/scanner found USB scanner (UNKNOWN vendor and product) at device /dev/usbscanner found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x2f11 [psc 1200 series]) at libusb:001:002 # scanimage -d hp:/dev/usbscanner scanimage: open of device hp:/dev/usbscanner failed: Error during device I/O So what should I do? Any idea? Greetings Sebastian Wieseler -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/P1s+4z2wBHhPV9sRArJmAJoDTB3jk0CASt9Op6mjOlGvP8c4FACeJfnM T2Qn1Xc/JKTUPM/QM9NcSjY= =iCqZ -END PGP SIGNATURE-
[sane-devel] Xsane go.... -no go.... Bugger!
On Sun, 03 Aug 2003 9:59 pm, Henning Meier-Geinitz wrote: Hi, On Mon, Aug 04, 2003 at 05:01:54PM +1200, Frank wrote: The system 'hung' when I attempted to access the memory stick but continued on its way when I switched off the 'Self' mode. Very strange. scanimage -L. device `v4l:/dev/video0' is a Noname STV0680 virtual device That's your camera. If you don't want to use it with SANE, you can disable it by commenting out v4l in /etc/sane.d/dll.conf. OK. Tried that and got back to 'no devices found' NB. when xsane was running [and previewing me through my PocketCam] I went to preferences and selected 'Load devices'. Do you mean load device settings? That only loads the option values you used last time with your scanner. It doesn't change which device you are using. The pop up dialogue says no devices available but this time I had followed your advice as below before attempting to issue $Xsane. There it saw my scanner but the resultant action when I selected it had me back out. You saw the settings for your scanner. That doesn't help. Er. wait till you see below. gulp! Your problem is that SANE, or better, the snapscan backend does not find your device. Still see below double gulp! Aug 4 00:24:54 localhost kernel: scanner.c: open_scanner(0): Scanner device is already open That means when you run scanimage -L another program had already opened the scanner. YOu can't open it twice at the same time. Maybe there was xsane or another fronetend running? Maybe it crashed but is still blocking /dev/usb/scanner0 for some reason? Check ps -ax. Er nothing obvious to me here. What ought I be looking for? You can use lsof /dev/usb/scanner0 to find out if some program has already opened the scanner. At this point I got on with following your advice and the following is the results: [root@localhost root]# lsof /dev/usb/scanner0 [root@localhost root]# rmmod scanner [root@localhost root]# scanimage -L device `snapscan:libusb:001:003' is a Acer FlatbedScanner13 flatbed scanner This is exactly as printed in the text console. Also after this I see that the desktop icon has gone. SANE_DEBUG_SNAPSCAN=255 scanimage -d snapscan /tmp/image.pnm 2log I couldn't get any results from this issue so dropped the /tmp... etc part and got: The 2log means write the debug messages to the file named 'log' in the current directory. Which for me may mean that there was no output hence no find? # SANE_DEBUG_SNAPSCAN=255 scanimage -d snapscan [sanei_debug] Setting debug level of snapscan to 255. [snapscan] sane_snapscan_init [snapscan] sane_snapscan_init: Snapscan backend version 1.4.22 [snapscan] add_usb_device(libusb:001:003) [snapscan] add_usb_device: Detected (kind of) an USB device [snapscan] snapscani_usb_open(libusb:001:003) [snapscan] add_usb_device: error opening device libusb:001:003: Device busy That's basically the same message as in the kernel log file. Try (as root) rmmod scanner to unload the kernel scanner driver. Then try (also as root) if scanimage -L finds your scanner now. You can see the results above. It seems that my scanner is being seen? Got that and it fits with my NB above. I just wonder if there is a means within Xsane to actually select the preferred device? That's not the real proble. If the snapscan backend found the scanner, xsane would show it to you. Can I see your snapscan.conf (in /etc/sane.d/), please? How can I refuse such a polite request? Does this mean I'm about to be dressed military style? Sorry, it's past midnight here so I'm taking things lightly. Hope the following doesn't blow my file size budget. #-- General --- # Change to the fully qualified filename of your firmware file, if # firmware upload is needed by the scanner firmware /path/to/your/firmware/file.bin # If not automatically found you may manually specify a device name. # For USB scanners also specify bus=usb, e.g. # /dev/usb/scanner0 bus=usb # For SCSI scanners specify the generic device, e.g. /dev/sg0 on Linux. # /dev/sg0 #--- # No changes should be necessary below this line #--- #-- SCSI scanners -- # These SCSI devices will be probed automatically scsi AGFA * Scanner scsi COLOR * Scanner scsi Color * Scanner scsi ACERPERI * Scanner #--- USB scanners --- # These USB devices will be probed automatically # (This will currently work only on Linux) # Benq/Acer/Vuego 310U usb 0x04a5 0x1a20 # Benq/Acer/Vuego 320U usb 0x04a5 0x2022 # Benq/Acer/Vuego 620U / 620UT usb 0x04a5 0x1a2a usb 0x04a5 0x2040 # Benq/Acer/Vuego 640U usb 0x04a5 0x2060 # Benq/Acer/Vuego 640BU usb
[sane-devel] Xsane go.... -no go.... Bugger!
Thank you for your prompt reply. To date, the following: On Sat, 02 Aug 2003 8:29 pm, Henning Meier-Geinitz wrote: Hi, On Sun, Aug 03, 2003 at 06:20:20PM +1200, Frank wrote: Then I went and replaced my second USB2 connected camera with a USB2 hub. I noticed almost immediately that Linux-Mandrake did not prefer to have the Self power enabled and worked better without that feature running. I did not change the (First) USB2 connector and left the scanner connected to it directly. Which kernel version do you use? What do you mean by Linux prefers non-self power mode? Error messages? Kernel version : 2.4.21 I believe, forgotten syntax to see. Self mode refers to the hub using it's own power source. ie. It is plugged into the wall socket directly for it's power and not reliant on my 'box' supplying it with it's power. [Either option is available with this device.] So you have no problems if you unplug the hub? That's most probably a problem in the Linux kernel drivers (or the hardware). No. The problems only started and now continue since I brought and fitted the hub. [NB. The peripherals fitted to the hub work fine. ( Camera, video port, memory stick.) ] Remember that the USB2 connection for the scanner has NOT been altered. There are two such ports in my box and the one I allocated for the scanner remains unchanged. I don't know the details about your specific scanner, but here are some general tips for USB trouble: Disable apic and acpi in the kernel. Both seem to cause USB trouble in some configurations. I think there are boo-time options, check google for noapic. Hmmm. Not sure here. The scanner worked fine until this addition and now... even though the connections to my box remain the same for the scanner. 1. The scanner light stays on all the time, even after a Halt and That's probably because SANE hasn't detected it and so can't turn off the lamp or set a timer to turn it off. What you see now, is the standard behaviour of the scanner if no driver is loaded. 2. Xsane [and other programs, eg. OOo1.1rc] can no longer access the scanner. Failed to open device 'snapscan:/dev/usb/scanner0'. Invalid argument. Any error messages in syslog (/var/log/messages)? The scanner is listed by scanimage -L correctly? scanimage -L. device `v4l:/dev/video0' is a Noname STV0680 virtual device /var/log/messages: [When attempting to use Xsane] Aug 4 00:24:54 localhost kernel: scanner.c: open_scanner(0): Scanner device is already open Aug 4 00:24:54 localhost kernel: stv680.c: [stv_init:381] STV(i): CIF is supported Aug 4 00:24:54 localhost kernel: stv680.c: [stv_init:399] STV(i): Camera has 0 pictures. Aug 4 00:24:54 localhost kernel: stv680.c: [stv_init:426] STV(i): Video Mode set to CIF Aug 4 00:24:54 localhost kernel: scanner.c: open_scanner(0): Scanner device is already open Aug 4 00:24:56 localhost last message repeated 13 times Aug 4 00:24:56 localhost kernel: stv680.c: [stv_init:381] STV(i): CIF is supported Aug 4 00:24:56 localhost kernel: stv680.c: [stv_init:399] STV(i): Camera has 0 pictures. Aug 4 00:24:56 localhost kernel: stv680.c: [stv_init:426] STV(i): Video Mode set to CIF Try SANE_DEBUG_SNAPSCAN=255 scanimage /tmp/image.pnm 2log One very blank file? Size 0. and send us the file log. It should contain debugging messages. I do not believe that there is anything wrong with sane, it's just that I needed to start somewhere relative to my problems. I attempted to reset the preferences for xsane thinking that the base settings had been changed with the new hub connection and reboot with the new hub. I get, and am leaving undone till later, the following response; File /home/frank/.sane/Acer.FlatbedScanner13.drc has been created for device Acer.FlatbedScanner13, you want to use it for device Noname:STV0680 , this may cause problems! Now this newbie is feeling a little humbled so any suggestions most welcome. -- Frank Big or small, any challenge requires the same commitment to resolve.
[sane-devel] Xsane go.... -no go.... Bugger!
Having followed the mailing list here to gain insight and knowledge to help me get my scanner sailing, [ Both within Mandrake 9.0 and now 9.1 ], I now find I need to seek your help with my Acer (Benq) 640U scanner and hope that this is the place for my particular problem. I have installed Mandrake9.1 three times so far [ Partitioning experiments ] and each time my scanner is [ and still is ] recognized. Then I went and replaced my second USB2 connected camera with a USB2 hub. I noticed almost immediately that Linux-Mandrake did not prefer to have the Self power enabled and worked better without that feature running. I did not change the (First) USB2 connector and left the scanner connected to it directly. However I now have two problems. 1. The scanner light stays on all the time, even after a Halt and 2. Xsane [and other programs, eg. OOo1.1rc] can no longer access the scanner. Failed to open device 'snapscan:/dev/usb/scanner0'. Invalid argument. Yes, things worked great before, even surviving my many re-installs. As above, I hope this is the right place and regardless, any suggestions are welcome. (Be as childlike as you care to, I do not mind, everything helps me learn.) Regards -- Frank Big or small, any challenge requires the same commitment to resolve.
[sane-devel] SANE2 (was Re: Scanning negatives with Epson Perferction 1260 Photo)
Jonathan Buzzard wrote: henn...@meier-geinitz.de said: [SNIP] I've asked multiple times for concrete proposals how the standard can be changed or appended. Each time there hasn't been any response. With concrete proposals I mean patches to SANE2 or at least the text of the to-be-added well-known options. If I remember correctly, we came to the conclusion that most proposed features can be done by adding well-known options (like multi-pass, selection of a specific range of images, auto/manual focus) and providing the functionality in the backend. So please send proposals. I did sit down and make a long list of things that I thought where missing from the SANE API for negative scanning and posted it to this list. I am not sufficiently familiar with the SANE API to be qualified to make good proposals on how it should be extended, and it would take significant amounts of my time that I don't have to do so. It seems to me a far superior solution for those that know what is missing from the standard to point out what is missing and for those that have intimate knowledge of the standard to add those features in the way that best fits in with the standard. It seems to me that if nothing happens on the SANE2 front (eg development), SANE2 will stay a mirage. A well documented illusion. A lot of people have given some input, but if the proposal isn't implemented, why care? Bigger projects like the linux kernel are changing everyday. Code gets in, code gets throwned out, the APIs change and break, but at the end of the day, there is something. The SANE2 framework is enough to get started. Frank. (this was not a rant, just a observation).
[sane-devel] SANE2 (was Re: Scanning negatives with Epson Perferction 1260 Photo)
Major A wrote: It seems to me that if nothing happens on the SANE2 front (eg development), SANE2 will stay a mirage. A well documented illusion. A lot of people have given some input, but if the proposal isn't implemented, why care? Good point, Frank. The bad thing is that SANE1 and SANE2 are mostly incompatible, so it's currently quite difficult to write a SANE2 frontend because there no suitable backends, and vice versa. scanimage can be used as the reference frontend. It's only 2000 lines, so it's easy to adapt. It just occurred to me that we could make a shortcut: create a metabackend that converts from SANE1 to SANE2, and one for the other way round. All that would be needed is an appropriate directory structure in CVS, and we could have SANE1 and SANE2 running concurrently. A converter from sane1 to sane2 might be good for unmaintained backends. A converter from sane2 to sane1 would be a waste of effort IMHO, and not a good incentive to convert backends. I might have some time in a couple of weeks, so maybe I'll have a closer look at SANE2 to find out how the conversion can be done. This is an RFC. Andras Frank.
[sane-devel] UMAX Astra 2200 USB weirdness (Repost)
Oliver Rauch wrote: Disable qualtiy calibration Oliver Olivier, could the backend avoid using this command for the umax 2200, since the scanner does not support it (even in scsi)? I don't have access to that scanner anymore, so I cannot test. Frank.
[sane-devel] detect the correct scanner
Hi Foffy_69, Assuming your scanner works, why do you care? Another solution to your problem would be to print a Plustek sticker and put it on top of the Genius logo. :) Frank. Foffy wrote: i have a genius color page vivid-III but when mandrake detect it as a plustek, that has the same chip. Is this important or not? and how i can get it detected as genius color page vivid-III.
[sane-devel] sane-backends effectively GPL'd in disguise?
Hi Olaf, IANAL but I'll try to answer anyway. None of these contain code. Just prototype and APIs. I don't think that the omission of the SANE exception would propagate to the rest of the code. Besides the README states that the backends are under GPL+exception. It is also quite clear that the authors of these files didn't intend to put these files under GPL only since they were written specifically for SANE. The files should be fixed though. Frank. Olaf Meeuwissen wrote: Dear all, I have been upgrading Image Scan! for Linux to use SANE internals from sane-backends-1.0.12. Ever since the FSF slapped us on the wrist for an unintentional violation of the GPL, we have a little allergic to license issues so I combed through the include/, lib/ and sanei/ directories for license problems. The following files in include/ and sanei/ are GPL'd *without* the SANE exception: include/lalloca.h include/lassert.h include/sane/sanei.h include/sane/sanei_codec_ascii.h include/sane/sanei_codec_bin.h include/sane/sanei_scsi.h include/sane/sanei_thread.h include/sane/sanei_usb.h include/sane/sanei_wire.h include/sane/saneopts.h sanei/linux_sg3_err.h Even though I have read the GPL twenty+ times over, I am still not sure whether this means that files including any of these would effectively void their SANE exception (assuming they have one). After all the SANE exception explicitly states: This exception does not, however, invalidate any other reasons why the executable file might be covered by the GNU General Public License. Ergo, files like sanei/sanei_scsi.c and sanei/sanei_usb.c, which include their counterpart header files, might in effect be released under the GPL and the GPL only without any SANE exception. The same logic applies to backends including files from the above list. The TODO notes that the getopt*.c and md5.c files have been checked for (and replaced by LGPL'd versions) precisely the reasons cited above. Could anyone shed any light on this?
[sane-devel] Compiling SANE backends on Mac OS X 10.1.5
I'm not an OSX user, but it seems this (sick pice of) code needs to be compiled with a C++ compiler, or at least a C compiler with non-standard extensions. You can try CC=g++ ./configure and recompile. Frank. David Alan Hjelle wrote: Hello. I've been trying to get my Microtek SlimScan C6 cheap-o scanner to work under Mac OS X for a while now, and just recently ran across SANE. I figure I should be able to use SANE with the GIMP, which I use somewhat regularly. I was trying to compile the lastest CVS snapshot (from June 2, 2003) of SANE backends, but I ran into some problems. ./configure ran no problem. make, however, eventually gave me the following errors (Or, at least, these are the errors deaing with the sanei_scsi.c file that seemed to be the cause for the compilation problem. I think everything else was just warnings. Of course, what do I know? I'm only just teaching myself C programming and have only had experience in VB and Java shrug.):
[sane-devel] translation question
Hi Andras, Major A wrote: As if I didn't have enough work already... now I came up with the idea of creating a new translation for the SANE backends. I read the README in the po directory and found a .po file for each language. Now a few questions: - Are the comments in the .po file that tell where a string is used (file, line) automatically generated, and if yes, how? If no, are they really necessary? (I would hate to have to update the file every time a backend changes.) Yes, they are. The GNU tools (xgettext, msgfmt and msgmerge) take care of the details. You just have to translate from english and forget about the rest. - What happens if a string isn't found in a language? Does gettext just use the original version hardcoded into the backend? Yes. So you can do the translation bit by bit, since it's a tedious process. Frank.
[sane-devel] sane backends port to windows
Hi, I've started a port of the sane backends to windows. It's rather limited right now, but I can use one of my scsi scanner under the cygwin environment. Infos and patch at my temporary site: http://home.austin.rr.com/fzago/sane/windows/sane_on_windows.html Frank.
[sane-devel] can not initialize sane when linux system booting up
On Tue, 20 May 2003 01:24, Henning Meier-Geinitz wrote: Hi Henning Even though I have completely re-partitioned [more partitions] my hard drive [though same spot as mdk9.0 install] before installing mdk9.1, I have my acer 640u scanner running great guns. Is it possible that this latest install was able to use my previously configured scanner settings?? I'm only asking so as to be of help to others by passing on my experiences with this scanner because I believed that this recent fresh install had actually configured things for me??? H might explain why I have website history in my browsers first time up with 9.1 SnapafunFrank Hi, On Mon, May 19, 2003 at 07:14:58PM +0700, T.M.Thanh wrote: Sane can't initialize my Acer 640 BU Scanner when linux system booting Does sane-find-scanner fin the scanner? If not, it's a kernel issue. If it's found by sane-find-scanner but not scanimage -L, maybe you haven't given the correct path to the firmware filr in snapscan.conf? Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel -- Regards Frank 025853824 Either big or small, a challenge requires the same commitment to resolve.
[sane-devel] Q: Recommendation on ADF scanners?
A Panasonic kv-ss25 or ss25d can scan about 20 to 25 A4 page per minutes. They retail new for about $2K to $4K, but you can find some used on ebay for less than $400. I don't know how often they need maintenance, though. Both scanners are supported by SANE. Note that the scan speed is for a batch job. A page per page scan speed will be about 5 ppm. Frank. Mattias K wrote: I need some recommendations about which scanner to buy. I need a fast A4 scanner with ADF. Scan speed around 30 ppm. Black/white or grayscale. I need it to scan waybills (around 500 per day). No high quality requirements; quality has to be only slightly better than faxed documents... Price should be no more than USD 4000. Any ideas? Which scanner should i choose?? Thanks in advance. /Mattias _ Fynda på nätet! Handla på MSN Shopping http://www.msn.se/shopping ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Last call for new backends
Henning Meier-Geinitz wrote: Hi, if you intend to get a new backend into SANE 1.0.12 it's now time to tell us. Currently there are two backends on the TODO list: - Hewlett-Packard 4200c [...] http://fz.eryx.net/sane/#hp4200 What's the status of those? Are there any others that are intended to go in 1.0.12 (or later versions)? Last time I tested my version (http://fz.eryx.net/sane/#hp4200), it worked. However I don't have access to that scanner anymore, so I won't push for its inclusion. Frank.
[sane-devel] Re: Upgrade question
On Thu, 20 Mar 2003 19:10, T. Ribbrock wrote: On Thu, Mar 20, 2003 at 11:20:30AM +0800, Stephen Liu wrote: Where on earth did you get that sane-1.0.3 RPM from? It was not amon= g the ones you listed as downloaded in your original mail! So, why are you installing it? As I mentioned in my earlier mails, sane-1.0.3 = is an *older* version of sane - but you've already successfully install= ed 1.0.10/1.0.11 - you've said so yourself above. Forget that package! Sorry, I have no idea where did sane-1.0.3 come from. rpm -qa | g= rep sane could not find it. Of course not - it's *not* installed, so rpm cannot find it! But when you tried to upgrade/install the newer RPMs, you used rpm -Uhv *.rpm, which would try to use *all* RPMs present in the curr= ect directory. So, for whatever reasons, there is a sane-1.0.3-.SOMETHING.r= pm in the same directory you stored the newer RPMs in. XXX Hi Stephen This point above is so important. I am still trying to rid my system = of a=20 rpm I had left behind. Still, Linux is a welcome change I am enjoying. --=20 Regards Frank fr...@snapafun.co.nz 025853824 XXX Hint: If using a wildcard when installing/upgrading RPMs (like so: '*.rpm'), you need to make *absolutely sure* that the directory you're= in contains *only* the RPMs you really want to install/upgrade, otherwise= , chaos will ensue... [...] I have following packages for RH8.0 downloaded but encountering probl= em to install them BZZT! No need to read further for me. Stephen, please think about this: You *yourself* told us that you have a RHL 7.3 system. WHY are you downloading RHL 8.0 packages to install on that system? Cheerio, Thomas
[sane-devel] Upgrade question
On Wed, 19 Mar 2003 00:27, Stephen Liu wrote: Hi Frank, Thanks for your advice. Frank wrote: - snip - Now I have following packages downloaded from ftp.redhat.com sane-backends-1.0.11-1.i586.rpm sane-backends-devel-1.0.11-1.i586.rpm sane-frontends-1.0.10-1.i586.rpm xsane-0.90-1.i586.rpm xsane-gimp-0.90-1.i586.rpm Kindly advise whether I can upgrade and run those packages (.i586.r= pm) in my system While you wait for expert advise why not cd to your directory you downloaded to and issue the following. #rpm -Uvh --test *.rpm It may help a lot. as USER $ su - Password: # rpm -Uvh --test /home/satimis/Download/Sane/i586/*.rpm Preparing...### [100%] file /usr/bin/sane-config conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/bin/scanimage conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/libsane.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-abaton.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-agfafocus.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-apple.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-artec.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-avision.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-canon.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-coolscan.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-dc210.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-dc25.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-dll.so.1 conflicts between attempted install= s of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-dmc.so.1 conflicts between attempted install= s of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-epson.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-hp.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-microtek.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-microtek2.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-mustek.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-mustek_pp.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-net.so.1 conflicts between attempted install= s of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-plustek.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-qcam.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-ricoh.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-s9036.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-sharp.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-snapscan.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-sp15c.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-st400.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-tamarack.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-umax.so.1 conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/lib/sane/libsane-v4l.so.1 conflicts between attempted install= s of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/sbin/saned conflicts between attempted installs of sane-backends-1.0.11-1 and sane-1.0.3-1 file /usr/bin/xcam conflicts between attempted installs of sane-frontends-1.0.10-1 and sane-1.0.3-1 file /usr/bin/xscanimage conflicts between attempted installs of sane-frontends-1.0.10-1 and sane-1.0.3-1 It seems there are conflicts
[sane-devel] Spot Dynotak 6p
Spot's been long dead. AFAIK there is no sane driver, not even a started one, and very little chance to see one one day. Frank. Libbi wrote: Hi, the list of the supported scanners doesn't contain Spot Dynotak 6p. There doesnt exist any win xp-dirver, so i hoped to get it working using linux. But the scanner seems not to be supported, too. Is it possible to use the scanner anyway? Or will the scanner be supported in the near future? Thanks for your help, Libbi
[sane-devel] Upgrade question
On Tue, 18 Mar 2003 17:30, Stephen Liu wrote: Hi all folks, RH7.3 CPU: PII-350 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D I have following packages installed and running in my system $ rpm -qa|grep sane sane-backends-1.0.7-6 sane-frontends-1.0.7-2 xsane-0.84-2 sane-backends-devel-1.0.7-6 Now I have following packages downloaded from ftp.redhat.com sane-backends-1.0.11-1.i586.rpm sane-backends-devel-1.0.11-1.i586.rpm sane-frontends-1.0.10-1.i586.rpm xsane-0.90-1.i586.rpm xsane-gimp-0.90-1.i586.rpm Kindly advise whether I can upgrade and run those packages (.i586.rpm) in my system Thanks in advance. B.Regards Stephen Liu While you wait for expert advise why not cd to your directory you downloa= ded=20 to and issue the following.=20 #rpm -Uvh --test *.rpm It may help a lot. --=20 Regards Frank fr...@snapafun.co.nz 025853824
[sane-devel] lost with FUJITSU scanner M3096G
I've tried it with RedHat 8.0 linux. The sense bytes 16 and 17 really point to the offending byte (I've tried to set a invalid resolution an others). There is a 8 byte window header you can't see in the hexdump above. The offending byte is at position 25 (0x02). This means 'grayscale monochrome'. Dirks M3096G doesn't seem to support grayscale (probably that firmware bug?). Or it support grayscale, but not with a 8 bits depth. What about 4? See set_WD_bitsperpixel in setWindowParam(). Frank
[sane-devel] lost with FUJITSU scanner M3096G
[fujitsu] set_window_param [fujitsu] Window set [fujitsu] 000: 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00 00 00 [fujitsu] 016: 03 b0 00 00 05 89 00 00 00 02 08 00 00 00 00 00 [fujitsu] 032: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0 [fujitsu] 048: 20 00 00 00 00 84 00 00 00 00 00 00 00 00 00 00 [fujitsu] 5/38/0: Invalid field in parm list [fujitsu] sanei_scsi_cmd: returning 0x0004 [fujitsu] sane_start: ERROR: failed to set window The scanner rejected the window parameter. If the scsi implementation is decent, the sense might contain the offset of the offending byte somewhere around byte 16 oy 17. To get that, at the beginning of scsi_sense_handler, add this line: hexdump (MSG_IO, Sense, sensed_data, sensed_data[7]+8); Frank.
[sane-devel] Problem in setting up Xsane (problem half solved)
On Sat, 01 Mar 2003 06:10, Stephen Liu wrote: Hi Stephen As a technically inclined newbie I tried what you did and discovered the = below=20 difference. Maybe might help you? Hi Henning, Further to my later posting I take following actions; as user su password [root@server /]# rpm -qa|grep sane sane-backends-1.0.7-6 sane-frontends-1.0.7-2 xsane-0.84-2 sane-backends-devel-1.0.7-6 [root@server /]# sane-find-scanner # Note that sane-find-scanner will find any scanner that is connected # to a SCSI bus and some scanners that are connected to the Universal # Serial Bus (USB) depending on your OS. It will even find scanners # that are not supported at all by SANE. It won't find a scanner that # is connected to a parallel or proprietary port. sane-find-scanner: found SCSI scanner AGFA SNAPSCAN 310 1.90 at devic= e /dev/sg1 sane-find-scanner: found SCSI scanner AGFA SNAPSCAN 310 1.90 at devic= e /dev/sgb In the following section I was sure to include exactly what sane-find-sca= nner=20 returned. In your case might I suggest : ( NB -Do not go as su! ) #cd /dev #chmod -c 0777 sg1 I not sure why but I think in ensures 777 status to your sg1 file as loca= l and=20 not possibly only as root. [ This also allowed me to see the double entry= I=20 did know I had of my scanner when I issued xsane. I was given given a cho= ice=20 in my case to select xxx/scanner or xxx/scanner0. H Both wor= ked. XXX [root@server /]# cd /dev/ [root@server dev]# ln -s sgb scanner [root@server /]# ls -l /dev/sgb lrwxrwxrwx1 root root3 Aug 24 2002 /dev/sgb - sg1 [root@server dev]# cd / [root@server /]# chmod -c 0777 /dev/sg1 mode of `/dev/sg1' changed to 0777 (rwxrwxrwx) Start 'xsane'. After accepting the licence an Error warning popup xane: no devices available B.Regards Stephen Henning Meier-Geinitz wrote: Hi, On Fri, Feb 28, 2003 at 08:45:54PM +0800, Stephen Liu wrote: # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e Type: CD-ROM ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 02 Lun: 00 Vendor: AGFA Model: SNAPSCAN 310 Rev: 1.90 Type: Scanner ANSI SCSI revision: 02 Good. Does sane-find-scanner find your scanner? Does it find it if you run as user? If it only works as root, you must set up permissions for t= he SCSI devices. See man sane-scsi and search for permission. When it's found by sane-find-scanner, try scanimage -L. If it's not found, show us the output of SANE_DEBUG_SNAPSCAN=3D255 scanimage -L Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel --=20 Regards Frank fr...@snapafun.co.nz 025853824
[sane-devel] XSane newbie worry?
Hi folks I follow your forum in the hope of learning things because I had to set u= p my=20 own firmware and stuff for Acer640U. It appears to function OK but when I start xsane from within a terminal I= get (xsane:3657): Gtk-CRITICAL **: file ../../gtk/gtkbox.c: line 395=20 (gtk_box_pack_end): assertion `child-parent =3D=3D NULL' failed Should I be concerned at this point? --=20 Regards Frank fr...@snapafun.co.nz 025853824
[sane-devel] USB for Umax Astra 2200 SU
Klaus Dahlke wrote: Hi all, I have a problem with my Umax Astra 2200 SU (it has both connectors, SCSI and USB). SCSI and USB works fine with Win98 (i.e., hardware is okay), SCSI works also under Linux (for various reasons I am thinking of switching to USB). When attached to USB, scanner is detected by xscanimage on either /dev/usbscanner or /dev/usb/scanner0. I can nicely do a preview or multiple previews. But when I want to do the actual scan, the scanner starts with some action (about a second or so) and then do nothing. The output from strace is continuously producing: Hi Klaus, Have you disabled quality calibration option? If not, do it and try again. Frank.
[sane-devel] USB for Umax Astra 2200 SU
Frank, thanks for the quick reply. With having quality calibration switched off, it wokrs fine now. Is then there any loss in quality compared to SCSI with quality calibration switched on? I don't think so. The command to set the qualibration level fails on both usb and scsi (command not supported). The difference is that the backend knows how to handle bad news from the scanner when accessed with scsi but not with usb. A proper fix would be to disable that command for that scanner, but I don't have access to it anymore. Frank.
[sane-devel] Sane and gsc-1.1 on AIX 4.3.3-ml10
Hi Stephen, Can you enable the tracing, as described in the readme file, and send me the output? Since you're using aix 4.3.3, you can try using the original gsc (version 1.0). Frank. Stephen Hegarty wrote: Hi All, Anyone using AIX?? I am trying to use sane on AIX 4.3.3 (RS/6000) but to do this, sane requires generic scsi drivers: http://fz.eryx.net/aix/gsc-1.1.tar.gz. I have built this using gcc 3.2.1 and GNU make. However, `lsdev -Cc generic` returns - gsc0 Available 10-60-00-1,0 Feral Software Generic SCSI Release 1.1 But, `./tstinq /dev/gsc0` returns - GSC_CMD: I/O error This results in `sane-find-scanner` returning - # No SCSI scanners found. Has anyone sucessfully run Sane or GSC on an AIX 4.3.3 system? AIX has no native scanner support and IBM UK UNIX support team have not been helpful. Any help would be appreciated. Regards, Stephen. __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] no scanners found (leo s3 scsi-scanner)
Hi,
I've added an entry in the backend for this variant. You might as well wait for
sane 1.10.
But if you're in a hurry, remove the spaces and recompile sane.
eg change
{6, LEO , LEOScan-S3 ,
to
{6, LEO, LEOScan-S3,
Regards,
Frank.
Henning Meier-Geinitz wrote:
Hi,
On Thu, Jan 16, 2003 at 11:01:54PM +0100, axel dammers wrote:
But sane-find-scanner -v -v shows not a 0 behind the scanner name:
Yes, it does:
searching for SCSI scanners:
checking /dev/scanner... open ok
Inquiry for device:
000: 06 00 02 02 1f 00 00 00 4c 45 4f 00 00 00 00 00LEO.
016: 4c 45 4f 53 63 61 6e 2d 53 33 00 00 00 00 00 00LEOScan-S3..
There are the 00 00 ... after the text. The backend expects spaces (32
= 0x20).
Have I to do anything in the sourcecode ?
Try it. Remove the spaces as I mentioned.
Bye,
Henning
___
Sane-devel mailing list
sane-de...@www.mostang.com
http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] no scanners found (leo s3 scsi-scanner)
axel dammers wrote: Hi, thanks for your tip. I compiled it without the spaces in leo.c and the scanner runs !!! Very much thanks for your good help. :-)) Bye, Axel Thanks for the report. Frank.
[sane-devel] no scanners found (leo s3 scsi-scanner)
Henning Meier-Geinitz wrote:
Hi,
On Wed, Jan 15, 2003 at 09:59:03PM +0100, axel dammers wrote:
It's right, the name of the scanner is LEO LEOScan-S3.
Here are the output of SANE_DEBUG_LEO=255 scanimage -L:
[sanei_debug] Setting debug level of leo to 255.
[leo] sane_init
[leo] This is sane-leo version 1.0-9
[leo] (C) 2002 by Frank Zago
[leo] attach_scanner: /dev/sg0
[leo] leo_init: enter
[leo] leo_init: exit
[leo] attach_scanner: opening /dev/sg0
[leo] leo_identify_scanner: enter
[leo] device is LEO LEOScan-S3 1.10
[leo] leo_identify_scanner: exit, device not supported
Looks like a detection problem. I don't know anything about the leo
backend, but here is part of the source code (backend/leo.c):
static const struct scanners_supported scanners[] = {
{6, ACROSS , ,
Across, FS-1130},
{6, LEO , LEOScan-S3 ,
Leo, S3}
};
So the backend expects spaces after the names but the SCSI inqiry
seems to put a 0 after the names (?).
You can verify that by running sane-find-scanner -v -v and looking at
the SCSI inqiry. If there is a 0 after the names, that's the problem.
You can try to modify the source code by removing the spaces after LEO
and LEOScan-S3 to find out,i ft this is the problem.
Yes. That seems to be the problem. I have some scsi traces for that scanner,
and
there is spaces after the names. However the firmware version is not the same
(3.01 instead of 1.10 here).
I that fixes your issue, I'll add an entry for it before the next release of
SANE.
Frank.
[sane-devel] hp4200 driver patch for SANE 1.0.9
Julien BLACHE wrote: Till Kamppeter till.kamppe...@gmx.net wrote: I didn't test whether the driver is actually working with SANE 1.0.9, as I don't have the appropriate scanner. But the patch works and after compiling SANE the hp4200 backend is there. I included the backend in the libsane-extras Debian package, and I've got a few (one or two) success reports with it. Since then, SANE 1.0.9 made its way into the Debian archive and nobody complained, so... either it works[*] or nobody uses it :) Frank Zago said on October 30th that he was working on the backend, but nothing else has happened since then. Any news ? JB. [*] IIRC the backend only supports a few features Hi Julien, I've posted my changes at http://fz.eryx.net/sane/#hp4200 I'll try to borrow that scanner again to finish testing the backend. When it's ready, I'll submit it for inclusion. Frank.
[sane-devel] Looking for docs. Net sane?
Hi David, There a link for that on the sane documentation page: http://mostang.com/sane/docs.html To acces your scanner from windows, check SaneTwain. http://mostang.com/sane/sane-frontends.html Frank. David Hostetler wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have heard that you can set up SANE on a Linux / BSD / Solaris box and share it to any of the machines on a network. I am looking for docs on how to do this, and how to be able to access it from Windows, and Linux clients. I have one scanner and three PCs that need to access it. One of the PCs is my wife's Windows 2000 PC. Am I on the right track and can you suggest what docs to read for doing this? Thanks... - -- David B. Hostetler First Line Computer Systems -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE98SsBUpT27+K2BFURAjgzAJwOwYC3UlOeXZXO9sSAQrHloIYUNQCg1VN2 kw3swgR9rRPPhpvjrB9GI6c= =AVII -END PGP SIGNATURE- ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] SANE i18n: only one translation file per language?
Opinions? Other advantages/disadvantages? It looks good. Another advantage is that might help harmonize the terminology used in various backends (eg Color vs Colour.) Frank.
