[sane-devel] Re: sane-devel digest, Vol 1 #103 - 13 msgs
Martin Pisz
pisz at primus.ca
Sun Dec 7 23:46:52 GMT 2003
Thanks you very much.
It should be noted that the Microtek E3 SCSI scanner with adaptec 2906
SCSI card requires the kernel to be recompiled without multiple LUN
support to work properly.
On Sat, 2003-12-06 at 10:25, sane-devel-request at lists.alioth.debian.org
wrote:
> Send sane-devel mailing list submissions to
> sane-devel at lists.alioth.debian.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> or, via email, send a message with subject or body 'help' to
> sane-devel-request at lists.alioth.debian.org
>
> You can reach the person managing the list at
> sane-devel-admin at lists.alioth.debian.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of sane-devel digest..."
>
>
> ______________________________________________________________________
> Today's Topics:
>
> 1. Epson perfection 1250 transparency adapter (Wai-Ming Ho)
> 2. Re: Snapscan on Mac OS X 10.3 (Henning Meier-Geinitz)
> 3. Re: Problems with old MUSTEK MFZ-06000CZ (Henning Meier-Geinitz)
> 4. MacOS X SCSI support updated in CVS (Henning Meier-Geinitz)
> 5. Re: You guys need information about HP Scanjet 3970? (Henning Meier-Geinitz)
> 6. Re: Problem with Xsane 0.91 and Mustek ScanExpress A3 USB (Henning Meier-Geinitz)
> 7. Re: [SANE2 proposal] Error handling (Henning Meier-Geinitz)
> 8. Microtek E3 scanner problem? (Martin Pisz)
> 9. Re: You guys need information about HP Scanjet 3970? (Oliver Putz)
> 10. Re: Microtek E3 scanner problem? (Henning Meier-Geinitz)
> 11. Re: Snapscan on Mac OS X 10.3 (=?ISO-8859-1?Q?R=E9mi_Zara?=)
> 12. Re: Visioneer Onetouch 4400 USB (Visioneer/Primax
> Primascan Colorado 2600u, Memorex 6142u) (m. allan noah)
>
> ______________________________________________________________________
> From: Wai-Ming Ho <melanoleuca at free.fr>
> To: sane-devel at lists.alioth.debian.org
> Subject: [sane-devel] Epson perfection 1250 transparency adapter
> Date: Sat, 06 Dec 2003 09:08:58 +0100
>
> Hi,
>
> Has anyone tried to force the transparency adapter to turn on during a normal
> scan ? I m thinking of scanning medium format negatives.
>
> While I m at it, would it also be possible to turn off the light of the
> scanning CCD ?
>
> The config files do not deal with these custom tweaks.
>
> regards,
> Wai-Ming
>
>
>
> ______________________________________________________________________
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> To: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] Snapscan on Mac OS X 10.3
> Date: Sat, 06 Dec 2003 12:19:23 +0100
>
> Hi,
>
> On Sun, Nov 30, 2003 at 01:46:37PM +0100, Rémi Zara wrote:
> > >Environment variable: SANE_DEBUG_SANEI_SOMETHING, e.g.
> > >SANE_DEBUG_SANEI_USB=255 or SANE_DEBUG_SANEI_SCSI=255.
> >
> > This is very interresting !
> > With SANE_DEBUG_SANEI_USB=255, scanimage -L finds my snapscan e40 !
> > Set it back to 0, and it does not find it anymore.
> > Set it back to 255, and here it is !
> > Either something's wrong with debugging, either there is maybe some
> > timing problems ?
>
> Usually that's a timinig issue. Maybe a problem in libusb?
>
> Bye,
> Henning
>
>
> ______________________________________________________________________
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> To: sane-devel at lists.alioth.debian.org <sane-devel at lists.alioth.debian.org>
> Subject: Re: [sane-devel] Problems with old MUSTEK MFZ-06000CZ
> Date: Sat, 06 Dec 2003 12:34:07 +0100
>
> Hi,
>
> On Tue, Dec 02, 2003 at 03:02:36PM +0100, Pekka K. Kurki wrote:
> > found SCSI scanner "MUSTEK MFC-06000CZ 1.02" at /dev/scanner
> > found SCSI scanner "MUSTEK MFC-06000CZ 1.02" at /dev/sg0
> > found SCSI scanner "MUSTEK MFC-06000CZ 1.02" at /dev/sga
>
> Both "sane-find-scanner" and "scanimage -L" have been run as the same
> user? Check permissions of /dev/sg0.
>
> > Now I don't know where to search any more. Unfortunately sane doesn't
> > produce any log/error files. Any ideas?
>
> Try "SANE_DEBUG_MUSTEK=255 scanimage -L". If that doesn't produce any
> output, the mustek backend is not loaded at all. If that happens, you
> can check by setting "SANE_DEBUG_DLL=255" why that happens.
>
> Bye,
> Henning
>
>
> ______________________________________________________________________
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> To: SANE Mailing List <sane-devel at lists.alioth.debian.org>
> Subject: [sane-devel] MacOS X SCSI support updated in CVS
> Date: Sat, 06 Dec 2003 14:39:30 +0100
>
> Hi,
>
> I've just appliead a patch for the SCSI support on MacOS X from
> Mattias Ellert to CVS. All MacOS X users please test if it compiles on
> your version of MacOS X and if it works.
>
> Either use CVS to get the latest code or wait one day and use one of
> the snapshots.
>
> I'll attach Mattias' mail to me as he can explain what he did much
> better :-)
>
> Bye,
> Henning
>
>
> Mattias Ellert <mattias.ellert at tsl.uu.se>:
> | I have now completed my efforts to get the autotools to configure the
> | Mac OS X scsi stuff.
> |
> | There are patches to two files. The first is in configure.in to make a
> | check for two different header files instead of one, so that the two
> | different APIs can be checked.
> |
> | The second one is sanei_scsi.c. Most changes are to remove the
> | OSX_ONLY_10_x_API symbols and replace them with the two new symbols
> | declared by autotools.
> |
> | With Mac OS X 10.3 there is a new feature in the linker that allows to
> | cross-compile for older versions of Mac OS X, provided you have the
> | correct SDKs installed. Some of the changes in the patch was made in
> | order to make the code compile with gcc 2.95.2, which is necessary for
> | doing a cross compilation for Mac OS X 10.1. With the patch the
> | compilation works, but since I don't have a computer running Mac OS X
> | 10.1 I haven't been able to verify that it runs. But at least it
> | compiles now.
> |
> | The kIOMasterPortDefault is not defined on Mac OS X 10.1 so I replaced
> | it with calls to IOMasterPort that works.
> |
> | I have also fixed bug #300317, by calling CFRelease on the created
> | CFStrings.
> |
> | This took a bit longer than I expected. The reason for this was mainly
> | the new cross compilation feature that required that I compiled
> | maciconv, gettext, libusb and sane-backends 3 times (for 10.1.5, 10.2.7
> | and 10.3.0) in order to test the three available cross compilation
> | SDKs.
> |
> | With the patches all three versions compile. The Mac OS X 10.3 version
> | runs. I can not test the other ones, since they were obtained using
> | cross compilation, and I don't have any computer running those versions
> | of Mac OS X to install on.
>
>
>
>
> ______________________________________________________________________
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> To: SaneDevel <sane-devel at lists.alioth.debian.org>
> Subject: Re: [sane-devel] You guys need information about HP Scanjet 3970?
> Date: Sat, 06 Dec 2003 16:13:57 +0100
>
> Hi,
>
> On Tue, Dec 02, 2003 at 10:36:21PM +0100, Ripper2004 at web.de wrote:
> > Hi, I bought a new Scanjet a few days ago, but did not check the
> > Linux compatibility. Now I know that it is not supported yet. On the
> > SANE Homepage I saw that there is already some Information about the
> > scanner. And before I spam the Mailing List with dozens of lines from
> > sane-find-scanner -v -v or cat /proc/bus/usb/devices I wanted to ask
> > if there is some requirement for this kind of information, or if it
> > would be redundant.
>
> As we already have the devices output it's not really necessary.
> Additional information may be useful hwoever. E.g. if the maunal
> and/or Windows drivers that came with the scanner mention other
> scanners (e.g. the 3500 sereies). Or, if you don't fear to open thed
> evice, what's printed on the chips.
>
> Bye,
> Henning
>
>
> ______________________________________________________________________
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> To: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] Problem with Xsane 0.91 and Mustek ScanExpress A3 USB
> Date: Sat, 06 Dec 2003 16:24:33 +0100
>
> Hi,
>
> On Sun, Nov 30, 2003 at 09:54:21PM +0100, Fabien3D wrote:
> > After several tests - and kicks at the back of my scanner - it finally works !
> > The problem came from a checked option by default : I don't know its original
> > translation, but it could be "Fast calibration". Both "Fast" and "High
> > Quality" Calibration were checked at the same time. Unchecking "Fast
> > calibration" allowed my scanner to work properly !
>
> The following options are available:
>
> * "Coarse calibration": If you disable this one, you must set offset
> and gain manually for each color.
> * "Coarse calibration for first scan only": That's just to make
> scanning a bit faster
> * "Quality calibration": That's the white calibration done for every
> pixel of the CCD/CIS sensor.
>
> Which one was it? Telling me the French name is also ok :-)
>
> Are the colors ok now? I.e. is red scanned as ed and there are no
> small horizontal stripes?
>
> Which version of sane are you using (scanimage --version)? The version
> of xsane is not that important.
>
> Bye,
> Henning
>
>
> ______________________________________________________________________
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> To: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] [SANE2 proposal] Error handling
> Date: Sat, 06 Dec 2003 16:57:38 +0100
>
> Hi,
>
> On Fri, Nov 28, 2003 at 06:12:19PM +0100, Julien BLACHE wrote:
> > Here's a proposal for SANE2 regarding error handling.
>
> This answer is not only for Julien, but concerns the whole thread.
>
> Please everyone reread the discussions on the error handling for sane2
> in the list archives. Most of this has already been discussed and it's
> not that easy unfortunately. I'll comment on some of the proposals only:
>
> > As of now, error
> > handling is somewhat imprecise and often not meaningful, and we're
> > spending everyone's time debugging problems that could be solved
> > quickly if only the user was given the appropriate status/error
> > message.
>
> I also propose to add more appropriate/detailed fixed error messages
> now. We don't even have "File not found". While this is easy, it's not
> that useful (which file hasn't been found?).
>
> > Proposal 1:
> > -----------
> >
> > Define SANE_Status as a struct :
> >
> > typedef struct {
> > int code;
> > char *msg;
> > } SANE_Status;
> >
> > SANE_Status.code is *always* a standard SANE status code.
> >
> > If SANE_Status.msg is NULL, then the standard SANE status message is
> > printed, end of the story.
> >
> > Otherwise, the custom SANE_Status.msg is printed, and the caller must
> > free SANE_Status.msg.
>
> First i thought that way may be troublesome with net/saned. But it may
> be possible as the struct can be transmitted as any other SANE
> structure. The net backend gets the string from saned and allocates
> memory on the client. saned frees the memory on the server immediately
> after copying the string over the net. The real backend frees the
> string taht was allocated by the net backend.
>
> Open questions: translation. Who translates such error messages? The
> backend or the frontend?
>
> I don't see any other problems with that proposal currently. i don't
> like the "backend frees" approach but that's probably the only one
> that works.
>
> > Proposal 2 (preferred) :
> > ------------------------
> >
> > Slightly redefine SANE_Status, as a 32bit integer where the 2 MSB are
> > a backend-specific error code and the 2 LSB are a standard SANE status
> > code.
> >
> > The 2 LSB will always correspond to a SANE status.
>
> That's ok.
>
> > If the 2 MSB are non-zero, they are passed to a sane_backend_status()
> > routine inside the backend that returns a proper status message that
> > is then echoed to the user. (depending on what we want to achieve,
> > we'd require the caller to free the message after use, think
> > sprintf(), etc...)
>
> That opens a can of worms. Which error message is printed? Remeber
> that more than one device can be open at the same time. In case of
> threads we are in trouble now. We also can't supply the SANE_Handle
> because otherwise we couldn't print errors before sane_open.
>
> If we used that proposal, we would have to disallow threaded
> frontends. Or to be more exact: disallow running more that one sane
> api function at the same time.
>
> The SANE option containing the error message has the same problem: It
> only works once sane_open succeeds and if the error doesn't occur in
> sane_control_option.
>
> I think returning the string at the exact time when the sane api
> function returns is the only way.
>
> And while defining structs keep in mind that the SANE standard only
> defines what a SANE_Word is. There is no "short" SANE_Type and it's
> also not defined that four SANE_Bytes are as long as one SANE_Word.
> SANE_Word may be 64 or even 128 bits.
>
> Bye,
> Henning
>
>
> ______________________________________________________________________
> From: Martin Pisz <pisz at primus.ca>
> To: sane-devel at lists.alioth.debian.org
> Subject: [sane-devel] Microtek E3 scanner problem?
> Date: Sat, 06 Dec 2003 09:48:24 -0700
>
> Hi
> I'm just a xsane user not a developer. I have a Microtek E3 SCSI
> Scanner hooked up to s Adaptec 2906 SCSI card. Mandrake 9.2 detects the
> scanner under xsane or Scannerdrake 20 times. The only difference is
> sg0-sg9 at the last line, whatever that means. Anyway, the light on the
> scanner blinks like 20 times when it's being detected. It used to blink
> only once before on
> Mandrake 9.0 during detection, when it was detected fine by the old
> version. When I try to preview or scan it starts scanning, but dies and
> crashes half way through scanning. Any ideas of how to solve the
> problem? Xsane worked awesome under Mandrake 8.1, worked fine under
> Mandrake 9.0 {Except it would no longer scan legal size-detection
> problem}. Unfortunately,Seems to not work at all under Mandrake 9.2.
> My system:
> AMD Duron 600
> Gigabyte zx7-1 VIA KT133 motherboard
> 3Com 5610 Hardware 56K modem
> SB Live value (OEM)
> Adaptec 2906 SCSI card
> Ps2 logitek wheelmouse and keyboard,
> USB Microsoft ForceFeedbak 2 Joystick
> A90 Viewsonic monitor
> A couple of serial connector for ti-83 calculator and sharp el6010
> organizer
>
> Thanks
> Martin
>
>
>
> ______________________________________________________________________
> From: Oliver Putz <Ripper2004 at web.de>
> To: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] You guys need information about HP Scanjet 3970?
> Date: Sat, 06 Dec 2003 17:58:13 +0100
>
> Henning Meier-Geinitz wrote:
>
> > E.g. if the maunal
> > and/or Windows drivers that came with the scanner mention other
> > scanners (e.g. the 3500 sereies).
>
> Well, the manual mentions some other scanners. There seems to be one manual for the following models:
>
> HP Scanjet 2400
> HP Scanjet 3670
> HP Scanjet 3690
> HP Scanjet 3970
>
> There are in fact several differences between the models which are named in the manual, (e.g. a button for creating a cd on the HP Scanjet 3970, or a special buit in Scanner for dias and negatives (all exept the HP Scanjet 2400) but nevertheless, I think that this is the one Manual given to every owner of one of the above mentioned scanners.
>
> HTH
>
> Oliver
> ______________________________________________________________________________
> WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und
> nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130
>
>
>
> ______________________________________________________________________
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> To: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] Microtek E3 scanner problem?
> Date: Sat, 06 Dec 2003 18:17:33 +0100
>
> Hi,
>
> On Sat, Dec 06, 2003 at 09:48:24AM -0700, Martin Pisz wrote:
> > I'm just a xsane user not a developer. I have a Microtek E3 SCSI
> > Scanner hooked up to s Adaptec 2906 SCSI card. Mandrake 9.2 detects the
> > scanner under xsane or Scannerdrake 20 times. The only difference is
> > sg0-sg9 at the last line, whatever that means.
>
> /dev/sg0 (1, 2 and so on) are the device files to access SCSI generic
> devices like scanners. Usually you use only one per device.
>
> Maybe Mandrake turned on "use multiple LUNs" in the Linux kernel? That
> may be necessary for some SCSI devices but makes trouble for others
> like this scanner. i don't know if you can turn off that function at
> run-time but you should at least find some hints on google.
>
> Bye,
> Henning
>
>
> ______________________________________________________________________
> From: Rémi Zara <remi_zara at mac.com>
> To: Henning Meier-Geinitz <henning at meier-geinitz.de>
> Cc: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] Snapscan on Mac OS X 10.3
> Date: Sat, 06 Dec 2003 18:20:44 +0100
>
>
> Le 6 déc. 03, à 12:19, Henning Meier-Geinitz a écrit :
>
> > Hi,
> >
> > On Sun, Nov 30, 2003 at 01:46:37PM +0100, Rémi Zara wrote:
> >>> Environment variable: SANE_DEBUG_SANEI_SOMETHING, e.g.
> >>> SANE_DEBUG_SANEI_USB=255 or SANE_DEBUG_SANEI_SCSI=255.
> >>
> >> This is very interresting !
> >> With SANE_DEBUG_SANEI_USB=255, scanimage -L finds my snapscan e40 !
> >> Set it back to 0, and it does not find it anymore.
> >> Set it back to 255, and here it is !
> >> Either something's wrong with debugging, either there is maybe some
> >> timing problems ?
> >
> > Usually that's a timinig issue. Maybe a problem in libusb?
> >
>
> Hi,
>
> The problem might indeed be in libusb, since I found that the debug
> level necessary to make it find my scanner is anything >= 5, which
> activates debugging in libusb:
>
> in sanei_usb_init (void)
>
> #ifdef DBG_LEVEL
> if (DBG_LEVEL > 4)
> usb_set_debug (255);
> #endif /* DBG_LEVEL */
>
> Regards,
>
> Rémi Zara
> --
> Rémi Zara
> http://www.remi-zara.net/
>
> ______________________________________________________________________
> From: m. allan noah <anoah at pfeiffer.edu>
> To: Keith Watson <kpwatson at ukfsn.org>
> Cc: Sane Developers <sane-devel at lists.alioth.debian.org>
> Subject: Re: [sane-devel] Visioneer Onetouch 4400 USB (Visioneer/Primax Primascan Colorado 2600u, Memorex 6142u)
> Date: Sat, 06 Dec 2003 12:24:05 -0500
>
> keith, i dont like snoopypro, i prefer either the original (non-pro) or
> even better, SniffUSB.exe v1.8 from
> http://benoit.papillault.free.fr/usbsnoop/index.php
>
> the latter is easier to install, and i like the debug log it makes better.
>
> you can cat the output from it into the attached perl script, which cleans
> things up some, though it does not deal with control packets fully...
>
> i usually work on adf scanners, which have alot of sensors and buttons,
> usually, so i test them by doing one thing at a time with a pause between
> each, ie: start sniffer, open lid, wait 15 seconds, close lid, wait, push
> paper sensor, wait, button1, wait, button2, etc. then i add paper to the
> scanner, and press the buttons again, etc.
>
> then you stare at the output for awhile, and try to find patterns.
>
> allan
>
> On Sat, 6 Dec 2003, Keith Watson wrote:
>
> > Ok, so I've grabbed a copy of SnoopyPro and installed it on Windows2000. I've
> > opened the TWAIN interface got the scanner to scan an image. SnoopyPro has
> > captured a load of things called URBs (what's a URB daddy?).
> >
> > Presumably I really should approach this methodically and perform a series of
> > smaller captures with each one addressing a specific operation. Is there any
> > material anywhere which covers this? Failing that is anyone able to mentor me
> > through this? e.g. suggest what operations I need to capture and in what order?
> >
> > If someone could tell me what to do, I could then post the output somewhere so
> > that others more knowledgeable and able than me can look at them and perhaps
> > deduce what's going on.
> >
> > Keith
> >
> >
More information about the sane-devel
mailing list