# Re: [snapscan] Problem with 2.4.0-test10 and AGFA SnapScan 1236S

From: Lawrence Glaister (lg@jfm.bc.ca)
Date: Mon Nov 06 2000 - 16:19:27 PST

- Next message: Russ Burdick: "Re: [snapscan] Problem with 2.4.0-test10 and AGFA SnapScan 1236S"
  - Previous message: Henning Meier-Geinitz: "Re: detection problem"
  - In reply to: Timothy Little: "Re: [snapscan] Problem with 2.4.0-test10 and AGFA SnapScan 1236S"
  - Next in thread: Russ Burdick: "Re: [snapscan] Problem with 2.4.0-test10 and AGFA SnapScan 1236S"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  I dont have a 2.2 system at the moment. But I have noticed occasional
  problems
  when scanning subsections of the entire scanner area. It is quite possible
  that we
  may need to limit sizes to multiples of 8 or 16 pixels... This is a total
  guess, but
  could explain some of the odd scans I have seen. I haven't looked at the
  interaction
  between xscanimage or xsane and the backend.... I'm not sure if the
  restriction
  could be put in the backend (may need zero fills to pad to frontend
  requested
  size) or in the frontend by letting the user only select particular size
  areas.
  Glad to see so much activity on the snapscan backend.
  =======================================================
  Lawrence Glaister VE7IT email: lg@jfm.bc.ca
  1462 Madrona Drive http://jfm.bc.ca
  Nanoose Bay BC Canada
  V9P 9C9
  =======================================================
  ----- Original Message -----
  From: Timothy Little <tim@lilly-villa.little-possums.net>
  To: <sane-devel@mostang.com>
  Sent: Monday, November 06, 2000 1:13 PM
  Subject: Re: [snapscan] Problem with 2.4.0-test10 and AGFA SnapScan 1236S

  > On Mon, Nov 06, 2000 at 06:06:48PM +0100, Sebastien Sable wrote:
  >
  > > Could someone with one of those snapscan scanners not perfectly
  > > working with 2.4-test try a 2.2 kernel (Timothy, Chris, Lawrence ?)?
  >
  > OK, just tried it out. The previously-reported problem is perfectly
  > replicated in 2.2.15 with USB backport. Every res/width combination
  > working in 2.4.0-test9 works in 2.2.15+usb, and every failure fails in
  > both.
  >
  > Looks very much like a problem in the backend somewhere. Of course,
  > it could also be a problem with the scanner capabilities, one that is
  > worked around by Agfa's Windows driver :^)
  >
  >
  > > Agfa 1212U
  > > SNAPSCAN 1212U
  > > Works sometime (but fails sometime?)
  >
  > 2.2.15 +USB, 2.4.0-test9
  >
  > > 600dpi
  > > SNAPSCAN600P
  >
  >
  > - Tim
  >
  > --
  > Source code, list archive, and docs: http://www.mostang.com/sane/
  > To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
  >

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

  - Next message: Russ Burdick: "Re: [snapscan] Problem with 2.4.0-test10 and AGFA SnapScan 1236S"
  - Previous message: Henning Meier-Geinitz: "Re: detection problem"
  - In reply to: Timothy Little: "Re: [snapscan] Problem with 2.4.0-test10 and AGFA SnapScan 1236S"
  - Next in thread: Russ Burdick: "Re: [snapscan] Problem with 2.4.0-test10 and AGFA SnapScan 1236S"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  This archive was generated by hypermail 2b29 : Mon Nov 06 2000 - 16:14:23 PST