# Re: Mustek 1200 SP Pro + aha152x + linux 2.4.3 = success

From: Henning Meier-Geinitz (hmg-ml@gmx.de)
Date: Sun Apr 01 2001 - 12:16:38 PDT

- Next message: Novak Levente: "Re: Logs for Phantom 636cx"
  - Previous message: Ulrich Hopp: "Mustek 1200 SP Pro + aha152x + linux 2.4.3 = success"
  - In reply to: Ulrich Hopp: "Mustek 1200 SP Pro + aha152x + linux 2.4.3 = success"
  - Next in thread: Ulrich Hopp: "Re: Mustek 1200 SP Pro + aha152x + linux 2.4.3 = success"
  - Reply: Ulrich Hopp: "Re: Mustek 1200 SP Pro + aha152x + linux 2.4.3 = success"
  - Reply: Ulrich Hopp: "Re: Mustek 1200 SP Pro + aha152x + linux 2.4.3 = success"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  Hi,

  On Sun, Apr 01, 2001 at 06:12:33PM +0200, Ulrich Hopp wrote:
  > SuSE 7.1
  > aha1505
  > Mustek 1200 SP PRO + TA
  > kernel version 2.4.3
  > aha152x driver delivered with kernel version 2.4.3
  > cvs Tree version 1.11 but (!!) Mustek backend version 1.0.104
  >
  > some notes
  >
  > kernel 2.4.3 + kernel 2.2.16:
  >
  > CVS Tree 1.11 + Mustek backendversion 1.0.105 (as delivered with the CVS )
  > doesn't work for me. The scanner tries to scan beyond the physical scanarea.

  I'm using Linux 2.2.18 at the moment with an Adaptec 2940. My scanner
  doesn't scan beyond the physical scan area at least not in the modes I
  tried. What did you do exactly? A preview scan or a full size scan?
  In which resolution and mode?

  I'm asking all these questions because I don't think I have changed
  anything concerning the Pro scanner between 104 and 105. But you never
  know...

  > To use the TA I had to hardcode the TA_flag in the sources. It seems, that
  > there is no special byte for the TA in the result string. But I may be wrong.

  It's not in the inquiry information like for the other Mustek scanners
  but you can get the information from a "request sense" command. If a
  TA is present, byte 2 of the sense buffer is 0x40, otherweise it's 0.
  I have implemented that in my code but I'm not sure if it works. I
  think I sent you the source some hours ago. If it doesn't work because
  of the other problems maybe you can extract the detection cahnges and
  try them in 104.

  > If I use the 36 bit option it only works if I start xscanimage directly (
  > e.g. from a terminal box). Then the image is put directly into a file.
  >
  > Scanning with 36 bit with xscanimage as a gimp-plugin results in a KDE error
  > message, which says that KDE can't handle the output. ( may be due to my KDE
  > configuration)

  GIMP can't handle more than 8 bit/color. But you shouldn't get a
  message from KDE but from xsane.

  > kernel 2.2.17 - 2.2.19 :
  >
  > system hangs if I try scanning with the option quality calibration.

  This doesn't happen here. Maybe this one and the "out of scan area"
  problem are related to SCSI driver bugs? Can you test this with a
  different SCSI controller?

  Thanks for the report.

  Bye,
  Henning

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

  - Next message: Novak Levente: "Re: Logs for Phantom 636cx"
  - Previous message: Ulrich Hopp: "Mustek 1200 SP Pro + aha152x + linux 2.4.3 = success"
  - In reply to: Ulrich Hopp: "Mustek 1200 SP Pro + aha152x + linux 2.4.3 = success"
  - Next in thread: Ulrich Hopp: "Re: Mustek 1200 SP Pro + aha152x + linux 2.4.3 = success"
  - Reply: Ulrich Hopp: "Re: Mustek 1200 SP Pro + aha152x + linux 2.4.3 = success"
  - Reply: Ulrich Hopp: "Re: Mustek 1200 SP Pro + aha152x + linux 2.4.3 = success"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  This archive was generated by hypermail 2b29 : Sun Apr 01 2001 - 13:59:09 PDT