Oh & I forgot to mention - in the logs that 'beep' there's a return code (32772) from usbbulkread that says 'less data than requested returned'. In this case, 1 byte was requested and 0 returned..... log excerpt below shows what the backend does when this occurs.
[sanei_usb] sanei_usb_read_bulk: rc = 32772 [plustek] UIO error [plustek] Calibration file-name set to: [plustek] >E:\tcpipapp\home/.sane/Canon-N670U_N676U_LiDE20.cal< In the log without beeps - the rc=32772 doesn't occur, and there are an extra few usbbulkread/write's before the calibration file is set... Hope this helps it make more sense :) Paul Smedley wrote: > Hi All, > Wonder if anyone has any ideas on the semi-random LiDE20 hangs on OS/2. > > Most of the time - if I run scanimage -L it hangs scanimage.exe. When > it runs - I get a single beep out of the PC speaker, and looking at the > logs, scanimage has gone through all the backend exit routines. Usually, > unplugging the scanner will clear the scanimage -L hang. > > A sample log of this condition is at > http://smedley.info/lide20debugoutput-L-hang.txt > > Sometimes, scanimage -L will still give the beep, but not hang - sample > log at http://smedley.info/lide20debugoutput-L-beep-nohang.txt > > Finally, even rarer, sometimes scanimage -L doesn't beep at all, nor > does it hang - a log of this condition is at > http://smedley.info/lide20debugoutput-scan-good.txt > > Anyone have any clues at all? > > Cheers, > > Paul. >
