<html><head>
<link media="all" type="text/css" href="/netmail/static/deg/css/wysiwyg-3933289048.css" rel="stylesheet">
</head><body>
Does this give me any help with the Canoscan 4200F ?<br>Thanks!<br><div style="font-size: 12px; font-family: arial;"><div style="font-size: 12px; font-family: arial;"><div style="font-family: arial; font-size: 12px;"><div style="font-family: arial; font-size: 12px;"><div style="font-family: arial; font-size: 12px;"><br></div></div></div></div></div><br><br>Oct 28, 2010 10:38:38 AM, kitno455@gmail.com wrote:<br><blockquote style="border-left: 3px solid rgb(102, 153, 204);">On Thu, Oct 28, 2010 at 1:27 PM, Denis Prost <denis.prost@wanadoo.fr> wrote:<br>> Yes Allan, with just that line, it works !<br>><br>> Denis<br><br>Well, I think that is the best solution then. (though the backend<br>should still be fixed)<br><br>allan<br><br>><br>> Le 28/10/2010 16:57, m. allan noah a écrit :<br>>><br>>> Several comments:<br>>><br>>> 1. the backend should be changed to look at multiple rows of its config<br>>> file.<br>>><br>>> 2. The canon backend code does this:<br>>><br>>> if (ibuf[0] != 6<br>>> || strncmp ((char *) (ibuf + 8), "CANON", 5) != 0<br>>> || strncmp ((char *) (ibuf + 16), "IX-", 3) != 0)<br>>> {<br>>> DBG (1, "attach: device doesn't look like a Canon scanner\n");<br>>> .....<br>>><br>>> So the apple machine must respond as a canon too.<br>>><br>>> 3. The sanei_scsi code appears to use strncmp with the length of the<br>>> string from the config, so this should work:<br>>><br>>> scsi CANON IX<br>>><br>>> Denis- can you put only that line in your config file, and verify that<br>>> the scanner still appears?<br>>><br>>> allan<br>>><br>>> On Thu, Oct 28, 2010 at 10:35 AM, Johannes Meixner<jsmeix@suse.de> wrote:<br>>>><br>>>> Hello,<br>>>><br>>>> On Oct 28 09:52 m. allan noah wrote:<br>>>>><br>>>>> I would need to check the code, but I think the canon backend mostly<br>>>>> supports machines who's model name starts with 'IX' so the best<br>>>>> solution might be:<br>>>>><br>>>>> scsi CANON IX*<br>>>>><br>>>>> or some such?<br>>>><br>>>> I do not have a scanner which is supported by the "canon" backend<br>>>> so that all what I write here is only based upon what I read<br>>>> somewhere.<br>>>><br>>>> According to what I read in "man sane-scsi"<br>>>> ---------------------------------------------------------------<br>>>> scsi VENDOR MODEL TYPE BUS CHANNEL ID LUN<br>>>><br>>>> ... a field's value can be replaced with an asterisk<br>>>> symbol (``*''). An asterisk has the effect that any<br>>>> value is allowed for that particular field.<br>>>> ---------------------------------------------------------------<br>>>> so that it seems it is not possible to replace only a part<br>>>> of a particular field with an asterisk.<br>>>><br>>>> According to<br>>>> http://www.sane-project.org/sane-backends.html#S-CANON<br>>>> the "canon" backend supports at least one non-CANON scanner,<br>>>> the "Apple Color OneScanner 600/27".<br>>>> I have no idea how this device shows up at the SCSI<br>>>> but I assume Apple made sure that "their device" shows up<br>>>> at the SCSI under a manufacturer name like "APPLE".<br>>>><br>>>> According to my tests in<br>>>> http://lists.alioth.debian.org/pipermail/sane-devel/2006-May/016922.html<br>>>> it seems it is not possible to have something like<br>>>> -------------------------------------------------------------------<br>>>> #canon.conf<br>>>> scsi CANON<br>>>> scsi APPLE<br>>>> -------------------------------------------------------------------<br>>>> because it seems only the last entry "scsi APPLE" is used then.<br>>>><br>>>> According to my tests in<br>>>> http://lists.alioth.debian.org/pipermail/sane-devel/2006-May/016922.html<br>>>> it seems not to cause problems if devices are probed<br>>>> which are no scanners so that in the end our patch results<br>>>> an unrestricted plain "scsi" by default in /etc/sane.d/canon.conf<br>>>> -------------------------------------------------------------------<br>>>> # canon.conf<br>>>> #<br>>>> # Activate exactly one of the following choices:<br>>>> #<br>>>> # Probe on all /dev/sg* devices:<br>>>> scsi<br>>>> #<br>>>> # Probe for "CANON" on all /dev/sg* devices:<br>>>> #scsi CANON<br>>>> #<br>>>> # Probe only on one fixed device:<br>>>> #/dev/sg0<br>>>> -------------------------------------------------------------------<br>>>><br>>>> We have this since July 2006 and at least I noticed no bug reports<br>>>> or user complaints because of this - but I have no idea how many<br>>>> users use scanners which are supported by the "canon" backend.<br>>>><br>>>> By default we have all backends in /etc/sane.d/dll.conf disabled<br>>>> (to avoid that a SANE frontend lets various backends start up<br>>>> and do needless probing for devices which do not exist)<br>>>> so that the "canon" backend only runs for those users which<br>>>> actually use a matching scanner.<br>>>><br>>>><br>>>> Kind Regards<br>>>> Johannes Meixner<br>>>> --<br>>>> SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany<br>>>> AG Nuernberg, HRB 16746, GF: Markus Rex<br>>>><br>>>> --<br>>>> sane-devel mailing list: sane-devel@lists.alioth.debian.org<br>>>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel<br>>>> Unsubscribe: Send mail with subject "unsubscribe your_password"<br>>>> to sane-devel-request@lists.alioth.debian.org<br>>>><br>>><br>>><br>><br>><br>><br><br><br><br>-- <br>"The truth is an offense, but not a sin"<br><br>--<br>sane-devel mailing list: sane-devel@lists.alioth.debian.org<br>http://lists.alioth.debian.org/mailman/listinfo/sane-devel<br>Unsubscribe: Send mail with subject "unsubscribe your_password"<br> to sane-devel-request@lists.alioth.debian.org<br></jsmeix@suse.de></denis.prost@wanadoo.fr></blockquote></body></html>