[sane-devel] Progress on HP ScanJet 4600?

[Ethan Glasser-Camp]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig2BC8D2E955A606096C4BE02B
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thank you for your rapid response! (Sorry I didn't do as well regarding
timeliness.)

Bertrik Sikken wrote:
> The scanner search engine at sane-project.org has some info on the USB
> configuration of this device and even a link to an USB log.
> I'll have a look at the log.

I had a look at it too. Of course, I didn't get much out of it, because 
  I didn't know what I was looking for.

> It may help to check the .inf file in the windows driver package and
> see if any other scanners besides the 4600 are supported by that driver.

I looked at the inf file, and if I'm reading it right, there's no other
scanners supported by it. I'm not sure how much of the file I can
actually reference in this email without violating copyright, but I
think the only models of scanner mentioned in it are the HP4600.

> If you're really courageous, you can open the scanner and take note
> of the chips inside it.

I don't have access to the scanner, and my friend (who does) isn't quite
brave enough. If I get access to the hardware later, I'll certainly let
you know, but it seems unlikely yet.

On the subject of reverse-engineering the driver -- I understand that I
have no experience with this sort of thing at all, so feel free to say,
"No, that's hopelessly naive" -- but since there *is* a USB log, can't
we just pluck out bits and pieces of it and try to send them to the
scanner and see what happens, and reverse-engineer it that way? Some
brittle shell script or something that scans something sometimes would
certainly be a first step. (Of course, it would be hard to progress past 
  that with only one USB log, wouldn't it?)

Thanks again for your time.
-- 
Ethan Glasser-Camp, self-styled Computersman


--enig2BC8D2E955A606096C4BE02B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBWijbhRlgoLPrRPwRAi3UAJ9tcyvTqU9tPhJKhVp7UZOaIzz2jACeIGrR
miEb92AW/ap+JmuhNEZoexI=
=nIer
-END PGP SIGNATURE-

--enig2BC8D2E955A606096C4BE02B--

[sane-devel] Problems with Canon 2700

[Thomas Loescher]

On Tue, 28 Sep 2004 22:37:27 +0900
"mitsuru okaniwa"  wrote:

> Dear Thomas,
> Thank you very much for your useful try!

Dear Mitsuru,
Thank you for helping me trying it ;-)

...
> In these test case, I recommend you to edit Makefile(it is in directory of
> /sane-backends-1.0.XX/backend/) after did "configure", as follows;
...
> 
> I could compile the sane different version test (case1. and case2.) by the
> above way on my Linux.
> If you will have the compile error again, would you send me the error
> massage of your compiler?
> 
With your help to edit the Makefiles I also could compile these two testcases.
Case 1 (copy canon.c, canon.h, canon-scsi.c, canon-sane.c and sanei_backend.h 
rom sane-backend-1.0.14 to sane-backend-1.0.11)

But the scan error still exist 

Case 1 (copy canon.c, canon.h, canon-scsi.c, canon-sane.c and sanei_backend.h 
rom sane-backend-1.0.11 to sane-backend-1.0.14)

This test gave me success!
Scanning works fine!

Thank you

