Model names (was: [sane-devel] Proposed timetable for the release of sane-backends-1.0.16)
Johannes Meixner jsm...@suse.de writes: Hello, Hi, On Jul 5 08:50 Gerhard Jaeger wrote (shortened): On Tuesday 05 July 2005 02:10, Olaf Meeuwissen wrote: I would much appreciate it if someone with commit privileges would be so kind as to update doc/descriptions-external/epkowa.desc. done - with a small correction, you might want to cross-check that. I noticed that many model names are a bit different in epson.desc and epkowa.desc. In epkowa.desc I tried to stick to the names under which the scanners are marketed as much as possible. That means that most of the names in that file should correspond (quite well) with what is on the case, so users should be able to find out whether their particular model is supported or not. I don't have the detailled knowledge which model names are exactly the right ones but I assume that many of those models are on fact the same. Yes, many of them are and, where known, I included such information in the comment. You'll see things like overseas version of the As scanner config tools build the model lists from the *.desc files it leads to some user confusion which exact model he should select. Such scanner config tools put an awful lot of faith in files that in most situations are updated manually and bear no direct mechanical correspondence to the sources for the backend. I know that such a correspondence will be hard to establish but anyway. The user may think that one model is only supported by one backend because of sightly different model names. Actually, I've seen the reverse. Oh, the Perfection 1650 is supported by the epson and epkowa backends. Cool! I'll go buy the 1670. That should work. Well, it doesn't. BTW, the 1670 is supported by the snapscan backend. A scanner config tool cannot find the matching backends if the model name in *.desc is sightly different than the autodetected model name and therefore the tool will not offer all backends which work in fact for the scanner to the user. Example: The labels on my scanners (i.e. what is on the hardware) are EPSON PERFECTION 1240U and EPSON PERFECTION 2480 PHOTO. In epson.desc there is Epson Perfection 1240. In snapscan.desc there is Epson Perfection 2480. In epkowa.desk there is EPSON Perfection 1240U and EPSON Perfection 2480 PHOTO. Apart from upper/lower case differences, they match alright with what is in epkowa.desc, but see below. Note, the SANE spec even says that backends should use Epson for the vendor strings. If this is the worst of your troubles, may I suggest that your config tool uses strcasecmp(). sane-find-scanner finds the EPSON PERFECTION 1240U as ... vendor=0x04b8 [EPSON], product=0x010b [Perfection1240] ... and the EPSON PERFECTION 2480 PHOTO as ... vendor=0x04b8 [EPSON], product=0x0121 [EPSON Scanner] ... lsusb -v lists the EPSON PERFECTION 1240U as idVendor 0x04b8 Seiko Epson Corp. idProduct 0x010b Perfection 1240 iManufacturer 1 EPSON iProduct2 Perfection1240 and the EPSON PERFECTION 2480 PHOTO as idVendor 0x04b8 Seiko Epson Corp. idProduct 0x0121 iManufacturer 1 EPSON iProduct2 EPSON Scanner Summary: Most model strings are slightly different depending where the information is stored. Very well observed and this is exactly why autodetected strings do not match, in principle, what is on the case. When case is ignored and meaningless characters (e.g. all except abcdefghijklmnopqrstuvwxyz0123456789+) are ignored, more model strings become equivalent but trailing meaningful characters (like U or PHOTO) cannot be ignored by a scanner setup tool and this leads to the above problems for the users. FYI, the U stands for USB and PHOTO indicates that the scanner sports a TPU. There is also S for SCSI. As far as EPSON scanners are concerned, I think you'll get along quite well with longest substring match. I would apprecialte it if at least the manufacturer and model strings in epson.desc and epkowa.desc would be the same and if possible exactly those which are autodetected. The first part of your request can be done. It just needs a bit of synchronisation between the files. (Karl, are you listening? CC'd you explicitly, so I'd say yes. Want a diff against epson.desc?) The second part is plain impossible. By the way: Does anybody know why model name autodetection fails for the EPSON PERFECTION 2480 PHOTO? Is the model name stored inside the scanner and this model reports only EPSON Scanner on the USB bus or has the USB system a map model ID - model name where an entry for this model is missing? Let's see how many names there are. - one on the scanner case - one reported as part of the USB/SCSI information - one reported by the firmware As Oliver Schwartz already noted in a different follow-up, the names used by EPSON are, eh, not very consistent. That puts it mildly. Just take a
[sane-devel] epson 1250 scanning dark color
John H. mistama...@yahoo.com writes: My epson 1250 is scanning very dark when I do color, why is that? xsane-gimp-0.96-1 sane-frontends-1.0.13-2 sane-backends-1.0.15-9 xsane-0.96-1 good color in windows. What backend? I'd guess plustek but this scanner is also supported by the epkowa backend. -- Olaf Meeuwissen EPSON AVASYS Corporation, LAN FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] testing of the HP Jetscan 2400c
Le Mardi 5 Juillet 2005 12:14, carlos a =E9crit=A0: Hi, I have an HP Jetscan 2400c. I have compiled and tried the genesys backend, and when I try scanimage -T it endups in an endless loop. The following trace repeats forever: [genesys] gl646_read_valid_words [genesys] genesys_low_read_register (0x44, 0x00) completed [genesys] genesys_low_read_register (0x43, 0x00) completed [genesys] genesys_low_read_register (0x42, 0x00) completed [genesys] gl646_read_valid_words: 0 words If anyone is interested I can attach a file with the complete traces. cheers, Carlos. Hello, the geneys backend doesn't fully support the 2400c. It is a matter of find= ing=20 all the constants for it. I have received some USB logs so I should be able= =20 to find some things, but I have no hardware to test. If you feel so, I can= =20 start improving 2400c support in the backend. But you'll have to test the=20 changes. BTW, this seems to be a case where the 'experimental' directory will be=20 handy, since we are preparing for a sane-backends release, and 'normal' CVS= =20 should get stable. Regards, Stef
[sane-devel] sanei_usb.c
Hi All, On 3/7/2005, Henning Meier-Geinitz henn...@meier-geinitz.de wrote: Hi, On Tue, Jun 28, 2005 at 10:24:36PM +0930, Paul Smedley wrote: OS/2 doesn't have libusb, but has a library usbcalls that provides similar functionality, albeit most of the calls use different syntax. I have sane-find-scanner working now for most scanners, and have started work on remaining functions in sanei_usb.c As an update. Last night I did my first scan with scanimage and a modified sanei_usb.c Originally I was working with sane-backends-1.0.15 so I'm now bringing my stuff up to scratch with the latest code in CVS. I need some help with configure - I'm not familiar with the syntax.. What I need is to check for the presence of usbcalls.h - and if present, add HAVE_USBCALLS to config.h add -lusbcalls to LIBS BACKENDLIBS Other changes only involve changes to sanei_usb.c and sane-find-scanner.c sane-find-scanner still isn't perfect so I'll probably not update that for 1.0.16 but hopefully I'll have a good patch for sanei_usb.c tonight. Is there a standard format/options for diffs sane? Cheers, Paul.
[sane-devel] testing of the HP Jetscan 2400c
Hi, I have scanjet 2400c. I can do testing. How do I do testing? Thx, Sanjay Hello, the geneys backend doesn't fully support the 2400c. It is a matter of finding all the constants for it. I have received some USB logs so I should be able to find some things, but I have no hardware to test. If you feel so, I can start improving 2400c support in the backend. But you'll have to test the changes. BTW, this seems to be a case where the 'experimental' directory will be handy, since we are preparing for a sane-backends release, and 'normal' CVS should get stable. Regards, Stef -- 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 __ __
Model names (was: [sane-devel] Proposed timetable for the release of sane-backends-1.0.16)
Hello Olaf, many thanks for the detailed information. I need it very much to reject all those wishes for a full automagic hardware setup which come up again and again by the usability experts ;-)) On Jul 6 10:02 Olaf Meeuwissen wrote (shortened): Johannes Meixner jsm...@suse.de writes: As scanner config tools build the model lists from the *.desc files it leads to some user confusion which exact model he should select. Such scanner config tools put an awful lot of faith in files that in most situations are updated manually and bear no direct mechanical correspondence to the sources for the backend. I know that such a correspondence will be hard to establish but anyway. I do not trust these files. Therefore I didn't implement an automated scanner setup. The user must select the model from a list. But I build the list from the *.desc files because I don't know a better method. I preselect a model in the list if the autodetected model name is equivalent to exactly one model name in the list. Preselect means that the list entry is marked (highlighted) as selected but nevertheless the whole list is shown so that the user can see and select any other list entry. Equivalent means: I convert both the autodetected model name and the model name in the list to lower characters and remove all characters except abcdefghijklmnopqrstuvwxyz0123456789+. If the resulting strings are the same, the autodetected model name and the model name in the list are equivalent. If more list entries (i.e. more backends) match, I don't preselect because too many users accept blindly anything what is preselect but I let the user select the model (i.e. the backend) manually. But if the model name in one *.desc file is equivalent but not in another *.desc file because of slightly different model names, I may preselect it even if it is in fact supported by two backends (or if it is marked as unsupported in one *.desc but not in the other). The user may think that one model is only supported by one backend because of sightly different model names. Actually, I've seen the reverse. Oh, the Perfection 1650 is supported by the epson and epkowa backends. Cool! I'll go buy the 1670. That should work. Well, it doesn't. BTW, the 1670 is supported by the snapscan backend. As the 1670 is well documented in epkowa.desc and snapscan.desc, there should be no problem. But this shows that it is important to have even unsupported models listed (like the 1670 in epkowa.desc) so that the user is informed. And the example shows that consistent model names for same models in different *.desc files are important because on the one hand slightly different model numbers can make a big difference but on the other hand other minor differences don't make a real difference - how should a normal user understand this without consistent model names. I would apprecialte it if at least the manufacturer and model strings in epson.desc and epkowa.desc would be the same and if possible exactly those which are autodetected. The first part of your request can be done. It just needs a bit of synchronisation between the files. (Karl, are you listening? CC'd you explicitly, so I'd say yes. Want a diff against epson.desc?) The second part is plain impossible. I don't think it is plain impossible. I think it is possible but requires enhanced *.desc files (model autodetection strings must be added to the *.desc files) and a lot of additional work. The question is whether a full automagic hardware setup is what normal users really must have? Up to now I don't have one single user complaint because he must select his model from a list. Why all the different names? These scanners are all marketed in different regions (something that I also try to explain in a comment in epkowa.desc). Not only are the model names different, but quite often the imprint on the panel differs as well. Then there may also be minor differences in what Windows/Mac software comes with it. None of these differences have anything to do with getting the thing to work with SANE, but, well, someone thinks there's a need to keep them apart somehow. # And drive you and me nuts in the meantime ;-) If all the different names are listed in the *.desc file it is perfectly o.k. because all what a normal user want is that he finds his model in the list. If there are too many same models with slightly different names, something like ACME FunScanner 12xx series is also perfectly o.k. provided that there are no exceptions (e.g. if ACME FunScanner 123L doesn't work the same as the rest of ACME FunScanner 12xx series). The epkowa backend bends over backwards to try to figure out a model name that corresponds to what is on the case Of course it is the backend which knows best about all its models and all the special cases, remember the discussion e.g.: http://lists.alioth.debian.org/pipermail/sane-devel/2005-February/013155.html (and the whole big
[sane-devel] testing of the HP Jetscan 2400c
--u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Stef, I very much would like to contribute with the testing, let me know when you have something new to try.=20 cheers, Carlos On 06/07/05 06:57, St=E9phane VOLTZ wrote: Le Mardi 5 Juillet 2005 12:14, carlos a =E9crit=A0: Hi, I have an HP Jetscan 2400c. I have compiled and tried the genesys backend, and when I try scanimage -T it endups in an endless loop. The following trace repeats forever: [genesys] gl646_read_valid_words [genesys] genesys_low_read_register (0x44, 0x00) completed [genesys] genesys_low_read_register (0x43, 0x00) completed [genesys] genesys_low_read_register (0x42, 0x00) completed [genesys] gl646_read_valid_words: 0 words If anyone is interested I can attach a file with the complete traces. cheers, Carlos. =20 Hello, =20 the geneys backend doesn't fully support the 2400c. It is a matter of fi= nding=20 all the constants for it. I have received some USB logs so I should be ab= le=20 to find some things, but I have no hardware to test. If you feel so, I ca= n=20 start improving 2400c support in the backend. But you'll have to test the= =20 changes. =20 BTW, this seems to be a case where the 'experimental' directory will be= =20 handy, since we are preparing for a sane-backends release, and 'normal' C= VS=20 should get stable. =20 Regards, Stef =20 -- 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 --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCy6cju03MR1b64EkRAjVgAJ4sYJpRl8MjG2ILMUhAFJYU1HQkYwCdHKgd oCGod2lUHZKsZ2ZCrtK3heE= =PImm -END PGP SIGNATURE- --u3/rZRmxL6MmkK24--
[sane-devel] Nikon LS 5000
Greetings, I tried to email directly the author of the Nikon sane project but never obtained a reply. So, I try to post here with the hope to get an answer, if possible (even from himself). Between Nikon LS 4000 and LS 5000 there are major improvements that made me choose the LS 5000. Moreover, LS 4000 has been discontinued by Nikon, at least in Italy. So, how will I be able to make my LS 5000 work if I do not see any compatibility with sane? I kindly wish to ask if the developer for Nikon has any plan and any schedule date. Also, I wish to ask you guys for help/advice. Obviously, I am aware of ViewScan, but do not know if I can perform batch perfectly with the Nikon LS 5000. I have to scan a lot of pictures, 35mm films made of negatives that have been cut to 4 frames per each. I have to manual feed them, but wish to do so through batch so that I do not have to interact with the GUI part. Any advice would be appreciated. Thank you so much, Spiro
[sane-devel] sane-backends/lib/getopt.c compiling on OS/2
--=-xxoVopfl9ikfNlv+Vwa4 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2005-07-03 at 15:10 +0200, Henning Meier-Geinitz wrote: getopt.c is compiled and linked unconditionally on all platforms as far as I can see. As this works on all the other platforms there must be something different on OS/2. =20 You could try to move getopt and getopt_long to AC_REPLACE_FUNCS in configure.in and modify lib/Makefile.in accordingly. But I haven't checked all the implications of that. Maybe linking the getopt code was done intentionally. You shouldn't have to do this. If the compiler finds that the glibc has the right getopt version all the code in getopt.c is removed by the #ifndef ELIDE_CODE conditional and it creates an empty getopt.o. Mattias --=-xxoVopfl9ikfNlv+Vwa4 Content-Type: application/x-pkcs7-signature; name=smime.p7s Content-Disposition: attachment; filename=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGbDCCAzIw ggKboAMCAQICAgRqMA0GCSqGSIb3DQEBBAUAME8xDTALBgNVBAoTBEdyaWQxEjAQBgNVBAoTCU5v cmR1R3JpZDEqMCgGA1UEAxMhTm9yZHVHcmlkIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA1 MDQyOTE0MDMzMFoXDTA2MDQyOTE0MDMzMFowUDENMAsGA1UEChMER3JpZDESMBAGA1UEChMJTm9y ZHVHcmlkMRIwEAYDVQQLEwl0c2wudXUuc2UxFzAVBgNVBAMTDk1hdHRpYXMgRWxsZXJ0MIGfMA0G CSqGSIb3DQEBAQUAA4GNADCBiQKBgQDAvfOgojs2NG75FpsOGa0zGOWo+E0CVrTByLd3nC5/ND9Y vghvxoZOtrIugGg5ucNgY/I3Cw6xUILsUbwE+Gi/AbQyKn5kbmUBsOKSnGzdO4pL1UM/4AbBdMo8 3iuBAdznae6SL17hIxmO5heWetqWIG8552dNqM//YXM+j5eBJQIDAQABo4IBGjCCARYwCQYDVR0T BAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIBDQQfFh1PcGVu U1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUA0fPe21XoshhXhD524iDCb2ELwUw dwYDVR0jBHAwboAUGAXA/AvRtzr0ZZIJ+1mhX8eIxPChU6RRME8xDTALBgNVBAoTBEdyaWQxEjAQ BgNVBAoTCU5vcmR1R3JpZDEqMCgGA1UEAxMhTm9yZHVHcmlkIENlcnRpZmljYXRpb24gQXV0aG9y aXR5ggEAMCMGA1UdEQQcMBqBGG1hdHRpYXMuZWxsZXJ0QHRzbC51dS5zZTANBgkqhkiG9w0BAQQF AAOBgQASoeMOjsIA8fXQqWApEZvx8sKNeTQqLXAFk2GOkT1oq9ZQxyVEt0u1gJAQ1CvYqxT8AqZ1 gN0eBjATOblwuRC1M8Apa3T59aPKh6NV+bBWShSoOLMlLTCzjY2ztprrsQs57DJrngzsZ7j2gOnE sayCdy8QTaVGkl3novC4s3q57jCCAzIwggKboAMCAQICAgRqMA0GCSqGSIb3DQEBBAUAME8xDTAL BgNVBAoTBEdyaWQxEjAQBgNVBAoTCU5vcmR1R3JpZDEqMCgGA1UEAxMhTm9yZHVHcmlkIENlcnRp ZmljYXRpb24gQXV0aG9yaXR5MB4XDTA1MDQyOTE0MDMzMFoXDTA2MDQyOTE0MDMzMFowUDENMAsG A1UEChMER3JpZDESMBAGA1UEChMJTm9yZHVHcmlkMRIwEAYDVQQLEwl0c2wudXUuc2UxFzAVBgNV BAMTDk1hdHRpYXMgRWxsZXJ0MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDAvfOgojs2NG75 FpsOGa0zGOWo+E0CVrTByLd3nC5/ND9YvghvxoZOtrIugGg5ucNgY/I3Cw6xUILsUbwE+Gi/AbQy Kn5kbmUBsOKSnGzdO4pL1UM/4AbBdMo83iuBAdznae6SL17hIxmO5heWetqWIG8552dNqM//YXM+ j5eBJQIDAQABo4IBGjCCARYwCQYDVR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQD AgXgMCwGCWCGSAGG+EIBDQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4E FgQUA0fPe21XoshhXhD524iDCb2ELwUwdwYDVR0jBHAwboAUGAXA/AvRtzr0ZZIJ+1mhX8eIxPCh U6RRME8xDTALBgNVBAoTBEdyaWQxEjAQBgNVBAoTCU5vcmR1R3JpZDEqMCgGA1UEAxMhTm9yZHVH cmlkIENlcnRpZmljYXRpb24gQXV0aG9yaXR5ggEAMCMGA1UdEQQcMBqBGG1hdHRpYXMuZWxsZXJ0 QHRzbC51dS5zZTANBgkqhkiG9w0BAQQFAAOBgQASoeMOjsIA8fXQqWApEZvx8sKNeTQqLXAFk2GO kT1oq9ZQxyVEt0u1gJAQ1CvYqxT8AqZ1gN0eBjATOblwuRC1M8Apa3T59aPKh6NV+bBWShSoOLMl LTCzjY2ztprrsQs57DJrngzsZ7j2gOnEsayCdy8QTaVGkl3novC4s3q57jGCAiowggImAgEBMFUw TzENMAsGA1UEChMER3JpZDESMBAGA1UEChMJTm9yZHVHcmlkMSowKAYDVQQDEyFOb3JkdUdyaWQg Q2VydGlmaWNhdGlvbiBBdXRob3JpdHkCAgRqMAkGBSsOAwIaBQCgggErMBgGCSqGSIb3DQEJAzEL BgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA1MDcwNjEwMzExMVowIwYJKoZIhvcNAQkEMRYE FHGVmBDc+oIIWqImpGaURFPD6cm7MGQGCSsGAQQBgjcQBDFXMFUwTzENMAsGA1UEChMER3JpZDES MBAGA1UEChMJTm9yZHVHcmlkMSowKAYDVQQDEyFOb3JkdUdyaWQgQ2VydGlmaWNhdGlvbiBBdXRo b3JpdHkCAgRqMGYGCyqGSIb3DQEJEAILMVegVTBPMQ0wCwYDVQQKEwRHcmlkMRIwEAYDVQQKEwlO b3JkdUdyaWQxKjAoBgNVBAMTIU5vcmR1R3JpZCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eQICBGow DQYJKoZIhvcNAQEBBQAEgYCTc/o62WLIIhK7d1gLEtHdwgZ+uR5x2PH6KNW2vrp1w3U9YMBbusL5 ODqkEZQghzvhtSnsoS8OXEPyc9DcvNAvJxlI/fOOzSFJozsKsWPmQ/9gATm1wI+wOlUJS6yRgxoE l4tgAg0GBUNeMz/lLvtxcqLFAPAMoqv2S3od/TOuaA== --=-xxoVopfl9ikfNlv+Vwa4--
[sane-devel] Nikon LS 5000
Hi, Please check out the archives of this list -- we have hashed out quite a few times what is necessary, what we have etc. A bunch of people (including me) have access to the specifications (under NDA) but not the hardware (I don't, for example) Finally my request for the NDA was accepted by Nikon i was told (took 3 months because i didn't request it under a company hood) so i should get the specs soon. I also have the scanner so i hope to be able to get it working ;-) (hope is the last thing you should loose, right? ;-) But i don't promise any timeframe because holidays are already scheduled :- Cheers, Ariel
[sane-devel] Fujitsu Fi-5110EOX2 USB with current Fujitsu SANE backend?
Has anyone had occasion to use the following Fujitsu scanner with the current SANE fujitsu back-end? Fujitsu Fi-5110EOX2 600 x 600dpi USB Interface Sheet Fed/Document Fed Scanner I'd been planning on a Fujitsu Fi-4120C2, which costs more than twice as much. I presume that despite similar external appearances, the two Fujitsu scanners have completely different internal mechanisms and electronics (hence different SANE compatibility characteristics). The Fi-4120C2 is most likely worth the extra money. Still, if the Fi-5110EOX2 works with the current fujitsu back end equally well, I'd like to get a couple of these cheaper units for lower volume users. Thanks. Sell on Yahoo! Auctions no fees. Bid on great items. http://auctions.yahoo.com/
[sane-devel] Nikon LS 5000]
Thank you very much Ariel! Thank you for replying to my question too. I am glad you are working on this scanner as I see more people needing your assistance. As for me, I am now very happy because the project I have to work on is very big; it involved about 15000 pictures (35mm) and the sponsor, for charity, trusts my work. So, on my behalf, I then trust and rely on your assistance. So, I will purchase the NIKON LS-5000 (feeling more relaxed and peaceful) and as soon as you are completed with the driver I will start my project. I would only ask you one favor, if possible: Please let me-us know when you believe to be close to completing the development and also, if you need me to do some testing let me know. I work on amd64 64bit. I hope to hear something soon or some updates. Thank you, and GOOD WORK! Spiro Hi, Please check out the archives of this list -- we have hashed out quite a few times what is necessary, what we have etc. A bunch of people (including me) have access to the specifications (under NDA) but not the hardware (I don't, for example) Finally my request for the NDA was accepted by Nikon i was told (took 3 months because i didn't request it under a company hood) so i should get the specs soon. I also have the scanner so i hope to be able to get it working ;-) (hope is the last thing you should loose, right? ;-) But i don't promise any timeframe because holidays are already scheduled :- Cheers, Ariel
[sane-devel] sanei_usb.c
Hi, On Wed, Jul 06, 2005 at 04:05:16PM +0930, Paul Smedley wrote: Is there a standard format/options for diffs sane? diff -u (and -r if you diff more than one file) are convenient. Bye, Henning
[sane-devel] Proposed timetable for the release of sane-backends-1.0.16
Hi, On Tue, Jul 05, 2005 at 06:27:21PM +0900, Olaf Meeuwissen wrote: Gerhard Jaeger gerh...@gjaeger.de writes: I would much appreciate it if someone with commit privileges would be so kind as to update doc/descriptions-external/epkowa.desc. It's been a while :-) done - with a small correction, you might want to cross-check that. Thanks. I don't mind having the :status yanked, but why? :status is only valid after the :model keyword (and then you use :unsupported, :good and so on). See doc/descriptions.txt for details. We used to use :status for the :backend but this has been changed to :model. Bye, Henning
[sane-devel] Fujitsu Fi-5110EOX2 USB with current Fujitsu SANE backend?
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1386613362-494497759-1120673779=:29890 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT jeff, any fujitsu with EOX2 on the end is not supported by the sane fujitsu backend. as far as i can tell, those scanners share no electronics with the 'C' versions of the same model. in fact, i have a 4110EOX2, and it is really an MA1509 Mustek chip. i expect that the other EOX2 models are similar. the fi-5110C and the fi-4120C (and C2) work pretty well, i have about 100 of all three. the fi-4120C (no 2) is a little flaky on usb, but the other two seem a little better behaved. the 5110C is noisier, and perhaps only 3/4 the speed of the 4120, but they use the same comm protocol. allan On Wed, 6 Jul 2005, Jeff Kowalczyk wrote: Has anyone had occasion to use the following Fujitsu scanner with the current SANE fujitsu back-end? Fujitsu Fi-5110EOX2 600 x 600dpi USB Interface Sheet Fed/Document Fed Scanner I'd been planning on a Fujitsu Fi-4120C2, which costs more than twice as much. I presume that despite similar external appearances, the two Fujitsu scanners have completely different internal mechanisms and electronics (hence different SANE compatibility characteristics). The Fi-4120C2 is most likely worth the extra money. Still, if the Fi-5110EOX2 works with the current fujitsu back end equally well, I'd like to get a couple of these cheaper units for lower volume users. Thanks. Sell on Yahoo! Auctions no fees. Bid on great items. http://auctions.yahoo.com/ -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera --1386613362-494497759-1120673779=:29890--
[Fwd: Re: [sane-devel] Proposed timetable for the release of sane-backends-1.0.16]
--=-gMCbEfSMB4BdgbWZNbu/ Content-Type: text/plain Content-Transfer-Encoding: 7bit -- m.vr.gr. Gerard Klaver --=-gMCbEfSMB4BdgbWZNbu/ Content-Disposition: inline Content-Description: Forwarded message - Re: [sane-devel] Proposed timetable for the release of sane-backends-1.0.16 Content-Type: message/rfc822 Return-Path: ger...@gkall.hobby.nl Received: from smtp08.wanadoo.nl (smtp08.wanadoo.nl [194.134.35.149]) by meel.hobby.nl (8.12.10/8.12.10) with ESMTP id j66IYNFU089501 for ger...@gkall.hobby.nl; Wed, 6 Jul 2005 20:34:23 +0200 (CEST) (envelope-from ger...@gkall.hobby.nl) Received: from [192.168.43.75] (c529d8363.cable.wanadoo.nl [82.157.131.99]) by smtp8.wanadoo.nl (Postfix) with ESMTP id 1CFCC54488; Wed, 6 Jul 2005 20:34:23 +0200 (CEST) Subject: Re: [sane-devel] Proposed timetable for the release of sane-backends-1.0.16 From: gerard klaver ger...@gkall.hobby.nl Reply-To: ger...@gkall.hobby.nl To: Henning Meier-Geinitz henn...@meier-geinitz.de In-Reply-To: 20050703135544.ga15...@meier-geinitz.de References: 20050703135544.ga15...@meier-geinitz.de Content-Type: text/plain Date: Wed, 06 Jul 2005 20:33:52 +0200 Message-Id: 1120674833.7269.9.camel@gk-lex3 Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=disabled version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on meel.hobby.nl Status: Content-Transfer-Encoding: 7bit On Sun, 2005-07-03 at 15:55 +0200, Henning Meier-Geinitz wrote: Hi everyone, Now that the genesys backend is included into CVS, I think it's time for a new release of sane-backends. Please feel free to comment on the timetable: This is the proposed timetable for the release of sane-backends 1.0.16 2005-07-17 Feature freeze (snapshot) 2005-07-31 Code freeze (snapshot) 2005-08-07 Release Feature freeze means that only bug fixes and documentation updates are allowed. After code freeze only fixes of grave bugs that render a backend completely unusable or break compilation and documentation updates are accepted. If there are any new backends that should be included in that release please tell us NOW. Please everyone have a look at out growing list of bugs and fix as many bugs as possible: http://alioth.debian.org/tracker/index.php?group_id=30186atid=410366 If the bug report is bogus, please close it with a comment why it's closed. If you need more information from the author, add a comment. If you don't get more info and can't reproduce the bug, close it. Also, you can view only bugs assigned to you to reduce the number of visible bugs. Having a look at bugs assigned to nobody is also worth a try as some bugs affect several backends/maintainers. You can also sort by topic (Summary). Happy bug-hunting, Henning I have stil some memory leakage errors (with valgrind xcam -B) when using my stv680 backend. At the moment no idea how to solve them. So i don't know if it will be ready before 17-07-2005. I have placed the files and a log on http://gkall.hobby.nl/downloads.html Files: stv680.c, stv680.h stv680.conf, stv680.desc, sane-stv680.man log-valgrind-stv680.txt So in anyone has an idea about this errors please let me know. -- m.vr.gr. Gerard Klaver --=-gMCbEfSMB4BdgbWZNbu/--
[Fwd: Re: [sane-devel] Proposed timetable for the release of sane-backends-1.0.16]
--=-+Q8ajE/q059bc6Ai+WaD Content-Type: text/plain Content-Transfer-Encoding: 7bit -- m.vr.gr. Gerard Klaver --=-+Q8ajE/q059bc6Ai+WaD Content-Disposition: inline Content-Description: Forwarded message - Re: [sane-devel] Proposed timetable for the release of sane-backends-1.0.16 Content-Type: message/rfc822 Return-Path: ger...@gkall.hobby.nl Received: from smtp08.wanadoo.nl (smtp08.wanadoo.nl [194.134.35.149]) by meel.hobby.nl (8.12.10/8.12.10) with ESMTP id j66IYNFU089501 for ger...@gkall.hobby.nl; Wed, 6 Jul 2005 20:34:23 +0200 (CEST) (envelope-from ger...@gkall.hobby.nl) Received: from [192.168.43.75] (c529d8363.cable.wanadoo.nl [82.157.131.99]) by smtp8.wanadoo.nl (Postfix) with ESMTP id 1CFCC54488; Wed, 6 Jul 2005 20:34:23 +0200 (CEST) Subject: Re: [sane-devel] Proposed timetable for the release of sane-backends-1.0.16 From: gerard klaver ger...@gkall.hobby.nl Reply-To: ger...@gkall.hobby.nl To: Henning Meier-Geinitz henn...@meier-geinitz.de In-Reply-To: 20050703135544.ga15...@meier-geinitz.de References: 20050703135544.ga15...@meier-geinitz.de Content-Type: text/plain Date: Wed, 06 Jul 2005 20:33:52 +0200 Message-Id: 1120674833.7269.9.camel@gk-lex3 Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=disabled version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on meel.hobby.nl Status: Content-Transfer-Encoding: 7bit On Sun, 2005-07-03 at 15:55 +0200, Henning Meier-Geinitz wrote: Hi everyone, Now that the genesys backend is included into CVS, I think it's time for a new release of sane-backends. Please feel free to comment on the timetable: This is the proposed timetable for the release of sane-backends 1.0.16 2005-07-17 Feature freeze (snapshot) 2005-07-31 Code freeze (snapshot) 2005-08-07 Release Feature freeze means that only bug fixes and documentation updates are allowed. After code freeze only fixes of grave bugs that render a backend completely unusable or break compilation and documentation updates are accepted. If there are any new backends that should be included in that release please tell us NOW. Please everyone have a look at out growing list of bugs and fix as many bugs as possible: http://alioth.debian.org/tracker/index.php?group_id=30186atid=410366 If the bug report is bogus, please close it with a comment why it's closed. If you need more information from the author, add a comment. If you don't get more info and can't reproduce the bug, close it. Also, you can view only bugs assigned to you to reduce the number of visible bugs. Having a look at bugs assigned to nobody is also worth a try as some bugs affect several backends/maintainers. You can also sort by topic (Summary). Happy bug-hunting, Henning I have stil some memory leakage errors (with valgrind xcam -B) when using my stv680 backend. At the moment no idea how to solve them. So i don't know if it will be ready before 17-07-2005. I have placed the files and a log on http://gkall.hobby.nl/downloads.html Files: stv680.c, stv680.h stv680.conf, stv680.desc, sane-stv680.man log-valgrind-stv680.txt So in anyone has an idea about this errors please let me know. -- m.vr.gr. Gerard Klaver --=-+Q8ajE/q059bc6Ai+WaD--
