[sane-devel] HP ScanJet 6200C timeout trouble

[m. allan noah]

On 12/30/07, m. allan noah <kitno455 at gmail.com> wrote:
> On 12/29/07, m. allan noah <kitno455 at gmail.com> wrote:
> > On 12/27/07, Thilo-Alexander Ginkel <maillist at tgbyte.com> wrote:
> > > Thilo-Alexander Ginkel wrote:
> > > > right now, I am struggling with getting my HP ScanJet 6200C (connected
> > > > via USB) to work reliably using SANE.
> > >
> > > Just a quick update: In order to make sure that the scanner hardware
> > > itself is not at fault, I installed the HP driver / scanner software in
> > > a Windows XP KVM (forwarding the USB device to the KVM), which worked
> > > perfectly, i.e. there is most likely nothing wrong with the hardware.
> > >
> >
> > well, i dusted off my ancient 6200C and tried it with current sane cvs- i get:
> >
> > ...
> > [hp] sane_start called
> > [hp] hp_GetOpenDevice: device libusb:003:006 is open with fd=0
> > [hp] Start downloading parameters to scanner
> > [hp] sanei_hp_optset_scan_type: scantype=0
> > [hp] scsi_flush: writing 2 bytes:
> > [hp]  0x0000  1B 45                                            .E
> > [hp] scsi_flush: writing 7 bytes:
> > [hp]  0x0000  1B 2A 73 32 35 37 45                             .*s257E
> > [hp] scl_inq: read failed (End of file reached)
> > [hp] scl_errcheck: Can't read SCL error stack: End of file reached
> > [hp] scsi_close: closing fd 0
> > [hp] hp_IsOpenFd: 0 is open
> > [hp] scsi_close: not closing. Keep open
> > [hp] sane_start will finish with Error during device I/O
> > scanimage: sane_start: Error during device I/O
> > ...
> >
> > which seems to be a failure even sooner than yours. i do not know for
> > sure if this thing works anymore, but it did when i last used it a
> > couple years ago. i dont have the docs or the time to dig into this,
> > but perhaps someone who knows SCL is listening?
> >
>
> and i just tried it on a 32 bit machine and it works just fine, unlike
> the 64 bit machine above. so perhaps it is a 32/64 bit issue. can you
> verify?
>

and now it seems to be working on 64 bit, even after a power cycle. i
dont know what the problem is/was. let us know if you can see any
pattern.

allan
-- 
"The truth is an offense, but not a sin"