Hi,
On Thu, Feb 20, 2003 at 10:17:36AM -0600, Ted Drude wrote:
> I do a SANE_DEBUG_PLUSTEK=255 scanimage -L and here is the relevant output:
>
> [plustek] attach (/dev/usb/scanner0, 0xbfffd340, (nil))
[...]
> [plustek] usbDev_close() [plustek] attach: model = >TravelScan 464<
> [plustek] sane_g
Hi,
> What does happen when you try to scan?
The scanner makes some noise, seems to "light up" inside, then feeds an
A4-size paper sheet about 1/3 of the way through..then tries to reverse it
a bit, then finally quits.
I guess the driver is assuming this is a flatbed, so it's "seeking" the XY
OK, thanks for the advice!
I fixed up the /etc/sane.d/plustek.conf and the "plustek-devs.c" files so
the ID strings now match.
Did a make and make install. I also fixed the ID problem I had in the
/etc/modules.conf file.
I do a SANE_DEBUG_PLUSTEK=255 scanimage -L and here is the relevant out
Hi,
On Wed, Feb 19, 2003 at 11:51:35AM -0600, t...@hhsys.org wrote:
> Here is the output with the Syscan TravelScan 464 connected:
>
> T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=0a82 ProdID=4600 Rev
>Can you please show us the ouput of "cat
/proc/bus/usb/devices" when
>both scanners are connected?
Here is the output with the Syscan TravelScan 464 connected:
# cat /proc/bus/usb/devices
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso
