# Re: Problems with Acer ScanPrisa 640S

From: abel deuring (a.deuring@satzbau-gmbh.de)
Date: Sat Oct 21 2000 - 06:27:19 PDT

- Next message: Sebastien Sable: "Re: Problems with Acer ScanPrisa 640S"
  - Previous message: abel deuring: "Re: scanimage: open of device sharp-s:/dev/sg0 failed: Invalid argument"
  - In reply to: abel deuring: "Re: Problems with Acer ScanPrisa 640S"
  - Next in thread: cbagwell@sprynet.com: "Re: Re: Problems with Acer ScanPrisa 640S"
  - Maybe reply: cbagwell@sprynet.com: "Re: Re: Problems with Acer ScanPrisa 640S"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  I wrote:

  > Thus, there is no way to check in sanei_scsi.c or "below", if my
  > suspicion is right. But it could help to initialize pss->cmd in function
  > inquiry in snapscan-scsi.c to something else than zero. (Well, the CDB
  > should not be initialized with a non-zero value, but data block
  > following the CDB...)

  That's of course nosense. What I meant was to initialize the first
  pss->read_bytes bytes of pss->buf to something else than zero, before
  sanei_scsi_cmd is called in function inqiury in snapscan-scsi.c. If the
  command will return only 0x24 bytes with the atp870u driver, this will
  give at least a different error.

  Abel

      --
      Source code, list archive, and docs: http://www.mostang.com/sane/
      To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

  - Next message: Sebastien Sable: "Re: Problems with Acer ScanPrisa 640S"
  - Previous message: abel deuring: "Re: scanimage: open of device sharp-s:/dev/sg0 failed: Invalid argument"
  - In reply to: abel deuring: "Re: Problems with Acer ScanPrisa 640S"
  - Next in thread: cbagwell@sprynet.com: "Re: Re: Problems with Acer ScanPrisa 640S"
  - Maybe reply: cbagwell@sprynet.com: "Re: Re: Problems with Acer ScanPrisa 640S"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  This archive was generated by hypermail 2b29 : Sat Oct 21 2000 - 06:09:35 PDT