--Boundary-00=_QDn1Cp0H087tSdX
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Thursday 14 July 2005 14:58, Olaf Leidinger wrote:
> Hallo!
>
> > that's because the device-id is not known by the backend.
> > If you want to, I can create a patch, which needs to be applied to the
> > latest CVS-version of SANE. Then recompile and install the stuff to
> > see if it works.
>
> Okay, great! But I can test it soonest on saturday, as I'm currently not at
> home. ;-(
Here you are,
apply the patch, recompile install and see what happens.
I assume, that the device is more or less a LiDE30...
If all that fails, we need to check the USB-logs from a Windoze installation.
Good luck
Gerhard
--Boundary-00=_QDn1Cp0H087tSdX
Content-Type: text/x-diff;
charset="iso-8859-1";
name="lide25.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="lide25.patch"
--- sane-backends/backend/plustek-usb.c.orig 2005-07-05 08:58:24.000000000
+0200
+++ sane-backends/backend/plustek-usb.c 2005-07-14 13:37:35.000000000 +0200
@@ -1094,7 +1094,8 @@ static int usbDev_Prepare( Plustek_Devic
/* the CanoScan CIS devices need special handling... */
if((dev->usbDev.vendor == 0x04A9) &&
(dev->usbDev.product==0x2206 || dev->usbDev.product==0x2207 ||
- dev->usbDev.product==0x220D || dev->usbDev.product==0x220E)) {
+ dev->usbDev.product==0x220D || dev->usbDev.product==0x220E ||
+ dev->usbDev.product==0x2220)) {
use_alt_cal = SANE_TRUE;
} else {
--- sane-backends/backend/plustek-usbdevs.c.orig 2005-07-05
08:58:24.000000000 +0200
+++ sane-backends/backend/plustek-usbdevs.c 2005-07-14 13:36:45.000000000
+0200
@@ -2348,6 +2348,7 @@ static SetDef Settings[] =
{"0x04A9-0x2208", &Cap0x04A9_0x2208, &Hw0x04A9_0x2208, "D660U"
},
{"0x04A9-0x220D", &Cap0x04A9_0x220D, &Hw0x04A9_0x220D,
"N670U/N676U/LiDE20" },
{"0x04A9-0x220E", &Cap0x04A9_0x220E, &Hw0x04A9_0x220E,
"N1240U/LiDE30" },
+ {"0x04A9-0x2220", &Cap0x04A9_0x220E, &Hw0x04A9_0x220E, "LiDE25"
},
/* Please add other devices here...
* The first entry is a string, composed out of the vendor and product
id,
--Boundary-00=_QDn1Cp0H087tSdX--
