[sane-devel] Mustek BearPaw 4800 TA Pro

2003-10-12 Thread Miroslav Jurkas
This is a cryptographically signed message in MIME format. --ms090408060704070901010207 Content-Type: multipart/mixed; boundary="040306080108010308030003" This is a multi-part message in MIME format. --040306080108010308030003 Content-Type: text/plain; charset

[sane-devel] Epson 1670 Driver Support

2003-10-12 Thread Joerg Skottke
Hi *, if anyone besides Oliver is interested, you can download a 6MB zipfile containing a b/w image + the corresponding usb-log created with sniffUSB.exe from here: http://www.gleitmeier.de/downloads/log.zip Joerg Joerg Skottke wrote: > Hi * (This time really *) ;) > > I have attached a logf

[sane-devel] Epson Perfection 1660 Photo

2003-10-12 Thread Karl Heinz Kremer
The log looks OK, this means that it is more likely that the problem really is in XSane. I have no idea why the scan gets cropped, this is also something that Oliver Rauch is in a better position to comment on. Karl Heinz On Sunday, October 12, 2003, at 08:13 PM, Terry Boldt wrote: > On Sun

[sane-devel] Epson Perfection 1660 Photo

2003-10-12 Thread Terry Boldt
On Sunday 12 October 2003 17:14, you wrote: > Terry, > > I'm still waiting for the log output with SANE_DEBUG_EPSON=3D128 Sorry. I got confused about what was wanted. I never saw your request for= the=20 sane log output and then received a request for the xsane log output. I just performed the t

[sane-devel] Epson Perfection 1660 Photo

2003-10-12 Thread Karl Heinz Kremer
[ Resent to the sane-devel list because moderator approval is required for emails this big - I've now removed the log file contents ] On Sunday, October 12, 2003, at 05:14 PM, Karl Heinz Kremer wrote: > Terry, > > I'm still waiting for the log output with SANE_DEBUG_EPSON=128 > > From the xsane

[sane-devel] Mustek 2400CU Plus

2003-10-12 Thread Henning Meier-Geinitz
Hi, On Sun, Oct 12, 2003 at 05:23:57PM -0200, shirshe...@freemail.lt wrote: > Oh shit. No, not everything's OK. After creating /dev/usbscanner0 scanimage > finds > my scanner, but when I try to scan, it prints: > scanimage: open of device gt68xx:/dev/usbscanner0 failed: Error during device > I/O

[sane-devel] Mustek 2400CU Plus

2003-10-12 Thread shirshe...@freemail.lt
This is a multi-part message in MIME format. ---=_post.5ci.lt3f8963fd Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Oh shit. No, not everything's OK. After creating /dev/usbscanner0 scanimage finds my scanner, but when I try to scan, it prints: scanimage: open of

[sane-devel] Mustek 2400CU Plus

2003-10-12 Thread shirshe...@freemail.lt
Hi again, I recompiled sane-backends and then tried 'SANE_DEBUG_GT68XX=255 scanimage -L'. Here's what I got: root:/usr/src/sources# SANE_DEBUG_GT68XX=255 scanimage -L [sanei_debug] Setting debug level of gt68xx to 255. [gt68xx] SANE GT68xx backend version 1.0 build 46 from sane-backends 1.0.12 [

[sane-devel] Mustek 2400CU Plus

2003-10-12 Thread Henning Meier-Geinitz
Hi, On Sun, Oct 12, 2003 at 01:46:38PM -0200, shirshe...@freemail.lt wrote: > I recompiled sane-backends and then tried 'SANE_DEBUG_GT68XX=255 scanimage > -L'. > Here's what I got: > > root:/usr/src/sources# SANE_DEBUG_GT68XX=255 scanimage -L > [sanei_debug] Setting debug level of gt68xx to 255.

[sane-devel] Mustek 2400CU Plus

2003-10-12 Thread Henning Meier-Geinitz
Hi, On Sat, Oct 11, 2003 at 11:33:53PM +0200, Linas Valiukas wrote: > Hello Henning, I'm cc'ing sane-devel again. > I'm using sane 1.0.12 Ok. > root:~# sane-find-scanner > found USB scanner (vendor=0x055f, product=0x021d [USB Scanner]) at > libusb:001:003 Looks fine. > root:~# SANE_DEBUG_GT