On Dienstag, 6. Februar 2001 22:15, you wrote:
> Hi Roy, Hi Oliver,
>
> I got the logfile from Oliver and discovered that the scanner returns
> unexpected data with the scsi_read_image_info command. Normally it gives
> back the width and height of the image to be scanned and the amount of data
> it will provide. But here it looks like the scanner simply returns the
> bytes it has recieved during the last command (scsi_set_window).
> By the way, have you modified the backend code? I would have expected that
> you get an error message because your model (model code 0x99) is not
> recognized by the backend.
case 0x99:
*model_string = "ScanMaker X6USB";
if ( md->revision == 1.00 )
md->model_flags |= MD_OFFSET_2;
md->model_flags |= MD_X6_SHORT_TRANSFER;
break;
This code is by John Fremlin originally and was incorporated in sane-1.0.3
> In fact I think there are two possibilities:
> a) Microtek again doesn't follow it's own standards with newer scanners and
> the scanner must be handled different from the others
> b) there is a problem with the sg / USB driver or interface
I think this is not the case, as this error is fully reproducible and seems
to be limited to this command only.
Furthermore it affects only two users with different kernel versions.
I myself can scan. I am attaching a log of a test which works.
> to make this clear it would be helpful to know about the communication with
> the scanner when scanning with Windows. I got my (SCSI-via-)parport scanner
> running with wine and was able to trace the data that was send via the ASPI
> interface. I don't know if it is possible with SCSI-via-USB.
That can't be done. Native windows can be snooped but I don't have windows.
Regards
Oliver Neukum
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Tue Feb 06 2001 - 14:22:13 PST