> > > The next test is
> > > 3. copying only "sanei_scsi.c" file from sane-backend-1.0.11 into the
> > > backend-1.0.14 and tried to compile the backend-1.0.14, install and test
> > > Of course, canon files used are newest in sane-backend-1.0.14.
> > >
> > > "sanei_scsi.c" file is in directory of /sane-backends-1.0.XX/sanei/.
> > > "sanei_scsi.c" was added some change around "sanei_scsi_req" between
> > > sane1.0.11 and sane1.0.13.
> > >
> > Compiling was succesfully, but whan I try to scan, same behavior as in
> sane-backends above 1.0.11
> > I mean, no success :-(
> 
> Would you do "make clean" and "make" and "make install" again?
>

Tried it again,
Still no success

Thank you for not giving up! 

Any Ideas howto proceed?

Best regards

Thomas Loescher

[sane-devel] Troubles with sniffusb 1.8

[svo...@wanadoo.fr]

Hello,

I'm using sniffusb-1.8 to log the data flow for a Medion MD6471, and 
ran into a couple of issues:

- first, logs show some messages like
*** non printable URB with function code 0x1004 
or 
*** non printable URB with function code 0x1003 
as anwsers to URB_FUNCTION_ABORT_PIPE.

Did anyone allready noticed such a thing ?

- second, I get allocation errors which leads to incomplete 
buffer dumps (see 'myAllocationFailed'):
[79468 ms] UsbSnoop - RemoveDevice(ff1ca6f0) : fido=c1612bc8 
pdx=c1612c80
[79468 ms] UsbSnoop - DriverUnload(ff1ca640) : DriverObject c1603ad8, 
IRQL=0
[79468 ms] Driver unloaded!
MyThreadFunction : myMsgCount=7639 myMaxSemaphoreCount=9 myMaxIrql=2, 
myAllocationFailed=10732, mySemaphoreFailed=0

Did anyone get into this ?

- last, I see that that the usbsnoop.log isn't used directly, but 
parsed with some awk scripts. Would it be worth to have a 
modified version of sniffusb to output in 'the right format'
directly ?

Regards,
Stef

[sane-devel] plustek 100 parallel scanner

[Jude DaShiell]

First does sane run this scanner with sane-plustek-pp?  If so, I think I 
need some configuration lines and commands I can use to make this 
paperweight wake up.  I use the command line interface and will continue 
to do so until I find out how to get X to work on this Fedora Core 2 
system and get gnopernicus talking.  The scanner is on lp0 0x378 now.

[sane-devel] HP Scanjet 3670

[ander...@novalinux.com.br]

Hi,

I'm new here but I have been reading this list in the past week to see if
I can find the solution to my problem (a big one).

my name is Anderson and I'm from Brasil. (sorry by my English)

I'm migrating all M$ Windows for LINUX in a football club (soccer team)
but I'm stuck in this HP SCANJET 3670!!!

Did any one get this thing work on Linux???

I contact the HP in USA but whithout no result, just the promess of "the
driver is being developed by our engineers and as soon it is done it'll be
in the homepage"

Well, I can't wait. so, if any one can help, please, I'll be all ears, I
mean, eyes...hehe

I'm also trying to get in toucth with some one in HP that I think he may
help.

I am not a developer, I am consultant of computer science and free software.
but I can understand codes, so, if you need me, I'll be here.


Thank's.

Anderson Alipio
ander...@novalinux.com.br

[sane-devel] sane-find-scanner finds Lide20, plustek backend does not

[Lloyd Sumpter]

Gerhard Jaeger wrote:
> Hi,
> 
> On Thursday 23 September 2004 18:42, Lloyd Sumpter wrote:
> 
>>Hi,
>>
>>My Canon Lide20 (USB) was working on Mandrake 9.0 (sane 1.0.11, iirc and
>>Linux 2.4.x) using scanner.o. I upgraded to Mandrake 10.0 (sane 1.0.13,
>>Linux 2.6.3) and I found scanner.o has been discontinued, and I have to
>>use libusb. Sane tells me the scanner is supported with plustek backend.
>>



>>I took the vender and product IDs from sane-find-scanner and made
>>plustek.conf as:
>>
>>[usb] 0x04a9 0x220d
>>device auto
> 
> 
> Go and try
> [usb]
> device auto
> 

Tried it. Same result.

> If the problems still exist, send us the output of the following:
> export SANE_DEBUG_SANEI_USB=255 ; export SANE_DEBUG_PLUSTEK=20 ; scanimage -L
> 
> and
> 
> ls -l /proc/bus/usb/001/
> 
Thanks for the help! Still doesn't work, Here's the result of the ls:

[root@druid root]# ls -l /proc/bus/usb/001/
total 0
-rw-rw  1 lsumpter usb 43 Sep 23 17:28 001
-rw-rw  1 lsumpter usb 57 Sep 23 17:28 002
[root@druid root]# ls -l /proc/bus/usb/002/
total 0
-rw-rw  1 lsumpter usb 43 Sep 23 17:28 001
-rw-rw  1 lsumpter usb 43 Sep 22 21:34 002

(Scanner is on Bus=01 Lev=01)

And here is the DEBUG output:

[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such device
[sanei_usb] sanei_usb_init: found 0 devices
[sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0230
[sanei_usb] sanei_usb_open: trying to open device `/dev/usbscanner'
[sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner' in list
[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such device
[sanei_usb] sanei_usb_init: found 0 devices
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x1a20
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x1a26
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x2022
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x1a2a
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x2040
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x2060
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x207e
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x20c0
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x20b0
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x20de
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x20fc
[sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x20fe
[sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x0002
[sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x0001
[sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x2061
[sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x2093
[sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x2091
[sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x2095
[sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x2097
[sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x208d
[sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x20ff
[sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x208f
[sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x20fd
[sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0114
[sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x011f
[sanei_debug] Setting debug level of plustek to 20.
[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such device
[sanei_usb] sanei_usb_init: found 0 devices
[plustek] Plustek backend V0.46-9, part of sane-backends 1.0.13
[plustek] ># Plustek-SANE Backend configuration file<
[plustek] ># For use with LM9831/2/3 based USB scanners<
[plustek] >#<
[plustek] ><
[plustek] >[usb] 0x04a9 0x220d<
[plustek] section contains no device name, ignored!
[plustek] next device is a USB device (0x04A9-0x220D)
[plustek] ... next device
[plustek] >device auto<
[plustek] Decoding device name >auto<
[plustek] ><
[plustek] ><
[plustek] ><
[plustek] ><
[plustek] ><
[plustek] attach (auto, 0xbfffc670, (nil))
[plustek] Device configuration:
[plustek] device name  : >auto<
[plustek] USB-ID   : >0x04A9-0x220D<
[plustek] warmup   : -1s
[plustek] lampOff  : -1
[plustek] lampOffOnEnd : yes
[plustek] cacheCalData : no
[plustek] altCalibrate : no
[plustek] skipCalibr.  : no
[plustek] skipFine : no
[plustek] skipFineWhite: no
[plustek] invertNegs.  : no
[plustek] pos_x: 0
[plustek] pos_y: 0
[plustek] pos_shading_y: -1
[plustek] neg_x: 0
[plustek] neg_y: 0
[plustek] neg_shading_y: -1
[plustek] tpa_x: 0
[plustek] tpa_y: 0
[plustek] tpa_shading_y: -1
[plustek] red gain : -1
[plustek] green gain   : -1
[plustek] blue gain: -1
[plustek] red Gamma: 1.00
[plustek] green Gamma  : 1.00
[plustek] blue Gamma   : 1.00
[plustek] gray Gamma   : 1.0

[sane-devel] Problems with Canon 2700F

[mitsuru okaniwa]

This is a multi-part message in MIME format.

--Boundary_(ID_q+v0ypq2c7wkxfpb0OuFfw)
Content-type: text/plain; charset=iso-2022-jp
Content-transfer-encoding: 7BIT

Dear Thomas,
Thank you very much!
- Original Message - 
From: "Thomas Loescher" 
To: "mitsuru okaniwa" 
Cc: "Ulrich Deiters" 
Sent: Monday, September 27, 2004 8:03 AM
Subject: Re: [sane-devel] Problems with Canon 2700F


> Only a short reply (iT's quite late I and should go to bed soon)
> I tried both ways as you recommended:
>
> > Well, Thomas, would you test again?
> > Now, overwrite canon-backend(canon.c, canon.h, canon-sane.c,
canon-scsi.c)
> > in sane1.0.14 to sane1.0.11, and check if the sane1.0.11 will work well.
> > And overwrite canon-backend(canon.c, canon.h, canon-sane.c,
canon-scsi.c) in
> > sane1.0.11 to sane1.0.14, and check if the sane1.0.14 will work well.
>
> 1. copying the canon files from sane-backend-1.0.11 into the
backend-1.0.14 and tried to compile... it failed due compile errors
> 2. copying the canon files from sane-backend-1.0.14 into the
backend-1.0.11 and tried to compile... it failed due compile errors

Ok, would you overwrite /sane-backends-1.0.XX/include/sane/sanei_backend.h
too?
So,
1. copying the canon files and "sanei_backend.h" file from
sane-backend-1.0.11 into the backend-1.0.14 and tried to compile the
backend-1.0.14, install and test
2. copying the canon files and "sanei_backend.h" file from
sane-backend-1.0.14 into the backend-1.0.11 and tried to compile the
backend-1.0.11, install and test

I think that case1. will not work well and case2. will work well
The reason I think is that a cause of this problem will be in sanei_scsi.c
and so on but not canon-backend files.

The next test is
3. copying only "sanei_scsi.c" file from sane-backend-1.0.11 into the
backend-1.0.14 and tried to compile the backend-1.0.14, install and test
Of course, canon files used are newest in sane-backend-1.0.14.

"sanei_scsi.c" file is in directory of /sane-backends-1.0.XX/sanei/.
"sanei_scsi.c" was added some change around "sanei_scsi_req" between
sane1.0.11 and sane1.0.13.

> P.S. It seems, it's going to a kind of personal mail traffic... Should I
send my experiences to the mailing list, too?
> Now I have Ullrich (hello ;-)) in the cc-field. Who should also go into
the cc-field?

Ulrich Deiters and Abel Deuring are great developers for canon-backend, I
think.

Best regards,

mitsuru okaniwa

--Boundary_(ID_q+v0ypq2c7wkxfpb0OuFfw)
Content-type: text/html; charset=iso-2022-jp
Content-transfer-encoding: 7BIT








Dear Thomas,Thank you 
very much!- Original Message - From: "Thomas Loescher" 
mailg...@gmx.de>To: "mitsuru okaniwa" 
m-okan...@bea.hi-ho.ne.jp>Cc: "Ulrich 
Deiters" u...@xenon.pc.uni-koeln.de>Sent: Monday, 
September 27, 2004 8:03 AMSubject: Re: [sane-devel] Problems with Canon 
2700F> Only a short reply (iT's quite late I and should go to 
bed 
soon)> I tried both ways as you recommended:>> > Well, 
Thomas, would you test again?> > Now, overwrite 
canon-backend(canon.c, 
canon.h, canon-sane.c,canon-scsi.c)> > in sane1.0.14 to 
sane1.0.11, and check if the sane1.0.11 will work well.> > And 
overwrite canon-backend(canon.c, canon.h, canon-sane.c,canon-scsi.c) 
in> > sane1.0.11 to sane1.0.14, and check if the sane1.0.14 will work 
well.>> 1. copying the canon files from sane-backend-1.0.11 into 
thebackend-1.0.14 and tried to compile... it failed due compile 
errors> 2. copying the canon files from sane-backend-1.0.14 into 
thebackend-1.0.11 and tried to compile... it failed due compile 
errorsOk, would you overwrite 
/sane-backends-1.0.XX/include/sane/sanei_backend.htoo?So,1. copying 
the canon files and "sanei_backend.h" file fromsane-backend-1.0.11 into the 
backend-1.0.14 and tried to compile thebackend-1.0.14, install and 
test2. copying the canon files and "sanei_backend.h" file 
fromsane-backend-1.0.14 into the backend-1.0.11 and tried to compile 
thebackend-1.0.11, install and testI think that case1. will not 
work 
well and case2. will work wellThe reason I think is that a cause of 
this 
problem will be in sanei_scsi.cand so on but not canon-backend 
files.The next test is3. copying only "sanei_scsi.c" file from 
sane-backend-1.0.11 into thebackend-1.0.14 and tried to compile the 
backend-1.0.14, install and testOf course, canon files used are newest in 
sane-backend-1.0.14."sanei_scsi.c" file is in directory of 
/sane-backends-1.0.XX/sanei/."sanei_scsi.c" was added some change around 
"sanei_scsi_req" betweensane1.0.11 and sane1.0.13.> P.S. It 
seems, it's going to a kind of personal mail traffic... Should Isend my 
experiences to the mailing list, too?> Now I have Ullrich (hello ;-)) in 
the cc-field. Who should also go intothe cc-field?Ulrich Deiters 
and 
Abel Deuring are great developers for canon-backend, Ithink.Best 
regards,mitsuru okaniwa

--Boundary_(ID_q+v0ypq2c7wkxfpb0OuF