From svoltz@wanadoo.fr  Fri Oct  1 05:27:33 2004
From: svoltz@wanadoo.fr (svoltz@wanadoo.fr)
Date: Fri, 1 Oct 2004 06:27:33 +0200
Subject: [sane-devel] umax_pp slow
In-Reply-To: <415C7DD3.3090102@kc.rr.com>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com>
Message-ID: <20041001042733.GA2166@wanadoo.fr>

On Thu, Sep 30, 2004 at 04:42:43PM -0500, Joe Henley wrote:
> Stef,
> 
> Thanks very much for your reply.  I changed my umax_pp.conf file to read:
> -------------------------------
> option buffer 8388608
> port 0x378
> option astra 2000
> 
> Then I ran the export command, then the scanimage command.  The log 
> contents are:
> -------------------------------------------------------------
> [sanei_debug] Setting debug level of umax_pp_low to 1.
> [umax_pp_low] SANE_INB level 3
> [umax_pp_low] sanei_umax_pp_InitPort(0x378,)
> [umax_pp_low] sanei_ioperm(0x378, 8, 1) OK ...
> [umax_pp_low] UMAX Astra 1220/1600/2000 P ASIC detected (mode=31)
> [umax_pp_low] registerRead, found 0xFF expected 0x00 (umax_pp_low.c:6633)

	Weird, your paralle port can't do EPP when used directly, while it
works with ppdev.

> [umax_pp_low] *** It appears that EPP data transfer doesn't work    ***
> [umax_pp_low] *** Please read SETTING EPP section in sane-umax_pp.5 ***
> [umax_pp_low] Hardware can't do ECP, giving up (umax_pp_low.c:6856) ...
> [umax_pp_low] No EPP or ECP mode working, giving up ... (umax_pp_low.c:7475)
> 
> The results surprised me.  I ran ppdiag to check and got:
> ---------------------------------------------------
> S01: parport built as module
> S02: parport0:
> S02:    modes:PCSPP,TRISTATE,EPP
> S02:    ADDR :0x378
> S02:    IRQ  :no IRQ used
> S02:    DMA  :no DMA used
> S03: no parport parameters
> S10: ppdev built as module
> S12: /dev/parport0 exists ...
> S12: /dev/parport0 is readable ...
> S12: /dev/parport0 is writable ...
> successfull end ....
> 
> I double checked my BIOS and it's set to EPP, port 378 and IRQ 7.
> 
> So now I'm really stumped.  Please point me in the right direction.
> 
> If it's relevant:  using RedHat 9, kernel is 2.4.20-20.9, xsane is 
> version 0.96, sane-backend is: 1.0.14 with the 6.3 patch for umax_pp, 
> mobo is an Intel 875PBZ.
> 
> Joe
> 
> PS:  Sorry about RoadRunner blocking your replies.  I don't know why.

	Try tweaking the parport parameters in /etc/modules.conf :

alias parport_lowlevel parport_pc
options parport_pc io=0x378 io_hi=0x778 irq=7 dma=none

	Another thing to try is to check is the kernel you use is
compiled with the followwing options in 'Parallel port support':

    <M> Parallel port support
    <M> PC-style hardware
    < > Multi-IO cards (parallel and serial)
    [*] Use FIFO/DMA if available (EXPERIMENTAL)
    [*] SuperIO chipset support (EXPERIMENTAL)
    < > Support for PCMCIA management for PC-style ports
    [ ] Support foreign hardware
    [*] IEEE 1284 transfer modes 

	What other parallel port BIOS setting do you have ?

Regards,
	Stef


From gerhard@gjaeger.de  Fri Oct  1 07:49:00 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Fri, 1 Oct 2004 08:49:00 +0200
Subject: [sane-devel] sane-find-scanner finds Lide20, plustek backend does not
In-Reply-To: <415C3AA4.7020508@lynx.net>
References: <4152FD0F.6070103@lynx.net> <20040929162241.GA8559@meier-geinitz.de> <415C3AA4.7020508@lynx.net>
Message-ID: <200410010849.00927.gerhard@gjaeger.de>

On Thursday 30 September 2004 18:56, Lloyd Sumpter wrote:
> Henning Meier-Geinitz wrote:
> > Hi,
> >
> > On Tue, Sep 28, 2004 at 01:22:01PM -0700, Lloyd Sumpter wrote:
> >>[sanei_debug] Setting debug level of sanei_usb to 255.
> >>[sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such
> >> device [sanei_usb] sanei_usb_init: found 0 devices
> >
> > Oh. That means that SANE isn't built with libusb support. It only
> > searches for /dev/usb/ but not for libusb devices.
>
> Ah...THAT would explain a lot!
>
> > As your sane-find-scanner program finds libusb devices, maybe you have
> > an old installation of the SANE backends without libusb support that's
> > used by scanimage?
>
> I'm using the backends that came with Mandrake 10.0, which claim to be
> 1.0.13. Sounds like I should un-install the Mandrake version of sane and
> install from another source (hopefully I won't have to compile...)
>
> Can I just change the backends, or should I change the whole thing?

Always change the whole thing, only by that you're guaranteed that it'll
work together. For the LiDE20 try to get the latest 1.0.14 stuff, because
of some missing calibration stuff in 1.0.13.

Ciao,
  Gerhard



From gerhard@gjaeger.de  Fri Oct  1 08:43:03 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Fri, 1 Oct 2004 09:43:03 +0200
Subject: [sane-devel] USB: scanimage bails out
In-Reply-To: <415BF7E9.7080209@gmx.de>
References: <415BF7E9.7080209@gmx.de>
Message-ID: <200410010943.03758.gerhard@gjaeger.de>

Hi,

On Thursday 30 September 2004 14:11, Cornelius Koelbel wrote:
> Hello all,
>
> I am running a SuSE 9.1 with a Canon USB Scanner attached.
>
> sane-find-scanner tells me this:
> found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan],
> chip=LM983x?) at libusb:002:003

Try to run it as root and the "?" in "chip=LM983x" will disappear...
>
> and I set up the scanner with yast.
>
> Wenn I log into X and start xsane, I am able to scan.
> But when I got to a terminal and do a "/usr/bin/scanimage", I get this
> message:
> "scanimage: no SANE devices found"

This is somewhat strange. What's the output of:
export SANE_DEBUG_PLUSTEK=20; scanimage -L

[SNIPSNAP]
> The device in the proc filesystem exists:
> --snip--
> linux:~ # ls /proc/bus/usb/002/003  -l
> -rw-rw-rw-  1 root root 57 Sep 30 11:20 /proc/bus/usb/002/003
> --snip--

So there should be no problem in accessing the scanner.

>
> I get such a message in the /var/log/messages:
> --snip--
> Sep 30 11:26:16 linux scanimage: resmgr: server response code 200
> Sep 30 11:26:16 linux scanimage: resmgr: server response code 200
> --snip--

Hmmm, not quite sure about that - maybe here's the problem.
Anybody else?

Gerhard




From cornelius.koelbel@gmx.de  Fri Oct  1 08:52:40 2004
From: cornelius.koelbel@gmx.de (Cornelius Koelbel)
Date: Fri, 01 Oct 2004 09:52:40 +0200
Subject: [sane-devel] USB: scanimage bails out
In-Reply-To: <200410010943.03758.gerhard@gjaeger.de>
References: <415BF7E9.7080209@gmx.de> <200410010943.03758.gerhard@gjaeger.de>
Message-ID: <415D0CC8.4050900@gmx.de>

Hello,

I set the /usr/bin/scanimage suid and now it works (at the moment).
But I was so much fiddling about, that I am not sure, if it works, when 
I install it anew.
Hm, we will see. I guess this thread isn't closed yet ;-)

I will check your hints!

Regards
Cornelius

Gerhard Jaeger wrote:
> Hi,
> 
> On Thursday 30 September 2004 14:11, Cornelius Koelbel wrote:
> 
>>Hello all,
>>
>>I am running a SuSE 9.1 with a Canon USB Scanner attached.
>>
>>sane-find-scanner tells me this:
>>found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan],
>>chip=LM983x?) at libusb:002:003
> 
> 
> Try to run it as root and the "?" in "chip=LM983x" will disappear...
> 
>>and I set up the scanner with yast.
>>
>>Wenn I log into X and start xsane, I am able to scan.
>>But when I got to a terminal and do a "/usr/bin/scanimage", I get this
>>message:
>>"scanimage: no SANE devices found"
> 
> 
> This is somewhat strange. What's the output of:
> export SANE_DEBUG_PLUSTEK=20; scanimage -L
> 
> [SNIPSNAP]
> 
>>The device in the proc filesystem exists:
>>--snip--
>>linux:~ # ls /proc/bus/usb/002/003  -l
>>-rw-rw-rw-  1 root root 57 Sep 30 11:20 /proc/bus/usb/002/003
>>--snip--
> 
> 
> So there should be no problem in accessing the scanner.
> 
> 
>>I get such a message in the /var/log/messages:
>>--snip--
>>Sep 30 11:26:16 linux scanimage: resmgr: server response code 200
>>Sep 30 11:26:16 linux scanimage: resmgr: server response code 200
>>--snip--
> 
> 
> Hmmm, not quite sure about that - maybe here's the problem.
> Anybody else?
> 
> Gerhard
> 
> 
> 

-- 
Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte untersucht
und ist - aktuelle Virenscanner vorausgesetzt - sauber.
MailScanner dankt transtec fur die freundliche Unterstutzung.



From cornelius.koelbel@gmx.de  Fri Oct  1 10:17:00 2004
From: cornelius.koelbel@gmx.de (Cornelius Koelbel)
Date: Fri, 01 Oct 2004 11:17:00 +0200
Subject: [sane-devel] scanimage does not scan the whole page
Message-ID: <415D208C.3090103@gmx.de>

Hello,

here I am again with a new problem.
I got my scanner a USB Cannon CanoScan N670/676U  with the plustek 
backend, scanning now.

But when I issue the command scanimage --format tiff --mode Color > 
test.tif,

I get only a small portion of the image (240x160), not the whole page.

What do I have to do to get the whole page?

Thanks
Cornelius


From henning@meier-geinitz.de  Fri Oct  1 10:57:14 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 1 Oct 2004 11:57:14 +0200
Subject: [sane-devel] scanimage does not scan the whole page
In-Reply-To: <415D208C.3090103@gmx.de>
References: <415D208C.3090103@gmx.de>
Message-ID: <20041001095714.GA8035@meier-geinitz.de>

Hi,

On Fri, Oct 01, 2004 at 11:17:00AM +0200, Cornelius Koelbel wrote:
> But when I issue the command scanimage --format tiff --mode Color > 
> test.tif,
> 
> I get only a small portion of the image (240x160), not the whole page.
> 
> What do I have to do to get the whole page?

"scanimage --help" prints all the available options.

Bye,
  HJenning


From gerard@gkall.hobby.nl  Fri Oct  1 12:51:08 2004
From: gerard@gkall.hobby.nl (gerard klaver)
Date: Fri, 01 Oct 2004 11:51:08 +0000
Subject: [sane-devel] scanimage does not scan the whole page
In-Reply-To: <1096631360.2324.21.camel@gk-lex3>
References: <415D208C.3090103@gmx.de>  <1096631360.2324.21.camel@gk-lex3>
Message-ID: <1096631467.1597.23.camel@gk-lex3>

On Fri, 2004-10-01 at 11:49, gerard klaver wrote:
> On Fri, 2004-10-01 at 09:17, Cornelius Koelbel wrote:
> > Hello,
> > 
> > here I am again with a new problem.
> > I got my scanner a USB Cannon CanoScan N670/676U  with the plustek 
> > backend, scanning now.
> > 
> > But when I issue the command scanimage --format tiff --mode Color > 
> > test.tif,
> > 
> > I get only a small portion of the image (240x160), not the whole page.
> > 
> > What do I have to do to get the whole page?
> > 
> > Thanks
> > Cornelius
> 
> scanimage -h -d plustek
> 
> see the options for Geometry
-- 
----------
m.vr.gr.
Gerard Klaver



From gerhard@gjaeger.de  Fri Oct  1 14:03:17 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Fri, 1 Oct 2004 15:03:17 +0200
Subject: [sane-devel] scanimage does not scan the whole page
In-Reply-To: <415D208C.3090103@gmx.de>
References: <415D208C.3090103@gmx.de>
Message-ID: <200410011503.18059.gerhard@gjaeger.de>

On Friday 01 October 2004 11:17, Cornelius Koelbel wrote:
> Hello,
>
> here I am again with a new problem.
> I got my scanner a USB Cannon CanoScan N670/676U  with the plustek
> backend, scanning now.
>
> But when I issue the command scanimage --format tiff --mode Color >
> test.tif,
>
> I get only a small portion of the image (240x160), not the whole page.

That's the default scanarea of the plustek backend.

>
> What do I have to do to get the whole page?

Set the scanarea dimensions correctly ;)

Gerhard



From Thereidos <thereidos@gmail.com>  Fri Oct  1 18:19:48 2004
From: Thereidos <thereidos@gmail.com> (Thereidos)
Date: Fri, 1 Oct 2004 19:19:48 +0200
Subject: [sane-devel] Plustek OpticPro UT16
Message-ID: <872262d404100110195dc588ba@mail.gmail.com>

Hi there.

I'm new round here. I have bought Plustek OpticPro UT16 USB scanner
which is marked on sane's webpage as being supported. Unfortunatelly
sane (or actually xsane) cannot detect it. Neither doesn any other
scanning app.

I'm running Mandrake 10.0, sane 1.0.14 and 2.6.3 kernel.

I've just heard that 2.6.x series kernel have problems with usb. May
it be the reason?
-- 
Cezary 'Thereidos' Morga <thereidos@gmail.com>
Registered Linux User No. 362185 <http://counter.li.org>
GG# 169903 ICQ# 328-700-565 Jabber: thereidos@ebox.pl
backup email addresses: cezarym@pf.pl, cezarymorga@o2.pl


From gerard@gkall.hobby.nl  Fri Oct  1 20:40:47 2004
From: gerard@gkall.hobby.nl (gerard klaver)
Date: Fri, 01 Oct 2004 19:40:47 +0000
Subject: [sane-devel] Plustek OpticPro UT16
In-Reply-To: <872262d404100110195dc588ba@mail.gmail.com>
References: <872262d404100110195dc588ba@mail.gmail.com>
Message-ID: <1096659647.1588.31.camel@gk-lex3>

On Fri, 2004-10-01 at 17:19, Thereidos wrote:
> Hi there.
> 
> I'm new round here. I have bought Plustek OpticPro UT16 USB scanner
> which is marked on sane's webpage as being supported. Unfortunatelly
> sane (or actually xsane) cannot detect it. Neither doesn any other
> scanning app.
> 
> I'm running Mandrake 10.0, sane 1.0.14 and 2.6.3 kernel.
> 
> I've just heard that 2.6.x series kernel have problems with usb. May
> it be the reason?
> -- 
> Cezary 'Thereidos' Morga <thereidos@gmail.com>
> Registered Linux User No. 362185 <http://counter.li.org>
> GG# 169903 ICQ# 328-700-565 Jabber: thereidos@ebox.pl
> backup email addresses: cezarym@pf.pl, cezarymorga@o2.pl

Read www.project-sane.org/README.linux,

Check your hotplug setup
check (path can be different) /etc/hotplug/usb/libsane.usermap for
presence or you scanner vid and pid.

check your plustek.conf file (for example etc/sane.d/plustek.conf)

sane-find-scanner -v -v  first check if scanner is found.

export SANE_DEBUG_PLUSTEK=128
xscanimage
or 
xsane

check error log

-- 
----------
m.vr.gr.
Gerard Klaver



From joehenley@kc.rr.com  Fri Oct  1 16:56:51 2004
From: joehenley@kc.rr.com (Joe Henley)
Date: Fri, 01 Oct 2004 10:56:51 -0500
Subject: [sane-devel] umax_pp slow
In-Reply-To: <20041001042733.GA2166@wanadoo.fr>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com> <20041001042733.GA2166@wanadoo.fr>
Message-ID: <415D7E43.8080907@kc.rr.com>

Stef,

New results after the changes you suggested to modules.conf.  At the end 
are some more info.

So added the following to /etc/modules.conf and then rebooted:

alias parport_lowlevel parport_pc
options parport_pc io=0x378 io_hi=0x778 irq=7 dma=none

svoltz@wanadoo.fr wrote:
> On Thu, Sep 30, 2004 at 04:42:43PM -0500, Joe Henley wrote:
> 
>>Stef,
>>
>>Thanks very much for your reply.  I changed my umax_pp.conf file to read:
>>-------------------------------
>>option buffer 8388608
>>port 0x378
>>option astra 2000
>>

No changes to the above

>>Then I ran the export command, then the scanimage command.  The log 
>>contents are:
>>-------------------------------------------------------------
>>[sanei_debug] Setting debug level of umax_pp_low to 1.
>>[umax_pp_low] SANE_INB level 3
>>[umax_pp_low] sanei_umax_pp_InitPort(0x378,)
>>[umax_pp_low] sanei_ioperm(0x378, 8, 1) OK ...
>>[umax_pp_low] UMAX Astra 1220/1600/2000 P ASIC detected (mode=31)
>>[umax_pp_low] registerRead, found 0xFF expected 0x00 (umax_pp_low.c:6633)
> 
> 
> 	Weird, your paralle port can't do EPP when used directly, while it
> works with ppdev.
> 

The new results are esssentially the same; except for the line I marked
with asterisks:

[sanei_debug] Setting debug level of umax_pp_low to 1.
[umax_pp_low] SANE_INB level 3
[umax_pp_low] sanei_umax_pp_InitPort(0x378,)
[umax_pp_low] sanei_ioperm(0x378, 8, 1) OK ...
[umax_pp_low] UMAX Astra 1220/1600/2000 P ASIC detected (mode=31)
[umax_pp_low] Unexpected value for for register 0x0D, expected 0x00 or
0x40, got 0x18 ! (umax_pp_low.c:7406) ********New line*****************
[umax_pp_low] registerRead, found 0xFF expected 0x00 (umax_pp_low.c:6633)
[umax_pp_low] *** It appears that EPP data transfer doesn't work    ***
[umax_pp_low] *** Please read SETTING EPP section in sane-umax_pp.5 ***
[umax_pp_low] Hardware can't do ECP, giving up (umax_pp_low.c:6856) ...
[umax_pp_low] No EPP or ECP mode working, giving up ... (umax_pp_low.c:7475)

> 
>>[umax_pp_low] *** It appears that EPP data transfer doesn't work    ***
>>[umax_pp_low] *** Please read SETTING EPP section in sane-umax_pp.5 ***
>>[umax_pp_low] Hardware can't do ECP, giving up (umax_pp_low.c:6856) ...
>>[umax_pp_low] No EPP or ECP mode working, giving up ... (umax_pp_low.c:7475)
>>
>>The results surprised me.  I ran ppdiag to check and got:
>>---------------------------------------------------
>>S01: parport built as module
>>S02: parport0:
>>S02:    modes:PCSPP,TRISTATE,EPP
>>S02:    ADDR :0x378
>>S02:    IRQ  :no IRQ used
>>S02:    DMA  :no DMA used
>>S03: no parport parameters
>>S10: ppdev built as module
>>S12: /dev/parport0 exists ...
>>S12: /dev/parport0 is readable ...
>>S12: /dev/parport0 is writable ...
>>successfull end ....
>>

Then reran ppdiag and got:
S01: parport built as module
S02: parport0:
S02:    modes:PCSPP,TRISTATE,EPP
S02:    ADDR :0x378
S02:    IRQ  :7
S02:    DMA  :no DMA used
S03: parport parameters are: options parport_pc io=0x378 io_hi=0x778
irq=7 dma=none
S10: ppdev built as module
S12: /dev/parport0 exists ...
S12: /dev/parport0 is readable ...
S12: /dev/parport0 is writable ...
successfull end ...


>>I double checked my BIOS and it's set to EPP, port 378 and IRQ 7.
>>
>>So now I'm really stumped.  Please point me in the right direction.
>>
>>If it's relevant:  using RedHat 9, kernel is 2.4.20-20.9, xsane is 
>>version 0.96, sane-backend is: 1.0.14 with the 6.3 patch for umax_pp, 
>>mobo is an Intel 875PBZ.
>>
>>Joe
>>
>>PS:  Sorry about RoadRunner blocking your replies.  I don't know why.
> 
> 
> 	Try tweaking the parport parameters in /etc/modules.conf :
> 
> alias parport_lowlevel parport_pc
> options parport_pc io=0x378 io_hi=0x778 irq=7 dma=none
> 
> 	Another thing to try is to check is the kernel you use is
> compiled with the followwing options in 'Parallel port support':
> 
>     <M> Parallel port support
>     <M> PC-style hardware
>     < > Multi-IO cards (parallel and serial)
>     [*] Use FIFO/DMA if available (EXPERIMENTAL)
>     [*] SuperIO chipset support (EXPERIMENTAL)
>     < > Support for PCMCIA management for PC-style ports
>     [ ] Support foreign hardware
>     [*] IEEE 1284 transfer modes 
> 

In my compile config file (it's Red Hat, so there's abit of translation)
is the following.  I think I have all but the two experimental options
set as you'd suugest:
#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
CONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
CONFIG_PARPORT_PC_PCMCIA=m
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

With all these changes, I tried to do a scan and it failed with
essentially the same messages as in the log entry above.

> 	What other parallel port BIOS setting do you have ?

In the BIOS set up screen, it says I have "Output only,"
"Bi-directional," "EPP," and "ECP".  I had forgotten I had ECP.  Oddly
it's in the BIOS, but ppdiag doesn't see it as an option.

So I rebooted and set the BIOS to ECP.  All other settings the same
(including the "export" command).  The scanimage command hung in a loop
with the following:

[sanei_debug] Setting debug level of umax_pp_low to 1.
[umax_pp_low] SANE_INB level 3
[umax_pp_low] sanei_umax_pp_InitPort(0x378,)
[umax_pp_low] sanei_ioperm(0x378, 8, 1) OK ...
[umax_pp_low] UMAX Astra 1220/1600/2000 P ASIC detected (mode=31)
[umax_pp_low] Unexpected value for for register 0x0D, expected 0x00 or
0x40, got 0x18 ! (umax_pp_low.c:7406)
[umax_pp_low] registerRead, found 0xFF expected 0x00 (umax_pp_low.c:6633)
[umax_pp_low] *** It appears that EPP data transfer doesn't work    ***
[umax_pp_low] *** Please read SETTING EPP section in sane-umax_pp.5 ***
[umax_pp_low] ECPregisterRead failed, expecting 0x20, got 0x22
(umax_pp_low.c:2850)
[umax_pp_low] ECPregisterRead failed, expecting 0x20, got 0x22
(umax_pp_low.c:2850)
[umax_pp_low] ECPregisterRead failed, expecting 0x20, got 0x22
(umax_pp_low.c:2850)
.........................the avove line just keeps going, over and over
.....

The results for ppdiag (under ECP) are:
S01: parport built as module
S02: parport0:
S02:    modes:PCSPP,TRISTATE
S02:    ADDR :0x378
S02:    IRQ  :7
S02:    DMA  :no DMA used
S03: parport parameters are: options parport_pc io=0x378 io_hi=0x778
irq=7 dma=none
S10: ppdev built as module
S12: /dev/parport0 exists ...
S12: /dev/parport0 is readable ...
S12: /dev/parport0 is writable ...
successfull end ....

Perhaps it's relevant, I looked in the messages boot log and saw the
following:
Oct  1 10:26:30 Eddie kernel: parport0: PC-style at 0x378 (0x778), irq 7
[PCSPP,TRISTATE]
Oct  1 10:26:40 Eddie kernel: parport0: PC-style at 0x378 (0x778), irq 7
[PCSPP,TRISTATE]
Oct  1 10:26:40 Eddie kernel: lp0: using parport0 (interrupt-driven).
Oct  1 10:26:40 Eddie kernel: lp0: console ready
Oct  1 10:38:56 Eddie kernel: ppdev: user-space parallel port driver

Again I tried to do a scan, it crapped out with messages as in the log file.

Does all this tell you something (other than my parallel port is screwed 
up)?  Any further thoughts or suggestions?

Again, thanks for all your help.

Joe Henley


> 
> Regards,
> 	Stef
> 




From Thereidos <thereidos@gmail.com>  Sat Oct  2 00:39:54 2004
From: Thereidos <thereidos@gmail.com> (Thereidos)
Date: Sat, 2 Oct 2004 01:39:54 +0200
Subject: [sane-devel] Plustek OpticPro UT16
In-Reply-To: <1096659647.1588.31.camel@gk-lex3>
References: <872262d404100110195dc588ba@mail.gmail.com>
 <1096659647.1588.31.camel@gk-lex3>
Message-ID: <872262d404100116393ebdf725@mail.gmail.com>

On Fri, 01 Oct 2004 19:40:47 +0000, gerard klaver <gerard@gkall.hobby.nl> wrote:
> Read www.project-sane.org/README.linux,

Alright. The problem was in missing usb interface module in modprobe.conf.

Now I'm having another problem - all the scans are too dark. I've
tried gamma and brightness correction but it didn't help. Anyone got
any idea?
-- 
Cezary 'Thereidos' Morga <thereidos@gmail.com>
Registered Linux User No. 362185 <http://counter.li.org>
GG# 169903 ICQ# 328-700-565 Jabber: thereidos@ebox.pl
backup email addresses: cezarym@pf.pl, cezarymorga@o2.pl


From Francois.Patte@math-info.univ-paris5.fr  Sat Oct  2 15:25:14 2004
From: Francois.Patte@math-info.univ-paris5.fr (=?iso-8859-1?b?RnJhbudvaXM=?= Patte)
Date: Sat,  2 Oct 2004 16:25:14 +0200
Subject: [sane-devel] scanner hp5400
Message-ID: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr>

Bonjour,

I am unable to have the scanner hp5400c working under linux. Here the res=
ult of:

***
lsusb:

Bus 003 Device 002: ID 03f0:1005 Hewlett-Packard ScanJet 5400c

*****
sane-find-scanner:

found SCSI scanner "Nikon LS-2000 1.31" at /dev/scanner
found SCSI scanner "Nikon LS-2000 1.31" at /dev/sg0
found SCSI scanner "Nikon LS-2000 1.31" at /dev/sga
  # Your SCSI scanner was detected. It may or may not be supported by SAN=
E. Try
  # scanimage -L and read the backend's manpage.

found USB scanner (vendor=3D0x03f0, product=3D0x1005) at /dev/usb/scanner=
0
found USB scanner (vendor=3D0x03f0 [Hewlett-Packard], product=3D0x1005 [H=
P Scanjet
5400C Series]) at libusb:003:002
  # Your USB scanner was (probably) detected. It may or may not be suppor=
ted by
  # SANE. Try scanimage -L and read the backend's manpage.

*********
scanimage -L:

device `coolscan2:scsi:/dev/scanner' is a Nikon    LS-2000          film =
scanner
device `coolscan:/dev/sg0' is a Nikon    LS-2000          slide scanner

SANE_DEBUG_HP5400=3D255 scanimage -L

[sanei_debug] Setting debug level of hp5400 to 255.
[hp5400] sane_init: SANE hp5400 backend version 1.0-3 (from sane-backends
1.0.14)
[hp5400] Reading config file
[hp5400] Discarding line 1
[hp5400] Discarding line 2
[hp5400] Discarding line 3
[hp5400] Discarding line 4
[hp5400] Trying to attach usb 0x03f0 0x1005
[hp5400] vendor/product 0x03F0-0x1005 opened
[hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D 1200
[hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D C500
[hp5400] Command 12 verified
[hp5400] Sorry, unknown scanner version. Attempted match on :
[hp5400] * 'SilitekIBlizd C3 ScannerV0.84'
[hp5400] * 'SilitekIBlizd C3 ScannerV0.86'
[hp5400] * 'SilitekIBlizd C3 ScannerV0.87'
[hp5400] Version is ''
[hp5400] attach_one_device: attached /dev/usb/scanner0 successfully
[hp5400] hp5400_open: open returned Device busy
[hp5400] hp5400_open failed
[hp5400] attach_one_device: couldn't attach libusb:003:002
[hp5400] Discarding line 6
[hp5400] Discarding line 7
[hp5400] Discarding line 8
[hp5400] Discarding line 9
[hp5400] Discarding line 10
[hp5400] Discarding line 11
[hp5400] Discarding line 12
[hp5400] Discarding line 13
[hp5400] Trying to attach /dev/usb/scanner0
[hp5400] vendor/product 0x03F0-0x1005 opened
[hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D 1200
[hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D C500
[hp5400] Command 12 verified
[hp5400] Sorry, unknown scanner version. Attempted match on :
[hp5400] * 'SilitekIBlizd C3 ScannerV0.84'
[hp5400] * 'SilitekIBlizd C3 ScannerV0.86'
[hp5400] * 'SilitekIBlizd C3 ScannerV0.87'
[hp5400] Version is ''
[hp5400] attach_one_device: attached /dev/usb/scanner0 successfully
[hp5400] Discarding line 15
[hp5400] Discarding line 16
[hp5400] sane_get_devices
device `coolscan2:scsi:/dev/scanner' is a Nikon    LS-2000          film =
scanner
device `coolscan:/dev/sg0' is a Nikon    LS-2000          slide scanner
[hp5400] sane_exit

********
The /etc/sane.d/hp5400.conf is:

# hp5400.conf
# See man sane-hp5400 for a description.
#
# HP 5400C
usb 0x03f0 0x1005
#
# HP 5470C
#usb 0x03F0 0x1105
#
# Device filename to use for scanner access
#
# Uncomment the following line if autodetection fails
#
/dev/usb/scanner0
#libusb:003:002
#option connect-device


What can I do else?

Thank you.
--
Fran=E7ois Patte

Ecole fran=E7aise d'Extr=EAme-Orient - Pune - Inde
Universit=E9 Ren=E9 Descartes - Paris 5
UFR de math=E9matiques et informatique
http://www.math-info.univ-paris5.fr/~patte


From henning@meier-geinitz.de  Sat Oct  2 15:31:04 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 2 Oct 2004 16:31:04 +0200
Subject: [sane-devel] account problem
In-Reply-To: <20040930103929.51775.qmail@web17810.mail.tpe.yahoo.com>
References: <20040930103929.51775.qmail@web17810.mail.tpe.yahoo.com>
Message-ID: <20041002143104.GF10327@meier-geinitz.de>

Hi,

On Thu, Sep 30, 2004 at 06:39:29PM +0800, sean035@yahoo.com.tw wrote:
> I have a big problem about account. I am developing a
> new scanner driver for Xsane and backend. But I meet a
> bug about account that I just can work normally as
> root not other user account. When I log in as user
> account I can't use scan and preview as Xsane
> applicaiton. It's always say "Operation was
> cancelled".

While I'm surprised about the error message that's most probably a
permission problem. See README.linux (e.g. here:
http://www.sane-project.org/README.linux) for details.

For which scanner are you developping a backend? Can you give some
details?

Bye,
  Henning



From Oliver.Schwartz@gmx.de  Sat Oct  2 16:16:44 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Sat, 2 Oct 2004 17:16:44 +0200
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <415BD75B.1060103@bigpond.net.au>
References: <415BD75B.1060103@bigpond.net.au>
Message-ID: <200410021716.46218.Oliver.Schwartz@gmx.de>

Hi,

> - "scanimage > /tmp/junkimage.bin" gives me :
>
> [snapscan] Scanner warming up - waiting 9 seconds.
> [snapscan] Scanner warming up - waiting 33 seconds.
> scanimage: sane_start: Error during device I/O
>
> This usually takes more than 9 + 33 seconds to happen

please repeat the test by running 
"SANE_DEBUG_SNAPSCAN=255 scanimage >/tmp/junk.bin 2>debug.log" 
and send me the debug.log file.

/Oliver


From henning@meier-geinitz.de  Sat Oct  2 16:37:19 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 2 Oct 2004 17:37:19 +0200
Subject: [sane-devel] Troubles with sniffusb 1.8
In-Reply-To: <20040928165005.GB858@wanadoo.fr>
References: <20040928165005.GB858@wanadoo.fr>
Message-ID: <20041002153719.GI10327@meier-geinitz.de>

Hi,

On Tue, Sep 28, 2004 at 06:50:05PM +0200, svoltz@wanadoo.fr wrote:
> 	Did anyone get into this ?

I don't remeber having seen such messages.

> 	- last, I see that that the usbsnoop.log isn't used directly, but 
> 	parsed with some awk scripts. Would it be worth to have a 
> 	modified version of sniffusb to output in 'the right format'
> 	directly ?

I don't think so. The log should contain all available information.
Then, the developer can chose which information is needed for his
specific task. Maybe inerrupt tarffic can be ignored, maybe not.
Sometimes you only need contorl messages, sometimes only bulk.

So that really depends on the chipset and the task that should be
performed.

Bye,
  Henning


From henning@meier-geinitz.de  Sat Oct  2 16:39:57 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 2 Oct 2004 17:39:57 +0200
Subject: [sane-devel] HP Scanjet 3670
In-Reply-To: <33041.200.205.218.14.1096404835.squirrel@webmail.novalinux.com.br>
References: <33041.200.205.218.14.1096404835.squirrel@webmail.novalinux.com.br>
Message-ID: <20041002153957.GJ10327@meier-geinitz.de>

Hi,

On Tue, Sep 28, 2004 at 05:53:55PM -0300, anderson@novalinux.com.br wrote:
> I'm migrating all M$ Windows for LINUX in a football club (soccer team)
> but I'm stuck in this HP SCANJET 3670!!!
> 
> Did any one get this thing work on Linux???

Most probably not, at least not with SANE.

> I contact the HP in USA but whithout no result, just the promess of "the
> driver is being developed by our engineers and as soon it is done it'll be
> in the homepage"

Interesting. But I rather think that means "never".

> I am not a developer, I am consultant of computer science and free software.
> but I can understand codes, so, if you need me, I'll be here.

Well, the code is in CVS. So just go ahead and fix it.

http://www.meier-geinitz.de/sane/genesys-backend/

Bye,
  Henning


From henning@meier-geinitz.de  Sat Oct  2 16:49:47 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 2 Oct 2004 17:49:47 +0200
Subject: [sane-devel] scanner hp5400
In-Reply-To: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr>
References: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr>
Message-ID: <20041002154946.GK10327@meier-geinitz.de>

Hi,

On Sat, Oct 02, 2004 at 04:25:14PM +0200, François Patte wrote:
> I am unable to have the scanner hp5400c working under linux. Here the result of:

[...]

> [hp5400] vendor/product 0x03F0-0x1005 opened
> [hp5400] Read: reqtype = 0xC0, req = 0x04, value = 1200
> [hp5400] Read: reqtype = 0xC0, req = 0x04, value = C500
> [hp5400] Command 12 verified
> [hp5400] Sorry, unknown scanner version. Attempted match on :
> [hp5400] * 'SilitekIBlizd C3 ScannerV0.84'
> [hp5400] * 'SilitekIBlizd C3 ScannerV0.86'
> [hp5400] * 'SilitekIBlizd C3 ScannerV0.87'
> [hp5400] Version is ''

> What can I do else?

Rebuild sane-backends like this:

CFLAGS="-DNO_STRING_VERSION_MATCH" ./configure
make
make install

That's untested but I think it disables the version test.

See bug report:
https://alioth.debian.org/tracker/index.php?func=detail&aid=300542&group_id=30186&atid=410366

Thomas: As this issue pops up from time to time can't the version test
be disabled completely?

bye,
  Henning



From eppesuig@users.sourceforge.net  Sat Oct  2 15:27:11 2004
From: eppesuig@users.sourceforge.net (Giuseppe Sacco)
Date: Sat, 02 Oct 2004 16:27:11 +0200
Subject: [sane-devel] is coolscan2 maintained?
Message-ID: <1096727231.3040.561.camel@localhost>

Hi,
I am trying to get in touch with the coolscan2 backend author but I got
no replies neither to private emails, neither in this list.
I even checked that his last commit is dated january 2003, so I am
wondering if he is still working at this project.

Is anyone in contact with him?

Thanks,
Giuseppe



From henning@meier-geinitz.de  Sat Oct  2 17:08:03 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 2 Oct 2004 18:08:03 +0200
Subject: [sane-devel] Releases of sane-backends and sane-frontends planned
Message-ID: <20041002160803.GL10327@meier-geinitz.de>

Hi everyone,

I intend to start the release process for sane-backends 1.0.15 soon if
nobody objects. If there are any external backends that should be
included into sane-backends 1.0.15 please send patches now.

I also intend to make a release of sane-frontends soon. If there is
anything that should be included into the next release please commit
it soon.

I'll post timetables in the next few days.

Happy hacking!

Bye,
  Henning


From afb@paradise.net.nz  Sun Oct  3 10:07:20 2004
From: afb@paradise.net.nz (Adam Felix Bogacki)
Date: Sun, 03 Oct 2004 22:07:20 +1300
Subject: [sane-devel] xsane-win32 config : "no devices available"
Message-ID: <415FC148.3000708@paradise.net.nz>

re."C:\sane\bin\xsane.exe"

.... after considerable head-scratching I finally RTFM and realised I 
had put it in
the wrong directory. Re-installing and unzipping in C:, it now works but 
after following
SANE webpage config directions keeps telling me "no devices available".

The scanner works well with xsane on the Deb unstable drive.

I looked at the 'sane-config' file, but it does not seem to have the same
functions as the linux version.

I edited 'C:\sane\etc\sane.d\net.conf' to include the IP adresses of both
my server (midi tower) and my ISP ...
made sure that 'C:\sane\etc\sane.d\dll.conf' contains the uncommented 
line 'net',
and that 'C:\sane\etc\sane.d\epson.conf'  contains

> # For libusb support for unknown scanners use the following command
> # usb <product ID> <device ID>
> # e.g.:
>  usb 0x04b8 0x010c
> # And for the scanner module, use the following configuration:
> #usb /dev/usbscanner0
> usb /dev/usb/scanner0

I'm a bit unsure about the last bit because this is being done in WinXP.

Constructive ideas appreciated.

Adam Bogacki,
afb@paradise.net.nz




From thomas.soumarmon@cogitae.net  Sat Oct  2 17:09:31 2004
From: thomas.soumarmon@cogitae.net (Thomas Soumarmon)
Date: Sat, 02 Oct 2004 18:09:31 +0200
Subject: [sane-devel] scanner hp5400
In-Reply-To: <20041002154946.GK10327@meier-geinitz.de>
References: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr> <20041002154946.GK10327@meier-geinitz.de>
Message-ID: <415ED2BB.1000403@cogitae.net>

Hi Henning,

I have been far away from hp5400 stuff for a while.
I agree with you that the version match test is more an annoyance than a=20
killing feature.
Could you give me back a pointer to the parameters for CVS developper=20
access ?
I shall do this during the week-end.

Have a nice day.

Henning Meier-Geinitz a =E9crit :

>Hi,
>
>On Sat, Oct 02, 2004 at 04:25:14PM +0200, Fran=E7ois Patte wrote:
> =20
>
>>I am unable to have the scanner hp5400c working under linux. Here the r=
esult of:
>>   =20
>>
>
>[...]
>
> =20
>
>>[hp5400] vendor/product 0x03F0-0x1005 opened
>>[hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D 1200
>>[hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D C500
>>[hp5400] Command 12 verified
>>[hp5400] Sorry, unknown scanner version. Attempted match on :
>>[hp5400] * 'SilitekIBlizd C3 ScannerV0.84'
>>[hp5400] * 'SilitekIBlizd C3 ScannerV0.86'
>>[hp5400] * 'SilitekIBlizd C3 ScannerV0.87'
>>[hp5400] Version is ''
>>   =20
>>
>
> =20
>
>>What can I do else?
>>   =20
>>
>
>Rebuild sane-backends like this:
>
>CFLAGS=3D"-DNO_STRING_VERSION_MATCH" ./configure
>make
>make install
>
>That's untested but I think it disables the version test.
>
>See bug report:
>https://alioth.debian.org/tracker/index.php?func=3Ddetail&aid=3D300542&g=
roup_id=3D30186&atid=3D410366
>
>Thomas: As this issue pops up from time to time can't the version test
>be disabled completely?
>
>bye,
>  Henning
>
> =20
>


--=20
---------------------------------------------
Thomas Soumarmon.
Ing=E9nieur D=E9veloppement & Logiciels Libres
---------------------------------------------
      COGITAE    //www.cogitae.net/
---------------------------------------------
  tel: 05.34.14.39.39 - fax: 05.34.14.39.31
---------------------------------------------




From eppesuig@users.sourceforge.net  Sat Oct  2 18:15:16 2004
From: eppesuig@users.sourceforge.net (Giuseppe Sacco)
Date: Sat, 02 Oct 2004 19:15:16 +0200
Subject: [sane-devel] Releases of sane-backends and sane-frontends
 planned
In-Reply-To: <20041002160803.GL10327@meier-geinitz.de>
References: <20041002160803.GL10327@meier-geinitz.de>
Message-ID: <1096737316.3040.582.camel@localhost>

Il sab, 2004-10-02 alle 18:08, Henning Meier-Geinitz ha scritto:
> Hi everyone,
> 
> I intend to start the release process for sane-backends 1.0.15 soon if
> nobody objects. If there are any external backends that should be
> included into sane-backends 1.0.15 please send patches now.

Hi,
I would like to update the italian translation of sane-backend. I
contacted the translator that worked on it during 2003 and may send the
complete po in one week.

Is there any string freeze planned during the release? Should I get the
original pot at any specific date?

Bye,
Giuseppe



From henning@meier-geinitz.de  Sun Oct  3 10:58:59 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 11:58:59 +0200
Subject: [sane-devel] Releases of sane-backends and sane-frontends planned
In-Reply-To: <1096737316.3040.582.camel@localhost>
References: <20041002160803.GL10327@meier-geinitz.de> <1096737316.3040.582.camel@localhost>
Message-ID: <20041003095859.GB7885@meier-geinitz.de>

Hi,

On Sat, Oct 02, 2004 at 07:15:16PM +0200, Giuseppe Sacco wrote:
> Is there any string freeze planned during the release? Should I get the
> original pot at any specific date?

There shouldn't be any major changes to the strings after feature
freeze. Wait for the timetable for the actual date. Using the po from
after feature freeze should be ok.

Translations can be added at any time as their risk of breaking
anything is rather low. The same is true for documentation updates.

Bye,
  Henning


From henning@meier-geinitz.de  Sun Oct  3 11:03:15 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 12:03:15 +0200
Subject: [sane-devel] xsane-win32 config : "no devices available"
In-Reply-To: <415FC148.3000708@paradise.net.nz>
References: <415FC148.3000708@paradise.net.nz>
Message-ID: <20041003100315.GC7885@meier-geinitz.de>

Hi,

On Sun, Oct 03, 2004 at 10:07:20PM +1300, Adam Felix Bogacki wrote:
> The scanner works well with xsane on the Deb unstable drive.

Which scanner?

> I looked at the 'sane-config' file, but it does not seem to have the same
> functions as the linux version.

sane-config just shows the installation directories and the
compiler/linker flags of the installed SANE version.

> I edited 'C:\sane\etc\sane.d\net.conf' to include the IP adresses of both
> my server (midi tower) and my ISP ...

What do you intend to do? Is the scanner connected to the same
computer? Or do you want to scan over the network?

> made sure that 'C:\sane\etc\sane.d\dll.conf' contains the uncommented 
> line 'net',

That's for scanning over the net.

> and that 'C:\sane\etc\sane.d\epson.conf'  contains

That's for local scanning.

Bye,
  Henning


From uli.e@gmx.de  Sun Oct  3 11:46:44 2004
From: uli.e@gmx.de (Ulrich Eckhardt)
Date: Sun, 03 Oct 2004 12:46:44 +0200
Subject: [sane-devel] is coolscan2 maintained?
In-Reply-To: <1096727231.3040.561.camel@localhost>
References: <1096727231.3040.561.camel@localhost>
Message-ID: <415FD894.1090507@gmx.de>

Giuseppe Sacco wrote:

> I even checked that his last commit is dated january 2003, so I am
> wondering if he is still working at this project.
> 
> Is anyone in contact with him?

Hi,

the last time i heard about him was in July. I had send him
some logs from my Coolscan 5 and he replied, that he is now
working on a backend.

Uli
-- 
Ulrich Eckhardt                  http://www.uli-eckhardt.de

Ein Blizableiter auf dem Kirchturm ist das denkbar stärkste
Misstrauensvotum gegen den lieben Gott. (Karl Krauss)


From henning@meier-geinitz.de  Sun Oct  3 13:34:40 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 14:34:40 +0200
Subject: [sane-devel] Fix for net/saned on 64 bit systems: please test
Message-ID: <20041003123440.GF7885@meier-geinitz.de>

Hi,

I've just applied a oneliner fix to the CVS version of the net
backend. Please test net/saned especially on 64 bit platforms.

Here is a description of the bug:
https://alioth.debian.org/tracker/index.php?func=detail&aid=300837&group_id=30186&atid=410366

Bye,
  Henning


From eppesuig@users.sourceforge.net  Sun Oct  3 13:01:56 2004
From: eppesuig@users.sourceforge.net (Giuseppe Sacco)
Date: Sun, 3 Oct 2004 14:01:56 +0200
Subject: [sane-devel] is coolscan2 maintained?
In-Reply-To: <415FD894.1090507@gmx.de>
References: <1096727231.3040.561.camel@localhost> <415FD894.1090507@gmx.de>
Message-ID: <20041003120156.GA21739@libero.it>

Il Sun, Oct 03, 2004 at 12:46:44PM +0200, Ulrich Eckhardt ha scritto:
[...]
> the last time i heard about him was in July. I had send him
> some logs from my Coolscan 5 and he replied, that he is now
> working on a backend.

Ok, thanks. I will wait some more then.

Bye,
Giusepe


From henning@meier-geinitz.de  Sun Oct  3 13:58:57 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 14:58:57 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
Message-ID: <20041003125857.GG7885@meier-geinitz.de>

Hi,

I've just fixed some remaining compilation warnings of the microtek2
backend in SANE CVS. As I don't have any scanner that's supported by
the microtek2 backend: Could users of such scanners please test the
latest version? Especially check if calibration still works as
expected. Thanks.

For details see bug report:
https://alioth.debian.org/tracker/index.php?func=detail&aid=300823&group_id=30186&atid=410366

Bye,
  Henning


From henning@meier-geinitz.de  Sun Oct  3 14:20:48 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 15:20:48 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <20041003125857.GG7885@meier-geinitz.de>
References: <20041003125857.GG7885@meier-geinitz.de>
Message-ID: <20041003132048.GH7885@meier-geinitz.de>

Hi again,

Also a work-around to fix scanning on the microtek phantom c6 on big
endian platforms has been committed to SANE CVS. Please everyone check
if that doesn't break anything.

I'm especially interested in reports from users of big endian systems.

Here is the bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23274523

Karsten: I've applied both patches as you don't seem to have committed
changes to the microtek2 backend for quite some time. If you want to
become active again, details on getting CVS access are here:
http://www.sane-project.org/cvs.html

Bye,
  Henning


From henning@meier-geinitz.de  Sun Oct  3 15:04:39 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 16:04:39 +0200
Subject: [sane-devel] Fixing 64 bit problems in sanei code and several backends
Message-ID: <20041003140439.GI7885@meier-geinitz.de>

Hi everyone,

I'm currently trying to fix bug #300814:
https://alioth.debian.org/tracker/index.php?func=detail&aid=300814&group_id=30186&atid=410366
and #300799:
https://alioth.debian.org/tracker/index.php?func=detail&aid=300799&group_id=30186&atid=410366

Most of these warnings are caused by the assumption that size_t is
always 4 bits. E.g.:

size_t hubba;
...
printf ("hubba=%d\n", hubba);

See doc/backend-writing.txt for details.

Unfortunately the patch attached to the bug report can't be used
directly as it assumes that all platforms are 64 bit. So I'll try to
fix all the obvious problems manually like this:

printf ("hubba=%lu\n", (u_long) hubba);

As there are many size_t = 4 byte assumptions throughout the code of
SANE, the changes will touch many backends. Instead of creating bug
reports or mailing every single maintainer for some on e liner patches
I intend to change the code in CVS directly also for the backends.

If anybody doesn't like this approach please tell me.

Bye,
  Henning


From henning@meier-geinitz.de  Sun Oct  3 18:32:14 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 19:32:14 +0200
Subject: [sane-devel] Fixing 64 bit problems in sanei code and several backends
In-Reply-To: <20041003140439.GI7885@meier-geinitz.de>
References: <20041003140439.GI7885@meier-geinitz.de>
Message-ID: <20041003173214.GJ7885@meier-geinitz.de>

Hi,

On Sun, Oct 03, 2004 at 04:04:39PM +0200, Henning Meier-Geinitz wrote:
> As there are many size_t = 4 byte assumptions throughout the code of
> SANE, the changes will touch many backends. Instead of creating bug
> reports or mailing every single maintainer for some on e liner patches
> I intend to change the code in CVS directly also for the backends.

The changes are in CVS now. Please test. As I can't test on 64 bit
platforms myself I'm especially interested in reports about
compilation warnings and errors from such platforms.

Bye,
  Henning


From svoltz@wanadoo.fr  Mon Oct  4 05:46:44 2004
From: svoltz@wanadoo.fr (svoltz@wanadoo.fr)
Date: Mon, 4 Oct 2004 06:46:44 +0200
Subject: [sane-devel] umax_pp slow
In-Reply-To: <415D7E43.8080907@kc.rr.com>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com> <20041001042733.GA2166@wanadoo.fr> <415D7E43.8080907@kc.rr.com>
Message-ID: <20041004044644.GA6220@wanadoo.fr>

	Hello,

	I think you should try again ECP. I think the message you get is
harmless. You can comment it out in the sourcecode before doing tests
again. 
	But until you see ECP mode detected by ythe linux kernel, I'm
afraid you'll have troubles.

Regards,
	Stef


From cornelius.koelbel@gmx.de  Mon Oct  4 09:05:29 2004
From: cornelius.koelbel@gmx.de (Cornelius Koelbel)
Date: Mon, 04 Oct 2004 10:05:29 +0200
Subject: [sane-devel] scanning for faxes
Message-ID: <41610449.10304@gmx.de>

Hello,

I want to scan a A4 page, that I want to fax then.

I read that using the lineart-mode is the best solution.
But when I use the option --mode lineart with my plustek-driver, I get 
an error, that setting of --mode failed due to a wrong argument.

Any hints how I could best scan for faxes?

Regards
Cornelius

-- 
Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte untersucht
und ist - aktuelle Virenscanner vorausgesetzt - sauber.
MailScanner dankt transtec fur die freundliche Unterstutzung.



From scottf@bigpond.net.au  Mon Oct  4 09:06:50 2004
From: scottf@bigpond.net.au (scott fagg)
Date: Mon, 4 Oct 2004 18:06:50 +1000
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <200410021716.46218.Oliver.Schwartz@gmx.de>
References: <415BD75B.1060103@bigpond.net.au> <200410021716.46218.Oliver.Schwartz@gmx.de>
Message-ID: <Pine.LNX.4.53.0410041806350.16694@localhost.localdomain>

On Sat, 2 Oct 2004, Oliver Schwartz wrote:

> Date: Sat, 02 Oct 2004 17:16:44 +0200
> From: Oliver Schwartz <Oliver.Schwartz@gmx.de>
> To: sane-devel@lists.alioth.debian.org
> Subject: Re: [sane-devel] epson 2580 problems
>
> Hi,
>
> > - "scanimage > /tmp/junkimage.bin" gives me :
> >
> > [snapscan] Scanner warming up - waiting 9 seconds.
> > [snapscan] Scanner warming up - waiting 33 seconds.
> > scanimage: sane_start: Error during device I/O
> >
> > This usually takes more than 9 + 33 seconds to happen
>
> please repeat the test by running
> "SANE_DEBUG_SNAPSCAN=255 scanimage >/tmp/junk.bin 2>debug.log"
> and send me the debug.log file.

I've sent you a copy directly.

>
> /Oliver
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org
>

--
scottf@bigpond.net.au



From us@bernafon.ch  Mon Oct  4 09:18:53 2004
From: us@bernafon.ch (Ullrich Sigwanz)
Date: Mon, 4 Oct 2004 10:18:53 +0200
Subject: [sane-devel] XSane: Grey-scale and line-art for "color-only" scanners?
Message-ID: <2ED257AB11E3D84B8526737E255288EE14FCD7@brnnt12.bernafon.ch>

Hi all,

Is there a way to let XSane scan/view/store grey-scale or line-art, 
when there are only color scan modes for the backend available 
(as it is with the "niash" backend), 
or must the backend itself supply 
at least a grey-scale scan mode.

Thank you in advance

Ullrich


From afb@paradise.net.nz  Mon Oct  4 09:45:35 2004
From: afb@paradise.net.nz (Adam Felix Bogacki)
Date: Mon, 04 Oct 2004 21:45:35 +1300
Subject: [sane-devel] xsane-win32
Message-ID: <41610DAF.8050108@paradise.net.nz>

Thanks Oliver,

    My server is 203.79.110.81, ISP is 203.96.152.4

I've played around with commenting out  'localhost' or local server but  
all options give me
'no devices available'.

trying 'C:\sane\bin\xsane  net:localhost (with 'localhost' enabled) gave 
me the response

"Failed to open device 'net:localhost'
Error during device I/O."

Adam Bogacki,
afb@paradise.net.nz


> # This is the net config file.  Each line names a host to attach to.
> # If you list "localhost" then your backends can be accessed either
> # directly or through the net backend.  Going through the net backend
> # may be necessary to access devices that need special privileges.
>  localhost
> #192.168.0.7
> #203.79.110.81
> #203.96.152.4





From henning@meier-geinitz.de  Mon Oct  4 10:54:16 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 4 Oct 2004 11:54:16 +0200
Subject: [sane-devel] scanning for faxes
In-Reply-To: <41610449.10304@gmx.de>
References: <41610449.10304@gmx.de>
Message-ID: <20041004095416.GB9814@meier-geinitz.de>

Hi,

On Mon, Oct 04, 2004 at 10:05:29AM +0200, Cornelius Koelbel wrote:
> I read that using the lineart-mode is the best solution.
> But when I use the option --mode lineart with my plustek-driver, I get 
> an error, that setting of --mode failed due to a wrong argument.

That's because "lineart" is not a mode the plustek backend knows
about. Run "scanimage --help". It will print all options. I guess
"Binary" is the right one.

Maybe the Plustek backend can be changed to use the
SANE_VALUE_SCAN_MODE_* macros from saneopts.h?

Bye,
  Henning


From Oliver.Rauch@Rauch-Domain.DE  Mon Oct  4 14:32:50 2004
From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch)
Date: 04 Oct 2004 15:32:50 +0200
Subject: [sane-devel] XSane: Grey-scale and line-art for "color-only"
 scanners?
In-Reply-To: <2ED257AB11E3D84B8526737E255288EE14FCD7@brnnt12.bernafon.ch>
References: <2ED257AB11E3D84B8526737E255288EE14FCD7@brnnt12.bernafon.ch>
Message-ID: <1096896770.2141.2.camel@Babylon7>

XSane does not allow color->grayscale->lineart transformation.
That is something that all scanners/backends should make available.

I will think about adding such a feature to xsane.

Oliver

Am Mon, 2004-10-04 um 10.18 schrieb Ullrich Sigwanz:
> Hi all,
> 
> Is there a way to let XSane scan/view/store grey-scale or line-art, 
> when there are only color scan modes for the backend available 
> (as it is with the "niash" backend), 
> or must the backend itself supply 
> at least a grey-scale scan mode.
> 
> Thank you in advance
> 
> Ullrich



From gerard@gkall.hobby.nl  Mon Oct  4 17:22:55 2004
From: gerard@gkall.hobby.nl (gerard klaver)
Date: Mon, 04 Oct 2004 16:22:55 +0000
Subject: [sane-devel] XSane: Grey-scale and line-art for "color-only"
 scanners?
In-Reply-To: <1096896770.2141.2.camel@Babylon7>
References: <2ED257AB11E3D84B8526737E255288EE14FCD7@brnnt12.bernafon.ch>
 <1096896770.2141.2.camel@Babylon7>
Message-ID: <1096906974.2067.52.camel@gk-lex3>

On Mon, 2004-10-04 at 13:32, Oliver Rauch wrote:
> XSane does not allow color->grayscale->lineart transformation.
> That is something that all scanners/backends should make available.
> 
> I will think about adding such a feature to xsane.
> 
> Oliver
> 
> Am Mon, 2004-10-04 um 10.18 schrieb Ullrich Sigwanz:
> > Hi all,
> > 
> > Is there a way to let XSane scan/view/store grey-scale or line-art, 
> > when there are only color scan modes for the backend available 
> > (as it is with the "niash" backend), 
> > or must the backend itself supply 
> > at least a grey-scale scan mode.
> > 
> > Thank you in advance
> > 
> > Ullrich

Workaround:
Use GIMP to startup XSANE then after scanning in submenu Gimp choice
image then choice mode and then choice color, gray or b/w to change 
scanning object.
-- 
----------
m.vr.gr.
Gerard Klaver



From boldra@tiscali.it  Mon Oct  4 17:44:37 2004
From: boldra@tiscali.it (Enrico Boldrini)
Date: Mon, 04 Oct 2004 18:44:37 +0200
Subject: [sane-devel] homepage for "artiscan 9600" scanner
Message-ID: <1096908276.936.26.camel@vicious>

Hi everyone,
It's online a site for artiscan 9600 scanner at:
http://home.pages.at/artiscann9600/
Here you'll find some instructions to make the scanner work under wine
and a place where developers of artiscan9600 may exchange their ideas.
current status of project:
developers of windows driver(documan) don't want to give us the
documentation; we have to do reverse engineering job to make it work.

Bye, enrico




From Oliver.Schwartz@gmx.de  Mon Oct  4 19:26:57 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Mon, 4 Oct 2004 20:26:57 +0200
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <Pine.LNX.4.53.0410041806350.16694@localhost.localdomain>
References: <415BD75B.1060103@bigpond.net.au> <200410021716.46218.Oliver.Schwartz@gmx.de> <Pine.LNX.4.53.0410041806350.16694@localhost.localdomain>
Message-ID: <200410042026.59822.Oliver.Schwartz@gmx.de>

Hi,

> > please repeat the test by running
> > "SANE_DEBUG_SNAPSCAN=255 scanimage >/tmp/junk.bin 2>debug.log"
> > and send me the debug.log file.
>
> I've sent you a copy directly.

The first three lines of the log read

[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.35

And later

[snapscan] sane_snapscan_open (after firmware upload): "EPSON 
Scanner1" is not a supported scanner

It seems you're using an old version of the snapscan backend. The 
backend revision should say "1.4.40" if you use the CVS version. 
Since you wrote earlier that you're using a fairly recent CVS 
snapshot you probably have two versions of SANE installed (e.g. one 
in /usr/lib/sane and one in /usr/local/lib/sane).

/Oliver


From henning@meier-geinitz.de  Mon Oct  4 19:28:57 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 4 Oct 2004 20:28:57 +0200
Subject: [sane-devel] homepage for "artiscan 9600" scanner
In-Reply-To: <1096908276.936.26.camel@vicious>
References: <1096908276.936.26.camel@vicious>
Message-ID: <20041004182857.GA2294@meier-geinitz.de>

Hi,

On Mon, Oct 04, 2004 at 06:44:37PM +0200, Enrico Boldrini wrote:
> It's online a site for artiscan 9600 scanner at:
> http://home.pages.at/artiscann9600/

I the full name of that scanner "Tamarack Artiscan 9600" or "Tamarack
Artiscan 9600 pro 36"?

Bye,
  Henning


From scottf@bigpond.net.au  Mon Oct  4 21:25:57 2004
From: scottf@bigpond.net.au (scott fagg)
Date: Tue, 05 Oct 2004 06:25:57 +1000
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <200410042026.59822.Oliver.Schwartz@gmx.de>
References: <415BD75B.1060103@bigpond.net.au>
 <200410021716.46218.Oliver.Schwartz@gmx.de>
 <Pine.LNX.4.53.0410041806350.16694@localhost.localdomain>
 <200410042026.59822.Oliver.Schwartz@gmx.de>
Message-ID: <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain>

On Mon, 4 Oct 2004, Oliver Schwartz wrote:

> Date: Mon, 04 Oct 2004 20:26:57 +0200
> From: Oliver Schwartz <Oliver.Schwartz@gmx.de>
> To: sane-devel@lists.alioth.debian.org
> Subject: Re: [sane-devel] epson 2580 problems
>
> Hi,
>
> > > please repeat the test by running
> > > "SANE_DEBUG_SNAPSCAN=255 scanimage >/tmp/junk.bin 2>debug.log"
> > > and send me the debug.log file.
> >
> > I've sent you a copy directly.
>
> The first three lines of the log read
>
> [sanei_debug] Setting debug level of snapscan to 255.
> [snapscan] sane_snapscan_init
> [snapscan] sane_snapscan_init: Snapscan backend version 1.4.35
>
> And later
>
> [snapscan] sane_snapscan_open (after firmware upload): "EPSON
> Scanner1" is not a supported scanner
>
> It seems you're using an old version of the snapscan backend. The
> backend revision should say "1.4.40" if you use the CVS version.
> Since you wrote earlier that you're using a fairly recent CVS
> snapshot you probably have two versions of SANE installed (e.g. one
> in /usr/lib/sane and one in /usr/local/lib/sane).

That might explain why i had some success earlier on, but none now. I'll
track down all copies, clean up and try again.

>
> /Oliver
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org
>

--
scottf@bigpond.net.au



From shirshegsm@delfi.lt  Mon Oct  4 21:46:43 2004
From: shirshegsm@delfi.lt (Linas Valiukas)
Date: Mon, 4 Oct 2004 23:46:43 +0300
Subject: [sane-devel] FreeBSD 5.2.1 and Mustek 2400CU Plus
Message-ID: <200410042346.43883.shirshegsm@delfi.lt>

--Boundary-00=_zabYBuwY6FKMi8n
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello.

I'm using FreeBSD 5.2.1-RELEASE on i386 and sane-backends-1.0.14_1 (from 
ports). Also I have Mustek 2400CU Plus connected to USB port.

My problem is that after scanning something I have to reattach my scanner 
(detach and attach again the USB cable), because SANE doesn't find my scanner 
anymore.

Here's what I get when plugging in my scanner at the first time:

%scanimage -L
device `gt68xx:libusb:/dev/usb0:/dev/ugen0' is a Mustek BearPaw 2400 CU Plus 
flatbed scanner

And then I scan something...

%scanimage > picture.pnm

...and when I'm trying to try scanning again I get:

%scanimage -L
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

I've checked output of usbdevs (command, which shows attached USB devices). 
Before scanning:

%usbdevs
addr 1: UHCI root hub, VIA
 addr 2: USB Scanner, Mustek Systems

...and after:
%usbdevs
addr 1: UHCI root hub, VIA
 addr 2: ?????, Mustek Systems

It looks like that after using my BearPaw, system can't find out that device 
on addr 1 is a scanner. Also, when I'm scanning multiple pages with scanadf, 
I can scan them all (I don't get "No scanners were identified" error between 
scans).

Here's some debug output:

first scan:
%env SANE_DEBUG_GT68XX=255 scanimage > /dev/null
<...>
[gt68xx] sane_read: scan complete: 3973 bytes, 9080709 total
[gt68xx] sane_read: start (line 3543 of 3543, byte_count 2563 of 2563)
[gt68xx] sane_read: nothing more to scan: EOF
[gt68xx] sane_cancel: start
[gt68xx] sane_cancel: scan finished, scanned 9080709 bytes in 56 seconds
[gt68xx] gt68xx_line_reader_free: enter
[gt68xx] gt68xx_device_read_finish: read_bytes_left = 0
[gt68xx] gt68xx_line_reader_free: leave
[gt68xx] gt68xx_device_generic_req: command=0x41
[gt68xx] >> 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 
00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 0000 00 00 00 00 
41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00
[gt68xx] << 00 41 b3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] gt68xx_device_generic_req: command=0x17
[gt68xx] >> 17 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] << 00 17 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] gt68xx_device_generic_req: command=0x24
[gt68xx] >> 24 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] << 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] sane_cancel: exit
[gt68xx] sane_close: start
[gt68xx] gt68xx_device_generic_req: command=0x25
[gt68xx] >> 25 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] << 00 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] gt68xx_device_close: enter: dev=0x8059800
[gt68xx] gt68xx_device_close: leave: ok
[gt68xx] gt68xx_calibrator_free: enter
[gt68xx] gt68xx_calibrator_free: min_clip_count=0, max_clip_count=0
[gt68xx] gt68xx_calibrator_free: leave: ok
[gt68xx] gt68xx_calibrator_free: enter
[gt68xx] gt68xx_calibrator_free: min_clip_count=518050, max_clip_count=4
[gt68xx] gt68xx_calibrator_free: leave: ok
[gt68xx] gt68xx_calibrator_free: enter
[gt68xx] gt68xx_calibrator_free: min_clip_count=0, max_clip_count=0
[gt68xx] gt68xx_calibrator_free: leave: ok
[gt68xx] sane_close: exit
[gt68xx] sane_exit: start
[gt68xx] gt68xx_device_free: enter: dev=0x8059800
[gt68xx] gt68xx_device_free: freeing dev
[gt68xx] gt68xx_device_free: leave: ok
[gt68xx] sane_exit: exit

second scan:
%env SANE_DEBUG_GT68XX=255 scanimage > /dev/null
[sanei_debug] Setting debug level of gt68xx to 255.
[gt68xx] SANE GT68xx backend version 1.0 build 60 from sane-backends 1.0.14
[gt68xx] sane_init: authorize != null
[gt68xx] sane_init: debug options are enabled, handle with care
[gt68xx] sane_init: little endian machine
[gt68xx] sane_init: reading config file `gt68xx.conf'
<...>
[gt68xx] sane_init: config file line 96: trying to attach `usb 0x055f 0x021d'
<...>
[gt68xx] sane_init: exit
[gt68xx] sane_get_devices: start: local_only = false
[gt68xx] sane_get_devices: exit
scanimage: no SANE devices found
[gt68xx] sane_exit: start
[gt68xx] sane_exit: exit

I'm using PS2Dfw.usb backend (which is identical to Mustek's provided in 
installation CD - by the way, my BearPaw on Windows works just fine).

Yes, I know that reattaching the cable is not a big deal. But I want to know 
what's wrong, how to fix it and what can I do to work it properly... ;-)

Can you help me with this?

Respectfully Yours,

Linas Valiukas

--Boundary-00=_zabYBuwY6FKMi8n
Content-Type: application/pgp-keys;
  name="OpenPGP key 0x692E662F8F8ECEFE588CC55CDBA23BED89508A29"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=0x692E662F8F8ECEFE588CC55CDBA23BED89508A29.asc

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.6 (FreeBSD)

mQGiBEFgLuoRBADKyjZYFGgKgMwHDR1jHekLwPKsRlCZvkjS64TfaZXSfgztchcT
C4ieSQZfxmgDCYlUQ5Rg13x+xgIGnIuoD0ajxt6FXri3M1p4ALktHlMw31aRbZZt
5xypifNRIB+REnp6kYSzEF5MepAvFlSlU4PYtv2M1bQVzJJSCq75w6xcgwCgqs/6
jvV07NX9DMFK5MI+YZNsiqkD/0P7Sv8HZKw3sWIcr1r3kPWyuAkrQ4tm0dcOWEIy
Z+2LhsLOxkod2C/T0bm2pVTwD2veQLfNaQqE45HWTbl2BHmPu8vHYbP+rYRE5DLN
+J/ihlLZcHnXmY4mb0rx+5P2S7dgM2pDKJ6n4PYt2pOCXeItXWgUOGbWKnMKjtQG
TPfoA/9ZJW3EyNbdkHbZgykDnfgTnwYdTFcHtPnLd84zLE7XwBE9NAeOpdC3SIwK
GSI5QcbgghBeQGjSZluezOz2pRiJdtBGRkBcdhcnxtuPguhV5+uz0Sp+hFUIMdSz
IzTMahiv4Nkd4I69emk5NToy/0QI8qgmopZrLNNtdiSa/ecDtrQxTGluYXMgVmFs
aXVrYXMgKFNoaXJzaGVHU00pIDxzaGlyc2hlZ3NtQGRlbGZpLmx0PoheBBMRAgAe
BQJBYC7qAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJENuiO+2JUIopf2AAoIaw
DetwPrCNfa86yqeFPq8SlhucAJ0UcrNMmtB0wCGntS20ivUhJcBcKLkBDQRBYC7s
EAQA/uaj55ji2GGTKtGPBFhbWUYMuZahLiVfDfDOWmLqJQHPTVMDu1UkWtaXJZ0J
5sEUiA1q+2Uda3JMrB4xy91xMa+adZGkX6F3z+wbf7aCBAHsH1qEWWTop8JWfMA7
zc6sD/bkRR0w6ST5POaXvfyCGc32N0bN9TXQP+McTxt/josAAwYEAPUDxKv6VOIG
qeamFBR6edsQ2xaVjFpUBBKfeO3xQNlPMS+8qKQ6nb9OXuOILESq063H6uXPxnFf
omjfA879mSvpqmvLLOiXOVe+fEINkHszT0dGkQ3Joqv9Vvr5o0LBDNi655dSfFl9
fnYX5XA8WsL40qbuHgvEJJD7vaCNx5+oiEkEGBECAAkFAkFgLuwCGwwACgkQ26I7
7YlQiikM1ACgosQFmW2kbHqp9h4Yy3t+tBncYwAAn2T9BhesJDRzCY3VeckZC+mz
MkDu
=NjCr
-----END PGP PUBLIC KEY BLOCK-----

--Boundary-00=_zabYBuwY6FKMi8n--


From karsten.festag@gmx.de  Mon Oct  4 22:52:55 2004
From: karsten.festag@gmx.de (Karsten Festag)
Date: Mon, 4 Oct 2004 23:52:55 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <20041003132048.GH7885@meier-geinitz.de>
References: <20041003125857.GG7885@meier-geinitz.de> <20041003132048.GH7885@meier-geinitz.de>
Message-ID: <200410042352.55031.karsten.festag@gmx.de>

Hi,

Henning, thanks for updating the backend.
I recently replaced my old microtek parallelport scannner with an Epson 2480 
(what a difference!) and I think I will stop working on the microtek2 
backend. But finally I would like to commit the changes I collected in the 
last time so they don't get lost. Henning, I'll send you the current files 
for the CVS, (I don't think I will need CVS access). They include the changes 
you made.
I tried to test todays CVS version on my old machine with the old scanner and 
I experienced a compilation problem:

make[1]: Wechsel in das Verzeichnis 
Verzeichnis /home/karsten/tmp/sane-backends/tools
gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes 
-pedantic -ansi -DHAVE_CONFIG_H -I. -I. -I../include -I../include 
-DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d      
-DPATH_SANE_DATA_DIR=/usr/local/share           -DV_MAJOR=1 -DV_MINOR=0 
sane-find-scanner.c
sane-find-scanner.c: In function `parse_file':
sane-find-scanner.c:973: warning: implicit declaration of function 
`check_libusb_device'
sane-find-scanner.c:974: sizeof applied to an incomplete type
[...much more of this...]
sane-find-scanner.c:1070: dereferencing pointer to incomplete type
sane-find-scanner.c:1073: dereferencing pointer to incomplete type
make[1]: *** [sane-find-scanner.o] Fehler 1
make[1]: Verlassen des Verzeichnisses 
Verzeichnis /home/karsten/tmp/sane-backends/tools
make: *** [all-recursive] Fehler 1

Looks like a libusb issue? I don't have libusb installed on the old machine 
but I ran configure with --disable-libusb so I expected no problems. 
Compiling on the new machine (which has libusb) works, but the 2.6 Kernel 
doesn't have ppscsi support so I can't test the backend right now.

Regards,

Karsten


On Sunday 03 October 2004 15:20, Henning Meier-Geinitz wrote:
> Hi again,
>
> Also a work-around to fix scanning on the microtek phantom c6 on big
> endian platforms has been committed to SANE CVS. Please everyone check
> if that doesn't break anything.
>
> I'm especially interested in reports from users of big endian systems.
>
> Here is the bug report:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23274523
>
> Karsten: I've applied both patches as you don't seem to have committed
> changes to the microtek2 backend for quite some time. If you want to
> become active again, details on getting CVS access are here:
> http://www.sane-project.org/cvs.html
>
> Bye,
>   Henning


From janer@sdf-eu.org  Mon Oct  4 19:47:03 2004
From: janer@sdf-eu.org (Jeney =?iso-8859-1?q?J=E1nos?=)
Date: Mon, 4 Oct 2004 20:47:03 +0200
Subject: [sane-devel] Lide 80
Message-ID: <200410042047.03317.janer@mail.datanet.hu>

Has anyone tried the Canon LIDE 80 with sane? Is any other scanner suppor=
ted=20
that scans negatives??
Janos


From henning@meier-geinitz.de  Tue Oct  5 10:46:03 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 11:46:03 +0200
Subject: [sane-devel] FreeBSD 5.2.1 and Mustek 2400CU Plus
In-Reply-To: <200410042346.43883.shirshegsm@delfi.lt>
References: <200410042346.43883.shirshegsm@delfi.lt>
Message-ID: <20041005094603.GA7772@meier-geinitz.de>

Hi,

On Mon, Oct 04, 2004 at 11:46:43PM +0300, Linas Valiukas wrote:
> I'm using FreeBSD 5.2.1-RELEASE on i386 and sane-backends-1.0.14_1 (from 
> ports). Also I have Mustek 2400CU Plus connected to USB port.
> 
> My problem is that after scanning something I have to reattach my scanner 
> (detach and attach again the USB cable), because SANE doesn't find my scanner 
> anymore.

That's a known issue. It happens with all scanners supported by the
gt68xx backend on all *BSD systems I've tested. I've tried to find the
reason for this but haven't been successful until now. But I'll try
again.

> I've checked output of usbdevs (command, which shows attached USB devices). 
> Before scanning:
> 
> %usbdevs
> addr 1: UHCI root hub, VIA
>  addr 2: USB Scanner, Mustek Systems
> 
> ...and after:
> %usbdevs
> addr 1: UHCI root hub, VIA
>  addr 2: ?????, Mustek Systems

If you enable debugging for USB (SANE_DEBUG_SANEI_USB=255) you'll see
that the scanner doesn't respond to a request sending its descriptors
after the first scan.

> It looks like that after using my BearPaw, system can't find out that device 
> on addr 1 is a scanner. Also, when I'm scanning multiple pages with scanadf, 
> I can scan them all (I don't get "No scanners were identified" error between 
> scans).

The error happens after the scanner is accessed AND its file
descriptor is closed for the first time. E.g. you can scan using xsane
for multiple times as long as you don't close xsane.

Bye,
  Henning


From henning@meier-geinitz.de  Tue Oct  5 10:49:36 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 11:49:36 +0200
Subject: [sane-devel] Lide 80
In-Reply-To: <200410042047.03317.janer@mail.datanet.hu>
References: <200410042047.03317.janer@mail.datanet.hu>
Message-ID: <20041005094936.GB7772@meier-geinitz.de>

Hi,

On Mon, Oct 04, 2004 at 08:47:03PM +0200, Jeney János wrote:
> Has anyone tried the Canon LIDE 80 with sane?

It's unsupported, see out scanner lists.

> Is any other scanner supported 
> that scans negatives??

E.g. the some of the Mustek BearPaw TA scanners are supported and can
scan negatives. But as they are flatbed scanners, scan quality won't
be as good as with "real" slide/negative scanners.

Bye,
  Henning


From henning@meier-geinitz.de  Tue Oct  5 11:50:18 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 12:50:18 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <200410042352.55031.karsten.festag@gmx.de>
References: <20041003125857.GG7885@meier-geinitz.de> <20041003132048.GH7885@meier-geinitz.de> <200410042352.55031.karsten.festag@gmx.de>
Message-ID: <20041005105018.GE7772@meier-geinitz.de>

Hi,

On Mon, Oct 04, 2004 at 11:52:55PM +0200, Karsten Festag wrote:
> I recently replaced my old microtek parallelport scannner with an Epson 2480 
> (what a difference!) and I think I will stop working on the microtek2 
> backend. But finally I would like to commit the changes I collected in the 
> last time so they don't get lost. Henning, I'll send you the current files 
> for the CVS, (I don't think I will need CVS access). They include the changes 
> you made.

One issue:
(line 4657):
    if ( !(md->revision=='2.70') && (md->model_flags & MD_RII_TWO_BYTES) )

That looks strange. I've removed the quotes around the 2.70 but you
should double-check if that works.

I've committed your backend to CVS now.

What about the microtek2.desc file? Shouldn't at least the version
number (currently 0.95) be increased? Why not just use the build number?

Is the Microtek Colorpage-EP a newly supported scanner? That one
should also show up in our scanner lists. Is it support complete,
good, basic or minimal?


> I tried to test todays CVS version on my old machine with the old scanner and 
> I experienced a compilation problem:

That was my fault. It's fixed now.

By the way: Could you change all references (e.g. on your website) to
mostang.com to www.sane-project.org? 

Bye,
  Henning


From henning@meier-geinitz.de  Tue Oct  5 12:24:31 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 13:24:31 +0200
Subject: [sane-devel] Timetable for release of sane-frontends 1.0.13
Message-ID: <20041005112430.GF7772@meier-geinitz.de>

Hi,

That's the timetable for the release of sane-frontends 1.0.13:

2004-10-10 Feature freeze (a snapshot will be made)
2004-10-17 Release

Please test sane-frontends and add any fixes to CVS now.

Bye,
  Henning


From henning@meier-geinitz.de  Tue Oct  5 12:32:02 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 13:32:02 +0200
Subject: [sane-devel] Timetable for the release of sane-backends-1.0.15
Message-ID: <20041005113202.GG7772@meier-geinitz.de>

Hi,

This is the timetable for the release of sane-backends 1.0.15

2004-10-17 Feature freeze (snapshot)
2004-10-31 Code freeze (snapshot)
2004-11-07 Release

Feature freeze means that only bug fixes and documentation updates are
allowed. After code freeze only fixes of grave bugs that render a
backend completely unusable or break compilation and documentation
updates are accepted.

If there are any new backends that should be included in that release
please tell us NOW.

Please everyone have a look at out growing list of bugs and fix as
many bugs as possible:
http://alioth.debian.org/tracker/index.php?group_id=30186&atid=410366

Or, if the bug report is bogus, close it.
You can view only bugs assigned to you to reduce the number of visible
bugs. Having a look at bugs assigned to nobody is also worth a try as
some bugs affect several backends/maintainers. You can also sort by
topic ("Summary").

Bye,
  Henning


From jb@jblache.org  Tue Oct  5 12:37:53 2004
From: jb@jblache.org (Julien BLACHE)
Date: Tue, 05 Oct 2004 13:37:53 +0200
Subject: [sane-devel] Timetable for release of sane-frontends 1.0.13
In-Reply-To: <20041005112430.GF7772@meier-geinitz.de> (Henning
 Meier-Geinitz's message of "Tue, 5 Oct 2004 13:24:31 +0200")
References: <20041005112430.GF7772@meier-geinitz.de>
Message-ID: <874ql9cs4u.fsf@frigate.technologeek.org>

Henning Meier-Geinitz <henning@meier-geinitz.de> wrote:

Hi,

> 2004-10-10 Feature freeze (a snapshot will be made)
> 2004-10-17 Release
>
> Please test sane-frontends and add any fixes to CVS now.

I have icons for xscanimage and xcam sitting in my inbox. I'll dig
them up and eventually add them to the CVS (more on that on IRC).

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb@jblache.org>                                  GPG KeyID 0xF5D65169


From david@phenix.fr  Tue Oct  5 14:52:28 2004
From: david@phenix.fr (Dave Neary)
Date: Tue, 05 Oct 2004 15:52:28 +0200
Subject: [sane-devel] Re: Timetable for the release of sane-backends-1.0.15 (Henning Meier-Geinitz)
In-Reply-To: <20041005133248.27973.49959.Mailman@haydn.debian.org>
References: <20041005133248.27973.49959.Mailman@haydn.debian.org>
Message-ID: <4162A71C.5090101@phenix.fr>

Hi,

Henning said:
> 2004-10-17 Feature freeze (snapshot)
> 2004-10-31 Code freeze (snapshot)
> 2004-11-07 Release
> 
> Feature freeze means that only bug fixes and documentation updates are
> allowed. After code freeze only fixes of grave bugs that render a
> backend completely unusable or break compilation and documentation
> updates are accepted.

I would like to have a go at fitting the changes we made to the Windows 
version of net into CVS before this. Is there a bugzilla where I can 
attach a final patch file? Or should I send it here?

Cheers,
Dave.

-- 
David Neary
Phenix Engineering
110 ave Jean Jaures, 69007 Lyon


From henning@meier-geinitz.de  Tue Oct  5 15:01:42 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 16:01:42 +0200
Subject: [sane-devel] Re: Timetable for the release of sane-backends-1.0.15 (Henning Meier-Geinitz)
In-Reply-To: <4162A71C.5090101@phenix.fr>
References: <20041005133248.27973.49959.Mailman@haydn.debian.org> <4162A71C.5090101@phenix.fr>
Message-ID: <20041005140142.GI7772@meier-geinitz.de>

Hi,

On Tue, Oct 05, 2004 at 03:52:28PM +0200, Dave Neary wrote:
> I would like to have a go at fitting the changes we made to the Windows 
> version of net into CVS before this. Is there a bugzilla where I can 
> attach a final patch file?

https://alioth.debian.org/tracker/?atid=410366&group_id=30186&func=browse

Please use a unified diff.

Bye,
  Henning


From kpeters@LHSolutions.com  Tue Oct  5 19:38:36 2004
From: kpeters@LHSolutions.com (Kenneth H. Peters)
Date: Tue, 5 Oct 2004 14:38:36 -0400
Subject: [sane-devel] Interesting image problem when scanning color ...
Message-ID: <00cb01c4ab0a$8731ff80$6601a8c0@khp5000elaptop>

This is a multi-part message in MIME format.

------=_NextPart_000_00CC_01C4AAE9.00205F80
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_00CD_01C4AAE9.00205F80"


------=_NextPart_001_00CD_01C4AAE9.00205F80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Folks:

 

I am using the following:

 

*	IXP425 Big-endian
*	MontaVista 2.4.18 kernel
*	SANE 1.0.14
*	Plustek backend
*	Scanimage as frontend
*	Canon LiDE 30
*	USB 1.1

 

Issue: Able to scan with "-mode Gray" and "-mode Binary", however using
"Color" produces images as shown in image-segment below. 

 



 

Analysis: Seems to be getting 1/3 more data in the X direction that is
"wrapping" around the image in the X direction.

 

I am interested in learning if anyone has seen this behavior. 

 

I thank you in advance for any insights you can provide. 

 

Thanks,

K.P.

 

 


------=_NextPart_001_00CD_01C4AAE9.00205F80
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Folks:</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I am using the following:</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<ul type=3Ddisc>
 <li class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
     font-family:Arial'>IXP425 Big-endian</span></font></li>
 <li class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
     font-family:Arial'>MontaVista 2.4.18 kernel</span></font></li>
 <li class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
     font-family:Arial'>SANE 1.0.14</span></font></li>
 <li class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
     font-family:Arial'>Plustek backend</span></font></li>
 <li class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
     font-family:Arial'>Scanimage as frontend</span></font></li>
 <li class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
     font-family:Arial'>Canon LiDE 30</span></font></li>
 <li class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
     font-family:Arial'>USB 1.1</span></font></li>
</ul>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Issue: Able to scan with &#8220;&#8212;mode =
Gray&#8221; and &#8220;&#8212;mode
Binary&#8221;, however using &#8220;Color&#8221; produces images as =
shown in
image-segment below. </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><img width=3D272 height=3D214
src=3D"cid:image001.jpg@01C4AAE8.FB73EE70"></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Analysis: Seems to be getting 1/3 more data in the X
direction that is &#8220;wrapping&#8221; around the image in the X =
direction.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I am interested in learning if anyone has seen this =
behavior.
</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I thank you in advance for any insights you can =
provide. </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>K.P.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------=_NextPart_001_00CD_01C4AAE9.00205F80--

------=_NextPart_000_00CC_01C4AAE9.00205F80
Content-Type: image/jpeg;
	name="image001.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image001.jpg@01C4AAE8.FB73EE70>

/9j/4AAQSkZJRgABAQEAYABgAAD//gAcU29mdHdhcmU6IE1pY3Jvc29mdCBPZmZpY2X/2wBDAAoH
BwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8
SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCADWARADASIAAhEBAxEB/8QAGwAAAQUBAQAAAAAAAAAAAAAA
BQECAwQGAAf/xABLEAABAwIEAQkEBAoKAgEFAAABAgMRAAQFEiExEwYUIkFRYXGBkSMyocEVJCWx
MzRCQ1KCkqKy0TVERWJjcnPC4fBTVIMWdNLi8f/EABcBAQEBAQAAAAAAAAAAAAAAAAABAgP/xAA4
EQABAgEICQMDAwQDAAAAAAABAAIRAyExQYHC0fASQlFhcaGxwcMygpEicuFSorITYrPSIzNT/90A
BAAo/9oADAMBAAIRAxEAPwAM/hL+QjOlxbiBcADTKBv91VHGns7iAk5uIiAOuYitGgZkIJB/o9UA
edXE2DZwtu8UnpobZCdJ3c1++gnhnZirCDtEbYcz2aEGa5OvKFwt4pRDzaSgHXWPSjS+RTaDcgqL
gCkOoC1/k6SDA33q+GeNdYikA6XDaie3KkH5VLyixR2yXzW3EO3Nqo5iJyhKdx3yRWgBMduLcSst
P0xrAj+0Hsh1zyNaIuilI0Wh1slw6o0kH40NxHk020LwMOqCm7hqM0EQoA9neK1WG3LtzhTj9wSp
ZtRKoiYqg+UKdxErCiOdNAd5hMfGKywaRA4c9HEqghrtHZ2cB2WIusOuba7uLZ1vKtLmcZiAFAGJ
E7jQ1WeaWguFaCk8RKkzpI0o7ysXw8cRmORa1rSolAVplby7+WvVNC3kFxDgWlY1QGgDMqlMx8TW
i0gZ3YqtEYWZ5BVFHNxiANHkz30rgEOkagupGvXtRdvAHnE3DlwsNBu4bCkx0tY/nV5/k7ZsC9h1
48K5bSASNjHd31mCjZyIbruIVG1AIEp15u4RHZKqtpEqQJ15iqfjRxvk5ZJQ+Q8+eEgpBKh1kz1d
9Q3uBP2pUphwvIatFJUkDpagkadfZ/3S1jP6Vhs8nZ2dihLYSnhROTmCv91ciPZSf7PVt51zR1ZK
SMpw9RBBntolhOFpxC047jqkhqzAGm8lQNRtVl1blK7fIsC6kS/HVdJ+VK6AOMQTrdJER4Vorrk4
02L360r2N82mCkag5f51DiHJ5TC7pu3WVlN6gFa9EgHLv3yfv7KIyfRs8eIQJ0ZeMMx/GU+W1ctP
4Yk6i5THwrSOcmrdtF8lx5a1tXrSQRCQZiervrsQ5NNti/Nu8scG9aQOJBCgQnsHfQpJz6NnjxWb
cB9tB/rSZHpSOJjiwZ+tJ8tqMJwC6WLxx1KWktXyG1AkySSNu7vq/dcmrRpN+niPHhXrSRJHXlnq
76IyeA4XMVmHBJeJIkXKY132pFhWZ6N+cpn4UbxvABZNX77ClKbtrtAUFaqIIG1BSQsOqSM2a5Rr
6Uz1Rk4FlxNcEcQjUc5TBnr0rljLxQRrzlMCPCjieTwNpcPLdUCm6ZlOXfMEmPKamuOS6G03h5ws
8G9aRoj3gcvf30KSZiG2XMQs6tJ9r0Yy3KflXL6RcUEz9ZTr6Uac5Pvca8zOZGmL5DaiRC1agSB2
de9X7nk1ZNc/9s/7G9aQNREHL3UOc2oykWXMVllCC6CD+Mp0jwrlI1dASR9ZT8qNY1gow5N86y4p
xm3vEBebdIIBB+XpQhYBDpCtrlOs9WlDXnajNWy4mrg8UmSTdJn4UqhHE3SnnKZ6+yrTdk/ecZbK
FZOdoSpZEJTMbmip5Nrb52H7lALN62kpQJ3y9Z8aHPNGTkWXMUAXl9rrM3KflTV/nQSfxlM/CtRc
cmrZoXpD7h4N80lJJGxy76d9QX3Joti8LFykhm9QkhY3CgI2oc80k59Gy5iFn1ge0I2Nykd3VXKA
Ic65uU93ZU9/aPWF2/bPphSLoa9R229fiKiWJ40kaXKevwoc80ZVZcW0TCktqTtzBXnvR7FGxb4U
zb5oKUW4VHV0h/KsCygv3K0hBKOOiR2jStjdkTiIKZ+tsz3+7QAiGdiD6ng7wf3A3uW+YnYIi7xc
lWUBQI7uiP50Gx13nPKZWVYUhnDVAa6AmQf4a0Ns1wVYgqNHE5/l8qyFqF4jcuXTaDmuLVxYHYFK
UR99WEHCG64pMZIEbAP2uwRu4xmxw7Bg1zhIWbRmQlJI1UAqIGp1OlCb3G8O+vkXJOa5aWnoK1HR
7vhVfHMJvW7ZhJZgIQ2lcqGhKjHXQx/B71sXJVbwEPoSuVA5SYisNh6uHZaB+qaon+QOGSuxvEnb
zlDcvsvZ2GwlDedOgCokCRpt8aKYfaFNnc3LxCnRcMJQVa5EyDp61nOjccRQUFEvJIKevats82ll
vEGgICLlhPkMtaGw5oUZ6mjh1ZiU+7k/SRBH44zHd7tZ3lPiN19L3OHMPKbRxUuOZDBJhIGu/bWi
vAiMTUCfxtme73aykDEeUmI3KyFJTdpAI/RC4HyoJyM7EZ6WngPkMwXoLIcQ1dZyFEJAJPWZ3q67
KlXOgM26YHbVRKQOe9KBAnu1qW+dbtmL19RMItQo+ArQpFlxc2egcOyxa0p5++hsANpt3QiBoBmW
BHlWpwm3LGDRlmbRKvXX51k8NaUq3tklRK12BPmZ6/Ot2WktMuobMJTaoSnuArLKrLq6Shi93E9X
rK3yuhigKZ+0GOr/AC0DxzG7lnG76wtWmlIN20palAkyMsAQe6jt8CRieupxBj/bWRw8fSGLX18k
wF36XUzuBnEfxUFWdiSUzWn7Ryk8FrbwhRxWQZN+xPf7tdfED6VBkfX2J/dpbyScUiP6QYj92qfK
O5Va4ZjawoBQvWsneYSflSMM8EkdT2+JDrbHHsVvMSKW0JtHLptaDBz6KQB1xtR29gjFASdcQY/2
1neT9uWsMvnMslNzboSfMSPgK0V8oxigKQftBjXt92m7NSklSOI6ySpcpHhb4bjqwqCLtqJ7YTWP
tWc44QPSVcNpn0o7y1f1uLIT7bEUK06wlAB+KhVTC2Au6uV5dGbhtQ02OZI/nQCOdyrJgwbdG4Fq
LwJSjE0BURfsadnu11+QlOKKKoAv2NSf8tLfKGXFQRMX7BOm/u0O5V3CLfCsZTrmdvWkJ8coPyNS
MBHNSSNDfb4lSwvFb/FnMQuH1pDbty0rhhMJSc6Y132760F5mSrFACAPpBiP3aBYDbIawa+JB6V5
bpPkR/Ojl5lCsU105+xt+rVomzUklSOI6ySH8q7hDOEY2FxLt60hHecoPyrL2tup5fBJJHOWwSB4
Ci3LV7NfuWY2cv0uK7sqEgfxGhzNy9bLuFNBKlKuUJhQJMykyPMUG/MyMmDODbi2LzDdqziLTDSU
IRfsBKR+rVPlRemzw/GCk5XHL5pLagNc2UH5VVVc47cpvVKYt2UqvWuJnQpJQejl0JmpcSwu8xIX
gxG4aHDxBpSkMIICiQANT3HspOklqjh8/wDF3TcI4/0JeruFuPLN8zKnFFRVqnrNFb7UYoQmZxBj
z92keYTbsYiy0IQi+YSkeGWnXwJGKEdeIMR+7VrzuSSPpP2+JZzlqtAvVt5fam/BBjYBKJHxHpVb
DsPF0q6fcT0GLtoFO8kqAjwiaZyofL/Km8SFyhl9IA6go5Z/ho1hDC2cGvCQEqVfMHylJH31BQjJ
9D23EewNJBW+oSG8OAkd6v8Ailu1qUrENM31pmJ6/dqpZ4km0slNJMuO27IBPYXCD8DRFLYfu8QR
r0bhC/GEg/Kkl9TgDRN2ipENlC7eeTwe6IY1dCzw6/Wg5FiylA74JoRyZY4dtnUNGsNSknxP/FG8
UsWcQaeZfUpKU24MoI1kEfOlYtGMOtH225UEWqZUqJO5/nUaYQJ3XEeKhn1/hDMZuOILtCoysu26
QI7kn5mg/Ka6FthmMEHhuKuGwgzucoPy+FXcQdbbaxJbiwhKbtkqJ2A6PXWR5QYmMYxC4SwZskXA
Xmj31QEg94iY8ajWwaAM0LbSCdKjH6Cuwe2SXsmVKuC40ojzSPnWxuspOJAkD64zIP6tZTDbhpm6
uC6qEqcbT2D3knX0rVXWUnEdtbxme/3a3nosyfqFnWTUOMPItLPF7hYjh3LRJHcE6Vn+TNsn6Pu3
SekHWQqe9QJ+6tFi1m1e22LMrUoIcu2kqKTBAgfzpicPYsLS/tmiYTdsiTE/k9njUbh2Uk5w0fb4
0fCUxeycu3lrVDlVccO0et0LTxLljJE6lIQok+sVbceYtkXy33UNo6yT2a/98KzN9e/TWLJvkoWm
3FivhJVoddJPkBVr+Liy3/qsulf/0LWD2wcuWUgwG7Eqynq1j51qn0DLc9RNskTQTk+xNq86oa8z
SkEDvJPyo4+klNxHXbpFVtVlxHUu4nq5YflG+bXDMaeSsBXPGshJ1JASflQnk7b5MOvVwUqTc26A
Y2MifuFP5aO5lv2YBJfxFCtOxKAI/eFX7BhdvhN4kmSq9YUD45TUGCScPoH2n/GEQvM32qYn7QYg
/s1n+Wj+Z16y19riCV/soSP91H73MPpWP/fYj92spyjdVc8qL5KOmll9CQN4UcoP8NTPRJKYDgOk
kjlk2q3wa9GXU3rCvXKfnRC+UqMTITmH0gxHf7tMuE8C3xBtA6Dd9bhI8k0++VrimkxiDHn7tWMc
8EkdX2+JZPlS+XuVF4gaoYfSQB1KOUH+GieDILdhiTpQBN8wM3mKzq3+eXeIXoGj98FjNuAVSPvr
X2rYtsLvEAEReW6jPUSEmgoST9TW7NHkZMK5ergYp2C/YMH9Ws7yzuM1+5ZwMqr4OLHglAH8RrRX
ygBik9WIMT+7VHFcJs7u/v75xS+I3etIgKEFJyb+lTPRJKhvAdJJSsspYw27aIEi8t83eYRPxqze
5SrFOqb9iR+zXXqUk4n337H+2oMXuWLRjF3n3AEC+ZJ11MBJgd+hqxz8JI6nt8Sy3KFxN1ynxFxJ
lLdwhvwUCAfuo3h+HNNYZdvLCVOqu2IUR7oOU+W9ZcKW+bq6e6DlxeBah4mfnW7uWkoZxJCdEi+Y
SI6gMtBNMkn62iqbrJqS+SPtSTlJxBjy92szdYnc4xjd2i3dUmyN+ich1cghMk9nX51pb5BIxQBU
A4gx5e7QbDsBXhbV8HXUrcbu2Wxk2MlJnx0HxoEkqGQ/t+ISf4Rm9B+1I0m/Ygfs03EAcuKT/wC+
x0v2aW+CoxXvv2I/dqjynuTbYVjSwvKpV60EGdZyg/KpGAjmpJKhvt8SyCnjeP3t4AQbi9CwOsSZ
+dbdbJt7W+YBjh3lukeQRWIaCmG1JI919saDQ6Ct1cuBxGJONqCkKvmCkjWfdqiabNKSc72nh/KT
WSW457ZYJzJdTlg69X/FGrTlTe2Ju1LbRccQpSSsa5imAaDrYdcDx0CgpK8siQkbmPKmuac4G0up
zGgOxBPMc+lahfLu7Sp4GxYPsksmFn3u3w12nzqC75b4k8h4ItrZuUJZVopRJ7RrtHdQK5ZYaacU
HXHA6+AgZAIjLqTOm9Ods3FuPpBBUHwJBkCIGseIqETQOaMBkqiMxzPDE5Cjv7i6vXbly5uXHQp5
OZuYbJ0g5RpUbiQkOwkpSHUwR1bVJcNqbeuGVwF8VBPhprU7lmUXd4wXIQh5EKKd5OnnAJ8KtEyj
arLqquHV7NqeMnumrSb+7YbuW0OqCVOtyk9IAiI38Kh4Djlut+NHH2wnWdVCQDHh5RrTnLZZU8kK
alb4T0VggkRO2+9AjaRZdV645Q3jnO+iwA7cNqUcp6oiNe6m3ePX7qbxCnGkF59BUW0agiIiSRVZ
dqviXTfQCkPIzBSgIB6/DvpHWFht5a1JCA62rOpQAOYSPgDRGVDhd/CvW6FPuOOXFw8+oNuauqzQ
TPlV1BBKJJ1sldW3vVFZWr5L5DYHDStspnUqEggDrirbDZdY47YCkps4ATqVEhUADr2rVfxdWaWW
dnqe1xO5tLUWrakBCrIqMpkyJiNamOPX7iTJZTxbPMroERE7a1UTbqBQiUKCbFRJSsESJnXzpiMi
m+MT0GsPUolOuYajTqNZaaDwurUprQ331k8VuX8Su3rt9ac4uE9FAIAJy9XkKuO45eIRctN8FKFX
TUJymRlyxGvdVVxpSlPJSkqDlwkyRH6Mg9h1FI/bLQ6+0UiedoSIUNTpHlvrRJPVPC4rz3KHEHOd
lQYHEvG1KIQdCI217hQ5TriL+7uyUqdcvkuKBGkzPpJp71sspuXlJgc6QJHVt1U24ZWkXWcQU3Sc
ySRJGnSjeO/voknQ0cLiIv8AKG/WLvo244t42owg7iIjXupLvlBfvIvEKDHtrttSlJSRqIiNaov2
ykLuUkDMLxCClJBIPV9xpbi3UlVyhRTpcpOfOIgZQTO3WKIzVsufhR29uSVW6DP1ptInc7CttdwB
iYCQIv2I/drE3CFNF8qWE/WUQmdequuLc5bpao6T6M0q6WXQgxvHw1FEk6Wnh1kytpiTqWmcVWuM
ib5kk/s1jbHFrtq0ulLcz84u21qCtRMgyKR22m/uLJS0qUbptClSCCJEDvFN4JDDy05UJRcIVlzC
QNNY7NvUUoCMmDRw6MCv3PKDEXFXgU3bAO3balnIqZERHS7qH37r2IXNzcXLy3Sq6QSjZAOgkJ+F
SP27gRcRlzC+bby5tQog7j9XrphbUsvFOWOcpIlQAjTWiMENGy4mOkAvgkzzlGvZtRI43eN2920S
hea6b6S5mU5Y6+6qLrKg04RkIXdgCFTERM+tNdZWFuphP4wghWYQQY65+NUzIyltlxErzlLfPKvO
Ezbth27bUQSpRSRHh2VCrHMQSu9ccdQ6u4u2lKzJMJIg9ETp1egqlcJKAsqEFV5kyxsU5ZB9a51A
SxcOrgJF2hMASpUidPSoRBGao4XETf5RYgvnYJtgHbttRhCtCIiOlVPFsSu8WbfbuSykKvUOKyJI
1CcvWTprUDrf4wJBSm4b6UgJ1iBPbSuMOk3BKMpTcpCgSARtMg7ax60KSdUN1xMcJ9sAZBuU+ulW
m8QurRFwhp+EKuUHKTI0Ig1AthZW8lKQqbpAnMNZ2g9+tNcRo+o9JIuEmRBECOvukeoojNU8Livr
uwgqCkZ0ohsBRnKSNx2a6x2z209y5Q2tS2zKoCFkdRIKesfox8aquQgOJgKCnUkH0pXASXpGzqcs
9dSCkIiB3dsVK++VgIKdGHANTuSQSfgB5d9PReOsF8oWqFOqCgSNcw1B01Hd3VA5J46gI9qmfCuc
gB8ESC6mfhWokiGasFQIwBzRipXrkrfuHVpSVq4bQiBAGWOrup1xdvOKkqUCh8KIKpClFRPwmAPH
tNQOgAvlW/FTHeNK52V8aAZ4iJ76yAAFYlxBOaMSnuvuqS6gr2cbAUAAoECAZ3+VOeu3S48Gm0Nt
cT3RGslJ7AOr4moXYC346Q4yZIpzo/Dkkg8ZPyrQUbQNk11TPPOKN2RlzOrbQroD8nb/APmx002q
O4Wp1h9twnKpxodEAe6mB99NcByviSCHkTHlSuweMoHQPJ2O21ZgKEaIQz+lGLa4ddXc5iVKebcK
urcyY/5q2yostBporQkWcgg6iM0R61QsYzvST+DXV5sbJk6WSt/MV0NIsurJjoWdnqVLpKQEAISu
wV0UiBqSSR19XxpjS+CylsapOHFEKTOg+HVSSlRQsH+oqHhvSBxKUtpK97FRHxrDarLq1Kax4+RZ
h59ee8UdA4+hBRAygSk6AeApr7zixiCSonjXLeYgDoxsR2bx51C66gceFxFynr8Ka9dBan1Aac4S
o9w0ojICFlxWrl9x1FzKspNy0knrMAAb0txcOLFyVFOdy5QkuESQOjoPQenjVJ664S3kKGUm4QqC
PAiuD6rh1xtsArXcpy/AUpRk2jZcRC5ulqubx1GVtKr5C4SNZG0nzNOuGbq8ReO8FcKfQ2TlUrKC
U/lGSdhua0DeFM2VrfJWhDrrd8wOIodfRmOwVdxBaWU4qtSkIQm/ZJKjAA6O/dRJP6tGO7x4rK3l
niLzdy2q3UhAvGwsZYggADw3/wCwKS7ZvQm8C7ZQPOG2ystnMkdGB2dQrSKxKzvziptXm3frzCgR
1iR67VYvZjFRAP2gx5+7SlJOfRs8eKxRcULi5uCU8Q3aDrtoR/OmuLUDcZYUC4honulH/wCIotyv
tmbVd1dtIS3GIoQpCRuCgGf3fjQTil4vBDanM1yj3U77VKkZQ08D/Bf/0cq/dLU5cLCUArvm3SQn
UqA3/eNNW4WnbkhCUDjIQlKSQAJSd5nq7aa42sl8Bp3W6SAMu5008aR1CgHytCkzdIEnypRwRk5b
ZcT33VvC5OVOt2D0REZimQPQelIp9aGnUJSJ47ScwBkZQBoZ9fAU1aVLLwRKvrSNvKnOtLh+EKGa
7SPd8KHPNGVHhcXXLpccu86ASu7zpImEqUUkx6U1SoauEuIS4OdoV0gdCOyO4mkcSpIfSoGedJk+
lNdB9uZiLlAj0odiMqsuJ7r6184zpQQq7bVkywExpoJ7/hSPPOZ7tSlZi4+AtUdpSSfVNcptxzjl
DZVN0kaAneKlcsbxAfSbZ7o3SAZbOh0gfGkEZPo2XFEt1QUs6At3LJTp+iIHwNJnLTT7ZSlaecAK
Cp1zFJO3+WluGnEF8OpLak3SRChqDppTXDBf6puU79W1NqM1bLiL2+F8fNxyQlxtT6Y6wkaeGoq+
1ZWwUmWUkuWanVzrK9ddalb14RBzfZ651/zVG9xOE2GtVKsD0ZjQkyfSaF00c6qOEIt48tMdh8KR
thk8M8NIzWClHQb66+NMNlauobC2wc1mp05dOkJg99DsPeatHrlT6smdpSR16lOm3bNXRiNpCSX4
CbRTKhkOizMD40Aojn0o+cEiuf8AmepHJDL60NshBLmj4Q4BHu6x8qrq142uX2qdTVrErpt5tlCD
+CQhCpGxkn51UdAl0E5vaJ1HVWWxhOrrEVRm4REOSVZjjZTMup07KVWzpkD2qY7tqY4QS7BA9qnS
KateXijKEkuj5VpRtR4XVM6V5XpEEPJ1FNW4RxsmxdTofKqr10AXI6XtAe8VA5crVm6REqkGiCaG
di0FncJQtyI/BLINWU3pPDEgzYLPjE0GsCpSlTp9Xc+dELfdjoyPo9cAjbetn1fF1Zd6LOz1Km4W
rgZdJw5Zg+dQm5LYYz5jmw1ZkfrVK0mOAFD+zlwQP81QXKsqGAEjXDXNSPGsNqsurUrr+7yrJOXa
Sl2cyiVgiYE7VI9idws3IQwhtLqkBScvZEeG1Vg5LT5hI6aeiNIpFkEOmVKGdPTiezrpnogqzsVp
Dq3g8pwSS6jXso5gbCF3dw4sBQadbKdOvOgfdNBmQCh0xHtkaR4UVw6/TYPPlYJQt9AVHVCkmfhV
EyjaWneOrVt77KRikjU4gxP7tDuVLVw9h2MN2wzFV80FgbkZRt5xV995m4axFxtaHEKv2DmSoEH3
afehKlYoCd8QYkd3RrNIhmpWR1R9viWOwy/t8JZvmX2Xi6u6ZACUiUhJkgyRr/Kil1ytsXBfDm92
C9eNLBKU6AZf72+lE8YwqzvVYmp5sJWMQZHETAUAQBv51l8ZwJ7DVXax7W3bu0oK06lOgIzdkj/v
bUk6ARuP+M4KPlJiyMZec5s28hnnWdSXABrCQNiddD61f5MI+p4nJibq1g9nSNAXADxZOvHTtt1V
ouTqfqeKRp9cttf1jRGUs9vVi0d2FZsTgyPpBiB+zWW5cOKTiysugF0TE/3W61F6CVYpHXfsQP2a
yfK1Dl1ypftkiVcdOXxIQPlRJKgcB0kkSwFlYwa+uloOZd6wBmHVIPxmjeIKyIxQyAlN+wder3aj
dZFraYgw0DkavbdCJ3IASKE8tcSNta4jZogOXN8gbbJCBJ9cvrSOfhJGo8D/AIigN5dqxXE76/II
4t2kNpOkJnTTtiK0bWBtWjN8XkB11u8ZTB1TrlnxrM4Ic9/lmQh9pSZ7QpIj41vL1ZAxSOrEGCB+
zVAgknO5tnWTUV9wLVjFYQ2023fsnqSAOj6Ux29t7xGKKt3EvJ5+wQpOypy9dQ8o7W4vbHFWGVJQ
TiDQUTPSBSBHqRQhq6cwS0vbd2xczG9a6R0TKSDE+tQRSSoYft8eC0GINNOfSYcaQ4E4gxAUkHfK
KyWP2zOHY1d27M5DcJUlJMlHumPDX4USuuVIUq+izI4t204mXOsZdDp3b0Gxa6ViOL3t+UBAU8hI
TMxtUSTobHd0k8CtBa3jL6wgnIpq0W0QdMxgkR5VYbAJaG04cuR61T+irZQTnLkuWpf3/KEwPDSq
jd06xcLDaypIAbIVroodIDzJNbYIkAbrqjgYEGme+OpNiKKtmX0sJcAUnmBUDOxEkGh93hJ4YUyr
MpxoPqTtAB1jyE0UbKSWSkSDh6p0/wA1IpaW2mio6/Ry+vxrmTBsc6q0+Ykjf1lD2Czbogu6nV1M
67bVE4pI4hkCXRrSPvhIcg/nAfEVSccLnEOoGYGOsVpRueSneuOk4JklwGKrrcWrPuBm9DXFOUqm
dxr2U/hDpTIhQB76IM8lGUkgwCOlv21IGzJgE9KIp5SIUR+mAR2U4iCqDpnGtEGeSIYcmFqPYy59
1EGZljt5gvq8ao4cOmvXXhOQfKiDOYhmTrzBcj1rZ9XxdWXeizs9ObkC3AGhw9eh86hU0p0MbH7O
WBPnVhsAcCDCfo9fzrkbW86kYeuPjWG1WXVqV1vd5Fi12pIcBVs8kdEb7UqrZvM5qo+2SIJ32qw4
DDs/+wnT0rlAw6QdOcJ+VEbVZdTMiUpcATPt0/KiTmCYkEvlVuQG7pCVSRoTEVWZb4twWiR07pGv
pW+vMwTieWNMQYgfs0RlLRw6sHdZJOHYzZi54TS2gLttLic4iZBTIntotbY4m9cxG3u0JRcLvWSc
h6JIUkEDX/utFcSWUN4ssNlRTfskACSfdrF4FaPvvF8oUpLd02taiDBJKdJ7daonKSeqa4t8Z6rb
3oT9q9U4gxP7tNxFDa28WCwCFX7AVO0dHqp17H2r0f7QY07fdqnyiu02WHY06YC+etZCfyjAMfCs
56JI6vt8SwTZBZdgyOcJEnfqrT8nUzY4nrl+uW3l0jWYSkoZUn/GRPjArTcncvMMTmR9ctvLpGqj
KW8W9WLR3iSVYp1k4gx/toTdWZe5TYvewCll9htEj8oqH3R8aK3gGbFZJP19if3abdNoQnFglRBV
iLJM9+WgpCSWp7fEn32YJxSE/wBoMQf2dKwWPXhxXG7+5CszIuQhqDoRIE+YANajlbiHMrHFGkLh
+4v20ohUKEJBJHw9RWMCAhDiRqA+kDx0qJJzNbZ8QZgmhTjLrjjKi2tLyYjQg6VqmOVrVy1epvEB
p126ZcCkjoyCkHw2n/utqywu0GE3CnWGlu86tzmWgEjMEkjw1q5eYXYoGJZbO26N+ylPshoDlnyN
aoMEk5y0jd1kz3CnuLhDzeJOMOIdQb9gpUhWYH3eynX4C/pMFAUOfsaHr92sRh9w89jNw5a5mGHr
1Ci0gQlKc4IkDTSa3F5M4pt/SDH+2pCbO5JKYtHDrJDsgmOYI19pO2jeRTV62Aj8lQUBoOzU+lZs
rStLqwdC+gjw0rY8pLs2eHY04HAFG9aDfaVQD8jWNS3wmXEbkPNx3aCoEZQ2zoxbBogcCTBGHrid
Y96oWbVlLiFBAlVmtxZk6qgifSs+l11HFLbikEOBJhRGh0I8KY/fvozQ+5ocg6R0T1p8K0JqM0YK
O+qO+POJvD4X/9KrzhDQZVnCfs9e58az+JYqm4ZYaaUYQwELVHXmJj7taFuqWpSgSdxuaUNmFkg6
KAqQz8YKkxMRmc/7QXKClSSZ1EHtp4SVlZGhkaUh0nSemBTiIUsf3x51VBnknRlzD3gVDWuIJCtQ
emIrh+USDIUAaRWx6+mKIKc7k4qKsxAAOcadtKTlzgJzJ4gpi/ytx7QUpkZxB/CCiDPJFcO99wn/
AMTkDyq+0VEtdGDzFc9+9DcNB4jm8Bpz7qIM6lkgx9QXr61s+r4urLvRZ2epW4HBAEp+j1/OlRBD
OYa/R64+NMaEBjU/0ev51zRkMawRh64643rDarLq1K61vkWWcJ9tOh5wme/auXHtinbnCflSOEji
6kfWE+W1IswXQNg+nTs2ojarLqkKw2XTJCucJII8q1iMetLtm+Di+C4u7YUQqADGUGD4/CserQOz
oecJ8tq5ZJ4nX9YT8qIykHh1Yey39ziFi59JqbvWSOfMKlLgICZTrXX1/YMqxNC7xhsm+YUAXEjT
omYrAO6lzQfjCdI8KapKRxYQke3TrHhTOfhJObRsuYLbYryhw1kYkEXXHLl60tCWOnmAyyQRp1dt
ZnG8Ufxm8uHVJLVvzsLSyTrMASrqmB8TVFX50bgPpj4Urqp4qhEl9OnpRGTADh0YOymTbXDyXiy0
taU3CASlMhJMRPjWlwSyftLDEuMgtE3tuAlQgiD1jzFCLDGW8Osru3NqXFu3Ta82aAcpBg0QueVr
Thv8lov21004iVD8nLIP86Voylsdo6s/K0V7mnFAYMYgxv8Aq0l9ITipER9IMaH9Ws5d8rm3ef5L
JeZ66acTK492JB07qFYtj9/ifO0KysW790la0NEyYAAGbs8qZ6JJTaMd3L+ngUnKDEBiuN3dw2ZY
TcgN66KOgKvOBVJe7ukw+nz2pvQQHRB/DJgDq2rlkkuhRMh9OvpUqRtVl1afD+UFuLG5t7gcNfOG
MpAkEJyj1gTRm7xPD1oxOLu3VN8yqQ6nUDLJ32rAOKkulMxxk/KudIh2dy+n5Vo0pJzaMN1zBb27
u8LtzieR+1bm+ZVAUkSJSZ7xuarYryiwto4kUvh9S71paQx08wGWYI06u2sWpCU8UQDD6dY8KVzK
Q8oCBxk6elRGTQsuYK3jmLPYzeXTpSpu3NwlaGp1JgAFXVMekmmKeEXZIP4VsgelV3IHGH6TyflT
nP6yOx1HyoM8kbVZdUlxcauBGvTBjtqBRJKlb5iNOyjdhyUuMQsmrxN2wgPKISlQVmK5hKdBurWP
A9lWWORty7zgpumIaeKCoEqzKBGUCBrmzaeB7KpEEb9QiFnco6QV+kNRU4QpZVAIg7dwrT2nIW8v
EqWxd2jieItAUFnVSQdtO40/B+Ty3nlZlw2m0dcK0oKs4Byykde4qAhSM01XWH4WfRYLdOiYzoLv
kJ/lTvoswJXIWyXx5T/KtYxgC0tNOKuUN5bZ23AKVCVAxsRIkqG47ZiqzOCKvG7VIu0NEttMHMk6
8QKUI79COrxoQ7RmGZlo0kCqPLSH+vysgtE5jqOkDFcTAXA3WDR5HJe4csnLhVy2goLpSkgwoN5Z
g9pKtPA1I1yNu320ZH2kKXcllQWCmDlzbRPbuBQ/SIlZBBoq7QWcUkDOJkZwd6cTmzkmCFii5wNt
vnwdcWo26UuJhOWZIHX3GpnuStw0pCFXDedd6i30BgFQlPiNDPzoZs8cFWzz51cQqeHK6bsR+DXP
jFEGoBaGYRzFcd29S4bgqUN4itSsxZYKgrVOih2Ea7do86vYZgTl48hrjtAIsyk5Vhc5ioCCDB27
a26Z3x2UM7Jtl12IQ9vZgkgH6PX86Rsn2EEQMPX660WRyfcThzd8u4aCG7VxlQ1BzQdACO/4GrFp
yaCcTYtLp4lPM3EKU2NFEKjQnTZU1htAzsVlJ9IDf5MQvN3MoLxB05wnL3bVy59qFRIuE/Kiz/J9
1vDXb5T7RTzlv2c6wpIUIqV3kq+BdDnLWdu/LConUpKRpp2q+FDnmjJ9GFcOehiEDWNHSIgPp+VK
4YLvXL6flRK9wR63tFP8VLue7Q2EtpJkkAjq37jHdMGEdwZ9Nk5cqdbTmuEezMzEAztHWOuaGvO1
GVWXMUNWMpdSd+Onz2rnEzxiBoH0/KjL3Jq6S7cNm4YUEX3BUsFWiklIPV/e+HhMOJ4G/YM3Dq7h
lwIvENw2VbkSDqBpANDnmjJ4WXMQhbkS7odX0/KudTlLoI2fT57Urub2wiPbpn4UjmzsCRx0+PVR
G1WXVywFcUkf1hPypq93Ozjp07dqc4SeLO/HTEbdVIsqBe2B46fPaiNqsupHAAXdx7dPypFiOLO/
HHypXD+FgacZOh6tq5wiXZ1h9OvpQo2qy6kWJ4uuz6dPSuUdHCDEvjy2pV6B2dPbp07dqVUEudGI
fTI7NqI2qy6mr6KnATs+k/dXKEcSYTD6dOzanKgB3rHHTr6UjgEOSfz6fPahRtVl1IqSHDMy+nX0
py5l0SB7dOnpSL/O9vHTPwpVAe1AP59PyojarLqVcw8dvbp1PVtXOEkPn/GT8q5QEOzI9smPhSuD
R8/4yZ+FEbVZdRe2xW6tW2UWzzjXDaM5FESZUZ8YUR50rGIOsJUkOOoQpAVDbhHTGyvEH7zVEEjY
TpG1Wm0sFSZkgsqOk6Kgx8dfOrHPxgkdFphmnFXsOvn2VJ5u68ylNu4tWV0wpeVXSjqOvwqNfKC8
YSxza5fbU1b8DMlw6AmTHZ1egqq6+0GEJSYVwcqtN1Fc/dFV7ZSUvLLkZQFASJg5THxrAo3I4Qnz
S4dD0Vm3xi5ZDyTc3GVzMFBLhIJOkkHQ7nXvrmcTeSUhdxcBLMFASs+8AcvX1SdeqqrxbPDLZ1Sk
ZoEQZPrpFSANZzmAAyTpO8fzro1zozTZCQBic5/CvJx27Vaos3Hngw0lZKEq0WpXWrt18fiac3jt
6AgP3D60oaWE+0V7xCgFHXcZonsqiopyt5cqSGjO+8mP+jSkaWlG4B6BGo7vA/8AeyofqEDmhY0R
PNt7qRzELtxanHLl4uOCFrKzKx2E9dPvMav7x3iO3LiYWFBKVEBKgNwOo99UioR1Kpq4BOhGorK2
Js8EWs7+6ecuC5dPrLrS+IVOE5oGk9tXrO7ubdTRYuXGSbFRPDUUzGaNuyg+HqSFukx+Cck+VXG7
hILKQZnD3D/FXR3qFl1R3ps7PRNGI3K7BizLvsTaLeUCNVLhQmd6ajFLsrt3VXz5XzBagsumQZJJ
nyHoKFtvKXzaTlnDV7frVG0kq5sSSqcMcGp396sNqsuqyut7vLgv/9PBv4s+WHbdV48tkvpVw85K
TAAGm2wpruOXhLxFxcgruA4QXDqoxJOu5ga0PUmSqOt0aUi0KhcmfajWiNmhZdV9eOYgpKhzp4pR
cJcSC6egoQAR39U1G5jN4pl1g3DxZU8lfD4hyyI1jwFUyknMP8QQI3peEolRCYlwDWiCqy6rzmOX
zjjinLl8qL+f8KTqYJPiYHpXPYs++26lx95xKrhKyFqnUaA7771XTZOuZsqFKBeCZCZ1pqkNNyVK
Mh4DKOyhzzRtVl38Kc3AUHOkNXknXyp63lHiSnUviI2O1WF4ey3hou0PsqeVcp9gD0ggpBzeE6UK
eu3IWkBIHGnQazTPVG1WXSrxeHtCJA46SZHhSqUPaaT7dOnZtQ4XLgBCoMOA1KH0KKxOUl0Ez2aU
RtVl1XXCPazr7dOvpSOEe16vbp09KiUsgOQMwL4gU9TiTxJ34ydfSiNqsupy4l3T8+me7auWQQ50
pHHT8qVwZS7PRh9Mjt2pqiDxYH59Oh6tqI2qy6nORLoOh4ydO3akX+d/10z3bUi4l3Un26dfSuXH
tJP59PntRG1WXVywCHNZBfTr6U5e7oJg8dOg8qRce1MQS8nT0rlAe1G/t069lEbVZdTlCeNH/mTP
dtXOGQ+Z04yY+FI5HtjP55MfCnOA+36iXkz8KI2qy6rRbWknQjYgdo7aepwob6GmkGOqT/31oitl
K0shWn1MrEd00KcVmBOgIiagMVTM6GaSOyYQSVTqAoQqlIICuqFDTtpHFATB0zCuj3zM9MEVVBnk
npklXRGh9KkGm2ojrpiT0lAq1p8gglOwTVRL3bHLtTTMajYU7QDUySmR3VGtyNJ1CJqIkUpMb6D/
ALFQvXErV0dSZ0FIoqcggRptUjVhcv6tW7roUoICkIJE9nxoikw8lTi8xJ9i5PpVhCHC4wRP9GOC
Qf8ANRLBOS+IvqUothpJ4jEumDmjrG9F/wD6YftmbZxxaVQw6wtLY20Jmf8Aitumd8dsCo+dp4Ho
/ELP26COadv0Yuf3qcwkEW2szhqxp+tRFm0Q0bUZc0Wbidf1qjtkJSu1ASAOZOQf2qwJs8MFZWfS
t8mKxYaKioBKtXwBOlT2+HOXL6W0lIC7pKO2Nqm6yMv9b179qMYFbZlpeySPpJCfuqOmBtvYKsnL
d8OehintclLRCBxn3FufSSWCRCUxp1R86ut4TYW6AlNs2SnFgiVjMSnTTWrzsJkQYOMj5VXJAJmR
GMD5VZSYOt8mAUkZ9An+3xYn5ScNAa4baEhH0uBlAgDbqrB3zKmXnWlbouSk+VbhRkyCf6W1+FZb
HWcl68oSAq6UfOar/UTx6vSTna3gP4yaisblsWRaWgFYuYCiNcpA08NKF3Iha9PztTWyy3cKAGpd
BB7IP/NR3aeirUH2u4qHPNG0Z/tUMwTH6YpqzCierOKWN+5YpHB7xj8uiDPJWW3VAkFU+1BqzmQt
KgJTL407apIM+HEFWE7T/jihzzRtWf0qdRKc4KSZfA8KepQUHJM+2Tr6VGF6EETL41pVJmY1l8Dx
2oc80bVZdT168TSPbJkdu1csghwgTLyfLamFZUHCRB4w86ctWi463k/KiNqsupy4BczHTjJ19K5f
507e2TpPhTVGOINY44P3VxIPEJ34yflQo2qy6nrIPGjWXkz3bUrmnGlWnGTr27VGtR9rpu8mR6U5
yAHtNOMn5URtVl1GU3alM97LCmp7if8A9vhVB0zJzflCKUqKQoBWqiJ8KRSTCwQICgRrSuKs02a4
902Fap09/UVIhM5irUT8aaRnzQJOYVIo6EQNd6KDPJIZKjqNfjXFYbTmMRsdaVZSgKJgJGsmhV1e
quFkRAImIiaIrq79GcABSugde2q4vFqCSEgeyJ6XXVVO4AG7etcIgSDAa0oM8kNedqsm5cU4FgZP
Zk5U7DettyVxpF3bW9g+Uh1Nw06k7Zx7p89vWsFJ0J0Vwezxp7Fy5bvtutLUhTYBCknUEf8ANQzt
IzRDurQ6Ow9CT2XtGH6qcMRF8vb/ACir7YB4GmYFxfzoDyVxRvFrPjpgLVdFS0g7EpB++fSj7H5g
GZ4i4+NdJWk5/Ust9IG4dAs3iGHc2cYUkHhqaeSO7cx6H4UAT0XLQkERZOCP2q367dN0ww0oEAqc
EjqkEfOsO+1w1MJMhQtHRHYelWTTnaq/0k7j0disgTM7/jY2rVYM2G7FtJkEYsj1gVlEkbztdD5V
rbJ5LdilxRhIxVCoAmdBPyrL/Sbej1ZP1N9vWTVt1JUggSCMaHyqDhrUQTr9sAHu2qyozqCDGNCf
hSEwTqNcaEaeFWV1vd5FJGhnt8KpltwKMaA4uB4HShuI4U/eIhGVJ+klNyoxExvRrXXb+mR8qiOu
sJP2wNT5UlKXW+RJGhg+3wrMp5NONnjLeQVovuCUJnWI66FXdkttkKKAhHOC2FEyJ03rdKJ7tcXG
npQoNMl1Vq6gKbGJiQRIjY0fMTCqPV+CSc4bvhzEniVlbrD7i0fUw4ElansgIOkg1XdbUjOlYgpc
itRyms22GhcsJgJv1oTHUAARQG/TmPEH5bx89v51XTE8T3wRk4B3A8m4qolQOYxrxBpVhJ0Ij88K
qAkLUf74qwgyP/mFQ0Z3oKs7F//U83gGdNnxUzYUokBJM3AkVANv/nFWLdWV0HX8ZGvpR1edqNpF
l1OeZKc4KSAbiJ9KjVpxAqfwwjv2o0W232FIXOt+NhrBihdxbqbUtCxqLmJo6k524IygWXMVGR+E
mQQ8mmubuHWA8mfhSKJOfMelxhSqVHE6gXk/KhRtVl1OXoHZJ1eTHwrljR4bEPJn4U1X50/4wju2
pXFyHTm1LyflRG1WXVeMCdCK5SRBkaA70pOihGxk1ygIMDSd6IuJnx2pCpLaVKUco656qcYg5tDv
Qy7ueMspT7gST20SpNuLgvL6wjISBVUyYk65PSpNAU/6Z19ajJAif0NqIc809B1EGPZmaVGoT/pH
r2qNBhX6p8qeCIET+DImmeihzzXFUxKphvekkz2dH1pCf4dqSNf1d+ygVOea1vIbFfo/FUpWqGXB
K52SR1+Qn1r1Zifq8mPaLjv3rw/CSeKoz/V3Pur1nkniHP8AB8Pzrl1KRmkydtz4wa3KUWXfyoZj
nacEYZmbeB+Uv51lcZY4d4gpEpUw8duuVVq2QSbfXZa9fWg2NslTFs6NcofSR4g/yrLqc7XKn0ng
ehXkyDlBG8XY1rU4M9ns2VEapxVAI7QQn+VZTVLygOu50HnRrA3lZyyPeN+2pOvXMfOo+g8D0ckn
6m8W9WLSlW/X9tCdPCmHKCdI+2h8qdmzCQf7ZHntTZgmE/2yPlSV1vd5UkNT2+FMVlJM7/TA19Kj
MQdY+2BPwqQqGsjN9siD6UxR6JnT7YHntSV1vd5EkdT2+FRKCYOhAOL6921DrsBF5mJ97ESJ8CP5
0RUQQej/AGuJ+FUcQA4ClDXLih6ttB/KkpS63rKJJUN4DpJLsSSm+5Ou6jOnEzp3FH/FZRcLsB2p
uNvIVrMPSi4tXbdZyleIJj7vuNZTL7V5g/8Anj5VXeo2nm5GTtFg/axUFj2itZ6e9TI6z/ijzqJ0
CFkbcSIp6Tv28QVCgqzsVkSZH+OKkbOVYUOq4EGoge/8+KeNyRp9YHlQ152o2qy6jtuoqb315+kj
4U64Z4zaxAzC/gE+VVrJZLYTP9dSfDar2oOh/tER8KPrtvpJ1WeNA3mvfEQRcxEa1FPvzvxk/Kit
4yZW6AAeewR6UNeQUlxQEjnAE0dSbe6NoFl1NV+c/wBZOvbtXLP4T/WGkeFKvZyT+eTHftSrn2o2
PGTp6URtVl1EHEFA3GsE1ygBOmmkd1dXUQzKjfvFBUyN8hUT2jsqic0HUfgjXV1BnkhzzSkjoqiB
w9BUZ7DqQiurqgzyTPVNE5iR+jrTyRlBA0yaV1dVz0VOeaaQRKTrCaWNTp+TXV1RNqI4WfaL/wDt
3P4a2vIe7LOK2VsZKHrIE+IUY+811dXR1fDsFH0DP/ot8yn8XzGTnX86qXjXOMPSAY0c38FCurqw
6u28i8Yuk5XCof8AtmrWHOFq+ZVr+PJ+8V1dR9BtvIyltl1a5gEtQkwE4yAPKBTjOae3GgPurq6k
rre7ypI6nt8KYZBgmZxkEfCo8pgxAjGBHwrq6rKa1vkSR1Pb4VEpROkCfpff0qC6SVMOomQcT+Qr
q6j6XW+RJHU9viVPCF/WWU9uII+8UAv0cLF3UnX60Qe/pV1dUfSc1uRlAzUxD7kAKd7eKR5UxKok
a6uCa6uoaSoKs7FYB0P+sKk3BJ344rq6hoOdqrarLqv2S4gdXO0/Ki0aEgwPpAQOzaurqj6DbeRl
Is6sSKSHQpJnXEAPuoW8iC4knTncGurqrqTbeST1bOjFWWI4g/xwB3bVywTxROvGTr6V1dRG1WXV
/9k=

------=_NextPart_000_00CC_01C4AAE9.00205F80--



From karsten.festag@gmx.de  Tue Oct  5 21:44:47 2004
From: karsten.festag@gmx.de (Karsten Festag)
Date: Tue, 5 Oct 2004 22:44:47 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <20041005105018.GE7772@meier-geinitz.de>
References: <20041003125857.GG7885@meier-geinitz.de> <200410042352.55031.karsten.festag@gmx.de> <20041005105018.GE7772@meier-geinitz.de>
Message-ID: <200410052244.47533.karsten.festag@gmx.de>

--Boundary-00=_/ewYBvyf4+rPVX6
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

On Tuesday 05 October 2004 12:50, Henning Meier-Geinitz wrote:
> Hi,
>
> On Mon, Oct 04, 2004 at 11:52:55PM +0200, Karsten Festag wrote:
> > I recently replaced my old microtek parallelport scannner with an Epson
> > 2480 (what a difference!) and I think I will stop working on the
> > microtek2 backend. But finally I would like to commit the changes I
> > collected in the last time so they don't get lost. Henning, I'll send you
> > the current files for the CVS, (I don't think I will need CVS access).
> > They include the changes you made.
>
> One issue:
> (line 4657):
>     if ( !(md->revision=='2.70') && (md->model_flags & MD_RII_TWO_BYTES) )
>
> That looks strange. I've removed the quotes around the 2.70 but you
> should double-check if that works.

It's o.k., the quotes were a mistake.

>
> I've committed your backend to CVS now.

Thanks! 
>
> What about the microtek2.desc file? Shouldn't at least the version
> number (currently 0.95) be increased? Why not just use the build number?
>
> Is the Microtek Colorpage-EP a newly supported scanner? That one
> should also show up in our scanner lists. Is it support complete,
> good, basic or minimal?

The Genius ColorPage-EP is a OEM version of the Microtek Scanmaker V300. It 
has an additional firmware peculiarity I had to handle so that the support is 
good, like the V300.
I attach the updated microtek2.desc file. I called the recent version 0.96, I 
used the build number only for internal referencing. Could you please change 
MICROTEK2_MINOR in microtek2.h accordingly?

>
> > I tried to test todays CVS version on my old machine with the old scanner
> > and I experienced a compilation problem:
>
> That was my fault. It's fixed now.

I tested again and I get some other errors:

gcc -o sane-find-scanner sane-find-scanner.o 
check-usb-chip.o ../backend/.libs/sane_strstatus.o  ../sanei/libsanei.a ../lib/liblib.a 
-lnsl -lm /usr/lib/libjpeg.so
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
.../sanei/libsanei.a(sanei_scsi.o): In function `lx_mk_devicename':
:2491: undefined reference to `rsm_open_device'
:2491: undefined reference to `rsm_open_device'
.../sanei/libsanei.a(sanei_scsi.o): In function `get_max_buffer_size':
:781: undefined reference to `rsm_open_device'
.../sanei/libsanei.a(sanei_scsi.o): In function `sanei_scsi_open_extended':
:1245: undefined reference to `rsm_open_device'
:1245: undefined reference to `rsm_open_device'
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Could not find abbrev number 186.
.../sanei/libsanei.a(sanei_config.o): In function `sanei_config_read':
sanei_config.o(.text+0x36): undefined reference to `__ctype_b_loc'
sanei_config.o(.text+0x51): undefined reference to `__ctype_b_loc'
.../sanei/libsanei.a(sanei_config.o): In function 
`sanei_config_skip_whitespace':
sanei_config.o(.text+0xaa): undefined reference to `__ctype_b_loc'
.../sanei/libsanei.a(sanei_config.o): In function `sanei_config_get_string':
sanei_config.o(.text+0xf3): undefined reference to `__ctype_b_loc'
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
.../sanei/libsanei.a(sanei_usb.o): In function `sanei_usb_open':
:720: undefined reference to `rsm_open_device'
.../sanei/libsanei.a(sanei_usb.o): In function `sanei_usb_init':
:276: undefined reference to `rsm_open_device'
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
.../sanei/libsanei.a(sanei_init_debug.o): In function `sanei_init_debug':
:81: undefined reference to `__ctype_toupper_loc'
collect2: ld returned 1 exit status
make[1]: *** [sane-find-scanner] Fehler 1
make[1]: Verlassen des Verzeichnisses 
Verzeichnis /home/karsten/tmp/sane-backends/tools
make: *** [all-recursive] Fehler 1


>
> By the way: Could you change all references (e.g. on your website) to
> mostang.com to www.sane-project.org?

If I didn't forget something, this is done now.

Bye, Karsten

--Boundary-00=_/ewYBvyf4+rPVX6
Content-Type: text/plain;
  charset="iso-8859-1";
  name="microtek2.desc"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="microtek2.desc"

;
; SANE Backend specification file
;
; It's basically emacs-lisp --- so ";" indicates comment to end of line.
; All syntactic elements are keyword tokens, followed by a string or
;  keyword argument, as specified.
;
; ":backend" *must* be specified.
; All other information is optional (but what good is the file without it?).
;

:backend "microtek2"              ; name of backend
:version "0.96"                   ; version of backend
;:status :alpha                   ; :alpha, :beta, :stable, :new
:manpage "sane-microtek2"         ; name of manpage (if it exists)
:url "http://karstenfestag.gmxhome.de"

:devicetype :scanner              ; start of a list of devices....

:mfg "Microtek"                   ; name a manufacturer
:url "http://www.microtek.com/"

:model "ScanMaker E3plus"
:interface "Parport"
:status :complete

:model "ScanMaker E3plus"         ; name models for above-specified mfg.
:interface "SCSI"
:status :complete

:model "ScanMaker X6"
:interface "SCSI"
:status :complete

:model "ScanMaker X6EL"
:interface "SCSI"
:status :basic

:model "ScanMaker X6USB"
:interface "USB"
:status :good

:model "ScanMaker V300"
:interface "SCSI"
:status :good

:model "ScanMaker V300"
:interface "Parport"
:status :good

:model "ScanMaker V310"
:interface "SCSI"
:status :basic

:model "ScanMaker V310"
:interface "Parport"
:status :basic

:model "ScanMaker V600"
:interface "SCSI"
:status :basic

:model "ScanMaker V600"
:interface "Parport"
:status :basic

:model "ScanMaker 330"
:interface "SCSI"
:status :basic

:model "ScanMaker 630"
:interface "SCSI"
:status :basic

:model "ScanMaker 636"
:interface "SCSI"
:status :complete

:model "ScanMaker 9600XL"
:interface "SCSI"
:comment "only flatbed mode ?"
:status :good

;:model "ScanMaker 9600XL"
;:interface "SCSI"
;:status :minimal

:model "Phantom 330CX"
:interface "Parport"
:status :complete

:model "SlimScan C3"
:interface "Parport"
:status :complete

:model "Phantom 636"
:interface "SCSI"
:status :complete

:model "Phantom 636CX"
:interface "Parport"
:status :complete

:model "SlimScan C6"
:interface "USB"
:status :complete

:model "ScanMaker V6USL"
:interface "SCSI"
:status :complete

:model "ScanMaker V6USL"
:interface "USB"
:status :complete

:model "ScanMaker X12USL"
:interface "SCSI"
:comment "only Flatbed mode ?"
:status :good

:mfg "Vobis"
:url "http://www.vobis.de/"

:model "HighScan"                 ; name models for above-specified mfg.
:interface "SCSI"
:comment "only E3plus based models"
:status :complete

:mfg "Scanport"
:url "http://www.scanport.com/"
:model "SQ300"
:interface "Parport?"
:status :basic

:model "SQ2030"
:interface "Parport"
:status :basic

:model "SQ4836"
:interface "SCSI"
:status :basic

:mfg "Genius"
:url "http://www.geniusmouse.co.uk/"
:model "ColorPage-EP"
:interface "Parport"
:status :good


--Boundary-00=_/ewYBvyf4+rPVX6--


From gerhard@gjaeger.de  Wed Oct  6 07:42:50 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Wed, 6 Oct 2004 08:42:50 +0200
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <00cb01c4ab0a$8731ff80$6601a8c0@khp5000elaptop>
References: <00cb01c4ab0a$8731ff80$6601a8c0@khp5000elaptop>
Message-ID: <200410060842.50352.gerhard@gjaeger.de>

Hi,

On Tuesday 05 October 2004 20:38, Kenneth H. Peters wrote:
> I am using the following:
> *	IXP425 Big-endian
> *	MontaVista 2.4.18 kernel
> *	SANE 1.0.14
> *	Plustek backend
> *	Scanimage as frontend
> *	Canon LiDE 30
> *	USB 1.1
> Issue: Able to scan with "-mode Gray" and "-mode Binary", however using
> "Color" produces images as shown in image-segment below.
> Analysis: Seems to be getting 1/3 more data in the X direction that is
> "wrapping" around the image in the X direction.
>
> I am interested in learning if anyone has seen this behavior.
>
looks strange, can you please test again with the latest CVS snapshot?
I've no problems here.

Gerhard



From gerhard@gjaeger.de  Wed Oct  6 07:57:42 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Wed, 6 Oct 2004 08:57:42 +0200
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <00cb01c4ab0a$8731ff80$6601a8c0@khp5000elaptop>
References: <00cb01c4ab0a$8731ff80$6601a8c0@khp5000elaptop>
Message-ID: <200410060857.42745.gerhard@gjaeger.de>

Hi,

On Tuesday 05 October 2004 20:38, Kenneth H. Peters wrote:
> I am using the following:
> *	IXP425 Big-endian
> *	MontaVista 2.4.18 kernel
> *	SANE 1.0.14
> *	Plustek backend
> *	Scanimage as frontend
> *	Canon LiDE 30
> *	USB 1.1
>
in my first post, I missed the "Big-endian" issue!!!!
As I don't have a big endian machine available, it might be, that
there's such a problem.
Can you please do a scan @ 50dpi and @300dpi, always with
SANE_DEBUG_PLUSTEK=20 ?
Send us these outputs. 

Ciao, 
  Gerhard



From scottf@bigpond.net.au  Wed Oct  6 09:59:47 2004
From: scottf@bigpond.net.au (scott fagg)
Date: Wed, 6 Oct 2004 18:59:47 +1000
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain>
References: <415BD75B.1060103@bigpond.net.au> <200410021716.46218.Oliver.Schwartz@gmx.de>
 <Pine.LNX.4.53.0410041806350.16694@localhost.localdomain>
 <200410042026.59822.Oliver.Schwartz@gmx.de> <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain>
Message-ID: <Pine.LNX.4.53.0410061856300.13865@localhost.localdomain>

On Tue, 5 Oct 2004, scott fagg wrote:

> Date: Tue, 05 Oct 2004 06:25:57 +1000
> From: scott fagg <scottf@bigpond.net.au>
> To: Oliver Schwartz <Oliver.Schwartz@gmx.de>
> Cc: sane-devel@lists.alioth.debian.org
> Subject: Re: [sane-devel] epson 2580 problems
>
> On Mon, 4 Oct 2004, Oliver Schwartz wrote:
>
> > Date: Mon, 04 Oct 2004 20:26:57 +0200
> > From: Oliver Schwartz <Oliver.Schwartz@gmx.de>
> > To: sane-devel@lists.alioth.debian.org
> > Subject: Re: [sane-devel] epson 2580 problems
> >
> > Hi,
> >
> > > > please repeat the test by running
> > > > "SANE_DEBUG_SNAPSCAN=255 scanimage >/tmp/junk.bin 2>debug.log"
> > > > and send me the debug.log file.
> > >
> > > I've sent you a copy directly.
> >
> > The first three lines of the log read
> >
> > [sanei_debug] Setting debug level of snapscan to 255.
> > [snapscan] sane_snapscan_init
> > [snapscan] sane_snapscan_init: Snapscan backend version 1.4.35
> >
> > And later
> >
> > [snapscan] sane_snapscan_open (after firmware upload): "EPSON
> > Scanner1" is not a supported scanner
> >
> > It seems you're using an old version of the snapscan backend. The
> > backend revision should say "1.4.40" if you use the CVS version.
> > Since you wrote earlier that you're using a fairly recent CVS
> > snapshot you probably have two versions of SANE installed (e.g. one
> > in /usr/lib/sane and one in /usr/local/lib/sane).
>
> That might explain why i had some success earlier on, but none now. I'll
> track down all copies, clean up and try again.

Using the latest drivers helps and i can now scan, however preview doesn't
work. At least i can get an image out of it now.

It seems to only preview either the area of the most recent scan or
nothing, and then stretches that image vertically to fit the A4 scannable
area and shows that as a preview.

>
> >
> > /Oliver
> >
> > --
> > sane-devel mailing list: sane-devel@lists.alioth.debian.org
> > http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> > Unsubscribe: Send mail with subject "unsubscribe your_password"
> >              to sane-devel-request@lists.alioth.debian.org
> >
>
> --
> scottf@bigpond.net.au
>
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org
>

--
scottf@bigpond.net.au



From henning@meier-geinitz.de  Wed Oct  6 12:09:02 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 6 Oct 2004 13:09:02 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <200410052244.47533.karsten.festag@gmx.de>
References: <20041003125857.GG7885@meier-geinitz.de> <200410042352.55031.karsten.festag@gmx.de> <20041005105018.GE7772@meier-geinitz.de> <200410052244.47533.karsten.festag@gmx.de>
Message-ID: <20041006110901.GC10804@meier-geinitz.de>

Hi,

On Tue, Oct 05, 2004 at 10:44:47PM +0200, Karsten Festag wrote:
> The Genius ColorPage-EP is a OEM version of the Microtek Scanmaker V300. It 
> has an additional firmware peculiarity I had to handle so that the support is 
> good, like the V300.
> I attach the updated microtek2.desc file. I called the recent version 0.96, I 
> used the build number only for internal referencing. Could you please change 
> MICROTEK2_MINOR in microtek2.h accordingly?

Done. I've also removed the Genius from the unsupported scanners list.

> > > I tried to test todays CVS version on my old machine with the old scanner
> > > and I experienced a compilation problem:
> >
> > That was my fault. It's fixed now.
> 
> I tested again and I get some other errors:
> 
> gcc -o sane-find-scanner sane-find-scanner.o 
> check-usb-chip.o ../backend/.libs/sane_strstatus.o  ../sanei/libsanei.a ../lib/liblib.a 
> -lnsl -lm /usr/lib/libjpeg.so
> /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.

Check what the dwarfs are doing inside your computer :-)
I've never seen such an error message.

> /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
> /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
> .../sanei/libsanei.a(sanei_scsi.o): In function `lx_mk_devicename':
> :2491: undefined reference to `rsm_open_device'

Looks like linking to the resource manage library failed. In fact,
it's not in the list of linked libraries after the gcc command.

However, the call is inside #ifdef HAVE_RESMGR so something must have
defined that.

Does the same happen after "make distclean; ./configure; make"?

In this case, check config.log for "resmgr".

There is a small error in the configure script that I've fixed now in
CVS. However, I'm not sure if it can cause that misdetection.


> .../sanei/libsanei.a(sanei_config.o): In function `sanei_config_read':
> sanei_config.o(.text+0x36): undefined reference to `__ctype_b_loc'
> sanei_config.o(.text+0x51): undefined reference to `__ctype_b_loc'

That's even more strange. Looks like some internal error?

Can you please show us the compilation warnings you get in sanei/ (not
only the linker errors)?


Bye,
  Henning


From vsu@altlinux.ru  Wed Oct  6 12:47:52 2004
From: vsu@altlinux.ru (Sergey Vlasov)
Date: Wed, 6 Oct 2004 15:47:52 +0400
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <200410052244.47533.karsten.festag@gmx.de>
References: <20041003125857.GG7885@meier-geinitz.de> <200410042352.55031.karsten.festag@gmx.de> <20041005105018.GE7772@meier-geinitz.de> <200410052244.47533.karsten.festag@gmx.de>
Message-ID: <20041006114752.GA14845@master.mivlgu.local>

--ZPt4rx8FFjLCG7dd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Oct 05, 2004 at 10:44:47PM +0200, Karsten Festag wrote:
> .../sanei/libsanei.a(sanei_config.o): In function `sanei_config_read':
> sanei_config.o(.text+0x36): undefined reference to `__ctype_b_loc'
> sanei_config.o(.text+0x51): undefined reference to `__ctype_b_loc'

Looks like this object file was compiled with glibc-2.3.x headers, but is
being linked with an older glibc.  This won't work - run "make clean" and
recompile everything with the proper headers.

> /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.

This also might be caused by "too recent" object files from another
machine.

--ZPt4rx8FFjLCG7dd
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBY9toW82GfkQfsqIRAoPJAKCBiUsIxWQ9MMq7qZZGtJFqrOMvJACeLbcC
YpdUTteMohrlPvuxad5R6es=
=ckQD
-----END PGP SIGNATURE-----

--ZPt4rx8FFjLCG7dd--


From Chris McKeever <techjedi@gmail.com>  Wed Oct  6 19:22:31 2004
From: Chris McKeever <techjedi@gmail.com> (Chris McKeever)
Date: Wed, 6 Oct 2004 13:22:31 -0500
Subject: [sane-devel] strange problems
Message-ID: <d9aa9070410061122270e5a94@mail.gmail.com>

I have been wrestling with this for a while now, and not turning up
much through searching the web.  I have installed SANE 
sane-backends-1.0.14 and have a CANON lide30 scanner.
At low resolutions it will process fine.  If I go to 300 is fails at
about 75% and anyhting higher wont even start.

I had it working with an LIDE20 - until that unit crapped out - the
optic bar would just pin itself to the edge and grind.

I am connecting to the SANE backend via XSANE from a remote linux box
as well as a remote windows box - very similar results (the connection
itself works, just scanning isnt working well)

Any suggestions?

thanks


From Oliver.Schwartz@gmx.de  Wed Oct  6 19:29:47 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Wed, 6 Oct 2004 20:29:47 +0200
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <Pine.LNX.4.53.0410061856300.13865@localhost.localdomain>
References: <415BD75B.1060103@bigpond.net.au> <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain> <Pine.LNX.4.53.0410061856300.13865@localhost.localdomain>
Message-ID: <200410062029.50935.Oliver.Schwartz@gmx.de>

Hi,

> Using the latest drivers helps and i can now scan, however preview
> doesn't work. At least i can get an image out of it now.
>
> It seems to only preview either the area of the most recent scan or
> nothing, and then stretches that image vertically to fit the A4
> scannable area and shows that as a preview.

Please send me a debug log of a preview scan.

/Oliver


From Chris McKeever <techjedi@gmail.com>  Wed Oct  6 20:29:33 2004
From: Chris McKeever <techjedi@gmail.com> (Chris McKeever)
Date: Wed, 6 Oct 2004 14:29:33 -0500
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <d9aa9070410061122270e5a94@mail.gmail.com>
References: <d9aa9070410061122270e5a94@mail.gmail.com>
Message-ID: <d9aa90704100612297776dd31@mail.gmail.com>

some more tests get me some new results.

1 - I have noticed that with 3 different USB 2.0 cards, that the
scanner will not register itself as a USB 2.0 device, it only
registers as a 1.1 (CD Wiriters register as 2.0, so I know that the
card and the kernel are recognizing it properly)

2 - I moved the scanner to the built-in USB 1.1 port, and I was able
to finish a scan at 300 DPI and 600 DPI (although it takes quite some
time)
3

3 - 1200 DPI still hangs, and letting it sit, I get: error during
read: error during device I/O.

any suggestions?

thanks




On Wed, 6 Oct 2004 13:22:31 -0500, Chris McKeever <techjedi@gmail.com> wrote:
> I have been wrestling with this for a while now, and not turning up
> much through searching the web.  I have installed SANE
> sane-backends-1.0.14 and have a CANON lide30 scanner.
> At low resolutions it will process fine.  If I go to 300 is fails at
> about 75% and anyhting higher wont even start.
> 
> I had it working with an LIDE20 - until that unit crapped out - the
> optic bar would just pin itself to the edge and grind.
> 
> I am connecting to the SANE backend via XSANE from a remote linux box
> as well as a remote windows box - very similar results (the connection
> itself works, just scanning isnt working well)
> 
> Any suggestions?
> 
> thanks
>


From karsten.festag@gmx.de  Wed Oct  6 20:34:07 2004
From: karsten.festag@gmx.de (Karsten Festag)
Date: Wed, 6 Oct 2004 21:34:07 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <20041006110901.GC10804@meier-geinitz.de>
References: <20041003125857.GG7885@meier-geinitz.de> <200410052244.47533.karsten.festag@gmx.de> <20041006110901.GC10804@meier-geinitz.de>
Message-ID: <200410062134.07871.karsten.festag@gmx.de>

Hi,

>
> Check what the dwarfs are doing inside your computer :-)
> I've never seen such an error message.
>
> > /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM
....
> Does the same happen after "make distclean; ./configure; make"?
>
The dwarfs went back to work after "make distclean"! ;-) Sorry, that should 
have been my idea.
Testing with my scanner (Phantom330CX, Parport) was successful, so I 
personally have no objections against releasing this code.

all the best,

Karsten


From jurekt@kabatnet.waw.pl  Wed Oct  6 21:50:28 2004
From: jurekt@kabatnet.waw.pl (jurek Ela Tryjarscy)
Date: Wed, 06 Oct 2004 22:50:28 +0200
Subject: [sane-devel] No device available
Message-ID: <41645A94.1060007@kabatnet.waw.pl>

Hi ,
In my box I have Redhat 9.
I must connect via SCSI Interface Umax Mirage II scanner.
SCSI adapter is Acard AEC-6712TU.


During startup of computer the following communique appears:

    ROM Address: C800h
    I/O Port :           1000h
    IRQ Number  :    11(level)

SCANNING SCSI DEVICE

ID=    1    06(scanner)        UMAX    MIRAGE II    v1.4
ID=    7    * Host Adapter

NO HARD DIASK DETECT.    ON-BOARD BIOS DISABLE ...

( On the same box on another disk I've intalled Windows 98 and 
MgicScan32 V4.3 - scaner function well. )

Linux System logs contain:

Oct  4 19:19:05 localhost kernel:    ACARD AEC-671X PCI Ultra/W SCSI-3 
Host Adapter: 0    IO:1000, IRQ:11.
Oct  4 19:19:05 localhost kernel:          ID:  7  Host Adapter
Oct  4 19:19:05 localhost kernel: scsi0 : ACARD AEC-6710/6712/67160 PCI 
Ultra/W/LVD SCSI-3 Adapter Driver V2.6+ac

information.

Driver is atp870u.

My qustion is:
How to install correctly the scanner and the scsi adapter - I must make 
any mistake.
I do:
modprobe sg
modprobe atp870u

[root@localhost scsi]# lsmod
Module                  Size  Used by    Not tainted
atp870u                23856   0  (unused)
sg                     36524   0  (unused)
scsi_mod              107160   2  [atp870u sg]
ide-cd                 35676   0  (autoclean)
cdrom                  33728   0  (autoclean) [ide-cd]
parport_pc             19076   1  (autoclean)
lp                      8996   0  (autoclean)
parport                37056   1  (autoclean) [parport_pc lp]
autofs                 13268   0  (autoclean) (unused)
8139too                18120   1
mii                     3976   0  [8139too]
keybdev                 2976   0  (unused)
mousedev                5492   1
hid                    22148   0  (unused)
input                   5888   0  [keybdev mousedev hid]
usb-uhci               26348   0  (unused)
usbcore                78816   1  [hid usb-uhci]
ext3                   70784   2
jbd                    51892   2  [ext3]

[root@localhost root]# ls  /proc/scsi
atp870u  scsi

[root@localhost scsi]# more  scsi
Attached devices: none

I think it should be also sg directory in  /proc/scsi

[root@localhost root]# sane-find-scanner

# No SCSI scanners found. If you expected something different, make sure 
that
# you have loaded a SCSI driver for your SCSI adapter.
# Also you need support for SCSI Generic (sg) in your operating system.
# If using Linux, try "modprobe sg".

Can anyone help me ?

Jurek



From brian@aljex.com  Wed Oct  6 22:07:46 2004
From: brian@aljex.com (Brian K. White)
Date: Wed, 6 Oct 2004 17:07:46 -0400
Subject: [sane-devel] Re: strange problems LIDE30
References: <d9aa9070410061122270e5a94@mail.gmail.com> <d9aa90704100612297776dd31@mail.gmail.com>
Message-ID: <00af01c4abe8$98a1f610$6800000a@venti>

Chris McKeever wrote:
> some more tests get me some new results.
>
> 1 - I have noticed that with 3 different USB 2.0 cards, that the
> scanner will not register itself as a USB 2.0 device, it only
> registers as a 1.1 (CD Wiriters register as 2.0, so I know that the
> card and the kernel are recognizing it properly)
>
> 2 - I moved the scanner to the built-in USB 1.1 port, and I was able
> to finish a scan at 300 DPI and 600 DPI (although it takes quite some
> time)
> 3
>
> 3 - 1200 DPI still hangs, and letting it sit, I get: error during
> read: error during device I/O.
>
> any suggestions?
>
> thanks
>
>
>
>
> On Wed, 6 Oct 2004 13:22:31 -0500, Chris McKeever
> <techjedi@gmail.com> wrote:
>> I have been wrestling with this for a while now, and not turning up
>> much through searching the web.  I have installed SANE
>> sane-backends-1.0.14 and have a CANON lide30 scanner.
>> At low resolutions it will process fine.  If I go to 300 is fails at
>> about 75% and anyhting higher wont even start.
>>
>> I had it working with an LIDE20 - until that unit crapped out - the
>> optic bar would just pin itself to the edge and grind.
>>
>> I am connecting to the SANE backend via XSANE from a remote linux box
>> as well as a remote windows box - very similar results (the
>> connection itself works, just scanning isnt working well)
>>
>> Any suggestions?
>>
>> thanks

LiDE 30  _IS_ only a usb 1.1 device.
There are sloppily written advertisements on various shopping sites that 
list it as usb2.0 but in truth, the lide30 is usb1.1
Later lide50 is usb2.0
go to the canon site instead of guessing or trusting others (hey, including 
me :)

I have a 30 and a 2.0 card and went through the same motions you are and 
finally I did what I should have done first and consulted the only 
authoritative source and all mysteries were solved.

I never tried to scan at 1200 though, trying now...
Working...
It's going but incredibly slowly at 2400 full color (what bit depth is "full 
color"?)
The manufacturer says that it does 1200x2400 optically, but xsane only 
offers a listbox that says a single value from 0 to 2400, no XXXxYYY 
choices, so I picked 2400 just to go for a worst case scenario but I have no 
idea what it's actually going to do.
A lie, only actualy produce 1200x1200? a distorted image? silently double 
every pixel in one direction? silently double every pixel in both 
directions? or maybe the scanner will do the doubling in one direction in 
firmware and present sane with 2400x2400 data?

It's only at about 10 or 15% progress after 20 minutes so I'll send another 
post when it's done, or when it crashes.
This box has a gig of ram so hopefully it's enough for this worst-case 
scenario if sane doesn't open a file and work with smaller chunks in ram. 
This is a dual 1gig p3 too. That might be relevant by making it more likely 
that there is always a cpu available to service the usb interrups? Or 
rather, that the one cpu that seems to be the only one that even sees 
interrupts, is more likely to be able to keep up.

It's basically a straight suse personal 9.1 with yast configured to use 
ftp.ale.org

Brian K. White  --  brian@aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani



From henning@meier-geinitz.de  Wed Oct  6 22:19:27 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 6 Oct 2004 23:19:27 +0200
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <00af01c4abe8$98a1f610$6800000a@venti>
References: <d9aa9070410061122270e5a94@mail.gmail.com> <d9aa90704100612297776dd31@mail.gmail.com> <00af01c4abe8$98a1f610$6800000a@venti>
Message-ID: <20041006211926.GA4132@meier-geinitz.de>

Hi,

On Wed, Oct 06, 2004 at 05:07:46PM -0400, Brian K. White wrote:
> The manufacturer says that it does 1200x2400 optically, but xsane only 
> offers a listbox that says a single value from 0 to 2400, no XXXxYYY 
> choices, so I picked 2400 just to go for a worst case scenario but I have 
> no idea what it's actually going to do.
> A lie, only actualy produce 1200x1200? a distorted image? silently double 
> every pixel in one direction? silently double every pixel in both 
> directions? or maybe the scanner will do the doubling in one direction in 
> firmware and present sane with 2400x2400 data?

As it doesn't make sense to crete distorted images SANE backends
usually either duplicate pixels or interpolate them.

I've seen several Windows drivers that interpolate even if it's not
necessary: E.g. harware resolution 100 and 200 dpi, driver uses 100
dpi when asked for 200.

Also some scanners are advertized to make 600x1200 dpi but can't do
(and don't do) 1200 dpi even vertically. It looks like nobody ever
checked what the Windows driver really scans.

I don't know what's the case with the LiDEs, however.

> It's only at about 10 or 15% progress after 20 minutes so I'll send another 
> post when it's done, or when it crashes.

At least with the scanners supported by the gt68xx backend, a low scan
width is important for higher speed at high resolutions. As you
usually use high resolutions for smaller sections of photos or slides
that's not that unreasonable.

> This box has a gig of ram so hopefully it's enough for this worst-case 
> scenario if sane doesn't open a file and work with smaller chunks in ram. 
> This is a dual 1gig p3 too. That might be relevant by making it more likely 
> that there is always a cpu available to service the usb interrups? Or 
> rather, that the one cpu that seems to be the only one that even sees 
> interrupts, is more likely to be able to keep up.

One of the problems is that libusb doesn't allow async i/o. So you
can't send some buffers to be filled and wait for their completion.

Bye,
  Henning


From adeuring@gmx.net  Wed Oct  6 22:30:46 2004
From: adeuring@gmx.net (abel deuring)
Date: Wed, 06 Oct 2004 23:30:46 +0200
Subject: [sane-devel] No device available
In-Reply-To: <41645A94.1060007@kabatnet.waw.pl>
References: <41645A94.1060007@kabatnet.waw.pl>
Message-ID: <41646406.6060704@gmx.net>

jurek Ela Tryjarscy wrote:
> Hi ,
> In my box I have Redhat 9.
> I must connect via SCSI Interface Umax Mirage II scanner.
> SCSI adapter is Acard AEC-6712TU.

> Linux System logs contain:
> 
> Oct  4 19:19:05 localhost kernel:    ACARD AEC-671X PCI Ultra/W SCSI-3 
> Host Adapter: 0    IO:1000, IRQ:11.
> Oct  4 19:19:05 localhost kernel:          ID:  7  Host Adapter
> Oct  4 19:19:05 localhost kernel: scsi0 : ACARD AEC-6710/6712/67160 PCI 
> Ultra/W/LVD SCSI-3 Adapter Driver V2.6+ac

I have never used the atp870u driver, but I assume that this driver 
should print some message about the devices it detected on the bus as 
other drivers do. In other words: for some reason it could not find the 
scanner.

> My qustion is:
> How to install correctly the scanner and the scsi adapter - I must make 
> any mistake.
> I do:
> modprobe sg
> modprobe atp870u
> 
> [root@localhost scsi]# lsmod
> Module                  Size  Used by    Not tainted
> atp870u                23856   0  (unused)
> sg                     36524   0  (unused)
> scsi_mod              107160   2  [atp870u sg]
> ide-cd                 35676   0  (autoclean)
> cdrom                  33728   0  (autoclean) [ide-cd]
> parport_pc             19076   1  (autoclean)
> lp                      8996   0  (autoclean)
> parport                37056   1  (autoclean) [parport_pc lp]
> autofs                 13268   0  (autoclean) (unused)
> 8139too                18120   1
> mii                     3976   0  [8139too]
> keybdev                 2976   0  (unused)
> mousedev                5492   1
> hid                    22148   0  (unused)
> input                   5888   0  [keybdev mousedev hid]
> usb-uhci               26348   0  (unused)
> usbcore                78816   1  [hid usb-uhci]
> ext3                   70784   2
> jbd                    51892   2  [ext3]
> 
> [root@localhost root]# ls  /proc/scsi
> atp870u  scsi
> 
> [root@localhost scsi]# more  scsi
> Attached devices: none

here you should get 3 lines describing the scanner.

> 
> I think it should be also sg directory in  /proc/scsi

yes -- but I don't know, if the SG driver creates this directory, if it 
does not see any devices.

> 
> [root@localhost root]# sane-find-scanner
> 
> # No SCSI scanners found. If you expected something different, make sure 
> that

that's because sane-find-scanner simply reads /proc/scsi/scsi, and this 
file is empty.

> # you have loaded a SCSI driver for your SCSI adapter.
> # Also you need support for SCSI Generic (sg) in your operating system.
> # If using Linux, try "modprobe sg".
> 
> Can anyone help me ?

I don't have a really good hint. The core problem is that the atp870u 
driver does not find the scanner, hence any attempt to access it will 
fail. Unfortunately the kernel sources don't seem to contain useful 
documentation e.g. about module parameters.

A very simple attempt could be to issue the command

	echo "scsi add-single-device 0 0 6 0" > /proc/scsi/scsi

If the atp870u driver performs a bus reset and does not wait long enough 
for SCSI devices to finish their "reset procedure", it will not find the 
scanner, when it scans the bus for devices after the reset.

Abel


From Chris McKeever <techjedi@gmail.com>  Wed Oct  6 22:45:05 2004
From: Chris McKeever <techjedi@gmail.com> (Chris McKeever)
Date: Wed, 6 Oct 2004 16:45:05 -0500
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <20041006211926.GA4132@meier-geinitz.de>
References: <d9aa9070410061122270e5a94@mail.gmail.com>
 <d9aa90704100612297776dd31@mail.gmail.com>
 <00af01c4abe8$98a1f610$6800000a@venti>
 <20041006211926.GA4132@meier-geinitz.de>
Message-ID: <d9aa9070410061445229ab527@mail.gmail.com>

On Wed, 6 Oct 2004 23:19:27 +0200, Henning Meier-Geinitz
<henning@meier-geinitz.de> wrote:
> Hi,
> 
> On Wed, Oct 06, 2004 at 05:07:46PM -0400, Brian K. White wrote:
> > The manufacturer says that it does 1200x2400 optically, but xsane only
> > offers a listbox that says a single value from 0 to 2400, no XXXxYYY
> > choices, so I picked 2400 just to go for a worst case scenario but I have
> > no idea what it's actually going to do.
> > A lie, only actualy produce 1200x1200? a distorted image? silently double
> > every pixel in one direction? silently double every pixel in both
> > directions? or maybe the scanner will do the doubling in one direction in
> > firmware and present sane with 2400x2400 data?
> 
> As it doesn't make sense to crete distorted images SANE backends
> usually either duplicate pixels or interpolate them.
> 
> I've seen several Windows drivers that interpolate even if it's not
> necessary: E.g. harware resolution 100 and 200 dpi, driver uses 100
> dpi when asked for 200.
> 
> Also some scanners are advertized to make 600x1200 dpi but can't do
> (and don't do) 1200 dpi even vertically. It looks like nobody ever
> checked what the Windows driver really scans.
> 
> I don't know what's the case with the LiDEs, however.
> 
> > It's only at about 10 or 15% progress after 20 minutes so I'll send another
> > post when it's done, or when it crashes.
> 


Thanks for the input thus far - I have some new results/information


I did some remote scanning tests with the scanner hooked up to a
mandrake10 box (2.6.xx kernel).  The delay in starting to scan was not
as intrusive as it is on the RH7.3 box (2.4.18 kernel).

In fact - it was able to scan at 1200 DPI, whereas when using the
RH7.3 box it just would timeout

I upped the memory in the RH box - and still the same result.  SO now
there are three main differences with the MDK and RH box - the kernel
and the CPU:

1 - the RH box has 1.0.14 and the MDK box 1.0.13
2 - the kernel - 2.4 uses scanner.o and 2.6 uses libusb
3 - the RH box is a 500Mhz and the MDK box is an 800

would any of these be a direct reason for the delay in starting the
scan?  I understand that there are 3 variables - but if libusb is the
main key - that would be good to know


I am going to try to revert to 1.0.13 and see what happens
I can then try rolling out a more CPU equivalent box

so the real variable is the LIBUSB - does anyone know if that is a
module in 2.4.xx?

thanks





> At least with the scanners supported by the gt68xx backend, a low scan
> width is important for higher speed at high resolutions. As you
> usually use high resolutions for smaller sections of photos or slides
> that's not that unreasonable.
> 
> > This box has a gig of ram so hopefully it's enough for this worst-case
> > scenario if sane doesn't open a file and work with smaller chunks in ram.
> > This is a dual 1gig p3 too. That might be relevant by making it more likely
> > that there is always a cpu available to service the usb interrups? Or
> > rather, that the one cpu that seems to be the only one that even sees
> > interrupts, is more likely to be able to keep up.
> 
> One of the problems is that libusb doesn't allow async i/o. So you
> can't send some buffers to be filled and wait for their completion.
> 
> Bye,
>   Henning
> 
> 
> 
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org
>


From brian@aljex.com  Wed Oct  6 23:26:14 2004
From: brian@aljex.com (Brian K. White)
Date: Wed, 6 Oct 2004 18:26:14 -0400
Subject: [sane-devel] Re: strange problems LIDE30
References: <d9aa9070410061122270e5a94@mail.gmail.com> <d9aa90704100612297776dd31@mail.gmail.com> <00af01c4abe8$98a1f610$6800000a@venti>
Message-ID: <010b01c4abf3$8d8b0f40$6800000a@venti>

> It's only at about 10 or 15% progress after 20 minutes so I'll send

still cranking away
just over 50%

Now I wish I'd used the time command so I can see just how long this will 
take even if I go out to eat and it finishes while I'm gone. Then we could 
look at the total data and total time and see if it transferred at full usb 
1.1 speed. Seems like it should be able to go a lot faster than this with 12 
megabit available.

Brian K. White  --  brian@aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani



From andras@users.sourceforge.net  Wed Oct  6 23:41:03 2004
From: andras@users.sourceforge.net (Major A)
Date: Wed, 6 Oct 2004 23:41:03 +0100
Subject: [sane-devel] is coolscan2 maintained?
In-Reply-To: <1096727231.3040.561.camel@localhost>
References: <1096727231.3040.561.camel@localhost>
Message-ID: <20041006224102.GA11406@ventus.lan>

> I am trying to get in touch with the coolscan2 backend author but I got
> no replies neither to private emails, neither in this list.
> I even checked that his last commit is dated january 2003, so I am
> wondering if he is still working at this project.

Sorry for not replying, I've had a busy time at work. I'm maintaining
coolscan2, but I need help with a few things. Here's the list of the
most important tasks still to be done:

- get LS50 and LS5000 to work, maybe LS9000 too.

- fix frame offset on LS4000 (should be easy, I just haven't had the
  time yet).

- add multiscan for those models that support it.

- fix positioning with LS8000.

I tried to get the first point done a few times, but it has proved a
bit difficult with no direct access to a scanner. If anyone could work
out what needs to be done, I'd be happy to incorporate it into the
code. Same goes for all other tasks. Since I have an LS4000, I'll
probably do points 2 and 3 myself.

With respect to all points above except multiscanning, there is no
more information that I can find in the Nikon specs that could
help. These things have to be solved via reverse engineering (looking
at logs).

Please do NOT contact me privately. If you have a question, please
post it on the list, I subscribe to it, and even if I don't reply,
someone else might help you.

  Andras


From Chris McKeever <techjedi@gmail.com>  Thu Oct  7 00:10:12 2004
From: Chris McKeever <techjedi@gmail.com> (Chris McKeever)
Date: Wed, 6 Oct 2004 18:10:12 -0500
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <010b01c4abf3$8d8b0f40$6800000a@venti>
References: <d9aa9070410061122270e5a94@mail.gmail.com>
 <d9aa90704100612297776dd31@mail.gmail.com>
 <00af01c4abe8$98a1f610$6800000a@venti>
 <010b01c4abf3$8d8b0f40$6800000a@venti>
Message-ID: <d9aa90704100616102dac4784@mail.gmail.com>

well - did some more testing - downgraded the RH 7.3 box to SANE
1.0.13 - same delay in in starting the scan (+2 min. @ 600 DPI).. I
think tried it on a slightly more powerful CPU and had the same
result.  This is leaning me towards that the 2.6 kernel with its
implemenation of LIBUSB works a lot better - I am going to give SuSE
9.1 a shot in a little and see if results are coincide with MANDRAKE
tests earlier

can anyone confirm that LIBUSB implementation would create this type of result?


On Wed, 6 Oct 2004 18:26:14 -0400, Brian K. White <brian@aljex.com> wrote:
> > It's only at about 10 or 15% progress after 20 minutes so I'll send
> 
> still cranking away
> just over 50%
> 
> Now I wish I'd used the time command so I can see just how long this will
> take even if I go out to eat and it finishes while I'm gone. Then we could
> look at the total data and total time and see if it transferred at full usb
> 1.1 speed. Seems like it should be able to go a lot faster than this with 12
> megabit available.
> 
> 
> 
> Brian K. White  --  brian@aljex.com  --  http://www.aljex.com/bkw/
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani
> 
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org
>


From brian@aljex.com  Thu Oct  7 02:09:50 2004
From: brian@aljex.com (Brian K. White)
Date: Wed, 6 Oct 2004 21:09:50 -0400
Subject: [sane-devel] Re: strange problems LIDE30
References: <d9aa9070410061122270e5a94@mail.gmail.com> <d9aa90704100612297776dd31@mail.gmail.com> <00af01c4abe8$98a1f610$6800000a@venti> <010b01c4abf3$8d8b0f40$6800000a@venti>
Message-ID: <015401c4ac0a$684c5560$6800000a@venti>

Brian K. White wrote:
>> It's only at about 10 or 15% progress after 20 minutes so I'll send
>
> still cranking away
> just over 50%
>
> Now I wish I'd used the time command so I can see just how long this
> will take even if I go out to eat and it finishes while I'm gone.
> Then we could look at the total data and total time and see if it
> transferred at full usb 1.1 speed. Seems like it should be able to go a 
> lot faster than this
> with 12 megabit available.

Just crashed, 8:07 pm
I sent my original mail at 5:07 pm
I probably started that email (and the xsane process) at about 4:30 pm

It was xsane in kde so I don't have any error message. It just winked out.
It was somewhere near 90% but I don't think it was done.
It's speed was constant the whole time and I had looked at it a few minutes 
before and it was still just under 90% and I don't think it was nearly 
enough time for it to have gone the rest of the way, maybe only another 1 or 
2 %.
So I will tentatively say it failed while in progress, not after it was done 
scanning and tried to do whatever it does next.
I was scanning "to viewer".

This box is not overclocked at all and has not exhibited any other signs of 
flaky hardware so I don't suspect ram/cpu/etc
It's running 2 seti@home processes 24/7 and I do a fair/medium amount of 
work on it, lots of rxvt & ssh to other boxes, some gimp, lots of konquerer, 
xmms is playing some 128 kbit shoutcast stream almost 24/7, I have a fairly 
large java app that runs 24/7 that interfaces with our voip phone system, I 
play the occasional dvd. None of these has yet surprised me.
I have not used the adaptec usb 2.0 pci card for very much at all although 
the optical mouse is plugged in to it and the scanner, and I have used the 
scanner and xsane without incident several times before but only at 
300dpi-gray and 200dpi-bw.

I wasn't touching the machine at the time. xmms was not playing, the mouse 
was not moving, the screensaver was up.
(I'm working on my laptop but I'm at the same desk)

At least I can go eat now and know I won't miss anything :)

I'm not above suspecting the usb card. I have not been able to get my 
unpowered usb2.0 2.5" hard drive to work on it.
Sorry, I can't define "not work" since I gave up a few months ago and by now 
I don't recall what I tried and what I saw because it was never actually 
important to me.
But that could just as easily be the enclosure or drive and not the usb 
card. The drive & enclosure works on my laptop, but it does give windows 
delayed write failed error messages once in a while if it's left plugged in 
and idle a long time. *shrug*

I could do some transfers to a 512 meg sd card in a jump drive trio and see 
if that is reliable.
sd cards are normally only about 1 megabit, but I have a 10/9 mb read/write 
card. that should be an ok test.
I'll just to simple large monolithic transfers so as to minimize the number 
of write cycles I use up.
I'll dd 500 megs directly to it a few times, and same thing to read.
I'll start with a given file, dd it on, dd it back to a new file and cmp the 
files to verify that the writes & reads didn't have a silent error that 
corrupted the data.
If that works I'll call the usb card stable at least in usb1 mode.


Brian K. White  --  brian@aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani



From gerhard@gjaeger.de  Thu Oct  7 08:01:59 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Thu, 7 Oct 2004 09:01:59 +0200
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <015401c4ac0a$684c5560$6800000a@venti>
References: <d9aa9070410061122270e5a94@mail.gmail.com> <010b01c4abf3$8d8b0f40$6800000a@venti> <015401c4ac0a$684c5560$6800000a@venti>
Message-ID: <200410070901.59917.gerhard@gjaeger.de>

Hi,

let's try and shed some light on the plustek-backend and the LiDE30
scanner:

- The scanner is a USB1.1 device, as the used chipset, a LM9833 is only
  capable to do USB1.1. 
- The LM9833 is able to scan @ 8bit per color-channel or @ 16bit
  where did you get the "full-color" from? You either scan with the
  "color" option, then it's 8bit per channel or you scan with the
  "color 42/48" option, then it's 16bit.
- The LiDE30 is able to scan @1200dpi in X direction, because it's the
  native resolution of the sensor, and the motor is able to do 2400dpi
  steps. Therefore X direction information is doubled.
- The backend does some calibration @ the start of each scan, this might
  take a while. This time has also been increased from 1.0.13 up to 1.0.14
  This is necessary to avoid stripes. To reduce the time, it's now possible
  to let the backend save the information of the coarse calibration 
  (option cacheCalData in the config file, or --calibration-cache=yes for
   scanimage). This is working for the latest CVs snapshots.

Please note, all backend before 1.0.14 are not recommendend for use with the
LiDE devices, as the calibration does not work correctly!
Also using kernel 2.6.x (x < 8) might cause problems with the USB.

Also note, that full-size scanning using the 2400dpi might not work. At least
I've never tested, because I've not that much memory in my boxes. 
2400dpi also create that much data, that a USB1.1 device really needs some
time to send the data to the box. Here the bandwidth is the limiting factor.
We might can tweak the motor settings for the 2400dpi to avoid backtracking.

Before continuing, I suggest to use the latest CVS snapshots, a kernel > 2.6.7
and the latests libusb. The next step will be to check if you really need to
do scans @2400dpi, at least full-size ones.

Ciao,
  Gerhard



From Francois.Patte@math-info.univ-paris5.fr  Thu Oct  7 12:11:42 2004
From: Francois.Patte@math-info.univ-paris5.fr (=?iso-8859-1?b?RnJhbudvaXM=?= Patte)
Date: Thu,  7 Oct 2004 13:11:42 +0200
Subject: [sane-devel] scanner hp5400
In-Reply-To: <20041002154946.GK10327@meier-geinitz.de>
References: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr> <20041002154946.GK10327@meier-geinitz.de>
Message-ID: <1097147502.4165246ea080a@www.math-info.univ-paris5.fr>

Selon Henning Meier-Geinitz <henning@meier-geinitz.de>:

> Hi,
>
> On Sat, Oct 02, 2004 at 04:25:14PM +0200, Fran=E7ois Patte wrote:
> > I am unable to have the scanner hp5400c working under linux. Here the
> result of:
>
> [...]
>
> > [hp5400] vendor/product 0x03F0-0x1005 opened
> > [hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D 1200
> > [hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D C500
> > [hp5400] Command 12 verified
> > [hp5400] Sorry, unknown scanner version. Attempted match on :
> > [hp5400] * 'SilitekIBlizd C3 ScannerV0.84'
> > [hp5400] * 'SilitekIBlizd C3 ScannerV0.86'
> > [hp5400] * 'SilitekIBlizd C3 ScannerV0.87'
> > [hp5400] Version is ''
>
> > What can I do else?
>
> Rebuild sane-backends like this:
>
> CFLAGS=3D"-DNO_STRING_VERSION_MATCH" ./configure
> make
> make install
>
> That's untested but I think it disables the version test.

This has solved the problem: scanner is now working.

Please include this change in the next version of sane-backends. I hope t=
hat
linux distributors will make the change too: it is not so easy to compile=
 only
one package when several packages depend on it and that all where install=
ed by
the way of rpm....

Thank you.
--
Fran=E7ois Patte

Ecole fran=E7aise d'Extr=EAme-Orient - Pune - Inde
Universit=E9 Ren=E9 Descartes - Paris 5
UFR de math=E9matiques et informatique
http://www.math-info.univ-paris5.fr/~patte


From henning@meier-geinitz.de  Thu Oct  7 12:33:36 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 13:33:36 +0200
Subject: [sane-devel] scanner hp5400
In-Reply-To: <1097147502.4165246ea080a@www.math-info.univ-paris5.fr>
References: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr> <20041002154946.GK10327@meier-geinitz.de> <1097147502.4165246ea080a@www.math-info.univ-paris5.fr>
Message-ID: <20041007113336.GC8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 01:11:42PM +0200, François Patte wrote:
> This has solved the problem: scanner is now working.
> 
> Please include this change in the next version of sane-backends. I hope that
> linux distributors will make the change too: it is not so easy to compile only
> one package when several packages depend on it and that all where installed by
> the way of rpm....

The version check has already been disabled in CVS so the change will
be in sane-backends 1.0.14.

Bye,
  Henning


From henning@meier-geinitz.de  Thu Oct  7 12:57:51 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 13:57:51 +0200
Subject: [sane-devel] scanner hp5400
In-Reply-To: <20041007113336.GC8083@meier-geinitz.de>
References: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr> <20041002154946.GK10327@meier-geinitz.de> <1097147502.4165246ea080a@www.math-info.univ-paris5.fr> <20041007113336.GC8083@meier-geinitz.de>
Message-ID: <20041007115751.GD8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 01:33:36PM +0200, Henning Meier-Geinitz wrote:
> The version check has already been disabled in CVS so the change will
> be in sane-backends 1.0.14.

1.0.15 obviously.

> Bye,
>   Henning


From eppesuig@users.sourceforge.net  Thu Oct  7 14:00:50 2004
From: eppesuig@users.sourceforge.net (Giuseppe Sacco)
Date: Thu, 07 Oct 2004 15:00:50 +0200
Subject: [sane-devel] is coolscan2 maintained?
In-Reply-To: <20041006224102.GA11406@ventus.lan>
References: <1096727231.3040.561.camel@localhost>
 <20041006224102.GA11406@ventus.lan>
Message-ID: <1097154050.1604.24.camel@casa>

Il gio, 2004-10-07 alle 00:41, Major A ha scritto:
[...]
> I tried to get the first point done a few times, but it has proved a
> bit difficult with no direct access to a scanner. If anyone could work
> out what needs to be done, I'd be happy to incorporate it into the
> code. Same goes for all other tasks. Since I have an LS4000, I'll
> probably do points 2 and 3 myself.

I may give you ssh access to a linux machine connected to an LS-50. I
may do it only for one week, just send me an ssh public key, a disk
quota requirement, a username, a start date and specify if you need a
color slide or a color/b&W film loaded.

If I might help in any other way, just tell me.

Bye,
Giuseppe



From brian@aljex.com  Thu Oct  7 16:19:38 2004
From: brian@aljex.com (Brian K. White)
Date: Thu, 7 Oct 2004 11:19:38 -0400
Subject: [sane-devel] Re: strange problems LIDE30
References: <d9aa9070410061122270e5a94@mail.gmail.com> <010b01c4abf3$8d8b0f40$6800000a@venti> <015401c4ac0a$684c5560$6800000a@venti> <200410070901.59917.gerhard@gjaeger.de>
Message-ID: <005e01c4ac81$1f563ac0$6800000a@venti>

Gerhard Jaeger wrote:
> Hi,
>
> let's try and shed some light on the plustek-backend and the LiDE30
> scanner:
>
> - The scanner is a USB1.1 device, as the used chipset, a LM9833 is
>  only capable to do USB1.1.
> - The LM9833 is able to scan @ 8bit per color-channel or @ 16bit
>  where did you get the "full-color" from? You either scan with the
>  "color" option, then it's 8bit per channel or you scan with the
>  "color 42/48" option, then it's 16bit.
> - The LiDE30 is able to scan @1200dpi in X direction, because it's the
>  native resolution of the sensor, and the motor is able to do 2400dpi
>  steps. Therefore X direction information is doubled.
> - The backend does some calibration @ the start of each scan, this
>  might take a while. This time has also been increased from 1.0.13 up
>  to 1.0.14 This is necessary to avoid stripes. To reduce the time,
>  it's now possible to let the backend save the information of the
>  coarse calibration (option cacheCalData in the config file, or
>   --calibration-cache=yes for scanimage). This is working for the
> latest CVs snapshots.
>
> Please note, all backend before 1.0.14 are not recommendend for use
> with the LiDE devices, as the calibration does not work correctly!
> Also using kernel 2.6.x (x < 8) might cause problems with the USB.
>
> Also note, that full-size scanning using the 2400dpi might not work.
> At least I've never tested, because I've not that much memory in my
> boxes. 2400dpi also create that much data, that a USB1.1 device
> really needs some time to send the data to the box. Here the
> bandwidth is the limiting factor. We might can tweak the motor
> settings for the 2400dpi to avoid backtracking.
>
> Before continuing, I suggest to use the latest CVS snapshots, a
> kernel > 2.6.7 and the latests libusb. The next step will be to check
> if you really need to do scans @2400dpi, at least full-size ones.
>
> Ciao,
>  Gerhard

Very informative
Thanks much

No, I at least have no real use for scanning full sheets in color at 
2400dpi.
I only did it for the purpose of testing the system, it's the worst case 
combination of all offered options.
I never had a problem with "normal" jobs.
I've done a few partial pages at 600dpi color, many full pages at 100-600 
gray & b&w
Never had a problem.

Even though I'm just under your recommendation on several fronts.
These are all what's currently available from suse pre-built and 
Yast-installable:

bwlin1:~ # uname -a
Linux bwlin1 2.6.5-7.108-smp #1 SMP Wed Aug 25 13:34:40 UTC 2004 i686 i686 
i386 GNU/Linux
bwlin1:~ # scanimage --version
scanimage (sane-backends) 1.0.13; backend version 1.0.13
bwlin1:~ # ls /usr/lib/*usb*
/usr/lib/libusb-0.1.so.4      /usr/lib/libusb.a   /usr/lib/libusb.so
/usr/lib/libusb-0.1.so.4.4.0  /usr/lib/libusb.la
bwlin1:~ #

Brian K. White  --  brian@aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani



From sirius-c@iname.com  Thu Oct  7 16:21:10 2004
From: sirius-c@iname.com (Jason Anderson)
Date: Thu, 07 Oct 2004 10:21:10 -0500
Subject: [sane-devel] Compiling problems
Message-ID: <20041007152110.E41FE4BDA9@ws1-1.us4.outblaze.com>

Hello everyone.

Here's my problem.  When I try to compile the latest sane backends with t=
he Genesys files, it returns an error about not being able to find genesy=
s.o in the "lib" folder.  Now I read the README file, but it still won't =
compile properly.  Does anyone have a suggestion?

Thank you,

----------
Jason A.
ICQ# 148434286
--=20
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm



From henning@meier-geinitz.de  Thu Oct  7 16:49:03 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 17:49:03 +0200
Subject: [sane-devel] Compiling problems
In-Reply-To: <20041007152110.E41FE4BDA9@ws1-1.us4.outblaze.com>
References: <20041007152110.E41FE4BDA9@ws1-1.us4.outblaze.com>
Message-ID: <20041007154903.GF8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 10:21:10AM -0500, Jason Anderson wrote:
> Here's my problem.  When I try to compile the latest sane backends
> with the Genesys files, it returns an error about not being able to
> find genesys.o in the "lib" folder.  Now I read the README file, but
> it still won't compile properly.  Does anyone have a suggestion?

You have changed configure.in and backend/Makefile.in, ran "autoconf",
make distclean, ./configure, make?

If yes, please post the esact error message (and some more lines of
context).

Bye,
  Henning


From christoph.knauer@web.de  Thu Oct  7 18:46:20 2004
From: christoph.knauer@web.de (Christoph Knauer)
Date: Thu, 7 Oct 2004 19:46:20 +0200
Subject: [sane-devel] scanning via network
Message-ID: <200410071946.25043.christoph.knauer@web.de>

--nextPart1419820.9XbQ2pkNat
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi People,

I've just build me a new backend-package from sourcen, where I used newer c=
ode=20
for microtek2 (from karsten festag) which works now with SM X6 and LightLid=
35=20
(the scannerlamp now is of if I use the lightlid).

But now there is a network-problem since I'm using this "new" backend-packa=
ge:=20
I can't scan on my network anymore. To compile only the microtek2-code was=
=20
changed, all other stuff was used before, too.

When I've a look into my xinetd.log, there are these entries:

> 04/10/5@17:49:02: START: sane from=3D192.168.10.1
> 04/10/5@23:39:51: EXIT: sane status=3D0 duration=3D21049(sec)
> --------------------------^ before using the "new" microtek2
> 04/10/6@10:15:59: START: sane from=3D192.168.10.1
> 04/10/6@10:15:59: EXIT: sane status=3D127 duration=3D0(sec)
> --------------------------^ after using the "new" microtek2

I've looked for all my conf-files, and they seems to be unchanged.

Any Ideas?

Thanx, Christoph

PS: I'm sorry, but my english is not very well
=2D-=20
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
=2D----
alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
unter http://www.profiseller.de/shop/christoph-knauer

--nextPart1419820.9XbQ2pkNat
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBZYDwgy/nEXRCgmERAhlxAJ0anM+XGscpfIfaKP/lP84ReOERvwCeJsFE
5gKDsVsz0XnvTat7BQh9XJ4=
=cyLJ
-----END PGP SIGNATURE-----

--nextPart1419820.9XbQ2pkNat--


From ukd@xenon.pc.Uni-Koeln.DE  Thu Oct  7 20:24:45 2004
From: ukd@xenon.pc.Uni-Koeln.DE (Ulrich Deiters)
Date: Thu, 07 Oct 2004 19:24:45 METDST
Subject: [sane-devel] No device available
Message-ID: <200410071724.TAA02695@xenon.pc.Uni-Koeln.DE>

Are you sure that the SCSI ID of the scanner is different
from any other ID on the bus? Is the bus properly
terminated? Is the SCSI cable of permissible length?
If the SCSI controller cannot initialize its bus, it
might declare itself as offline at boot time.

Regards,

Ulrich Deiters


From henning@meier-geinitz.de  Thu Oct  7 18:59:09 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 19:59:09 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <200410071946.25043.christoph.knauer@web.de>
References: <200410071946.25043.christoph.knauer@web.de>
Message-ID: <20041007175909.GH8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 07:46:20PM +0200, Christoph Knauer wrote:
> But now there is a network-problem since I'm using this "new" backend-package: 
> I can't scan on my network anymore. To compile only the microtek2-code was 
> changed, all other stuff was used before, too.

If that's true, it's not a network problem.

> When I've a look into my xinetd.log, there are these entries:
> 
> > 04/10/5@17:49:02: START: sane from=192.168.10.1
> > 04/10/5@23:39:51: EXIT: sane status=0 duration=21049(sec)
> > --------------------------^ before using the "new" microtek2
> > 04/10/6@10:15:59: START: sane from=192.168.10.1
> > 04/10/6@10:15:59: EXIT: sane status=127 duration=0(sec)
> > --------------------------^ after using the "new" microtek2
> 
> I've looked for all my conf-files, and they seems to be unchanged.
> 
> Any Ideas?

First describe what you do and what your problem actually is. Is the
network scanner not detected or doesn't it scan?

Log messages from saned?

Bye,
  Henning


From tomasz.orlinski@wp.pl  Thu Oct  7 19:26:50 2004
From: tomasz.orlinski@wp.pl (=?iso-8859-2?Q?Tomasz_Orli=F1ski?=)
Date: Thu, 7 Oct 2004 20:26:50 +0200
Subject: [sane-devel] USB scanners DO work on Solaris 10 x86
Message-ID: <002501c4ac9d$8be2b530$0100a8c0@athlon64>

I would like to inform you, that I have compiled SANE on Sun Solaris 10 x86
with built-in USB scanner support. It was possible, because Sun had prepared
libusb library wrapper for Solaris 10. I know, that Solaris 10 Software
Express Release 08/04 is required. I have done it in that way:
LD_LIBRARY_PATH=/usr/sfw/lib:$LD_LIBRARY_PATH
CFLAGS="-I/usr/sfw/include"
CPPFLAGS="-I/usr/sfw/include"
LDFLAGS="-L/usr/sfw/lib -R/usr/sfw/lib -lusb"
export LD_LIBRARY_PATH CFLAGS CPPFLAGS LDFLAGS
./configure --prefix=/opt/sane --disable-fork-process
make
make install
It was also required to add a generic USB kernel driver. I had to look for
my scanner device name in output of
prtconf -D -v
command. My scanner is Plustek UT24 and the apropriate part of output looked
like this:
name='compatible' type=string items=8 value='usb7b3,17.100' + ...
I had to remove the not used kernel driver
rem_drv ugen
And add it again:
add_drv -i 'usb7b3,17.100' ugen
Then, /opt/sane/bin/sane-find-scanner detected my scanner and everything
worked fine. I to add " " signs around usb7b3,17.100 name in
/etc/driver_aliases to have the scanner working after reboot.
To compile this packages SUNWlibusb and SUNWlibusbugen were needed. I used
Solaris Software Companion CD gcc 2.95.3 compiler and Sun's /usr/ccs/bin/ld
linker. USB support DOES NOT work in Solaris 9 and earlier versions.
I hope, that this information would be useful for other USB scanner users.

Tomasz Orlinski



From henning@meier-geinitz.de  Thu Oct  7 20:02:33 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 21:02:33 +0200
Subject: [sane-devel] USB scanners DO work on Solaris 10 x86
In-Reply-To: <002501c4ac9d$8be2b530$0100a8c0@athlon64>
References: <002501c4ac9d$8be2b530$0100a8c0@athlon64>
Message-ID: <20041007190233.GI8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 08:26:50PM +0200, Tomasz Orli?ski wrote:
> I would like to inform you, that I have compiled SANE on Sun Solaris 10 x86
> with built-in USB scanner support.

Very nice. I'd like to place your mail in README.solaris in SANE CVS
so it can be easily find. What's your opinion on this?

I guess you used sane-backends 1.0.14? I'll update our "supported
platforms list" accordingly.

Thanks for your report. It looks like a real adventure to use
Solaris/x86 :-)

Bye,
  Henning

> -- 
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org


From christoph.knauer@web.de  Thu Oct  7 20:31:15 2004
From: christoph.knauer@web.de (Christoph Knauer)
Date: Thu, 7 Oct 2004 21:31:15 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <20041007175909.GH8083@meier-geinitz.de>
References: <200410071946.25043.christoph.knauer@web.de> <20041007175909.GH8083@meier-geinitz.de>
Message-ID: <200410072131.20022.christoph.knauer@web.de>

--nextPart1547262.qRYlrS05dl
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

I can scan from my server, where the scanner is connected, but i can't scan=
=20
from my network-pc. The only change on the system is a backend-update on th=
e=20
server by using the last sorces of karsten festag.

It seems to be an error in the updatet files, I've just reinstalled the las=
t=20
version before, and suddenly there is no error ...

Thanks

Am Donnerstag, 7. Oktober 2004 19:59 schrieb Henning Meier-Geinitz:
> Hi,
>
> On Thu, Oct 07, 2004 at 07:46:20PM +0200, Christoph Knauer wrote:
> > But now there is a network-problem since I'm using this "new"
> > backend-package: I can't scan on my network anymore. To compile only the
> > microtek2-code was changed, all other stuff was used before, too.
>
> If that's true, it's not a network problem.
>
> > When I've a look into my xinetd.log, there are these entries:
> > > 04/10/5@17:49:02: START: sane from=3D192.168.10.1
> > > 04/10/5@23:39:51: EXIT: sane status=3D0 duration=3D21049(sec)
> > > --------------------------^ before using the "new" microtek2
> > > 04/10/6@10:15:59: START: sane from=3D192.168.10.1
> > > 04/10/6@10:15:59: EXIT: sane status=3D127 duration=3D0(sec)
> > > --------------------------^ after using the "new" microtek2
> >
> > I've looked for all my conf-files, and they seems to be unchanged.
> >
> > Any Ideas?
>
> First describe what you do and what your problem actually is. Is the
> network scanner not detected or doesn't it scan?
>
> Log messages from saned?
>
> Bye,
>   Henning

=2D-=20
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
=2D----
alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
unter http://www.profiseller.de/shop/christoph-knauer

--nextPart1547262.qRYlrS05dl
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBZZmHgy/nEXRCgmERAnPhAJ0V4GrMKFR1RyakkTHtWzIBme+2rgCeJt5n
jTzEb4W4mIU3kaX8tBIjheo=
=i8Sr
-----END PGP SIGNATURE-----

--nextPart1547262.qRYlrS05dl--


From henning@meier-geinitz.de  Thu Oct  7 20:34:58 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 21:34:58 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <200410072131.20022.christoph.knauer@web.de>
References: <200410071946.25043.christoph.knauer@web.de> <20041007175909.GH8083@meier-geinitz.de> <200410072131.20022.christoph.knauer@web.de>
Message-ID: <20041007193458.GJ8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 09:31:15PM +0200, Christoph Knauer wrote:
> I can scan from my server, where the scanner is connected, but i can't scan 
> from my network-pc. The only change on the system is a backend-update on the 
> server by using the last sorces of karsten festag.
> 
> It seems to be an error in the updatet files, I've just reinstalled the last 
> version before, and suddenly there is no error ...

Ok. So I'll ask again:

> > First describe what you do and what your problem actually is. Is the
> > network scanner not detected or doesn't it scan?

If it doesn't scan, which error message do you get and when?

Bye,
  Henning


From bertrik@zonnet.nl  Thu Oct  7 21:49:09 2004
From: bertrik@zonnet.nl (Bertrik Sikken)
Date: Thu, 07 Oct 2004 22:49:09 +0200
Subject: [sane-devel] niash backend dependencies in backend/Makefile.in
Message-ID: <4165ABC5.5040406@zonnet.nl>

Hi all,

I just tried sane-backends CVS and found that it did not work
for my hp3300 (niash backend). Scanimage -L complains about
missing 'sanei_scsi_find_devices'. I think this is somehow
pulled in from another sanei function.

I noticed that nearly all other backends have a line in
backend/Makefile.in that declares dependency on sanei_scsi.lo
(the niash backend does not have it)
Adding the following line to backend/Makefile.in made it work
for me:
libsane-niash.la: ../sanei/sanei_scsi.lo

I'm not sure what is going on, perhaps I'm overlooking something.
The patch to sane-backends that we used before the niash backend
was integrated into sane CVS didn't have the
'libsane-niash.la: ../sanei/sanei_scsi.lo'
line either, yet it seemed to work.

Can someone review the correctness of the dependencies in
backend/Makefile.in for the niash backend?
What dependencies are needed for what sanei_functions?

All the best,
Bertrik


From christoph.knauer@web.de  Thu Oct  7 22:13:05 2004
From: christoph.knauer@web.de (Christoph Knauer)
Date: Thu, 7 Oct 2004 23:13:05 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <20041007193458.GJ8083@meier-geinitz.de>
References: <200410071946.25043.christoph.knauer@web.de> <200410072131.20022.christoph.knauer@web.de> <20041007193458.GJ8083@meier-geinitz.de>
Message-ID: <200410072313.05389.christoph.knauer@web.de>

--nextPart2147052.XxAo4Y6qCR
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

the problem is not in network-scanning. Please forget this thead, thanks

=46or info: it seems to be a problem with the last build on my system ... u=
sing=20
the package before (which I know as good) -> ok, all is working fine
Using the last builded package -> nothing works, only error:=20

Julia2002:~ # scanimage -L
scanimage: relocation error: /usr/local/lib/sane/libsane-microtek2.so.1:=20
undefined symbol: sanei_thread_init

On the weekend perhaps I've more time to search the solution ...

Thanks,

Christoph

Am Donnerstag, 7. Oktober 2004 21:34 schrieb Henning Meier-Geinitz:
> > > First describe what you do and what your problem actually is. Is the
> > > network scanner not detected or doesn't it scan?
>
> If it doesn't scan, which error message do you get and when?

=2D-=20
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
=2D----
alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
unter http://www.profiseller.de/shop/christoph-knauer

--nextPart2147052.XxAo4Y6qCR
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBZbFhgy/nEXRCgmERAgAuAJ9AZfyimX6R0IPRckV+1k4F2LgLgQCdFRWG
InCfuIR25QhMj+5ejO+uUR4=
=pI0a
-----END PGP SIGNATURE-----

--nextPart2147052.XxAo4Y6qCR--


From peder@park.se  Fri Oct  8 10:29:19 2004
From: peder@park.se (peder)
Date: Fri, 8 Oct 2004 11:29:19 +0200 (CEST)
Subject: [sane-devel] Two xsane-Win32-0.96 annoyancies
Message-ID: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>

 Thanx for a nifty port.

 I've been happlily using xsane in out school network for a couple of
 years. We have 5 old linux boxes scattered around the place as scanner
 servers and the WinXP/Win98-clients use xsane to connect.

 However there are two issues.

 The minor one: Is there a technical reason why the program has to
 be installed to c:\sane? Can't the program search for it's files
 using perhaps a XSANE variable or in current directory?
 I like to have the program installed on the server so I can upgrade
 it for every user and not having to walk around 300+ PC's.
 This works in 0.90 on Win98 but not on WinXP for some reason.
 In 0.96 it works on neither.

 I found out you only have to put some files in c:\sane so I can
 distribute those every time, so this issue is not a biggie.

 The major one: In xsane-0.83 and 0.90 I could run
 'xsane.exe ip-of-scan-server:device'. In 0.96 this doesn't work; I have
 to add all my servers in net.conf, wait for xsane to "scan for devices"
 and choose the right one from five nearly identical entries.
 Maybe I can pick the right one but definitely not my users.
 Can we please have the scan-server argument back?

 FYI, version 0.90 was much faster than 0.96. I tried them on a
 400MHz and 0.96 was really sluggish, perhaps due to newer gtk versions.


 Regards,

 Peder Hedlund


From henning@meier-geinitz.de  Fri Oct  8 11:00:43 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 8 Oct 2004 12:00:43 +0200
Subject: [sane-devel] Two xsane-Win32-0.96 annoyancies
In-Reply-To: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>
References: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>
Message-ID: <20041008100043.GB9991@meier-geinitz.de>

Hi,

On Fri, Oct 08, 2004 at 11:29:19AM +0200, peder wrote:
>  The major one: In xsane-0.83 and 0.90 I could run
>  'xsane.exe ip-of-scan-server:device'. In 0.96 this doesn't work; I have
>  to add all my servers in net.conf, wait for xsane to "scan for devices"
>  and choose the right one from five nearly identical entries.

Just a wild guess: If xsane 0.83 was linked directly against the net
backend and 0.96 was linked against the dll backend the format would be:
xsane.exe net:ip-of-scan-server:device

>  Maybe I can pick the right one but definitely not my users.

At least on Unix systems there is the SANE_DEFAULT_DEVICE varaiable
that preselects the device to use. That means you only have to press
enter.

Bye,
  Henning


From henning@meier-geinitz.de  Fri Oct  8 10:52:56 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 8 Oct 2004 11:52:56 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <200410072313.05389.christoph.knauer@web.de>
References: <200410071946.25043.christoph.knauer@web.de> <200410072131.20022.christoph.knauer@web.de> <20041007193458.GJ8083@meier-geinitz.de> <200410072313.05389.christoph.knauer@web.de>
Message-ID: <20041008095256.GA9991@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 11:13:05PM +0200, Christoph Knauer wrote:
> For info: it seems to be a problem with the last build on my system ... using 
> the package before (which I know as good) -> ok, all is working fine
> Using the last builded package -> nothing works, only error: 
> 
> Julia2002:~ # scanimage -L
> scanimage: relocation error: /usr/local/lib/sane/libsane-microtek2.so.1: 
> undefined symbol: sanei_thread_init
> 
> On the weekend perhaps I've more time to search the solution ...

The reason is that you only use a new microtek2 backend.
backend/Makefile.in also must be updated.

As the latest microtek2 code is now in CVS I recommend using a CVS
snapshot.

Bye,
  Henning


From henning@meier-geinitz.de  Fri Oct  8 12:03:25 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 8 Oct 2004 13:03:25 +0200
Subject: [sane-devel] niash backend dependencies in backend/Makefile.in
In-Reply-To: <4165ABC5.5040406@zonnet.nl>
References: <4165ABC5.5040406@zonnet.nl>
Message-ID: <20041008110325.GA23598@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 10:49:09PM +0200, Bertrik Sikken wrote:
> I just tried sane-backends CVS and found that it did not work
> for my hp3300 (niash backend). Scanimage -L complains about
> missing 'sanei_scsi_find_devices'. I think this is somehow
> pulled in from another sanei function.

That's called from sanei_config_attach_matching_devices.

However, at least in current CVS niash doesn't seem to use that
function.

> I noticed that nearly all other backends have a line in
> backend/Makefile.in that declares dependency on sanei_scsi.lo
> (the niash backend does not have it)
> Adding the following line to backend/Makefile.in made it work
> for me:
> libsane-niash.la: ../sanei/sanei_scsi.lo

That's only needed for SCSI backends. USB backends should use
sanei_usb_attach_matching_devices (which is in sanei_usb.lo).

> Can someone review the correctness of the dependencies in
> backend/Makefile.in for the niash backend?

It's correct as far as I can see.

If it still happens after "cvs update ; make distclean; ./congigure ;
make ; make install" could you show us some more details (e.g. if it's
really the niash backend that uses this function)?

I don't get any errors with scanimage -L.

Bye,
  Henning


From peder@park.se  Fri Oct  8 12:09:21 2004
From: peder@park.se (peder)
Date: Fri, 8 Oct 2004 13:09:21 +0200 (CEST)
Subject: [sane-devel] Two xsane-Win32-0.96 annoyancies
In-Reply-To: <20041008100043.GB9991@meier-geinitz.de>
References: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>
 <20041008100043.GB9991@meier-geinitz.de>
Message-ID: <Pine.LNX.4.58.0410081302550.19226@tux.park.se>

On Fri, 8 Oct 2004, Henning Meier-Geinitz wrote:

> Hi,
>
> On Fri, Oct 08, 2004 at 11:29:19AM +0200, peder wrote:
> >  The major one: In xsane-0.83 and 0.90 I could run
> >  'xsane.exe ip-of-scan-server:device'. In 0.96 this doesn't work; I have
> >  to add all my servers in net.conf, wait for xsane to "scan for devices"
> >  and choose the right one from five nearly identical entries.
>
> Just a wild guess: If xsane 0.83 was linked directly against the net
> backend and 0.96 was linked against the dll backend the format would be:
> xsane.exe net:ip-of-scan-server:device

 Pretty accurate wild guess! Thanx.

 Peder


From Chris McKeever <techjedi@gmail.com>  Fri Oct  8 14:48:22 2004
From: Chris McKeever <techjedi@gmail.com> (Chris McKeever)
Date: Fri, 8 Oct 2004 08:48:22 -0500
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <200410070901.59917.gerhard@gjaeger.de>
References: <d9aa9070410061122270e5a94@mail.gmail.com>
 <010b01c4abf3$8d8b0f40$6800000a@venti>
 <015401c4ac0a$684c5560$6800000a@venti>
 <200410070901.59917.gerhard@gjaeger.de>
Message-ID: <d9aa907041008064815c04b9e@mail.gmail.com>

n Thu, 7 Oct 2004 09:01:59 +0200, Gerhard Jaeger <gerhard@gjaeger.de> wrote:
> Hi,
> 
> let's try and shed some light on the plustek-backend and the LiDE30
> scanner:
> 
> - The scanner is a USB1.1 device, as the used chipset, a LM9833 is only
>   capable to do USB1.1.
> - The LM9833 is able to scan @ 8bit per color-channel or @ 16bit
>   where did you get the "full-color" from? You either scan with the
>   "color" option, then it's 8bit per channel or you scan with the
>   "color 42/48" option, then it's 16bit.
> - The LiDE30 is able to scan @1200dpi in X direction, because it's the
>   native resolution of the sensor, and the motor is able to do 2400dpi
>   steps. Therefore X direction information is doubled.
> - The backend does some calibration @ the start of each scan, this might
>   take a while. This time has also been increased from 1.0.13 up to 1.0.14
>   This is necessary to avoid stripes. To reduce the time, it's now possible
>   to let the backend save the information of the coarse calibration
>   (option cacheCalData in the config file, or --calibration-cache=yes for
>    scanimage). This is working for the latest CVs snapshots.
> 

Thanks everyone for all your information! - I have gotten it all
working, and just want to summarize (again) what was laerned found

- yes the canon 30 is only 1.1USB
- when moving from a 2.4 kernel to a 2.6 kernel the startup time for the scanner
decreased significantly (I think the is a libusb v. scanner.o issue). 
I am now able to remote scan @ 1200 (it is however slow)
- originally I had a generic USB2 card - that was causing me some
grief in-and-of-itself with the scanner, dropping it to the onboard
1.1 solved at least some of the issue
- I am using the stock kernel and libusb from SUSE 9.1 (2.6.5) - I am
not having any issue thus far w/ 1.0.14

once again - thanks





> Please note, all backend before 1.0.14 are not recommendend for use with the
> LiDE devices, as the calibration does not work correctly!
> Also using kernel 2.6.x (x < 8) might cause problems with the USB.
> 
> Also note, that full-size scanning using the 2400dpi might not work. At least
> I've never tested, because I've not that much memory in my boxes.
> 2400dpi also create that much data, that a USB1.1 device really needs some
> time to send the data to the box. Here the bandwidth is the limiting factor.
> We might can tweak the motor settings for the 2400dpi to avoid backtracking.
> 
> Before continuing, I suggest to use the latest CVS snapshots, a kernel > 2.6.7
> and the latests libusb. The next step will be to check if you really need to
> do scans @2400dpi, at least full-size ones.
> 
> Ciao,
>   Gerhard
> 
> 
> 
> 
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org
>


From Anton Mazkovoi <anton.mazkovoi@gmail.com>  Sat Oct  9 06:37:06 2004
From: Anton Mazkovoi <anton.mazkovoi@gmail.com> (Anton Mazkovoi)
Date: Sat, 9 Oct 2004 15:37:06 +1000
Subject: [sane-devel] SaneTwain - windows losing connection
Message-ID: <9647569f0410082237451ebb75@mail.gmail.com>

------=_Part_46_1697784.1097300226605
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

I have a epson cx6500 scanner/printer which I have working with epkowa
drivers and sane-backends-1.0.12-2 on a RedHat 9 box. Saned is started
through xinetd and I have a Windows XP SP1 machine running SaneTwain
1.25 and scanning images with no problem.

Another Windows XP SP1 machine on the same local network refuses to
scan. Its running the same version of SaneTwain. When scanimage.exe is
started it tries to retrieve the scanners from the server and I see
the saned process started on the server (and a connection reported on
both windows and linux boxes using "netstat -na"). The scanimage
window is unusable (unclickable) for a while. After some time  the
window becomes usable and the devices dropdown is correctly populated
with the scanner's device.

Clicking "preview" or "scan", results in a pop-up which says: "Write
error 64, the specified network name is no longer available". When I
do a "netstat -na" on a windows box I can see that the tcp connection
is NOT there. The linux box (netstat -na) thinks the connection IS
there, the saned process is still running and is doing a read from the
socket which is (was) connected to the windows box.

Also, the "options" tab of the scanimage window is completely empty.
(On the working windows XP box it shows options).

Also, printing to the scanner/printer device from both windows boxes
causes no problems. The linux box also acts as the gateway to the
internet for both windows boxes. Surfing the web and downloading files
from both machines seems to have no problems.

I am attaching the log produced by running scanimage --debug on the
non-working windows box.

Is this a known windows problem? Has anyone seen anything like this before?

Any help is very much appreciated!

Thanks in advance,
Anton

------=_Part_46_1697784.1097300226605
Content-Type: application/octet-stream; name="sanetwain.dbg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="sanetwain.dbg"

RGVidWcgc2Vzc2lvbiBzdGFydGVkLiBWZXJzaW9uIGlzIHYxLjI1DQpPcGVuaW5nIGNvbm5lY3Rp
b24NCk1lc3NhZ2UgbG9nZ2VkOiBPcGVuaW5nIGNvbm5lY3Rpb24NCk9wZW5pbmcgc29ja2V0IG9u
IHBvcnQgNjU2Ng0KTWVzc2FnZSBsb2dnZWQ6IExvb2tpbmcgdXAgaG9zdCBidXJuZXINCk1lc3Nh
Z2UgbG9nZ2VkOiBDb25uZWN0aW5nIHRvIGhvc3QgYnVybmVyDQpNZXNzYWdlIGxvZ2dlZDogQ29u
bmVjdGVkIHRvIGhvc3QgYnVybmVyDQpMb2dnaW5nIG9uIGFzIFBDVVNFUg0KR290IHNvY2tldCBj
b25uZWN0aW9uDQpNZXNzYWdlIGxvZ2dlZDogR2V0dGluZyBsaXN0IG9mIGF2YWlsYWJsZSBkZXZp
Y2VzDQpNZXNzYWdlIGxvZ2dlZDogUmV0cmlldmluZyBvcHRpb24gdmFsdWVzDQpTYW5lT3B0aW9u
IGNyZWF0ZWQ6IDAsIA0KCU9wdGlvbiBjYXBhYmlsaXRpZXM6IDQNClNhbmVPcHRpb24gY3JlYXRl
ZDogMSwgDQoJT3B0aW9uIGNhcGFiaWxpdGllczogMA0KU2FuZU9wdGlvbiBjcmVhdGVkOiAyLCBt
b2RlDQoJT3B0aW9uIGNhcGFiaWxpdGllczogNQ0KU2FuZU9wdGlvbiBjcmVhdGVkOiAzLCBkZXB0
aA0KCU9wdGlvbiBjYXBhYmlsaXRpZXM6IDM3DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDQsIGhhbGZ0
b25pbmcNCglPcHRpb24gY2FwYWJpbGl0aWVzOiAzNw0KU2FuZU9wdGlvbiBjcmVhdGVkOiA1LCBk
cm9wb3V0DQoJT3B0aW9uIGNhcGFiaWxpdGllczogNjkNClNhbmVPcHRpb24gY3JlYXRlZDogNiwg
YnJpZ2h0bmVzcw0KCU9wdGlvbiBjYXBhYmlsaXRpZXM6IDM3DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6
IDcsIHNoYXJwbmVzcw0KCU9wdGlvbiBjYXBhYmlsaXRpZXM6IDM3DQpTYW5lT3B0aW9uIGNyZWF0
ZWQ6IDgsIGdhbW1hLWNvcnJlY3Rpb24NCglPcHRpb24gY2FwYWJpbGl0aWVzOiA1DQpTYW5lT3B0
aW9uIGNyZWF0ZWQ6IDksIGNvbG9yLWNvcnJlY3Rpb24NCglPcHRpb24gY2FwYWJpbGl0aWVzOiAx
MDENClNhbmVPcHRpb24gY3JlYXRlZDogMTAsIHJlc29sdXRpb24NCglPcHRpb24gY2FwYWJpbGl0
aWVzOiA1DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDExLCB0aHJlc2hvbGQNCglPcHRpb24gY2FwYWJp
bGl0aWVzOiA1DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDEyLCANCglPcHRpb24gY2FwYWJpbGl0aWVz
OiA2NA0KU2FuZU9wdGlvbiBjcmVhdGVkOiAxMywgbWlycm9yDQoJT3B0aW9uIGNhcGFiaWxpdGll
czogMzcNClNhbmVPcHRpb24gY3JlYXRlZDogMTQsIHNwZWVkDQoJT3B0aW9uIGNhcGFiaWxpdGll
czogNQ0KU2FuZU9wdGlvbiBjcmVhdGVkOiAxNSwgYXV0by1hcmVhLXNlZ21lbnRhdGlvbg0KCU9w
dGlvbiBjYXBhYmlsaXRpZXM6IDUNClNhbmVPcHRpb24gY3JlYXRlZDogMTYsIHNob3J0LXJlc29s
dXRpb24NCglPcHRpb24gY2FwYWJpbGl0aWVzOiA1DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDE3LCB6
b29tDQoJT3B0aW9uIGNhcGFiaWxpdGllczogMzcNClNhbmVPcHRpb24gY3JlYXRlZDogMTgsIHJl
ZC1nYW1tYS10YWJsZQ0KCU9wdGlvbiBjYXBhYmlsaXRpZXM6IDUNClNhbmVPcHRpb24gY3JlYXRl
ZDogMTksIGdyZWVuLWdhbW1hLXRhYmxlDQoJT3B0aW9uIGNhcGFiaWxpdGllczogNQ0KU2FuZU9w
dGlvbiBjcmVhdGVkOiAyMCwgYmx1ZS1nYW1tYS10YWJsZQ0KCU9wdGlvbiBjYXBhYmlsaXRpZXM6
IDUNClNhbmVPcHRpb24gY3JlYXRlZDogMjEsIHdhaXQtZm9yLWJ1dHRvbg0KCU9wdGlvbiBjYXBh
YmlsaXRpZXM6IDY5DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDIyLCBtb25pdG9yLWJ1dHRvbg0KCU9w
dGlvbiBjYXBhYmlsaXRpZXM6IDY5DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDIzLCANCglPcHRpb24g
Y2FwYWJpbGl0aWVzOiA2NA0KU2FuZU9wdGlvbiBjcmVhdGVkOiAyNCwgY2N0LTENCglPcHRpb24g
Y2FwYWJpbGl0aWVzOiAxMDENClNhbmVPcHRpb24gY3JlYXRlZDogMjUsIGNjdC0yDQoJT3B0aW9u
IGNhcGFiaWxpdGllczogMTAxDQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDI2LCBjY3QtMw0KCU9wdGlv
biBjYXBhYmlsaXRpZXM6IDEwMQ0KU2FuZU9wdGlvbiBjcmVhdGVkOiAyNywgY2N0LTQNCglPcHRp
b24gY2FwYWJpbGl0aWVzOiAxMDENClNhbmVPcHRpb24gY3JlYXRlZDogMjgsIGNjdC01DQoJT3B0
aW9uIGNhcGFiaWxpdGllczogMTAxDQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDI5LCBjY3QtNg0KCU9w
dGlvbiBjYXBhYmlsaXRpZXM6IDEwMQ0KU2FuZU9wdGlvbiBjcmVhdGVkOiAzMCwgY2N0LTcNCglP
cHRpb24gY2FwYWJpbGl0aWVzOiAxMDENClNhbmVPcHRpb24gY3JlYXRlZDogMzEsIGNjdC04DQoJ
T3B0aW9uIGNhcGFiaWxpdGllczogMTAxDQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDMyLCBjY3QtOQ0K
CU9wdGlvbiBjYXBhYmlsaXRpZXM6IDEwMQ0KU2FuZU9wdGlvbiBjcmVhdGVkOiAzMywgDQoJT3B0
aW9uIGNhcGFiaWxpdGllczogNjQNClNhbmVPcHRpb24gY3JlYXRlZDogMzQsIHByZXZpZXcNCglP
cHRpb24gY2FwYWJpbGl0aWVzOiA1DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDM1LCBwcmV2aWV3LXNw
ZWVkDQoJT3B0aW9uIGNhcGFiaWxpdGllczogNQ0KU2FuZU9wdGlvbiBjcmVhdGVkOiAzNiwgDQoJ
T3B0aW9uIGNhcGFiaWxpdGllczogNjQNClNhbmVPcHRpb24gY3JlYXRlZDogMzcsIHRsLXgNCglP
cHRpb24gY2FwYWJpbGl0aWVzOiA1DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDM4LCB0bC15DQoJT3B0
aW9uIGNhcGFiaWxpdGllczogNQ0KU2FuZU9wdGlvbiBjcmVhdGVkOiAzOSwgYnIteA0KCU9wdGlv
biBjYXBhYmlsaXRpZXM6IDUNClNhbmVPcHRpb24gY3JlYXRlZDogNDAsIGJyLXkNCglPcHRpb24g
Y2FwYWJpbGl0aWVzOiA1DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDQxLCBxdWljay1mb3JtYXQNCglP
cHRpb24gY2FwYWJpbGl0aWVzOiA2OQ0KU2FuZU9wdGlvbiBjcmVhdGVkOiA0MiwgDQoJT3B0aW9u
IGNhcGFiaWxpdGllczogNjQNClNhbmVPcHRpb24gY3JlYXRlZDogNDMsIHNvdXJjZQ0KCU9wdGlv
biBjYXBhYmlsaXRpZXM6IDM3DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDQ0LCBhdXRvLWVqZWN0DQoJ
T3B0aW9uIGNhcGFiaWxpdGllczogMzcNClNhbmVPcHRpb24gY3JlYXRlZDogNDUsIGZpbG0tdHlw
ZQ0KCU9wdGlvbiBjYXBhYmlsaXRpZXM6IDM3DQpTYW5lT3B0aW9uIGNyZWF0ZWQ6IDQ2LCBmb2N1
cy1wb3NpdGlvbg0KCU9wdGlvbiBjYXBhYmlsaXRpZXM6IDEwMQ0KU2FuZU9wdGlvbiBjcmVhdGVk
OiA0NywgYmF5DQoJT3B0aW9uIGNhcGFiaWxpdGllczogMzcNClNhbmVPcHRpb24gY3JlYXRlZDog
NDgsIGVqZWN0DQoJT3B0aW9uIGNhcGFiaWxpdGllczogMzcNClVwZGF0aW5nIHN0cmluZyBvcHRp
b246IG1vZGUNClVwZGF0aW5nIG51bWJlciBvcHRpb246IGRlcHRoDQpVcGRhdGluZyBzdHJpbmcg
b3B0aW9uOiBoYWxmdG9uaW5nDQpVcGRhdGluZyBzdHJpbmcgb3B0aW9uOiBkcm9wb3V0DQpVcGRh
dGluZyBudW1iZXIgb3B0aW9uOiBicmlnaHRuZXNzDQpVcGRhdGluZyBudW1iZXIgb3B0aW9uOiBz
aGFycG5lc3MNClVwZGF0aW5nIHN0cmluZyBvcHRpb246IGdhbW1hLWNvcnJlY3Rpb24NClVwZGF0
aW5nIHN0cmluZyBvcHRpb246IGNvbG9yLWNvcnJlY3Rpb24NClVwZGF0aW5nIG51bWJlciBvcHRp
b246IHJlc29sdXRpb24NClVwZGF0aW5nIG51bWJlciBvcHRpb246IHRocmVzaG9sZA0KVXBkYXRp
bmcgYm9vbGVhbiBvcHRpb246IG1pcnJvcg0KVXBkYXRpbmcgYm9vbGVhbiBvcHRpb246IHNwZWVk
DQpVcGRhdGluZyBib29sZWFuIG9wdGlvbjogYXV0by1hcmVhLXNlZ21lbnRhdGlvbg0KVXBkYXRp
bmcgYm9vbGVhbiBvcHRpb246IHNob3J0LXJlc29sdXRpb24NClVwZGF0aW5nIG51bWJlciBvcHRp
b246IHpvb20NClVwZGF0aW5nIG51bWJlciBvcHRpb246IHJlZC1nYW1tYS10YWJsZQ0KU3RhcnRp
bmcgcHJldmlldyBzY2FuDQpEZWJ1ZyBzZXNzaW9uIGVuZGVkDQoNCg==
------=_Part_46_1697784.1097300226605--


From usigwanz@lycos.de  Sat Oct  9 14:50:32 2004
From: usigwanz@lycos.de (Ullrich Sigwanz)
Date: Sat, 09 Oct 2004 13:50:32 GMT
Subject: [sane-devel] Scanner Button
Message-ID: <1097329832013643@lycos-europe.com>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--=_NextPart_Lycos_0136431097329832_ID
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><head><style type="text/css">body{font:12px Arial;margin:3px;overflow-y:auto;overflow-x:auto}p{margin:0px;}blockquote, ol, ul{margin-top:0px;margin-bottom:0px;}</style></head>

<body><div style="display: block; font-family: Arial; font-size: 12px;">Hi all,<br>
<br>
Are there thoughts /ideas/implementations for including the button handling in SANE (resp. SANE2) in a standardized way?<br>
<br>
(e.g. a polling daemon, callbacks to start applications etc.)<br>
<br>
Regards<br>
<br>
Ullrich<br>
</br><p style="margin-top:11px;padding-top:3px;background-image: url(http://mail.lycos.co.uk/Images/Mail/_content/dot.gif);background-repeat: repeat-x;background-position: 0px 0px;"><br>2,90 EUR geschenkt: kostenloser Probemonat bei Lycos Premium Mail: 250 MB, Super Antispam, Pop3, SSL uvm -  <a href="http://secure.mail.lycos.de/services/content/packs.jsp?id=1"> jetzt kostenlos testen! </a></div></body></html>


--=_NextPart_Lycos_0136431097329832_ID--



From christoph.knauer@web.de  Sat Oct  9 16:08:28 2004
From: christoph.knauer@web.de (Christoph Knauer)
Date: Sat, 9 Oct 2004 17:08:28 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <20041008095256.GA9991@meier-geinitz.de>
References: <200410071946.25043.christoph.knauer@web.de> <200410072313.05389.christoph.knauer@web.de> <20041008095256.GA9991@meier-geinitz.de>
Message-ID: <200410091708.34359.christoph.knauer@web.de>

--nextPart7731823.kJYL0kSC6s
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

ok, I'm trying the snapshot from today ...

Bye,
Christoph

Am Freitag, 8. Oktober 2004 11:52 schrieb Henning Meier-Geinitz:
> Hi,
>
> On Thu, Oct 07, 2004 at 11:13:05PM +0200, Christoph Knauer wrote:
> > For info: it seems to be a problem with the last build on my system ...
> > using the package before (which I know as good) -> ok, all is working
> > fine Using the last builded package -> nothing works, only error:
> >
> > Julia2002:~ # scanimage -L
> > scanimage: relocation error: /usr/local/lib/sane/libsane-microtek2.so.1:
> > undefined symbol: sanei_thread_init
> >
> > On the weekend perhaps I've more time to search the solution ...
>
> The reason is that you only use a new microtek2 backend.
> backend/Makefile.in also must be updated.
>
> As the latest microtek2 code is now in CVS I recommend using a CVS
> snapshot.
>
> Bye,
>   Henning

=2D-=20
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
=2D----
alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
unter http://www.profiseller.de/shop/christoph-knauer

--nextPart7731823.kJYL0kSC6s
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBZ/7ygy/nEXRCgmERAri5AKCAVJJLHlFtIe2+nR+t2BIdjgU/+ACfTaSk
N51w0xW5rwNh14/KQAgMk1g=
=s32i
-----END PGP SIGNATURE-----

--nextPart7731823.kJYL0kSC6s--


From anoah@pfeiffer.edu  Sat Oct  9 16:34:43 2004
From: anoah@pfeiffer.edu (m. allan noah)
Date: Sat, 9 Oct 2004 11:34:43 -0400 (EDT)
Subject: [sane-devel] Scanner Button
In-Reply-To: <1097329832013643@lycos-europe.com>
References: <1097329832013643@lycos-europe.com>
Message-ID: <Pine.LNX.4.61.0410091126330.30301@limos.pfeiffer.edu>

there has been much discussion in the past, but everyone seems too busy to 
actually get anything in writing. search the archives of the sane mailing 
list, there where several threads about it in the earlier part of this 
year, IIRC.

basically:

front end polling a backend via asking for updates on certain OPTs seems 
to be the consensus. details that need work: how to identify which opts, 
recommendations for how frontends could display that data, and does the 
backend need to be able to specify the polling interval. how the buttons 
are affected by the network scanner locking code also seems like a good 
topic for discussion.

allan

On Sat, 9 Oct 2004, Ullrich Sigwanz wrote:

> Hi all,
> 
> Are there thoughts /ideas/implementations for including the button
> handling in SANE (resp. SANE2) in a standardized way?
> 
> (e.g. a polling daemon, callbacks to start applications etc.)
> 
> Regards
> 
> Ullrich
> 
> 
> 2,90 EUR geschenkt: kostenloser Probemonat bei Lycos Premium Mail: 250
> MB, Super Antispam, Pop3, SSL uvm - jetzt kostenlos testen!
> 
>

-- 
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera


From mattias.ellert@tsl.uu.se  Sat Oct  9 19:59:23 2004
From: mattias.ellert@tsl.uu.se (Mattias Ellert)
Date: Sat, 9 Oct 2004 20:59:23 +0200
Subject: [sane-devel] niash backend dependencies in backend/Makefile.in
In-Reply-To: <20041008110325.GA23598@meier-geinitz.de>
References: <4165ABC5.5040406@zonnet.nl> <20041008110325.GA23598@meier-geinitz.de>
Message-ID: <55B42F66-1A25-11D9-9296-0003930D2AFC@tsl.uu.se>

2004-10-08 kl. 13.03 skrev Henning Meier-Geinitz:

> Hi,
>
> On Thu, Oct 07, 2004 at 10:49:09PM +0200, Bertrik Sikken wrote:
>> I just tried sane-backends CVS and found that it did not work
>> for my hp3300 (niash backend). Scanimage -L complains about
>> missing 'sanei_scsi_find_devices'. I think this is somehow
>> pulled in from another sanei function.

I have the same problem with the CVS version...

  gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes 
-pedantic -DHAVE_CONFIG_H -I. -I. -I../include -I../include 
-DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d 
-DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 
-D_REENTRANT -DBACKEND_NAME=niash -DLIBDIR=/usr/local/lib/sane niash.c  
-fno-common -DPIC -o .libs/niash.o
niash.c: In function `sane_niash_exit':
niash.c:805: warning: cast discards qualifiers from pointer target type
rm -f niash-s.c
ln -s ./stubs.c niash-s.c
  gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes 
-pedantic -DHAVE_CONFIG_H -I. -I. -I../include -I../include 
-DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d 
-DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 
-D_REENTRANT -DSTUBS -DBACKEND_NAME=niash niash-s.c  -fno-common -DPIC 
-o .libs/niash-s.o
gcc -bundle  -o .libs/libsane-niash.1.0.14.so  .libs/niash.o 
.libs/niash-s.o .libs/sane_strstatus.o 
../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o 
../lib/.libs/isfdtype.o ../lib/.libs/strndup.o 
../sanei/.libs/sanei_config2.o ../sanei/.libs/sanei_constrain_value.o 
../sanei/.libs/sanei_usb.o  /usr/local/lib/libusb-0.1.4.4.1.dylib 
-lpthread -lm -framework CoreFoundation -framework IOKit
ld: Undefined symbols:
_sanei_scsi_find_devices
make[1]: *** [libsane-niash.la] Error 1
make: *** [all-recursive] Error 1

> That's called from sanei_config_attach_matching_devices.
>
> However, at least in current CVS niash doesn't seem to use that
> function.
>
>> I noticed that nearly all other backends have a line in
>> backend/Makefile.in that declares dependency on sanei_scsi.lo
>> (the niash backend does not have it)
>> Adding the following line to backend/Makefile.in made it work
>> for me:
>> libsane-niash.la: ../sanei/sanei_scsi.lo

Well, the correct fix is to remove the line asking for linking against 
sanei_config2.lo

--- sane-backends-2004-10-09-cvs.orig/backend/Makefile.in       Sun Oct 
  3 19:39:43 2004
+++ sane-backends-2004-10-09-cvs/backend/Makefile.in    Sat Oct  9 
20:09:03 2004
@@ -365,7 +365,6 @@
  libsane-net.la: ../sanei/sanei_codec_bin.lo
  libsane-net.la: ../sanei/sanei_net.lo
  libsane-net.la: ../sanei/sanei_wire.lo
-libsane-niash.la: ../sanei/sanei_config2.lo
  libsane-niash.la: ../sanei/sanei_constrain_value.lo
  libsane-niash.la: ../sanei/sanei_usb.lo
  libsane-pint.la: ../sanei/sanei_constrain_value.lo

If this line is removed the linking works...

	Mattias



From christoph.knauer@web.de  Sat Oct  9 22:18:31 2004
From: christoph.knauer@web.de (Christoph Knauer)
Date: Sat, 9 Oct 2004 23:18:31 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <20041008095256.GA9991@meier-geinitz.de>
References: <200410071946.25043.christoph.knauer@web.de> <200410072313.05389.christoph.knauer@web.de> <20041008095256.GA9991@meier-geinitz.de>
Message-ID: <200410092318.37609.christoph.knauer@web.de>

--nextPart1558445.qRXEbktaJs
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

Ive just testet with the todays snapshot. The Lightlid will work, but there=
 is=20
the wrong-color-problem again.

I've modified the microtek2.c with the change I got from Karsten 1,5 years=
=20
ago, and now it works fine, with right colors.

Bye,

Christoph

Am Freitag, 8. Oktober 2004 11:52 schrieb Henning Meier-Geinitz:
> Hi,
>
> On Thu, Oct 07, 2004 at 11:13:05PM +0200, Christoph Knauer wrote:
> > For info: it seems to be a problem with the last build on my system ...
> > using the package before (which I know as good) -> ok, all is working
> > fine Using the last builded package -> nothing works, only error:
> >
> > Julia2002:~ # scanimage -L
> > scanimage: relocation error: /usr/local/lib/sane/libsane-microtek2.so.1:
> > undefined symbol: sanei_thread_init
> >
> > On the weekend perhaps I've more time to search the solution ...
>
> The reason is that you only use a new microtek2 backend.
> backend/Makefile.in also must be updated.
>
> As the latest microtek2 code is now in CVS I recommend using a CVS
> snapshot.
>
> Bye,
>   Henning

=2D-=20
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
=2D----
alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
unter http://www.profiseller.de/shop/christoph-knauer

--nextPart1558445.qRXEbktaJs
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBaFWtgy/nEXRCgmERAlNsAJ9RswvF8228hKI8wVIMUJX0RABJxACeMCGX
9+4ZLsWSEsekatJi+dUWZks=
=j25b
-----END PGP SIGNATURE-----

--nextPart1558445.qRXEbktaJs--


From Anton Mazkovoi <anton.mazkovoi@gmail.com>  Sun Oct 10 08:55:27 2004
From: Anton Mazkovoi <anton.mazkovoi@gmail.com> (Anton Mazkovoi)
Date: Sun, 10 Oct 2004 17:55:27 +1000
Subject: [sane-devel] Re: SaneTwain - windows losing connection
In-Reply-To: <9647569f0410082237451ebb75@mail.gmail.com>
References: <9647569f0410082237451ebb75@mail.gmail.com>
Message-ID: <9647569f04101000552a199d27@mail.gmail.com>

I have updated the driver for my network card and everything works
flawlessly  now.

Thanks,
Anton



On Sat, 9 Oct 2004 15:37:06 +1000, Anton Mazkovoi
<anton.mazkovoi@gmail.com> wrote:
> Hi,
> 
> I have a epson cx6500 scanner/printer which I have working with epkowa
> drivers and sane-backends-1.0.12-2 on a RedHat 9 box. Saned is started
> through xinetd and I have a Windows XP SP1 machine running SaneTwain
> 1.25 and scanning images with no problem.
> 
> Another Windows XP SP1 machine on the same local network refuses to
> scan. Its running the same version of SaneTwain. When scanimage.exe is
> started it tries to retrieve the scanners from the server and I see
> the saned process started on the server (and a connection reported on
> both windows and linux boxes using "netstat -na"). The scanimage
> window is unusable (unclickable) for a while. After some time  the
> window becomes usable and the devices dropdown is correctly populated
> with the scanner's device.
> 
> Clicking "preview" or "scan", results in a pop-up which says: "Write
> error 64, the specified network name is no longer available". When I
> do a "netstat -na" on a windows box I can see that the tcp connection
> is NOT there. The linux box (netstat -na) thinks the connection IS
> there, the saned process is still running and is doing a read from the
> socket which is (was) connected to the windows box.
> 
> Also, the "options" tab of the scanimage window is completely empty.
> (On the working windows XP box it shows options).
> 
> Also, printing to the scanner/printer device from both windows boxes
> causes no problems. The linux box also acts as the gateway to the
> internet for both windows boxes. Surfing the web and downloading files
> from both machines seems to have no problems.
> 
> I am attaching the log produced by running scanimage --debug on the
> non-working windows box.
> 
> Is this a known windows problem? Has anyone seen anything like this before?
> 
> Any help is very much appreciated!
> 
> Thanks in advance,
> Anton
> 
> 
>


From nr19ch@freesurf.ch  Sun Oct 10 13:35:28 2004
From: nr19ch@freesurf.ch (nr19ch)
Date: Sun, 10 Oct 2004 14:35:28 +0200
Subject: [sane-devel] Agfa Snapscan e40 and Suse9.1
Message-ID: <200410101435.28178.nr19ch@freesurf.ch>

Hello
I try to install Snapscan e40. I've installed it with Yast but when I launch 
xsane I get the error message "failed to open device 
'snapscan:libusb:001:003'.
I've had a Mustek Scanner 1200Cu plus installed and it worked fine. Do I have 
to uninstall somethig before using my new scanner (cause after I've installed 
the new scaner my old mustek still works fine.)
I don't know much about linux and hope that there is anybody who can provide 
help for my problem.
Thanks! D.S.


From tomasz.orlinski@wp.pl  Fri Oct  8 15:06:14 2004
From: tomasz.orlinski@wp.pl (Tomasz Orlinski)
Date: Fri, 8 Oct 2004 16:06:14 +0200
Subject: [sane-devel] USB scanners DO work on Solaris 10 x86
References: <002501c4ac9d$8be2b530$0100a8c0@athlon64> <20041007190233.GI8083@meier-geinitz.de>
Message-ID: <001f01c4ad40$59044220$0100a8c0@athlon64>

Yes, I think it would be a good idea to include this information to
README.solaris file. I have used 1.0.14 release of sane-backends. Sun in
Driver Development Kit v. 0.9 writes how to compile SANE, but it does not
really work :) They write about compiling with gcc and give options for Sun
Forte compiler (cc) and forget about attaching a kernel driver. But they
write, that versions earlier than 1.0.14 cannot be used. They want also to
build SANE with Posix threads enabled. So I think that can be true. Sun
writes also, that Solaris Software Express release at least S10_62 is needed
to use libusb. Release number can be checked in /etc/release. The newest
version can be downloaded from www.sun.com/solaris for free.
In my opinion it is important to be cautious when using scanner or just
libusb on important Solaris machines (especially multi-processor ones),
because unlike in other systems, Solaris kernel is fully preemtible, what
means, that many instances of the same driver can ran simultanously - it's
dangerous, when drivers are not perfect. And Solaris USB framework is
absolutely new, so it can contain bugs. I tried to crash my Solaris using
USB subsystem and SANE, I didn't manage to, but it doesn't mean, it's
impossible.
SANE frontends work without any problems with Xsun and GIMP included in
Solaris Software Companion CD.



From marc53shapiro@hotmail.com  Sat Oct  9 10:06:06 2004
From: marc53shapiro@hotmail.com (Marc)
Date: Sat, 9 Oct 2004 10:06:06 +0100
Subject: [sane-devel] scanning on Epson Stylus Scan 2500 works
Message-ID: <7409F833-19D2-11D9-81EF-000393CD04D6@hotmail.com>

A message from a happy user: even though the all-in-one Epson Stylus 
Scan 2500 is not listed on your list of supported scanners, it works 
for me (on MacOS X 10.3.5, flatpanel iMac).  Thanks!!!

												Marc




From dwhysong@physics.ucsb.edu  Sun Oct 10 05:07:07 2004
From: dwhysong@physics.ucsb.edu (David Whysong)
Date: Sat, 9 Oct 2004 21:07:07 -0700
Subject: [sane-devel] Epson 2480 not detected
Message-ID: <34eaeeaa0410092107abeda33@mail.gmail.com>

Hi,

I read the previous reports about making this scanner work, but I have
had no luck.

I removed the SANE frontend and backend RPMs, then downloaded and
compiled the current CVS backend. I copied the hotplug scripts to
/etc/hotplug/usb, extracted the firmware and put the proper path and
the vendor/device ID line in the /usr/local/etc/sane.d/snapscan.conf
file.

Here is what I have:

[dwhysong@sleepy sane-backends]$ sane-find-scanner
[...]
found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON
Scanner]) at libusb:001:011
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.
[...]

[dwhysong@sleepy sane-backends]$ scanimage -L
                                                                                
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).


I have rw permissions for the /proc/bus/usb/001/011 file.

The other "curiosity" is this. Upon connecting the USB cable, I see:

Oct  9 21:04:22 sleepy kernel: usb 1-1: new full speed USB device
using address 12
Oct  9 21:04:22 sleepy /etc/hotplug/usb.agent: Bad USB agent invocation
Oct  9 21:04:25 sleepy /etc/hotplug/usb.agent: Setup libusbscanner for
USB product 4b8/121/110
Oct  9 21:04:25 sleepy /etc/hotplug/usb.agent: Module setup
libusbscanner for USB product 4b8/121/110
Oct  9 21:04:26 sleepy devlabel: devlabel service started/restarted

I'm not sure why I'm getting "Bad USB agent invocation" -- that
happens when the $PRODUCT or $ACTION variables are not defined for
usb.agent (and I verified that neither are defined). But it seems to
run the libusbscanner script, so I'm guessing the real problem does
not lie with the hotplug scritps.

Kernel 2.6.6-rc1, x86_64 architecture.

Any suggestions?

-- 
David


From nr19ch@freesurf.ch  Sun Oct 10 14:04:39 2004
From: nr19ch@freesurf.ch (nr19ch)
Date: Sun, 10 Oct 2004 15:04:39 +0200
Subject: [sane-devel] Again Agfa Snapscan e40 and Suse9.1
Message-ID: <200410101504.39487.nr19ch@freesurf.ch>

Hello everybody again
Finally managed to solve my problem and the scanner now works fine (there was 
no read or write permission for the firmware file). Sorry for my disturbing 
mail and have a good time enjoying Linux.
D.S.


From henning@meier-geinitz.de  Sun Oct 10 14:16:39 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 15:16:39 +0200
Subject: [sane-devel] scanning on Epson Stylus Scan 2500 works
In-Reply-To: <7409F833-19D2-11D9-81EF-000393CD04D6@hotmail.com>
References: <7409F833-19D2-11D9-81EF-000393CD04D6@hotmail.com>
Message-ID: <20041010131639.GD3144@meier-geinitz.de>

Hi,

On Sat, Oct 09, 2004 at 10:06:06AM +0100, Marc wrote:
> A message from a happy user: even though the all-in-one Epson Stylus 
> Scan 2500 is not listed on your list of supported scanners, it works 
> for me (on MacOS X 10.3.5, flatpanel iMac).  Thanks!!!

Thanks for your report. Can you give some more details, i.e. what's
teh output of:

scanimage -L
and
scanimage --version

Bye,
  Henning



From henning@meier-geinitz.de  Sun Oct 10 14:20:12 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 15:20:12 +0200
Subject: [sane-devel] Scanner Button
In-Reply-To: <1097329832013643@lycos-europe.com>
References: <1097329832013643@lycos-europe.com>
Message-ID: <20041010132012.GE3144@meier-geinitz.de>

Hi,

On Sat, Oct 09, 2004 at 01:50:32PM +0000, Ullrich Sigwanz wrote:
> <html><head><style type="text/css">body{font:12px Arial;margin:3px;overflow-y:auto;overflow-x:auto}p{margin:0px;}blockquote, ol, ul{margin-top:0px;margin-bottom:0px;}</style></head>

Buh, HTML.


> Are there thoughts /ideas/implementations for including the button
> handling in SANE (resp. SANE2) in a standardized way?<br>

See chapter 4.5.14 of the latest SANE2 draft for a possible interface.
Also see lots of discussions on sane-devel. If you want to discuss the
way how to implement the SANE interface (backend/frontend) for
buttons, the sane-standard list is the right one.

Bye,
  Henning



From henning@meier-geinitz.de  Sun Oct 10 14:23:39 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 15:23:39 +0200
Subject: [sane-devel] Epson 2480 not detected
In-Reply-To: <34eaeeaa0410092107abeda33@mail.gmail.com>
References: <34eaeeaa0410092107abeda33@mail.gmail.com>
Message-ID: <20041010132339.GF3144@meier-geinitz.de>

Hi,

On Sat, Oct 09, 2004 at 09:07:07PM -0700, David Whysong wrote:
> [dwhysong@sleepy sane-backends]$ scanimage -L
>                                                                                 
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
> 
> 
> I have rw permissions for the /proc/bus/usb/001/011 file.

Does scanimage -L find the scanner as root? If it doesn't, it's not a
permissions nor hotplug issue.

Enable debugging like this:
export SANE_DEBUG_SNAPSCAN=255 
and run scanimage -L again. Please show us the debug output.

Bye,
  Henning


From henning@meier-geinitz.de  Sun Oct 10 14:34:45 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 15:34:45 +0200
Subject: [sane-devel] Upgrading sane-backend on Mandrake 10.0
In-Reply-To: <3DDE554B.2030606@dccnet.com>
References: <3DDE554B.2030606@dccnet.com>
Message-ID: <20041010133445.GG3144@meier-geinitz.de>

Hi,

On Fri, Nov 22, 2002 at 08:03:23AM -0800, Lloyd Sumpter wrote:

Strange date.

> <RANT MODE ON>
> This is what bugs me about Linux packages! In order to upgrade one 
> simple program, you end up upgrading your entire OS!!

You don't need to do that. At least I haven't ever needed to do that.
Just get the latest package and install it. Well it's mandrake so ...
:-)

> What the H*LL does sane-backends have to do with harddrake, anyway?

sane-backends doesn't know anything about harddrake and couldn't care
less :-)

> So, apparently libsane1-1.0.13 is required by kdegraphics, and 
> sane-backends-1.0.13 is required by harddrake. I looked at kdegraphics 
> and decide I don't need it, so erase it. Then I go ahead and upgrade to 
> libsane1-1.0.14-3mdk and sane-backends-1.0.14-3mdk.

I don't know these details but I'm surprised that they need a specific
version of sane-backends.

> Next thing I know, my CPU meter is pinned and performance is fast 
> disappearing. I manage to reboot before it goes away altogether. Next 
> boot, same thing starts, but I manage to find out it's "scannerdrake", 
> along with sane-find-scanner and several usb utilities (*I* didn't run 
> these programs!) are using all the resources. I manage to erase the 
> sane-backends, which stops the bleeding. I re-install 1.0.13 and all is 
> well again.

I have never heard that anything from sane-backends does this. So I
think it's one of the Mandrake tools.

> No man pages for harddrake or scannerdrake.
> 
> So...How do I upgrade sane-backends on Mandrake 10.0 without sending 
> harddrake (I assume that's what's launching scannerdrake?) into a 
> tailspin? Also, what is "libsane"? It seems to be required in Mandrake, 
> but I don't see it in the source code packages - is it normally just 
> included in the sane-backend package?

The package "libsane" seems to be an invention of distributors. I know
that debian has the source package "sane-backends" and binary package
"libsane" (the SANE libraries) and "sane-utils" (e.g. scanimage).
Maybe it's similar with Mandrake?

Most of your questions are better suited in a Mandrake forum as they
aren't really related to SANE itsself but the packages created by
Mandrake.

> BTW: The reason I have to upgrade is that apparently the sane-backends 
> included with Mandrake 10.0 do NOT support libusb (but since the kernel 
> is 2.6.x, there's no scanner.o to use instead...)

sane-backends supports libusb since quite some time. And it was needed
before kernel 2.6 at least for some scanners. So I'd be surprised if
the Mandrake version had no libusb support.

You can check by running "sane-find-scanner -v -v". It should print
messages about using libusb.

Bye,
  Henning


From henning@meier-geinitz.de  Sun Oct 10 15:15:16 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 16:15:16 +0200
Subject: [sane-devel] Feature Freeze for sane-frontends 1.0.13: Snapshot
Message-ID: <20041010141516.GI3144@meier-geinitz.de>

Hi everyone,

Feature freeze for sane-frontends 1.0.13 is active now. If no grave
bugs are found, the package will be released 2004-10-17 (next Sunday).

There is a 1.0.13-pre1 snapshot. Please test it and report any bugs to
the bug tracking system.

Download:
http://alioth.debian.org/project/showfiles.php?group_id=30186
ftp://ftp.sane-project.org/pub/sane/

The Changelog is attached.

Bye,
  Henning

-- snapshot 1.0.13-pre1

2004-10-10  Henning Meier-Geinitz <henning@meier-geinitz.de>

	* Makefile.in: Added xscanimage-icon-48x48-2.png to DISTFILES.

2004-10-05  Henning Meier-Geinitz <henning@meier-geinitz.de>

	* xscanimage-icon-48x48-2.png: Added xscanimage icon (from Maciek
	  Podkomorzy <gammaray@satfilm.net.pl>).

2004-10-03  Henning Meier-Geinitz <henning@meier-geinitz.de>

	* src/gtkglue.c: Don't try to print non-readable options. Don't
	  try to write non-writable options (bug #300621). Don't print
	  warnings for options without constraints.

2004-07-09  Henning Meier-Geinitz <henning@meier-geinitz.de>

	* doc/scanadf.man src/scanadf.c: Added -N option to stop scanadf
	  from overwriting files (patch from Paul Walmsley
	  <paul@booyaka.com>). 

2004-05-12  Henning Meier-Geinitz <henning@meier-geinitz.de>

	* acinclude.m4 aclocal.m4 configure sane-frontends.lsm: Removed
	  old links to ftp.mostang.com.

2004-04-29  Julien Blache <jb@jblache.org>
	* src/gtkglue.h: looks like someone wanted GSGDialog.twocolumn to
	an int rather than a GtkWidget *. Fixed.

2004-04-24  Henning Meier-Geinitz <henning@meier-geinitz.de>

	* Makefile.in: Remove autoconf temp files in distclean.

2004-04-20  Julien Blache <jb@jblache.org>

	* src/preview.c: make the preview work when it's resized.

2004-04-19  Julien Blache <jb@jblache.org>

	* src/xcam.c: fixed xcam layout.

2004-04-17  Henning Meier-Geinitz <henning@meier-geinitz.de>

	* configure configure.in: Set version to 1.0.12-cvs.
	



From mogensjaeger@get2net.dk  Sun Oct 10 15:59:10 2004
From: mogensjaeger@get2net.dk (Mogens Jaeger)
Date: Sun, 10 Oct 2004 16:59:10 +0200
Subject: [sane-devel] Translation
Message-ID: <41694E3E.7080109@get2net.dk>

Hello
I was looking in the cvs at:=20
http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/sane-frontends/?cvsroot=3D=
sane,=20
for a po/pot file for the 'sane-frontends 1.0.13' but I did not find any=20
- is it not aviable, or am I looking a wrong place?

--=20
mvh Mogens J=E6ger



From henning@meier-geinitz.de  Sun Oct 10 16:32:05 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 17:32:05 +0200
Subject: [sane-devel] Translation
In-Reply-To: <41694E3E.7080109@get2net.dk>
References: <41694E3E.7080109@get2net.dk>
Message-ID: <20041010153205.GJ3144@meier-geinitz.de>

Hi,

On Sun, Oct 10, 2004 at 04:59:10PM +0200, Mogens Jaeger wrote:
> I was looking in the cvs at: 
> http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/sane-frontends/?cvsroot=sane, 
> for a po/pot file for the 'sane-frontends 1.0.13' but I did not find any - 
> is it not aviable, or am I looking a wrong place?

None of the frontends included in the sane-frontends package has
internationalization support.

Bye,
  Henning


From joehenley@kc.rr.com  Sun Oct 10 21:40:10 2004
From: joehenley@kc.rr.com (Joe Henley)
Date: Sun, 10 Oct 2004 15:40:10 -0500
Subject: [sane-devel] umax_pp slow
In-Reply-To: <20041004044644.GA6220@wanadoo.fr>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com> <20041001042733.GA2166@wanadoo.fr> <415D7E43.8080907@kc.rr.com> <20041004044644.GA6220@wanadoo.fr>
Message-ID: <41699E2A.5010109@kc.rr.com>

Hi Stef,

Sorry for the delay in responding.  I was out of town on business.

svoltz@wanadoo.fr wrote:
> 	Hello,
> 
> 	I think you should try again ECP. I think the message you get is
> harmless. You can comment it out in the sourcecode before doing tests
> again. 

I'm not sure I understand which message you're referring to.  With the 
BIOS set for ECP, it (scanimage -L 2>log) just runs on without stopping. 
  I have to use ^C to stop it.  Is that the message you refer to?

The BIOS says it's ECP, but Linux doesn't report it that way in the 
/var/log/messages or kernel files.  Very odd!  Even more odd is that I 
run Win4Lin on this machine, using Win98.  I can run Linux running 
Win4Lin, running Win98, running the VistaScan copier program, and it 
runs just fine.  The speed is very good.  So somehow it's figuring out 
to run quickly thru the parallel port.  If I shut down 
VistaScan/Win98/Win4Lin and without rebooting, load up sane and try it, 
it's very slow.  Arrrgh!

Any suggestions?

> 	But until you see ECP mode detected by ythe linux kernel, I'm
> afraid you'll have troubles.
> 
> Regards,
> 	Stef
> 
Thanks!

Joe Henley


From Oliver.Rauch@Rauch-Domain.DE  Sun Oct 10 21:36:43 2004
From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch)
Date: 10 Oct 2004 22:36:43 +0200
Subject: [sane-devel] Two xsane-Win32-0.96 annoyancies
In-Reply-To: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>
References: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>
Message-ID: <1097440603.2148.4.camel@Babylon7>

Am Fre, 2004-10-08 um 11.29 schrieb peder:
>  Thanx for a nifty port.
> 
>  I've been happlily using xsane in out school network for a couple of
>  years. We have 5 old linux boxes scattered around the place as scanner
>  servers and the WinXP/Win98-clients use xsane to connect.
> 
>  However there are two issues.
> 
>  The minor one: Is there a technical reason why the program has to
>  be installed to c:\sane? Can't the program search for it's files
>  using perhaps a XSANE variable or in current directory?
>  I like to have the program installed on the server so I can upgrade
>  it for every user and not having to walk around 300+ PC's.
>  This works in 0.90 on Win98 but not on WinXP for some reason.
>  In 0.96 it works on neither.

XSane uses hardcoded paths. This is a usual way on unix systems.
The paths are created while configurating xsane and are compiled in.
When you compile xsane-win32 yourself then you can compile in your own
paths.

> 
>  I found out you only have to put some files in c:\sane so I can
>  distribute those every time, so this issue is not a biggie.
> 
>  The major one: In xsane-0.83 and 0.90 I could run
>  'xsane.exe ip-of-scan-server:device'. In 0.96 this doesn't work; I have
>  to add all my servers in net.conf, wait for xsane to "scan for devices"
>  and choose the right one from five nearly identical entries.
>  Maybe I can pick the right one but definitely not my users.
>  Can we please have the scan-server argument back?
> 

The differences between 0.95/0.96 and the previous xsane-win32 versions
are that the new versions are linked against sane-dll, the old versions
were linked agains sane-net.

You have to use the same syntax as in linux:

xsane net:192.168.0.1



>  FYI, version 0.90 was much faster than 0.96. I tried them on a
>  400MHz and 0.96 was really sluggish, perhaps due to newer gtk versions.

On my systems I had the feeling that xsane-0.96 is much faster. Do you
use the same settings in preferences and view?

Oliver



From sean035@yahoo.com.tw  Mon Oct 11 01:52:22 2004
From: sean035@yahoo.com.tw (sean035@yahoo.com.tw)
Date: Mon, 11 Oct 2004 08:52:22 +0800 (CST)
Subject: [sane-devel] permission problem
Message-ID: <20041011005222.87323.qmail@web17807.mail.tpe.yahoo.com>

Hello everybody,
I had meet a strange things when I developing new
scanner backend. I can make my scanner work fine as
root account or super user, but didn't as the others
account. Now, my new scanner backend can work fine and
support Xsane as log in root this super user but I
can't use "scanimage -L" to find my scanner device. Is
problem about permission or another situation? If is,
which permission of device file I have to setup?
Thanks a lot for everyone.
Walker,  

-----------------------------------------------------------------
Yahoo!İ_ĵŻıq¤lĞH½c
100MB §KĥOĞH½cĦAıq¤lĞH½c·sĴö¤¸ħq³oĥ}İlĦI
http://mail.yahoo.com.tw/


From gerhard@gjaeger.de  Mon Oct 11 07:43:56 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Mon, 11 Oct 2004 08:43:56 +0200
Subject: [sane-devel] permission problem
In-Reply-To: <20041011005222.87323.qmail@web17807.mail.tpe.yahoo.com>
References: <20041011005222.87323.qmail@web17807.mail.tpe.yahoo.com>
Message-ID: <200410110843.56481.gerhard@gjaeger.de>

On Monday 11 October 2004 02:52, sean035@yahoo.com.tw wrote:
> Hello everybody,
> I had meet a strange things when I developing new
> scanner backend. I can make my scanner work fine as
> root account or super user, but didn't as the others
> account. Now, my new scanner backend can work fine and
> support Xsane as log in root this super user but I
> can't use "scanimage -L" to find my scanner device. Is
> problem about permission or another situation? If is,
> which permission of device file I have to setup?

See README.linux.
BTW: On what "new"-backend are you working? Which is the supported
scanner?

--
  Gerhard



From afb@paradise.net.nz  Mon Oct 11 10:41:33 2004
From: afb@paradise.net.nz (Adam Felix Bogacki)
Date: Mon, 11 Oct 2004 22:41:33 +1300
Subject: [sane-devel] xsane-win32
Message-ID: <416A554D.6000509@paradise.net.nz>

Sorry Oliver. I removed and re-installed  Epson Smart Panel for Scanner 
and Twain and it
recognised the scanner and was usable. However, xsane springs into action,
shows me the 'Xsane End User Licence Agreement', and after I click the 
'I accept' panel
searches around and quickly gives me  'no devices available'.

It was doing this when Smart Panel and Twain were not working so I don't 
think it may be
a case of the scanner being assigned to one program and denied to 
another. I could be wrong.

I have gone through the 'help' list of  possible reasons for this and 
the only thing which looks
plausible is  'backend is not configured correct'.

In 'C:\sane\etc\sane.d\net.conf' I used 'localhost' and '192.168.0.1' - 
the localhost TCP/IP address ..

In 'C:\sane\etc\sane.d\dll.conf' the only lines enabled are 'epson' and 
'gphoto2' (in case of future digital camera use) , and in

'C:\sane\etc\sane.d\epson.conf' the only uncommented lines are

'usb 0x04b8 0x010c' and 'usb /dev/usb/scanner0'

Are there any obvious errors here ? Confusion of backward and forward slashes ?

One thing I came across in reading WinXP help files was that Twain does not work
after the scanner is disconnected (as in re-plugging with Linux hotplug). It then has to be
reinstalled via XP's 'New Hardware Install' wizard. 

Could this be contributing here ?

It's frustrating having a fine program like xsane not working in XP. 

Adam Bogacki,
afb@paradise.net.nz




From afb@paradise.net.nz  Mon Oct 11 11:06:30 2004
From: afb@paradise.net.nz (Adam Felix Bogacki)
Date: Mon, 11 Oct 2004 23:06:30 +1300
Subject: [sane-devel] xsane-win32: 'cygwin1.dll was not found'
Message-ID: <416A5B26.3040803@paradise.net.nz>

Hi, trying 'sane-find-scanner' gave the error message

'This application has failed to start because cygwin1.dll was not found.
Re-installing the application may fix this problem'.

I'll keep trying.

Adam.




From karsten.festag@gmx.de  Mon Oct 11 13:16:20 2004
From: karsten.festag@gmx.de (Karsten Festag)
Date: Mon, 11 Oct 2004 14:16:20 +0200 (MEST)
Subject: [sane-devel] scanning via network
References: <200410092318.37609.christoph.knauer@web.de>
Message-ID: <23810.1097496980@www47.gmx.net>

Hi,

I thought I had merged the fix for the wrong color problem into the latest
backend but obviously not :-(
Unfortunately I have not much time this week, so:
Christoph, could you please re-send my modification to me to make sure I'm
not mixing something? Thanks! I'll check what's going on.

Karsten

> Hi,
> 
> Ive just testet with the todays snapshot. The Lightlid will work, but
> there is 
> the wrong-color-problem again.
> 
> I've modified the microtek2.c with the change I got from Karsten 1,5 years
> ago, and now it works fine, with right colors.
> 
> Bye,
> 
> Christoph
> 
> Am Freitag, 8. Oktober 2004 11:52 schrieb Henning Meier-Geinitz:
> > Hi,
> >
> > On Thu, Oct 07, 2004 at 11:13:05PM +0200, Christoph Knauer wrote:
> > > For info: it seems to be a problem with the last build on my system
> ...
> > > using the package before (which I know as good) -> ok, all is working
> > > fine Using the last builded package -> nothing works, only error:
> > >
> > > Julia2002:~ # scanimage -L
> > > scanimage: relocation error:
> /usr/local/lib/sane/libsane-microtek2.so.1:
> > > undefined symbol: sanei_thread_init
> > >
> > > On the weekend perhaps I've more time to search the solution ...
> >
> > The reason is that you only use a new microtek2 backend.
> > backend/Makefile.in also must be updated.
> >
> > As the latest microtek2 code is now in CVS I recommend using a CVS
> > snapshot.
> >
> > Bye,
> >   Henning
> 
> -- 
> GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
> -----
> alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
> unter http://www.profiseller.de/shop/christoph-knauer
> 

-- 
GMX ProMail mit bestem Virenschutz http://www.gmx.net/de/go/mail
+++ Empfehlung der Redaktion +++ Internet Professionell 10/04 +++



From marc53shapiro@hotmail.com  Sun Oct 10 14:51:48 2004
From: marc53shapiro@hotmail.com (Marc)
Date: Sun, 10 Oct 2004 14:51:48 +0100
Subject: [sane-devel] scanning on Epson Stylus Scan 2500 works
In-Reply-To: <20041010131639.GD3144@meier-geinitz.de>
References: <7409F833-19D2-11D9-81EF-000393CD04D6@hotmail.com> <20041010131639.GD3144@meier-geinitz.de>
Message-ID: <87A94C23-1AC3-11D9-A0FB-000393CD04D6@hotmail.com>

Le 10 oct. 04, =E0 14:16, Henning Meier-Geinitz a =E9crit :

>> A message from a happy user: even though the all-in-one Epson Stylus
>> Scan 2500 is not listed on your list of supported scanners, it works
>> for me (on MacOS X 10.3.5, flatpanel iMac).  Thanks!!!
>
> Thanks for your report. Can you give some more details, i.e. what's
> teh output of:
>
> scanimage -L

device `epson:libusb:001:006-04b8-0106-ff-ff' is a Epson StylusScan2500=20=

flatbed
scanner

> and
> scanimage --version

scanimage (sane-backends) 1.0.14-cvs; backend version 1.0.14

										=
	Marc





From dwhysong@physics.ucsb.edu  Sun Oct 10 19:13:11 2004
From: dwhysong@physics.ucsb.edu (David Whysong)
Date: Sun, 10 Oct 2004 11:13:11 -0700
Subject: [sane-devel] Epson 2480 not detected
In-Reply-To: <20041010132339.GF3144@meier-geinitz.de>
References: <34eaeeaa0410092107abeda33@mail.gmail.com>
 <20041010132339.GF3144@meier-geinitz.de>
Message-ID: <34eaeeaa04101011133f9b735c@mail.gmail.com>

Thanks, but I solved the problem. Sane-backend wasn't building shared
libraries. The libtool script really needs to look in /usr/local/lib
for stuff... (and /usr/lib64 on x86_64 machines!).

BTW, I had already tried scanimage -L as root with various debug
environment variables, and it never gave any extra output (of course,
since it didn't have any drivers to load).

It works nicely now. Thanks!

- David


On Sun, 10 Oct 2004 15:23:39 +0200, Henning Meier-Geinitz
<henning@meier-geinitz.de> wrote:
> Hi,
> 
> On Sat, Oct 09, 2004 at 09:07:07PM -0700, David Whysong wrote:
> > [dwhysong@sleepy sane-backends]$ scanimage -L
> >
> > No scanners were identified. If you were expecting something different,
> > check that the scanner is plugged in, turned on and detected by the
> > sane-find-scanner tool (if appropriate). Please read the documentation
> > which came with this software (README, FAQ, manpages).
> >
> >
> > I have rw permissions for the /proc/bus/usb/001/011 file.
> 
> Does scanimage -L find the scanner as root? If it doesn't, it's not a
> permissions nor hotplug issue.
> 
> Enable debugging like this:
> export SANE_DEBUG_SNAPSCAN=255
> and run scanimage -L again. Please show us the debug output.
> 
> Bye,
>   Henning
>


From andreas_klinger@debitel.net  Sun Oct 10 19:21:54 2004
From: andreas_klinger@debitel.net (Klinger)
Date: Sun, 10 Oct 2004 20:21:54 +0200
Subject: [sane-devel] unsubscribe moasta27
In-Reply-To: <20041010153205.GJ3144@meier-geinitz.de>
Message-ID: <000001c4aef6$077d5a60$0100a8c0@BLANCA>

I wanted to develop a backend for my hp scanjet 4500 scanner, but i've seen
it'll take about 4 weeks or more just to analyze the protocol. My wife will
kill me if i'm doing it ;)

Thanks for your mails

Andreas




From henning@meier-geinitz.de  Mon Oct 11 13:23:52 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 11 Oct 2004 14:23:52 +0200
Subject: [sane-devel] scanning on Epson Stylus Scan 2500 works
In-Reply-To: <87A94C23-1AC3-11D9-A0FB-000393CD04D6@hotmail.com>
References: <7409F833-19D2-11D9-81EF-000393CD04D6@hotmail.com> <20041010131639.GD3144@meier-geinitz.de> <87A94C23-1AC3-11D9-A0FB-000393CD04D6@hotmail.com>
Message-ID: <20041011122352.GC8269@meier-geinitz.de>

Hi,

On Sun, Oct 10, 2004 at 02:51:48PM +0100, Marc wrote:
> Le 10 oct. 04, à 14:16, Henning Meier-Geinitz a écrit :
> 
> >>A message from a happy user: even though the all-in-one Epson Stylus
> >>Scan 2500 is not listed on your list of supported scanners, it works
> >>for me (on MacOS X 10.3.5, flatpanel iMac).  Thanks!!!
> >
> >Thanks for your report. Can you give some more details, i.e. what's
> >teh output of:
> >
> >scanimage -L
> 
> device `epson:libusb:001:006-04b8-0106-ff-ff' is a Epson StylusScan2500 
> flatbed
> scanner
> 
> >and
> >scanimage --version
> 
> scanimage (sane-backends) 1.0.14-cvs; backend version 1.0.14

Ok, so it's supported by the epson backend.

Karl-Heinz, could you add that scanner to epson.desc?

Also, what about the "Epson ES-300GS"?
https://alioth.debian.org/tracker/index.php?func=detail&aid=300682&group_id=30186&atid=410366

By the way, I guess some of "your" bugs can be closed (#300598,
#300490?, #300179). Could you have a look at these bug reports?


Bye,
  Henning



From henning@meier-geinitz.de  Mon Oct 11 13:26:18 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 11 Oct 2004 14:26:18 +0200
Subject: [sane-devel] Epson 2480 not detected
In-Reply-To: <34eaeeaa04101011133f9b735c@mail.gmail.com>
References: <34eaeeaa0410092107abeda33@mail.gmail.com> <20041010132339.GF3144@meier-geinitz.de> <34eaeeaa04101011133f9b735c@mail.gmail.com>
Message-ID: <20041011122618.GD8269@meier-geinitz.de>

Hi,

On Sun, Oct 10, 2004 at 11:13:11AM -0700, David Whysong wrote:
> Thanks, but I solved the problem. Sane-backend wasn't building shared
> libraries. The libtool script really needs to look in /usr/local/lib
> for stuff... (and /usr/lib64 on x86_64 machines!).

I'll have a look for is a more current libtool version.

> BTW, I had already tried scanimage -L as root with various debug
> environment variables, and it never gave any extra output (of course,
> since it didn't have any drivers to load).

SANE_DEBUG_DLL=255 may help in such a case.

Bye,
  Henning


From sirius-c@iname.com  Mon Oct 11 19:02:57 2004
From: sirius-c@iname.com (Jason Anderson)
Date: Mon, 11 Oct 2004 13:02:57 -0500
Subject: [sane-devel] Trying to work out the Genesys backend
Message-ID: <20041011180257.26616101D8@ws1-3.us4.outblaze.com>

Hello everyone.

I'm trying to figure out how to make the Genesys backend work, but I don'=
t even know where to start.  Is it in the conf file?  Or is it in the sou=
rce files?  If anyone has been working on it for a while could please con=
tact me, that would be greatly appreciated.

----------
Jason A.
ICQ# 148434286
--=20
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm



From henning@meier-geinitz.de  Mon Oct 11 19:43:04 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 11 Oct 2004 20:43:04 +0200
Subject: [sane-devel] Trying to work out the Genesys backend
In-Reply-To: <20041011180257.26616101D8@ws1-3.us4.outblaze.com>
References: <20041011180257.26616101D8@ws1-3.us4.outblaze.com>
Message-ID: <20041011184304.GE17236@meier-geinitz.de>

Hi,

On Mon, Oct 11, 2004 at 01:02:57PM -0500, Jason Anderson wrote:
> I'm trying to figure out how to make the Genesys backend work, but I
> don't even know where to start.  Is it in the conf file?  Or is it in
> the source files?  If anyone has been working on it for a while could
> please contact me, that would be greatly appreciated.

Which scanner do you have and what do you want to achieve?

The README files explains how to install/use it. If you want to add a
scanner, you must change both the source code and the config file.

Bye,
  Henning


From henning@meier-geinitz.de  Mon Oct 11 13:27:42 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 11 Oct 2004 14:27:42 +0200
Subject: [sane-devel] unsubscribe moasta27
In-Reply-To: <000001c4aef6$077d5a60$0100a8c0@BLANCA>
References: <20041010153205.GJ3144@meier-geinitz.de> <000001c4aef6$077d5a60$0100a8c0@BLANCA>
Message-ID: <20041011122742.GE8269@meier-geinitz.de>

Hi,

On Sun, Oct 10, 2004 at 08:21:54PM +0200, Klinger wrote:
> I wanted to develop a backend for my hp scanjet 4500 scanner, but i've seen
> it'll take about 4 weeks or more just to analyze the protocol. My wife will
> kill me if i'm doing it ;)

Please read the footer added to each message sent to sane-devel to
find out how to unsubscribe:

> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org


Bye,
  Henning


From georg.halfas@gmx.net  Mon Oct 11 18:51:04 2004
From: georg.halfas@gmx.net (Georg Halfas)
Date: Mon, 11 Oct 2004 19:51:04 +0200
Subject: [sane-devel] Unsubscribe
Message-ID: <200410111951.04689.georg.halfas@gmx.net>

sorry I forgot my password so I cannot unsubscribe
=2D-=20
Mit freundlichen Gr=FC=DFen

Georg Halfas
___________________________________________________________________________=
__
Dipl.-Ing. Georg Halfas
Landschaftsarchitekt
Preystra=DFe 11
22303 Hamburg
info.hamburg@architektur-und-landschaft.de


From henning@meier-geinitz.de  Mon Oct 11 19:51:15 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 11 Oct 2004 20:51:15 +0200
Subject: [sane-devel] Unsubscribe
In-Reply-To: <200410111951.04689.georg.halfas@gmx.net>
References: <200410111951.04689.georg.halfas@gmx.net>
Message-ID: <20041011185115.GF17236@meier-geinitz.de>

Hi,

On Mon, Oct 11, 2004 at 07:51:04PM +0200, Georg Halfas wrote:
> sorry I forgot my password so I cannot unsubscribe

Well, I repeat: Read the footer! :-)
There is a link at the bottom of the web site page linked to in the
footer where you can enter your mail address address and get a
password reminder mail.

> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org

If you still can't unsubscribe please tell me (privately) the email
address you used to subscribe and I'll try to find and delete your
address from the list.

bye,
  Henning


From rene@exactcode.de  Mon Oct 11 21:54:06 2004
From: rene@exactcode.de (=?ISO-8859-1?Q?Ren=E9_Rebe?=)
Date: Mon, 11 Oct 2004 22:54:06 +0200
Subject: [sane-devel] Scanner Button
In-Reply-To: <Pine.LNX.4.61.0410091126330.30301@limos.pfeiffer.edu>
References: <1097329832013643@lycos-europe.com> <Pine.LNX.4.61.0410091126330.30301@limos.pfeiffer.edu>
Message-ID: <416AF2EE.3000407@exactcode.de>

Hi,

m. allan noah wrote:

> there has been much discussion in the past, but everyone seems too busy 
> to actually get anything in writing. search the archives of the sane 
> mailing list, there where several threads about it in the earlier part 
> of this year, IIRC.
> 
> basically:
> 
> front end polling a backend via asking for updates on certain OPTs seems 
> to be the consensus. details that need work: how to identify which opts, 
> recommendations for how frontends could display that data, and does the 
> backend need to be able to specify the polling interval. how the buttons 
> are affected by the network scanner locking code also seems like a good 
> topic for discussion.
> 
> allan
> 
> On Sat, 9 Oct 2004, Ullrich Sigwanz wrote:
> 
>> Hi all,
>>
>> Are there thoughts /ideas/implementations for including the button
>> handling in SANE (resp. SANE2) in a standardized way?
>>
>> (e.g. a polling daemon, callbacks to start applications etc.)

Proof of concept implemented in the Avision backend (might not yet be in 
CVS - I merge in the next days). Code is here:

   http://svn.exactcode.de/sane-avision/trunk/

An example "how to poll the buttons":

   http://svn.exactcode.de/sane-avision/trunk/sanebuttonsd/

Have fun,

PS: I might mail with the wrong From: address for the list - sorry.

-- 
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
             +49 (0)30  255 897 45


From joehenley@kc.rr.com  Mon Oct 11 23:23:08 2004
From: joehenley@kc.rr.com (Joe Henley)
Date: Mon, 11 Oct 2004 17:23:08 -0500
Subject: [sane-devel] umax_pp slow
In-Reply-To: <41699E2A.5010109@kc.rr.com>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com> <20041001042733.GA2166@wanadoo.fr> <415D7E43.8080907@kc.rr.com> <20041004044644.GA6220@wanadoo.fr> <41699E2A.5010109@kc.rr.com>
Message-ID: <416B07CC.2040302@kc.rr.com>

Stef,

I made some changes.  In looking on Google I see that RedHat 9 doesn't 
activate ECP as a default.  I recompiled the parport module section and 
now I'm getting ECP!  Cool.  Now the data is:

run export ....
run scanimage -L 2>log
-------------------------------------------------------------
[sanei_debug] Setting debug level of umax_pp_low to 1.
[umax_pp_low] SANE_INB level 3
[umax_pp_low] sanei_umax_pp_InitPort(0x378,)
[umax_pp_low] sanei_ioperm(0x378, 8, 1) OK ...
[umax_pp_low] status 128 doesn't match! umax_pp_low.c:4927
[umax_pp_low] No scanner detected by 'ringScanner(2,0)'...
[umax_pp_low] status 128 doesn't match! umax_pp_low.c:4927
[umax_pp_low] No scanner detected by 'ringScanner(5,0)'...
[umax_pp_low] status 128 doesn't match! umax_pp_low.c:4927
[umax_pp_low] No scanner detected by 'ringScanner(5,10000)'...
[umax_pp_low] status 128 doesn't match! umax_pp_low.c:4927
[umax_pp_low] No scanner detected by 'ringScanner(5,10000)'...
[umax_pp_low] No 1220P/2000P scanner detected by 'ringScanner()'...
[umax_pp_low] Trying 610p (umax_pp_low.c:7346)
[umax_pp_low] connect610p control=0F, expected 0x0E (umax_pp_low.c:3860)
[umax_pp_low] connect610p control=0F, expected 0x0C (umax_pp_low.c:3870)
[umax_pp_low] connect610p control=0F, expected 0x0E (umax_pp_low.c:3880)
[umax_pp_low] connect610p control=0F, expected 0x0C (umax_pp_low.c:3890)
[umax_pp_low] connect610p control=07, expected 0x04 (umax_pp_low.c:3899)
[umax_pp_low] sync610p failed (got 0x80 expected 0x38)! (umax_pp_low.c:3683)
[umax_pp_low] sync610p failed! Scanner not present or powered off ... 
(umax_pp_low.c:6232)
[umax_pp_low] initTransport610p() failed (umax_pp_low.c:6536)


run ./ppdiag
----------------------------------------------------------------
[root@Eddie tools]# ./ppdiag
S01: parport built as module
S02: parport0:
S02:    modes:PCSPP,TRISTATE,COMPAT,ECP
S02:    ADDR :0x378
S02:    IRQ  :7
S02:    DMA  :no DMA used
S03: parport parameters are: options parport_pc io=0x378 io_hi=0x778 
irq=7 dma=none
S10: ppdev built as module
S12: /dev/parport0 exists ...
S12: /dev/parport0 is readable ...
S12: /dev/parport0 is writable ...
successfull end ....

The contents of umax_pp.conf are:
-------------------------------------------
option buffer 8388608
port 0x378
option astra 2000

The /etc/modules.conf includes:
-------------------------------------------
alias parport_lowlevel parport_pc
options parport_pc io=0x378 io_hi=0x778 irq=7 dma=none

When I run lsmod, I get the following relevant items:
------------------------------------------------------
ppdev                   6796   0  (unused)
parport_pc             31848   1  (autoclean)
lp                      8996   0  (autoclean)
parport                37056   1  (autoclean) [ppdev parport_pc lp]

The BIOS is set to ECP, IRQ=7, Addr=0x378, DMA=3

I reset (pc off, scanner off, scanner on, pc on) the scanner before 
these runs of the tests.

The scanner is on, despite the messages when I ran these.

OK, so now I've got ECP; what's next?   ... thanks for all your help!

Joe Henley

Joe Henley wrote:
> Hi Stef,
> 
> Sorry for the delay in responding.  I was out of town on business.
> 
> svoltz@wanadoo.fr wrote:
> 
>>     Hello,
>>
>>     I think you should try again ECP. I think the message you get is
>> harmless. You can comment it out in the sourcecode before doing tests
>> again. 
> 
> 
> I'm not sure I understand which message you're referring to.  With the 
> BIOS set for ECP, it (scanimage -L 2>log) just runs on without stopping. 
>  I have to use ^C to stop it.  Is that the message you refer to?
> 
> The BIOS says it's ECP, but Linux doesn't report it that way in the 
> /var/log/messages or kernel files.  Very odd!  Even more odd is that I 
> run Win4Lin on this machine, using Win98.  I can run Linux running 
> Win4Lin, running Win98, running the VistaScan copier program, and it 
> runs just fine.  The speed is very good.  So somehow it's figuring out 
> to run quickly thru the parallel port.  If I shut down 
> VistaScan/Win98/Win4Lin and without rebooting, load up sane and try it, 
> it's very slow.  Arrrgh!
> 
> Any suggestions?
> 
>>     But until you see ECP mode detected by ythe linux kernel, I'm
>> afraid you'll have troubles.
>>
>> Regards,
>>     Stef
>>
> Thanks!
> 
> Joe Henley
> 


From afb@paradise.net.nz  Tue Oct 12 04:20:31 2004
From: afb@paradise.net.nz (Adam Bogacki)
Date: Tue, 12 Oct 2004 16:20:31 +1300
Subject: [sane-devel] xsane-win32
In-Reply-To: <1097513065.2140.1.camel@Babylon7>
References: <416A554D.6000509@paradise.net.nz>
 <1097513065.2140.1.camel@Babylon7>
Message-ID: <416B4D7F.4000901@paradise.net.nz>

I should have mentioned that I have just set up a network - an old P I 
running Win 98 configured
with the XP drive on my PIII machine to give an 80 yr old lady some 
email and browser access.

I intend to also try setting up a Linux network using Tulip when I get 
around to it.

This could be used to access Xsane on the PIII server.
I presume I would use 'net' and appropriate DNS settings.

 Any tips on config ?

Adam.

Oliver Rauch wrote:

>Hello Adam,
>
>it looks like you want to use xsane-win32 to work with a scanner that
>is locally connected to the windows machine. This does not work yet.
>
>Oliver
>
>Am Mon, 2004-10-11 um 11.41 schrieb Adam Felix Bogacki:
>  
>
>>Sorry Oliver. I removed and re-installed  Epson Smart Panel for Scanner 
>>and Twain and it
>>recognised the scanner and was usable. However, xsane springs into action,
>>shows me the 'Xsane End User Licence Agreement', and after I click the 
>>'I accept' panel
>>searches around and quickly gives me  'no devices available'.
>>
>>It was doing this when Smart Panel and Twain were not working so I don't 
>>think it may be
>>a case of the scanner being assigned to one program and denied to 
>>another. I could be wrong.
>>
>>I have gone through the 'help' list of  possible reasons for this and 
>>the only thing which looks
>>plausible is  'backend is not configured correct'.
>>
>>In 'C:\sane\etc\sane.d\net.conf' I used 'localhost' and '192.168.0.1' - 
>>the localhost TCP/IP address ..
>>
>>In 'C:\sane\etc\sane.d\dll.conf' the only lines enabled are 'epson' and 
>>'gphoto2' (in case of future digital camera use) , and in
>>
>>'C:\sane\etc\sane.d\epson.conf' the only uncommented lines are
>>
>>'usb 0x04b8 0x010c' and 'usb /dev/usb/scanner0'
>>
>>Are there any obvious errors here ? Confusion of backward and forward slashes ?
>>
>>One thing I came across in reading WinXP help files was that Twain does not work
>>after the scanner is disconnected (as in re-plugging with Linux hotplug). It then has to be
>>reinstalled via XP's 'New Hardware Install' wizard. 
>>
>>Could this be contributing here ?
>>
>>It's frustrating having a fine program like xsane not working in XP. 
>>
>>Adam Bogacki,
>>afb@paradise.net.nz
>>
>>
>>    
>>
>
>
>
>  
>



From gerhard@gjaeger.de  Tue Oct 12 09:52:25 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Tue, 12 Oct 2004 10:52:25 +0200
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <00f201c4abaa$23c46500$6601a8c0@khp5000elaptop>
References: <00f201c4abaa$23c46500$6601a8c0@khp5000elaptop>
Message-ID: <200410121052.25872.gerhard@gjaeger.de>

Hi,

On Wednesday 06 October 2004 15:41, Kenneth H. Peters wrote:
> Gergard, thanks for the assist ... :) ...
>
> As you requested, below is output from two scan sessions:
>
> 	1.) scanimage -x 10 -y 10 --format=tiff --resolution 50
> 	2.) scanimage -x 10 -y 10 --format=tiff --resolution 300
>
> I am curious to know what specifically you are look for? An engineer here
> believes this is a Big-Endian issue, but I have not been able to nail it
> down.

sorry for ignoring your mail so far - I'm short of time (anyway who is not ;)
First I thought, that there's really something wrong with BE/LE on the
backend, but when comparing the register settings on my box and on your box
everything looks fine. The picture data are 8bit wide and therefore I guess
there's no problem.
Did you do all scans using TIFF? Can you please check PNM output too?

Ciao,
  Gerhard



From svoltz@wanadoo.fr  Tue Oct 12 20:07:12 2004
From: svoltz@wanadoo.fr (svoltz@wanadoo.fr)
Date: Tue, 12 Oct 2004 21:07:12 +0200
Subject: [sane-devel] umax_pp slow
In-Reply-To: <416B07CC.2040302@kc.rr.com>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com> <20041001042733.GA2166@wanadoo.fr> <415D7E43.8080907@kc.rr.com> <20041004044644.GA6220@wanadoo.fr> <41699E2A.5010109@kc.rr.com> <416B07CC.2040302@kc.rr.com>
Message-ID: <20041012190712.GA2278@wanadoo.fr>

	Hello, 

	I checked that ECP was still working on my laptop. I'll try
on my other linux box to see if I get the same. Can you raise trace 
level to 255 and send me the output of the test program ?

Regards,
	Stef


From mogensjaeger@get2net.dk  Tue Oct 12 22:32:55 2004
From: mogensjaeger@get2net.dk (Mogens Jaeger)
Date: Tue, 12 Oct 2004 23:32:55 +0200
Subject: [sane-devel] Translation
In-Reply-To: <20041010153205.GJ3144@meier-geinitz.de>
References: <41694E3E.7080109@get2net.dk> <20041010153205.GJ3144@meier-geinitz.de>
Message-ID: <416C4D87.4050807@get2net.dk>

Hello

I have been working on the Danish translation of Sane-backends-1.0.15 -=20
from cvs.

I don't understand the meaning of:

Red-gain value of the AFE

This AFE - is it a professional term that's not needed to translate, or??=
??

sincerely

--=20
mvh Mogens J=E6ger



From bertrik@zonnet.nl  Tue Oct 12 23:57:35 2004
From: bertrik@zonnet.nl (Bertrik Sikken)
Date: Wed, 13 Oct 2004 00:57:35 +0200
Subject: [sane-devel] Translation
In-Reply-To: <416C4D87.4050807@get2net.dk>
References: <41694E3E.7080109@get2net.dk> <20041010153205.GJ3144@meier-geinitz.de> <416C4D87.4050807@get2net.dk>
Message-ID: <416C615F.8010309@zonnet.nl>

Mogens Jaeger wrote:
> Hello
> 
> I have been working on the Danish translation of Sane-backends-1.0.15 - 
> from cvs.
> 
> I don't understand the meaning of:
> 
> Red-gain value of the AFE
> 
> This AFE - is it a professional term that's not needed to translate, or????

AFE means analog front-end.

This is an electronic circuit that processes the analog signals from
the CCD. The AFE chip that I have some knowledge about, contains an
amplifier for each color channel that can be configured in coarse steps.
It is used to make the dynamic range of the CCD signal roughly equal
(but slightly lower) than the dynamic range of the A/D converter
(hope this still makes sense)
The gain of the amplifier for the red color channel is probably what is
meant here.

I don't know how to translate it. I think it's a very technical term
that end users probably should not even need to know about.

Regards,
Bertrik



From kpeters@lhsolutions.com  Wed Oct 13 00:46:32 2004
From: kpeters@lhsolutions.com (Ken Peters (NEW))
Date: Tue, 12 Oct 2004 19:46:32 -0400
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <200410121052.25872.gerhard@gjaeger.de>
Message-ID: <004001c4b0b5$b48b3e50$6400a8c0@kpdesktop>

Gerhard:

I figure you are pretty busy! ... I appreciate any support you provide.=20

I get the same results for both TIFF and PNG.=20

I am currently going through the process of looking at the raw data from =
the
scanner. I'll keep plug-in away ...=20

Thanks,
K.P.

-----Original Message-----
From: sane-devel-admin@lists.alioth.debian.org
[mailto:sane-devel-admin@lists.alioth.debian.org] On Behalf Of Gerhard
Jaeger
Sent: Tuesday, October 12, 2004 3:52 AM
To: Kenneth H. Peters
Cc: sane-devel@lists.alioth.debian.org
Subject: Re: [sane-devel] Interesting image problem when scanning color =
...

Hi,

On Wednesday 06 October 2004 15:41, Kenneth H. Peters wrote:
> Gergard, thanks for the assist ... :) ...
>
> As you requested, below is output from two scan sessions:
>
> 	1.) scanimage -x 10 -y 10 --format=3Dtiff --resolution 50
> 	2.) scanimage -x 10 -y 10 --format=3Dtiff --resolution 300
>
> I am curious to know what specifically you are look for? An engineer =
here
> believes this is a Big-Endian issue, but I have not been able to nail =
it
> down.

sorry for ignoring your mail so far - I'm short of time (anyway who is =
not
;)
First I thought, that there's really something wrong with BE/LE on the
backend, but when comparing the register settings on my box and on your =
box
everything looks fine. The picture data are 8bit wide and therefore I =
guess
there's no problem.
Did you do all scans using TIFF? Can you please check PNM output too?

Ciao,
  Gerhard


--=20
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@lists.alioth.debian.org



From sean035@yahoo.com.tw  Wed Oct 13 02:56:18 2004
From: sean035@yahoo.com.tw (sean035@yahoo.com.tw)
Date: Wed, 13 Oct 2004 09:56:18 +0800 (CST)
Subject: [sane-devel] scanimage can't detect my scanner.
Message-ID: <20041013015618.51521.qmail@web17808.mail.tpe.yahoo.com>

Hi everyone,
I have a question about scanimage.
How do I edit my scanner backend source code to make
the scanimage can detect my new scanner device?
Because my scanner can work on my new backend, but
scanimage can't detect it.
Anybody can tell me why?
Thanks a lot.

Walker,

-----------------------------------------------------------------
Yahoo!İ_ĵŻıq¤lĞH½c
100MB §KĥOĞH½cĦAıq¤lĞH½c·sĴö¤¸ħq³oĥ}İlĦI
http://mail.yahoo.com.tw/


From gerhard@gjaeger.de  Wed Oct 13 07:56:05 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Wed, 13 Oct 2004 08:56:05 +0200
Subject: [sane-devel] scanimage can't detect my scanner.
In-Reply-To: <20041013015618.51521.qmail@web17808.mail.tpe.yahoo.com>
References: <20041013015618.51521.qmail@web17808.mail.tpe.yahoo.com>
Message-ID: <200410130856.05124.gerhard@gjaeger.de>

On Wednesday 13 October 2004 03:56, sean035@yahoo.com.tw wrote:
> Hi everyone,
> I have a question about scanimage.
> How do I edit my scanner backend source code to make
> the scanimage can detect my new scanner device?
> Because my scanner can work on my new backend, but
> scanimage can't detect it.
> Anybody can tell me why?

Tell us more about your backend. Is it integrated in SANE? Is it enabled
in /<your sysconfig path>/sane.d/dll.conf?
Have you red sane-backends/doc/backend-writing.txt?

Again my question, what scanner-backend are your working on?

Regards,
  Gerhard



From eppesuig@users.sourceforge.net  Tue Oct 12 23:02:21 2004
From: eppesuig@users.sourceforge.net (Giuseppe Sacco)
Date: Wed, 13 Oct 2004 00:02:21 +0200
Subject: [sane-devel] Translation
In-Reply-To: <416C4D87.4050807@get2net.dk>
References: <41694E3E.7080109@get2net.dk>
 <20041010153205.GJ3144@meier-geinitz.de>  <416C4D87.4050807@get2net.dk>
Message-ID: <1097618540.9579.8.camel@casa>

Il mar, 2004-10-12 alle 23:32, Mogens Jaeger ha scritto:
> Hello
> 
> I have been working on the Danish translation of Sane-backends-1.0.15 - 
> from cvs.
> 
> I don't understand the meaning of:
> 
> Red-gain value of the AFE
> 
> This AFE - is it a professional term that's not needed to translate, or????

I hope that it is the "Analog FrontEnd" mentioned two string earlier,
otherwise I made a wrong translation :-(

Bye,
Giuseppe



From mogensjaeger@get2net.dk  Wed Oct 13 15:33:59 2004
From: mogensjaeger@get2net.dk (Mogens Jaeger)
Date: Wed, 13 Oct 2004 16:33:59 +0200
Subject: [sane-devel] Error at translation
Message-ID: <416D3CD7.8020900@get2net.dk>

Hello

When I in emacs runs the 'Validate' command, on the sane-backends da.po=20
file, I get the folloving error:

cd ~/Oversaettelse/Sane-backends-1.0.15/
msgfmt --statistics -c -v -o /dev/null
/home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po
/home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po:1268:
'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the
directive number 1, the character 'b' is not a valid conversion specifier.

The message looks this way:

#: .tmp/microtek2.h:697
#, c-format
msgid "Balance factor for red. A value of 100% means no correction."
msgstr "Balancefaktor for roed. Vaerdien 100% betyder ingen korrektion."

I have asked in my Language-Team, and one said that there should not be=20
a '#, c-format' up front???????

I had 3 messages with errors like this, lines in da.po file : 1268=20
(above), 1277 and 1268, all with the same errormessage.

--=20
mvh Mogens J=E6ger



From mogensjaeger@get2net.dk  Wed Oct 13 15:36:16 2004
From: mogensjaeger@get2net.dk (Mogens Jaeger)
Date: Wed, 13 Oct 2004 16:36:16 +0200
Subject: [sane-devel] Translation
In-Reply-To: <1097618540.9579.8.camel@casa>
References: <41694E3E.7080109@get2net.dk>	 <20041010153205.GJ3144@meier-geinitz.de>  <416C4D87.4050807@get2net.dk> <1097618540.9579.8.camel@casa>
Message-ID: <416D3D60.7020807@get2net.dk>

Giuseppe Sacco skrev:

>Il mar, 2004-10-12 alle 23:32, Mogens Jaeger ha scritto:
> =20
>
>>Hello
>>
>>I have been working on the Danish translation of Sane-backends-1.0.15 -=
=20
>>from cvs.
>>
>>I don't understand the meaning of:
>>
>>Red-gain value of the AFE
>>
>>This AFE - is it a professional term that's not needed to translate, or=
????
>>   =20
>>
>
>I hope that it is the "Analog FrontEnd" mentioned two string earlier,
>otherwise I made a wrong translation :-(
>
>Bye,
>Giuseppe
>
>
> =20
>
You are right - sorry for missing the connection betwen Analog Frontend=20
and AFE :-!

--=20
mvh Mogens J=E6ger



From fzago@austin.rr.com  Wed Oct 13 16:18:51 2004
From: fzago@austin.rr.com (Frank Zago)
Date: Wed, 13 Oct 2004 10:18:51 -0500
Subject: [sane-devel] Error at translation
In-Reply-To: <416D3CD7.8020900@get2net.dk>
References: <416D3CD7.8020900@get2net.dk>
Message-ID: <416D475B.9030303@austin.rr.com>

Mogens Jaeger wrote:
> Hello
> 
> When I in emacs runs the 'Validate' command, on the sane-backends da.po 
> file, I get the folloving error:
> 
> cd ~/Oversaettelse/Sane-backends-1.0.15/
> msgfmt --statistics -c -v -o /dev/null
> /home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po
> /home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po:1268:
> 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the
> directive number 1, the character 'b' is not a valid conversion specifier.
> 
> The message looks this way:
> 
> #: .tmp/microtek2.h:697
> #, c-format
> msgid "Balance factor for red. A value of 100% means no correction."
> msgstr "Balancefaktor for roed. Vaerdien 100% betyder ingen korrektion."
> 
> I have asked in my Language-Team, and one said that there should not be 
> a '#, c-format' up front???????
> 
> I had 3 messages with errors like this, lines in da.po file : 1268 
> (above), 1277 and 1268, all with the same errormessage.
> 

It's a bug in the original string "...100% means". The "%" should be "%%". The 
source code must be updated.

Frank.


From henning@meier-geinitz.de  Wed Oct 13 16:19:27 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 13 Oct 2004 17:19:27 +0200
Subject: [sane-devel] Error at translation
In-Reply-To: <416D3CD7.8020900@get2net.dk>
References: <416D3CD7.8020900@get2net.dk>
Message-ID: <20041013151927.GF8948@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 04:33:59PM +0200, Mogens Jaeger wrote:
> When I in emacs runs the 'Validate' command, on the sane-backends da.po 
> file, I get the folloving error:
> 
> cd ~/Oversaettelse/Sane-backends-1.0.15/
> msgfmt --statistics -c -v -o /dev/null
> /home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po
> /home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po:1268:
> 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the
> directive number 1, the character 'b' is not a valid conversion specifier.

I have also gotten similar messages while updating .de.po.

As far as I can see xgettext tries to be intelligent by marking
everything that containts a % as c-format. It's not intelligent
enough to really find out which string is intended as a format string
and which is not.

We could use the flag option for xgettext:

$(XGETTEXT) -dsane-backends -kSANE_I18N --flag=SANE_I18N:1:no-c-format $(TMP_FILE_DIR)/*.*

That marks all strings as "no-c-format". However, I don't know how
compatible that is.

Other ideas?

Bye,
  Henning


From stan@saticed.me.uk  Wed Oct 13 16:23:29 2004
From: stan@saticed.me.uk (Tristan Hill)
Date: Wed, 13 Oct 2004 16:23:29 +0100
Subject: [sane-devel] scanadf: waiting for child processes to finish
Message-ID: <20041013152329.GA28252@marge.cehill.co.uk>

--VS++wcV0S1rZb1Fb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline


I use the --scan-script option with scanadf, however, if I want to do
some work on all the files processed by the script is it difficult
because scanadf may finish before one or more of the script processes
do.  For example, I want to use it to combine the processed images into
a single file.  As scanadf knows what processes it has forked I thought
it easiest to use wait(), implemented as per attached patch.  However, I
am open to other suggestions.

Thanks

--VS++wcV0S1rZb1Fb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="scanadf-script-wait.patch"

--- scanadf.c.orig	2004-10-11 08:52:34.000000000 +0100
+++ scanadf.c	2004-10-13 15:47:42.000000000 +0100
@@ -39,6 +39,7 @@
 #include <string.h>
 #include <sys/types.h>
 #include <sys/stat.h>
+#include <sys/wait.h>
 
 #include "sane/sane.h"
 #include "sane/sanei.h"
@@ -102,6 +103,7 @@
   { "start-count", required_argument, 0, 's' },
   { "end-count", required_argument, 0, 'e' },
   { "scan-script", required_argument, 0, 'S' },
+  { "script-wait", no_argument, 0, 128 },
   { "raw", no_argument, 0, 'r' },
   {0, }
 };
@@ -137,6 +139,7 @@
    [ -o | --output-file <name> ]     name of file to write image data\n\
                                      (%%d replacement in output file name).\n\
    [ -S | --scan-script <name> ]     name of script to run after every scan.\n\
+   [ --script-wait ]                 wait for scripts to finish before exit\n\
    [ -s | --start-count <num> ]      page count of first scanned image.\n\
    [ -e | --end-count <num> ]        last page number to scan.\n\
    [ -r | --raw ]                    write raw image data to file.\n";
@@ -1281,6 +1284,7 @@
   char *full_optstring;
   SANE_Bool raw = SANE_FALSE;
   const char *scanScript = NULL;		/* script to run at end of scan */
+  int scriptWait = 0;
   const char *outputFile = "image-%04d";	/* file name(format) to write output to */
   int startNum = 1, endNum = -1;		/* start/end numbers of pages to scan */
   int no_overwrite = 0;
@@ -1335,6 +1339,7 @@
 
 	case 'o': outputFile = optarg; break;
 	case 'S': scanScript = optarg; break;
+	case 128: scriptWait = 1; break;
 	case 's': startNum = atoi(optarg); break;
 	case 'e': endNum = atoi(optarg); break;
 	case 'r': raw = SANE_TRUE; break;
@@ -1348,6 +1353,9 @@
 	}
     }
 
+  if (scriptWait && !scanScript)
+    scriptWait = 0;
+
   if (help)
     printf (usage, prog_name);
 
@@ -1574,6 +1582,9 @@
   sane_cancel (device);
   sane_close (device);
 
+  if (scriptWait)
+    while (wait(NULL) != -1);
+
   return (status == SANE_STATUS_GOOD) ? 0 : 1;
 }
 

--VS++wcV0S1rZb1Fb--


From henning@meier-geinitz.de  Wed Oct 13 16:29:36 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 13 Oct 2004 17:29:36 +0200
Subject: [sane-devel] Error at translation
In-Reply-To: <416D475B.9030303@austin.rr.com>
References: <416D3CD7.8020900@get2net.dk> <416D475B.9030303@austin.rr.com>
Message-ID: <20041013152936.GG8948@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 10:18:51AM -0500, Frank Zago wrote:
> It's a bug in the original string "...100% means". The "%" should be "%%". 
> The source code must be updated.

Are you sure? SANE titles and descriptions are not C format strings.
If you use "%%" you'll get "%%" in the output.

Bye,
  Henning


From karsten.pietsch@gmx.de  Wed Oct 13 20:52:25 2004
From: karsten.pietsch@gmx.de (Karsten Pietsch)
Date: Wed, 13 Oct 2004 21:52:25 +0200
Subject: [sane-devel] [Fwd: [Bug 3531] problems with my usb-scanner canon630u (sane)]
Message-ID: <416D8779.8090705@gmx.de>

This is a multi-part message in MIME format.
--------------070506080203040505010201
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

hello!

in the attachment is my bug-report for the kernel-peoples....

i got a answer with  the tip to send thes bug to the x-sane-people....

hier is my problem:-)



--------------070506080203040505010201
Content-Type: message/rfc822;
 name="[Bug 3531] problems with my usb-scanner canon630u (sane)"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="[Bug 3531] problems with my usb-scanner canon630u (sane)"

Return-Path: <www@osdl.org>
X-Flags: 0000
Delivered-To: GMX delivery to keytrix@gmx.de
Received: (qmail 21290 invoked by uid 65534); 13 Oct 2004 17:06:04 -0000
Received: from fire.osdl.org (EHLO fire-1.osdl.org) (65.172.181.4)
  by mx0.gmx.net (mx023) with SMTP; 13 Oct 2004 19:06:04 +0200
Received: from fire-1.osdl.org (localhost [127.0.0.1])
	by fire-1.osdl.org (8.12.8/8.12.8) with ESMTP id i9DH5qWL002444
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <keytrix@gmx.de>; Wed, 13 Oct 2004 10:05:52 -0700
Received: (from www@localhost)
	by fire-1.osdl.org (8.12.8/8.12.5/Submit) id i9DH5pa4002443;
	Wed, 13 Oct 2004 10:05:51 -0700
Date: Wed, 13 Oct 2004 10:05:51 -0700
Message-Id: <200410131705.i9DH5pa4002443@fire-1.osdl.org>
From: bugme-daemon@osdl.org
To: keytrix@gmx.de
Subject: [Bug 3531] problems with my usb-scanner canon630u (sane)
X-Bugzilla-Reason: Reporter
X-Bugzilla-Category: Drivers
X-Bugzilla-Component: USB
Received-SPF: pass (localhost is always allowed.)
X-Spam-Status: No, hits=1.088 required=5 tests=NO_REAL_NAME
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 2.63-osdl_revision__1.34__
X-MIMEDefang-Filter: osdl$Revision: 1.93 $
X-Scanned-By: MIMEDefang 2.36
X-GMX-Antivirus: 0 (no virus found)
X-GMX-Antispam: 0 (Mail was not recognized as spam)

http://bugme.osdl.org/show_bug.cgi?id=3531

greg@kroah.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |REJECTED
         Resolution|                            |INVALID



------- Additional Comments From greg@kroah.com  2004-10-13 10:05 -------
Hm, there is no usb scanner driver in the kernel anymore, so this really
isn't a kernel issue, right?

I suggest you ask the xsane people about this instead, as their userspace programs
should work just fine.

------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.


--------------070506080203040505010201--


From henning@meier-geinitz.de  Wed Oct 13 19:16:42 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 13 Oct 2004 20:16:42 +0200
Subject: [sane-devel] [Fwd: [Bug 3531] problems with my usb-scanner canon630u (sane)]
In-Reply-To: <416D8779.8090705@gmx.de>
References: <416D8779.8090705@gmx.de>
Message-ID: <20041013181642.GH8948@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 09:52:25PM +0200, Karsten Pietsch wrote:
> hello!
> 
> in the attachment is my bug-report for the kernel-peoples....
> 
> i got a answer with  the tip to send thes bug to the x-sane-people....
> 
> hier is my problem:-)

If the error message is really "device busy" it just means that.
Another program is blocking your scanner. Otherwise it's proabably a
kernel or hardware issue.

Could you please show us a debug log? E.g.:

SANE_DEBUG_CANON630U=255 scanimage -y 10 >/dev/null 2>dbg.log

Bye,
  Henning


From Franz Bakan" <fbakan@gmx.net  Wed Oct 13 22:25:08 2004
From: Franz Bakan" <fbakan@gmx.net (Franz Bakan)
Date: Wed, 13 Oct 2004 23:25:08 +0200 (CEST)
Subject: [sane-devel] compiling with gcc 3.3.4 on OS/2

Hi,

I'm trying to build with gcc 3.3.4 and besides other small problems

compiling fails with:

sanei_scsi.c: In function `sanei_scsi_find_devices':
sanei_scsi.c:3857: error: assignment of read-only member `str'
sanei_scsi.c:3858: error: assignment of read-only member `str'
sanei_scsi.c:3859: error: assignment of read-only member `str'
sanei_scsi.c:3860: error: assignment of read-only member `str'
sanei_scsi.c:3861: error: assignment of read-only member `i'
sanei_scsi.c:3862: error: assignment of read-only member `i'
sanei_scsi.c:3863: error: assignment of read-only member `i'
sanei_scsi.c:3864: error: assignment of read-only member `i'

I didn't have seen this problem with earlier versions of gcc.

Is there a solution or compiler-flag to solve the problem?

BTW Sane-CVS-code still compiles fine with earlier versions of gcc.

Franz




From mreuther@umich.edu  Thu Oct 14 03:48:53 2004
From: mreuther@umich.edu (Matt Reuther)
Date: Wed, 13 Oct 2004 22:48:53 -0400
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
Message-ID: <200410132249.08934.mreuther@umich.edu>

--Boundary-00=_VkebBRx89EMFBEs
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi. I picked up an Epson Perfection 4180 scanner. I have it plugged into a=
=20
USB 2.0 card. I have Slackware 10 on my computer, with linux-2.4.27=20
installed on top of it. I am using xsane-0.93 compiled against GTK-2.4.1=20
and with GIMP 2.0 support.

The scanner shows up in lsusb, and I set permissions and added the=20
vendor/product ID to /etc/hotplug/usb.usermap, so it works with libusb. It=
=20
shows up with scanimage -L and if I start xsane, I can pick it from the=20
devices list. However, xsane crashes once I pick the scanner.

I set SANE_DEBUG_DLL=3D3 and captured the output. It's attached.

Any ideas?
=2D --=20
Matt Reuther
mreuther@umich.edu
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD4DBQFBbekjFse4xrb7oagRAhAgAKCDy1eifHc2JzEmActdNn45JjIssACXcYhs
+0+OnCxEvvt2gCz4HOex3Q=3D=3D
=3DECYu
=2D----END PGP SIGNATURE-----

--Boundary-00=_VkebBRx89EMFBEs
Content-Type: application/x-bzip2;
  name="sanelog-dll-epson4180.txt.bz2"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="sanelog-dll-epson4180.txt.bz2"

QlpoOTFBWSZTWTvvFZIAB83fgAAQQOf/8iIBCAr///9wYAdfPtx0tAAB6D4gAAPiNSnkJ+qbQ9Cg
ZD1AAAeoA0RpU9tqpspmKgABoAAAZSnvVRiNoQyDQGINGg0aaHef6qo0BoAANAAAABtVT0JphMgM
jRiaA0MQaaBUUSaGhARpiGoyGTJpNqbKMEnSySDdYP8wGH0wgbZ0zj+s/t9vH9NwT5ySNyIxUhMh
NAmkiRmkTZpmr1RW4ALv7ZsjSSIQBNACfYkkiCJvxc4kQBLIiIJNPQxKZ3K6yaVjFqhNeX8ok9yb
+8mq81WIw075Upq892fctrsiIgIACXV2hQsyzjCM851pe99M1vTbVjttKtMpz12WXW3CMMofFNmU
G2rFcpQi9avpjGLZrimmjPphq11eeM8La+JgAJ188FCKFRFVEUKiBatWrVq1Fq2Wr9A/PSdmy/T6
+P76/XWUt0goFns833ichOBMWJcu5JJJclypXeyMQS0nJhlFQWMToAB4IiIIPsLzkyggylHKTLvr
TEtxIJ7AnTqe+SRo7vTXh4Y087m9e7GfHzM81Lo52qjVFGGmJldbjvvbBT4W6AAATQACcAAC+8kk
ceiemHlXLnnOmMO3FshGQ+bezpbbb8Vz4l957tuVttu0gnt5SSK5503c/g136jhIR3zF9RjSvceR
iOq9JCNvLx56ZznOummmmq119fXlv379+m8rB1zwrNVor44xbWs1xtptz1z6in6Xqll7PebaQvLF
xyzyuLPcRHgYH6G3L8mm23HbRoes3MH4NZi7saZ100ziu+x4HwOhnXhjhwxl/PXnTXXXTRdt3u/T
X3SJHHt2PA75y58uOcrp1HDr8gTOJJHbkJeXVjxCoecglgj7/f7/L0f2JB9fnJEHQJsH45SB1v1N
BDUMyB+xsEkwfE8PnPv8JPoeCBPuHsBNgTcb5v7JJHyDsOhSf1IR7REmBvm/vOw7wm83TdZbL1m4
zM4HA5SSR7cdUEPwE1+h8ZCP4G004yE6LeV/i4uLi44SYzc+fVIRk/J1E2m1l+2TlO/PkE6JBOJN
x2BxnGy9u0gbhvDf4nrkIfvQmgJ2BPLAJx5xBbmTQJndIRX5kggBhJIcXb8LBXFIgACkk1rWoAAp
JIkkfz3ayEWSZEjuCc3uzbbbQ34wR7/tIT4IE4ncdc677DfZykC7HxiD58d08e3Em48A9o8HEPEw
6Tq9W6SSR67e2IN5rNezj1W22/xIRsaBKazWy2X2+EkjukkjSaYCeqew9B4naHf3hL+wf5IQhOw/
twAAAAAAAAAAAAAARiAAAAAAACJZ9YuKSRynebgtSEdUgcOs6gmxZJH+HbJI4HmeueFlstloqBMa
Zvzn6hcSRB5hu06zpIR5Ty7v/JIP99JJGsJBoCWSRsMhwGPTNttvYbTbJiY5jgZmbLZbLv5hOtib
7atWy265kkZkM2xTCyQjgcMhDWwTdIRbJCThOGMTGgRPQLJJGgs4B7H98JtJIveT0DvBKduTyDiL
ttfZtjGMs5zgM3OaXCQjUTe4ySPND0kIsgZ4EHEa8vPNttuxg5yE7p3WeB2GJnuGppGqQjskDBrN
dCDhJJG8iczfrNecgaBzwNTjRx3Zev1/zbbbTU2m2vkE8ZO6iMSSMCR8uEeHfbbbTjOPGQN4Tu0m
m89XecTdN1l/2SRmMzOskkcaTtNlPzp5Wq/c5BMRBTjOPMYmLLZfX1LVq1Sm6SRt0Q8ApEOj1GJA
zToGmpuOf4+u1xcXFxcXF6Tpl3h4PKOzWa2XHWantN/A8ZJI+W6222nGcfeHV22dh9rbbbHZIJ2n
g0gC/i7kinChIHfeKyQ=

--Boundary-00=_VkebBRx89EMFBEs--


From gerhard@gjaeger.de  Thu Oct 14 07:53:32 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Thu, 14 Oct 2004 08:53:32 +0200
Subject: [sane-devel] Re: [sane-commit] CVS update: sane-backends/backend
In-Reply-To: <4131C12D.4050107@freesurf.ch>
References: <4131C12D.4050107@freesurf.ch>
Message-ID: <200410140853.32953.gerhard@gjaeger.de>

Hi Ullrich,

could it be that you've missed to add your changes to the Changelog?
No worries ;) I've just added that, because I also needed to change it.
Hope it's okay.
  Gerhard



From gerhard@gjaeger.de  Thu Oct 14 07:58:42 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Thu, 14 Oct 2004 08:58:42 +0200
Subject: [sane-devel] memory problem
In-Reply-To: <200408261201.55683.oschirr@abm.de>
References: <200408251749.12668.oschirr@abm.de> <200408261012.09052.gerhard@gjaeger.de> <200408261201.55683.oschirr@abm.de>
Message-ID: <200410140858.42684.gerhard@gjaeger.de>

Hi Oliver, hi all,

On Thursday 26 August 2004 12:01, Oliver Schirrmeister wrote:
> Am Donnerstag 26 August 2004 10:12 schrieb Gerhard Jaeger:
> > [SNIPSNAP]
> >
> > > I've linked the sane backends statically with the 'frontend'. The
> > > problem is the same. The pthread lib is linked dynamically.
> > > I've tried valgrind. That revealed only two 'real' memory leaks in some
> > > init-routines of sanei_usb, the test backend and the pthread library,
> > > nothing severe.
> >
> > Is the sanei_usb memory-leak related to the patch you've sent me?
>
> Yes.
>
> > > Under control of valgrind the vm-size doesn't increase !?!
> >
> > Hmmm, strange...
> > anybody out there with some ideas?
>
> valgrind supplies its own libpthread.so, probably without that bug?
>
> > On what box are you working? Kernel-Version and glibc Version?
>
> Linux version 2.4.20-8 (bhcompile@porky.devel.redhat.com) (gcc version
> 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003
>
> RedHat 9.0 P4-2.8, libc-2.3.2

I remember this old issue with some memory problems, when using the pthread on
linux. In the meantime I checked the sanei_thread stuff again and I noticed,
that the call to pthread_detach() is missing after the pthread_join(). This
pthread_detach() is necessary to mark the pthread resources for further usage
by next threads. As long, as scanimage is used to scan only one picture this
does not make any problems, but when using scanadf (I think Oliver did this),
the thread resources won't be freed and will eat up the memory.

The applied fix should fix this problem. 
@Oliver: Could you please test with your scenario?

Ciao,
  Gerhard





From henning@meier-geinitz.de  Thu Oct 14 12:55:40 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 13:55:40 +0200
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <200410132249.08934.mreuther@umich.edu>
References: <200410132249.08934.mreuther@umich.edu>
Message-ID: <20041014115540.GA12141@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 10:48:53PM -0400, Matt Reuther wrote:
> Hi. I picked up an Epson Perfection 4180 scanner.

That scanner is not in our lists. But maybe it's supported under a
different name?

> I have it plugged into a USB 2.0 card. I have Slackware 10 on my
> computer, with linux-2.4.27 installed on top of it. I am using
> xsane-0.93 compiled against GTK-2.4.1 and with GIMP 2.0 support.
> 
> The scanner shows up in lsusb, and I set permissions and added the 
> vendor/product ID to /etc/hotplug/usb.usermap, so it works with libusb. It 
> shows up with scanimage -L and if I start xsane, I can pick it from the 
> devices list. However, xsane crashes once I pick the scanner.

Can you show us the "scanimage -L" output, please?

> I set SANE_DEBUG_DLL=3 and captured the output. It's attached.
> 
> Any ideas?

Looks like it crashes when handling option resolution. Please run
xsane again with SANE_DEBUG_EPSON=255. Does it also happen when
scanning with scanimage or other frontends?

Bye,
  Henning


From henning@meier-geinitz.de  Thu Oct 14 13:00:30 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 14:00:30 +0200
Subject: [sane-devel] compiling with gcc 3.3.4 on OS/2
In-Reply-To: <E1CHqpj-0001Z6-00@mxng18.kundenserver.de>
References: <E1CHqpj-0001Z6-00@mxng18.kundenserver.de>
Message-ID: <20041014120030.GB12141@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 11:25:08PM +0200, Franz Bakan wrote:
> I'm trying to build with gcc 3.3.4 and besides other small problems
> 
> compiling fails with:
> 
> sanei_scsi.c: In function `sanei_scsi_find_devices':
> sanei_scsi.c:3857: error: assignment of read-only member `str'
> sanei_scsi.c:3858: error: assignment of read-only member `str'
> sanei_scsi.c:3859: error: assignment of read-only member `str'
> sanei_scsi.c:3860: error: assignment of read-only member `str'
> sanei_scsi.c:3861: error: assignment of read-only member `i'
> sanei_scsi.c:3862: error: assignment of read-only member `i'
> sanei_scsi.c:3863: error: assignment of read-only member `i'
> sanei_scsi.c:3864: error: assignment of read-only member `i'

The struct itsself is const so I guess a warning would be ok. I'm not
sure if the error is correct.

If I remember correctly, that code was changed to avoid error messages
from gcc some time ago. The assigments to u and i were done in the
initializer before that.

> I didn't have seen this problem with earlier versions of gcc.
> 
> Is there a solution or compiler-flag to solve the problem?

Make the struct non-const? I haven't checked the consequences.

Bye,
  Henning


From kpeters@LHSolutions.com  Wed Oct 13 22:16:28 2004
From: kpeters@LHSolutions.com (Kenneth H. Peters)
Date: Wed, 13 Oct 2004 17:16:28 -0400
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <004001c4b0b5$b48b3e50$6400a8c0@kpdesktop>
Message-ID: <000901c4b169$e8829190$6601a8c0@khp5000elaptop>

This is a multi-part message in MIME format.

------=_NextPart_000_000A_01C4B148.6170F190
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Gerhard:

More info ...=20
=20
I download, compiled and installed the latest 1.0.14 CVS version (this
version also exhibited the imaging anomalies with plustek.) I wanted to =
try
another backend, so I purchased the Epson 2480 (need latest CVS to =
support
this) and used the "snapscan" backend.=20

I was able to scan using this scanner which indicates to me that any
big-endian issues associated with running on a IXP425 in BE mode is not =
in
the frontend (i.e. scanimage) but maybe in the backend.=20

Attached is a ZIP file that contains output using the "script" command.=20

The "gentoo_xxx" (Works fine) are files generated on the following:

	- Gentoo 2.6 kernel
	- x86
	- libusb
	- Canon LiDE 30
	- plustek backend
	- scanimage frontend

The "ixp425_xxx: (demonstrates "color-bar" problem) are files generated =
on
the following:

	- MV 2.4.18
	- IXP425 in big endian mode
	- Canon LiDE 30
	- plustek backend
	- scanimage frontend

These all used the "scanimage -x 10 -y 10"

There is additional output in the function "scan_it" from scanimage.c. =
This
diag output is from "if ((output_format =3D=3D OUTPUT_TIFF) || =
(parm.depth !=3D
16)) and dumps "buffer".=20

Please let me know what additional information I can provide.=20

Thanks,
K.P.

-----Original Message-----
From: sane-devel-admin@lists.alioth.debian.org
[mailto:sane-devel-admin@lists.alioth.debian.org] On Behalf Of Ken =
Peters
(NEW)
Sent: Tuesday, October 12, 2004 7:47 PM
To: 'Gerhard Jaeger'
Cc: sane-devel@lists.alioth.debian.org
Subject: RE: [sane-devel] Interesting image problem when scanning color =
...

Gerhard:

I figure you are pretty busy! ... I appreciate any support you provide.=20

I get the same results for both TIFF and PNG.=20

I am currently going through the process of looking at the raw data from =
the
scanner. I'll keep plug-in away ...=20

Thanks,
K.P.

-----Original Message-----
From: sane-devel-admin@lists.alioth.debian.org
[mailto:sane-devel-admin@lists.alioth.debian.org] On Behalf Of Gerhard
Jaeger
Sent: Tuesday, October 12, 2004 3:52 AM
To: Kenneth H. Peters
Cc: sane-devel@lists.alioth.debian.org
Subject: Re: [sane-devel] Interesting image problem when scanning color =
...

Hi,

On Wednesday 06 October 2004 15:41, Kenneth H. Peters wrote:
> Gergard, thanks for the assist ... :) ...
>
> As you requested, below is output from two scan sessions:
>
> 	1.) scanimage -x 10 -y 10 --format=3Dtiff --resolution 50
> 	2.) scanimage -x 10 -y 10 --format=3Dtiff --resolution 300
>
> I am curious to know what specifically you are look for? An engineer =
here
> believes this is a Big-Endian issue, but I have not been able to nail =
it
> down.

sorry for ignoring your mail so far - I'm short of time (anyway who is =
not
;)
First I thought, that there's really something wrong with BE/LE on the
backend, but when comparing the register settings on my box and on your =
box
everything looks fine. The picture data are 8bit wide and therefore I =
guess
there's no problem.
Did you do all scans using TIFF? Can you please check PNM output too?

Ciao,
  Gerhard


--=20
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@lists.alioth.debian.org


--=20
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@lists.alioth.debian.org

------=_NextPart_000_000A_01C4B148.6170F190
Content-Type: application/x-zip-compressed;
	name="gentoo_vs_ixp425_plustek.zip"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="gentoo_vs_ixp425_plustek.zip"

UEsDBBQAAAAIAARxTDEyX31SOQ0AABYaAAAVAAAAZ2VudG9vX3gxMF95MTAuc2NyaXB07VntT1vn
Ff86IfF9UtX16XvTBHNffN8cDL6vBpKQtLSTtqqZDDjFDdjINkmoKk1dpzYJGAMGG0Je2qRpu1Vr
1UJ4M2AgJglZlDXp2mzS1FX7sj9iX3bOufdSUrVT83FSJYc8PPe55zkvv/M755j2znSiL8sy2Vg6
G+9iqSR7oT/ODnZmGS8wPhji5JDAMYHjgjUPvcTxe0Wh92hfPBtPZyKZ7kS2Ox7rYu6DYG+mM5bs
ibMncIOj3xK9sVfirO4E4zlWN4A/G1myv6cnkE0cqa3Z13yIbZ+qrdlehlgyxdr1Npt1xY8lOuMZ
diTVn+yqfVANHnpp309KbCsRS8brjiSSXXWZzp+xn8EHjyTj6dqa2hrGHmdtcJPZ3sK8be+qAGs5
wgZS/Sx+oi/eiRDJpHrj2e5E8hXWlThyJJ6OJ7N7WG/saJxl+tNxlu2OZV2B+FZ37Fic9aRiXfBi
zJXflU4ci6dBehpPpN3NWFesDwwJoDJ0L3ux3fBVYc8ciye7Uukwd4ILxrQ9rC+d6urvzMLvgsDF
97DO7kRfeP8BTRVPNO1isSzrSXT0ZzpCHMfDP9VV51d42U6px2MZ9gyI6oh19AzsAg9nyUCwOAv2
DDBQEP9LprKsA43r60tRjnQMuAIxLgH2QnqA7QjwfhYD5dMYCggI64h1HgXdn86AqGQfnAh86+4s
6B3vPIqeRGf0xdKxnp54D8NrtqOwff5AKpNl7X5sOlPwP4Ujm6KL7n8bxKVgN42e6ksn4pDdA/Qk
4woDMU+TVb7RYBSISWTwhVfSsd7ta8Fr5IXjsWQW70r3J+87yMCJ6VSKniG6GGjhgzXADiY74xhl
V5YbWNTWD4F3cI/rYERPCqDwaj+YGuuEB3BNPN2byGQSqWQGrnLlgOXwCEwKPHAiZADIoK6bAO4H
ta+tORTLZI6n0l0h9q1MfPKDAh//sSzXEct0h76FSAhi19uLIEFgfSedf8yNkMv1/Zl0fU+qM9ZT
35FI1j8wv+CvB/viSYi7GwGMNm7Wsf12W4hJCjP6MbdD7ClOTaffnP73f944+8Xx8t/bhmfN3KIz
shItLbWWrjiF5UhxXS+sG4X5aKFsjV4LT1StiVVnarW2RpCZyDFRZYqAH1VkmsFshTkGU3mmmcwS
mQI3GczSWNBmqs2MIAuKTLWYATsy0zhmWCyoMA2O6Syo00KiRyIzTBbkmCYzk2dBHndwIdAjhd4S
UXgwyDSemaCMxTSJmUHakZhhkxwNF/dZz/PBbfMf5vbWvXzi8AfX912uOIXFyFurkVPlhuKcUbhi
5ypOvhKZLjdNz+kjFefUDWN4LXxmQS+tOmPXHn1W3vXya7++uNX87mbzmc2W/NXmsaXQ2CfhoU/D
v1tsHCw7U2W9VLHGrraM3zSn16zzs5FC2ThZra3hLfKbwQSLSRZTVCbZTFeYCUYZTAfNHd8DGnpA
lckWWGhor2iiTwzZdwW4SyKX0luqQwsOY4GHHVrI5EDOP6MxU8XXISImR37TmaHSGcX3m4AuFXgm
6EyEhUaq6kzSmQ6PQDGV6eB2CRfwOi40vN0UaUfAgIo6LnQHr1BNZvC0ENAuEfBAGnoxMvzbHQqf
QHI0pgWZqSNmwApQFR+5KOL86IMVKgb9B0P8893KU4dfP/D+VtuFqlHatPIbjaNzkfxHewdnGk5V
zJFl88xSw9RqQ6HaXNxsmV62SnOhsUrj4MbD9dqTv3n9xctb9vlqZOhaU35dLy40jsw05Jaahst6
YcYqzhj55VBu3Rxdc4pLZqGij11vLG5CiFUmgPMVBjkCwVUAyRbTZfKbzTSHUCqgvei3IPlNQJ8A
kjFYHO7oBoIEvSRi0DH6DrmCo9QQKWo64YFAjguRJKuUNRQRjL5JflNQshsRkOP6Hy4FNArwq8YE
iUkOqipJCEJUVUJvm+RtCB+mmEOquvkoI2ZQZ87X0CJ9HMp0w8tZeIS3y7QQCJ8mqgGHUY5IycsR
DGQiAZHecuh1AZMCryBz7guxIKjbIX6MCz11+LdtF/5ycPK2MbkZmZprGJnXf79iDJUjxStNE7PO
cLklv2EWlq3ifGRoNTp4tWVy8/mZu4/xoV0dbzZPf9U8fbv1vev2mUUjv9oytKLn5/ShT/YOlsOn
NyLFCuSyPbUWLVXNwupz52Y///ofT3Las51v7bvwRfPF287F9ZaptabhStPIfNPwn8zcjDW41pi/
2jC5ak8tOxMbzePVaPGjv/3zG1VUH61X64+81fbhLfODasvZijO4YQxXI5ML+uSCNbJi5Cp6aSFS
mgESNk9VrVzl+XN//PzObL0oAd8KxBu6DyrHxxIsIM0hC2wClUqh5wgVMqGCI8LkmRokvhUoGQ2P
XYFAkCUkSivZj53mYdILh+kHUfHAgCyhEITcPKVLJQGjbAkMVeVJVY3JVBoQk1AIZG+BqgKTBIn0
JEKy5sPDpttNUpWnHaIv2EEmMTzeQCbRSUPXCmcHk0i4QFBRZTGDvhU2kwBUFlpqccyymWUi7NGr
GhKdLCLZAgmDVy3SGbmO+BAXPFlKkj2QO+Q6cq+7o1t+gSPYq8RamGtEjBgLlQwkDdGrMtUsgdwS
JFUVNAdy31KZ5TCbKqwo4k9kY4cWDpNlUhVuBM8TG+iupRpWXo/nKcE9nnc5U/V53l0E/RIs+BXE
JWGVDitkxXa9FqlwUHl1D0O4wZm6Ts7k0auoHqj6nVTd0W48wWm7u0+2X9raP3kzMn67ZWItMrFs
ji/pOcieZXtyvq3wWTi3sndo3RiD+rn02uTHf5gp7+GV/69MDfqYMpisYoGSID4icSpBAGsaRwEn
sCMEONqRfGoPEhfynqc9lJkEHJWy0CZEC5QHFsYQM8P0WyRhR0XVsW7DWzqARcOQwiPBpARV7g+U
iKD0ObV+b92rg21n7zw39VX0/Ofm+eXWySU7txY5Wd47PGuMz9mja/bQ9WgJWpvFSHFpYHz+7r1/
7ebkRwJafWLQmf7ywIV7z13css8thQvr+ukNMzfXOPpxaHgpPFSNjGzY0yvm2SV7bD2aX/tidf6D
v379aEANdOei5+60X7rZfn7VnKiE85uNhao9uWhNzBijlYZ8xRids8fmornlxlwVxB4+W7l3b+OR
gML35g+9d63lw2vPnb1qDV4Hsca5Rb1UjuTWo4W15okFozhrDK06p6tWYUWfmI2WrhtvDP4ioIrJ
/IHLW63v3mo9cyc6sbVvennf5JVIrtz4dtnMl83SfNNIpWF0yyqtt55d2lf89M7X33AQH06rT+Xb
L11vvvBl6zt37XM3WqbKrePLkbdXGweXwDlGYSEyWo0UrumAq6n5ty/f/OzcxG4IdUAL9OQPXrz1
y+m7+8dvNZ1dN4sbOhwbq4ZLS/rUrFNYiA5WwqfL0IZY+cXce1dG8mN1Hv0Ljtc2yjomN2LAxMxD
VtOIXBWs2JCOCCGbAEOhRyxRk+jCDABpuM2F20wJhDeZ0OVWY4mwpPgMut15aT7dAqioOwMoAt9b
CrMFank47BZ5hwk24R+ISiNVZaJ/CfsgJFcFdfYaSYkoWac+VPSaC4/aXe6Rvc4IAIyNg+0dRg1d
VuPosETNDhEwUiCZrLm0rRABc0jqwL6gM5ClFcQKgJxqE6falKruOGKRV92c1XGBttskmdpzvN3B
iifafs/lJqbmDx/U7GA351Bn5Hblgt/fkWIGxQsNNKlEWChn2wmS7RE5+Ao+2Km5XlUwc2VSQOKo
hMrIIVgHZEKCSTXZLT7KDicQW6OGLi1Q/fe6MJqlMMoqKU/DAUY56DcLVAMxKO50JXrF2esaXJAo
dJjHe3nb8ypUA5mqH/a/blOp09zgIlNHP+Pr7iPDb1cNcqbkaYhYBSGuziI5kxZoheJzI/kZ0at5
3S7apftIMMgcHq+DoGNRhU8Q1RM4n6sBq9TeenFXyBsOgRZ05hDnLlZxeNL8XkOnLKBRVaXhyZts
9B1p5Q5qblHlfdCKFDh+RyOgoTkgBB2lI7drNNFiWgVJQ85PK8AqgQr6Pkwi6Nnd/BKovgRxB91i
+i22TAnC77hU8MGmeIUGbw/6c6fqNXce1HV/zqYZwp1XAEgQGoAfhEmjeQVkAjV9T/3fOY2xejXQ
M9b8zlct79w+cOGqeWYtXPhzZOyGdWbFKM1FSov64Fp0BMh/NjI0Hz65ET1VmR4fe2LProcD2p6j
hdbzd+xLtw+9fyM6tdk8esMurpsT89HBufCp9VBurWlqpak0r+dX9JEVfXR2ejz1tCD9VFb+d1nh
/KaSQKVRK4pod1mFoxaFSNsUvaHT+84AsOTOEAJlRJC6eMuba90pFhdEOG4jjJnO7SBSf7LELLZo
jhcIeDTpAp41+iYAuiloV2CSwFHVxb/JZAMVwOyziUMkylmbKFEmfRRq1d3vJ3jakfwvk9zbFR/k
9NUR9ra8P5hSg48ZYdFC8ecnx+c9zl9Q2+uqCuwhgCEC4v8Bv/CLn0hka2vcnw/4jefOV2va3b/2
dKWS8e/5U48a4hT3Tz3/BVBLAwQUAAAACABodkwx3GJv04slAAAi/wAAGwAAAGdlbnRvb194MTBf
eTEwX0RFQlVHLnNjcmlwdOxd6W/byJL/+jDA/AXvSwcD7CgDHbwP7XOwjq/xjh0blvOSIAgMimza
3EiklqTseP/6reomZTYvydcknqGhyUis6urq6urqXxVb1MSNg0VKktSJU+qRKCTnS0pO3JTICpG1
sWaPdYsokqT99M/PkvyfqjKPoyj9r+QqSK+o4xF+VZsnrhPOKPkFL0jsUzB3LikZSP8g//hGZIkM
bvHfNyRczmbDNPB//im5GpMV55i40XzuhB4Jo5T40TL0fr5Xn//8/Eeh29ou/7Hmb/RYAcvHCkge
KyD+7jaYPVZA9FgB7mMFON/dBo+eheljBQSPFRB+dxv8/NMfv5/eRZiff/qcOCENLjw6XV5+IROa
pkF4SdhHMqPXdEYinyxmyySlX0kaQdwbQqPswhdymlGmjvuVQqD6tzTUzIEs98kCwie2RfmDjJwQ
eSgNZa0o4c0vuZDBZPvdHnmbSXKj0A8ul7GTBhCC/WBG/1Vqth/FZJlQcgMxkBwd25Yqj5SRCrok
ELffT96ycYY0TkotxY9lsdRxr8AA14FLSUgpKO2kYAonSUl6E5FZENJkXG40IJ+XyfQLuQbVo3hw
uEswbC/iyFu6KXys8mc98P+FzrwyvGBIhxD045WNe9I3yXyrvibvz2VlJBsjRWPXJNl8XW7MteEN
COcps2QKjOD/I+DObFXmiipXsnazYAqtxtPpdOx5Xpnp5orGlACRBAmBLYoAc7icT2nMDAMt2NXc
zIxSljF3vlKSLEFOegVTcBst2XzH5MqBOXFdmiTokSOwsjsC+TiKEXQ5qupTFu14XoB+5cxmtyiY
wOBJsqBu4N+SJJpTEi2QXvYccuPE8+WiT2Ynvn8S7oUevHXmC/i0pkd0VmeZRh5NqctcGoZSO2sP
mqfqtJEkmC9mt5t0UdM48JlZbpwwJU5mmcDNdZku2XTARFzD5EUk8KhDnGkEl2FWGwYQwthRNDbE
ZcsdqJ/pSRKa5qtnzdrZ3LfR4GvG+u7kfG9cmhlw2cTxaZ+AnwUpKst9OAj9CC9cRmlZDP/z42jO
OFnwWU6TW2CYD8khs+avMWVAbplgiK0xFP8TdOkzcx2/n5xzYztpCuGJenxJ8GE2iMlWDKgyWERx
2l+tIi4pm1PqDYfDe8THqv+E9FuuCTeVMIAiJ/RU5G7ppeqSfDmyeIgGXsQgIlomzNI0TOOyo5cF
JLBLQFzHxQq7kk8cP4VI8u3bN3A8N+kTiXhB4kxn2VT71Ekh8ohSuBL5gieqJAn0XepGHk5txvem
NjLURxSyoHEQeeBiqE8EWyWqNKcOjBkWGGeq1SZrL+vtutRJKKuSdwibHTgIaj+ALCgFKy/DNFqi
3/WZB+eMmVGjSvTDrAk3/gt3FpXDXG7FPIISeY0Vc8ZW5ZscBjaI9IY6X/kCZsiJZXawJhK2BZQb
9j5sn707fHcwxhYx/ZXZPwjBW2C3ILETggSwhPv11atX5W23LCv31jCK59AYQzdxYuq0NsvGDfrB
wD+SNT6WsbWI+LSZiE/tvsGGAqNPANfR0A1oUttlunA20TpjaxGxVuuMbb3WIb0EDHndoDBQN1E4
Y2sRsVbhjO1eXoz6JxkmR0dyHdg1M0icpHGwIM/hxmQgZwsc9+npMpil0HRDp51cOTjsTyBkrdvl
vE1+sLGsAm/TFG0sq8B7r7lK0b7XNE75ks+9brOtpd6cXN67XNQ6Dyux31f7BKL+KKZJGgFQcSMn
TkSH85x0o8jlIkLZcWa7wL9O5SLvvfRFz3RmzJ1TUc0YYCjmaJuoChJ2Ck3XKCtyt6rLV+7XYLFA
ATdX0ay8eGn9do5t7qFSif0eOgFoCmCefTDVGs1+qXMGwMheFNZv7djHPsrdQHnka9faw7JLzPNF
8M7ljJUV2ErCPm6uAtEBWlX6wLg31IsxrzdpTBczx81D9KUDGO7amS1pwku2xFvGQKzYdI3GMfUu
mCyyNmLlrLVyLmNKQy5pnZw71lpJUxhTptI6SSvWe61pNKbj/Q9cyI3pUd/BCb905nMns+om6xos
csCa5H/ycM2c5y2abVgUuFbcXYtGUwoKrhW4atGgoHN7P3mrFveaIdglaIhbGTk/3Sa9ECSdcnKW
0yWA/Ge3FUCRJwz5fE4p5KABpqeQYq8yUcx+eJ6dwZSU7ZplYTk44Zps4g6cE1VeY5UV472sguUK
CEkujCehhbrWoKasV267SXWnqZqxUj+vsEB3sEtVih7rJxXmBWOpA7DlJpPW53kSr65yQsJT+krx
c21NiVctSA9VAzz0ber7vqvqUh9cKJi9fi0Oio1FKP+OiwzFwZJxzXix4nG4my2EcWn488jDmvZ1
PGREqUjLUum8oawnRWqe9mdUyP5rqDyjHZNbKrQVINEYoLhgnTtYQSvEuw1+SGqJbKPlKtUT2S5W
Jq6gYlIjFpD5xbc8kpRshLTbFlrCofPF7Rg2iSIRAHGjUKQ1CUVao1DA/Y1CkdYkFGmNQmErINnO
iw1FIgvsOblMxCC9alonFr0Eq08NYjNyrdi8aZ3YVegfY+CXqoIzhiqZic6b17V2blvIg7q/IgME
BljPF9GChnzxC0t9u1goHA6FG0s7mJtibENQgLXeqTpgtV5pIy55Iy5zIy79CWWpT8i12Rg3s5f2
hJbYTJbxhFbdiEvajMt/Qq6ntJfSxqVJEnDJktQ62yuuVs/ZkEu3gEtZY9UVl7URl70JV/vqWHG1
2n7F1eqFqo+WkPT2ecy4jHYubYo9wnJs9ZycS/ZauGRDMphPGG2znXPJrVySZvvcv5xWLsdGeylS
q71WXO0+kXO1+0TO1WaJOy7hZtI+T7sz1JySN9m9ahgl/GcJePDf7JYjOdzdQnHbdp+c8huP/BKI
3iuyg5gguthlmxY7cvCtnTomvAbAPikjwXU5H2zf/LYn+Y/8nid0PSZcnUFVhd384EDCDqph3oLW
eCM0+Bfvd1jS7iIIgxQE9DS5z83XH8h18PvD9j5Tgf8ZNRbjiTreiYwAY+84YamOcbR9fDqYnG+f
v58UJAm+eLY32Ts/P3x3AO8ODifne2eTXkmdnOH89z1yfDjZIYejEwFZ5xezG3pMJPZnGH22CPBf
W4xkhSoWHithWRq7/QwjKTK+GeEZu9EQb2SN2AAH72RFk95fHAW7e6o0dJ2ZMGQ08ISmE8jhTp0Y
pIJGSU8Yz2/k993TwzGxhiVb/EY+AmFLxqQIWbZqOD6tOI6DEN5/2jJ1kQPzi9PgG51NMHfb0pU+
OYIUAHISeC+M7Q2BiwPOVuxSlLe/nM3IJKULdiNtAhkFrifWimxlsyq2QOZJ8H+0dxpTsOlrYJO1
7JyKLZVsgZbCQpi7nLH5SEog8Dem/RENL9OrLVnS7Ww8Z5Ap7USzKN5Sq70n0Dv0atts7jUDFzae
E9BMeEe1ksFOd8mWbUhMQdUtK8jIqmTJBjKYliG97rMKKcFetlgf+DFRYnq9pSpi69mMhrnaM1Ht
Pvnf1A3TLatPrnz2puxIBzQ93jn6Yze4Djwal73oMEzpZebE5wH47zZbjjgppHfnP30mYkvD92Xb
Z7eVDjBBOP1wvLtMb3du3Rn9Pbi8Ell3lnFMw5SgMJIpBD0xqRUHOD45PzkbZNKTMQHROAMwUHh3
sfv+/BN8lH2x0f5+7jcgV7EgCn+GCbO+cCeT+Uebf1Rkse3p1e3b25QmkKFsEaNCQ3/htNLUn0ep
M+Mtt4hZmrrToy3F1vvEjajvs7lWMJYk4Ky04nWnzjKhR8E8QPsrXFkq6u7nHzeIF6ywXo7cmEZd
0nTHWZQiyoRXjNjhlHheLZdk4XpMWAQTQicrhQCFR7URj2pFjv2Zc5mw5Lk2fnvxNbu/LyqUKZuk
0QJ1qyUiAeJP73VWZcIQtHDir1tSDXNNH7ygNM6qOVvkjTAEISizYwhguYu8QNnj9SeqGeCT4qpg
vJiskgERMUORi0c2vnhYaszLlKSHy12TbKO00naucIZmn6Uv/ayQrVRje84kb8KkbMKkNjPV5u2l
JB7PiZ6AKWiOpCqGYjNXM18s2xfNJ+b9f3vMpf1YmKukzvsJklfAKvP1R6KuthCGRW9cybCQ1YY2
cbQ4hABXCSa4TR7iqZ4q9fT0CMGHkFMenW5Xrr1lfLqQs0xj2ATTEE+YSrgJhGmM53/rolPCA/he
eF1VbuJc0wbtvBsMrisQhVn35kP7DWPQdUBvWAzHM4w4S6+KLBwP7BxOjpw52FucYRCQRzAX8QiL
o0WGHBzMnQWELcR8uIVLuk9Nt4lPvuMz1BY+pcBnlvhWewdElurmkYNnuSbqcfQs5VC2joXBZ1Nv
Qs8bLJ4JO++GAzli5wiF7fQDu3swQDQW598eWi9fWCQodSUgWixEAd6Nn7uMlrkMXGMI5pTGiHOY
H5Nim/PD4z0CnZ6dF68Wlt4qkDPU8fNPMXUA3V3gmWr0/vxbUD0Id1+pJ0yHyDpmrGgbyBTO9rZ3
2XkR0pMlSyVTVFJoPF363PnBC1xNq1tZ4ON42KzqB3ABIn5USORKkGjvHKHqZ2uEGyU/bsvOiBJr
TIwMtfbBjUqz29hMHhP1rpnY6hf2R7Z3/xsP6eIkk97OyfbZZO81J/1S5D6O0ijmDoqyjp1vx9E1
nSwo9bakoWrAtTssvCXLutnnSc1WSVkGsxvRNbqIju9Y4mOxfZZlQza8tXTBRXDMF/v7HzD6AjJ4
w3bBirl5PDnCsJhEy9il5aW5w8+IFLPrCZ5QG4tsORzHMFwKaZi3cqQuS0p58eYQHzF+eeJ+IycQ
r4Nw+BHblreQTVNyuSmoKHdRpSkn55N5/6QcBtqSlzMzFLoWxT5Nbm4rPDevpL7PmZubtimtknPu
rSYDfiXDYfat2VxFWbVqs3PFMC1WXzAsR8zOeS/JKj0vWeO7ZOdKlp3LhexcrcvO74wly7aur6yl
0NxaU7XGGqZmWcxanlZvLU3hDDqlorWybp7eXE9Rasijr8j8+FKDbCtiqUESSg1uqUOx1CCXyuGl
ckMpvAnlBtlSDblkpdOjLVmTiiUHpt0GJQfWrFB00LQnKjqwPP0thdBaxba70U04ixwvOyuLQa6E
Ms+gYYLpwe4SwNKU+niuFEED+gKCA2FrQOOPycePEMCJoRBFIpKNH+ElqYRIGrskEVknmksUH9/D
SxQhgwi8rhFJJ5JBJDNjgxe7pLAP8t3ViggFRCg20R0kqdCrRSQXe2Ui1FwE18Ukqk98vyRC5VoA
VbaJoeXvVaJopNCznL9qtNBAhMauKyt+aE/JVGUi3IL+8NI0FCSK0LkWvkt0SijnBKtZBAIufjAM
IhvElgVziCIMEAEtVQoOi5wy9GQQTyKWxAeiZc2mK12mJRFmNiP5Sy28FwjFV9nXDhN0r+1rJ5hh
qeUw3D3bPhZdkp2sCRLi5EwlGbVVJ7mu6lRc5k2rPMMqNUhlBxycBTu8tUB+5SdnB+y7NNIwdm5+
LTK/IR/ZJg96fEJlPLrAzdTYUGBy4yweJhRPjKKIC3YYBbYldSQbqqWODF1XBfjCz4SueBmroUtS
lZOd+RQZNbuOcef9We+sf9B/+xqjkyG7Tk/RJVV7jZucJVlyT1Us22QfTZeaPVW2Tb20m52fnJDd
7bM/GGJdLkTi6lteM4yQmL6AJN+nGbxV9/f37yOulQgp9uBD9q1QOXn1SsjCO/hZaDHp4GfRRzv4
2cFPu4OfPxr8RGSUQ7yXDj9VhbhW9l4xiGa9PPgJ+gP8hGZTj41dI4a1GkgVfpZFdPBzhRbl54Cf
DxNahp8ce26KQBn8lFVpExDKEKhtrYehOvVpT9FU2WK40/UVo6erkiqxj75lOj0DgmZ5V3sGGPr2
7PDg93PGA3ZaijdeH9CjodtSc48dfO3gawdfO/jawdcOvv5w8JVR+XvZJVPj5cFXQKomg680h69O
G3xVO/jahDaV54CvDxP6OPjKkWsDdy1+NVWdg1hhZCJ89XwT4Kuk6xl8lacIX2WbfZw6vt3TTMv4
Yauo9++rA64dcO2AawdcO+DaAdcfGbgqMjH9F1x3Ndzmuqu90kXvgGsTzlSfA7g+TOgjgWsbdxm4
Msxq6aa+Friqak9RLZ0jVddzlZ4Omzs/DeBZVO3puq6oL6/u2sHXDr528LWDrx18vWPu4Gsd3vqh
664+kZ0XCV9N1szVmuGrudLF6OBrE9rUngO+Pkzonw1fTdtQGIYVRibCV5f6AF9NW87gq+EAfNUt
g3+0Nbuny7pid3XXOwkdcO2AawdcO+DaAdcKYwdcn67uKqHihZ5fGHCdttRd7+Co0gHXJpypPwdw
fZjQPxO4MsyqGNZa4GpZAFwNKzvv6voSAFfNyOqukobnB9Q/o+7aAdeMpQOuq9474NoB1w64dsD1
bwpcqf6CgauRV1yVDrg+CLgazwFcHyb0TwSuHLNqirwOuE4dDYCrZkhZxVXyEbja/OCrp6laT9dU
RfuOwPX+4u7sHPJnXClqEwNORG5bkado/7BOSP0EiTyFaQlrNRHnDSdOE5/I6zY8Lqy6c4iPTjuB
HXfvfPXwNLLJo9PgSv7sNFORhGen6aawb7Y9L01lT0krPS9NWT0vTRPg5trHpT38EW/iU/DurfGT
POHtBDAFTavb+A+WHElCbiTK63Kjot263KjLjbrc6DvlRpOhd5M/17IGBN4Rm8htCJORmxHmA/Iy
ETT9BfIyeCkm8ay/eV7GDnI7bnNeJq900V58XlafCAFYfeAD2M6oN1nO2QqFEOFcY8wTOmQhGVlw
EapmLc9bQM1MCsRhTTJqeaCjkwzdSyNZH6lypZcTBttrqCj/hOPxGurZ3gHEMpUFaPGHsTKK3Uhx
qpQusDDqkwcWP3+9sG+IuDqRKfZkuy1fbX75BZ/mwPKwp+AUAouq67osWavYoWqWsOQKIUa1TNXW
EKBlrADRmyKNrcqGodkrVkvXSgrcBRxzJFe7zONNmSiEmzKxGG3MGoLdRHAqhC7UMOqThxozf72w
2rJF8TQy9OQpf+nTvM2h5mFPLCiEGlkyVdPQVhAE0lGhZFBEM6ptmCbWlTJW1RB/OeUu1MiaLhmK
qqxYNbEQ8eOHmpoa2LqK5cH24bv7/tjDX6tiWUo5v0/J8sAp7w0b/RZFXmUgpTJD2+9QtP0KRfcb
FF39tKufdvXTrn6KandnS37ksyUPxf/ydy41WPomD6Moi3h5+L+17v+AcyWXAJEeWP483v5Y/LUG
XTZ6im6Z/NiwZ7hqT9dskz+9wfMsq6cbpqyIi5Bj7imGAvE3kjOK+6UcqzKCVyF0YKrQYtKBqULr
Dkx1YKoDUx2Y+l5gSpFeCpjixVQzvyFM2x6NUNaiA1MMTD3slo8Ipnz467GDsRmY0lwAU1Z2stXz
FBPAlCGLD20tgqlSkbcDU3diOzDVgamKNTow1YGpDky9CDAlSy+rMqX9TX6e6lnA1MNuaotgynUl
fHKoovBHL3m6jWDKsLIvtLuWBGBK06xGMKVoNZQOTHVgqgNTHZjqwFQHpkQRLwpMWS+rMrV6aGfN
VxX0lS4v/6sKzwKmHvZo+FJlCn8N09CV/Daf5k0BTGnZUy4919MATOlq820+RaqhdGCqA1MdmOrA
VAemOjAlinhRYEp7YWAqv81X88uTf6XvTDwLmHrYg8pFMEUNR+/ptqRlt/lUF8GUkv02ozc1DABT
smE8G5iqnJVf98UG9mSb3v7hu+wxLN2jWL7H9xp2wcWzKF36eoPorz5sXQMPmCu+eh8UrTTB6Dso
W8PyOBitS4JjCCBa041iv6LMDkO/QAwt5RhaWQeif1jcqVr6/7d35c9xFFf4d1fxD4QiaTAQG5A8
1+7MSFppZ6ZndNuO5YS4KMqRpbW1FV1ZyRhIBSpFmRhb1652ddsIxVC5ID4k69yVFklGPmJzhRyV
SijyhyT9Xs/IOyvZEGMOV6SCcmvmdfd7r9/73tfTq1k/7xR9vFPL444+3inJyoa7t1innLf+Ptop
wYt58zrXhGRRvxvWKUk+0ino3xDpzHt4cK9JJzLIL0c6+S//C+lkwoe/LaSTYYskEeij+U0Q9DuR
zqBG6rnYXZDOgADHoVI9C3Y4wVXwOFQT/KSz8bbuvP9I5+3KNWZIrqCfYD1dUbnfzmNYudJbfzn6
1TGsLd9+Lez16aZoZ+QL09djIL3FX7f46xZ/3eKv9wd/9X81xpfjrxo0tvgrkdZfSPfN8FdGTVXk
r9ohl79Kd+Kv9//fRty2YG8gsPcLbUKLaFvOuz82Mabgdj+5Qqwcd0YbCDwy9SXvvXw0687B3ziz
2Sz34tU2X8jahpyXpWwOj189EVMD3zIaJurfVhqm6Oo6CwNM4yzscF4BR5YlBgWuYP2mJEwWgwwa
mYB6SPOTMJyjY52D5Zf4LRL29ZMwURI23L1FwiTdf9N/di0oSn7nmpCkB3JJmCQGv9jRtegnYfK9
IGGVLfVHIntjbQ2sthURDKU6UEU7KG0Y7/Zcrba+3aNr+WF1KAZfSMC81YGRBNXDL9DQ1toZq2eB
RjyBTT461OiODtHVUt9OhA1pnS8hfq6ElCexwZDNMXkzXupPBJozkayRdjwEzRX4EsRVRiqWR1xF
TgH/34hr0JtMRl3EdeIq5ryYRN6cuEpIXNVDwDRB7C6Iq4IPXoUGIgfIodt9dPIrfPBaV9/S3hw5
QJzm+iOEFUayIyCQhxkPYehyrO5oy4GQ5P8z1ryHQO71gvZow6Yn7vBJmQMh2DDy83ZfPdnnRmtn
UwQjlrS2HfN9ux8DSdoeLXyeeD+AhvkfHgCJF3Ik/ATkhx2RmG+MEAkImwm8cDuB3UdbDkView4j
dB09DBAkK7r/Y4QI5XsjsRyZoK77CW7uW+E9Y/xVIffF8K6ErPkFciqD54+86pD7bnpPRvcL5CrB
DVb9Aj9inLIx9xX3+WrgCK6xKCDlK4EeoVFWkmKNKLHZ/f1tyN3Iho9vufdhbe5oBEhtbsTd78ge
2FZdsZcUkBp7N0txLUCYjYcjsSLymKC99OLLxz/5z8jolV+c//ePu+cq4gu1qWkrdYnGMzSVpWOZ
8OB0SXy+PLFSmVyxBuZDifmy5OpDBcWFzz7f8NvVqrMr4e5sWdc8TVwIx6fM1xaM3kV7eMYanStL
Lpb2LpvJpfLUJbN/oax3NTRw+btPKt9/9uf1b6xVDVyzhq7S4QVn+GJpz2T41dmSk5Ol8QsV8bTZ
vWIkl50zS+GxpeqBbLh3tTSR/s6T6uMHX6odv74vda18+Io1NF+SOmd2XaCvzYUSs6Xxi0Z/2oq/
Fx5ccV7P0NG0nciWJlZDyfRDBfpjB1+qfuN9Z/gGTWaLBy4V982Yx+fD8bQxMFmcnDQSC0531kjN
GQPTRk/a7lqpSK2ao4sPbJMCAD+sVqk2UQ2iOvDWJxpkHIroBtFNYulEpcQUiS2TANues7YBWMdA
0rSIQonOfK0SRcZGEN9MzW7Z2AgQS8SGhVcEoqsgLFsoYxJFJYzPWwoj2ERXsMHGCcItmcItaDh4
K0BESiRKZJNINglQompQEw0dbikGMXh3ATRkk7JemoVTKDiOhLOzSZmwRDQdlWc1wyGmQ5QA0dkV
DWc3wUA+Kbsl2yBjydAL1BBQZ24puyLDODCXA2qAzkFisSJiE8nEz8WpqKpJgiIxRGJpoCrImDiX
RiwDNeT6BLEh46Q2Mbk5zBs6eEwz4Aq7BVZI3hJQNIei7SJqKOM4NqoqgOehYZJb2QN0IxI72M6o
H+NmRawmtEY7miKNPh6Sm2476irLdxKrKdrcCFkHbIrs6Igeaa1vDokqy0wwSERluRtsdDklooFu
UKFgBxwIMRYvhkAsiwQkjA4eAjpEGfcHLLiFDhbQMgttVXDFDC8odM8NMhotoxtkuGKpbpSBP5gb
HC8STZQJYLiJrobuiimoKg8unbCEcFU1YcWo4C6LxcdRsLuJQRrEhoCBI0HeQLgJ3rKIKKOgjIKL
KaLyuM48SOFKAPOJC6sYkrarKrMdrNDQURi2YIVDfFCngs9cqHtEKNr5k5drz35Y/esr9EzGSM7o
JzJFJ2bt+Hk7OWP0LZYmFu3RWTNxye5Nm11Zo3+hYiSzf+LG42LREw2v1IxfNydWKl+/XNO/YsaX
wkOTod4LZa9Ml55YLOudCw3N2Imlqvha9eiKMXap8szk2j8+fVQofuLw8T1vrjkTV4yxa+XJNSs1
bwyc17rOG68u0J6M3T9TnFyw+lat5FrN6UzV6bc/+fQzIxDYLuiF0Vf3/O5K1dkr4cGrdk+2IjlH
EzNm71I4sRROzdojk+HkbEnXktGXoYmpA8lzf765UqiorOPOIydrxz+sHbppDq9VjE4X985bXVmn
L10yOFk6PF3es1DWvVScnA4lL5R0L/6sb+r3f7ikyer2XUW7ot1Vox/vPf1BDfgnbaeWre5sOHGx
rO+d0u750u5lK7FUMzRXOZwp7V+Jnbm09pd/PSUEHy7UhWh35fjNirdu1E5crh5YLu2/zMw0k++U
nZoqO7EYSmSKUnNWarGi/3LV4DLz8EfvTw5k//7ILk34aVf1m9eq317eM/Su3bVqJpaLRxbKBmft
7kx5fKVseKZo4Fy4a46efNfuZ1VoNjqU+evfPiIFWmFrz56J96on/lR++npZfJkOzVQOpu3e5eJ4
lg7NVw9O2T2Lob4sTS4YrJT1zJR3zYVf6/9eoaa09VWdvlmd+njP2A37zBI9M+/0L5WfWipJXLQS
k+HeBevkqplaCZ+Zs8fSVb2Z5X9+pmjqw7uKClrjlWM3nZFPas/eqBjPWgOLdmLF6p01+i+E+qZL
Ty2F+1bp4KI5MkeTmRcnri2Nj+1Ute2FutgSrx7/eN/Eh3tez9oj6VDPqhG/agxm7OFpM5k2Esy0
tNF/jvZPhU8s/ertzEhPXNCUh3YxG+O73/qA/ua9yrFlu3fN7F8LDWdDo3N2PGMnl+3UXNnQVKiX
1bEFeir9g67J/u6+R3c9QQq1p1oStRNX7DeuVo7fKB+4Xj2ybI7NlCTmjOOZcPdCODFlJdNaT9bs
XnYG5ipTfxzo++XjuxhTkSSsdQbsZYIC1DqAI4VQCZNdRhRSADsBNBBNWWozTNA0uMI6QkNHGBGh
JEIDZRTcd/ByATnOS4qJwhJeCWJGOx5gW176YwGBHDdgioBCDAmghgGmLKKqBlQ5jQGd5SIn626s
10wHqg27xcaBKxJiIAd+DcGH4qQS1igZa6+NVjhu1XJBVUMrODwKWKN4sTKRAnDsstAKHf2jwF1q
ERtPEcCrJqoaBBhUHGIEsHsQVdXd7i7aY1+XL5ge9InAQQDt0S1Q9CyEfb4WAXSU5mGphd0FREXZ
G5A5gaKwAQ2DAoth6tkSDMg2auw/SUZVdWAQQR1mAVUN1JAzCN0rHwaul43LpOGkhkclONo7np8l
rxHwYsNwSzf04qWbF2EeJLY3Dis0yHpYpaPMXQ74mSnGWANUzHVVWayqUPx56YRYxfVi8rDcOtqu
YbCp4B9YUyQXbowFcVKKVVX1GISOtUZF93L+QkFD172qVxYlVJ5CtKhc+QAxWKZgJLD1kmVXVcnB
WHXQqxSXwCRUgU8osbWgIkZvbn7xWhxAtiJ71RCdCfTHgbkMG2OVIiXABhd2HW5h0BoYkDqmp+1m
gSrhFEEMUZVQh0gWOjNIJBE9rMOvrqo6ppUDPjSCWOUpBm0Qgz8Ik7ojB3OCFskgaMhcZ4JboMHT
ilMUhAu3uPNeOIU7joExJt9CCSoD02Crw6kUNeA0DryqoaomrCZgFKdMJoQ3dHcwEiSPLQRctAGd
TYxDXFxYd4xMjSeIitmt4C2kvTJyUhPDGHIQQ52FHB8ZUm+dvOvgNx3xkDL3ouaSgNxJw7RC6gpp
JSEZM7FBcVIK8AWTiqi84sGOjiNTFyFd5UVv64CcENZCRfKOWen6WfBkFJfOr+9FQEbDCOfmCEAg
mSGigwGgQZYFMcw4XEAAmNCdBS141cJICHg8mgetidkku5sAtu6QMpYbtDwyXc7uuBgFPuSLEnB3
JzAOYgvAKWaKhhyVWU1tACtIfw3TSvTSioJXmUPAURaqGoTFZfjG6xeoqmEYi97+yfHAHHdUMIXu
lRvJdZ1bC0wPvjicKuhnji2GB3oKaMh2h7CUKG/gxoJBE9MT1l320kokQYqqmghWCvB81gtQy8Fq
JXoISbE22TipiMvNabDqAT7HKMnl55w83wpI6pnDV0fG2BAgB5l6mgoJwsZhE2noOr7HZb4Fnu/c
ilVQ1YbEpxhIhoZBy/0sewGpuVs91gDX6bgFoO5O0SUDtksG3KQOeJtIDcGBV+H1bQIvbbglCYgY
omiChuvC6inTkBVTSCuMVQZfQUQVF5owlw3uMQ5fPKmDSA8w8d0Nq4XZzUMU3Quz2+4uGdQQ3ErE
y6iJWexWPcmD3CBGFEdaNq8DvzI9NRFYCjhTzNlcNsaea2hu64j4H9jsr6xlwb2bbbOKWNHoyHvk
AwfoHZ1t7fBoasMJwx1P132Pn+6XM/Ma+JZwOGeLcWvgK6uPdsDGuxL8tG8zD2ziU7x0sD3aHiE7
Yviv73ZHfWvkIPNbQ6TZ9wiubZOL68sjseVROjYOA1NtuBp5PtqZe7Gu6WgnPhtoqG9uBqMaI88V
lB5uDBWIcGR5iJlSJAgi+9//WqCn66P82XRbDA7DWlsjsQJ4FPFC3ilN3bFoZ0MTSHpf+Z0nUGPU
7i2o22/s/2FdEeEf62M/4uZj1LhjfP4AvmegvsVra2+PND6w7cFnBLFYllpibW2d4Y6maGcT057w
q0oLmNQcIdvhgtDy4DPV3G/b6hpi0fZOPGkicPB6NEL2NHQSUSKiUhQQi0SWXIKgbPsvUEsDBBQA
AAAIABh8TDEIqXePUAgAAMIYAAAbAAAAZ2VudG9vX3gxMF95MTBfV0hJVEUuc2NyaXB01VnNbiPH
ET4mEKAn8KWBADnE3s38ckjF2RWHnPHCm9gGNrdFEMgStStEIhcSZTiHXPMkueUZfPYpz5CbY5Ec
9kx3zx8pkanu6RoOs9ZaCx4MU43BsKf/qur7vqoRXxxfnr0Zk6vx0eV4cEJGQ/Kn6wH5/HhMTIuY
7oFtHrg2sQzD2fvgpWH+zrYuLkej8eHV67Px68HRCal6nYur46Ph+YD8SnYY6tvZxdGrAXn0NTEN
8uhv8vqEDK/Pzx+Pz073965eH5B61AE5Hl1cHA1PyHA0Jqej6+HJ/nvt98HL5z+25S9/5POL3+66
wvWuC1ztusDlrgvs7IPzXRcY7brA8a4LHP3kPtg5Cl/uusDZrgsMf3If7O89f/bFRmL2915eHQ0H
Z385GXx5/erP5MVgPD4bviLqKzkffDU4J6NT8ub8+mo8+CsZj4jxuFri8zeDIUjjyeCrs2NYpup8
RP4QfHZAXI/416eng8sD8puPHv/6Q+uPf//Xt1EaZYt8tZrcRN99P/3u5r/T6XwWzaZTGkfzJEkE
EwlLmBBccCqS/T2rS6wesQJitYjlE9siTp94fdL1Sc8jQZ+Errq2SNgloUfCQLagS4KO7A9aJGiT
wFc30OOpe2gwpqcG9LAnJKGhemAFE5tDQktdTXVj4ldotr7KiWrAfdY/djr/+Oc3VOSivE2Xa/jw
lE0pn0XzyTSaRNNZRCllTPCYM8pEnOYsTWgSg/UBsR1id0i7RboO8fu4m6euHRL2pANCn4Rho9mq
00KzbLS1coyv7rvq6uOjUDdpn4X2GepqYb+jely1u6VuTPXIlP33WW9//PTf/5kk+SJdrMq79Wq9
jvl0BgbHFBwQzaI4TuCPZzSaJjzlLBVZnvM039+zbWL3iB2SXp/0Q3lkuZWnIu2qa6B80FdGB2i9
OrW2rDbLUDe1G/r6Xg42tAX6akswycHKPbKzcqeNRjsKbZ5qtvbHlvWm6dTme4dBAoi/XS/W6zsZ
+/Wci7n80Onk+3kSz+ZRzOMkmTDORJpzOskykVD2tBeki7vidr3EiTGgIhU3lM7ofBKnN/MZS/g0
TqI4YTShkjGwEKDG9ohjEEfFZ0OMnnJOF73U34ZMqHCvMC3902yhcmZXESnQXpLeC9CBNnrPVDGy
0FcOgkWRRD5qqeYgcCwZXMdWR60CCgu28aj+vUeV2yEAq4hIbocY4lAjvUKrfKTYrgmssFEdWJ/f
RIybmi4bYtemGfeH+LDXz29Xxd36dq0/5aKcJCyiIGgxpdENwJsJmjA2F6xg8yjlNBWz+GM/yJbr
5sR0kbMsBQ2IGIsZMENAbHkqBHTGGYPogjJSkEUZX/Cbg5ENlN8qR/XeclfdOsrJHaSSpam/0TsD
3diXftswQkVTj1QKIZFQiWNbf620WPutCkpPTgcKO5YKcQtj+pCjuohbS010NyIkN6pUysCrgWKN
0dTEdJCtrhYBeW81yI5SXpm2HWLPrEP8pPcsB/m6XdWRyous4FywJEkhTHOIJ09TWqYpz2NRJBno
GHSJwyDMlncQ4jucuIAkkBZcsjiOBZfQ4ILOM5pyCHMCPE7SOaX+p8/zpdxxiROXWTbjIuZpxAFC
MwrwiGWyjCggRG4fx2XMONA/UNhoo1QGmCiCdzrcU3FpqauNLLAQGO7Gz5UmaPdWfq7c29H3stND
97ZRhWr9rCc6WqacFmKj38DG26yvW7eR+lx94Cb99VGrXZoYtjWMJXpbaIXdwInZEAFltRbAUGG4
SxxfmeZve9W//6i+Fj3JBRshamPVYm+4o09e49nQOlmFQPO0BnbT+dXgDtLB3oax1XZrGP++9wko
ValyihacvBT5QpRpwlkscsqLpGBRUsQ0ZlkeZ3kKiObiaT+QaFxtlGpxB1VMCXJGOYuYyESU5GkE
CYiyOWQyXsRQzwjxxIeJWxK3vluyDNbNJ7MshiKHQg5M2ZxCXy7zP+wmWMaf9j+FHZvEWd8us7zM
gAGyWJIHTmBkmkvow15ZIRif88wPwcb11sTVKktLKCzhqWA5aCkosVRmASTNeJnFUG5wAcTpK+J4
DVHtvJWM3m5VjutgXdbF0szF4sHCaHoIrYoUba3A+t5A6FpYYBh44zaYpVAk86ajRLWJxqoEegfH
u0irCjmdjYbrg1moro7O1Pp4nkZsnRMrNEoe1ene1laEdf2oaCXlyGocNXyY/odqjI/eqP3gqVKk
p3oMTEkGkroiu4u0ChtzPQxH7caa+JYWKO3VbsOrD5GjyhAfN+pgkWNsdEknrCYkzMbuLlpXk7r2
YSXIjvawLtJayqWtBlbDBx9VvSBVOVEe1dI6U6+s9/IQA+4m6TeLBH286vCVvHd0UDaFsfLwvYVT
GHySbVN1USz5sqQMXoDgTTCFdyK4iTm8GbI8E0WRi3wpRHkYSnEoGxPvVstlDs/zvFiKRcnzMsmK
RGRcgIAB6TnUxnnx85IjGV9Xhbj1PiHuqmG+cr6vir0QA2ohxqqguxhWp/HIQJiZGHcPUdFWzUOh
8xHAHZXHW9vE6TzgqH3Mnj6WH22kqodWOJjubSSXiaQwEaI2muM2DPQ0x7VkeZpH95fx/WdVjqsj
VZZryJUJ4C5bZFmWpLcQFwbgLDKWFnmRQ+DonHf7/1/j3a7WRVkIqOYXBbwLCJFmOYQ6FXmRpAuJ
KJHN4+LnhUZDaWP7hzLOO0LcUS1sZFKzgaWWCm4LW1Vn9hpVmdWAbjW+AmobA+pt1CnAd1jHVEd9
36qyh+a01WnbCKoK1V3s72LedFD6vAbkXGRHG83pbicahVh5TkOOec9/5A++Phvv7+29qH6ZOBkN
Bz/ws4R1AFFSP0v8D1BLAwQUAAAACAC9e0wx1ldYhyYiAAD+9QAAIQAAAGdlbnRvb194MTBfeTEw
X1dISVRFX0RFQlVHLnNjcmlwdOxd63PbOJL/eFNTNX/BfsHUVN0oU3rw/dCtc+f4kfGNHbssZ5NU
bspFkaDNjUTqSMqO96/fboCUCJB6+JFNnKVLOyuyG41Go9H4dRNiRn4azXKS5V6a04AkMbmYU3Lq
50TViGoONWuouURTFOPHv3xU1P/StWmaJPn/ZNdRfk29gPC7xjTzvXhCyS94Q2FX0ZRe/UB+WHyi
qXdFSe8zURXSu8P/vvzv/+MkEkeT/t+jG/ga/vRjdj0kXAA0GBI/mU69OCBxkpMwmcfBT/dS5S8f
/1gIE3sveg1/WP/3H4PHtZ8/rnn2uObp45r3H9f8kaabPK75Dxuag2s8Awlf14bJ45r7j2vufdWx
P9Ly48c1jx7XPP6qY//pxz9+P1tG8Z9+/Jh5MY0uAzqeX/1JRjTPo/iKsEsyoTd0QpKQzCbzLKef
SJ7AltOHRsWNP8lZQRl7/icKm8HflL5h91S1S2awc2FblN8ryBlR+0pfNaoSXv5SCumNdt8ckFeF
JD+Jw+hqnnp5BLtfGE3oX6Vmh0lK5hklt7DPkOMT19HVgTbQQZcMtsy3o1dsnDFNM6mleCmLpZ5/
DQa4iXxKYkpBaS8HU3hZTvLbhEyimGZDuVGPfJxn4z/JDaiepL2jfYJb4yxNgrmfw2Wdv+iB/1/s
TWvDi/q0DxtrurBxR/ms2K/0F+TthaoNVGugGeyeotov5MZcG96AcB6ZpVBgAP8/AO7CVjJXUrtT
tJtEY2g1HI/HwyAIZKbba5pSAkQSZQRgAAHmeD4d05QZBlqwu6WZGUWWMfU+UZLNQU5+DVNwl8zZ
fKfk2oM58X2aZeiRA7CyPwD5OIoBdDmo6yOL9oIgQr/yJpM7FExg8CSbUT8K70iWTClJZkiXPYfc
eul0PuuSyWkYnsYHcQBfvekMrjb0iM7qzfMkoDn1mUvDUBpn7UHzVJ82kkXT2eRumy4aGkchM8ut
F+fEKywT+aUu4zmbDpiIG5i8hEQB9Yg3TuA2zOqKAcQwdhSNDXHZcgfqFnqSjObl6tmwdrb3bTT4
hrG+Ob04GEozAy6beSHtEvCzKEdluQ9HcZjgjaskl8XwvzBNpoyTBZ/5OLsDhmmfHDFr/ppSBpbn
GYbYBkPxP0GXLjPXydvRBTe2l+cQnmjAlwQf5goxxYoBVXqzJM27i1XEJRVzSoN+v3+P+Fj3n5h+
LjXhphIGUOWEnqrca3qpuyRfjiweooFnKYhI5hmzNI3zVHZ0WUAGuwTEdVyssCuFxAtziCSfP38G
x/OzLlFIEGXeeFJMdUi9HCKPKIUrUS54oiuKQN+nfhLg1BZ8LxsjQ3NEITOaRkkALob6JLBVokpT
6sGYYYFxpkZtivaquV6XJgmyKmWHsNmBg6D2PUhAc7DyPM6TOfpdl3lwyVgYNalFP0xYceO/9CeJ
HOZKK5YRlKgbrFgyrlV+lcPABpHfUu8TX8AMN7GkGtZExrYAuWHn3e75m6M3r4fYIqW/MvtHMXgL
7BYk9WKQAJbwP/3888/ytivLKr01TtIpNMbQTbyUemubFeMG/WDg78kGHyvY1oj4sJ2ID+t9gw0F
Rp8BrqOxH9Gssct85m2jdcG2RsRGrQu2zVrH9Aow5M0KhYG6jcIF2xoRGxUu2O7lxah/VmBydCTf
g12zgMRZnkYz8iXcmPTUYoHjPj2eR5Mcmm7ptKNrD4f9AYRsdLuSd5UfbC2rwrtqiraWVeG911zl
aN8bmuZ8yZdet93W0mxOLu9NKWqTh0ns99U+g6g/SGmWJwBU/MRLM9HhAi/fKnL5iFD2vMk+8G9S
ucp7L33RM70Jc+dcVDMFGIo52jaqgoS9StMNyorca9XlK/dTNJuhgNvrZCIvXtq8nWObe6gksd9D
JwBNEcxzCKbaoNkvTc4AGDlI4uatHfs4RLlbKI9867UOsOCS8nwRvHM+YWUFtpKwj9vrSHSAtSq9
Y9xb6sWYN5s0pbOJ55ch+soDDHfjTeY042VxEsxTINZsukHjlAaXTBbZGLFK1kY5VymlMZe0Sc6S
tVHSGMZUqLRJ0oL1XmsajekFf4cbpTEDGno44VfedOoVVt1mXYNFXrMm5Z/a3zDnZYvVNqwK3Chu
2WKlKQUFNwpctFihoHd3P3mLFveaIdglaIxbGbk42yWdGCSdcXKR02WA/Cd3NUBRJgzlfI4p5KAR
pqeQYi8yUcx+eJ5dwJSc7ZqysBKccE22cQfOiSpvsMqC8V5WwXIFhCQfxpPRSl2r11DWk9tuU91Z
Vc1YqF9WWKA72KVqRY/NkwrzgrHUA9hyW0jr8jyJV1c5IeMpfa34ubGmxKsWpIOqAR76PA7D0NdN
pQsuFE1evBAHxcYilH+HVYbqYMmwYbxY8TjaLxbCUBr+NAmwpn2T9hlRqdKKVLpsqJpZlVqm/QUV
sv8GKs9oh+SOCm0FSDQEKC5YZwkraI243OD7pJHINlquUjOR7WIycQEVswaxgMwvP5eRRLIR0u7W
0DIOnS/vhrBJVIkAiFcKRdoqoUhbKRRw/0qhSFslFGkrhcJWQIqdFxuKRBbYS7JMxCC9aNokFr0E
q08rxBbkRrFl0yaxi9A/xMCv1AUXDHUyE102b2rt3a0h95r+qgwQGGA9XyYzGvPFLyz13WqhsN8X
HiztYW6KsQ1BAdZ6x3qP1XqVrbjUrbjsrbjMJ5SlPyHXdmPczl7GE1piO1nWE1p1Ky5lO67wCbme
0l7aOi5DUYBLVZS1s73gWus5W3KZDnBpG6y64HK24nK34Vq/OhZca22/4FrrhXqIllDM9fNYcFnr
uYwx9gjLca3nlFxqsIZLtRSL+YS1brZLLnUtl2K4Ifcvby2X56K9NGWtvRZc632i5FrvEyXXOkss
uYSHSYc87S5Qc05eFs+qYZTwP1fAg39jjxzJ0f4Oitt1u+SMP3jkt0D0QZUdxETJ5T7btNiRg8/r
qUPCawDsShsIrsv5YPvmjz3Jf5bPPKHrIeHq9Ooq7JcHBzJ2RhDzFrTGS6HBX3m/fUm7yyiOchDQ
MdQuN1+3pzbB73e7h0wF/mc1WIwn6vgkMgGMvefFUh3jePfkrDe62L14O6pIEnzx/GB0cHFx9OY1
fHt9NLo4OB91JHVKhovfD8jJ0WiPHA1OBWRd3iwe6DGR2J9lddkiwP+6YiSrVLHwWAnL0tjjZxhJ
lfHlAM8xDvr4IGvABth7o2qG8vbyONo/0JW+702EIaOBRzQfQQ535qUgFTTKOsJ4fiO/758dDYnT
l2zxG3kPhB0VkyJk2Wng+LDgOIli+P5hxzZFDswvzqLPdDLC3G3H1LrkGFIAyEnguzC2lwRu9jhb
tUtR3uF8MiGjnM7Yg7QRZBS4nlgrslPMqtgCmUfRP2jnLKVg0xfAphrFORVXkWyBlsJCmD+fsPnI
JBD4G9P+mMZX+fWOqphuMZ5zyJT2kkmS7uj13jPoHXp1XTb3hoULG88JGDZ8o4ZksLN9suNaClNQ
92UFGVlXHNVCBtuxlBddViEl2MsO6wMvMy2lNzu6JraeTGhcqj0R1e6S/8/9ON9xuuQ6ZF9kR3pN
85O94z/2o5sooKnsRUdxTq8KJ76IwH932XLESSGdpf90mYgdA7/Lti8eK73GBOHs3cn+PL/bu/Mn
9Pfo6lpk3ZunKY1zgsJIoRD0xKTWHODk9OL0vFdIz4YEROMMwEDh2+X+24sPcKmGYqPDw9JvQK7m
QBT+CBPm/MmdTOWXLr/UVLHt2fXdq7ucZpCh7BCrRkN/4TRp6i+S3JvwljvElqbu7HhHc80u8RMa
hmyuNYwlGTgrrXndmTfP6HE0jdD+GleWirqH5eUW8YIV1uXIjWnUFc33vJkUUUa8YsQOp6TTermk
CNdDwiKYEDpZKQQoPKoNeFSrchxOvKuMJc+N8TtIb9jzfVGhQtksT2aoWyMRCRB/Oi+KKhOGoJmX
ftpRGpgb+uAFpWFRzdkhL4UhCEGZHUMAy12WBcoOrz9RwwKfFFcF48VklfSIiBmqXDyy8cXDUmNe
piQdXO6G4lrSStu7xhmafFT+7BaFbK0e20smdRsmbRsmfTVTY94uJfF4TvQUTEFLJFUzFJu5hvli
2b5oPjHv/7fHXMa3hbkkdd6OkLwAVoWvPxJ1rQthWPTGlQwLWV/RJk1mRxDgasEEt8kjPNVTp56d
HSP4EJbu8dlu7d4rxmcKOcs4hU0wj/GEqYKbQJyneP63KTplPIAfxDd15UbeDV2hXXCLwXUBojDr
3n5ov2EMuonoLYvheIYRZ+nnKgvHA3tHo2NvCvYWZxgElBHMRzzC4miVoQQHU28GYQsxH27hihlQ
21jFpy75LHUNn1bhMyW+xd4BkaW+eZTgWW2Iehw9KyWUbWJh8Nk2V6HnLRbPiJ13w4Ecs3OEwnb6
jj096CEaS8sfbm2WLywSlLoQkMxmooDgNixdxihcBu4xBHNGU8Q5zI9Jtc3F0ckBgU7PL6p3U+oB
hLvEg9Po4uWvzDoQ0z7R4MVq1iFjRQNAOnB+sLvPDoWQjqo4OhmjJkLj8TzkHg5T7Rm6jHFxqsGR
8URZfbKXWwzDQ1US8ELETyqJnASJDi4Qqn50BrhR8uO27IwocYbEKlBrF9xImt2VzdQh0ZfNxFa/
sD+yu/+/eEgXJ5l09k53z0cHLzjplyr3SZInKXdQlHXifT5JbuhoRmmwo/R1C+4tsfCOqpp2lyc1
O5KyDGavRNfoIiZ+Y4mPw/ZZlg258NUxBRfBMV8eHr7D6AvI4CXbBWvm5vHkGMNilsxTn8pLc4+f
Ealm1yM8oTYU2Uo4jmFYCmmYt3KkriqavHhLiI8YX56438gpxOso7r/HtvIWsm1Krq4KKtoyqqzK
yflk3j8ph4GuycuZGSpdi2KfJjd3NZ6b11LfL5mb266tLJJz7q02A36S4TD7Nlyuoqo7jdm5ZtkO
qy9Yjidm57yXbJGeS9b4Ktm5VmTnaiU715uy86WxVNU1zYW1NFpaa6w3WMM2HIdZKzCarWVonMGk
VLRW0c3Tm+spSg1l9BWZH19qUF1NLDUoQqnBlzoUSw2qVA6Xyg1SeBPKDaqjW6pkpbPjHdVQqiUH
pt0WJQfWrFJ0MIwnKjqwPP0VhdBax7b7yW08SbygOCuLQU5CmefQMMP0YH8OYGlMQzxXingCfQFx
g7A1oPGH5P17otrE0oimEIA3cAkfRSdEMYpbqkkMn2ghfoePKEIFEXjfIIpJFIsodsEGH3ZLYxfq
8m5NhAYiNJeYHpJ06NUhio+9MhF6KYLrYhM9JGEoidC5FkBVXWIZ5XedaAap9KyWnwYtDBBhsPva
gh/aUzLWmQi/oj98DAMFiSJMrkXoE5MSyjnBag6BgIsXlkVUi7iqYA5RhAUiLLACBYclgYo/NDWg
iUIchQ/EKJqNF7p4kgi7mJHyo1e+C4TqR/a1owzda/fGiyZYajmK9893T0SXZCdroox4JZMko7Hq
pDZVnarLfNUqL7BKA1LZAwdnwQ4fLZBf+cnZHvstjdJPvdtfq8wvyXu2yYMeH1CZgM5wM7W2FJjd
erOHCcUToyjikh1GgW1JH6iW7ugDyzR1Ab7wM6ELXsZqmYpS52RnPkVGw21i3Ht73jnvvu6+eoHR
yVJtv6MZrmm9wE3OUcKwo+uKprNLOzCVjq4ptb3/4vSU7O+e/8EQ63wmEhe/8ppghMTMBiSFIS3g
rX54eHgfcWuJkGL33hW/ClWzn38WsvAWflZajFr4WfXRFn628NNt4ee3Bj8VF+EngBDAa88dfuoa
8Z3iu2YRw3mW8NNm8FMzS/jprIGffgs/V6FF9UvAz4cJleEnx57bIlAGP1Vd2QaEMgTqOpthqBmq
BsBQ3VAY7vTDsdkxddXmMDR0HbUD6sGlFFafHoa+Oj96/fsF4wE7zcUHrw/o0TIhYVvZYwtfW/ja
wtcWvrbw9TuBr14BX5XnXz3lVP5d9cnYen7wFVraIcJXQK0cvpr16qm90GXcwtdVaFP7EvD1YUIf
B185cl3B3Yhfbd3kIFYYmQhfAzvsaLqrmxy+0kDtmJpr8MuxN6Ydw3YU+WjiN1NFvX9fLXBtgWsL
XFvg2gLX7wS4Kt8ncNVURICVnp8HcPUdVBuaBQYbu0EsZ1FALoGrWVFSFNEC1wXO1L8EcH2Y0EcC
13XcMnBlmNUxbXMTcPV9HYCrbdgcuAa2CcDVdPll4GqAY03TMZ9f3bWFry18beFrC19b+Lpk/o7h
6/g7rbuGRPWeZd2Vn1p1lKLuqtbrrktQ2tZdV6JN40vA14cJ/VfDV9u1NIZhhZFJ8NV0Ab5ahlrU
XQ0P4KujFqcIXI92TOjymz292gLXFrguDNcC1xa4tsC1rbt+H3VXBRWv9PzM6q7Gmrrr8sCA1QLX
VTjT/BLA9WFC/5XAlWFWzXI2AdexNwbgalhl3dUKsO7quLzuqup2B3oy3a8IXO8vbmnnmL8qQNNX
MeBElLYVear2j5uENE+QyFOZlrhRE3HegAHnrMqy6q0L9Z1DfAPFKey4BxeLd1CQbd5AAXfKV1DY
miK8gsK0Ba3WvXZCZy+bkF47oS1eO2EIcHPjWyce/qYMQ3mUxk/yooxTwBQ0b3gj0LeVHClCbiTK
a3Ojqt3a3KjNjdrc6CvlRqN+cFu+HqgBBC6Jq8jrECYjr0aYD8jLjO8tL4OPZpPAafMyh7j+v8d5
mOZECMDqA99jcU6D0XzKViiECPwHZnfE9ymykIwssAg1TW/keQWomUmB7UszrUYe6Oi0QPfKQDUH
ulrr5ZTB9gYqyj/leLyBen7wGmKZzgK0+O8LFBR3JcWrU9rAwqhPHljC8vPMAovpE5ViT4G/puAj
i/ieAsvDfkxcCSy6aTi6oWllXNANMXuthBjdMS3HrrDaTi0SFJFGd1VDM0x3werotqTAMuDYA3GV
C/FGJgrhRiZWo43dQHBXEbwaoQ01jPrkocYuP88m1OgUm+HRCA97gnxWDjXLAGJ+x6HmYT/8qoQa
VbEM1zHVMiioiiHUgqpoRncsRzGcBatuii+gXoYaCDSqq2jKktU1JAW+8VDTUAPbVLF8vXv05r7v
zP2+KpZSyvl1SpavPXlv2OqVvmWVgUhlhnWv8133Mt/2Vb5t/bStn7b107Z+imq3Z0u+5bMlD8X/
6tcrNXD8HxQ1TK1ew1QXumjPHv+vrfs/4FwJ/tPODyx/nuy+r7701jDMjmZaVnHcwnLDjmm4Bn/b
WOD5Rse0FEVKwjnmHmMoEP+puYLi/ynHqoIQ1AgtmKq0GLVgqtK6BVMtmGrBVAumvhaY0pTnAqZ4
MbUwXyOYWr6Y9vk/t/kiYOphj3xEMBXCX4cdjOXoyVGsDlwpGr8c+wqAKQBbK8GUVORtwdRSbAum
WjBVs0YLplow1YKpZwGmVOXZVKZYM2/N6bolRHr+p+u+CJh62ENtEUz5vuN0TE23lKIy5blYmTLL
ypSK72NyNPF9TFUwpRkNlBZMtWCqBVMtmGrBVAumRBHPCkw5z6syNS4f89F1lSmjBVNNYOphb9iU
K1O+3bFMwy4f86kIphyluHQdBcCUJe2SAphSGigtmGrBVAumWjDVgqkWTIkinhWYMp5XZUor38fT
8Jhv+bvP9jFfI5h62PseRTBFbSXsmK5q8lctBrAzApgytPKpn4uVKcOQFuETgqnaWflNP2xgb7bp
HB69KV7D0r6K5Wv8rmEfXLyI0tLPG0R/DWHr6gXAXPPV+6BobRWMXkLZBpbHwWhTERxDANEG/kp6
2a8os8XQzxBDKyWG1jaB6G8Wd+qOKeJOVcCdjoQdBdyp6UaNukSdujT/AuzUNMOSG/+zvSvZbSM5
w3cDfoK5VDCHOMDIYG9ktxLZ5ta24mWMkSeDwRwMmqItAloISh6P77nlSXLMI+QFgjxCLklgi2Qv
1RsXiflr+ZvVFMXxeDyLEVHldqv776p/q+//2EU1H2wZmvM+rFPXC6Sz5PxCpFP/UKTTkOyjSDo5
g/xxpFP88kNIJwg//7WQTsAWXSfsGrtoQslZRzrLNmkJsfcgnbv86eV6i5gGf3o5Xw5dfnr57qXu
/PhI52Xlms8QVbBIsL66t/2kucSwVOmrvxz96RjWlW9/Fvb61V73pPPO9PUVk77ir1f89Yq/XvHX
j4O/Gh/wpqnNdq74K79XKQb7hflrG/mrvo6/fvx/aHppwb5AYD8W2sQtahwpz/5YYczGZS9VCMrx
SbdN2C3TwuT9kLdm5RjiiTOrRvkQj7Z5J2vbysNSVsPjT0/EKtavjIZpzq+VhplOJWdhDNMEC3u+
VMA5y9LKJaFgayUJM7QyQCMIVJ7ZRRLGxzjOOdhyib8iYT8/CdP00oWzCxKmO8WTxbXrkmkuX/xg
S3cslYTpWvndlq61IgkzPgQJ2z5oveg87h+1obZtEp5KO0wV+6l+ob/LudrDVg/p2nJaPeuzLyQA
bx3zTGLVoyjQPjo86bcg0QgKrPjo0K7snWXXQatHShem9bKE9r0S+pLEBUNWY/IqXlqcCA1lIMMm
Pb4Iqgr8uBuvDtspEFdNUMD/N+JaxsEMrouWE1eNOLkVxmriqnPiWnnGmCYTe5/V/hJf7W+TtimJ
q3Zxtf8nvPG60zro7Xe+Ju5+6wWBwkhuWCXyG+AhgC6vdl4efL219JcXSzeB5PGNXre9csWdfVLm
6y32hlGstxfqyRcyW0/2OjxjyeHRq8K3+wFINnrdm98RfDE0XP7wAJN4rUgUCciXx51+oY8tYpVW
Cby+TODRy4Nnnf7nzzl0vXzOIMgwneLHCDmUP+70FZmy4xQJrvpUeDSmWBXUB8NLCcMuCiiVAf2x
VB3UZ9OjjFMUUJUQBleKAn8CTrmrPuJ+WQ3egzSWC+jLSnCPNLpQkvq7XGLV+SdHnLuRCx/fkudZ
bNYawaRWG/H+78iuX7t/7zHZIA+ajzahUwImPu/0N8lvP7v56WfGzp//9g8v8ZJpdj5/+2b47zen
/3nz39PBaDA8ha03HPm+HwVxEAQhjWgUeqF//ZoO+FQnepPoBtuBN06WQWyT1DRSb5KmS9yy3Lo1
4trEbQLzIM0qaTqk2SBNi+/USLPMdyp8v06aTb5t8F/zIy4/Aj2UsJnE1Yhr8a1oOnENflxsdT66
zoQL1uu2lZt/09r8y1//7kVpNJ6lZ3N4xUl46tPB0DsdeG9Hg8HQ970QrPYpGB+FUQbmj0Lf+MPt
f/7rNEynyXQ+OWcX+uFw6PleMAJvDQae7weBH8axNxrQKI5gL01TGqfOHTdMJslsPpnP+XVzP6Le
0Bv63uDtWy8AZw+DEH5OKQ3jJKWjQZLQwKO3Gm4yPRvP5rO5fAU0gW5PA2/gecMgfjs6DQM6DIKR
H8LQXhxFXgQhu1NvprPz8dn8DC+cTMenAR15MAxYNzwNfBhqFPgBXJOFo1ECF9NBACFuEsMiRpXY
NVJ1SF3jLgXfVvjWIW6d7zdYZBfN4kHXWfhYpAwMqIsBFWkgAs1PiZjKeOVx5Ncugmvi1lZC3JQh
hvQzIAld0oB+SnxonetWwwyEzqsyCRetxDtpSPWkDhrXDfNNKuli4gl9+IXMUoubw22RWlmoKj/L
dBDNkL8aDqvTJncR063Kt3XUUCi2pKeLOW/gXHCl39hOnfuzisrjZGECwnW4ZW4xeNMxTFwxqX+Z
N0N2AjtGk1Vvs4w+bGDQXdyubBrvpKy4qIaKiei7qJuFmVAjC/xihK/Tf9oD8g3seBOq8mH3eK+z
W2CCKuDd2Nm++ztS3+vu7zLcY3yW3Djuvjhs7W9pFcBG6QMDh9UQS/RFMJsuhs7ENEdoYeEyiCmC
WefBcTDrG5f4QASzxiSF9dLNrhIQzHqBdlITDA7TUJMZt9DNllnPzpYVtfkkc7Ui1FVMLYe6W3U3
nc4BBnL8SCdZmMQepV4YBZHnhzQIwyiK4zjxgjT0Az+KQy/Yqm+n0/Nsdr64MMsyGtOABokf+p4X
wUWJN4ljmgUx9AloEkWUVht30+ksO5M4x4BncpZEE+oFQ0DHGFAKpKKRl/oxICyUF8CrxPP82v37
fMSFqrMkHdE4iGIoQwxgQ8A1Gob+EJRO4oiCwhPYvd24B3pmio1JNo6zSTKOoW6FSRrQjKZ0SMcA
1GGaBmmSJDGl8W3AyOm56pzp+Zwm0yiceFE4pHFCR2EWDX0K1WAEyBxlAO7QZ+7VHFznZ1PoGTo+
HaUA2wGMFACK+2mSwfBQPcFmcNFt94/swnPlwtkMVM2igPpgShqCGAXVUmZeEEdpxnxFk7p7L53N
M3XE+Vkaj6MI3Ae+SOEH6kAYeD6UnTSJxkmQRklEG817CThHGXGSzcLZxKMZlJEQYg31LYbhwTUU
HDZOE5pNozi7c5eH43wRx7Pz2ZQlQZZNZvFkHKXjIEmhWrFKB1mQ0tCnSUarze0EvJpfNp+PJ/PJ
2TyMx+MUQpqEsA1h6JSNB6HKsjAMPQ8udMWIuaoQl/F4HMfTMfuZQMKBZRSil46hnIL+NMogQtev
McQyOGJVEPXzqboGsSp8ttoIyZbEPwG3suxoiAwlrFEa1isTgd+SsCqQmHWrY9EooYwuzxoNrqqD
qja5AgJe1qtqYzPk3JeIq3HlS3JQAbRSN1NRrIp6GrwTQaNy2/PiYCKZAiU1XgcqqGqdywuvXqxU
eavy1uDdmnzfwBrVUGqppeAwjshcLdCywo9bCi9A0rdA6TIaC0CtE7PG2rJX3bVerctiyHDVwCHE
WEg2VVIgFdbQ8zr6vKGkRxndaCgpUV0IAFthXrWVuNvvkKtlLuZg1AR9cDCgJuojpoCGUTaw1Df4
vrMgO66ODEVkbBmbhbGwuKp5BawVK+AaVWuYHgYyCMGMqhg7HfWxZO5JQmfzBGhgQURuKKNj4KSz
FSKGtq9DgDXFWpytKd5AVzDS2pT+kbCgKd7TFhyKKVPBAOXON3FrKsqXMQHKxKwWVW2+g6p13vIE
sHEiGMhSdYy4rgxqLALKTinJKaehifBiSJ2lw8vSpaaNFMhVcnW9qkJADOegH/LJW1bGzbfI1sSO
hFwLT1UQTxzUvIJdcXPYnLK4qmVlWn2vV6s4DXW+rWKsbUwwC7POwvluKlApCJ6LE8pQpqSDOove
atiJzYll5QJYCVXX4GoDa0StWA5szAeRG1V0eIXvaIgJ+mK6SU1MpSJU0PMlzA2eD6wEWLxalRUE
WKOkaA6+p6mi83XMBAdzqYz+0ZUjuuLwStGfOQDaGB3eZAnIVc0R4B0TIMcxB5vwCefwhW0V09hS
stFQkFM4XEzzqpI/hkStHOWUmz/9b9v7R8ed4q2cJ9sPoeo8ahBtE96KHy/dDGJL68cnRz120+rC
2sPadffCjamPZTX9Afv+cLYC1xfWsC+zfnnM3hBuMz99scoDK3zKDz3tdXsdcqPP/y+cPm4ddp6C
39qd/cLNuaMVB/Pw6BCe8vHFbthQF452vuueqAd39l6e8Pes7db+PjNqt/Ptxq3nu1sbGlvMfAam
bJZKGvwrfpH4V62uuGt91GfLZIeHnf4Ge4v8emn9ZudV96S9xyTxy8CXBB5UHz7e2HlSffLlziYR
H/iDl7a6jweyj+/voHB3tBC8o16vs3v92ifflLTfG/pB/+jo5M7xXvdkD7Qn4qh5wEza75BP2YHS
wSff3Bd+u7bT7nd7J3wNirAl2Zcd8nn7hGg60axN3dm02MJJybz2P1BLAwQUAAAACAB1h00xGvqK
c0kHAAAyEAAAFQAAAGl4cDQyNV94MTBfeTEwLnNjcmlwdIVYWYsUVxR+VBrmNc8HfIkEY+11axQz
dW9VjdMzYzsZJXkKDNrqEO3pbUQJhCDBRHAhhAQGHce4ByLiQsxbEsjivkeSf5Nzzj1V7YM9QjNz
+nLr3vOd7ztL9eyu7ny7D73+XLff3A0LLdixbxHqcy0AFzx/1AtHPRfcJHZq3YWF/ti7rYVWc/3o
5xt7u+Za+5vrgP7PH5jb24QNh8B1YMNh+rsFWov797/fn98zUpvcun2wy35ttJstvG138+D8Llyy
ixtgKt82CmEMenHPnmZ3FNYHm+bfWffeaO/b5R39X570e+cfHc6/+32k5iXgB+BriBJwI/QTPA1+
CrEPCX4yCAOIA9AKTEEGrqcemAziBIIQkhCMCw4EAW3XMZkuqJweKFzwDagMdGaXEzwnJxOfQ9dC
MiNIItpcbSjQ9As6zR7swTBMzuaJiY0qT7ccXs5nV/7ZXCz/MVLzHbo0SOjjFeArug2P9nPyGPHg
1xCBFZCFvDOiRRPQVbisQSf2VoVmapGpFIxHbkWgCll12O9AoLsCPWC4uRwWgHHosQwSVWEchmaq
8dH4zM5P9PgXF/TkykszcfHeSC1ABwvaFcQQuhCi7zk5h1+VA6nPtmY0AV2JoFO8NZEgp+JsyG4Z
MXFVi1voty+h9yCV0KuSEAyCERZiZtoX01SUDkPT+rRjuguL9caRy3njwosP8st3R2pRDpGG2CVP
Yw8iFBRykxJEhddHTFVBsDKfHMGvuGiUxDuRyLJb1gwqeSEa5CYtTRQgM6YZjZFVYwnBE0h/uehP
y4Z8KJr2Qj/tdw5ONY5emZi5dC8dP/PbSC12GEFAYaDEwL+IgAnDO9OYyEDO0pD4wD02cNYBFIdj
NYXA0G8TyqpfASPTq7hhVVI2GZshspoJ0b7wyOfqyMIdhqbTWdzS6y7q7cd+3Fq/+MhMf38f0biM
IOREYXqIGw9C9A9FhQgUUUXqylhpGSWAkQxBIRkjNIVVOMuKQKGXxCJ55RIEhzeU7GKGuHYvQSiz
SUuUguFo2v2821lMZ776yRRLzz4eP/3ConGYm5ChMDKMGfKhYkgNI4hIUhkuKuZGk+ocwpmgh/FA
HImNNynNF8ZK9SRMCCOP2W/XskD6S4WxpCpklEJMtBmKptvp1xGRmf36umms/Pswu/QM0VgEAREw
QOZTHVOK0pbQFFwFFPGA0ULVZa71ENPJxjBm1WtrlpmNpb6C4DIhoZiBFRIh11LILHkSBDqssFEa
zk2n0en0xhvHbn658+yLG/m5vytuXHJZVOeTR5Q3CWleBVTokATkAwNKVcARQni5qq+ORNZ6SH77
CaeFETOtcoG4UfYEkmJRnVBlU2TZXaUK9Nq9vNPubZ355sa1mUt3P2v88Bei8RmNz0pzS1uR0qi6
ulSSpAooiDXXN0yWyIoaY2i0RLasAjHnQm5XKcipYCwEmGF5ZTb0tIHNlOHKCbRXw6p5Y9H0x7ad
uL40ceHxzekzL9+IJiCug5zkj0pLklJSXGGpChjqPQ63IR4SrFtGRGdTKBLTFbdcEq7VlB7UBs36
470e68+I6UnAktXQjGGVzhvHb+3beu75f42VV6+jcWBQrbnHkOZ9iBRRherKPMiSMofoqtDjKpAI
IUXlN+lEnKVGKuNM1ZA06y+0q7SX2VUUPatVh2Xrw+p5s9CbxBGxmD1+e2xi+fHRybNPOW8IgU+X
oCFoIq4ChkaRgCNE00xOHYh8wRxyRBxGUiiuIBAaaerkYVn07GRTZkggaJyqC5G8BA1KkSjN34Km
05toYQf98OQdPXv+id529c+q3/DIQnNB2Ukx8KTumHuPnTULnnJySJVkSEaUWQ95nLHTW8wQ2EPF
KVQ2pLKEO4O0SAeFLGWMWhgLZW4Y3j3bna450O7Vp0/e3t648vBB/ep9ngUIjUchi7JSdSm5SmgC
aqOU+TGVZ8x46qRKuqfmgsA6yXlmTIUmJRgVJzk30oLjrayH1IWk0xIhTHTOEGSEJVNb5MMrdHdT
q9WtT5+4dWTy8oO7UxefVBXa49eCnD6EzKLhJqh46qTZTFNZw35Gc0Eh4VQ0Ijhc3lILLOA3ibKH
VPqLWLg8smmu/cXAbyOPhVK3fdYfK2341Nltd/KFVreYPnXz18krj5qN049s97T9JuS8sWgiRlMQ
3XgtoYnJ7YirA0qGIYQ8zlgIHqMpK3Qh6uE+WXVEX4ZVf/Cq4/O0nAqPJTcpF4+3dM9uq5u3DvTG
pk/9fG3qzNPm5NJzRiMIQuYmk/omaCLqN8gHVWWH0WieckjU1FS1VNKYCKlexnyb+sRCLvrzqlWR
oqQQkScvQOXcQPoru/Iqc1qrYxBNXj9+Z7K+9Grv+PmXtqbl8kYwQMMvBXR6TO6TpBKqyhG/BmFF
sP1GsejK1lPWYg6y9dtCKLtQKTorpGCgv/Ktx7w+2ZQj25vf1JvdQ/NrYW31WbOmeWi+P1Kzf2uz
9peA3fjUG34GiEexrvHPAP8DUEsDBBQAAAAIAHWHTTEq6vSBMSEAANntAAAbAAAAaXhwNDI1X3gx
MF95MTBfREVCVUcuc2NyaXB07F3tb9s4k//6YIH9H1gscOsu7ETUu4x179K8Nc8mTRCnT1ssFoEs
UYmeOpJPkpPmPtzffjOk5Ih6sZ002TQ9GUZricPhcDgc/mZEMWMvCWcZSTM3yZhP4ojsJSH5pxsR
ohJFGVJ9SC1CHUv5KYnj7L96URyx18P/3Uw9N5qyXwj7OouTjIy33u+e7+y+/bB/fnL4YXy2+8dI
VX5uqYP/h1fuBSODr4QqZHCL//4n+Qf5B3zfkGg+nW5kYfDzT3+8O7mj/vmnP1M3YuG5zybzi7/I
mGVZGF0Qfkmm7JpNSRyQ2XSeZuwLyWKiKhtQKb/xFznJSyau94VFPvmXsqFbA0r7ZAbdx7rIf5AX
p4RuKBtUL3N480vBZIA9Jm9zTl4cBeHFPHGzEFQYhFP2e6XaXpyQecrITZhdksMjx9boprqpgSwp
6P3D+C3vZ8SStFJTvqyyZa53CQq4Dj1GIsZAaDcDVbhpRrKbmEzDiKXDaqUB+XOeTv4i1yB6nAwO
dogLfZglsT/3Mris0+ctiP8i96rWvXCDbZAA+ljouKd8Vay32mvy4Yyqm9TcVHV+T6HW62plIY2o
QARNlSQXYBP+3wTqXFdVqrh2J683DSdQaziZTIa+71eJbi5ZwggUkjAl2SX8nKfR/GrCEq4YqMHv
FmrmJVUeV+4XRtI58MkuYQhu4zkf74RcujAmnsfSFC1yE7TsbQJ/7MUmNLlZl6fK2vX9EO3KnU5v
kTGBzpN0xrwwuCVpfMVIPMPyquWQGze5ms/6ZHocBMfRbuTDT/dqBlcrWkRjdedZ7LOMedykoSuN
o/agcaoPG0nDq9n0dp0mGiqHAVfLjRtlxM01E3qFLJM5Hw4YiGsYvJiEPnOJO4nhNoxqSwci6Duy
xoo4bYUB9XM5ScqyYvasmDvr2zYqfEVf3x+f7Q4rIwMmm7oB6xOwszBDYYUNh1EQ442LOKuyEZ8g
ia84JXc+80l6CwRXG+SAa/PXBJWA/NDFNihKfCRZ+lxdR+D+hbLdLAP3xHwxJUQ3W9jkMwZEGeB6
0l/MIsEpH1Pmb2xs3MM/1u0nYl8LSYSqpA6UKaGlMvWSVuomKaYj94eo4FkCLOJ5yjXNoiypGnqV
QQqrBPh1nKywKgXEDTLwJF+/fgXD89I+UYgfpu5kmg91wNwMPI/MRQhRTHiiKYpUvsO82Mehzene
NHqGZo9CZiwJYx9MDOWJYalEka6YC32GCSaIGqXJ61NjuSxNHKqiFA3CYgcGgtIPAMVkoOV5lMVz
tLs+t+CCMFdqXPN+iHpw4T/3pnHVzRVaLDwooSu0WBAuFb7NYGCByG6Y+0VMYI6QODKDOZHyJaBa
sfdx6/T9wfv9IdZI2K9c/2EE1gKrBUncCDiAJrwvr169qi67VV6FtUZxcgWV0XUTN2Hu0mp5v0E+
6PgnssLGcrIlLD6vx+LzctvgXYHep4DrWOSFLG1sMpu560idky1hsVLqnGy11BG7AAx53SIwlK4j
cE62hMVKgXOye1kxyp/mmBwNyXNh1cwhcZpBnEGewozJgOYTHNfpyTycZlB1TaMdX7rY7c/AZKXZ
FbRtdrA2rxJt2xCtzatEe6+xylC/1yzJxJQvrG69paVZnYLf+4LVKgurkN9X+hS8/mbC0iwGoOLF
bpLKBue72Vqey0OEsu1Od4B+lchl2nvJi5bpTrk5Z7KYCcBQjNHWERU4bJeqrhBWpl4qrpi5X8LZ
DBncXMbT6uRlzcs51rmHSBXye8gEoCmEcQ5AVSsk+6XJGAAj+3HUvLRjG3vIdw3hkW651DB5PDcR
8SJY53zK0wp8JmEbN5ehbABLRfrIqdeUixOvVmnCZlPXK1z0hQsY7tqdzhmi1TkGu/MECms6XSFx
wvxzzous9FgFaSOfi4SxSHBaxeeOtJHTBPqUi7SK04L0XnMalen6/4YbhTJ9Frg44Bfu1ZWba3Wd
eQ0a2edVig/dWDHmRY12HZYZrmR3V6NVlZKAKxkuarQI6N7ej9+ixr1GCFYJFuFSRs5OtghmIRfZ
KRHTpYD8p7c1QFEEDMV4ThjEoCGGpxBiLyJRjH5EnJ3DlIyvmlVmBTgRkqxjDoISRV6hlQXhvbSC
6QpwSR70J2WlvNagIa1XrbtOdqctm7EQv8iwQHOwStWSHqsHFcYFfakLsOUm59YXcZLIroqCVIT0
teTnypySyFqQHooGeOjrJAgCb2IqfTChcPr6tdwp3hcp/TssE5Q7S4YN/cWMx8FOPhGGle5fxT7m
tK+TDV6olMvyULqoSI20XFqE/XkpRP8NpSKiHZJbJtWVINEQoLiknTtYwWqFdwv8Bmks5AutEKm5
kK9i1cIFVEwb2AIyP/9aeJKKjrDsdklZKqDz+e0QFolyIQDiVqZY1sYUy1qZAu5vZYplbUyxrJUp
LAUkX3mxolzIHXtRXC1EJ72o2sQWrQSzTy1s8+JGtkXVJrYL1z9Ex6/UGecE9WLOuqjeVNu9XVI8
aPqUCcAxwHw+j2csEpNfmupb5UThxob0YGkbY1P0bQgKMNc70QY816usRUXXorLWojIekZf2iFTr
9XE9femPqIn1eJmPqNW1qJT1qIJHpHpMfanLqHRFASqqKEtHe0G11HLWpDJsoFJXaHVBZa9F5axD
tXx2LKiW6n5BtdQKtQA1oRjLxzGnMpdT6RNsEabjUsspqKi/hIqaisltwlw22gUVXUql6E4g7Mtd
SuU6qC9VWaqvBdVymyiolttEQbVME3dU0sOkPRF256g5I28q6LoaBHC6KtHvJLyIYozcy8T/4k8o
ycHOCFvfcvrkRDynFLdAkt0yObAL4/MdvsbxHQpfl5cOiUgZ8Ct1U5PlRDpY7cVTUvIfxSNSaHpI
hDiDugg7xT6DlO9LwTAHlfdGqvC7aHejIt15GIUZMOjptC+03R/QJrT+cWuPiyA+ZoPGRFyPDy5j
gOTbblRJexxuHZ0MxmdbZx/GJU6S6Z7ujnfPzg7e78Ov/YPx2e7puFcRpyA4e7dLjg7G2+Rg81gC
4sXN/PkfZ4ntmWafzxn815EdXynphbtQeFDHn1ZDT8qEbzZxa87mBj732uQdHLynqq58OD8Md3Y1
ZcNzp1KXUcFjlo3B3k7cBLiCRGlP6s9v5N3OycGQ2BsVXfxGPkHBiBoQQyHJqIHi84LiKIzg9+eR
ZcgUGI6chF/ZdIyh3shQ++QQIgYIYeC31Lc3BG4OBFm5SZnf3nw6JeOMzfhztzEEIDj9eC0yykdV
roHE4/B/WO8kYaDT10BG9Xxbi6NUdIGawryZN5/y8UgrmPE3Lv0hiy6yyxFVDCfvzykEVtvxNE5G
Wr31FFqHVh2Hj71u4sTGbQW6Bb+YXlHYyQ4ZOabCBdS8qoC8WFNsaiKBZZvK6z5PqBJsZcTbwMtU
Tdj1SFPl2tMpiwqxp7LYffLfmRdlI7tPLgP+o2pI+yw72j78Yye8Dn2WVK3oIMrYRW7EZyHY7xaf
jjgopHdnP33OYqTj76ru86dQ+xhPnHw82plnt9u33pS9Cy8uZdLteZKwKCPIjOQCQUuca80Ajo7P
jk8HOfd0SIA1jgB0FH6d73w4+wyXNJAr7e0VdgN8VRu88J8wYPZfwsiouHTEpUrluieXt29vM5ZC
QDMiZq0M7UWUVYb+LM7cqag5IlZl6E4OR6pj9IkXsyDgY62iL4GlZMpqVnfizlN2GF6FqH9VCMtk
2YPicg1/wfPwVc+NUdcFy7bdWcWjjMXqxveyJFf17EruroeEezDJdfLMCZQIr7YpvFqZYm/qXqQ8
1m70335yzbcDyALlwqZZPEPZGguxAPxP73WelEIXNHOTLyOlgbihDZF/GubJnxF5I3VBcsp81wJo
7rzIZ/ZEuop5hgcO4nWNFmNbMqgm8CTBhG8T04fH0iKvSXo44XXFMStzbfsSeUz/VP7q55lvte7d
CyK6DpG6DpHWTtQY6FeiftxYegzKYAX0qqmKj13DiPH0QFWBcqrg/z3u0r8v3FUR58MYixfgKrf2
b0Rey9wYWgnOZpjMWkudJJ4dgJOrORRcKg9wI1C99OTkEAGIFIYenmzV7r3ldIYU5kwSWAizCDel
KrgQRFmCW4abPFQqnPhudF0Xbuxesxbp/Bt0sAsghYH6+l37Db3QdchuuB/HbY84Sq/KJAITbB+M
D90r0Lc8wsCg8GEeYhLuS8sEBUC4cmfguBD3cTF1X/X0Njp6R2fQJXRqic6o0C3WD/At9QWkANC0
we8JBK0UcLaJhENoy2hD0GtMnjHfIocdOeRbD6Ul9SN/4DBARJYULwys5i9NEuS6YBDPZjID/yYo
TEbPTQbucRRzwhLEOtyOSbnO2cHRLoFGT8/Kd+9+JcwFQHeOu67R2Iv3HHrg3b4wX9K+TDrkpKgK
CA5Od7d2+I4S0qOKrZEJyiRVnsyDwtYNxw6qiBcHHUwat6MVw363yHBMVK4AFODx41IwV4FFu2cI
V/+0N3GpFDt0+bZSYg+JmSPXPphRZXRbq9Eh0e6qybV+4R+ytfNP3NeLg0x628dbp+Pd16LolzL1
UZzFiTBQ5HXkfj2Kr9l4xpg/UjY0fIp2h4dHlBpWXwQ2o4qwHGq3Imw0EQN/8eDH5ussj4gc+Gkb
kolgn8/39j6i9wVs8IavgjV1C39yiG4xjeeJx6pTc1tsKylH2GPc1DaUyQpIjm644tIwdhVonSpq
dfIWMB9xfnXgfiPH4K/DaOMT1q0uIeuG5bTNqah3XqUtLheDef/AHDq6JDbnaig1LbN9nPjcUUV8
Xgt/nzI+txxLWQTowlotDvwqisMIXHeEiFSzGyN01bRsnmMwbVeO0EUr6SJEr2jjWSJ0NY/QaSlC
15oi9DtlUeoYxkJbKiu0NdEatGHpts215evN2tJVQWAwJmsrb+bx1fUY6YbC+8rE355uoI4qpxsU
Kd3gVRqU0w20kkGvpBwq7k1KOVBbM2lFSyeHI6or5bQDl26NtAOvVko86PojJR54rP6WgWutY9ud
+Caaxq6fb69FJ1dBmadQMcXwYGcOYGnCAtyKiigCbQHRgrQ0oPKH5NMnAqjGVImq4A+4xDsaIYqe
36IG0T2iBvgbvjILCizwvk4UgygmUaycDL78lsov6N3dGgsVWKgOMVws0qBVmygetspZaAULIYtF
tIAEQYWFJqTgL4YSUy9+a0TVSallWnwbpNCBhc7vqwt6qM/IROMsvJL88NV1ZCSzMIQUgUcMRpig
BK3ZBBwuXpgmoSZxqKQOmYUJLHzQAiPqhNgBvoWq83GwFdERPa/mtKrTykek+Gql31JB+Vu1tYMU
zWvr2g2nmGw5iHZOt45kk+SbccKUuAVRhUdj5ok2ZZ7K07xtludYpQGpbIOBc2eHjxfIr2Kz7YC/
fqNsJO7Nr2XiN+QTX+RBjs8ojM9muJiaazJMb9zZw5jiJlNkcc73r8CypG1SU7O1TdMwNAm+iG2k
C1pOahqKUqfk20RlQt1pItz+cNo77e/3375G72SqltUDFKRYr3GRs6nj9TSN2gq/tPyJ09NUahuV
1ezs+JjsbJ3+wRHrfCYXLl4Mm6KHxHgGOAUBy+Gttre3dx92SwshxB58zF8kpemrV1IU3sHPUo1x
Bz/LNtrBzw5+Oh38/D7hp8AhLx1+airx7Py3ahLdfsnwk60DP40OfrahRfoU8PNhTKvwU2DPdREo
h59UU9YBoRyBOvYaMJSqRk/VbdPhuNNXTb9naMVlMJmoPVPXNf3pYejb04P9d2ecBvQ0lx+9dniz
w5sd3uzwZoc3O7z5feNN6pGJ+SLxphUg3jQKvGnW8aaxkEXt8GYbPFSfAm8+jOnfjDctzRCgU+qY
BDeNwPcAbhq6SHP61FMBbpqOzS8nnqX0dFutLWp/Z9azA5od0OyAZgc0O6DZAc3vOrFJEbGVWn5h
iU0jaAea3XP1ongJLtSeAmg+jOnfBzQ5xrQNy1gJNF0bgCYsXwJoKpYGQFMzNXHpUb9nmJruPHte
894tmgbMjtYWO/TaodcOvXbotUOvHXr97tArLxW/wc9R9wdFr5OFLGaHXtvApv4U6PVhTL8NvQrg
2kLdCF8tx1Q5hpV6JsNXWJB6fHnK4asxQfiqicfy3sS1eoZKte92d+j92+qAawdcO+DaAdcOuHbA
9XsGriA+CF5q+YcErlUpOuC6wJnGUwDXhzH9RuC6jLoGXDlmVU17JXBVXQCuVDFz4EptAK6qpYpL
TdF7hg7dekbgen92d3qOxKv4qtZGgANR6FamKes/amLSPEAyTWlYokZJ5HEDAhyzMknbqQb1lUM+
4eEYVtzds8UZD2SdEx7gTnHEg6Uq0hEPhiVJtexYB40f5lA51kFdHOugS3Bz5akODz+JQle+SeJH
OYjiGDAFyxpO3Pm+giNFio1kfl1sVNZbFxt1sVEXGz1TbDTe8G+K43caQOBdYVvxMoTJi9sR5gPi
MvklnG+Oy9Rnj8vgq1rEt7u4bEIsa5247OVvh2kOhACsPvCciFPmj+dXfIaCi8C/+TqSzyvkLhlJ
YGmiltpI8xZQM+cCNA4itQYaaOg4R/fKJjU2NVpr5ZjD9oZS5H8s8HhD6enuPvgyjTto+cj/vMRp
LXHrJc/uWKj9QzqWoPi+DMdiiBc6bECi+E4KtAS1fuSET7tjedjLuiXHohmWYaiGVvgFrfLXNEou
RrNtx9AUZ0FqywfzlTyN5uiGYznKHakcqUsOx9qk9SYLf1MtlNxNtbDsbayGAqetwK0VPD+Gef7c
svIErsYqvi8Gw4h3xyzuZNDVeDVXUxbyx3U1D3tPq+RqqOIYFtWswilQxZJyQSVXQ3WqOpa2QDRU
s2teIHc1VDcty6J3pLr2wlxNQw5sVcZyf+vg/X3PpP2xMpaVkPN5Upb7bnVtWOvI3CLLQCpphmXH
5S47LLc7KrfLn3b50y5/2uVPUexub8n3vLfkofifPvdZZUUO012Ww3z5+H9p3v8B+0rwry0/MP15
tPWpfJqXoQc91XA0Q2y3sAK7ZxiLXcSu7cOlU3nrLcfcE3QF8p9zy0u8v6q+Ki/wawUdmCrVGHdg
qlS7A1MdmOrA1HcMpqjzQ4MpVXkRYCp/buNix/ODX+0amLIWsnRgqhFMPeyRjwymAvj0+MZYgZ5M
wFaGbhdHCDiBDmDKqvzhyzKYqiR5OzB1x7YDUx2YqmmjA1MdmOoyUy8CTFHlZWWmjCW7636kw6ae
BEw97KG2DKY8X530DAAMOXoyLR/AlKPkx867igVgyqbyC+1lMKXqDSUdmOrAVAemOjDVgakOTMks
XhSYsjswpTR/q7b28sHUww7YXJ6ZsqgH6Ekx88d8Ezzr0qRW+2M+VWko6cBUB6Y6MNWBqQ5MdWBK
ZvGiwJT+UsBU/vd2zHYw9SO9M/EkYOph5z3KYIrZTOkZjknzE2tMhqkohebYyvVdAFOK2v6Y71vB
VG2v/KoXG/jJNr29g/f5MSzdUSzP8V7DDph47qUrrzfI9hrA0jXwgbhmq/dB0WobjL6Dsg0k3waj
DUUyDAlE64ZZblfm2WHoF4ihlQJDq6tA9HeLOzXbkHEnlXCnXcGOEu5UNb1Weoc6tcr4S7BTVXWz
WvlwpFHnIahTVSXQiW8SPwvoVJ8WdHIE+W2gU1zcB3QCcfC9gE7wLapKsI4td0FxloFO08bN9Uj2
LXvLdJVQxuFtHXSWoaTM4uWBzrblms+QMqEMsD6+OzjbrSCsMnX35ujTIaxOt38Lev14GWZsbfh6
g9Qdfu3wa4dfO/z6MvCr9oj4lf/JxQ6/ErXAiM+EX/Mn0C4JCvyq1/Gr36rOF41f5QW7BmBfCmzi
PdqJS2d/NHRm0PYpE8FynIUewZSpNHkfMzWbtyFOnGlq5TGOtlmrt17psJRm9/j0QMz6v/aurbeN
6wi/C9B/OG1fZCSq935hLdd7lUhREh3KKZxIlihyJRKRSIKUYistjFye85KiaWwnjqzKbfob+lAY
RV1Lsi0ZNhAkRf9Cf0Nn5pxd7lJcp0iDIkVjCPbxcvac+c58883sLkXq37M2TLa/r22YZptJF4aa
xruw9aECTl2WbEjcwdrIJkyVDZBGMDDXrGwTRmv0kx5suMT/0IT995swWZHOvDpowhQ7+2L22bWk
acMnl6cUW083YYps/HuPruVsE6Z+F01Ycau2EVV6nTrUtgIjKlXRFWtFOTNffq82V+vG7dowrdZ6
+IUEsFt9YhJWj6xBvdPe7tWAaCw2GPHWoYaYHdm1Vesy6UxaD1vI32ihDFmcATJak0f1pdlE8FML
qRbr0kPQtMF/0Liq1IoNNa4ybwH/3xpXI15MJV/kpHGVU+9YVEc3rgo1ruYadppo9i0a1zo1rlKd
aRF+hzt/2q9ZeY3rd/61kdXaVnczusrCzdoGg8LIJnSJ/Qj6EFCX69WdratTSvY3L4ZuAonjk91W
feQTd3ynzNUpvGDkz9uHPlyQs3W7GRFjWbtzPfPtfiCSfrf10xss/oNqOPzmAbTYTVlkG5Ar/aiX
mWOK6dIog908g/mdrbWot7BO0rWzjhKkanb2bYQk5ZWol7IxbDvb4KY/FT4Gk60K6Q+GFxbZT2Ns
XE9Vhng/hqpD+rPpYxs7a5B2ggM2swavQ0/ZSH/E/bAbNIMASwbKsBO0I34LSlKvQRajXl/sUO/G
zrx9S7yOsXkpCLQaDeLbX5GNj83OVNgkKwfzBXxHM0Bcj3oFNqn/rHVhfqPw4J9fLzb/8PX2jT89
3S3/+s/jY4rPVJ2pLoScqR7TAmaANjnMk1kQMN9huoZXt46JY1NjpsVcl3kBfgCz5jFbZW4IRQus
QHFcSHqUASvEYSjjExnLY66Hh3W08BQcKsw2mOvgEGQGvAxgqPrM1pknpoCjnoVDh+VhOlcIyz8u
1qfX9g9/Xrz97KJ/62+Ax0bvYVpwDq7kNRsrhmbiDQ9HYR68GuJB22G+zNSAlrKZZ+JSNg5dha8K
6sfhwLW4gZglNLfcZIgQCJhKu+AIvwGCwU+zNQ4BVrQDvk3gSB6ai97cnLL41vTinWde+eMngffJ
X8bH0EFw38cfUFiMhYuT4Ha7iABf9dAVz8cdRl8s5qnCLZjd5KsiGnIW6kPAPAnd8uioJdAABImf
htHT+Wloqw/2IxBoDDGvlItm6Y0Vd6Fxo1i+9cKrfnzsztwBNLrHdCBUiATQQmYQmzTOI5v5Gi6u
q4TGJRsLUXI0MqHxuQPolsIpg/QKxH6rImIybj1HA8FzOEZYxPIFvWBehU8mdsnhm5CHZnW55lSi
Xa+y/8KdvnfohvsPxseg1uk+M2RcD+qOoVNKqDgGpiEaBbfQkZF1ODaIgTIu5ZKHlthkR5BDT+iF
bg34h5lFHppoQDMg01QeR0yh1GmQn/bLY1O7Vvcr0TszpftPyqWDQ7f02SGgARAB5YoWo3FwoyDy
jk7s8misxWiAET6O+XZKgzAJpmGYfOaqYmgJTsk0DAWRFAFBwYSMowBDftQkKqgcYx6aleW6v9D4
pX/l4Hhm+vajt0ofnQDTQooNoRFMcwmZTghcQmbSShallEO+hGI7NcETeeCWk7AeSecL/rmULCKz
MaSaQGMIuGqSbjh0hDZ4uWiuXVsrz6//ylm8e1IsfXLyZfG3TwBNQLFRKAYBdmemR6zTUFg8EjRE
YOHYN0nITIwZd8sbUMYW5JDJb0dAiA040ywBAdDIIrqxvCkDWzKI+ZeHZnl5dXZ2/ebMwqfPn818
/vySu3cEaHyKDZzo4g+iCSgeIbrqqyRrsGiIY42WcoBe5IA+4LdNOWzxo5Y+kGVZDEPKbIvFycL1
z0aDpMioQt4U2hqHn5Yfm1qp3Lw5X9x/9o/Z3z1+dfr3D5PYyBgACA+USkQT4EKoAjLzfUTpwEpQ
kDxSBEPQQKVqEWeIJ4qjj5Th+22iAZdameC6Wf7xdONDqggco4YbyQVByUezXLs0t3Hzcune0Zfz
Bw+V6qePOBquaeQItAKARidwqGMOsSugHDKoIKlEr3iTNR4m3PqY6im3JApIvN+xAEskemKIcK1k
azjykFgZ8qP5KrB6YW7jXX/23l//Xto7enXhN08TFaBSx9FY5BHGQ8bI+5T5nF0Ym5ACQuXEoxQS
rI/Lt0qFipfBgMIU8ChYbiJ6yDTyW6cUSpUp0Sxg8FS+RH5sVv255rtO5eDJh5W906+m75wkseEI
fGSaJYnag/EgVuBYYj782MQeV2ga+c1Zb5Cm2cJZeRCFmH+8T5MEvZwk9XEG6hscgiCzuBfgKaTn
o1mqzcw2P3Crn72Ynd17fhzuH3M0HjHNIhUANCqugozyqXqSOiAalQSbV8+4ygViO91BGbQIAmE0
iV6B8FtPZAID4vNNAP1LaKtwCIjGFz2Gn69pS6tBqfl+qbp32qjefexevv+Qa5pHsdGRUYiGSiSg
4fGACqST26ACiFKmqmpwIqGmCSKhLyZHgzsb50IqCiYvMqgYoUBjDTjF+eeKQLtCK/Pz5s2lVW+m
9X44v396Ujl4VHhtH3po3Y3RqDg5XBlY1L5g5iuIBkglWGchHXTeW5ti1bhzVwYpRCqQSG0s4VwF
4soSqwB1b7zI2BQ8Os1L9A+O5qF5Y2nl0kzrveXyF6dHs18cv1K8j5rmIBrsOqUYjYyZBFM6FqFx
iGkWsktxSbl1AUGnKJgCQkx1XkhF94acIggBcWrQBaVaCE/0oog8FkhNaFr+9c3ym9eCYvO91y//
8elhcO/xhfDz55xpLpYcZJpNTJPxty2QUTZqF7ZnOumbR7pniErKieQKWbYHKcQzJG4LUv2lJGz1
zKVOLB501ZGmrfpypgGacLr1gVO5e/SgeOvklcrt0zQagy7SbFIB0jTMFboM5ZdlQDmIDR53MGac
aXG+u2Qdd5IWP6o6gyhIg26F11RDkC4UcQT9s5OL06S8aix10d57u77Z6UfZS/DF4lzAgnmfyQWm
yv2hi3h8JNrf7nTxZsOZe8YvfV6auaGAN0aj3kq316lH/X6BrbfarX4zamTumKZPmKgWp88xr9na
bOD9Abzvyyb6rY12bXNKNjOO/K88YS3jd0rjU5ke3yn8guOdPoIvYgxeG7W7I+JFh1a6rW7EJnr0
b+blfq0drUBM6tFm5oZNZ8TBJPQKhF7pn50GlzpzNLrR2k4frDZ3tik+9drmJoJqRG9PXlxvTE0C
Fc7Df84DmD6s3o562Zvsv6i1+L3MTo8Jg0kkxO7QXf3q9dZ2vYmW8VdEDxmUnbnKZHXRWbxSLTD+
NjD4I4+eoyzm+OYJMvfMMuHrdLtRY3ys1+lsX5pod9rRucLN8whhM/oJ4xvE/x6r1nut7jY9hmCd
Ngt7LVaqtRnDG+0FWS8oOpNtUxr7F1BLAwQUAAAACAB1h00xbFzi/KQFAAAsEAAAGwAAAGl4cDQy
NV94MTBfeTEwX1dISVRFLnNjcmlwdI2Y32/jRBDHX1Gl/g8j8QBIHKx/re1InHBiW4hDcNLd2wmJ
XpP0cm3T0suhuxf+F/4G/g8k/gKExDNtfjRum6Zmd2Z210Z1dZKVTJz17nx2vjOzybP9s8npDN7M
9s5moyGcTKE8m8C3e1MAH4TohX7PT8BLY7FzdnIy+/rT6cl09Fnv1y/f7O9Nj0Yfg36fHO8djODR
O0/AR/ARXaA+PHqvXx/D9O3R0RezyXh358k3T90T9PGH09FUrTwc/TLZV7fo5iP4rvi+B1EM/bfj
8eisB5/7weQTv9/7+bc/n/89X8/Oq837qrrZ3fEHEPgQBCBT8GNth+pjBrEHmQe5B1EIhQeluiTE
yi6hjKHsQ5yioa4MBBQJFCkUA23GUGT6Us+wnejbff2supSZQ1Hw4BRn9LRZWLMM8PK1GUEXk/yq
v/z9j7+W8+pmuaw2y/Xt3e5OICHINYOaoB/AoIC8xMk89pXnRgZtSCgHUBZ6qZIvciAiB5Sz6l19
Mn6TswN01mcw/IJMHlAKXDLQplor1AsJ/d5F8/jJ0+U/F+vV4nq7XF1v51fbWtEUEPYhQoeKECeV
OJnySO1/jo6GxlbrJWggQuZoPNzcnGk83lnjpEAUQc5qsAGFqTSXwPXQe4FLxExedNI8f/FydXmz
XVbb+ur6rl7c1opGSSnqg/TR5Qg9zE0w0Gs9d6qDUeLe6sAYBLqXs7O+RdBAwoXJ4zD1CZejYORV
UJhooJGXeqe73bF58XJ8WW3uVFjq9c1dPScaRJES5yA5FY1glBiqzHju3UNTOg8jFp20StNuleS3
cZaDhwMovQZM47PSCCh6ODZ7w1eLq9u7c0Wy2tT1vNY00gMZgkxwroRzQm+1JQgRsTQ0jWRpmCk+
EANmth4WOiGFzBhwxGieRvACigJd5hm663fS/HRwuKpu63OlsuVNXS+JRoCMQfZxgpi3Xi9o1RW4
BNH2/TQkR01D9Y9Mt8mUNOSsZyNGKDSAYoMDYnbmQaW9HB9dKKUtFM2Fiw3KTA5wPas0v0EjPiQ2
Eq+EffFtRbK5ECKxKcCcNxREGktVMWEz1w7gZF00w9dHi/Vmq2kuVc5URKNkliENuqAdz9s0kcsV
7en9NDGLTXDSkImCMsXJ9hBMGhKS10o3EyaPZS8eUtro+GSlesxc5c2lUto50UQgc5AlbxLljZ4v
a9AYpRVlC6FhZlZenAuS1dNQWshgJbIJp78GmEkhxn2gCgxfHWuaSxUbXQnmNjaJBmrRRC42rYrQ
qbTIKS10KSRtbSAqu/WyhZtxbBJHjipBs5PmYDRXVWCh4lKpvFlZGlUFIlzEVAG9is38uJE3YRdN
yk8KU6EzBgs4AQR3ZSu6CMwtChNtQgS26EUP0/w4Ovz3alPrvNG9hmiiXKNIOmIkxvFm3jR6TDdN
jvgpb33knI0pCnyyMQOELcBWXh7XIcGAVN5kJ83+5LRSsVmr2Kw3tkLjiTMW5hBJjstGbGQjNp0V
usBBA9ZUzDpJXb5HLkMCV4D9Vt0O3NjElpQumvHrY02z0r3m1lYBiTUtb9OE7R5jYtNdBUoGEqam
pU5I5lBpEityDamdLIKLnu+6p9dN8+pQnZuxc+oz2trSJNg97fmYCCxN42ymB9xPk6JbBXuYcZg8
7jMWIfmfs43YUEFw7dX0pi6ag8PTK9U9r1U9WzoaPAhopSWN7pk26ljwITQoM4oNFeuUGVM2k5YU
UwaT/IUw7c5Uupgf6/59Mxy/rlQxW18rpW3r+trWNBQbK61vvE4bSsuNnbYQGqapH8IdV0WrkSZ8
PBcmscwBIHGMjUOO2Y+HTjaHy+oWY7NQNBfNkw0pLTb9phkbv0HTRmiYFL2c/U5c6zFuZYiLZu7O
DQG3SmEOZ+YXgavx9/9qH72bzHZ36HXnGf0HMFRj7vkDIOoJn/4A+A9QSwMEFAAAAAgAdYdNMckr
Lud8HwAAme0AACEAAABpeHA0MjVfeDEwX3kxMF9XSElURV9ERUJVRy5zY3JpcHTsXetv27iy/3qw
wP4PLBa46yz80PthrIub5tWcTZogTk9bLBaBLFGJTh3JV5LzuB/u335nSMkW9bCdNNk0PTKM1hKH
w+FwOPzNiGLGbhzMUpKkTpxSj0Qh2Y8D8k8nJEQhkjTU9KGsEtk2pZ/iKEr/uxNGId0a/t8gcZ1w
Sn8h9G4WxSkZb3/Yu9jde/fxYOviH+Qf8L04Pfo4Pt/7Y6RIPzfUTTz4wan5Fy6Da+eSkt4dkSXS
u8d/35JwPp3208D/+ac/3p+SJKf6+ac/EyekwYVHJ/PLv8iYpmkQXhJ2Sab0hk5J5JPZdJ6k9CtJ
I6JIfaiU3fiLnGYlE8f9SkOP/Evqa2ZPlrtkBurAusi/lxUnRO5LfVkrcnj7S86khxog7zJObhT6
weU8dtIAVOoHU/p7qdp+FJN5QsltkF6Ro2PbUuWBMlBBlgTG4eP4HetnSOOkVFO8LLOljnsFCrgJ
XEpCSkFoJwVVOElK0tuITIOQJsNypR75c55M/iI3IHoU9w53iQN9mMWRN3dTuKzSZy3w/0LnutK9
oE/7xIc+5jruSHeS+U7dIh/PZWUgGwNFY/ck2dwqV+bS8AqE05RJMgEG8P8AqDNdlamiyp2s3jSY
QK3hZDIZep5XJrq9ojElUEiChKRX8HOehPPrCY2ZYqAGu5urmZWUeVw7XylJ5sAnvYIhuI/mbLxj
cuXAmLguTRK0yAFo2R0Af+zFAJocVOUps3Y8L0C7cqbTe2RMoPMkmVE38O9JEl1TEs2wvGw55NaJ
r+ezLpme+P5JuBd68NO5nsHVmhbRWJ15Gnk0pS4zaehK7ag9apyqw0aS4Ho2vd+kiZrKgc/UcuuE
KXEyzQRuLstkzoYDBuIGBi8igUcd4kwiuA2j2tCBEPqOrLEiTltuQN1MTpLQNJ89a+bO5raNCl/T
1w8n53vD0siAySaOT7sE7CxIUVhuw0HoR3jjMkrLbPjHj6NrRsmcz3yS3APBdZ8cMm3+GqMSkB+6
2BpF8Y8gS5ep6xiWAa5sJ03BPVGPTwnezQY22YwBUXq4vnQXs4hzysaUev1+/wH+sWo/Ib3LJeGq
EjpQpISWitQrWqmaJJ+OzB+igmcxsIjmCdM0DdO4bOhlBgmsEuDXcbLCquQTx0/Bk9zd3YHhuUmX
SMQLEmcyzYbap04KnkfkwoXIJzxRJUko36Vu5OHQZnRvaz1DvUchMxoHkQcmhvJEsFSiSNfUgT7D
BONEtdJk9WV9tSx1HMqi5A3CYgcGgtL3ANWkoOV5mEZztLsus+CcMFNqVPF+iIJw4b9wp1HZzeVa
zD0okddoMSdcKXyTwcACkd5S5yufwAwZMaQGcyJhS0C5YufT9tmHww8HQ6wR01+Z/oMQrAVWCxI7
IXAATbhf37x5U152y7xyaw2j+Boqo+smTkydldWyfoN80PHPZI2NZWQrWHzZjMWX1bbBugK9TwDX
0dANaFLbZDpzNpE6I1vBYq3UGdl6qUN6CRjypkFgKN1E4IxsBYu1AmdkD7JilD/JMDkakuvAqplB
4iSFuIM8hxmTnpxNcFynJ/NgmkLVDY12fOVgt78Ak7Vml9M22cHGvAq0TUO0Ma8C7YPGKkX93tA4
5VM+t7rNlpZ6dXJ+H3JW6yysRP5Q6RPw+oOYJmkEQMWNnDgRDc5z0o08l4sIZceZ7gL9OpGLtA+S
Fy3TmTJzTkUxY4ChGKNtIipw2ClUXSOsSL1SXD5zvwazGTK4vYqm5clL65dzrPMAkUrkD5AJQFMA
4+yDqtZI9kudMQBG9qKwfmnHNvaR7wbCI91qqWHyuE7M40WwzvmUpRXYTMI2bq8C0QBWivSJUW8o
FyNer9KYzqaOm7voSwcw3I0znVNEq3MMducxFFZ0ukbimHoXjBdZ67Fy0lo+lzGlIee0js+StJbT
BPqUibSO04L0QXMalel4/4YbuTI96js44JfO9bWTaXWTeQ0aOWBV8o/cXzPmeY1mHRYZrmW3rNGo
SkHAtQwXNRoEdO4fxm9R40EjBKsEDXEpI+en2wSzkYvsFI/pEkD+0/sKoMgDhnw8JxRi0ADDUwix
F5EoRj88zs5gSspWzTKzHJxwSTYxB06JIq/RyoLwQVrBdAW4JBf6k9BCXqtXk9Yr190ku9OUzViI
n2dYoDlYpSpJj/WDCuOCvtQB2HKbcevyOIlnV3lBwkP6SvJzbU6JZy1IB0UDPHQ38X3fnRhSF0wo
mG5tiZ1ifRHSv8MiQbGzZFjTX8x4HO5mE2FY6v515GFO+ybus0KpWJaF0nlFWU+KpXnYn5VC9F9T
yiPaIbmnQl0BEg0BigvaWcIKWilcLvB9UlvIFlouUn0hW8XKhQuomNSwBWR+cZd7kpKOsOx+RVnC
ofPF/RAWiWIhAOJGpljWxBTLGpkC7m9kimVNTLGskSksBSRbebGiWMgce15cLkQnvahaxxatBLNP
DWyz4lq2edU6tgvXP0THL1UZZwTVYsY6r15X27lfUdyr+xQJwDHAfL6IZjTkk1+Y6tvFRGG/LzxY
2sHYFH0bggLM9U7UHsv1ShtRyRtRmRtR6U/IS31Cqs36uJm+tCfUxGa8jCfU6kZU0mZU/hNSPaW+
lFVUmiQBlSxJK0d7QbXScjak0i2gUtZodUFlbURlb0K1enYsqFbqfkG10gpVHzUh6avHMaMyVlNp
E2wRpuNKy8mpZG8FlWxIBrMJY9Vo51TySipJs31uX85KKsdGfSnSSn0tqFbbRE612iZyqlWaWFIJ
D5P2edidoeaUvC2h63IQwOjKRL+T4DKMMHIvEv+LPaEkh7sjbH3b7pJT/pyS3wJJ9orkwC6ILnbZ
Gsd2KNytLh0SnjJgV8pAFeVEOljt+VNS8l/5I1Joeki4OL2qCLv5PoOE7VPBMAeV91ao8Dtvt1+S
7iIIgxQYdDS5y7Xd7cl1aP3T9j4TgX+MGo3xuB4fXEYAyXecsJT2ONo+Pu2Nz7fPP44LnATTPdsb
752fH344gF8Hh+PzvbNxpyROTnD+fo8cH453yOHgRADi+c3s+R9jie0ZRpfNGfzXFh1fIemFu1BY
UMeeVkNPioRvB7hFZ9DH514D1sHeB1nRpI8XR8Hunir1XWcqdBkVPKbpGOzt1ImBK0iUdIT+/Ebe
754eDonVL+niN/IZCkayDjEUkoxqKL4sKI6DEH5/GZm6SIHhyGlwR6djDPVGutIlRxAxQAgDv4W+
vSVws8fJik2K/Pbn0ykZp3TGnruNIQDB6cdqkVE2qmINJB4H/0s7pzEFnW4Bmaxl21psqaQL1BTm
zdz5lI1HUsKMvzHpj2h4mV6NZEm3s/6cQWC1E02jeKRWW0+gdWjVttnYawZObNxWoJnwi2olhZ3u
kpFtSExA1S0LyIpVyZINJDAtQ9rqsoQqwVZGrA28TJSY3oxURaw9ndIwF3sqit0l/5O6YTqyuuTK
Zz/KhnRA0+Odoz92g5vAo3HZig7DlF5mRnwegP1us+mIg0I6S/vpMhYjDX+XdZ89hTrAeOL00/Hu
PL3fuXen9H1weSWS7szjmIYpQWYkEwhaYlwrBnB8cn5y1su4J0MCrHEEoKPw62L34/kXuJR9sdL+
fm43wFexwAv/CQNm/cWNTOaXNr9UZLHu6dX9u/uUJhDQjIhRKUN74WWloT+PUmfKa46IWRq606OR
Yutd4kbU99lYK+hLYCmZ0orVnTrzhB4F1wHqX+HCUlF2P7/cwF+wPHzZc2PUdUnTHWdW8ihjvrqx
vSzxdTW7krnrIWEeTHCdLHMCJdyrDbhXK1LsT53LhMXatf7bi2/YdgBRoEzYJI1mKFttIRaA/+ls
ZUkpdEEzJ/46kmqIa9rg+adhlvwZkbdCFwSnzHYtgOYu8nxmh6erqKu74CC2KrQY25JeOYEnCMZ9
G58+LJbmeU3SwQmvSbZRmms7V8hj+qf0VzfLfCtV754TyZsQKZsQqc1EtYF+KerHjaUnoAyaQ6+K
qtjY1YwYSw+UFSimCv7jcZf2feGukjgfx1i8AFeZtX8j8lrlxtBKcDbDZFYb6sTR7BCcXMWh4FJ5
iBuBqqWnp0cIQIQw9Oh0u3LvHaPThTBnEsNCmIa4KVXChSBMY9wyXOehEu7E98KbqnBj54Y2SOfd
ooNdACkM1Dfv2m/ohW4Cesv8OG57xFF6UyThmGDncHzkXIO+xREGBrkPcxGTMF9aJMgBwrUzA8eF
uI+JqXmKqzXRyUs6XV5BpxTo9BLdYv0A31JdQHIALdf4PY6gpRzO1pEwCG3qTQh6g8kzZlvksCNH
bOuhsKR+Yg8ceojI4vwFgvX8hUmCXBcMotlMZODd+rnJaJnJwD2GYk5pjFiH2TEp1jk/PN4j0OjZ
efHu8ldMHQB0F7jrGo09f++hA97tK/UE7YukQ0aKqoDg4Gxve5ftKCEdWbJUMkGZhMqTuZ/bum5b
fhnx4qCDSeN2tHzYl4sMw0TFCkABHj8qBHMlWLR3jnD1T2uASyXfocu2lRJrSIwMuXbBjEqj21hN
HhJ1WU2s9Qv7kO3df+K+Xhxk0tk52T4b723xol+K1MdRGsXcQJHXsXN3HN3Q8YxSbyT1VXyKtsTD
I1nWzS4PbEYlYRnUbkTYaCI6/mLBj8XWWRYR2fDT0gUTwT5f7O9/Qu8L2OAtWwUr6ub+5AjdYhLN
Y5eWp+YO31ZSjLDHuKltKJLlkBzdcMmlYezK0bosKeXJm8N8xPnlgfuNnIC/DsL+Z6xbXkI2Dcvl
JqeiLL1KU1zOB/PhgTl0dEVsztRQaFpk+zTxua3w+LwS/j5nfG7aprQI0Lm1mgz4lRSHEbhmcxFl
1aqN0BXDtFiOwbAcMULnrSSLEL2kjReJ0JUsQpcLEbpaF6EvlSXLtq4vtKXQXFsTtUYbpmZZTFue
Vq8tTeEEOqWitrJmnl5dT5FuyL2vSPzt6QbZVsR0gySkG9xSg2K6QS5l0Esph5J7E1IOsqUacklL
p0cjWZOKaQcm3QZpB1atkHjQtCdKPLBY/R0F11rFtrvRbTiNHC/bXotOroQyz6BiguHB7hzA0oT6
uBUVUQTaAqIFYWlA5Q/J588EUI2h4L/whUu8oxIiaURht2SdaC5R/IxCZCEDC7yvEUknkkEkMyOD
L7vFGcvLuxUWCrBQbKI7WKRCqxaRXGyVsVBzFlwWk6g+8f0SC5VLAaWyTQwt/60SRSOFluX8WyOF
Biw0dl9Z0EN9SiYqY+EW5IevpiEjkYXOpfBdolNCOSVozSLgcPHCMIhsEFsW1CGyMICFB1qgRJkQ
zcS3TzU2DpbEO6Jl1SYLWbQSCzMbkfyrFn4LBcVv2dYOEzSv7RsnmGKy5TDcPds+Fk2SbcYJEuLk
RCUetZknuS7zVJzmTbM8wyo1SGUHDJw5O3y8QH7lm2177PUbqR87t78Wid+Sz2yRBzm+oDAeneFi
amzIMLl1Zo9jiptMkcUF278Cy5I6kA3VUgeGrqsCfOHbSBe0jNTQJalKybaJioSaXUe48/Gsc9Y9
6L7bQu9kKP6ko+iqam/hImcp8qSjqqpkskuTal5HVeBGaTU7Pzkhu9tnfzDEOp+JhYsXw6boITGe
AU6+TzN4q+7v7z+E3cpCCLF7n7IXSeXkzRshCm/hZ6HGuIWfRRtt4WcLP+0WfrbwU2DxpPBTVYhr
Zb8Vg2jWDw8/1RZ+NqFF+Tng5+OYluEnx56bIlAGP2VV2gSEMgRqWxvAUNmiHUWzTY3hTk+VtI6u
QT/Ype9qVsfQdEt7fhj67uzw4P05owE9zcVHry3ebPFmizdbvNnizRZvft94U3bJxHiVeNP0Gd40
mvGmvpBFb/FmEzxUngNvPo7p34w3TVXnoFPomAg3JdsGuGkqPOvpKbLd0VXT0tnlxNOdjmZp5t8A
N9vEZgs0W6DZAs0CcQs0W6ApsviuE5syIrZCy68HaFIBaDpVoCkvZGmfqzfiQvU5gObjmP59QJNh
TEs39TVAU/ddBYCmLmd5TVlzAWjqFs9req4md3QQT2/zmi3cbOGmyLqFm2JnWrjZws2Hw03Z+7Hy
mj6RndcHN/UcbipOBjcNq4Wbj4Gb2nPAzccx/ZvhpmkbCsOcQsdEuEl9GeCmKvFEpic5KsBNTZbZ
peuaVkdXVO0l85oPbsvQbam5rRa3tri1xa0tbm1x64+WJvVfP25lpfw3iA+CF1p+Vc/jLVT5Bvs/
yyxa3LqAmfpz4NbHMf023MohawN1BbgyzKoY1lrgqrkAXMGXZcCV5UlVJd8OOlE6uibbLwlcH85u
qeeQvzqvqE0EOBD5SIg0Rf2HdUyqA1RlUhiWsFYScdyAAMesSNJ0CkF15RBPZDiBFXfvfHEmA9nk
RAa4kx/JYCqScCSDbgpSrTqGQWWHL5SOYVAWxzBoAtxcewrD40+O0KRvkvhJDo44AUxB05oTcr6v
4EgSYiORXxsbFfXWxkZtbNTGRi8UG4373m1+XE4NCFwWNhWvQpisuBlhPiIuE0HTN8dlxovHZfBV
TOJZ/8Fxmc7fy2PVsucJP3ZcVh8IAVh95LkOZ9Qbz6/ZDAUXgX+jdSSeL8hcMpLA0mRg1raG5h2g
ZsYFaHTdrqWBhk4ydA9Rkz5Q5UorJwy215Qi/xOOx2tKz/YOwJepzEGLR/RnJXZjiVMteXnH8vIP
KqVncCx+/n1lDyoBDMkutgS1yo5l6S5e/wsYzY7lcS/XFhyLquuarWoL36FqljDlCi5GtUzT0JQl
qSVVPEHmaVRbxedGBVJdLQmwdDjmQK42mfubcqHgbsqFRW9j1hTYTQVOpeDFXI2ZuRrlx8QwZv59
ZRjGZU4GXY27wtUoP7Credx7VQVXI0umYirKAoJAOFrFGdzVQEyky4pmLEhVU5idBVcjaxr4LGvJ
VSv5hO/e1dTkwNZlLA+2Dz889AzZHytjWQo5XyZleeCU14aNjrjNswyklGZYdbztqsNt26Nt2/xp
mz9t86dt/hTFbl/B+573ljwW/8vf8St4S1RvvHr8vzLv/4h9JfjXkR+Z/jze/lw8DkH3lI5iSIbB
t1uYrt7RdUXlh8B6juXBpa3Z4iTkmHuCrkD882tZiftX2VdlBV6loAVThRrjFkwVardgqgVTLZhq
wdRLgSlFejVgih2c5W10cFYLpmrB1OMe+YhgyodPh22M5ejJ0n1AT6otZ2CK0o5uSJr4hyqLYKqU
5G3B1JJtC6ZaMFXRRgumWjD1w7ytP/mhwZQsvRYwle2uy0+9/8F31z0LmHrcQ20RTLnUA/Sk2Hp2
UKftSgCmTC17L8hVVDw/SRfPTyqCKUWrKWnBVAumWjDVgqkWTLWZKZHFqwJT1ut6zGfmmSm66jHf
699R/Cxg6nEHYq7JTKkyZqa07HKiYWZK1pRmMCXVlLRgqgVTLZhqwVQLplowJbJ4VWBKe12P+RZg
qiYzZS5kaR/z1YKpxx33KIIpOnHdjiGpRpaKMicO7plSjBxMaQim1OcDU5W98utebGAn23T2Dz9k
x7C0R7G8xHsNu2DimZcuvd4g2qsPS1fPA+KKrT4ERStNMHoJZWtIvg1G65JgGAKI1nSj2K7Is8XQ
rxBDSzmGVtaB6O8Wd6qWLuJOWcCdVgk7CrhTUbVK6RJ1qqXxF2CnomhGufLRSJXtx6BORRFAp2S/
EOgsrXdPDToZgvw20MkvHgI6gdj/XkAn+BZFIVjHErsg2atAp2Hh5noke3wGzyEOiEzZi7paBXR6
jep8faCzablmM6RIKAKsT+8Pz/dKCKtI3b45+nwIq9Xt34JeP10FKd0Yvt4idYtfW/za4tcWv74O
/Ko+IX5lf7Omxa9EyTHiC+JXH/HrxMnwq1RNmi7x6+s/aKZxwa4A2NcCm1iPdqPC2R81nek1fYpE
sByngfv/7V3dbtvIFb43kHeYojfeAm74T1GAu5X402bXSY2Vt0VaFIEsUbYSWRIoebO52SfpS/RB
2kfYm95vbMuWqli2OufMGXJGIr3GNi222BpEMhoeDs833/njUCIZLJlqzvsxl2bpHOKJM2Vn+RiP
tnkU2o7ysJTy8PifL8R890dWhpnBj7UMcwI/r8IgpokqrLeRwLHKMj1DKNguLcJs0+OhkQv4xzW9
CMNzTPIabDPF/78I++8XYaZlbO0tijAr0Hfq964Nx9k8+GDfCly1CLNM73G3rk29CLM/RhH27Kx9
kh5mow7PbXWGptQCVWqvrK3xqmu15+2xLNc2zeo4gxcS8NmaoCVB9tAFOqPhNGtzQ2NSoOSrQ10a
HazrrD1mxpZbb0qY3ythbUhsASmPyWV1qe4IkXIiu8bGeBNUFfg3ClcbS7GNwtUUJeBPrXD15Mls
1MXMC1eTBTkKu7xwtbBw9Y+h0gSxH1C4Ovg7FKPDHBNeggk/6nWYU6sqXO2PXbi22mfjQfqSJYP2
CeOJke26BvsZr0N4dHnbOj97uW/pv7zYWASi/r1xv1N6xx2+KfNyHy4Yxf12LZ98QdY6PU3RYtlw
9FZ7ux8PktG4/8uvmfyDaLj55QGQeKdI6AXIl5M008bYZ65RJvCuSuDF+dlxmv2uh6HrvAchyHYC
/WuEGMoP00yR8YJAL3DVp8JLMHpWUB8MTxJ2TRdQMoOcj43soD6bXsoEuoCqhADs6wK/5zVlV33E
/aYaOAKBRQFrUwmckajPU1LWRYmy/UcjrN3Y1te3aD9w8yAIkCoH8cOvyJ7sfP7bQ7bHDuIXdT4o
4xB7aVZne7bd/4X1aX3wl78ffXsxn14sVu/m/7x9smNFjF8K8c0LmNUAN7YTZjeYF7IgZGHMXIdF
MUsMlnjMd7DhsyRkfgA9SY0lTZ604oDFDRaH0KzhpyZLTBZ72F2D7iaLcRwDxOKIhANoit44F0gs
2ngT3jVbjsnfb8z++rdvZ5fz5Wy2uJ3N79ZPdmweWSMISInNmiYLI9TeBmVA3QDbNmJoYoN3cgUS
OFVCm4E7XKEA6GTCJwOVViDgDgFMomkWvQkeZjOcOI4CR3gAzaefHc7+cTGfXS5Xs+vl3cUS0STM
acBzEfhAsU0sEJoAWIC2g22cRWoghEaBxgR1uGaoNxyLMys2kzAaQlkAFhILuMU0QoLaC/Y9Oiyq
RHP0p+Pr+YfV1eJ+vVjer6/u1hwNNyW3CUtPoLKHGoZINB8yRm19RCDaFkFRuYlJLZsgmIX1RHgE
NYWFSYCKeeEk6OYFg8QPc/PHdu9mfruecU7mH+7XlytEw53EhFQJluKhOSWomeSAIAo0JmKVaGKV
G9DFJaPzYJNocOpVbqLCFBvITaijAaMjS+OHVaFpd0+vlqv798v1evZhvb5aAxqAgm99hrGEacU4
XiDn3i5MCmQUZ1GaDdzQ34Nc2URqZkjvM5j0EIExKgixyaYNsjjhQlY1mpM314vb9Xecl9ktR5Sj
8ZnXxAF84gZmMufDloSJdiWaQKCh8OGTWl6hoZ1jBB+VlDokINjFpogCOJhbjaY3uFjc3l9xS7vQ
uPEgIlPwbSIIS7E04zHceORfYhCL0DhFQED10LNhL/kNofFIwCUINppITQxWhabbH1wubu+ueAS4
4T4zF2gcyDWeCEQCTSTRCG7cwldA6XI0AUJuEhoXPhkUAoQvRGRLOQTZlFZpaZZmEppqS+sORtfz
1f0lR3PNLe19jiZkXiJjGvoNhWeBxiksLU40CEqzmZtXLKj1mLQt0TSLhJQUQS9RQ6HKY5G8qtB0
TgbXi9X9DUfzHmKaQGOj34TSbwQat0ADZ1RjWjkal0oDQx5LdpIEhMbVgPnUtAoebWJVYJS9xgNo
epeL1fqS+8y8iAICjSdPEkqtc1/xHhkFZE6VhYMhEy+pJQMCkSf9nSIdJQUUUEJ4Uonmz+mb7wAN
5+aSo7lGNG7EPBdiGpxERRMofORonCo0EQoFhU25xA2xILK/FBAWZsiAoNQNMngYJFAdBY774zkn
5YZzA1GAuLEgCvgGpTxS3FW4UaNAJTcxCoVkU5KbGn6yqVdmFuHvtaIp47ZTyPpEaTWa3us3C87N
NeWbC4GGh+cG5htf4capyDc6hK2mEtMCUsulsGwUWcjJi4VEFIASjVkw5uSxoQpNevJmhmh4riki
tCuzp72FRqhoPSZC18g0DYm+SUbnFMC8ghAlZdpF0y2aZp6bKrkZjJc8pi2BG47mJucmREsLlJgW
6NzkaNwqNCJNoaU1UO+gwIjNgGQM2it6xSWSzE2SMasYoboWOO69nnNubqBO42iWud+gsVE6D6XW
ap2Wowk0CEozIHM0tPDmFmrJ+TFkKpB61wp3kzQpaKpr6Hb6+mq+Wi/B0u5yvzExpjXkGKHUWrU0
eRVQ7TfCs+INQgSaBgk0qRnS+AZZnPCbWp4y1cMcply0Z191BqNJql+CHz17zsvkFxEz6/zaebJx
EQ+3RCfT0RgWG7bWjB+8X6otKMDCaJq9GmejTjqZcDPvD/uT07SrrZiqB+y2nv3mExae9gddWB+A
dV+2O+mfDNuDfdPXFPlfucN6AO+UhrsymZgpeMHx+QTAPwMOviib3RK+sOvVuD9O2W6G/2u7J+1h
+opz0kkH2oLNqKQzp97aol4MA6fa6k2/7k/Vztbp+RT56bQHAwDVTb/a+1Wvu7/HTeEp//CUg5nw
sw/TTF9k/0O7L9YyRxkjgT0wiHcbq/qtt/1p5xQk5SuiNwQOGs8P91pHjaMvW3UmvgbG/8zyMQ5o
jO8fQFsz0+gbjcdp98lONhpNf707HA3TT+rfPAUIg/TnTEyQ+Hen1cn64ynehmCjIUuyPvusPWQM
Ftrrjl+3HWYGvrHzL1BLAQIUABQAAAAIAARxTDEyX31SOQ0AABYaAAAVAAAAAAAAAAAAAAC2gQAA
AABnZW50b29feDEwX3kxMC5zY3JpcHRQSwECFAAUAAAACABodkwx3GJv04slAAAi/wAAGwAAAAAA
AAABAAAAtoFsDQAAZ2VudG9vX3gxMF95MTBfREVCVUcuc2NyaXB0UEsBAhQAFAAAAAgAGHxMMQip
d49QCAAAwhgAABsAAAAAAAAAAAAAALaBMDMAAGdlbnRvb194MTBfeTEwX1dISVRFLnNjcmlwdFBL
AQIUABQAAAAIAL17TDHWV1iHJiIAAP71AAAhAAAAAAAAAAEAAAC2gbk7AABnZW50b29feDEwX3kx
MF9XSElURV9ERUJVRy5zY3JpcHRQSwECFAAUAAAACAB1h00xGvqKc0kHAAAyEAAAFQAAAAAAAAAB
AAAAtoEeXgAAaXhwNDI1X3gxMF95MTAuc2NyaXB0UEsBAhQAFAAAAAgAdYdNMSrq9IExIQAA2e0A
ABsAAAAAAAAAAQAAALaBmmUAAGl4cDQyNV94MTBfeTEwX0RFQlVHLnNjcmlwdFBLAQIUABQAAAAI
AHWHTTFsXOL8pAUAACwQAAAbAAAAAAAAAAAAAAC2gQSHAABpeHA0MjVfeDEwX3kxMF9XSElURS5z
Y3JpcHRQSwECFAAUAAAACAB1h00xySsu53wfAACZ7QAAIQAAAAAAAAABAAAAtoHhjAAAaXhwNDI1
X3gxMF95MTBfV0hJVEVfREVCVUcuc2NyaXB0UEsFBgAAAAAIAAgASAIAAJysAAAAAA==

------=_NextPart_000_000A_01C4B148.6170F190--



From cnorton@biosensorhawaii.com  Wed Oct 13 16:23:14 2004
From: cnorton@biosensorhawaii.com (Chris Norton)
Date: Wed, 13 Oct 2004 11:23:14 -0400
Subject: [sane-devel] XEROX 620S SCSI Scanner.
Message-ID: <1097680994.2078.7.camel@superman.biosensorhawaii.com>

Is there any support for a XEROX D620S SCSI Scanner through sane?

I'm using Mandrake linux and with a Adaptec 2940 card.  sane-scan-finder
finds the Xerox scanner on /dev/sg0.

Under windows 98 the Twain and ISIS drivers worked without any
additional software. The point is that it appeared to be Twain and ISIS
compliant.

I really would like to use this scanner with linux. It's the only reason
I still have windows around.

Any help is appreciated.

Chris



From Thetargos@tutopia.com  Thu Oct 14 01:45:27 2004
From: Thetargos@tutopia.com (Gian Paolo Mureddu)
Date: Wed, 13 Oct 2004 19:45:27 -0500
Subject: [sane-devel] UMAX 2000 (HP3200c) scanner problems
Message-ID: <416DCC27.7010303@tutopia.com>

I had my UMAX 2000 branded HP 3200c (Parallel port) scanner working with 
SANE just fine after I edited the /etc/sane.d/dll.conf file to also look 
for this scanner, however (I don't know if it was coincidence or not, or 
if it has to do with the problem or not) after I upgreded my 
distribution (FC2) especially the GIMP to version 2.0.5 from 2.0.4, I 
could scan an image just fine, however while working on the scanned 
image (not yet saved) GIMP crashed (while xsane was still running). I 
tried to re-open xsane through GIMP, but xsane could not find my scanner 
anymore. When I tried running xsane or scanimage from the command line I 
get this output:

[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3281)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3933)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3281)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3933)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3281)
[umax_pp_low] Blindly going on .....
[umax_pp_low] Unexpected reg19: 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3980)
[umax_pp_low] CmdSetDataBuffer(initbuf) failed ! (umax_pp_low.c:5950)
scanimage: no SANE devices found

What does this mean?

Just for reference, the way I have setup the scanner is as follows: The 
scanner is attached to my Zip drive (parallel port also) which is 
connected to the parallel port (lp0)  on the computer, no printer is 
setup in the parallel port (I use an USB one). The parallel port is set 
to ECP and at an auto configured port in BIOS. Could this configuration 
be the conflicting point, even though it *was* working right? What can I 
do to have it working again?

Thanks in advance for any input.


From henning@meier-geinitz.de  Thu Oct 14 13:23:32 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 14:23:32 +0200
Subject: [sane-devel] scanadf: waiting for child processes to finish
In-Reply-To: <20041013152329.GA28252@marge.cehill.co.uk>
References: <20041013152329.GA28252@marge.cehill.co.uk>
Message-ID: <20041014122332.GC12141@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 04:23:29PM +0100, Tristan Hill wrote:
> I use the --scan-script option with scanadf, however, if I want to do
> some work on all the files processed by the script is it difficult
> because scanadf may finish before one or more of the script processes
> do.  For example, I want to use it to combine the processed images into
> a single file.  As scanadf knows what processes it has forked I thought
> it easiest to use wait(), implemented as per attached patch.  However, I
> am open to other suggestions.

So you do something like:
"scanadf --scan-script script && some-other-script image*."?

Ok. The patch looks ok (untested). But I'll apply it after the
sane-frontends release as it's a new feature.

Thanks!

Bye,
  Henning


From henning@meier-geinitz.de  Thu Oct 14 13:29:28 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 14:29:28 +0200
Subject: [sane-devel] XEROX 620S SCSI Scanner.
In-Reply-To: <1097680994.2078.7.camel@superman.biosensorhawaii.com>
References: <1097680994.2078.7.camel@superman.biosensorhawaii.com>
Message-ID: <20041014122928.GD12141@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 11:23:14AM -0400, Chris Norton wrote:
> Is there any support for a XEROX D620S SCSI Scanner through sane?

It's not mentioned in our lists so: probably no.

> I'm using Mandrake linux and with a Adaptec 2940 card.  sane-scan-finder
> finds the Xerox scanner on /dev/sg0.

Could you show us the output of "sane-find-scanner -v -v"?

> Under windows 98 the Twain and ISIS drivers worked without any
> additional software. The point is that it appeared to be Twain and ISIS
> compliant.

"TWAIN"-compliant doesn't mean anything. It's not a scanner standard
but a software interface standard. You still need a TWAIN driver for
each different scanner.

What is "ISIS"?

> I really would like to use this scanner with linux. It's the only reason
> I still have windows around.

Start writing a backend (=driver). This is not a joke. Drivers for
(older) SCSI scanners are usually easier than for the newer dumb USB
devices.

Bye,
  Henning


From gerhard@gjaeger.de  Thu Oct 14 14:16:38 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Thu, 14 Oct 2004 15:16:38 +0200
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <000901c4b169$e8829190$6601a8c0@khp5000elaptop>
References: <000901c4b169$e8829190$6601a8c0@khp5000elaptop>
Message-ID: <200410141516.38277.gerhard@gjaeger.de>

Hi Kenneth,

On Wednesday 13 October 2004 23:16, Kenneth H. Peters wrote:
[SNIPSNAP]
> I download, compiled and installed the latest 1.0.14 CVS version (this
> version also exhibited the imaging anomalies with plustek.) I wanted to=
 try
> another backend, so I purchased the Epson 2480 (need latest CVS to supp=
ort
> this) and used the "snapscan" backend.
>
> I was able to scan using this scanner which indicates to me that any
> big-endian issues associated with running on a IXP425 in BE mode is not=
 in
> the frontend (i.e. scanimage) but maybe in the backend.
>
> Attached is a ZIP file that contains output using the "script" command.
>
> The "gentoo_xxx" (Works fine) are files generated on the following:
>
> =09- Gentoo 2.6 kernel
> =09- x86
> =09- libusb
> =09- Canon LiDE 30
> =09- plustek backend
> =09- scanimage frontend
>
> The "ixp425_xxx: (demonstrates "color-bar" problem) are files generated=
 on
> the following:
>
> =09- MV 2.4.18
> =09- IXP425 in big endian mode
> =09- Canon LiDE 30
> =09- plustek backend
> =09- scanimage frontend
>
> These all used the "scanimage -x 10 -y 10"
>
> There is additional output in the function "scan_it" from scanimage.c. =
This
> diag output is from "if ((output_format =3D=3D OUTPUT_TIFF) || (parm.de=
pth !=3D
> 16)) and dumps "buffer".
>
> Please let me know what additional information I can provide.

When scanning with the debug options enabled, there will be a file=20
called plustek-pic.raw

Can you send me the files from your gentoo-box and from the IXP?
Please scan something which contains some colors and or stripes to
see the mismatch.
=46rom the logs you've currently sent I can't see any problems. The regis=
ter
settings seem to be okay, even the calibration steps seem to work on the
two boxes.
The only difference I see is, that on the gentoo box, scanimage seems to
get serveral lines in one transfer, while on the IPX each line is transfe=
rred.
The next odd thing is, that on the IXP you'll get some 0 data, but why?
You'll probably send me all the raw files you get from one scan...

Gerhard






From mreuther@umich.edu  Thu Oct 14 17:57:19 2004
From: mreuther@umich.edu (Matt Reuther)
Date: Thu, 14 Oct 2004 12:57:19 -0400
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <20041014115540.GA12141@meier-geinitz.de>
References: <200410132249.08934.mreuther@umich.edu> <20041014115540.GA12141@meier-geinitz.de>
Message-ID: <200410141257.21475.mreuther@umich.edu>

--Boundary-00=_v/qbBPcd1U8qDs8
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 14 October 2004 07:55 am, Henning Meier-Geinitz wrote:
> Hi,
>
> On Wed, Oct 13, 2004 at 10:48:53PM -0400, Matt Reuther wrote:
> > Hi. I picked up an Epson Perfection 4180 scanner.
>
> That scanner is not in our lists. But maybe it's supported under a
> different name?

Vuescan docs also call it a GT-F500, although the Epson drivers call it a=20
GT-F600.

[SNIP]

> > The scanner shows up in lsusb, and I set permissions and added the
> > vendor/product ID to /etc/hotplug/usb.usermap, so it works with
> > libusb. It shows up with scanimage -L and if I start xsane, I can pick
> > it from the devices list. However, xsane crashes once I pick the
> > scanner.

BTW, xsane segfaults when it crashes.

> Can you show us the "scanimage -L" output, please?

Here you go:

device `v4l:/dev/video0' is a Noname Kensington VideoCAM 67014 virtual=20
device
device `epson:libusb:004:002' is a Epson  flatbed scanner

[SNIP]

> Looks like it crashes when handling option resolution. Please run
> xsane again with SANE_DEBUG_EPSON=3D255. Does it also happen when
> scanning with scanimage or other frontends?

I attached the output of 'xsane' and 'scanimage -vv'. The GIMP lets me pick=
=20
it, but I see a brief flash of a dialog box, and then nothing. The GIMP=20
doesn't crash, it just acts like nothing happened.

I also tried Vuescan, and it doesn't even see the scanner, even though it=20
claims to support it. I am asking elsewhere about that.

> Bye,
>   Henning

Matt
=2D --=20
Matt Reuther
mreuther@umich.edu
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBbq/vFse4xrb7oagRAtviAKCilXS4KT1oWk2Sl0sm2bsV0A9k2QCePygj
0JuslcB+L34rqSszF6c/tak=3D
=3D8iIt
=2D----END PGP SIGNATURE-----

--Boundary-00=_v/qbBPcd1U8qDs8
Content-Type: application/x-bzip2;
  name="scanimagelog-epson4180.txt.bz2"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="scanimagelog-epson4180.txt.bz2"

QlpoOTFBWSZTWR3LwhMACNNfgFAQSOf/938nzgr////wYAteX1aM4u7PsHXd3IppgC2+C7tprLQU
0NTDFJpo0nlMEZEaPSeptQ1DamgaZAB6nqYyn+hKe9T1M0DSk0yaNAAGEGmgyAaEKb/VVTR6mmQy
DTQAGgDQDIAABJqRFTybU2lGjTam0gBoGgAaNAACKImmoymCaaE2qabSPUPUDDRPRPIj1NAESggI
aCAKn4o9U/KnpPRBkDQ9Rpp6h6lDMLmILsgVWYAIhA/nup+8D4op3+U4lQDdN6c1Z7+E+eRwHAdc
HRFePZ6YPh21yyiAN8AA/pawfBlrarE26vrQYb2G9037pzaNUfIFEIdnIchO1fnlKSvLETPyOJ1A
2Hj75+8sXGYfHXLkMDsGH+KAQcdXZrr6DTRR+PCLw7vmalI1XMYFh92Sb4gAHOSSbxVSlL3AHIAe
nT03mdMHIBWsRA539/TyFBsOIhkKkM3LdlrVNMce3Gvo4aLqptmOeugqX8B/bnt07cDI0z5Xv40F
TLUcdsvYAbqpkqmPvu3aTLHPqM8a1LAA51O3L2vnYx69Dqpl9uGOQ5w/POiGkQB6TPw/A2+PfmAO
IzoOVuPDr8jCtszoMFOm+7pjdLyubZQy13MKdAznVuABre5fr/QHQ2RYysk2zceqGvLLjBYRpqa+
rKWMa3z98PerLWkkigAA2p7VOJjAFaxaJunOcLgm15sJ8qzdYIxukEZYqkIlVAjm2KY8FgValkZW
wREk0EdCDLYIwzjaKNQJTROuKjbtwctYEtSyeMYUpSbQo55sJ9KzdYI0uoEZUS1AUFVQB0jmpUgQ
IQSQQSVtnsJceE/xyy4IeIcy/YrtN0zN/Z1Xc7W7tFTKm/nWqqY7BHtHVqIeegx7t2ezltJaZl/K
SINU0h1m/DUT+EVDw6sBN0OPlqcwGJJIQEN+V8VgyzaxuCkU8rJIY5n9ccN26C3Rtqa+rY3PnrfP
oherLduzUN/OSSRSSSMdIAAPIcSSSF1A7eyg40OW2VG+yUHnmjEmjiVVWguGc4F9eq7TzSgV3Hmg
+qdZx+YN0Hv3SSSScn+sXoIG6g35/y6+iqR3ZYhI1tW04mfiFZVKXJxMgOSeiZnIbDpF9PPfhWta
1rWta1qaYOuGGGGPNKJTf/G4W0uV70w1T1Sh0k9AzKMzzLGNOabYFW77JTAMzyHADNzolzonGqf9
TbuDIg70z7E0oOoLBtyvMY5dZMW2xGH4VQcdyjepVOCTcGc3J7em3wAGCpABnCXiqW5fCrgAC5s1
BpM96lXVCd3gMlJ7UySHivtwbQKGRTNYJG2TMhlCSkKJDy3Aih+RR3Pet0FpzwemQhXonhB7YPJ+
ZSz4uD/ZHP9H50XpENYiiTB93aD+oewP6E9QBgjFUkABiEEWRAgjJCAeYA+CH5FQDsfxSyA0ihHh
IL90FwKgH309gRGxVQKpqQdafEPje1n6k7RVTrhEfEDsABsAD0JkZBlT3HMqmee8VOOAEpVPXKuW
XMg7UVWwDY3hv7UxTy7ABwc0xDGBIyteGM6JRKtgtQPpA8R5BdyqkfqetBiQ0AAP+ADGg+CTz715
Aww0pNiVUvIrtCixyR3xLTTTTXt5rXbsMSSH9hohJqDeQflllNEmMJDpwJweAAzKCrtyurBVIPbA
VAyDKAimQBYSNJdfMKmkCc/OshXfI3oKqSLSSIjgADD3AGgAOBobymJWoB8mh860hMQBhkgw+SKA
RVOIcfhd1Tb5GZ9B+ux2FPYZ4QznrrTA7iV+rrriANrWtWta1pS/tbBAedMccbqp3h5kYfaY31/Q
VQYOKiO6QAeYb6ySSSRMVivQa1xyJcCxzGiDzKwtlbJQfiKqaDARwhXLprOOeiTvTp3BO7vRQvom
l+PCCcjr41tib9qGgBpTp+/IOk6wTKxbHJzD50XbpBUgAwDxDw3g74Ib0ufhzV7cVwri4BAPRNKj
WHcHdyqKlURW5Cdcly7hABKSNwvuzergxq2qq2qqNkCZwwgJvf7q4gEq8MMDIMkFCW9S6qdiqlwv
REeHevj2VTwEudWHkm2rXN+ZqvUi5EREsvmiIs5679TMzGdmbtzJAAAUpQAAAAAAAAAAAAAAAKVK
AAAAAAAAAAKDTiuK7ZkdNuLUzE5szMxVVEQPJ+kcVU0kCKSID5bAHDhk/22OtL/aqmFVGQBgAbJt
lVKZeSZ9Q0HlVSE1wtOJixYsUghCSatK3uYoPMHckayqKAfUBe/QKScUG9p5h54ah8RUCB1n1k+m
6qUVTSqgEIDm4AA0VSdh9+DUTADQToV5aXkkkk6J68Q48it08bhfoJxTXfU5YBhAn2YWDOXC8CWQ
HUAeFO+lUM6SoqgqijqovJIMJZSMKEVXgmqqVFVMYP44UtBBpIgxtRRVtpDT0VNcg1CuAWUADguJ
egKujvtgDrgT8W2LDDgBPhgS8A3Rq8JuG5VIPMr7AeAAMfpGp4fX2lDmFkqBdpyErpXYAaXKtdqq
1m1rVVWtIVVWswqAFQkBAPBdUzN6qVKMA/WAwA4Wtulads1APHavklsmn3DxE34aczF5NMJJJJOS
UT7D3HqBHzDzj+TsnLuSwX7rvZO3xT0C33+9k4p8tyImwg6gFE3hvo2kSEZAD36KqVWuY7yADUlJ
4pbgumFDjhhqGufgAaZ5GIHhcTNLmIUQd8cbm46JJCtZZK25e5VRtVMN4Mw2vbHqAHevIgCUVSii
PwLgnl0kkkkifIu9+OVR3Bu3AH+tTqMBRtO3EMdjFOyX5apNx2JcLwEdyqVqiJUK3VUy5Y9FFfq1
700doFEleBwHPbTvvgKlSm7CshLQpQRlPVKoA41dYgVTVrsG2eglQrAkCZDWbsCQkJCQiQeOfBDW
gA6uIqXK60A40o2WSAhwyAslQC0TO4F8UwA0hbTej7/XQ000000005hnbuPIcYHPtJJeBT0HqwMw
zgTsywFTA31DquwdUn6TxwN75E5KmFXNMGpJIbNKqqsMevwzHYGxq/KBwkxDlcGTVthwGDMGbd2e
7X4dKqovGDBIBnCwKDxS99GwpMQb9iI/+LuSKcKEgO5eEJg=

--Boundary-00=_v/qbBPcd1U8qDs8
Content-Type: application/x-bzip2;
  name="sanelog-dll+epson-epson4180.txt.bz2"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="sanelog-dll+epson-epson4180.txt.bz2"

QlpoOTFBWSZTWRxbk5MACdnfgFAQSOf/938nzgr////wYAsffbHqzz77ffX15dFaipT6aoFhmTQp
poFAjSTJpqPI0aRPTUYninqAABoAeo09QRVP9GpPNqjJoyo0AYgAAAAYQ0GSYgpqaepvUmnqNGjQ
aAAAAAAJGqRE1PSek02oPSNA0AAAAAAESiaU1PaibT1DFMNQZqAGmmmRoyNGgCJQgCNBMgmTQp5p
BBghk9EMhtSpqF4LwgquUAJED/dACh/iggG+Wm5WnRjTgoNhsOEN6X2008uqHTrtbCQDNADwZuC1
S6kYJQrxfYZIGZA2KwlyQy7CBgjK/EsSWk8Fmg4plkD9fI2OYNh8vhl8JYuGX/VpjxGB1GH6ZiPu
7vTv4+Ttnn/n7N2Rf/LC0lbTrShPP9KV+ncAO9VNwiUgoNLrgBxAHnz89xLnBRTGAjyu/r37ioxB
kQQkg+Z85he1uCS5dKkySRgglbMYPLbhucStwNZ6scxw2x94A3ADgqmPw11zmOGXYZYVqWAByUXT
3HowxXmSEeJ4xBkg+JwIIJqk8fSL/DdMAAyAoISJmdTpLW9K42oKaGevU7MrGpMMiIR1lNSUoq4C
IhOyM/r9aWlMR2qRFavbY3Rfftaet0z0sfepzp2SdDe06IJAAIERFqTNUZAIhva19j4wnOcqznZb
FBbfVGDnvurvO6/cKiKwjpCtzEtNpuqY1YxWVKUvsOkJSRZUSMblfSzbefxbdvi4deONcIBMshpK
WS2SlkC0tLCQkJBJCRkJuzH2gFn5cuLv7ZOr4cHNfz32tyVEZFhXCr1wAOJ7AGoAoVQAAAoCgweB
waQztdlnnTCsM7Z11MspT79aEpx6gFlUu6CP0jw4BDkUFOux5VwaDsgqKu6yUPkEEASAggBAOKb2
IDzsJpDbx4OQe1VIGf0e/rrPXTbzpbylZjdSutmVlrs91zTtdB6WP0JllnZJS3cOiGquorgAAUoA
Bb9JAD+5/1VTiHr2oPwoVhtwrra6tC3u133KCXgGwHudnAbaJJJKBcHsTaidO/ZKagoNeQN8x7wc
27hJJJmeuLioDhQbbnTyYqpDZyZdjYyLfheuE2M9VBPU2lgpeTECfwD2BQMpJwC4KkgEamHOYnLs
WyVVV2ZmoEQVrWZYJbSlKRvZhQqHJKQhUtSk+HKhvsfhk5V2v2zL6+7xDSofRMuTRnwCjcQbU1NG
1La1tqUrjWrooJvDnVsxPiFLx0PYGoF8101saXBcdwS+of+DjVrJQdZsywQi4C/HfAtApGbwpSCh
BN8wgrtGLMEj2zwnZyUUy6mYahOxz0v1rUlt4arX4+3jwABvoqlcfTWwA12kxS/TLpOLa89/wPRK
80pXDqnZu3ZTOm6U9Qp7QDeIaqAxAT+NgGQP2JCaJy1o/RJmIhXPTfgfl+50Xv2bP7Jn73tqukQ7
lQUpD3aAdY5w+ZOUAYIxVIQAGCRAkBAgjIQgGoAeAA/BVQDq/WEsKBPlQF9I4gFgQPjhb7WTggK2
DbDrevJazxh6gBDyxEewA1gA3gA/f3ho6fh0VTXWoB0CofdQHPh0UE4qgBZEsaOnYGAeXQAbzIMH
CMjK13YTmFAub2+r3xOEdpHcVUnMcPPSo5RBD+ADMz8QyUEr29AN7ffqF5FUyoK8gqhN87pSUlJT
81pWV4clBJUP3DJB1dYz5btTBbwQ3ZjnOiARSECcGkJTAU9NDaAa5rrK6KAXgTMxXIAmnkNPV0oO
NVRCkkT39tABxABhyAHrj33AA5m84lNa1UA7SnfWkMi0ygDDBQSHaqIEVTed7XZ1T9DE+Y+3qeBT
3jPOGU9elLzxJX8+tcABta1q1rXXdZAcaX332VSt1cmqqgkVsiL4JAB2DOskkkDBYDwGtcLAVNho
CbFYWwtgiP0ACGQwEb4Vx4Z78sw7Q4dGdKdQBL8wyv4b4pyO3hW2Bu2oZqAZ05/Zi859aoGNjDEy
D/lB2A8Hv1B9nn54LvuEN4Zfd2IHhoBfXBvIAZB4VGsO98OlkQHEj76GDhFAMQoOLjo+Xczdzkkr
SlDZQTeFyGXz6XgDS4LWMHCMjLtZZVNCqlm1FR08I8eeocQGe3rhwcembgC84Al0+MA3nh/Ukhv6
uXYqqqqqqqqqqqqqqqqqqqqqqqqqqqqq2qqqqqqqqqqqqqqqrV6BxHNfNrkJskkJEB4PzjuxjFCQ
BE8tygGuuL8ugWrvBQuDfRVM/2DTvGo81Ugbgq9YyMjIBBQHLkkuuL4E5nxgErVUQNQBa2LSTbUE
scTxWwD1ioEDt8j5q+aiqZUFAhubAA1VSnHVoBcAZgcyvDK6SSTmHt4PClg8LNuQG8M9a7Xt8Z9N
9gylzdGWOwAmx6apZptpbaFt1plJIUAthi2FChAFWbw0oAIYQfyvpaCDSRQSNqIgBfm591jaiNm1
wXoKPQAxoorl+N2aO0A+trfgxhQApYj0DjN3ypg8VUncD6AHeADH5wqd/n1KHFsFQC5pwArnXakm
rswuMXGMMgXDjFBbIBKAQsgBy5wpAHI3KpZowA+KgkBA32trK06zRQDw2r4pbGn1DwA3X58jB4tL
5JJOIUD0PwHsFHjeOPc7YbmkLm2mznmjhDUF3Py3BmDs2QFNgETRQCgbndRtIkIwigHJVSi0xTUg
A1JSeAW3LlfQ2uzc8u9QDLHAwAN2YGsMzQCBe2XRkdU+TsMUd2/7rbbjqOKGgcHhfbHoAO9eRAEo
qlERfQuRPLskkkgWe8vwqOjpooB+uZ2XijbtwcLw6znwDLIdgxcYz7VUtYBSzbFVTTlOyoPnp3Bm
7QKBN5vHLbPuuoTW6shM5BGlPaFUBwq6QECqaNdnbLMCrWMjMRrNbyQkJCBE4Zb0NKKpoWppQA4U
oZAEREN+IGQYkAMqGrMAz0hok1TGrJPx796ta1rW7O1fZPE8AD8u8VtAp607LzJyjMLGtA59WJoE
9x6rzc+SeVEupYyCUVU4ZSSSQL+3qX7O1PQA6jcHpLQe8OZaNo9/jv8fhjJISeoIEEBzgEHxDDDH
gVpIdm9Ef/i7kinChIDi3JyY

--Boundary-00=_v/qbBPcd1U8qDs8--


From henning@meier-geinitz.de  Thu Oct 14 18:21:15 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 19:21:15 +0200
Subject: [sane-devel] saned array memory limit
Message-ID: <20041014172115.GE12141@meier-geinitz.de>

Hi everyone,

There was a long-standing bug in saned that allowed to alloc huge
amounts of memory on the server by simply sending big string (or
array) sizes. I've now limited the total size of malloced arrays (and
pointers) by sanei_wire to 1 MB in CVS.

This limit applies e.g. to usernames (in SANE_NET_INIT) and options
(e.g. gamma curves).

Please test if your backend still works over the net.

If you get the following error, you may have found a bug or a really
big option value:
[sanei_wire] sanei_w_array: DECODE: maximum amount of allocated memory exceeded (limit: 1048576, new allocation: 4294967295, total: 1048575 bytes)

Do "make clean" before "make" otherwise the changes caused by the
header file won't be picked up.

Bye,
  Henning


From henning@meier-geinitz.de  Thu Oct 14 18:32:05 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 19:32:05 +0200
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <200410141257.21475.mreuther@umich.edu>
References: <200410132249.08934.mreuther@umich.edu> <20041014115540.GA12141@meier-geinitz.de> <200410141257.21475.mreuther@umich.edu>
Message-ID: <20041014173205.GF12141@meier-geinitz.de>

Hi,

On Thu, Oct 14, 2004 at 12:57:19PM -0400, Matt Reuther wrote:
> > Can you show us the "scanimage -L" output, please?
> 
> Here you go:
> 
> device `v4l:/dev/video0' is a Noname Kensington VideoCAM 67014 virtual 
> device
> device `epson:libusb:004:002' is a Epson  flatbed scanner
> 
> [SNIP]

Ok. Just to be safe, comment out "v4l" in dll.conf.

> > Looks like it crashes when handling option resolution. Please run
> > xsane again with SANE_DEBUG_EPSON=255. Does it also happen when
> > scanning with scanimage or other frontends?
> 
> I attached the output of 'xsane' and 'scanimage -vv'. 

The latter one is from v4l not the epson backend. Try again with 
"-d epson" (or comment out v4l in dll.conf).

> The GIMP lets me pick 
> it, but I see a brief flash of a dialog box, and then nothing. The GIMP 
> doesn't crash, it just acts like nothing happened.

If you start gimp from a console window, I guess you would have seen
an error message or even a debug trace.

The log still points to reading the option descriptor but I'm not sure
if it's an xsane or epson backend problem. 

Checking if it happens with scanimage may help.

Try something like
export SANE_DEBUG_EPSON=255
scanimage -d epson -y 50 -x 50 >/tmp/image.pnm 2>log

If it's an xsane problem, setting XSANE_DEBUG=something may also help.
However, that can create "insane" amounts of logs.

Bye,
  Henning


From jb@jblache.org  Thu Oct 14 19:54:53 2004
From: jb@jblache.org (Julien BLACHE)
Date: Thu, 14 Oct 2004 20:54:53 +0200
Subject: [sane-devel] saned array memory limit
In-Reply-To: <20041014172115.GE12141@meier-geinitz.de> (Henning
 Meier-Geinitz's message of "Thu, 14 Oct 2004 19:21:15 +0200")
References: <20041014172115.GE12141@meier-geinitz.de>
Message-ID: <87oej5qgea.fsf@frigate.technologeek.org>

Henning Meier-Geinitz <henning@meier-geinitz.de> wrote:

Hi,

> Do "make clean" before "make" otherwise the changes caused by the
> header file won't be picked up.

Speaking of that, would it be possible to use .depend files to track
dependencies ? That would be very handy, given that the Makfiles
currently do not track dependencies, and sometimes can't do it
(#include <foo.c>).

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb@jblache.org>                                  GPG KeyID 0xF5D65169


From henning@meier-geinitz.de  Thu Oct 14 19:58:42 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 20:58:42 +0200
Subject: [sane-devel] saned array memory limit
In-Reply-To: <87oej5qgea.fsf@frigate.technologeek.org>
References: <20041014172115.GE12141@meier-geinitz.de> <87oej5qgea.fsf@frigate.technologeek.org>
Message-ID: <20041014185842.GG12141@meier-geinitz.de>

Hi,

On Thu, Oct 14, 2004 at 08:54:53PM +0200, Julien BLACHE wrote:
> Speaking of that, would it be possible to use .depend files to track
> dependencies ? That would be very handy, given that the Makfiles
> currently do not track dependencies, and sometimes can't do it
> (#include <foo.c>).

Could you explain how that works or where I can read more about it?

I have already thought about using automake to generate the makefiles
but I guess we would need lots of special rules at least for backend/.

Bye,
  Henning


From svoltz@wanadoo.fr  Thu Oct 14 20:09:46 2004
From: svoltz@wanadoo.fr (svoltz@wanadoo.fr)
Date: Thu, 14 Oct 2004 21:09:46 +0200
Subject: [sane-devel] UMAX 2000 (HP3200c) scanner problems
In-Reply-To: <416DCC27.7010303@tutopia.com>
References: <416DCC27.7010303@tutopia.com>
Message-ID: <20041014190946.GA2675@wanadoo.fr>

On Wed, Oct 13, 2004 at 07:45:27PM -0500, Gian Paolo Mureddu wrote:
> I had my UMAX 2000 branded HP 3200c (Parallel port) scanner working with 
> SANE just fine after I edited the /etc/sane.d/dll.conf file to also look 
> for this scanner, however (I don't know if it was coincidence or not, or 
> if it has to do with the problem or not) after I upgreded my 
> distribution (FC2) especially the GIMP to version 2.0.5 from 2.0.4, I 
> could scan an image just fine, however while working on the scanned 
> image (not yet saved) GIMP crashed (while xsane was still running). I 
> tried to re-open xsane through GIMP, but xsane could not find my scanner 
> anymore. When I tried running xsane or scanimage from the command line I 
> get this output:
> 
> [umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3281)
> [umax_pp_low] Blindly going on .....
> [umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3933)
> [umax_pp_low] Blindly going on .....
> [umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3281)
> [umax_pp_low] Blindly going on .....
> [umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3933)
> [umax_pp_low] Blindly going on .....
> [umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3281)
> [umax_pp_low] Blindly going on .....
> [umax_pp_low] Unexpected reg19: 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3980)
> [umax_pp_low] CmdSetDataBuffer(initbuf) failed ! (umax_pp_low.c:5950)
> scanimage: no SANE devices found
> 
> What does this mean?
> 
> Just for reference, the way I have setup the scanner is as follows: The 
> scanner is attached to my Zip drive (parallel port also) which is 
> connected to the parallel port (lp0)  on the computer, no printer is 
> setup in the parallel port (I use an USB one). The parallel port is set 
> to ECP and at an auto configured port in BIOS. Could this configuration 
> be the conflicting point, even though it *was* working right? What can I 
> do to have it working again?
> 
> Thanks in advance for any input.
> 

	When you get 0xE8 or 0xD8 values, the scanner's ASIC is confused
and needs resetting. It can be done by powering off the scanner, unplugging
the parallel port cable, plugging it back then powering on. 
	The ASIC gets confused each time a command in progress fails, in your
case it's certainly caused by the GIMP crash wich prevented the the backend
to finish cleanly the scan.

Regards,
	Stef



From jb@jblache.org  Thu Oct 14 21:40:21 2004
From: jb@jblache.org (Julien BLACHE)
Date: Thu, 14 Oct 2004 22:40:21 +0200
Subject: [sane-devel] saned array memory limit
In-Reply-To: <20041014185842.GG12141@meier-geinitz.de> (Henning
 Meier-Geinitz's message of "Thu, 14 Oct 2004 20:58:42 +0200")
References: <20041014172115.GE12141@meier-geinitz.de>
 <87oej5qgea.fsf@frigate.technologeek.org>
 <20041014185842.GG12141@meier-geinitz.de>
Message-ID: <87fz4hqbii.fsf@frigate.technologeek.org>

Henning Meier-Geinitz <henning@meier-geinitz.de> wrote:

>> Speaking of that, would it be possible to use .depend files to track
>> dependencies ? That would be very handy, given that the Makfiles
>> currently do not track dependencies, and sometimes can't do it
>> (#include <foo.c>).
>
> Could you explain how that works or where I can read more about it?

It basically boils down to : gcc -E -MM foo.c > .depend, and then
including the resulting file in the Makefile.

This depends on gcc, but there are a couple of standalone dependency
extractors lying around (a quick search on google indicates there's
one in X, called makedepend, but I haven't verified).

> I have already thought about using automake to generate the makefiles
> but I guess we would need lots of special rules at least for backend/.

Yes, it'd take some time to get it up & running...

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb@jblache.org>                                  GPG KeyID 0xF5D65169


From mreuther@umich.edu  Fri Oct 15 00:30:31 2004
From: mreuther@umich.edu (Matt Reuther)
Date: Thu, 14 Oct 2004 19:30:31 -0400
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <20041014173205.GF12141@meier-geinitz.de>
References: <200410132249.08934.mreuther@umich.edu> <200410141257.21475.mreuther@umich.edu> <20041014173205.GF12141@meier-geinitz.de>
Message-ID: <200410141930.32684.mreuther@umich.edu>

--Boundary-00=_XwwbBGSvvgBHyZi
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 14 October 2004 01:32 pm, Henning Meier-Geinitz wrote:

[SNIP]

> Ok. Just to be safe, comment out "v4l" in dll.conf.

Done.

[SNIP]

> If you start gimp from a console window, I guess you would have seen
> an error message or even a debug trace.
>
> The log still points to reading the option descriptor but I'm not sure
> if it's an xsane or epson backend problem.

I ran gimp from the console and captured a log. It's attached. All I did in=
=20
gimp was pick File -> Acquire -> Xsane: epson:libusb:004:002, and then=20
quit.

> Checking if it happens with scanimage may help.
>
> Try something like
> export SANE_DEBUG_EPSON=3D255
> scanimage -d epson -y 50 -x 50 >/tmp/image.pnm 2>log

I did this and attached the output.

> If it's an xsane problem, setting XSANE_DEBUG=3Dsomething may also help.
> However, that can create "insane" amounts of logs.

Let me know if you want me to try this.

> Bye,
>   Henning

Matt
=2D --=20
Matt Reuther
mreuther@umich.edu
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBbwwXFse4xrb7oagRAnAYAKD6ONSmY12lFijcOxMYa0EgPX29XwCfReot
RNpjsAqHKVYzK3RfUukRTSY=3D
=3DUUEv
=2D----END PGP SIGNATURE-----

--Boundary-00=_XwwbBGSvvgBHyZi
Content-Type: application/x-bzip2;
  name="scanimagelog-epson4180.txt.bz2"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="scanimagelog-epson4180.txt.bz2"

QlpoOTFBWSZTWeGoibkAAmxfgFAQSOf/938nzgq/7//wUATVqzenHnNC7YI9dhJFNNJtI2qfpR6U
2RMBMIbKNpNAZpD1AyQyaUeiRptT0gGhoAAAAABIiImmmoyZI80hPUYID1DQ0AA9QMk0oA0DTQAA
AAAeoAAEkImgTEaNIaRoGhoGnqADTQGkRUF7aw6cUMsCVJUmfxAY0m18Bm2EPZnVRUAZUAC1pjw0
M+1tdU7R7LH4Cvxw5mHX3deW26zG7ySYTHn2NhwOBkq62uHPFaglo1YGkSlLqr1SFBfgcR98udUM
RknQ6W0c87hC08PXos5AnKXp881pHVZBvYRSrcxG77xO7inHVq3ZjORcp79vR1mBVLIlagTwLWWI
pVc1s0vfVJ6LrLlE8NrZNyymEl8VJPHPdV0nNsds4xFIDXex4CkpSFNLkVlJZAxQglEGige/rFeH
TYhkYolku1cRx3wrplcnhjp4ucspHc9rUhpM2BmGGOvqAUum+0aLHh1t72oovb19br2ZuDPbO4Qt
yXT1DBdUk2vv7r7ckaEEjUyu7cswLe3h3rr5FMdxIUFvTHA6K6wTi6ley10rTsD7+DeglJbGQRZL
Tf8akslxZhRBQuShKjSapBW088ymO2gSWOzUQiQsLEGihn3xGBEFdJNIn3mam/k24vGd2go3kV6r
yO17ba9Zi56XE5t77+mlxsjBwcqANzATYfZscCVlYBqIR5CAsDH0B6F0I7i0dwk7sd6kzyCOYJJD
E0vgm2TXAyoCCRNcjkdZJBuouyIFJeaGsdc3jU8Fl1qrmrgXpeq0QH6SCDRgrBp4N5C12ku3claI
86YJHFscB9zBNkgNZolCQScgDhEpsKi7WFlSwDT9SMqaVy1pQ20xtmT92DvBE5fAbtYmTRq/poaj
uS5MTePwSblYubnrHqNo0HDjTLQ8ClSyoErBkRiMBklFVqCY8YpYjtEp1BWl/lU0ZFjW6WYnzEkh
5RqtYSwMr4xur14nUxsnBORqKLtcwQbw3XCV7IRJdhijOonFi22ibhjSoznjFUA4y5bNY2mgpwzu
ZOTo0it0GikFTLjBTwUYtdKZeReKQrzdxqIG/CbLZN5AlbfpZmlCWwKUZpCuMtzYVJbzNPe5yBcU
UJYFC/G9PlVMDB5uekBlcBobHlabSSQ0HrrFrhwMvlAFdEXwASFBFFWASs31qAZfEpstSfcWGclM
ML44c2o046CDjCqrQ1xeQ202xJI5pRMWBsHGXXdSYq8b4WxFo/GlbgcRVZ16TsS8KPis2jMs70bQ
ns7e7mQArwabY2MaYeEZJ+esgd2jXYBNi6ZwpRVTN5QiQUBrCvkx40chh99+jSuQB4oSXFQG0L84
F9KjEhBey78pQBmgBbKsLg5sadDInrZqFqTXytm4zlbzcIMoiCLJ0kwyGREFJZI1bAQHcSMnsSOC
ZAdpqtEq5Ocu03i7tqQFrDyOglrVbhlJMc5umWLHO6reCqwoVDjBQolBczK8dlWyrz4Z+/PsSJMI
SzLO6wQN1pP+LuSKcKEhw1ETcg==

--Boundary-00=_XwwbBGSvvgBHyZi
Content-Type: application/x-bzip2;
  name="gimplog-epson4180.txt.bz2"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="gimplog-epson4180.txt.bz2"

QlpoOTFBWSZTWRCfeFYAAgxfgFAQSOf/938nzgq/7//wUAQe6uc7qttc3XVrdthJIVPEYCCMJ6g0
NBo8kAAA0DJTMmkaET1NADQ0AA0AAABIkTQRoTJPGkymTTQB6j1GnqA09QMhzCYBMAJhMJpgAAEy
aaBhJEaUZMmIaFD1Hoj1NAMg9Q02o0D1EiwMuex/fc+1xQKBZGMGpGt9+5j4+aIzMwGxgC2Wtwb4
/U47cvSyF9YXHlfbnu4iaGdned5XN8q3DlnyCP3aYApC4ZOEiYmj1VeS8TBqExyqELo18Nn52rLd
d+eF9pTfXNuU22/H3RL03yz5+m4dajjrtJCzCqQISsLvLB9dctskyPqA9FIBZ0wWQK0aK5sc3Rml
fllCAnUNZ915xqnockVUFkDIQTej5M4pw6LA4wZWc+qM9ENquVxRgx5M1MNjo2qhlJqyU+uIBQ46
b7xzrxhduxLXdczreZwOjhfELGLp5xljeJrpo4oPEWsSct6cUmnXbX11l2nmVhdCOmcwHDqC1g7L
4B2Q+0w7wVy7WlRiwv9kkV2lL5gTLRQKbEwnBV6ogKZVIo1GB0QQBtu9tHsHjQOz8TN7sDfumGQJ
3NseHNsp2GDl1uJbt7+fXO4ui9xziR1MBNh3Nj1PdJ12Ia1kEsX0sHJdsLipneNo/C4yFqEHcAIc
1uEFwisDUwJB5YCxvByQtDP1xPJntBZdCtfh66ZrEkv2hSPE1fXRyXLOKwR6E0TOD1faCbEloMQJ
IU3JJNzaSZghHUwUgolf3D1MKrYKG2KZZ/Iql8h8qoKFEf43ngLVeaSOgT1ste1qMAmxna6qLRIJ
ZKCJNoMGcAVUBoKkjJWDg/pZIPbXhO0eAABFUYW1oSLhpUhfZSenx4swaC3Bz7VK4DWY5gVrCCfK
/VN4W2gnSmxuec0qLbpGZMgfsoZ7zFZWlgyLJVCebFBQg16ScmrdEkKc2Z1ELRnhfLO9YJV2ZcBO
K8KUZpirLiyEsV0Psc2hXWsZdsOemLHi3TgMTgzNjLWkCGl76orcNbIElGD5nQpBNBDAlTrnkQq9
6lTIhoGVysrfn4tBnwzEGQqVWpvE2m2AI6JIlFSdumuco1vC6NaI24BR0EFUtR0C214qWqVUtVmB
/Jp686QIlGTMwY00D6KyREOVaU2W7KVVTHCOo1cJ5CTI25dUnnmEl0yAHWBfmkLtgtkKrxznNK5I
EYUt2XNtIRiEwZWPFAk3VAQYosHSGBgygySFjVkB7JzsxuV1YrJqwlZZBp0HhzCStZEiWWkBk3Jm
BogqWOLhDzUsLyRcJ1vYLR2U2WGO7Xj8EipKIawIcKA/4u5IpwoSAhPvCsA=

--Boundary-00=_XwwbBGSvvgBHyZi--


From khk@khk.net  Fri Oct 15 01:15:16 2004
From: khk@khk.net (Karl Heinz Kremer)
Date: Thu, 14 Oct 2004 20:15:16 -0400
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <200410141930.32684.mreuther@umich.edu>
References: <200410132249.08934.mreuther@umich.edu> <200410141257.21475.mreuther@umich.edu> <20041014173205.GF12141@meier-geinitz.de> <200410141930.32684.mreuther@umich.edu>
Message-ID: <4A35F8D0-1E3F-11D9-820C-000A957E40E8@khk.net>

It looks like this scanner does not "speak" the ESC/I protocol. At 
least not any flavor that the EPSON backend supports. Maybe Olaf can 
shed some light on this.

Karl Heinz


On Oct 14, 2004, at 7:30 PM, Matt Reuther wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thursday 14 October 2004 01:32 pm, Henning Meier-Geinitz wrote:
>
> [SNIP]
>
>> Ok. Just to be safe, comment out "v4l" in dll.conf.
>
> Done.
>
> [SNIP]
>
>> If you start gimp from a console window, I guess you would have seen
>> an error message or even a debug trace.
>>
>> The log still points to reading the option descriptor but I'm not sure
>> if it's an xsane or epson backend problem.
>
> I ran gimp from the console and captured a log. It's attached. All I 
> did in
> gimp was pick File -> Acquire -> Xsane: epson:libusb:004:002, and then
> quit.
>
>> Checking if it happens with scanimage may help.
>>
>> Try something like
>> export SANE_DEBUG_EPSON=255
>> scanimage -d epson -y 50 -x 50 >/tmp/image.pnm 2>log
>
> I did this and attached the output.
>
>> If it's an xsane problem, setting XSANE_DEBUG=something may also help.
>> However, that can create "insane" amounts of logs.
>
> Let me know if you want me to try this.
>
>> Bye,
>>   Henning
>
> Matt
> - --
> Matt Reuther
> mreuther@umich.edu
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFBbwwXFse4xrb7oagRAnAYAKD6ONSmY12lFijcOxMYa0EgPX29XwCfReot
> RNpjsAqHKVYzK3RfUukRTSY=
> =UUEv
> -----END PGP SIGNATURE-----
> <scanimagelog-epson4180.txt.bz2><gimplog-epson4180.txt.bz2>



From olaf@epkowa.co.jp  Fri Oct 15 02:37:39 2004
From: olaf@epkowa.co.jp (Olaf Meeuwissen)
Date: Fri, 15 Oct 2004 10:37:39 +0900
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <4A35F8D0-1E3F-11D9-820C-000A957E40E8@khk.net> (Karl Heinz
 Kremer's message of "Thu, 14 Oct 2004 20:15:16 -0400")
References: <200410132249.08934.mreuther@umich.edu>
 <200410141257.21475.mreuther@umich.edu>
 <20041014173205.GF12141@meier-geinitz.de>
 <200410141930.32684.mreuther@umich.edu>
 <4A35F8D0-1E3F-11D9-820C-000A957E40E8@khk.net>
Message-ID: <87u0sw3gnw.fsf@zen.epkowa.co.jp>

Karl Heinz Kremer <khk@khk.net> writes:

> It looks like this scanner does not "speak" the ESC/I protocol. At
> least not any flavor that the EPSON backend supports. Maybe Olaf can
> shed some light on this.

I guess I could ;-)

As the EPSON drivers say, this is a GT-F600.  It does not speak ESC/I.
It will be supported by iscan's epkowa backend in the near future (but
first we'll get a release for a bunch of all-in-ones).

FYI, it is closely related to the GT-9400 (Perfection 3170 PHOTO)
which is supported as of iscan-1.6.0.
 
> On Oct 14, 2004, at 7:30 PM, Matt Reuther wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On Thursday 14 October 2004 01:32 pm, Henning Meier-Geinitz wrote:
>>
>> [SNIP]
>>
>>> Ok. Just to be safe, comment out "v4l" in dll.conf.
>>
>> Done.
>>
>> [SNIP]
>>
>>> If you start gimp from a console window, I guess you would have seen
>>> an error message or even a debug trace.
>>>
>>> The log still points to reading the option descriptor but I'm not sure
>>> if it's an xsane or epson backend problem.
>>
>> I ran gimp from the console and captured a log. It's attached. All I
>> did in
>> gimp was pick File -> Acquire -> Xsane: epson:libusb:004:002, and then
>> quit.
>>
>>> Checking if it happens with scanimage may help.
>>>
>>> Try something like
>>> export SANE_DEBUG_EPSON=255
>>> scanimage -d epson -y 50 -x 50 >/tmp/image.pnm 2>log
>>
>> I did this and attached the output.
>>
>>> If it's an xsane problem, setting XSANE_DEBUG=something may also help.
>>> However, that can create "insane" amounts of logs.
>>
>> Let me know if you want me to try this.
>>
>>> Bye,
>>>   Henning
>>
>> Matt
>> - --
>> Matt Reuther
>> mreuther@umich.edu
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.4 (GNU/Linux)
>>
>> iD8DBQFBbwwXFse4xrb7oagRAnAYAKD6ONSmY12lFijcOxMYa0EgPX29XwCfReot
>> RNpjsAqHKVYzK3RfUukRTSY=
>> =UUEv
>> -----END PGP SIGNATURE-----
>> <scanimagelog-epson4180.txt.bz2><gimplog-epson4180.txt.bz2>
>

-- 
Olaf Meeuwissen                            EPSON KOWA Corporation, PF1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2


From olaf@epkowa.co.jp  Fri Oct 15 02:43:18 2004
From: olaf@epkowa.co.jp (Olaf Meeuwissen)
Date: Fri, 15 Oct 2004 10:43:18 +0900
Subject: [sane-devel] saned array memory limit
In-Reply-To: <87fz4hqbii.fsf@frigate.technologeek.org> (Julien BLACHE's
 message of "Thu, 14 Oct 2004 22:40:21 +0200")
References: <20041014172115.GE12141@meier-geinitz.de>
 <87oej5qgea.fsf@frigate.technologeek.org>
 <20041014185842.GG12141@meier-geinitz.de>
 <87fz4hqbii.fsf@frigate.technologeek.org>
Message-ID: <87pt3k3geh.fsf@zen.epkowa.co.jp>

Julien BLACHE <jb@jblache.org> writes:

> Henning Meier-Geinitz <henning@meier-geinitz.de> wrote:

>> I have already thought about using automake to generate the makefiles
>> but I guess we would need lots of special rules at least for backend/.
>
> Yes, it'd take some time to get it up & running...

Hmm, iscan still uses the build infra-structure (Makefile.in etc) from
sane-backends, but in my free time I've switched it over to use
automake (and I'm trying to get it included in our official releases).

Maybe, just maybe, I could see if generalising to multiple backends is
feasible.  Let me know if you're interested.

BTW, I'll also try to update epkowa.desc before sane-backends-1.0.15
comes out.
-- 
Olaf Meeuwissen                            EPSON KOWA Corporation, PF1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2


From thetargos@slackercentral.com  Fri Oct 15 04:09:44 2004
From: thetargos@slackercentral.com (Gian Paolo Mureddu)
Date: Thu, 14 Oct 2004 22:09:44 -0500
Subject: [sane-devel] UMAX 2000 (HP3200c) scanner problems
In-Reply-To: <20041014190946.GA2675@wanadoo.fr>
References: <416DCC27.7010303@tutopia.com> <20041014190946.GA2675@wanadoo.fr>
Message-ID: <416F3F78.90401@slackercentral.com>

This is a multi-part message in MIME format.
--------------050705070004090704050802
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

svoltz@wanadoo.fr wrote:

>On Wed, Oct 13, 2004 at 07:45:27PM -0500, Gian Paolo Mureddu wrote:
>  
>
>>I had my UMAX 2000 branded HP 3200c (Parallel port) scanner working with 
>>SANE just fine after I edited the /etc/sane.d/dll.conf file to also look 
>>for this scanner, however (I don't know if it was coincidence or not, or 
>>if it has to do with the problem or not) after I upgreded my 
>>distribution (FC2) especially the GIMP to version 2.0.5 from 2.0.4, I 
>>could scan an image just fine, however while working on the scanned 
>>image (not yet saved) GIMP crashed (while xsane was still running). I 
>>tried to re-open xsane through GIMP, but xsane could not find my scanner 
>>anymore. When I tried running xsane or scanimage from the command line I 
>>get this output:
>>
>>[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3281)
>>[umax_pp_low] Blindly going on .....
>>[umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3933)
>>[umax_pp_low] Blindly going on .....
>>[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3281)
>>[umax_pp_low] Blindly going on .....
>>[umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3933)
>>[umax_pp_low] Blindly going on .....
>>[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3281)
>>[umax_pp_low] Blindly going on .....
>>[umax_pp_low] Unexpected reg19: 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3980)
>>[umax_pp_low] CmdSetDataBuffer(initbuf) failed ! (umax_pp_low.c:5950)
>>scanimage: no SANE devices found
>>
>>What does this mean?
>>
>>Just for reference, the way I have setup the scanner is as follows: The 
>>scanner is attached to my Zip drive (parallel port also) which is 
>>connected to the parallel port (lp0)  on the computer, no printer is 
>>setup in the parallel port (I use an USB one). The parallel port is set 
>>to ECP and at an auto configured port in BIOS. Could this configuration 
>>be the conflicting point, even though it *was* working right? What can I 
>>do to have it working again?
>>
>>Thanks in advance for any input.
>>
>>    
>>
>
>	When you get 0xE8 or 0xD8 values, the scanner's ASIC is confused
>and needs resetting. It can be done by powering off the scanner, unplugging
>the parallel port cable, plugging it back then powering on. 
>	The ASIC gets confused each time a command in progress fails, in your
>case it's certainly caused by the GIMP crash wich prevented the the backend
>to finish cleanly the scan.
>
>Regards,
>	Stef
>
>
>  
>
Thanks, I pretty much discovered this on my own when I went to the UMAX 
backend site... That was exactly what I did: unplug the scanner power 
supply, unplug the parallel cable and then replug everything in reversed 
order (parallel, power) and the scanner worked again. Thanks for the 
additional information, much appreciated!!

--------------050705070004090704050802
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="mailto:svoltz@wanadoo.fr">svoltz@wanadoo.fr</a> wrote:
<blockquote cite="mid20041014190946.GA2675@wanadoo.fr" type="cite">
  <pre wrap="">On Wed, Oct 13, 2004 at 07:45:27PM -0500, Gian Paolo Mureddu wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">I had my UMAX 2000 branded HP 3200c (Parallel port) scanner working with 
SANE just fine after I edited the /etc/sane.d/dll.conf file to also look 
for this scanner, however (I don't know if it was coincidence or not, or 
if it has to do with the problem or not) after I upgreded my 
distribution (FC2) especially the GIMP to version 2.0.5 from 2.0.4, I 
could scan an image just fine, however while working on the scanned 
image (not yet saved) GIMP crashed (while xsane was still running). I 
tried to re-open xsane through GIMP, but xsane could not find my scanner 
anymore. When I tried running xsane or scanimage from the command line I 
get this output:

[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3281)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3933)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3281)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3933)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3281)
[umax_pp_low] Blindly going on .....
[umax_pp_low] Unexpected reg19: 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3980)
[umax_pp_low] CmdSetDataBuffer(initbuf) failed ! (umax_pp_low.c:5950)
scanimage: no SANE devices found

What does this mean?

Just for reference, the way I have setup the scanner is as follows: The 
scanner is attached to my Zip drive (parallel port also) which is 
connected to the parallel port (lp0)  on the computer, no printer is 
setup in the parallel port (I use an USB one). The parallel port is set 
to ECP and at an auto configured port in BIOS. Could this configuration 
be the conflicting point, even though it *was* working right? What can I 
do to have it working again?

Thanks in advance for any input.

    </pre>
  </blockquote>
  <pre wrap=""><!---->
	When you get 0xE8 or 0xD8 values, the scanner's ASIC is confused
and needs resetting. It can be done by powering off the scanner, unplugging
the parallel port cable, plugging it back then powering on. 
	The ASIC gets confused each time a command in progress fails, in your
case it's certainly caused by the GIMP crash wich prevented the the backend
to finish cleanly the scan.

Regards,
	Stef


  </pre>
</blockquote>
Thanks, I pretty much discovered this on my own when I went to the UMAX
backend site... That was exactly what I did: unplug the scanner power
supply, unplug the parallel cable and then replug everything in
reversed order (parallel, power) and the scanner worked again. Thanks
for the additional information, much appreciated!!<br>
</body>
</html>

--------------050705070004090704050802--


From livhu.tshisikule@telkomsa.net  Fri Oct 15 11:44:58 2004
From: livhu.tshisikule@telkomsa.net (Livhu Tshisikule)
Date: Fri, 15 Oct 2004 12:44:58 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
Message-ID: <200410151244.58949.livhu.tshisikule@telkomsa.net>

Hi,

I am a newbie to SANE, I have an Olivetti Job_Jet M400 (MFP) connected to a 
machine running Fedora 2. (I am also new to Linux but have Unix experience), 
at the moment I can only print but not scan. (It is powered by HP, I think it 
must be compatible to an HP scanner).

I have been searching the net without any luck. Can somebody help? 

Regards 
Livhu Tshisikule



From cnorton@biosensorhawaii.com  Thu Oct 14 16:12:10 2004
From: cnorton@biosensorhawaii.com (Chris Norton)
Date: Thu, 14 Oct 2004 11:12:10 -0400
Subject: [sane-devel] XEROX 620S SCSI Scanner.
In-Reply-To: <20041014122928.GD12141@meier-geinitz.de>
References: <1097680994.2078.7.camel@superman.biosensorhawaii.com>
 <20041014122928.GD12141@meier-geinitz.de>
Message-ID: <1097766730.2130.9.camel@superman.biosensorhawaii.com>

Thanks for reply.  The output is below.  With some direction I may be
able to make a back-end driver but right now I'm not sure where to
start.

Thanks for your help,

Chris
[nei@localhost nei]$ sane-find-scanner  -v -v 
 
searching for SCSI scanners: 
checking /dev/scanner... open ok 
  Inquiry for device: 
    000: 06 00 02 02 27 00 00 30 58 45 52 4f 58 20 20 
20    ....'..0XEROX 
    016: 44 6f 63 75 49 6d 61 67 65 36 32 30 53 20 20 20    
DocuImage620S 
    032: 30 30 30 31 01 27 00 56 20 00 00 0e                
0001.'.V ... 
found SCSI scanner "XEROX DocuImage620S 0001" 
at /dev/scanner 
checking /dev/sg0... open ok 
  Inquiry for device: 
    000: 06 00 02 02 27 00 00 30 58 45 52 4f 58 20 20 
20    ....'..0XEROX 
    016: 44 6f 63 75 49 6d 61 67 65 36 32 30 53 20 20 20    
DocuImage620S 
    032: 30 30 30 31 01 27 00 56 20 00 00 0e                
0001.'.V ... 
found SCSI scanner "XEROX DocuImage620S 0001" at /dev/sg0 
checking /dev/sg1... failed to open (Invalid argument) 
checking /dev/sg2... failed to open (Invalid argument) 
checking /dev/sg3... failed to open (Invalid argument) 
checking /dev/sg4... failed to open (Invalid argument) 
checking /dev/sg5... failed to open (Invalid argument) 
checking /dev/sg6... failed to open (Invalid argument) 
checking /dev/sg7... failed to open (Invalid argument) 
checking /dev/sg8... failed to open (Invalid argument) 
checking /dev/sg9... failed to open (Invalid argument) 
checking /dev/sga... failed to open (Invalid argument) 
checking /dev/sgb... failed to open (Invalid argument) 
checking /dev/sgc... failed to open (Invalid argument) 
checking /dev/sgd... failed to open (Invalid argument) 
checking /dev/sge... failed to open (Invalid argument) 
checking /dev/sgf... failed to open (Invalid argument) 
checking /dev/sgg... failed to open (Invalid argument) 
checking /dev/sgh... failed to open (Invalid argument) 
checking /dev/sgi... failed to open (Invalid argument) 
checking /dev/sgj... failed to open (Invalid argument) 
checking /dev/sgk... failed to open (Invalid argument) 
checking /dev/sgl... failed to open (Invalid argument) 
checking /dev/sgm... failed to open (Invalid argument) 
checking /dev/sgn... failed to open (Invalid argument) 
checking /dev/sgo... failed to open (Invalid argument) 
checking /dev/sgp... failed to open (Invalid argument) 
checking /dev/sgq... failed to open (Invalid argument) 
checking /dev/sgr... failed to open (Invalid argument) 
checking /dev/sgs... failed to open (Invalid argument) 
checking /dev/sgt... failed to open (Invalid argument) 
checking /dev/sgu... failed to open (Invalid argument) 
checking /dev/sgv... failed to open (Invalid argument) 
checking /dev/sgw... failed to open (Invalid argument) 
checking /dev/sgx... failed to open (Invalid argument) 
checking /dev/sgy... failed to open (Invalid argument) 
checking /dev/sgz... failed to open (Invalid argument) 
  # Your SCSI scanner was detected. It may or may not be 
supported by SANE. Try 
  # scanimage -L and read the backend's manpage. 
 
searching for USB scanners: 
checking /dev/usb/scanner... failed to open (Invalid 
argument) 
checking /dev/usb/scanner0... failed to open (Invalid 
argument) 
checking /dev/usb/scanner1... failed to open (Invalid 
argument) 
checking /dev/usb/scanner2... failed to open (Invalid 
argument) 
checking /dev/usb/scanner3... failed to open (Invalid 
argument) 
checking /dev/usb/scanner4... failed to open (Invalid 
argument) 
checking /dev/usb/scanner5... failed to open (Invalid 
argument) 
checking /dev/usb/scanner5... failed to open (Invalid 
argument) 
checking /dev/usb/scanner7... failed to open (Invalid 
argument) 
checking /dev/usb/scanner8... failed to open (Invalid 
argument) 
checking /dev/usb/scanner9... failed to open (Invalid 
argument) 
checking /dev/usb/scanner10... failed to open (Invalid 
argument) 
checking /dev/usb/scanner11... failed to open (Invalid 
argument) 
checking /dev/usb/scanner12... failed to open (Invalid 
argument) 
checking /dev/usb/scanner13... failed to open (Invalid 
argument) 
checking /dev/usb/scanner14... failed to open (Invalid 
argument) 
checking /dev/usb/scanner15... failed to open (Invalid 
argument) 
checking /dev/usbscanner... failed to open (Invalid 
argument) 
checking /dev/usbscanner0... failed to open (Invalid 
argument) 
checking /dev/usbscanner1... failed to open (Invalid 
argument) 
checking /dev/usbscanner2... failed to open (Invalid 
argument) 
checking /dev/usbscanner3... failed to open (Invalid 
argument) 
checking /dev/usbscanner4... failed to open (Invalid 
argument) 
checking /dev/usbscanner5... failed to open (Invalid 
argument) 
checking /dev/usbscanner6... failed to open (Invalid 
argument) 
checking /dev/usbscanner7... failed to open (Invalid 
argument) 
checking /dev/usbscanner8... failed to open (Invalid 
argument) 
checking /dev/usbscanner9... failed to open (Invalid 
argument) 
checking /dev/usbscanner10... failed to open (Invalid 
argument) 
checking /dev/usbscanner11... failed to open (Invalid 
argument) 
checking /dev/usbscanner12... failed to open (Invalid 
argument) 
checking /dev/usbscanner13... failed to open (Invalid 
argument) 
checking /dev/usbscanner14... failed to open (Invalid 
argument) 
checking /dev/usbscanner15... failed to open (Invalid 
argument) 
trying libusb: 
 
<device descriptor of 0x0000/0x0000 at 002:001 (Linux 
2.6.3-7mdk uhci_hcd UHCI H 
ost Controller)> 
bLength               18 
bDescriptorType       1 
bcdUSB                1.10 
bDeviceClass          9 
bDeviceSubClass       0 
bDeviceProtocol       0 
bMaxPacketSize0       8 
idVendor              0x0000 
idProduct             0x0000 
bcdDevice             2.06 
iManufacturer         3 (Linux 2.6.3-7mdk uhci_hcd) 
iProduct              2 (UHCI Host Controller) 
iSerialNumber         1 (0000:00:1f.4) 
bNumConfigurations    1 
 <configuration 0> 
 bLength              9 
 bDescriptorType      2 
 wTotalLength         25 
 bNumInterfaces       1 
 bConfigurationValue  1 
 iConfiguration       0 () 
 bmAttributes         64 (Self-powered) 
 MaxPower             0 mA 
  <interface 0> 
   <altsetting 0> 
   bLength            9 
   bDescriptorType    4 
   bInterfaceNumber   0 
   bAlternateSetting  0 
   bNumEndpoints      1 
   bInterfaceClass    9 
   bInterfaceSubClass 0 
   bInterfaceProtocol 0 
   iInterface         0 () 
    <endpoint 0> 
    bLength           7 
    bDescriptorType   5 
    bEndpointAddress  0x81 (in 0x01) 
    bmAttributes      3 (interrupt) 
    wMaxPacketSize    2 
    bInterval         255 ms 
    bRefresh          0 
    bSynchAddress     0 
 
<device descriptor of 0x0000/0x0000 at 001:001 (Linux 
2.6.3-7mdk uhci_hcd UHCI H 
ost Controller)> 
bLength               18 
bDescriptorType       1 
bcdUSB                1.10 
bDeviceClass          9 
bDeviceSubClass       0 
bDeviceProtocol       0 
bMaxPacketSize0       8 
idVendor              0x0000 
idProduct             0x0000 
bcdDevice             2.06 
iManufacturer         3 (Linux 2.6.3-7mdk uhci_hcd) 
iProduct              2 (UHCI Host Controller) 
iSerialNumber         1 (0000:00:1f.2) 
bNumConfigurations    1 
 <configuration 0> 
 bLength              9 
 bDescriptorType      2 
 wTotalLength         25 
 bNumInterfaces       1 
 bConfigurationValue  1 
 iConfiguration       0 () 
 bmAttributes         64 (Self-powered) 
 MaxPower             0 mA 
  <interface 0> 
   <altsetting 0> 
   bLength            9 
   bDescriptorType    4 
   bInterfaceNumber   0 
   bAlternateSetting  0 
   bNumEndpoints      1 
   bInterfaceClass    9 
   bInterfaceSubClass 0 
   bInterfaceProtocol 0 
   iInterface         0 () 
    <endpoint 0> 
    bLength           7 
    bDescriptorType   5 
    bEndpointAddress  0x81 (in 0x01) 
    bmAttributes      3 (interrupt) 
    wMaxPacketSize    2 
    bInterval         255 ms 
    bRefresh          0 
    bSynchAddress     0 
  # No USB scanners found. If you expected something 
different, make sure that 
  # you have loaded a driver for your USB host controller 
and have installed a 
  # kernel scanner module. 
 
  # Scanners connected to the parallel port or other 
proprietary ports can't be 
  # detected by this program. 
 
  # You may want to run this program as root to find all 
devices. Once you 
  # found the scanner devices, be sure to adjust access 
permissions as 
  # necessary. 
done 
[nei@localhost nei]$ 
 



On Thu, 2004-10-14 at 08:29, Henning Meier-Geinitz wrote:
> Hi,
> 
> On Wed, Oct 13, 2004 at 11:23:14AM -0400, Chris Norton wrote:
> > Is there any support for a XEROX D620S SCSI Scanner through sane?
> 
> It's not mentioned in our lists so: probably no.
> 
> > I'm using Mandrake linux and with a Adaptec 2940 card.  sane-scan-finder
> > finds the Xerox scanner on /dev/sg0.
> 
> Could you show us the output of "sane-find-scanner -v -v"?
> 
> > Under windows 98 the Twain and ISIS drivers worked without any
> > additional software. The point is that it appeared to be Twain and ISIS
> > compliant.
> 
> "TWAIN"-compliant doesn't mean anything. It's not a scanner standard
> but a software interface standard. You still need a TWAIN driver for
> each different scanner.
> 
> What is "ISIS"?
> 
> > I really would like to use this scanner with linux. It's the only reason
> > I still have windows around.
> 
> Start writing a backend (=driver). This is not a joke. Drivers for
> (older) SCSI scanners are usually easier than for the newer dumb USB
> devices.
> 
> Bye,
>   Henning



From henning@meier-geinitz.de  Fri Oct 15 12:57:57 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 15 Oct 2004 13:57:57 +0200
Subject: [sane-devel] XEROX 620S SCSI Scanner.
In-Reply-To: <1097766730.2130.9.camel@superman.biosensorhawaii.com>
References: <1097680994.2078.7.camel@superman.biosensorhawaii.com> <20041014122928.GD12141@meier-geinitz.de> <1097766730.2130.9.camel@superman.biosensorhawaii.com>
Message-ID: <20041015115757.GA3623@meier-geinitz.de>

Hi,

On Thu, Oct 14, 2004 at 11:12:10AM -0400, Chris Norton wrote:
> Thanks for reply.  The output is below. 

Thanks. I'll add your scanner to our lists as "unsupported".

> With some direction I may be
> able to make a back-end driver but right now I'm not sure where to
> start.

http://www.sane-project.org/contrib.html

Bye,
  Henning


From henning@meier-geinitz.de  Fri Oct 15 13:08:14 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 15 Oct 2004 14:08:14 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <200410151244.58949.livhu.tshisikule@telkomsa.net>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net>
Message-ID: <20041015120814.GB3623@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 12:44:58PM +0200, Livhu Tshisikule wrote:
> I am a newbie to SANE, I have an Olivetti Job_Jet M400 (MFP) connected to a 
> machine running Fedora 2. (I am also new to Linux but have Unix experience), 
> at the moment I can only print but not scan. (It is powered by HP, I think it 
> must be compatible to an HP scanner).

If it's really compatible to one of the HP multi function devices, it
may work with the hpoj SANE backend.

> I have been searching the net without any luck. Can somebody help? 

Please show us the output of "sane-find-scanner -v -v" when the
scanner is plugged in.

Bye,
  Henning


From livhu.tshisikule@telkomsa.net  Fri Oct 15 13:47:15 2004
From: livhu.tshisikule@telkomsa.net (Livhu Tshisikule)
Date: Fri, 15 Oct 2004 14:47:15 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <20041015120814.GB3623@meier-geinitz.de>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net> <20041015120814.GB3623@meier-geinitz.de>
Message-ID: <200410151447.15977.livhu.tshisikule@telkomsa.net>

Hi,

searching for SCSI scanners:
checking /dev/scanner... failed to open (Invalid argument)
checking /dev/sg0... failed to open (Invalid argument)
checking /dev/sg1... failed to open (Invalid argument)
checking /dev/sg2... failed to open (Invalid argument)
checking /dev/sg3... failed to open (Invalid argument)
checking /dev/sg4... failed to open (Invalid argument)
checking /dev/sg5... failed to open (Invalid argument)
checking /dev/sg6... failed to open (Invalid argument)
checking /dev/sg7... failed to open (Invalid argument)
checking /dev/sg8... failed to open (Invalid argument)
checking /dev/sg9... failed to open (Invalid argument)
checking /dev/sga... failed to open (Invalid argument)
checking /dev/sgb... failed to open (Invalid argument)
checking /dev/sgc... failed to open (Invalid argument)
checking /dev/sgd... failed to open (Invalid argument)
checking /dev/sge... failed to open (Invalid argument)
checking /dev/sgf... failed to open (Invalid argument)
checking /dev/sgg... failed to open (Invalid argument)
checking /dev/sgh... failed to open (Invalid argument)
checking /dev/sgi... failed to open (Invalid argument)
checking /dev/sgj... failed to open (Invalid argument)
checking /dev/sgk... failed to open (Invalid argument)
checking /dev/sgl... failed to open (Invalid argument)
checking /dev/sgm... failed to open (Invalid argument)
checking /dev/sgn... failed to open (Invalid argument)
checking /dev/sgo... failed to open (Invalid argument)
checking /dev/sgp... failed to open (Invalid argument)
checking /dev/sgq... failed to open (Invalid argument)
checking /dev/sgr... failed to open (Invalid argument)
checking /dev/sgs... failed to open (Invalid argument)
checking /dev/sgt... failed to open (Invalid argument)
checking /dev/sgu... failed to open (Invalid argument)
checking /dev/sgv... failed to open (Invalid argument)
checking /dev/sgw... failed to open (Invalid argument)
checking /dev/sgx... failed to open (Invalid argument)
checking /dev/sgy... failed to open (Invalid argument)
checking /dev/sgz... failed to open (Invalid argument)
  # No SCSI scanners found. If you expected something different, make sure 
that
  # you have loaded a SCSI driver for your SCSI adapter.

searching for USB scanners:
checking /dev/usb/scanner... failed to open (Invalid argument)
checking /dev/usb/scanner0... failed to open (Invalid argument)
checking /dev/usb/scanner1... failed to open (Invalid argument)
checking /dev/usb/scanner2... failed to open (Invalid argument)
checking /dev/usb/scanner3... failed to open (Invalid argument)
checking /dev/usb/scanner4... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner7... failed to open (Invalid argument)
checking /dev/usb/scanner8... failed to open (Invalid argument)
checking /dev/usb/scanner9... failed to open (Invalid argument)
checking /dev/usb/scanner10... failed to open (Invalid argument)
checking /dev/usb/scanner11... failed to open (Invalid argument)
checking /dev/usb/scanner12... failed to open (Invalid argument)
checking /dev/usb/scanner13... failed to open (Invalid argument)
checking /dev/usb/scanner14... failed to open (Invalid argument)
checking /dev/usb/scanner15... failed to open (Invalid argument)
checking /dev/usbscanner... failed to open (Invalid argument)
checking /dev/usbscanner0... failed to open (Invalid argument)
checking /dev/usbscanner1... failed to open (Invalid argument)
checking /dev/usbscanner2... failed to open (Invalid argument)
checking /dev/usbscanner3... failed to open (Invalid argument)
checking /dev/usbscanner4... failed to open (Invalid argument)
checking /dev/usbscanner5... failed to open (Invalid argument)
checking /dev/usbscanner6... failed to open (Invalid argument)
checking /dev/usbscanner7... failed to open (Invalid argument)
checking /dev/usbscanner8... failed to open (Invalid argument)
checking /dev/usbscanner9... failed to open (Invalid argument)
checking /dev/usbscanner10... failed to open (Invalid argument)
checking /dev/usbscanner11... failed to open (Invalid argument)
checking /dev/usbscanner12... failed to open (Invalid argument)
checking /dev/usbscanner13... failed to open (Invalid argument)
checking /dev/usbscanner14... failed to open (Invalid argument)
checking /dev/usbscanner15... failed to open (Invalid argument)
found USB scanner (vendor=0x0b3c [Olivetti], product=0xa880 [Job_Jet M400]) at 
l
ibusb:003:002
  # Your USB scanner was (probably) detected. It may or may not be supported 
by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Scanners connected to the parallel port or other proprietary ports can't 
be
  # detected by this program.
done

Regards
Livhu Tshisikule



From Oliver.Rauch@Rauch-Domain.DE  Fri Oct 15 15:44:42 2004
From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch)
Date: 15 Oct 2004 16:44:42 +0200
Subject: [sane-devel] Timetable for the release of sane-backends-1.0.15
In-Reply-To: <20041005113202.GG7772@meier-geinitz.de>
References: <20041005113202.GG7772@meier-geinitz.de>
Message-ID: <1097851482.2134.8.camel@Babylon7>

Hello.

I am not able to get access to the CVS server (permission denied).
Please could someone who has acces to the server take a look at that?!

I suggest to delay the feature freeze for some days when this
is not solved soon.

Best regards
Oliver

Am Die, 2004-10-05 um 13.32 schrieb Henning Meier-Geinitz:
> Hi,
> 
> This is the timetable for the release of sane-backends 1.0.15
> 
> 2004-10-17 Feature freeze (snapshot)
> 2004-10-31 Code freeze (snapshot)
> 2004-11-07 Release
> 
> Feature freeze means that only bug fixes and documentation updates are
> allowed. After code freeze only fixes of grave bugs that render a
> backend completely unusable or break compilation and documentation
> updates are accepted.
> 
> If there are any new backends that should be included in that release
> please tell us NOW.
> 
> Please everyone have a look at out growing list of bugs and fix as
> many bugs as possible:
> http://alioth.debian.org/tracker/index.php?group_id=30186&atid=410366
> 
> Or, if the bug report is bogus, close it.
> You can view only bugs assigned to you to reduce the number of visible
> bugs. Having a look at bugs assigned to nobody is also worth a try as
> some bugs affect several backends/maintainers. You can also sort by
> topic ("Summary").
> 
> Bye,
>   Henning



From henning@meier-geinitz.de  Fri Oct 15 13:37:03 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 15 Oct 2004 14:37:03 +0200
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <87u0sw3gnw.fsf@zen.epkowa.co.jp>
References: <200410132249.08934.mreuther@umich.edu> <200410141257.21475.mreuther@umich.edu> <20041014173205.GF12141@meier-geinitz.de> <200410141930.32684.mreuther@umich.edu> <4A35F8D0-1E3F-11D9-820C-000A957E40E8@khk.net> <87u0sw3gnw.fsf@zen.epkowa.co.jp>
Message-ID: <20041015123703.GF3623@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 10:37:39AM +0900, Olaf Meeuwissen wrote:
> Karl Heinz Kremer <khk@khk.net> writes:
> 
> > It looks like this scanner does not "speak" the ESC/I protocol. At
> > least not any flavor that the EPSON backend supports. Maybe Olaf can
> > shed some light on this.
> 
> I guess I could ;-)
> 
> As the EPSON drivers say, this is a GT-F600.  It does not speak ESC/I.
> It will be supported by iscan's epkowa backend in the near future (but
> first we'll get a release for a bunch of all-in-ones).

I've added Perfection 4160 and GT-F600 as unsupported to our lists for
now (with some details from your mail).

Bye,
  Henning


From henning@meier-geinitz.de  Fri Oct 15 13:56:40 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 15 Oct 2004 14:56:40 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <200410151447.15977.livhu.tshisikule@telkomsa.net>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net> <20041015120814.GB3623@meier-geinitz.de> <200410151447.15977.livhu.tshisikule@telkomsa.net>
Message-ID: <20041015125640.GH3623@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 02:47:15PM +0200, Livhu Tshisikule wrote:
> found USB scanner (vendor=0x0b3c [Olivetti], product=0xa880 [Job_Jet M400]) at libusb:003:002

Thanks. 0x03bc is really Olivetti so they haven't just used a HP
device and printed a new logo on the case.

So I guess it won't work with hpoj without source code changes (if at
all).

Could you rerun sane-find-scanner and use "-v -v" (very verbose) this
time?

Bye,
  Henning



From johannes@sipsolutions.net  Fri Oct 15 14:47:40 2004
From: johannes@sipsolutions.net (Johannes Berg)
Date: Fri, 15 Oct 2004 15:47:40 +0200
Subject: [sane-devel] [BUG] saned: missing input sanitization
Message-ID: <1097848060.4219.2.camel@johannes>

--=-4jUAPFROJACgVt5tWrHO
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

SANE_NET_OPEN makes saned segfault if a NULL name is passed, because it
tries to strdup() the name without checking for !=3D NULL.

johannes

--=-4jUAPFROJACgVt5tWrHO
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (SIP Solutions)

iQIVAwUAQW/U+aVg1VMiehFYAQIJ2xAAsItDNAE6jskDUoOptNrxmwvxMdjooCpx
haff88AIuXjKgWjsG27BxoLJJhw5v3S9uRLbOCx0q0oD4uIY1QuauBbncvIWlpS0
cqkEc2smmvDXyRP/uikIJGMaf9h45MuYttCBx9Irb+TZlc9X5IldReZBO2s7zMO+
M10MlPzwlJ8jEaQIykHTreEiLvj12WC+e7vTDM9K4uwwsU4/Ili8gm7v6Zs3aJ/Q
OEAZCTOPSXs+QYKi82E2souhh2eCt23HLWzn3Kt/G6FxakwJ26zGmySs5N0kItKL
0OGKQ4VYUS0w+nADJgFMm5CcB808yxm8WulONDlkIRybFghsbnfcxoPaKwMUGki7
00L9XlDmK6OBkalBpQ5h2rANEuw/QQET8kaChg3jA0PrSTTnJvgGt+mByAazzIOw
kVeIl0+AxZfMmsVvJdZzICnCDCrIj5YmHC7Vb5EeuO3XdkPifDEVQshL/z4AHoUQ
y6IbdndVfNie2DTedmRBB3/tsJx2ksZpR7mRAhpKv9bnKZyK7ppyWPkI1+brGBhb
RsV+I1TBz6KXAACumZ2CV+DwXx8l/EFdti16OfGdhRzMGjqkfGE7eZLDxOfv/INt
BSZ39j+ip6Sd1upA7VseidtJ48S8NNZNfm55nmH7ALjd+lcbLORGiHXDZazH5/FQ
2fOfBK6EVVM=
=s1YX
-----END PGP SIGNATURE-----

--=-4jUAPFROJACgVt5tWrHO--




From johannes@sipsolutions.net  Fri Oct 15 14:47:06 2004
From: johannes@sipsolutions.net (Johannes Berg)
Date: Fri, 15 Oct 2004 15:47:06 +0200
Subject: [sane-devel] possible bin_w_string security issue (not)
Message-ID: <1097848026.4219.0.camel@johannes>

--=-8KpxnP81NRNqGGtcVgwN
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I was going to write a mail without the "(not)" but then discovered that
this issue is actually a non-issue, but this is totally non-obvious.

Would you know off-hand why?

bin_w_string contains the following code:

  if (w->direction =3D=3D WIRE_DECODE)
    {
      if (len =3D=3D 0)
        *s =3D 0;
      else if (w->status =3D=3D 0)
        *(*s + len - 1) =3D '\0';
    }

If I interpret the code correctly, this could be used to bring the
server (running the binary protocol) into an invalid state:

1) send any kind of request that requires a string option at the end,
   for example SANE_NET_AUTHORIZE
2) tell the server that the length is 10 or so
3) send 9 bytes and close the connection

The server will react to this in the following way (if I interpret the
code correctly):
* during sanei_w_array it will notice that the status is
   bad and return
* bin_w_string will not(!) zero-terminate the string
   (because it is assuming that *s is not valid, while
   it actually is)
   sanei_w_array doesn't clear the array if anything
   item fails to read.
* now, the server has a password string that is not zero terminated,
   and strcpy()s that string accessing memory beyond the allocated size.


[Actually, I discovered this while I was documenting the wire protocol.
I think it is overly complex and the code badly structured, the wire's
direction thing is really strange!]





Ok, so here's the solution:

The server does
  signal (SIGPIPE, quit);

(which I think is actually another bug, why should sane_close,
sane_exit, sanei_w_exit and lots of other functions be async signal
safe?)

Still, this is that non-obvious that someone writing a server (or
client, which could then be attacked by a malevolent server) with the
sanei library functions could easily oversee this detail, ignore SIGPIPE
or use sockets that don't raise it.

Therefore I'm still sending this mail in hope that someone fixes the
sanei_w_array function to check for status !=3D 0 and clean up after
itself.

johannes

--=-8KpxnP81NRNqGGtcVgwN
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (SIP Solutions)

iQIVAwUAQW/U16Vg1VMiehFYAQItGRAApmPf+qNwUfTzFswVVe1K10VSArYVmcOJ
1wN5J3zAhf9oC7gSavY5q2Y5gCZoyCj2+p+iSWf3sjDAV2+RH8WVIS34IItamOC8
zyj9g8/NgHtaF99tTi7/O2j0/3eMvr9t4/dipDZ7l83EI7C0ZYv2CsGX97dmdXf8
HPJo/9Tl4DA+UsBGMngGsj7flVrjf2zThkJzcPqEAgLv8v2Mv4LW5JNtxZIozgGM
LvLdRgYS7SVtt+owY+2bSLdW3V0dYp/QXwqHNXSvZfFHe1FT9AVZBwvF1573J14v
t+T3AwNV/qRxZC4d/0VD6JsPWJA11HFA3agutUK4TN1G10lH+1BkmoM8NXVWWy9p
9jh1G8FsQsPmnV1WGY6jy6JF4rFLARrjfCIefcDKQt5kEC8s9eMiT0+wayvUYZRr
bhO6oOgunMoPpNX3AxyvDhwzZ1uZmoied7QY+C783pY7kIWtZ45mFFCsznnX6FFN
jwhFjubDeyK03SxTzit7KsBy89wTLXqQIaKKR2IqXc9KlXEUp/UGMoEsQSjBBKth
pUSlKymbhp9kSni0DZ8LGX/G9gYhnK0yMxNUYVzBnp8GWuqC/IO/aHX2rR8n0y+W
ztf389uXOpGU7EHKRPW4NfHuzvnW2CZBN9/ReXwkrMPT4K3enB8dAsh3ipj7Ruzh
FaYv+5kkYgU=
=867r
-----END PGP SIGNATURE-----

--=-8KpxnP81NRNqGGtcVgwN--




From johannes@sipsolutions.net  Fri Oct 15 15:03:04 2004
From: johannes@sipsolutions.net (Johannes Berg)
Date: Fri, 15 Oct 2004 16:03:04 +0200
Subject: [sane-devel] saned/sanei net bug
Message-ID: <1097848984.4219.3.camel@johannes>

--=-b6utnWCS15VlnOe3728l
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

somehow saned/the sanei network layer seem to get buffering wrong.

For example, I send the following:

SANE_NET_INIT
SANE_NET_GET_DEVICES
SANE_NET_EXIT

If I don't wait for the result from SANE_NET_GET_DEVICES before sending
the control code for SANE_NET_EXIT, then the SANE_NET_EXIT code is
discarded.
I would assume that somewhere there's a buffering problem and the old
buffer is simply dropped when the direction is changed or something.

The following works:
(echo  -n -e \\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00 ;
sleep .1 ; echo -n -e \\00\\00\\x00\\x01 ; sleep 1 ;
echo -en \\x00\\x00\\x00\\x0A ) | nc localhost 6566 -q 1 | hd

while this doesn't:
(echo  -n -e \\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00 ;
sleep .1 ; echo -n -e \\00\\00\\x00\\x01\\x00\\x00\\x00\\x0A
)| nc localhost 6566 -q 1 | hd

I think this is extremely counter-intuitive. TCP never guarantees
message boundaries, so one wouldn't think that data is explicitly read
by the application but then discarded.

johannes

--=-b6utnWCS15VlnOe3728l
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (SIP Solutions)

iQIVAwUAQW/YlaVg1VMiehFYAQLFPg//WIumi+9ZBodt1Ns31jdYGEiJa5z0hvkx
RivmO96L+BnL6Ld7Rut2mWx7ftE88yEhWnyzwBj3eFYseXi72n/2E12dpzyKyx+d
4ASxTTeatA/50Prdn2VzaPNe4zccKFpTJdYM7AXYDq3E49XyBrQ0fzin+rCaW0Pd
hjhD+bzzVuWxFxSgTsQn8T9z8h43W5BcUdD+a9fxZZMwRapXaFhTiFCTBxNH2zSI
yHCa7+Kx8xsGoTjsMt3BiggIn0k0ofNaSzht8BaYR0uelnKDEHrj+JdJgpfOz8OK
KcX3gPhsL5JdT4KbmuGyuJSkhZ9gdOGmneBkpX5WB/zUBvS8FxBLM0yyiAmqgzF1
rU9oqAg9psQgotkQY+koeJk8WnOHrstxgHX6rUO6Dbg2EIOv5tNDL/QZ1c/CAQY1
gcPf67was/FbFQ/WDhgyd4C3WdMDnaMrC9WZwIk1klxj6gFz0RqzcQbF97+s+OX0
yAgdl2V3b2SuYW9x9oojshxA6NN+yd3WrIhWxFFlOxkxrdoE1WGlPGwUvQwcVBja
KArLPRV4eHM6c8T0RyK6XWfC2aCOZ004EzTtPyOW8ARZZl026gGXNaF/jlw2L1PN
UiU8+spF5v4pBiQaiYmmEasGaaHmwHYL6oBI6PV2iMjUnFTz4dYM5EgyP3pSKypW
Ph0hiP5wYrc=
=L6hJ
-----END PGP SIGNATURE-----

--=-b6utnWCS15VlnOe3728l--




From johannes@sipsolutions.net  Fri Oct 15 15:03:24 2004
From: johannes@sipsolutions.net (Johannes Berg)
Date: Fri, 15 Oct 2004 16:03:24 +0200
Subject: [sane-devel] weird message configuring sane-frontends
Message-ID: <1097849004.4219.4.camel@johannes>

--=-Vnf8Fxo6iB28eSHM4qG1
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

[configure fails because it can't find sane-config]
"You may need to remove /dev/null before you run configure again."

Clearly, that is not something you want to do.

johannes

--=-Vnf8Fxo6iB28eSHM4qG1
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (SIP Solutions)

iQIVAwUAQW/YqKVg1VMiehFYAQKHHw/8C09hjnDLcF4l9sjKx8exSdTp+zlNoQn6
T7e5wAQ7KOEtMFJmqfE0zbNrYcZx/3u1mq+gqbCAvZNX6wTnVtQ/VHYzHRLw6b8X
TE2ebMFwV9QaF01tr5GilW6uBqtFPEm28Cd9dhN0mpN442FqZ9wG3Ekhx6BfnNLl
OSAu7ln2Eo2c0qI7Txq6vkm+unt/a+xuBD09tRBdMInpMOt+ozUB08LhOtm+iD3a
R0QZd7N6y6vvhndAKw/bvbzYs6asRhO324NLtj0aYJk9PK8fFdUCQj4FRV7lSPRH
55EdLCBzu+K/gGRPvIjzjy0iXhfo+ToKjoAyyAzjBEes28LeiygrpZhx5QdjTqJy
AYcrffYaOqcvawIrAym0PZp/+apkb4fMASERqZsAxoJI+yhUMrBDXe/o7tWhODGe
o+DQXjGIvSMwFZ8Qan2C6mZJoBV57j7qH8S597X8ipFqKO3gsDxDQTc/+NNwWWQ1
EAG4Bf+s5XkVbNpZh+i8/QCs09PmcERyuCqhe6/3D2IdUh+aBMvvVS24dw+oEZCP
6aqtcqgPHofqOEHjxhIdj1JFQYnwFVi6s+/rX/XUYeXFxfyT/n3PmU5vrLYyRQO5
8iQY04bcrQ1OJHaxKd/s8b+71M6z7zPhS5qxj1nqVUgiqa8rHNyRtDACjl4pQb7J
KSBLLrrPvUM=
=FagO
-----END PGP SIGNATURE-----

--=-Vnf8Fxo6iB28eSHM4qG1--




From livhu.tshisikule@telkomsa.net  Sat Oct 16 07:04:34 2004
From: livhu.tshisikule@telkomsa.net (Livhu Tshisikule)
Date: Sat, 16 Oct 2004 08:04:34 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <20041015125640.GH3623@meier-geinitz.de>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net> <200410151447.15977.livhu.tshisikule@telkomsa.net> <20041015125640.GH3623@meier-geinitz.de>
Message-ID: <200410160804.34631.livhu.tshisikule@telkomsa.net>

Henning,

Thanks a lot, here are the results of sane-find-scanner -v -v

<device descriptor of 0x0b3c/0xa880 at 003:003 (Olivetti Job_Jet M400)>
bLength               18
bDescriptorType       1
bcdUSB                2.00
bDeviceClass          0
bDeviceSubClass       0
bDeviceProtocol       0
bMaxPacketSize0       8
idVendor              0x0B3C
idProduct             0xA880
bcdDevice             1.00
iManufacturer         1 (Olivetti)
iProduct              2 (Job_Jet M400)
iSerialNumber         3 (MY43FT62DF82)
bNumConfigurations    1
 <configuration 0>
 bLength              9
 bDescriptorType      2
 wTotalLength         99
 bNumInterfaces       3
 bConfigurationValue  1
 iConfiguration       0 ()
 bmAttributes         192 (Self-powered)
 MaxPower             2 mA
  <interface 0>
   <altsetting 0>
   bLength            9
   bDescriptorType    4
   bInterfaceNumber   0
   bAlternateSetting  0
   bNumEndpoints      3
   bInterfaceClass    255
   bInterfaceSubClass 204
   bInterfaceProtocol 0
   iInterface         0 ()
    <endpoint 0>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x01 (out 0x01)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 1>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x81 (in 0x01)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 2>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x82 (in 0x02)
    bmAttributes      3 (interrupt)
    wMaxPacketSize    8
    bInterval         10 ms
    bRefresh          0
    bSynchAddress     0
  <interface 1>
   <altsetting 0>
   bLength            9
   bDescriptorType    4
   bInterfaceNumber   1
   bAlternateSetting  0
   bNumEndpoints      3
   bInterfaceClass    7
   bInterfaceSubClass 1
   bInterfaceProtocol 2
   iInterface         0 ()
    <endpoint 0>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x03 (out 0x03)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 1>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x83 (in 0x03)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 2>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x84 (in 0x04)
    bmAttributes      3 (interrupt)
    wMaxPacketSize    8
    bInterval         10 ms
    bRefresh          0
    bSynchAddress     0
  <interface 2>
   <altsetting 0>
   bLength            9
   bDescriptorType    4
   bInterfaceNumber   2
   bAlternateSetting  0
   bNumEndpoints      3
   bInterfaceClass    255
   bInterfaceSubClass 255
   bInterfaceProtocol 255
   iInterface         0 ()
    <endpoint 0>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x05 (out 0x05)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 1>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x85 (in 0x05)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 2>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x86 (in 0x06)
    bmAttributes      3 (interrupt)
    bRefresh          0
<trying to find out which USB chip is used>
    checking for GT-6801 ...
    this is not a GT-6801 (bDeviceClass = 0)
    checking for GT-6816 ...
    this is not a GT-6816 (bcdUSB = 0x200)
    checking for MA-1017 ...
    this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 255)
    checking for MA-1015 ...
    this is not a MA-1015 (bDeviceClass = 0)
    checking for MA-1509 ...
    this is not a MA-1509 (bDeviceClass = 0)
    checking for LM983[1,2,3] ...
    this is not a LM983x (bcdUSB = 0x200)
    checking for GL646 ...
    this is not a GL646 (bDeviceClass = 0, bInterfaceClass = 255)
    checking for GL660+GL646 ...
    this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 255)
<Couldn't determine the type of the USB chip>

found USB scanner (vendor=0x0b3c [Olivetti], product=0xa880 [Job_Jet M400]) at 
libusb:003:003

Regards
Livhu



From Oliver.Rauch@Rauch-Domain.DE  Sat Oct 16 09:48:37 2004
From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch)
Date: 16 Oct 2004 10:48:37 +0200
Subject: [sane-devel] Timetable for the release of sane-backends-1.0.15
In-Reply-To: <1097851482.2134.8.camel@Babylon7>
References: <20041005113202.GG7772@meier-geinitz.de>
 <1097851482.2134.8.camel@Babylon7>
Message-ID: <1097916516.2128.1.camel@Babylon7>

Am Fre, 2004-10-15 um 16.44 schrieb Oliver Rauch:
> Hello.
> 
> I am not able to get access to the CVS server (permission denied).
> Please could someone who has acces to the server take a look at that?!
> 
> I suggest to delay the feature freeze for some days when this
> is not solved soon.

Today everything works right again, no need for a delay.

Oliver



From jb@jblache.org  Sat Oct 16 10:23:44 2004
From: jb@jblache.org (Julien BLACHE)
Date: Sat, 16 Oct 2004 11:23:44 +0200
Subject: [sane-devel] Timetable for the release of sane-backends-1.0.15
In-Reply-To: <1097851482.2134.8.camel@Babylon7> (Oliver Rauch's message of
 "15 Oct 2004 16:44:42 +0200")
References: <20041005113202.GG7772@meier-geinitz.de>
 <1097851482.2134.8.camel@Babylon7>
Message-ID: <87k6trt3rz.fsf@frigate.technologeek.org>

Oliver Rauch <Oliver.Rauch@Rauch-Domain.DE> wrote:

> I am not able to get access to the CVS server (permission denied).
> Please could someone who has acces to the server take a look at that?!

It should be working again, LDAP crashed again.

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb@jblache.org>                                  GPG KeyID 0xF5D65169


From jb@jblache.org  Sat Oct 16 12:03:45 2004
From: jb@jblache.org (Julien BLACHE)
Date: Sat, 16 Oct 2004 13:03:45 +0200
Subject: [sane-devel] Snapscan: Epson 2480 hangs on amd64
Message-ID: <87fz4eudpq.fsf@frigate.technologeek.org>

Hi,

My Epson 2480 hangs when doing a preview on an amd64 box, however it
works fine on both an i386 and a PowerPC boxes.

Here's the end of the log :

[snapscan] sane_snapscan_start: after measuring speed:
        3816 bytes per scan line
        0.000000 milliseconds per scan line.
        ==>inf bytes per millisecond
[snapscan] calibrate: reading calibration data (1 lines)
[snapscan] read_calibration_data
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0x647088,10,0x75fdb0,0xbfffe438 (61200))
[snapscan] atomic_usb_cmd(0,0x647088,10,0x75fdb0,0xbfffe438 (61200))
[snapscan] usb_cmd(0,0x647088,10,0x75fdb0,0xbfffe438 (61200))
[snapscan] usb_cmd: cmdlen=10, datalen=0
[snapscan] usb_write: writing:  0x28 0x00 0x82 0x00 0x00 0x01 0x00 0xef 0x10 0x00
[snapscan] Written 10 bytes
[snapscan] usb_read: reading:  0xf9 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Read 8 bytes
[snapscan] usb_read Only 0 bytes read
[snapscan] usb_read: reading:  0x5e 0x5d 0x63 0x60 0x60 0x5d 0x62 0x5e 0x60 0x64 ...
[snapscan] Read 0 bytes
[snapscan] read_calibration_data: snapscan_cmd command failed: Error during device I/O
[snapscan] calibrate: read_calibration_data command failed: Error during device I/O
[snapscan] sane_snapscan_start: calibration failed.
[snapscan] release_unit
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0xbfffe480,6,0x0,0x0 (0))
[snapscan] atomic_usb_cmd(0,0xbfffe480,6,0x0,0x0 (0))
[snapscan] usb_cmd(0,0xbfffe480,6,0x0,0x0 (0))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x17 0x00 0x00 0x00 0x00 0x00
[snapscan] usb_write Only 0 bytes written
[snapscan] Written 0 bytes
[snapscan] release_unit: scsi command error: Error during device I/O
[snapscan] sane_snapscan_cancel
[snapscan] release_unit
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0xbfffe3b0,6,0x0,0x0 (0))
[snapscan] atomic_usb_cmd(0,0xbfffe3b0,6,0x0,0x0 (0))
[snapscan] usb_cmd(0,0xbfffe3b0,6,0x0,0x0 (0))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x17 0x00 0x00 0x00 0x00 0x00
[snapscan] usb_write Only 0 bytes written
[snapscan] Written 0 bytes
[snapscan] release_unit: scsi command error: Error during device I/O
[snapscan] close_scanner
[snapscan] snapscani_usb_close(0)
[snapscan] 1st read 977 write 411
[snapscan] usb_cmd(0,0xbfffe3b0,6,0x0,0x0 (0))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] usb_write Only 0 bytes written
[snapscan] Written 0 bytes
[snapscan] 2nd read 977 write 411

dmesg indicates the usb operations time out (ret -110).

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb@jblache.org>                                  GPG KeyID 0xF5D65169


From henning@meier-geinitz.de  Sat Oct 16 12:17:50 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 13:17:50 +0200
Subject: [sane-devel] Timetable for the release of sane-backends-1.0.15
In-Reply-To: <1097851482.2134.8.camel@Babylon7>
References: <20041005113202.GG7772@meier-geinitz.de> <1097851482.2134.8.camel@Babylon7>
Message-ID: <20041016111750.GA10704@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 04:44:42PM +0200, Oliver Rauch wrote:
> I am not able to get access to the CVS server (permission denied).
> Please could someone who has acces to the server take a look at that?!

The reason was a 100% full / file system which stopped login and other
services like mail. As far as I can see it's fixed now.

As the mailinglists are hosted on the same server as CVS
(alioth.debian.org), they usually don't work when CVS is broken by
such failures. The IRC channel #sane is not affected as it's
independent from alioth. So better ask there when CVS or anything else
is broken.

Bye,
  Henning


From henning@meier-geinitz.de  Sat Oct 16 12:50:28 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 13:50:28 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <200410160804.34631.livhu.tshisikule@telkomsa.net>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net> <200410151447.15977.livhu.tshisikule@telkomsa.net> <20041015125640.GH3623@meier-geinitz.de> <200410160804.34631.livhu.tshisikule@telkomsa.net>
Message-ID: <20041016115028.GD10704@meier-geinitz.de>

Hi,

On Sat, Oct 16, 2004 at 08:04:34AM +0200, Livhu Tshisikule wrote:
> Henning,
> 
> Thanks a lot, here are the results of sane-find-scanner -v -v

Thanks. I'll add that scanner as unsupported to our lists.

Bye,
  Henning


From henning@meier-geinitz.de  Sat Oct 16 13:20:33 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 14:20:33 +0200
Subject: [sane-devel] possible bin_w_string security issue (not)
In-Reply-To: <1097848026.4219.0.camel@johannes>
References: <1097848026.4219.0.camel@johannes>
Message-ID: <20041016122033.GE10704@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 03:47:06PM +0200, Johannes Berg wrote:
> I was going to write a mail without the "(not)" but then discovered that
> this issue is actually a non-issue, but this is totally non-obvious.
> 
> Would you know off-hand why?

SIGPIPE (ok, I read your mail before answering) :-)

> bin_w_string contains the following code:
> 
>   if (w->direction == WIRE_DECODE)
>     {
>       if (len == 0)
>         *s = 0;
>       else if (w->status == 0)
>         *(*s + len - 1) = '\0';
>     }
> 
> If I interpret the code correctly, this could be used to bring the
> server (running the binary protocol) into an invalid state:

Nearly any protocol violation from server or client can have strange
results. That's one of the problems with the SANE net protocol.

Also there are still many tests missing for a bad wire status (see bug
#300105).

> * now, the server has a password string that is not zero terminated,
>    and strcpy()s that string accessing memory beyond the allocated size.

There may be other locations but at least here it tests for the wire
status:

(saned.c l. 356)

  sanei_w_authorization_req (&wire, &req);
  if (wire.status)
    {
      DBG(DBG_ERR, "auth_callback: bad status %d\n", wire.status);
      return;
    }

  if (req.username)
    strcpy (username, req.username);  
[...]

All the wire code expects the caller to test the wire status before he
does anything else. I think there should be tests in all functions of
sanei_net.c also to avoid calling sanei_wire again when the wire is
already bad.

> [Actually, I discovered this while I was documenting the wire protocol.
> I think it is overly complex and the code badly structured, the wire's
> direction thing is really strange!]

I'm still not sure if I have understood all the details of the wire
code. But I guess the idea was to have only one function for each kind
of data. So you don't need one for the server and one for the client
and one for ascii and one for bin and one for sending and one for
receiving...

> Ok, so here's the solution:
> 
> The server does
>   signal (SIGPIPE, quit);
> 
> (which I think is actually another bug, why should sane_close,
> sane_exit, sanei_w_exit and lots of other functions be async signal
> safe?)

They aren't. Only sane_cancel() must be async signal safe.

Yes, I guess that's a bug.

> Still, this is that non-obvious that someone writing a server (or
> client, which could then be attacked by a malevolent server) with the
> sanei library functions could easily oversee this detail, ignore SIGPIPE
> or use sockets that don't raise it.

Nobody should ever use sanei_wire/sanei_net/sanei_codec_* without
really knowing what he does :-)

> Therefore I'm still sending this mail in hope that someone fixes the
> sanei_w_array function to check for status != 0 and clean up after
> itself.

But what should sanei_w_array do? It already exits when the wire is in
bad state. I think that's really up to the caller.

Bye,
  Henning


From Oliver.Schwartz@gmx.de  Sat Oct 16 13:23:34 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Sat, 16 Oct 2004 14:23:34 +0200
Subject: [sane-devel] Snapscan: Epson 2480 hangs on amd64
In-Reply-To: <87fz4eudpq.fsf@frigate.technologeek.org>
References: <87fz4eudpq.fsf@frigate.technologeek.org>
Message-ID: <200410161423.37058.Oliver.Schwartz@gmx.de>

Hi,

> [snapscan] read_calibration_data: snapscan_cmd command failed:
> Error during device I/O [snapscan] calibrate: read_calibration_data
> command failed: Error during device I/O [snapscan]
> sane_snapscan_start: calibration failed.

the error occurs during quality calibration. It's a known issue that 
quality calibration as implemented in the snapscan backend doesn't 
work for epson scanners. For that reason the option is disabled for 
epson models (see snapscan-options.c, line 522ff). In this case the 
calibrate function should never be called (see snapscan.c, line 
1600).

Either you're using a wrong version of the backend or there's some 
issue with option handling on amd64.

/Oliver


From johannes@sipsolutions.net  Sat Oct 16 13:34:41 2004
From: johannes@sipsolutions.net (Johannes Berg)
Date: Sat, 16 Oct 2004 14:34:41 +0200
Subject: [sane-devel] possible bin_w_string security issue (not)
In-Reply-To: <20041016122033.GE10704@meier-geinitz.de>
References: <1097848026.4219.0.camel@johannes>
 <20041016122033.GE10704@meier-geinitz.de>
Message-ID: <1097930081.4439.13.camel@johannes>

--=-yhkGcHckmX4ZO5PEvTHQ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

> SIGPIPE (ok, I read your mail before answering) :-)

:-)

> Nearly any protocol violation from server or client can have strange
> results. That's one of the problems with the SANE net protocol.
>=20
> Also there are still many tests missing for a bad wire status (see bug
> #300105).

Will do.

> There may be other locations but at least here it tests for the wire
> status:

Hm. I guess you're right. Seems I missed it, or maybe I was writing this
when I looked at a different location? Sorry.

> I'm still not sure if I have understood all the details of the wire
> code. But I guess the idea was to have only one function for each kind
> of data. So you don't need one for the server and one for the client
> and one for ascii and one for bin and one for sending and one for
> receiving...

Yeah, and then it is also "overloaded" for freeing allocated data.

> They aren't. Only sane_cancel() must be async signal safe.
>=20
> Yes, I guess that's a bug.

Ok.

> Nobody should ever use sanei_wire/sanei_net/sanei_codec_* without
> really knowing what he does :-)

:-)

> But what should sanei_w_array do? It already exits when the wire is in
> bad state. I think that's really up to the caller.

Yes, but before exiting it should free the result buffer and NULL the
pointer. When the wire is in an invalid state during reading, it cannot
be guaranteed that the buffer is in a valid state, so should be
discarded.

johannes

--=-yhkGcHckmX4ZO5PEvTHQ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (SIP Solutions)

iQIVAwUAQXEVXaVg1VMiehFYAQLPOw/9E6+OseXpkvwWNMTenxSGxMF28XX/Rl71
s7sYiR4Fg9hdmPQDy0RtTkQrKspY6izzgn1aGlsH7H2eLw2pIF7yqW36vX2gQXWo
kwju+ZF+dIDLWjQ8ICiyuJFgYUNWxjZjDTfLhwe16ByGnVT+nWIx9ZbPYaB1KR0N
PmqH3M9G+s7oaZFh5zKtPiJA6kSBbsgpnhSDZpqzop+Rfe8vrFIPN7UTQS2PqZUx
20kMuH4CQu0ggpJ9yekIfzRdbBAZcHSCxKo7vTuupfratbbib9D2firVgW77aaNO
Lo3gnue+/TgxLJWeaBxrn/unL/q5U/YnNGhUgAsDBlGymjpZJV+ApOYHoVarv5XS
CbyYKKrszzhO8otxfkfA07v7QxqqpDw1CRE2tfxHqXyk2hmyVsy38AHrZOyevMGS
D2du8D63miUyVaU3dlGrjmcSxE7pohki9BpMjZ54hIEiF0zw2H9pC1/363KWNzl+
2rVZcrCmBQMrwoewepWGpvQBJiFZ9sxUkAmaQu/Jv3HEOQnsX8ZmQwKZpKy1qPHm
ARqx2Yex/OJ8R8ViKQfPjpRVyBvYfchle+XNRpJh+lbn2VGwh4KKWNGaaoFqdOJd
Ybwv5LTz7XtYFmR3IOssFp8BjrTULE5oezwrwCFLqyIJAGC64dGnkdTli6xlEp2E
h41UsBd5daQ=
=cJpn
-----END PGP SIGNATURE-----

--=-yhkGcHckmX4ZO5PEvTHQ--




From jb@jblache.org  Sat Oct 16 14:15:31 2004
From: jb@jblache.org (Julien BLACHE)
Date: Sat, 16 Oct 2004 15:15:31 +0200
Subject: [sane-devel] Snapscan: Epson 2480 hangs on amd64
In-Reply-To: <200410161423.37058.Oliver.Schwartz@gmx.de> (Oliver Schwartz's
 message of "Sat, 16 Oct 2004 14:23:34 +0200")
References: <87fz4eudpq.fsf@frigate.technologeek.org>
 <200410161423.37058.Oliver.Schwartz@gmx.de>
Message-ID: <87zn2mst1o.fsf@frigate.technologeek.org>

Oliver Schwartz <Oliver.Schwartz@gmx.de> wrote:

Hi Oliver,

>> [snapscan] read_calibration_data: snapscan_cmd command failed:
>> Error during device I/O [snapscan] calibrate: read_calibration_data
>> command failed: Error during device I/O [snapscan]
>> sane_snapscan_start: calibration failed.
>
> the error occurs during quality calibration. It's a known issue that 
> quality calibration as implemented in the snapscan backend doesn't 
> work for epson scanners. For that reason the option is disabled for 
> epson models (see snapscan-options.c, line 522ff). In this case the 
> calibrate function should never be called (see snapscan.c, line 
> 1600).

This is fresh checkout, and the code seems OK. There is something
fishy going on... now it doesn't even find the scanner anymore. I'll
dig into it.

> Either you're using a wrong version of the backend or there's some 
> issue with option handling on amd64.

Looks like it :/

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb@jblache.org>                                  GPG KeyID 0xF5D65169


From henning@meier-geinitz.de  Sat Oct 16 14:17:05 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 15:17:05 +0200
Subject: [sane-devel] weird message configuring sane-frontends
In-Reply-To: <1097849004.4219.4.camel@johannes>
References: <1097849004.4219.4.camel@johannes>
Message-ID: <20041016131705.GF10704@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 04:03:24PM +0200, Johannes Berg wrote:
> [configure fails because it can't find sane-config]
> "You may need to remove /dev/null before you run configure again."
> 
> Clearly, that is not something you want to do.

That's the penalty for users who don't read the docs and install
sane-frontends before sane-backends :-)

Fixed in CVS now.

The idea was to print the name of the cache filr of autoconf (usually
./config.cache). Recent autoconf versions don't use it and set the
variable to /dev/null.

Bye,
  Henning


From henning@meier-geinitz.de  Sat Oct 16 14:32:11 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 15:32:11 +0200
Subject: [sane-devel] saned/sanei net bug
In-Reply-To: <1097848984.4219.3.camel@johannes>
References: <1097848984.4219.3.camel@johannes>
Message-ID: <20041016133211.GG10704@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 04:03:04PM +0200, Johannes Berg wrote:
> somehow saned/the sanei network layer seem to get buffering wrong.

I'm afraid that that's intentional. But that's only a guess.

> For example, I send the following:
> 
> SANE_NET_INIT
> SANE_NET_GET_DEVICES
> SANE_NET_EXIT
> 
> If I don't wait for the result from SANE_NET_GET_DEVICES before sending
> the control code for SANE_NET_EXIT, then the SANE_NET_EXIT code is
> discarded.

I think you must really read the result of any RPC before sending the
next one.

> I would assume that somewhere there's a buffering problem and the old
> buffer is simply dropped when the direction is changed or something.

That's done in sanei_w_set_direction().
Set SANE_DEBUG_SANEI_WIRE=255 and you'll even get a warning :-)

> The following works:
> (echo  -n -e \\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00 ;
> sleep .1 ; echo -n -e \\00\\00\\x00\\x01 ; sleep 1 ;
> echo -en \\x00\\x00\\x00\\x0A ) | nc localhost 6566 -q 1 | hd
> 
> while this doesn't:
> (echo  -n -e \\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00 ;
> sleep .1 ; echo -n -e \\00\\00\\x00\\x01\\x00\\x00\\x00\\x0A
> )| nc localhost 6566 -q 1 | hd
> 
> I think this is extremely counter-intuitive. TCP never guarantees
> message boundaries, so one wouldn't think that data is explicitly read
> by the application but then discarded.
 
I guess you are right but I don't really know how to fix that with the
current code. One option would be to set the wire to error state (and
exit?) when data is discarded.

Bye,
  Henning


From henning@meier-geinitz.de  Sat Oct 16 14:48:19 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 15:48:19 +0200
Subject: [sane-devel] [BUG] saned: missing input sanitization
In-Reply-To: <1097848060.4219.2.camel@johannes>
References: <1097848060.4219.2.camel@johannes>
Message-ID: <20041016134819.GH10704@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 03:47:40PM +0200, Johannes Berg wrote:
> SANE_NET_OPEN makes saned segfault if a NULL name is passed, because it
> tries to strdup() the name without checking for != NULL.

I've added a check to CVS. It returns an error to the client because I
think that's a protocol violation. Zero-length strings are allowed for
sane_open but not NULL-pointers.

Could you check if that works and doesn't create any new bugs?

Bye,
  Henning


From johannes@sipsolutions.net  Sat Oct 16 15:01:20 2004
From: johannes@sipsolutions.net (Johannes Berg)
Date: Sat, 16 Oct 2004 16:01:20 +0200
Subject: [sane-devel] [BUG] saned: missing input sanitization
In-Reply-To: <20041016134819.GH10704@meier-geinitz.de>
References: <1097848060.4219.2.camel@johannes>
 <20041016134819.GH10704@meier-geinitz.de>
Message-ID: <1097935280.4439.17.camel@johannes>

--=-RvFmJl5eUaAjiXBPw3Ib
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2004-10-16 at 15:48 +0200, Henning Meier-Geinitz wrote:
> I've added a check to CVS. It returns an error to the client because I
> think that's a protocol violation. Zero-length strings are allowed for
> sane_open but not NULL-pointers.

I think the problem is that the network layer does not distinguish
between zero-length strings and NULL pointers -- as far as I can see it
interprets a zero-length string (which is only a byte-array after all)
as a NULL string.

johannes

--=-RvFmJl5eUaAjiXBPw3Ib
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (SIP Solutions)

iQIVAwUAQXEpq6Vg1VMiehFYAQKfdw/8DmtQmW6bABrsnmshQFN+syVsTAZWFhRO
0veLBoM8uNxgFMLXUtiXhv0lWfbZdce6UXYREB3bPy2yrAIsm30rFipBGvckX9J9
RvmH21mrigWiYn5VoloGIqiCDum/BubxyeE/xSBkcVcDKh3wnOWtYzFDBEnyP79U
rUz0bMlchKHcKrPsZq78WeJ203hZaPBxPgmRKT/i/kjdOFMIiu/enMC8VEFrl3Oe
AhbXOhtj5GtkfPs1ueM5oms4f4wu4La+lF6+5lhHGFOY6Bwj+Xd0xwvxPge36NXD
NRn7XArGv9SLUPza1y9Nw6wlVMFpG4AdlUyTTH3zO28A8bOjksSC53p/ftl/x9z1
wE4j1yBvzUmlrCYmSYvPgzXG5Kwv6CndtE3+v6+f2dYrY80yMCLLWyMG1XLgKtvT
oDtuUFdpzOPSQSDWz7ICkCyl1Vv+5DiWlchXBqN5cHz/1mDMZOj9VAmtoo+b28kA
tIeEFq3q0ITTwJps6nrmUDshGDAiVWj86NH7y+Q6py0EmG8eHav1MvDdxiz5r7/x
Q160C87JrAfMgxl5o84zGF63XJHH4k6e0RLNEqDLCg6u0K+qZ9tkUgNQOLZ5Ym9Q
LcqYgokfISbLEfit7V4fp9lXz75ZU7HYsaDnsOKKH/EI0v3F1xzHQUG2LMNywlBj
8XQQi/XDORw=
=iuNs
-----END PGP SIGNATURE-----

--=-RvFmJl5eUaAjiXBPw3Ib--




From henning@meier-geinitz.de  Sat Oct 16 15:10:52 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 16:10:52 +0200
Subject: [sane-devel] [BUG] saned: missing input sanitization
In-Reply-To: <1097935280.4439.17.camel@johannes>
References: <1097848060.4219.2.camel@johannes> <20041016134819.GH10704@meier-geinitz.de> <1097935280.4439.17.camel@johannes>
Message-ID: <20041016141052.GA11265@meier-geinitz.de>

Hi,

On Sat, Oct 16, 2004 at 04:01:20PM +0200, Johannes Berg wrote:
> I think the problem is that the network layer does not distinguish
> between zero-length strings and NULL pointers -- as far as I can see it
> interprets a zero-length string 

A zero length string is e.g. SANE_String hubba = "";

> (which is only a byte-array after all)

For sane_net a zero-lenth string is 0 0 0 1 0 (Array of length 1 which
only contains a 0 byte as end marker).

> as a NULL string.

I hope it doesn't. A NULL string is encoded as an array of length 0
(and has no data).

zero-length is ok in sane_open, NULL isn't.

Bye,
  Henning


From johannes@sipsolutions.net  Sat Oct 16 15:23:07 2004
From: johannes@sipsolutions.net (Johannes Berg)
Date: Sat, 16 Oct 2004 16:23:07 +0200
Subject: [sane-devel] [BUG] saned: missing input sanitization
In-Reply-To: <20041016141052.GA11265@meier-geinitz.de>
References: <1097848060.4219.2.camel@johannes>
 <20041016134819.GH10704@meier-geinitz.de>
 <1097935280.4439.17.camel@johannes>
 <20041016141052.GA11265@meier-geinitz.de>
Message-ID: <1097936587.4439.19.camel@johannes>

--=-5n0e72bCo6NIQyEFjdhX
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2004-10-16 at 16:10 +0200, Henning Meier-Geinitz wrote:

> For sane_net a zero-lenth string is 0 0 0 1 0 (Array of length 1 which
> only contains a 0 byte as end marker).

Reading through the code again -- looks like you're right. Somehow I got
the impression that it was the same, but don't remember where I read
that now.

johannes

--=-5n0e72bCo6NIQyEFjdhX
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (SIP Solutions)

iQIVAwUAQXEuxqVg1VMiehFYAQKFVw//Uyr9ZkUO2zjzW/eDiaqWKp6o14qOwMDF
3p7QClunjZDGLPz3Bzt7mDZtqaecyy0Dly1Be0nk5LDOphvnuRk+OucWmrCcDfQT
dTmqnfScp0G+bzKEawnrBNC4nPiimJnqEEpdLcPv/tx1wi2AZ8yQZBx7lW5anjc0
Ewl3Ssnx3dVxu+MsfqXVwN+I+cTFVai7uDANnkqNl9UGi9MxUb0w34ZsGSkqdtJf
8VyTOzvrpq3cfe1yD2NL5uHAsb4fJ6+3KcfOzo/vXxJgKHFwI4R6DodwyOTjZnCT
4+MTcQEJCEEsYXPGwYCBqv33NTN1/y7VGFfAoHQycQu9VAfjo0uec5Gffzrc3szd
2lnaTAt94hRLtd1QxdgjQMMj3QBIPHz6FRvet+IQb7t97A4I294/32oQV4S425R/
brkA4BOEEzyHihFard7V2o3404frglJZGWUOBKqYRYcypmzyIk73xLFnyvHQnaAm
qG9uUxzDvtamzYmcst0v25MsGDzqyGVOfryLaWV6uMMmms3MWU9y7Y20MQMvBrjT
Yl6w/t85C/nomxiVftTS+8H6hKbVExB57TMN9SnQUN4tjw1LD1TCwROkl6BExpHI
D3GDSfWojZ2emFoZsIbJ+PKoq79K/MWFyE5DDpk4Qv/sPd6h9oII3qgBTSWZHR5H
MIOXVanpyXU=
=Ilg2
-----END PGP SIGNATURE-----

--=-5n0e72bCo6NIQyEFjdhX--




From lsumpter@dccnet.com  Sat Oct 16 16:35:28 2004
From: lsumpter@dccnet.com (Lloyd Sumpter)
Date: Sat, 16 Oct 2004 08:35:28 -0700
Subject: [sane-devel] Problems with libusb (WAS:Upgrading sane-backend
 on Mandrake 10.0)
In-Reply-To: <20041010133445.GG3144@meier-geinitz.de>
References: <3DDE554B.2030606@dccnet.com> <20041010133445.GG3144@meier-geinitz.de>
Message-ID: <41713FC0.6090006@dccnet.com>


Henning Meier-Geinitz wrote:
> Hi,
> 
> On Fri, Nov 22, 2002 at 08:03:23AM -0800, Lloyd Sumpter wrote:
> 
> Strange date.
> 
Sorry, had just rebooted (from the problems between harddrake and 
sane-find-scanner) and hadn't run rdate yet.

<snip>
> 
>>BTW: The reason I have to upgrade is that apparently the sane-backends 
>>included with Mandrake 10.0 do NOT support libusb (but since the kernel 
>>is 2.6.x, there's no scanner.o to use instead...)
> 
> 
> sane-backends supports libusb since quite some time. And it was needed
> before kernel 2.6 at least for some scanners. So I'd be surprised if
> the Mandrake version had no libusb support.
> 
> You can check by running "sane-find-scanner -v -v". It should print
> messages about using libusb.
> 

Thanks for your help! But on Sept 29, you wrote:

 > On Tue, Sep 28, 2004 at 01:22:01PM -0700, Lloyd Sumpter wrote:
 >
 > > [sanei_debug] Setting debug level of sanei_usb to 255.
 > > [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No 
such  > device
 > > [sanei_usb] sanei_usb_init: found 0 devices
 >
 >
 > Oh. That means that SANE isn't built with libusb support. It only
 > searches for /dev/usb/ but not for libusb devices.
 >
 > As your sane-find-scanner program finds libusb devices, maybe you have
 > an old installation of the SANE backends without libusb support that's
 > used by scanimage?

Note that sane-find-scanner DOES find the scanner (using libusb), but 
scanimage does not.

PLEASE, any help would be appreciated - I've been working on this for weeks!

Lloyd Sumpter



From henning@meier-geinitz.de  Sat Oct 16 17:51:03 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 18:51:03 +0200
Subject: [sane-devel] Problems with libusb (WAS:Upgrading sane-backend on Mandrake 10.0)
In-Reply-To: <41713FC0.6090006@dccnet.com>
References: <3DDE554B.2030606@dccnet.com> <20041010133445.GG3144@meier-geinitz.de> <41713FC0.6090006@dccnet.com>
Message-ID: <20041016165103.GB11265@meier-geinitz.de>

Hi,

On Sat, Oct 16, 2004 at 08:35:28AM -0700, Lloyd Sumpter wrote:
> >You can check by running "sane-find-scanner -v -v". It should print
> >messages about using libusb.
> 
> Thanks for your help! But on Sept 29, you wrote:

Oh, different thread, same problem? I usually don't look at the
author's name :-)

> > Oh. That means that SANE isn't built with libusb support. It only
> > searches for /dev/usb/ but not for libusb devices.
> >
> > As your sane-find-scanner program finds libusb devices, maybe you have
> > an old installation of the SANE backends without libusb support that's
> > used by scanimage?
> 
> Note that sane-find-scanner DOES find the scanner (using libusb), but 
> scanimage does not.

Ok.

> PLEASE, any help would be appreciated - I've been working on this for weeks!

See above. Have you checked if you don't use two different
installations of SANE?

E.g. check sane-find-scanner:
ldd /usr/bin/sane-find-scanner
Check libsane:
ldd /usr/lib/libsane.so.1
And to be safe, check the plustek backend:
ldd /usr/lib/sane/libsane-plustek.so.1
Also check if scanimage is linked to the right sane-backend libs:
ldd /usr/bin/scanimage

You may need to adjust the paths. All should print something about
libusb.

If sane-find-scanner is linked to libusb and libsane isn't, better ask
your distributer what the heck they are doing.

Bye,
  Henning


From scottf@bigpond.net.au  Sat Oct 16 22:02:17 2004
From: scottf@bigpond.net.au (scott fagg)
Date: Sun, 17 Oct 2004 07:02:17 +1000
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <200410062029.50935.Oliver.Schwartz@gmx.de>
References: <415BD75B.1060103@bigpond.net.au> <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain>
 <Pine.LNX.4.53.0410061856300.13865@localhost.localdomain>
 <200410062029.50935.Oliver.Schwartz@gmx.de>
Message-ID: <Pine.LNX.4.53.0410170702070.1932@localhost.localdomain>

On Wed, 6 Oct 2004, Oliver Schwartz wrote:

> Date: Wed, 06 Oct 2004 20:29:47 +0200
> From: Oliver Schwartz <Oliver.Schwartz@gmx.de>
> To: sane-devel@lists.alioth.debian.org
> Subject: Re: [sane-devel] epson 2580 problems
>
> Hi,
>
> > Using the latest drivers helps and i can now scan, however preview
> > doesn't work. At least i can get an image out of it now.
> >
> > It seems to only preview either the area of the most recent scan or
> > nothing, and then stretches that image vertically to fit the A4
> > scannable area and shows that as a preview.
>
> Please send me a debug log of a preview scan.

How do i get xsane to generate a debug log ?

>
> /Oliver
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org
>

--
scottf@bigpond.net.au



From scottf@bigpond.net.au  Sat Oct 16 22:08:14 2004
From: scottf@bigpond.net.au (scott fagg)
Date: Sun, 17 Oct 2004 07:08:14 +1000
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <200410062029.50935.Oliver.Schwartz@gmx.de>
References: <415BD75B.1060103@bigpond.net.au> <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain>
 <Pine.LNX.4.53.0410061856300.13865@localhost.localdomain>
 <200410062029.50935.Oliver.Schwartz@gmx.de>
Message-ID: <Pine.LNX.4.53.0410170707470.1932@localhost.localdomain>

On Wed, 6 Oct 2004, Oliver Schwartz wrote:

> Date: Wed, 06 Oct 2004 20:29:47 +0200
> From: Oliver Schwartz <Oliver.Schwartz@gmx.de>
> To: sane-devel@lists.alioth.debian.org
> Subject: Re: [sane-devel] epson 2580 problems
>
> Hi,
>
> > Using the latest drivers helps and i can now scan, however preview
> > doesn't work. At least i can get an image out of it now.
> >
> > It seems to only preview either the area of the most recent scan or
> > nothing, and then stretches that image vertically to fit the A4
> > scannable area and shows that as a preview.
>
> Please send me a debug log of a preview scan.

Ignore my earlier question.

Oliver : I've sent you a copy of the log and a screen shot of what occurs.

>
> /Oliver
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org
>

--
scottf@bigpond.net.au



From oliver.bonten@nexgo.de  Sun Oct 17 09:51:34 2004
From: oliver.bonten@nexgo.de (Oliver Bonten)
Date: Sun, 17 Oct 2004 10:51:34 +0200
Subject: [sane-devel] Canon 2700 slide scanner
Message-ID: <200410171051.34335.oliver.bonten@nexgo.de>

Hello,

in the sane-devel archives I found a discussion about 3 weeks old between=20
Thomas L=F6scher and Mitsuru Okaniwa about a problem with the Canon 2700 sl=
ide=20
scanner. The thread seems to be a bit open-ended to me, so I would like to=
=20
know if there has been any resolution for the problem. It seems that I have=
=20
the same problem with my 2700 and sane 1.0.13.=20

I found a work-around which is only a hack and not a solution. I'm using Su=
se=20
9.1, which includes sane 1.0.13-73. Before that, I used Suse 8.1, which=20
included sane 1.0.8-47. I didn't have the problem with Suse 8.1. So I =20
re-inserted the source-code from the 1.0.8 version of canon.c at the locati=
on=20
where the error occured (function sense_handler()) to canon.c 1.0.13 at the=
=20
corresponding location, with an if ( 1 ) { /* 1.0.8 source code */ } else=20
{ /* 1.0.13 source code */ }. However, this seems to disable some error=20
handling, and I have the feeling that my scanner doesn't execute the auto=20
focus anymore. Either that or my current set of slides is unusually=20
blurred. :-) Sorry, I don't have the source code anymore, because rpmbuild=
=20
doesn't work the way I expected it to work. But I can re-create it if neede=
d.

Would it be safe to re-insert the full 1.0.8 source code for the canon back=
end=20
(i.e., all files matching backend/canon*.[ch]) into an otherwise 1.0.13 san=
e=20
and recompile? I don't want to go back to an older version of sane because =
I=20
also have a flatbed scanner (not canon) which works much better with the=20
newer version of sane.=20

Regards,

Oliver


From Oliver.Schwartz@gmx.de  Sun Oct 17 12:11:26 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Sun, 17 Oct 2004 13:11:26 +0200
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <Pine.LNX.4.53.0410170707470.1932@localhost.localdomain>
References: <415BD75B.1060103@bigpond.net.au> <200410062029.50935.Oliver.Schwartz@gmx.de> <Pine.LNX.4.53.0410170707470.1932@localhost.localdomain>
Message-ID: <200410171311.28511.Oliver.Schwartz@gmx.de>

Hi,

> Oliver : I've sent you a copy of the log and a screen shot of what
> occurs.

it seems that the scanner somehow doesn't like the set_window command 
which is used to set the scanning area for previewing. 

Since normal scanning works I suspect that it's either the requested 
image size or the operation mode that causes problems. 

Please try to select a small scanning area in xsane and select 
"Preview" again, this should result in a preview of the selected 
area. If this works than it's most likely the default scan area that 
is not set correctly.

If selecting a smaller preview area still doesn't work you can try to 
play around with the operation_mode setting. It is set up in 
snapscan-scsi.c, around line 837, in the variable named "source". 
Bits 6 and 7 are the most likely suspects. The current value for 
preview is 0x80, you can try if any of the other three values gives 
better results.

/Oliver


From ukd@xenon.pc.Uni-Koeln.DE  Sun Oct 17 15:46:34 2004
From: ukd@xenon.pc.Uni-Koeln.DE (Ulrich Deiters)
Date: Sun, 17 Oct 2004 14:46:34 METDST
Subject: [sane-devel] Canon 2700 slide scanner
Message-ID: <200410171246.OAA05289@xenon.pc.Uni-Koeln.DE>

The trouble spot in the Canon SCSI backend has been located,
and we have an experimental backend that seems to support
both the 2700 and the 2710 now. But there is still some
testing and cleaning-up to be done, although that should
not take too long.

Regards,

Ulrich Deiters


From tim@boneko.de  Sun Oct 17 15:35:13 2004
From: tim@boneko.de (Tim Boneko)
Date: Sun, 17 Oct 2004 16:35:13 +0200
Subject: [sane-devel] snapscan: Identified scanner still doesn't work
Message-ID: <200410171635.22500.tim@brocken>

--nextPart1159101.dJXkVLNg8n
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello from southern germany,

after lots of googling and searching i finally found this mailing list,=20
thank goodness. snapscan.sourceforge.net doesn't mention this.=20
I hope someone can help me here:

I bought an Epson Perfection 2480 Photo and tried to install it using=20
the instructions on the mentioned sf-site. Software as follows:=20

Debian system, kernel 2.6.8.1, sane 1.0.12 from unstable, libsane=20
1.0.14-7 from unstable - building the cvs version failed, see below.=20
libusb 0.1.5 from unstable, hotplug 20040329 ditto.
My /etc/sane.d/snapscan.conf is attached below. The firmware file to be=20
uploaded is in /etc/sane.d.=20

The scanner is detected correctly by sane-find-scanner:

>found USB scanner (vendor=3D0x04b8 [EPSON], product=3D0x0121 [EPSON       =
   =20
>Scanner]) at libusb:003:004

Any access to the scanner (xsane and the like) end up in an error=20
message:

>Couldn't start scanner - error during device i/o=20

(translated from german)

=2E..so i tried sane-troubleshoot without any result i didn't already=20
know. The test-scan ended with the following in /var/log/syslog:

>ehci_hcd 0000:00:02.2: qh c1577780 (#17) state 1
>usb 3-3: usbfs: USBDEVFS_BULK failed ep 0x81 len 3856 >ret -75
>usb 3-3: bulk timeout on ep2out
>usb 3-3: usbfs: USBDEVFS_BULK failed ep 0x2 len 6 ret -110

To me this looks like a usb problem, right? After a failed access to the =20
scanner the led of it keeps flashing for minutes. During this time a=20
"cat /proc/bus/usb/devices" hangs for 30 seconds before giving out what=20
i've attached below.

I tried to build the  snapscan-backend from cvs, but couldn't:=20
"make" ended up with

>gcc -o gamma4scanimage gamma4scanimage.o  -lm
>gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations=20
>-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes=20
>-pedantic -ansi -DHAVE_CONFIG_H -I. -I. -I../include -I../include=20
>-DPATH_SANE_CONFIG_DIR=3D/usr/local/etc/sane.d         =20
>-DPATH_SANE_DATA_DIR=3D/usr/local/share           -DV_MAJOR=3D1=20
>-DV_MINOR=3D0 sane-desc.c
>gcc -o sane-desc=20
>sane-desc.o  ../sanei/libsanei.a ../lib/liblib.a /usr/lib/libusb.so=20
>-lnsl -lm
>make[1]: Leaving directory=20
>`/archiv/progs/snapscan-cvs/sane-backends/tools'
>making all in doc
>make[1]: Entering directory=20
>`/archiv/progs/snapscan-cvs/sane-backends/doc'
>Generating sane.ps...
>make[1]: *** [sane.ps] Fehler 1
>make[1]: Leaving directory=20
>`/archiv/progs/snapscan-cvs/sane-backends/doc'
>make: *** [all-recursive] Fehler 1

That's what i've achieved so far. Any hints are greatly appreciated.
TIA,

 tim

To complete the overkill, here's some output of /proc/bus/usb/devices=20
after booting:

T:  Bus=3D03 Lev=3D01 Prnt=3D01 Port=3D02 Cnt=3D01 Dev#=3D  7 Spd=3D480 MxC=
h=3D 0
D:  Ver=3D 2.00 Cls=3Dff(vend.) Sub=3Dff Prot=3Dff MxPS=3D64 #Cfgs=3D  1
P:  Vendor=3D04b8 ProdID=3D0121 Rev=3D 0.00
S:  Manufacturer=3DEPSON
S:  Product=3DEPSON Scanner
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D100mA
I:  If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=3Dff(vend.) Sub=3Dff Prot=3Dff Driver=
=3D(none)
E:  Ad=3D81(I) Atr=3D02(Bulk) MxPS=3D 512 Ivl=3D0ms
E:  Ad=3D02(O) Atr=3D02(Bulk) MxPS=3D 512 Ivl=3D0ms
E:  Ad=3D83(I) Atr=3D03(Int.) MxPS=3D   8 Ivl=3D4096ms

The output lacks the two "S" lines (Manuf. & Product) when i "cat" it=20
while the scanner led is flashing.

Here's my snapscan.conf:

firmware /etc/sane.d/esfw41.bin
usb 0x04b8 0x0121

Adding a line "/dev/usb/scanner0 bus=3Dusb" doesn't change anything. Same=20
for an empty firmware file.

--nextPart1159101.dJXkVLNg8n
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBcoMqG68ndDW+t7gRAqLmAKCJq+VvoiQqwueokfwGrvK9QrK2FQCghh/u
goDQsT8pkTAKcglbSg/OsFc=
=KR82
-----END PGP SIGNATURE-----

--nextPart1159101.dJXkVLNg8n--


From henning@meier-geinitz.de  Sun Oct 17 16:05:19 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 17:05:19 +0200
Subject: [sane-devel] snapscan: Identified scanner still doesn't work
In-Reply-To: <200410171635.22500.tim@brocken>
References: <200410171635.22500.tim@brocken>
Message-ID: <20041017150519.GA12072@meier-geinitz.de>

Hi,

On Sun, Oct 17, 2004 at 04:35:13PM +0200, Tim Boneko wrote:
> I tried to build the  snapscan-backend from cvs, but couldn't: 
> "make" ended up with
> 
> >gcc -o gamma4scanimage gamma4scanimage.o  -lm
> >gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations 
> >-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes 
> >-pedantic -ansi -DHAVE_CONFIG_H -I. -I. -I../include -I../include 
> >-DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d          
> >-DPATH_SANE_DATA_DIR=/usr/local/share           -DV_MAJOR=1 
> >-DV_MINOR=0 sane-desc.c
> >gcc -o sane-desc 
> >sane-desc.o  ../sanei/libsanei.a ../lib/liblib.a /usr/lib/libusb.so 
> >-lnsl -lm
> >make[1]: Leaving directory 
> >`/archiv/progs/snapscan-cvs/sane-backends/tools'
> >making all in doc
> >make[1]: Entering directory 
> >`/archiv/progs/snapscan-cvs/sane-backends/doc'
> >Generating sane.ps...
> >make[1]: *** [sane.ps] Fehler 1

latex or some other TeX tool didn't like the commands it got. 
configure checks if these commands are available but maybe you have a
rather strange TeX installation :-)

Anyway, just enter "make install". Make looks into the doc directory
after the backend directory so make install should still work. It may
complain about sane.ps but you can ignore it.

Ifyou like to debug the sane.ps issue, edit doc/Makefile, search for
the rule for sane.ps and delete the "@" in front of the commands and
all the ">/dev/null" and "2>/dev/null". That should print some more
reasonable error messages.

> T:  Bus=03 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#=  7 Spd=480 MxCh= 0
> D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs=  1
> P:  Vendor=04b8 ProdID=0121 Rev= 0.00
> S:  Manufacturer=EPSON
> S:  Product=EPSON Scanner
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
> I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad=83(I) Atr=03(Int.) MxPS=   8 Ivl=4096ms
> 
> The output lacks the two "S" lines (Manuf. & Product) when i "cat" it 
> while the scanner led is flashing.

I think when you cat the devices file the kernel tries to get the
strings by sending a USB control message to the scanner. If the
scanner is confused, it will not react to these messages and they time
out.

Bye,
  Henning


From henning@meier-geinitz.de  Sun Oct 17 16:53:38 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 17:53:38 +0200
Subject: [sane-devel] [ANNOUNCE] sane-frontends 1.0.13 released
Message-ID: <20041017155338.GD12072@meier-geinitz.de>

Hi everyone,

sane-frontends version 1.0.13 has just been released. Download it from
the usual locations as mentioned on http://www.sane-project.org/source.html

This is the md5sum:
2930626e627df49b45192a722cedc8a6  ./sane-frontends-1.0.13.tar.gz

Happy scanning!

Henning


From tim@boneko.de  Sun Oct 17 17:17:19 2004
From: tim@boneko.de (Tim Boneko)
Date: Sun, 17 Oct 2004 18:17:19 +0200
Subject: [sane-devel] snapscan: Identified scanner still doesn't work
In-Reply-To: <20041017150519.GA12072@meier-geinitz.de>
References: <200410171635.22500.tim@brocken> <20041017150519.GA12072@meier-geinitz.de>
Message-ID: <200410171817.27471.tim@brocken>

--nextPart2143341.gjVYRi686U
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Something pleasant happened: right after sending tons of text to the=20
list i had an idea how to avoid the build failure. After deleting the=20
"doc" entry in the SUBDIRS entry of the Makefile the building succeded=20
and the scanner seems to be working, apparently even without firmware=20
upload.
Sorry for whacking you with text & keep up the good work!
Danke Henning!

 tim

--nextPart2143341.gjVYRi686U
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBcpsXG68ndDW+t7gRAldxAJ9yOGP+ihyGs08rKGhn2NU6SE1fPACglfqx
tOVjPdF4HbyP01clqdLgDNI=
=WMkX
-----END PGP SIGNATURE-----

--nextPart2143341.gjVYRi686U--


From henning@meier-geinitz.de  Sun Oct 17 19:10:30 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:10:30 +0200
Subject: [sane-devel] [ANNOUNCE] First pre-release of sane-backends 1.0.15 available
Message-ID: <20041017181030.GG12072@meier-geinitz.de>

Hi everyone,

The first pre-release of sane-backends 1.0.15 is available at
the usual locations as mentioned on http://www.sane-project.org/source.html

The md5sum is:
ff9ad4def17e6644e03d66f07c708b13  sane-backends-1.0.15-pre1.tar.gz

We are in feature freeze currently. In two weeks, code freeze will
start. Release is planned for 2004-11-07.

I'll append the NEWS file for 1.0.15.

Please test this prerelease and tell us about any bugs.

Happy scanning!

Henning

New with 1.0.15, released 2004-??-??:

* New backends: niash
* Updated backends: agfafocus, artec_eplus48u.c, avision, canon, canon_pp,
  coolscan, dll, epson, fujitsu, gt68xx, hp, hp5400, leo, microtek2, mustek,
  mustek_pp, net, pie, plustek, plustek_pp, snapscan, sp15c, tamarack, teco2,
  umax, umax_pp, u12, v4l
* Portability fixes (especially for MacOS X, NetBSD, OS/2, 64 bit platforms).
* sane-find-scanner detects more chipsets now.
* Added Finnish translation. Updated other translations.
* Several saned fixes.
* Build system updates.
* Documentation updates.
* Bugfixes.


From henning@meier-geinitz.de  Sun Oct 17 19:12:09 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:12:09 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
Message-ID: <20041017181209.GH12072@meier-geinitz.de>

Hi everyone,

Feature freeze for sane-backends 1.0.15 is now active. That means,
that now new backend or new features for existing backends should be
committed to CVS. Bug fixes, documentation and translation updates are
ok.

Timetable:
2004-10-31 Code freeze (snapshot)
2004-11-07 Release

Bye,
  Henning


From sirius-c@iname.com  Sun Oct 17 19:16:06 2004
From: sirius-c@iname.com (Jason Anderson)
Date: Sun, 17 Oct 2004 13:16:06 -0500
Subject: [sane-devel] Scanner problems
Message-ID: <20041017181606.58D504BDAB@ws1-1.us4.outblaze.com>

Hello everyone!

I've just got a CanoScan N650U.  When I use the current backends, however, =
the darn picture is upside down!  I don't know why, either.  Any ideas?

----------
Jason A.
ICQ# 148434286
--=20
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm



From Oliver.Rauch@Rauch-Domain.DE  Sun Oct 17 19:12:29 2004
From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch)
Date: 17 Oct 2004 20:12:29 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
In-Reply-To: <20041017181209.GH12072@meier-geinitz.de>
References: <20041017181209.GH12072@meier-geinitz.de>
Message-ID: <1098036749.2126.1.camel@Babylon7>

Am Son, 2004-10-17 um 20.12 schrieb Henning Meier-Geinitz:
> Hi everyone,
> 
> Feature freeze for sane-backends 1.0.15 is now active. That means,
> that now new backend or new features for existing backends should be
       ^^^ I think this should be a NO or there is missing a NO.
But it should be clear anyway that it is NOT allowed to add new features
after feature freeze.

Oliver

> committed to CVS. Bug fixes, documentation and translation updates are
> ok.




From henning@meier-geinitz.de  Sun Oct 17 19:25:28 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:25:28 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
In-Reply-To: <1098036749.2126.1.camel@Babylon7>
References: <20041017181209.GH12072@meier-geinitz.de> <1098036749.2126.1.camel@Babylon7>
Message-ID: <20041017182528.GI12072@meier-geinitz.de>

Hi,

On Sun, Oct 17, 2004 at 08:12:29PM +0200, Oliver Rauch wrote:
> Am Son, 2004-10-17 um 20.12 schrieb Henning Meier-Geinitz:
> > Hi everyone,
> > 
> > Feature freeze for sane-backends 1.0.15 is now active. That means,
> > that now new backend or new features for existing backends should be
>        ^^^ I think this should be a NO or there is missing a NO.
> But it should be clear anyway that it is NOT allowed to add new features
> after feature freeze.

Right. Copy- and paste error. I wanted to write something like this:

"Feature freeze means that no new backends or new features for existing
backends should be committed to CVS."

Bye,
  Henning


From henning@meier-geinitz.de  Sun Oct 17 19:30:00 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:30:00 +0200
Subject: [sane-devel] Scanner problems
In-Reply-To: <20041017181606.58D504BDAB@ws1-1.us4.outblaze.com>
References: <20041017181606.58D504BDAB@ws1-1.us4.outblaze.com>
Message-ID: <20041017183000.GJ12072@meier-geinitz.de>

Hi,

On Sun, Oct 17, 2004 at 01:16:06PM -0500, Jason Anderson wrote:
> I've just got a CanoScan N650U.  When I use the current backends,

With current backends you mean the version from CVS?

> however, the darn picture is upside down!  I don't know why, either.

What's the last version of sane-backends that worked?

"Upside down" means that if you turn around (180°) the image that is
to be scanned the result will be ok?

Bye,
  Henning


From henning@meier-geinitz.de  Sun Oct 17 19:42:28 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:42:28 +0200
Subject: [sane-devel] Translation status
Message-ID: <20041017184228.GK12072@meier-geinitz.de>

Hi everyone,

As sane-backends is in feature freeze now I don't expect any bigger
changes to the option strings until release. So it's the right time to
update translations now.

This is the current status (percentage of translation):

sane-backends.bg.po (96.2%)
sane-backends.cs.po (92.8%)
sane-backends.da.po (100.0%)
sane-backends.de.po (99.7%)
sane-backends.es.po (40.2%)
sane-backends.fi.po (94.7%)
sane-backends.fr.po (90.1%)
sane-backends.it.po (100.0%)
sane-backends.nl.po (96.4%)
sane-backends.no.po (36.5%)
sane-backends.pt.po (23.7%)
sane-backends.ru.po (66.1%)
sane-backends.sv.po (100.0%)

Even if the percentage is near 100%, it doesn't harm to have a look at
the translations to check if they are correct.

New translations are always appreciated.

Here is a translation question: What does "8x8 Coarse Fatting" mean
(from leo.c)? Well, I know what 8x8 and coarse is, but I can't really
interpret "fatting".

Bye,
  Henning


From henning@meier-geinitz.de  Sun Oct 17 19:55:55 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:55:55 +0200
Subject: [sane-devel] Open bug reports
Message-ID: <20041017185555.GL12072@meier-geinitz.de>

Hi everyone,

There are currently 102 open bug reports for SANE. I'm quite sure that
some of them can be easily fixed.

If you are a SANE developer and have an account on alioth, please
logon on the alioth website. After login, you'll get a list with your
bug reports "My Assigned Items". These are the bug reports that have
been assigned to you. 

Please have a look at them. If you think they are bogus, write a short
comment and close them.

If you think it's a bug but not in your backend, write a short comment
and assign them to the "guilty" developer or "Nobody" if you don't
know which developer is the right one.

If it's a bug in your backend but it's not important decrease priority
and write a comment that you'll fix that later.

If there is not enough information, ask for more.

You'll get a mail once you have been assigned a bug and with every
change of that bug.

There are also quite some bugs that are not assigned to anyone because
they concern several backends or no backend at all. Please also have a
look at them.
Example: [ #300962 ] umax_pp & plustek: Harmonise option names

Also "normal" users are invited to add comments to the bug reports.
Maybe you have seen the same bug and can give more details? Or you
even know how to fix it? I recommend getting a login at alioth as
you'll be informed by mail when your bug is changed in this case. Also
you can attach files to bugs when you are logged in.

Happy bug-hunting!

Bye,
  Henning



From martin@mkcollins.org  Sun Oct 17 21:18:52 2004
From: martin@mkcollins.org (Martin Collins)
Date: Sun, 17 Oct 2004 21:18:52 +0100
Subject: [sane-devel] Translation status
In-Reply-To: <20041017184228.GK12072@meier-geinitz.de>
References: <20041017184228.GK12072@meier-geinitz.de>
Message-ID: <20041017211852.0bfeb848.martin@mkcollins.org>

On Sun, 17 Oct 2004 20:42:28 +0200
Henning Meier-Geinitz <henning@meier-geinitz.de> wrote:

> Here is a translation question: What does "8x8 Coarse Fatting" mean
> (from leo.c)? Well, I know what 8x8 and coarse is, but I can't
> really interpret "fatting".

Bizarre. Perhaps it should be "Fitting"? Doesn't make a great deal more
sense but at least it's an english word.

Martin


From johannes@sipsolutions.net  Sun Oct 17 21:58:24 2004
From: johannes@sipsolutions.net (Johannes Berg)
Date: Sun, 17 Oct 2004 22:58:24 +0200
Subject: [sane-devel] Translation status
In-Reply-To: <20041017184228.GK12072@meier-geinitz.de>
References: <20041017184228.GK12072@meier-geinitz.de>
Message-ID: <1098046704.5232.20.camel@johannes>

--=-BwDTxOoCFtEstoGY4Lzn
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2004-10-17 at 20:42 +0200, Henning Meier-Geinitz wrote:
> Here is a translation question: What does "8x8 Coarse Fatting" mean
> (from leo.c)? Well, I know what 8x8 and coarse is, but I can't really
> interpret "fatting".

It is a type of "rastern". See
http://www.pl32.com/tutorial/sraster/sraster.htm
for an image.

johannes

--=-BwDTxOoCFtEstoGY4Lzn
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (SIP Solutions)

iQIVAwUAQXLc66Vg1VMiehFYAQKDmQ/6AzwwK7P0DN0HLzRBLZ0S9LiAivr8AC9o
HJbWv2zS90PkMlljEEEVN/AvPKxjwvvR2IFDsXilPO0AZzEPqEkp4IZundgnjs/G
RqvcArMNntRJxNTuF6TVBTSo9rcaqypUr0w97HgB3ypJhYL2hJiQBwMNkI3Oxu4C
e8qmWL+EYW7fFTACrP6Wi4hkUWDYT3XwiioXNhnk0hfaf4YjHrC6dnARxnwYaLWT
+Esh9+MXZeBiCJKyUGtjOM6gmsFVKo5DJqdpJ4scUi5t+wLZY/5A0NW6v/RZILDw
D0UkopbZR+bbT0aba+KHAyu9goBQM1Ls2V+GBBAhlnB7jZSVJSMXqn3nBlWZtQWj
DMP2lDjue2ouiFnj0Y/QYdeSHdiv7nTGEP5jmt4RWULcoK/l+w+6m55x5kS3Dtaz
ZT4SaUrg1ZIoIpoH5DlB4sTnczSV190hs372C3jtN4FEHI/HO/oww3YNq2rYPvBZ
OO2CE9dgvoPrR+iKPsbIE5eiHGhFVuGT/bFCWWqN79xa2A1ZPeINWN3Pg9EyFh/N
4BUDVHCcfeKLA/maFk5L0yqbKScJbqev5mHrfwYjEgrNsisp8CXnOR8LXa0+W+pN
3F6NBoz217emhVqrr7KupA+Kai0nj9nfUw7IVKd+Hap7MESsFXpuzHK/UygYup7o
0DrCJmZ8+uk=
=VTx2
-----END PGP SIGNATURE-----

--=-BwDTxOoCFtEstoGY4Lzn--




From martin@mkcollins.org  Sun Oct 17 22:54:44 2004
From: martin@mkcollins.org (Martin Collins)
Date: Sun, 17 Oct 2004 22:54:44 +0100
Subject: [sane-devel] Translation status
In-Reply-To: <1098046704.5232.20.camel@johannes>
References: <20041017184228.GK12072@meier-geinitz.de>
 <1098046704.5232.20.camel@johannes>
Message-ID: <20041017225444.2305af39.martin@mkcollins.org>

On Sun, 17 Oct 2004 22:58:24 +0200
Johannes Berg <johannes@sipsolutions.net> wrote:

> It is a type of "rastern". See
> http://www.pl32.com/tutorial/sraster/sraster.htm
> for an image.

So it seems Fatting is the name of the inventor of a dither pattern,
like Bayer or Floyd Steinberg. No translation necessary.

Martin


From mattias.ellert@tsl.uu.se  Sun Oct 17 23:23:41 2004
From: mattias.ellert@tsl.uu.se (Mattias Ellert)
Date: Mon, 18 Oct 2004 00:23:41 +0200
Subject: [sane-devel] Translation status
In-Reply-To: <20041017225444.2305af39.martin@mkcollins.org>
References: <20041017184228.GK12072@meier-geinitz.de> <1098046704.5232.20.camel@johannes> <20041017225444.2305af39.martin@mkcollins.org>
Message-ID: <33453883-208B-11D9-B39B-0003930D2AFC@tsl.uu.se>

2004-10-17 kl. 23.54 skrev Martin Collins:

> On Sun, 17 Oct 2004 22:58:24 +0200
> Johannes Berg <johannes@sipsolutions.net> wrote:
>
>> It is a type of "rastern". See
>> http://www.pl32.com/tutorial/sraster/sraster.htm
>> for an image.
>
> So it seems Fatting is the name of the inventor of a dither pattern,
> like Bayer or Floyd Steinberg. No translation necessary.
>
> Martin
>

This is what is in there now. S=C3=A5 most translators have tried to =
find a=20
translation...

sane-backends-1.0.15-pre1/po/sane-backends.bg.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgstr "8x8 =D0=B3=D1=80=D1=
=83=D0=B1=20
Fatting"
--
sane-backends-1.0.15-pre1/po/sane-backends.bg.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgstr "8x8 =D1=84=D0=B8=D0=
=BD=20
Fatting"
--
sane-backends-1.0.15-pre1/po/sane-backends.cs.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.cs.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.cs.po-msgstr "8x8 hrub=C3=A9=20=

zv=C3=BDrazn=C4=9Bn=C3=AD (fatting)"
--
sane-backends-1.0.15-pre1/po/sane-backends.cs.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.cs.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.cs.po-msgstr "8x8 jemn=C3=A9=20=

zv=C3=BDran=C4=9Bn=C3=AD (fatting)"
--
sane-backends-1.0.15-pre1/po/sane-backends.da.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.da.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.da.po-msgstr "8x8 grov=20
fortykning"
--
sane-backends-1.0.15-pre1/po/sane-backends.da.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.da.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.da.po-msgstr "8x8 fin=20
fortykning"
--
sane-backends-1.0.15-pre1/po/sane-backends.de.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.de.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.de.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.de.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.de.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.de.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.es.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.es.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.es.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.es.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.es.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.es.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.fi.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.fi.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.fi.po-msgstr "8x8 raaka=20
lihavointi"
--
sane-backends-1.0.15-pre1/po/sane-backends.fi.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.fi.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.fi.po-msgstr "8x8 hieno=20
lihavointi"
--
sane-backends-1.0.15-pre1/po/sane-backends.fr.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.fr.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.fr.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.fr.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.fr.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.fr.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.it.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.it.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.it.po-msgstr "8x8 grana=20
grossa"
--
sane-backends-1.0.15-pre1/po/sane-backends.it.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.it.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.it.po-msgstr "8x8 grana fine"
--
sane-backends-1.0.15-pre1/po/sane-backends.nl.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.nl.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.nl.po-msgstr "8x8 Grof=20
Aandikken"
--
sane-backends-1.0.15-pre1/po/sane-backends.nl.po-#, fuzzy
sane-backends-1.0.15-pre1/po/sane-backends.nl.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.nl.po-msgstr "8x8 Fijn=20
Aandikken"
--
sane-backends-1.0.15-pre1/po/sane-backends.no.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.no.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.no.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.no.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.no.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.no.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.pt.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.pt.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.pt.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.pt.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.pt.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.pt.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.ru.po-#, fuzzy
sane-backends-1.0.15-pre1/po/sane-backends.ru.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.ru.po-msgstr "8x8 =
=D0=B3=D1=80=D1=83=D0=B1=D0=BE=D0=B5"
--
sane-backends-1.0.15-pre1/po/sane-backends.ru.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.ru.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.ru.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.sv.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.sv.po:msgid "8x8 Coarse=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.sv.po-msgstr "8x8 grov=20
f=C3=B6rtjockning"
--
sane-backends-1.0.15-pre1/po/sane-backends.sv.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.sv.po:msgid "8x8 Fine=20
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.sv.po-msgstr "8x8 fin=20
f=C3=B6rtjockning"

	Mattias



From martin@mkcollins.org  Mon Oct 18 00:06:08 2004
From: martin@mkcollins.org (Martin Collins)
Date: Mon, 18 Oct 2004 00:06:08 +0100
Subject: [sane-devel] Translation status
In-Reply-To: <33453883-208B-11D9-B39B-0003930D2AFC@tsl.uu.se>
References: <20041017184228.GK12072@meier-geinitz.de>
 <1098046704.5232.20.camel@johannes>
 <20041017225444.2305af39.martin@mkcollins.org>
 <33453883-208B-11D9-B39B-0003930D2AFC@tsl.uu.se>
Message-ID: <20041018000608.3c4f4917.martin@mkcollins.org>

On Mon, 18 Oct 2004 00:23:41 +0200
Mattias Ellert <mattias.ellert@tsl.uu.se> wrote:

> This is what is in there now. S=E5 most translators have tried to find
> a translation...

> sane-backends-1.0.15-pre1/po/sane-backends.cs.po-msgstr "8x8 hrub=E9=20
> zv=FDrazn__n=ED (fatting)"

> sane-backends-1.0.15-pre1/po/sane-backends.da.po-msgstr "8x8 grov=20
> fortykning"

> sane-backends-1.0.15-pre1/po/sane-backends.fi.po-msgstr "8x8 raaka=20
> lihavointi"

> sane-backends-1.0.15-pre1/po/sane-backends.it.po-msgstr "8x8 grana=20
> grossa"

> sane-backends-1.0.15-pre1/po/sane-backends.nl.po-msgstr "8x8 Grof=20
> Aandikken"

> sane-backends-1.0.15-pre1/po/sane-backends.sv.po-msgstr "8x8 grov=20
> f=F6rtjockning"

I'm no linguist but it looks like mostly variations on "fat" or
"fattening". I bet the guy is as skinny as a rake.

Martin


From olaf@epkowa.co.jp  Mon Oct 18 02:48:16 2004
From: olaf@epkowa.co.jp (Olaf Meeuwissen)
Date: Mon, 18 Oct 2004 10:48:16 +0900
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <20041015123703.GF3623@meier-geinitz.de> (Henning
 Meier-Geinitz's message of "Fri, 15 Oct 2004 14:37:03 +0200")
References: <200410132249.08934.mreuther@umich.edu>
 <200410141257.21475.mreuther@umich.edu>
 <20041014173205.GF12141@meier-geinitz.de>
 <200410141930.32684.mreuther@umich.edu>
 <4A35F8D0-1E3F-11D9-820C-000A957E40E8@khk.net>
 <87u0sw3gnw.fsf@zen.epkowa.co.jp>
 <20041015123703.GF3623@meier-geinitz.de>
Message-ID: <874qksn6e7.fsf@zen.epkowa.co.jp>

Henning Meier-Geinitz <henning@meier-geinitz.de> writes:

> Hi,
>
> On Fri, Oct 15, 2004 at 10:37:39AM +0900, Olaf Meeuwissen wrote:
>> Karl Heinz Kremer <khk@khk.net> writes:
>> 
>> > It looks like this scanner does not "speak" the ESC/I protocol. At
>> > least not any flavor that the EPSON backend supports. Maybe Olaf can
>> > shed some light on this.
>> 
>> I guess I could ;-)
>> 
>> As the EPSON drivers say, this is a GT-F600.  It does not speak ESC/I.
>> It will be supported by iscan's epkowa backend in the near future (but
>> first we'll get a release for a bunch of all-in-ones).
>
> I've added Perfection 4160 and GT-F600 as unsupported to our lists for
> now (with some details from your mail).

That's the Perfection 4180, but I see you've added it correctly in
unsupported.desc.

-- 
Olaf Meeuwissen                            EPSON KOWA Corporation, PF1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2


From sirius-c@iname.com  Mon Oct 18 04:59:09 2004
From: sirius-c@iname.com (Jason Anderson)
Date: Sun, 17 Oct 2004 22:59:09 -0500
Subject: [sane-devel] Re: Scanner Problems
Message-ID: <20041018035909.4D9636EEE9@ws1-5.us4.outblaze.com>

I'm talking about version 1.0.14, I think it's CVS, but I don't know.  And =
yep, I need to turn it 180 just to properly scan it.

>
>=20
> Hi,
>=20
> On Sun, Oct 17, 2004 at 01:16:06PM -0500, Jason Anderson wrote:
> > I've just got a CanoScan N650U.  When I use the current backends,
>=20
> With current backends you mean the version from CVS?
>=20
> > however, the darn picture is upside down!  I don't know why, either.
>=20
> What's the last version of sane-backends that worked?
>=20
> "Upside down" means that if you turn around (180=B0) the image that is
> to be scanned the result will be ok?
>=20
> Bye,
>   Henning
>=20
>=20

--=20
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm



From gerhard@gjaeger.de  Mon Oct 18 13:04:58 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Mon, 18 Oct 2004 14:04:58 +0200
Subject: [sane-devel] Re: Scanner Problems
In-Reply-To: <20041018035909.4D9636EEE9@ws1-5.us4.outblaze.com>
References: <20041018035909.4D9636EEE9@ws1-5.us4.outblaze.com>
Message-ID: <200410181404.58155.gerhard@gjaeger.de>

On Monday 18 October 2004 05:59, Jason Anderson wrote:
> I'm talking about version 1.0.14, I think it's CVS, but I don't know.  =
And
> yep, I need to turn it 180 just to properly scan it.

Which is the SANE version, that used to work? I'm pretty sure, that you w=
on't
find any other version that did it the other way. When opening the scanne=
r,
the sensor home position is on that side, where the button is located.=20

Ciao,
  Gerhard

>
> > Hi,
> >
> > On Sun, Oct 17, 2004 at 01:16:06PM -0500, Jason Anderson wrote:
> > > I've just got a CanoScan N650U.  When I use the current backends,
> >
> > With current backends you mean the version from CVS?
> >
> > > however, the darn picture is upside down!  I don't know why, either=
=2E
> >
> > What's the last version of sane-backends that worked?
> >
> > "Upside down" means that if you turn around (180=B0) the image that i=
s
> > to be scanned the result will be ok?
> >
> > Bye,
> >   Henning



From sushyad@yahoo.com  Mon Oct 18 17:03:55 2004
From: sushyad@yahoo.com (Susheel Yadav)
Date: Mon, 18 Oct 2004 09:03:55 -0700 (PDT)
Subject: [sane-devel] Need help analyzing USBSnoopy logs for Microtek Scanmaker 5600
In-Reply-To: <20040915221215.11604.qmail@web13903.mail.yahoo.com>
Message-ID: <20041018160355.27003.qmail@web13925.mail.yahoo.com>

Some good news on the Microtek Scanmaker 5600 front -
with Karsten's and Bertrik's help, I have been able to
decode the usb protocol for setting/reading status,
setting scan window and other scan parameters etc.
Using javax-usb, I have been able to read image data
through bulk transfer. I will start developing the
sane backend very soon. As a template, I plan to use
the sm3600 usb code.

I have a couple of questions regarding sane
integration:
1. Once I have the raw image data, what do I do with
it?
2. How do I process the raw image data to create
usable image?
3. Is there any common core sane code to handle the
raw image data like saving it in different formats?

Thanks!

Susheel

--- Susheel Yadav <sushyad@yahoo.com> wrote:

> Karsten,
> Please go ahead and send me the documents.
> 
> Bertrik,
> Your analysis is right on! So all that huge chunk of
> data in the beginning is just for calibration, and
> data the towards the end is the image data.
> 
> I will play around with those parameters and try to
> get some image. After that I will need to know how
> to
> use the calibration data.
> 
> Thanks a lot guys!
> 
> --- Karsten Festag <karsten.festag@gmx.de> wrote:
> 
> > Hi,
> > 
> > I just looked curiously on the data and I think
> > there are some similarities 
> > between the scsi based scanners driven by the
> > microtek2 backend and the 5600:
> > 
> > command 0x24 is used to setup the scan window,
> > probably first a fixed window 
> > for calibration and second the actual scan window.
> > 
> > command 0x28 0xnn 0x80 reads image information
> > (width, height, bytes)
> > command 0x28 0xnn 0x81 reads system status (Lamps
> > on/off, buttons,) and 0x2a 
> > 0xnn 0x81 should set the status.
> > command 0x28 0xnn 0x82 reads scanner attributes
> > (resolution, width, heigt of 
> > the scan area.......)
> > 
> > Maybe a look at the microtek2 sources helps you. I
> > also have some (quite old) 
> > documentation but it may help. Tell me if I shall
> > send it to you (its an ugly 
> > MS Word file :-()
> > 
> > Regards,
> > 
> > Karsten
> > 
> > 
> > On Wednesday 15 September 2004 21:57, Susheel
> Yadav
> > wrote:
> > > Thanks a lot Bertrik for your analysis. I have
> > figured
> > > out some things - I have written those down in
> the
> > > last  link on the web page.
> > >
> > > *request=0x24 value=0x00 data=0x45 bytes
> > > The data transferred in this request did not
> > change
> > > even if I moved the scan area horizontally
> keeping
> > the
> > > size constant. This makes me think that maybe it
> > scans
> > > the whole row and the software clips the image
> > later.
> > > What do you think?
> > >
> > > *request=0x26 value=0x00 data=0xef00 bytes
> > > This happens before bulk transfers, and the data
> > > returned in Nth step is sent to the scanner in
> the
> > > (N+1)th request.
> > >
> > > *The bulk transfer is followed by a small
> transfer
> > of
> > > 0x40 bytes. This returns 0x10 bytes. The last
> 0x30
> > > bytes sent always remain same, and the first
> 0x10
> > > bytes are the ones that were returned from the
> > > previous cycle. Could this signify the position
> of
> > the
> > > next chunk of data?
> > >
> > > *request=0x28, 0x40, 0x83, 0x12 repeat and I
> think
> > > they are status check. The windows driver has a
> > > scanner detector utility which when turned on,
> > keeps
> > > sending those packets.
> > >
> > > *request=0x28 value=0x83
> > > This request gets the data that is send back in
> > some
> > > 0x40 0x2a 0x81 requests.
> > >
> > > *request=0x29 seems to denote the end of
> transfer
> > > since there is no more bulk data after that.
> > >
> > > --- Bertrik Sikken <bertrik@zonnet.nl> wrote:
> > > > Susheel Yadav wrote:
> > > > > Hi,
> > > > > I am trying to write the linux driver for
> > Microtek
> > > > > Scanmaker 5600 scanner. I used USBSnoopy to
> > > >
> > > > generate
> > > >
> > > > > these logs from VMWare/Win2k. I have
> filtered
> > out
> > > >
> > > > the
> > > >
> > > > > big bulk transfers. The log files are still
> in
> > > >
> > > > ~200KB
> > > >
> > > > > range. I am providing a link below with the
> > log
> > > >
> > > > files.
> > > >
> > > > > I have made some progress in identifying the
> > > >
> > > > status
> > > >
> > > > > check packets, and some pattern in the bulk
> > > >
> > > > transfers,
> > > >
> > > > > but I have no idea what those medium sized
> > control
> > > > > packets mean. I would appreciate any help.
> > > > >
> > > > > http://blanca.homelinux.com/usblogs/
> > > > >
> > > > > Thank you very much!
> > > >
> > > > What medium sized control packets do you mean?
> > > >
> > > >
> > > > I looked a bit at the logs and noticed 10
> unique
> > > > patterns:
> > > >
> > > > * request=0x12, value=0x00: read version info?
> > > > The data returned by this transfer contains
> the
> > > > strings
> > > > "ScanMaker 5600  1.30"
> > > > "NowV0.10NewV0.10"
> > > >
> > > > * request=0x24, value=0x00: write 0x45 bytes
> of
> > scan
> > > > settings?
> > > > This transfer contains numbers like 1200, 600,
> > 300,
> > > > which are likely
> > > > DPI or LPI resolutions. I think that scan area
> > is
> > > > also coded in this
> > > > transfer. It noticed this transfer happens
> twice
> > > > (once for calibration,
> > > > then once for the actual scan?)
> > > >
> > > > * request=0x26, value=0x00: prepare bulk read
> > (index
> > > > = length)
> > > > This transfer always seems to happen just
> before
> > a
> > > > bulk read
> > > >
> > > > * request=0x28, value=0x80: get a bunch of
> bytes
> > > > (don't know what)
> > > >
> > > > * request=0x28, value=0x81: read some 9-byte
> > buffer
> > > >
> > > > * request=0x28, value=0x82: read scan
> > capabilities?
> > > > This transfer also has typical DPI numbers,
> but
> > > > always seem to be
> > > > the same (not always same length though)
> > > >
> > > > * request=0x28, value=0x83: read status byte?
> > > > (00 = ready, 08 = not ready?)
> > > >
> > > > * request=0x29, value=0x2101: prepare bulk
> write
> 
=== message truncated ===



		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com


From henning@meier-geinitz.de  Mon Oct 18 17:21:03 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 18 Oct 2004 18:21:03 +0200
Subject: [sane-devel] Need help analyzing USBSnoopy logs for Microtek Scanmaker 5600
In-Reply-To: <20041018160355.27003.qmail@web13925.mail.yahoo.com>
References: <20040915221215.11604.qmail@web13903.mail.yahoo.com> <20041018160355.27003.qmail@web13925.mail.yahoo.com>
Message-ID: <20041018162103.GA4761@meier-geinitz.de>

Hi,

On Mon, Oct 18, 2004 at 09:03:55AM -0700, Susheel Yadav wrote:
> Some good news on the Microtek Scanmaker 5600 front -
> with Karsten's and Bertrik's help, I have been able to
> decode the usb protocol for setting/reading status,
> setting scan window and other scan parameters etc.
> Using javax-usb, I have been able to read image data
> through bulk transfer. I will start developing the
> sane backend very soon. As a template, I plan to use
> the sm3600 usb code.

Good news. But please don't use direct calls to libusb as done in
sm3600. Instead use the sanei_usb_* functions that are provided by
sanei/sanei_usb.c. If backends use direct calls to libusb, they can't
be used with other USB access methods and every backend muste be
changed if e.g. a new USB access library is to be supported by SANE.

> I have a couple of questions regarding sane
> integration:
> 1. Once I have the raw image data, what do I do with
> it?

In the SANE backend, you implement the function sane_read() which is
called by the frontend to get the data from the backend. 

> 2. How do I process the raw image data to create
> usable image?

Depending on the scanner you may need to do line calibration
(correction of the brightness difference of every single CCD/CIS
pixel) and/or line distance correction (in color mode). More
intelligent scanners do that internally, however.

After that you process the image data to be compatible with the SANE
protocol (see SANE standard) and return it by sane_read().

> 3. Is there any common core sane code to handle the
> raw image data like saving it in different formats?

That's done by the frontend. As a backend author you don't need to
care about that.

Bye,
  Henning


From till.kamppeter@gmx.net  Mon Oct 18 19:29:19 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Mon, 18 Oct 2004 20:29:19 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Message-ID: <41740B7F.5040507@gmx.net>

Oi,

I got the above-mentioned scanners for some days for testing.
Unfortunately without the Windows CDs. Can someone send me the firmware
files for them (*.bin) files? The firmware file in Epson's IScan package
seems not to work, too old or so. XSane segfaults with it.

Thanks.

    Till



From drjones@vii.com  Mon Oct 18 18:48:08 2004
From: drjones@vii.com (Dr. Jones)
Date: Mon, 18 Oct 2004 11:48:08 -0600
Subject: [sane-devel] Scanjet 4C - newbie with linux and sane scanning
In-Reply-To: <41740B7F.5040507@gmx.net>
References: <41740B7F.5040507@gmx.net>
Message-ID: <417401D8.3020909@vii.com>

I am writing to get some help and pointers and to hopefully avoid the 
pitfalls.

I have been running debian 3.0 a while now, but have yet to hook up my 
scanner, which now resides on an older windows machine. It uses the SCSI 
card interface, and works well on my win 98se box; but I want to 
eliminate Windows completely from my network here.

Any suggestions other than to dive in and try it on my machine? I am 
thinking of just installing linux on my current 98se box...and then 
setting up SANE to handle the scanning, hoping that it's not too 
painful. I'd love to hear from others who use a ScanJet 4c device.

Scott

-- 
Dr. Scott S. Jones
Hands-On Chiropractic 
IRC: irc.freenode.net #utah
Yahoo: sanchiro12




From johannes@sipsolutions.net  Mon Oct 18 19:20:26 2004
From: johannes@sipsolutions.net (Johannes Berg)
Date: Mon, 18 Oct 2004 20:20:26 +0200
Subject: [sane-devel] update net.tex for sane1 documentation
Message-ID: <1098123627.5219.23.camel@johannes>

--=-xv5kleSaPGSbmUmx0lXI
Content-Type: multipart/mixed; boundary="=-JRc1KVGyz2RW6C1OPppe"


--=-JRc1KVGyz2RW6C1OPppe
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Here's a patch to add RPC codes and a short explanation of transferred
data to net.tex, with this the document is IMHO much more readable since
now you actually know what data is on the wire :)

johannes

--=-JRc1KVGyz2RW6C1OPppe
Content-Disposition: attachment; filename=net.tex.patch
Content-Type: text/x-patch; name=net.tex.patch; charset=ISO-8859-15
Content-Transfer-Encoding: base64

SW5kZXg6IG5ldC50ZXgNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT0NClJDUyBmaWxlOiAvY3Zzcm9vdC9zYW5lL3NhbmUt
YmFja2VuZHMvZG9jL25ldC50ZXgsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjINCmRpZmYgLXUg
LXIxLjIgbmV0LnRleA0KLS0tIG5ldC50ZXgJMjAgTm92IDIwMDAgMTg6NDk6MTYgLTAwMDAJMS4y
DQorKysgbmV0LnRleAkxOCBPY3QgMjAwNCAxODoxOToxMSAtMDAwMA0KQEAgLTE0Miw4ICsxNDIs
MTQgQEANCiBjbGllbnQgc2lkZSAodGhlIG5ldHdvcmsgYmFja2VuZCktLS1hIHNlcnZlciBpcyBy
ZXN0cmljdGVkIHRvDQogYW5zd2VyaW5nIHJlcXVlc3QgYnkgdGhlIGNsaWVudC4NCiANCitUaGUg
ZGF0YSB0cmFuc2ZlcnJlZCBmcm9tIHRoZSBjbGllbnQgdG8gdGhlIHNlcnZlciBpcyBjb21wcm9t
aXNlZCBvZg0KK3RoZSBSUEMgY29kZSAoYXMgYSBcY29kZXtTQU5FXF9XT1JEfSksIGZvbGxvd2Vk
IGJ5IHRoZSBhcmd1bWVudHMgaW4gdGhlDQorb3JkZXIgbGlzdGVkLiBUaGUgc2VydmVyIHJlcGx5
IGNvbnNpc3RzIG9ubHkgb2YgdGhlIGRhdGEgZ2l2ZW4gYmVsb3cuDQorDQogXHN1YnNlY3Rpb257
XGNvZGV7XGRlZm57U0FORVxfTkVUXF9JTklUfX19DQogDQorUlBDIENvZGU6IDANCisNCiBUaGlz
IFJQQyBlc3RhYmxpc2hlcyBhIGNvbm5lY3Rpb24gdG8gYSBwYXJ0aWN1bGFyIFNBTkUgbmV0d29y
ayBkYWVtb24uDQogSXQgbXVzdCBiZSB0aGUgZmlyc3QgY2FsbCBpbiBhIFNBTkUgbmV0d29yayBz
ZXNzaW9uLiAgVGhlIHBhcmFtZXRlcg0KIGFuZCByZXBseSBhcmd1bWVudHMgZm9yIHRoaXMgY2Fs
bCBhcmUgc2hvd24gaW4gdGhlIHRhYmxlIGJlbG93Og0KQEAgLTE4MSw2ICsxODcsOCBAQA0KIA0K
IFxzdWJzZWN0aW9ue1xjb2Rle1xkZWZue1NBTkVcX05FVFxfR0VUXF9ERVZJQ0VTfX19DQogDQor
UlBDIENvZGU6IDENCisNCiBUaGlzIFJQQyBpcyB1c2VkIHRvIG9idGFpbiB0aGUgbGlzdCBvZiBk
ZXZpY2VzIGFjY2Vzc2libGUgYnkgdGhlIFNBTkUNCiBkYWVtb24uDQogXGJlZ2lue2NlbnRlcn0N
CkBAIC0yMDAsNiArMjA4LDggQEANCiANCiBcc3Vic2VjdGlvbntcY29kZXtcZGVmbntTQU5FXF9O
RVRcX09QRU59fX0NCiANCitSUEMgQ29kZTogMg0KKw0KIFRoaXMgUlBDIGlzIHVzZWQgdG8gb3Bl
biBhIGNvbm5lY3Rpb24gdG8gYSByZW1vdGUgU0FORSBkZXZpY2UuDQogXGJlZ2lue2NlbnRlcn0N
CiBcYmVnaW57dGFidWxhcn17bGx9DQpAQCAtMjI0LDYgKzIzNCw4IEBADQogDQogXHN1YnNlY3Rp
b257XGNvZGV7XGRlZm57U0FORVxfTkVUXF9DTE9TRX19fQ0KIA0KK1JQQyBDb2RlOiAzDQorDQog
VGhpcyBSUEMgaXMgdXNlZCB0byBjbG9zZSBhIGNvbm5lY3Rpb24gdG8gYSByZW1vdGUgU0FORSBk
ZXZpY2UuDQogXGJlZ2lue2NlbnRlcn0NCiBcYmVnaW57dGFidWxhcn17bGx9DQpAQCAtMjQwLDYg
KzI1Miw4IEBADQogDQogXHN1YnNlY3Rpb257XGNvZGV7XGRlZm57U0FORVxfTkVUXF9HRVRcX09Q
VElPTlxfREVTQ1JJUFRPUlN9fX0NCiANCitSUEMgQ29kZTogNA0KKw0KIFRoaXMgUlBDIGlzIHVz
ZWQgdG8gb2J0YWluIHtcZW0gYWxsXC99IHRoZSBvcHRpb24gZGVzY3JpcHRvcnMgZm9yIGENCiBy
ZW1vdGUgU0FORSBkZXZpY2UuDQogXGJlZ2lue2NlbnRlcn0NCkBAIC0yNjcsNiArMjgxLDggQEAN
CiANCiBcc3Vic2VjdGlvbntcY29kZXtcZGVmbntTQU5FXF9ORVRcX0NPTlRST0xcX09QVElPTn19
fQ0KIA0KK1JQQyBDb2RlOiA1DQorDQogVGhpcyBSUEMgaXMgdXNlZCB0byBjb250cm9sIChpbnF1
aXJlLCBzZXQsIG9yIHNldCB0byBhdXRvbWF0aWMpIGENCiBzcGVjaWZpYyBvcHRpb24gb2YgYSBy
ZW1vdGUgU0FORSBkZXZpY2UuDQogXGJlZ2lue2NlbnRlcn0NCkBAIC0zMTgsNiArMzM0LDggQEAN
CiANCiBcc3Vic2VjdGlvbntcY29kZXtcZGVmbntTQU5FXF9ORVRcX0dFVFxfUEFSQU1FVEVSU319
fQ0KIA0KK1JQQyBDb2RlOiA2DQorDQogVGhpcyBSUEMgaXMgdXNlZCB0byBvYnRhaW4gdGhlIHNj
YW4gcGFyYW1ldGVycyBvZiBhIHJlbW90ZSBTQU5FDQogZGV2aWNlLg0KIFxiZWdpbntjZW50ZXJ9
DQpAQCAtMzM3LDYgKzM1NSw4IEBADQogDQogXHN1YnNlY3Rpb257XGNvZGV7XGRlZm57U0FORVxf
TkVUXF9TVEFSVH19fQ0KIA0KK1JQQyBDb2RlOiA3DQorDQogVGhpcyBSUEMgaXMgdXNlZCB0byBz
dGFydCBpbWFnZSBhY3F1aXNpdGlvbiAoc2Nhbm5pbmcpLg0KIFxiZWdpbntjZW50ZXJ9DQogXGJl
Z2lue3RhYnVsYXJ9e2xsfQ0KQEAgLTM4Nyw2ICs0MDcsOCBAQA0KIA0KIFxzdWJzZWN0aW9ue1xj
b2Rle1xkZWZue1NBTkVcX05FVFxfQ0FOQ0VMfX19DQogDQorUlBDIENvZGU6IDgNCisNCiBUaGlz
IFJQQyBpcyB1c2VkIHRvIGNhbmNlbCB0aGUgY3VycmVudCBvcGVyYXRpb24gb2YgYSByZW1vdGUg
U0FORQ0KIGRldmljZS4NCiBcYmVnaW57Y2VudGVyfQ0KQEAgLTQwNSw2ICs0MjcsOCBAQA0KIFxz
dWJzZWN0aW9ue1xjb2Rle1xkZWZue1NBTkVcX05FVFxfQVVUSE9SSVpFfX19XGxhYmVse3NlYzph
dXRob3JpemF0aW9ufQ0KIFxpbmRleHtuZXR3b3JrIGF1dGhvcml6YXRpb259DQogDQorUlBDIENv
ZGU6IDkNCisNCiBUaGlzIFJQQyBpcyB1c2VkIHRvIHBhc3MgYXV0aG9yaXphdGlvbiBkYXRhIGZy
b20gdGhlIG5ldCBjbGllbnQgdG8gdGhlDQogbmV0IHNlcnZlci4NCiBcYmVnaW57Y2VudGVyfQ0K
QEAgLTQ0MCw2ICs0NjQsOCBAQA0KIA0KIA0KIFxzdWJzZWN0aW9ue1xjb2Rle1xkZWZue1NBTkVc
X05FVFxfRVhJVH19fQ0KKw0KK1JQQyBDb2RlOiAxMA0KIA0KIFRoaXMgUlBDIGlzIHVzZWQgdG8g
ZGlzY29ubmVjdCBhIG5ldCBjbGllbnQgZnJvbSBhIG5ldCBzZXJ2ZXIuICBUaGVyZQ0KIGFyZSBu
byByZXF1ZXN0IG9yIHJlcGx5IGFyZ3VtZW50cyBpbiB0aGlzIGNhbGwuICBBcyBhIHJlc3VsdCBv
ZiB0aGlzDQo=


--=-JRc1KVGyz2RW6C1OPppe--

--=-xv5kleSaPGSbmUmx0lXI
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (SIP Solutions)

iQIVAwUAQXQJaKVg1VMiehFYAQIZuQ//fN3X4utoVGDvLMMoK/8GrDl4JJgzpmIO
20U11mc7emWrqEoJGxAw9yRWHG4qgVayqI/aXu3Kq3Rqin7WTlzUwV/Xe2+bdYqL
BjeFzM7qEWxTexxkw5/eCADb/++HbF4/zgL7Y91MaL0+yIFtsnbT7bhNOKRPPiML
ROLBoSoIsDGYiL4GAdjWscyKJGulcs3sX5VjGcWodZZMZBqYjiy/xl7Hhsw72EEU
DutsDAbtdFk0RzSe3jb78uT1UV/inQSAgCDrGgvEF6wXp9jOuzNyckSsK8HwtXMv
tI1eCcjaJuYfSykwlHFsWH0clLWcL3dbjVu6iBi2dK15rLKccuCXxQ5qhXqLbhrf
oaXbHsJP6t1WJqGg6POJa/bBcZExS20RxLQv5MWwKfs0YuXCj6Vx4nytPClHpJ1G
mvgo+PeGT/AJLqubEn+DIMARn9cBN8oTxdic3Ve72E76bc+Q/mCN5PXqsxA3o1VV
+nUogT4syeKR+vx3Hrl4VUvmVE1kPImK7SS7MJQjiNjN/r+2PqFnfrjKbKjfHeFv
ZFMFDDA4+nK+7iulj7MtHNMBQ4i/388LqPL/kzwgTqpzC9ebsN77kMEFlFk9QDvh
GbcSOZVrN8uI5UbTNPNSc9rc0VbkRCoisDXFn//SlxO7CJnb4lNGebuQKzBGcrJh
bcXlmtknm1Q=
=iYR4
-----END PGP SIGNATURE-----

--=-xv5kleSaPGSbmUmx0lXI--




From martin@mkcollins.org  Mon Oct 18 22:31:27 2004
From: martin@mkcollins.org (Martin Collins)
Date: Mon, 18 Oct 2004 22:31:27 +0100
Subject: [sane-devel] Scanjet 4C - newbie with linux and sane scanning
In-Reply-To: <417401D8.3020909@vii.com>
References: <41740B7F.5040507@gmx.net>
 <417401D8.3020909@vii.com>
Message-ID: <20041018223127.374c47f5.martin@mkcollins.org>

On Mon, 18 Oct 2004 11:48:08 -0600
"Dr. Jones" <drjones@vii.com> wrote:

> I am writing to get some help and pointers and to hopefully avoid
> the pitfalls.
...
> Any suggestions other than to dive in and try it on my machine?

If the default kernel doesn't support your SCSI card you will need to
find or compile one that does. Knowing what chipset it uses will help
there. Once your card is recognised you have to set appropriate
permissions on the device files so non-root users can use the scanner.

Once you have got your SCSI configured properly it should be easy. Just
  apt-get install xsane
and you're good to go. If it doesn't go start by reading man sane-scsi
and sane-hp then post your logs and other details here.

Martin


From khk@khk.net  Mon Oct 18 22:52:10 2004
From: khk@khk.net (Karl Heinz Kremer)
Date: Mon, 18 Oct 2004 17:52:10 -0400
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41740B7F.5040507@gmx.net>
References: <41740B7F.5040507@gmx.net>
Message-ID: <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net>

You can download them from EPSON's web site:

http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? 
BV_UseBVCookie=yes&oid=41623&infoType=Overview
http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? 
BV_UseBVCookie=yes&oid=41624&infoType=Overview

On Oct 18, 2004, at 2:29 PM, Till Kamppeter wrote:

> Oi,
>
> I got the above-mentioned scanners for some days for testing.
> Unfortunately without the Windows CDs. Can someone send me the firmware
> files for them (*.bin) files? The firmware file in Epson's IScan  
> package
> seems not to work, too old or so. XSane segfaults with it.
>
> Thanks.
>
>    Till
>
>
> -- 
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to sane-devel-request@lists.alioth.debian.org



From janunez07@hotmail.com  Tue Oct 19 14:29:51 2004
From: janunez07@hotmail.com (José Alberto Nuñez Aranguren)
Date: Tue, 19 Oct 2004 09:29:51 -0400
Subject: [sane-devel] Compatibility with scanner HP 8290
Message-ID: <BAY24-F304Atg2c7qIA0000bd28@hotmail.com>

  Hi,  I'm looking for information to use scanner HP8290 with sanelib.

   Does SANE compatible with this scanner?

regards

JAN

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.com/



From till.kamppeter@gmx.net  Tue Oct 19 16:03:14 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Tue, 19 Oct 2004 17:03:14 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net>
References: <41740B7F.5040507@gmx.net> <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net>
Message-ID: <41752CB2.8000504@gmx.net>

Thank you for the links. The Windows driver packages and so the firmware 
files are absolutely the same for both the 2480 and the 2580 scanners. 
Unfortunately, both scanners do not work.

I have specified the firmware file in /etc/sane.d/snapscan.conf and 
"scanimage -L" confirms that "snapscan" is the driver in use for both 
models. I am using sane-backends 1.15-pre1.

To get a debug log I executed

SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm 2> eps2580debug.log

The log files are

http://www.linuxprinting.org/till/tmp/eps2480debug.log
http://www.linuxprinting.org/till/tmp/eps2580debug.log

    Till


Karl Heinz Kremer wrote:
> You can download them from EPSON's web site:
> 
> http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? 
> BV_UseBVCookie=yes&oid=41623&infoType=Overview
> http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? 
> BV_UseBVCookie=yes&oid=41624&infoType=Overview
> 
> On Oct 18, 2004, at 2:29 PM, Till Kamppeter wrote:
> 
>> Oi,
>>
>> I got the above-mentioned scanners for some days for testing.
>> Unfortunately without the Windows CDs. Can someone send me the firmware
>> files for them (*.bin) files? The firmware file in Epson's IScan  package
>> seems not to work, too old or so. XSane segfaults with it.
>>
>> Thanks.
>>
>>    Till
>>
>>
>> -- 
>> sane-devel mailing list: sane-devel@lists.alioth.debian.org
>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>             to sane-devel-request@lists.alioth.debian.org
> 
> 
> 



From gerard@gkall.hobby.nl  Tue Oct 19 16:55:05 2004
From: gerard@gkall.hobby.nl (gerard klaver)
Date: Tue, 19 Oct 2004 15:55:05 +0000
Subject: [sane-devel] Compatibility with scanner HP 8290
In-Reply-To: <BAY24-F304Atg2c7qIA0000bd28@hotmail.com>
References: <BAY24-F304Atg2c7qIA0000bd28@hotmail.com>
Message-ID: <1098201305.1604.3.camel@gk-lex3>

On Tue, 2004-10-19 at 13:29, Jos=E9 Alberto Nu=F1ez Aranguren wrote:
>   Hi,  I'm looking for information to use scanner HP8290 with sanelib.
>=20
>    Does SANE compatible with this scanner?
>=20
> regards
>=20
> JAN

See this link below for some information about your scanner (its not
supported).

A start is to fill the mentioned form on this page with the missing=20
information.

 http://www.sane-project.org/unsupported/hp-scanjet-8290.html

--=20
----------
m.vr.gr.
Gerard Klaver



From hfiguiere@teaser.fr  Tue Oct 19 18:51:03 2004
From: hfiguiere@teaser.fr (Hubert Figuiere)
Date: Tue, 19 Oct 2004 13:51:03 -0400
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <20041015125640.GH3623@meier-geinitz.de>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net>
 <20041015120814.GB3623@meier-geinitz.de>
 <200410151447.15977.livhu.tshisikule@telkomsa.net>
 <20041015125640.GH3623@meier-geinitz.de>
Message-ID: <1098208264.27006.35.camel@atlan>

On Fri, 2004-10-15 at 14:56 +0200, Henning Meier-Geinitz wrote:
> > found USB scanner (vendor=0x0b3c [Olivetti], product=0xa880 [Job_Jet
> M400]) at libusb:003:002
> 
> Thanks. 0x03bc is really Olivetti so they haven't just used a HP
> device and printed a new logo on the case.
> 

They can still change the USB IDs in the firmware and still be
compatible. No ?

This is the case for rebadjed Lexmark 1150 (all-in-one) that are sold by
Dell as A920. They show up as Dell devices.

Hub
-- 
Crazy French - http://www.figuiere.net/hub/



From Oliver.Schwartz@gmx.de  Tue Oct 19 19:38:58 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Tue, 19 Oct 2004 20:38:58 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41752CB2.8000504@gmx.net>
References: <41740B7F.5040507@gmx.net> <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net> <41752CB2.8000504@gmx.net>
Message-ID: <200410192039.00356.Oliver.Schwartz@gmx.de>

Hi,

> http://www.linuxprinting.org/till/tmp/eps2480debug.log
> http://www.linuxprinting.org/till/tmp/eps2580debug.log

>[snapscan] sense_handler: Hardware error. (0x00, 0x04)

according to my docs this means "scan module locked". You probably 
didn't remove the transportation lock. For Benq scanners it's a small 
switch on the bottom side of the scanner.

/Oliver


From msampson@ic.sunysb.edu  Tue Oct 19 20:39:52 2004
From: msampson@ic.sunysb.edu (Mbosowo I Sampson)
Date: Tue, 19 Oct 2004 15:39:52 -0400 (EDT)
Subject: [sane-devel] clean up usbsnoop logs
Message-ID: <Pine.SOC.4.60.0410191537500.23235@sparky.ic.sunysb.edu>

I would like to post some usbsnoop logs to get some feedback, but the 
files are huge. I was wondering what scripts people used to strip the big 
bulk transfers from their logs. I have a web account that only gives me 
20mb of space, but my average log size is about 30Megs.


 							Mboso


From gerard@gkall.hobby.nl  Tue Oct 19 22:55:01 2004
From: gerard@gkall.hobby.nl (gerard klaver)
Date: Tue, 19 Oct 2004 21:55:01 +0000
Subject: [sane-devel] clean up usbsnoop logs
In-Reply-To: <Pine.SOC.4.60.0410191537500.23235@sparky.ic.sunysb.edu>
References: <Pine.SOC.4.60.0410191537500.23235@sparky.ic.sunysb.edu>
Message-ID: <1098222901.1604.18.camel@gk-lex3>

On Tue, 2004-10-19 at 19:39, Mbosowo I Sampson wrote:
> I would like to post some usbsnoop logs to get some feedback, but the 
> files are huge. I was wondering what scripts people used to strip the big 
> bulk transfers from their logs. I have a web account that only gives me 
> 20mb of space, but my average log size is about 30Megs.
> 
> 
>  							Mboso


See SANE CVS experimental/usbsnoop for a awk script

See the SANE mailing list archive for a spike4.pl (perl script) file

See http://spca50x.sourceforge.net/spca50x.php?page=tools for another
perl script usbfilter.pl

-- 
----------
m.vr.gr.
Gerard Klaver



From till.kamppeter@gmx.net  Tue Oct 19 22:42:47 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Tue, 19 Oct 2004 23:42:47 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410192039.00356.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net> <41752CB2.8000504@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de>
Message-ID: <41758A57.8010401@gmx.net>

Oliver Schwartz wrote:
> Hi,
> 
> 
>>http://www.linuxprinting.org/till/tmp/eps2480debug.log
>>http://www.linuxprinting.org/till/tmp/eps2580debug.log
> 
> 
>>[snapscan] sense_handler: Hardware error. (0x00, 0x04)
> 
> 
> according to my docs this means "scan module locked". You probably 
> didn't remove the transportation lock. For Benq scanners it's a small 
> switch on the bottom side of the scanner.
> 
> /Oliver
> 

Thanks, on the 2480 this was really the case. On the 2580 it was already 
open.

Now I have tried to scan with the 2480 and I was even successful 
sometimes. When it worked the problem was that there were long delays 
until the scan to start (command line) or the GUI to appear (xsane). 
There were console messages like

-----------------------------------------------------------------------
[snapscan] Scanner warming up - waiting 9 seconds.
[snapscan] Scanner warming up - waiting 33 seconds.
[snapscan] Scanner warming up - waiting 9 seconds.
[snapscan] Scanner warming up - waiting 33 seconds.
-----------------------------------------------------------------------

-----------------------------------------------------------------------
scanimage --test
-----------------------------------------------------------------------

worked with the long delays before actual scanning as described above.

-----------------------------------------------------------------------
SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm 2> eps2480_2debug.log
-----------------------------------------------------------------------

produced a correct output. 1.pnm was a scan of the full scanning area. 
Again the long delays.

-----------------------------------------------------------------------
SANE_DEBUG_SNAPSCAN=255 xsane > eps2480_3debug.log 2>&1 &
-----------------------------------------------------------------------

Successful run of xsane. Nothing than one pre-scan of the full scanning 
area was done. In another run of xsane the GUI opened but pre-scanning 
did not work, real scanning worked then and pre-scanning only bafter the 
first real scan.

On all later attempts I got a segmentation fault when the GUI started to 
open. The command line was the following:

-----------------------------------------------------------------------
SANE_DEBUG_SNAPSCAN=255 xsane > eps2480_4debug.log 2>&1 &
-----------------------------------------------------------------------

Here are the URLs of the debug log files:

http://www.linuxprinting.org/till/tmp/eps2480_2debug.log
http://www.linuxprinting.org/till/tmp/eps2480_3debug.log
http://www.linuxprinting.org/till/tmp/eps2480_4debug.log

    Till


From till.kamppeter@gmx.net  Tue Oct 19 22:47:10 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Tue, 19 Oct 2004 23:47:10 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41758A57.8010401@gmx.net>
References: <41740B7F.5040507@gmx.net> <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net> <41752CB2.8000504@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net>
Message-ID: <41758B5E.9040609@gmx.net>

Till Kamppeter wrote:
> -----------------------------------------------------------------------
> SANE_DEBUG_SNAPSCAN=255 xsane > eps2480_3debug.log 2>&1 &
> -----------------------------------------------------------------------
> 
> Successful run of xsane. Nothing than one pre-scan of the full scanning 
> area was done. In another run of xsane the GUI opened but pre-scanning 
> did not work, real scanning worked then and pre-scanning only bafter the 
> first real scan.
>

When the pre-scan failed, it said "Invalid argument".

    Till


From Oliver.Schwartz@gmx.de  Tue Oct 19 23:21:34 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Wed, 20 Oct 2004 00:21:34 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41758A57.8010401@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net>
Message-ID: <200410200021.37386.Oliver.Schwartz@gmx.de>

Hi,

> Thanks, on the 2480 this was really the case. On the 2580 it was
> already open.

It seems the 2580 behaves somewhat different, although it uses the 
same USB ID. Up to now I have no idea what's going wrong.

The log you sent for the 2580 indicates an error in 
snapscani_usb_open() which is only a small wrapper for 
sanei_usb_open(). Can you provide logs with SANE_DEBUG_SANEI_USB=255 
as well?

> Now I have tried to scan with the 2480 and I was even successful
> sometimes. When it worked the problem was that there were long
> delays until the scan to start (command line) or the GUI to appear
> (xsane). 

The delays are annoying, but it seems that all delays are requested by 
the scanner. You can try to reduce the number of retries for the 
test_unit_ready in snapscan-scsi.c, line 1008 and see if that works 
any better.

> On all later attempts I got a segmentation fault when the GUI
> started to open. The command line was the following:

There's nothing obvious in the log. Can you run xsane in gdb and 
create a stacktrace (command "bt" IIRC) after the crash?

/Oliver


From till.kamppeter@gmx.net  Wed Oct 20 00:59:05 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 01:59:05 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410200021.37386.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de>
Message-ID: <4175AA49.9040105@gmx.net>

Oliver Schwartz wrote:
> It seems the 2580 behaves somewhat different, although it uses the 
> same USB ID. Up to now I have no idea what's going wrong.
> 
> The log you sent for the 2580 indicates an error in 
> snapscani_usb_open() which is only a small wrapper for 
> sanei_usb_open(). Can you provide logs with SANE_DEBUG_SANEI_USB=255 
> as well?
>

Here we go:

http://www.linuxprinting.org/till/tmp/eps2580debug2.log

Coomand line was:

SANE_DEBUG_SANEI_USB=255 SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm 2> 
eps2580debug2.log

1.pnm had 0 bytes after running this command.

    Till


> 
>>Now I have tried to scan with the 2480 and I was even successful
>>sometimes. When it worked the problem was that there were long
>>delays until the scan to start (command line) or the GUI to appear
>>(xsane). 
> 
> 
> The delays are annoying, but it seems that all delays are requested by 
> the scanner. You can try to reduce the number of retries for the 
> test_unit_ready in snapscan-scsi.c, line 1008 and see if that works 
> any better.
> 
> 
>>On all later attempts I got a segmentation fault when the GUI
>>started to open. The command line was the following:
> 
> 
> There's nothing obvious in the log. Can you run xsane in gdb and 
> create a stacktrace (command "bt" IIRC) after the crash?
> 
> /Oliver
> 



From till.kamppeter@gmx.net  Wed Oct 20 01:00:36 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 02:00:36 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410200021.37386.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de>
Message-ID: <4175AAA4.1040805@gmx.net>

Oliver Schwartz wrote:
> 
> The delays are annoying, but it seems that all delays are requested by 
> the scanner. You can try to reduce the number of retries for the 
> test_unit_ready in snapscan-scsi.c, line 1008 and see if that works 
> any better.
>

Would this really help? The scanners are USB scanners and not SCSI scanners.

    Till



From till.kamppeter@gmx.net  Wed Oct 20 01:14:34 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 02:14:34 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410200021.37386.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de>
Message-ID: <4175ADEA.6050500@gmx.net>

Oliver Schwartz wrote:
>>On all later attempts I got a segmentation fault when the GUI
>>started to open. The command line was the following:
> 
> 
> There's nothing obvious in the log. Can you run xsane in gdb and 
> create a stacktrace (command "bt" IIRC) after the crash?
> 
> /Oliver
> 

Here is a stacktrace of a failed "scanimage --test":

--------------------------------------------------------------
[root@majax s]# gdb -c core.21805 /usr/bin/scanimage
GNU gdb 6.0-2mdk (Mandrake Linux)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-mandrake-linux-gnu"...Using host 
libthread_db library "/lib/tls/libthread_db.so.1".

Core was generated by `scanimage --test'.
Program terminated with signal 11, Segmentation fault.

warning: current_sos: Can't read pathname for load map: Input/output error

Reading symbols from /usr/lib/libsane.so.1...done.
Loaded symbols for /usr/lib/libsane.so.1
Reading symbols from /usr/lib/libusb-0.1.so.4...done.
Loaded symbols for /usr/lib/libusb-0.1.so.4
Reading symbols from /lib/libnsl.so.1...
Reading symbols from /usr/lib/debug//lib/libnsl-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /usr/lib/libjpeg.so.62...done.
Loaded symbols for /usr/lib/libjpeg.so.62
Reading symbols from /usr/lib/libieee1284.so.3...done.
Loaded symbols for /usr/lib/libieee1284.so.3
Reading symbols from /usr/lib/libgphoto2.so.2...done.
Loaded symbols for /usr/lib/libgphoto2.so.2
Reading symbols from /usr/lib/libgphoto2_port.so.0...done.
Loaded symbols for /usr/lib/libgphoto2_port.so.0
Reading symbols from /lib/libdl.so.2...
Reading symbols from /usr/lib/debug//lib/libdl-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/lib/libexif.so.9...done.
Loaded symbols for /usr/lib/libexif.so.9
Reading symbols from /lib/tls/libm.so.6...
Reading symbols from /usr/lib/debug//lib/tls/libm-2.3.3.so.debug...done.
---Type <return> to continue, or q <return> to quit---
done.
Loaded symbols for /lib/tls/libm.so.6
Reading symbols from /lib/tls/libc.so.6...
Reading symbols from /usr/lib/debug//lib/tls/libc-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/sane/libsane-hpaio.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpaio.so.1
Reading symbols from /usr/lib/libhpip.so.0...done.
Loaded symbols for /usr/lib/libhpip.so.0
Reading symbols from /lib/libnss_files.so.2...
Reading symbols from /usr/lib/debug//lib/libnss_files-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /usr/lib/sane/libsane-hpoj.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpoj.so.1
Reading symbols from /usr/lib/libptal.so.0...done.
Loaded symbols for /usr/lib/libptal.so.0
Reading symbols from /usr/lib/libhpojip.so.0...done.
Loaded symbols for /usr/lib/libhpojip.so.0
Reading symbols from /usr/lib/libsnmp.so.5...done.
Loaded symbols for /usr/lib/libsnmp.so.5
Reading symbols from /usr/lib/libcrypto.so.0.9.7...done.
Loaded symbols for /usr/lib/libcrypto.so.0.9.7
Reading symbols from /usr/lib/sane/libsane-v4l.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-v4l.so.1
Reading symbols from /usr/lib/sane/libsane-umax1220u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-umax1220u.so.1
Reading symbols from /usr/lib/sane/libsane-umax.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-umax.so.1
Reading symbols from /usr/lib/sane/libsane-u12.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-u12.so.1
Reading symbols from /usr/lib/sane/libsane-teco3.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco3.so.1
Reading symbols from /usr/lib/sane/libsane-teco2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco2.so.1
Reading symbols from /usr/lib/sane/libsane-teco1.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco1.so.1
Reading symbols from /usr/lib/sane/libsane-tamarack.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-tamarack.so.1
Reading symbols from /usr/lib/sane/libsane-sp15c.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sp15c.so.1
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/sane/libsane-snapscan.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-snapscan.so.1
Reading symbols from /usr/lib/sane/libsane-sm3600.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sm3600.so.1
Reading symbols from /usr/lib/sane/libsane-sharp.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sharp.so.1
Reading symbols from /usr/lib/sane/libsane-sceptre.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sceptre.so.1
Reading symbols from /usr/lib/sane/libsane-s9036.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-s9036.so.1
Reading symbols from /usr/lib/sane/libsane-ricoh.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ricoh.so.1
Reading symbols from /usr/lib/sane/libsane-qcam.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-qcam.so.1
Reading symbols from /usr/lib/sane/libsane-plustek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-plustek.so.1
Reading symbols from /usr/lib/sane/libsane-pie.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-pie.so.1
Reading symbols from /usr/lib/sane/libsane-nec.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-nec.so.1
Reading symbols from /usr/lib/sane/libsane-mustek_usb.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-mustek_usb.so.1
Reading symbols from /usr/lib/sane/libsane-mustek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-mustek.so.1
Reading symbols from /usr/lib/sane/libsane-microtek2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-microtek2.so.1
Reading symbols from /usr/lib/sane/libsane-microtek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-microtek.so.1
Reading symbols from /usr/lib/sane/libsane-matsushita.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-matsushita.so.1
Reading symbols from /usr/lib/sane/libsane-ma1509.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ma1509.so.1
Reading symbols from /usr/lib/sane/libsane-leo.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-leo.so.1
Reading symbols from /usr/lib/sane/libsane-ibm.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ibm.so.1
Reading symbols from /usr/lib/sane/libsane-hp5400.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp5400.so.1
Reading symbols from /usr/lib/sane/libsane-hp4200.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp4200.so.1
Reading symbols from /usr/lib/sane/libsane-hpsj5s.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpsj5s.so.1
Reading symbols from /usr/lib/sane/libsane-hp.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp.so.1
Reading symbols from /usr/lib/sane/libsane-gt68xx.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-gt68xx.so.1
Reading symbols from /usr/lib/sane/libsane-fujitsu.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-fujitsu.so.1
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/sane/libsane-epson.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-epson.so.1
Reading symbols from /usr/lib/sane/libsane-dmc.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-dmc.so.1
Reading symbols from /usr/lib/sane/libsane-coolscan2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-coolscan2.so.1
Reading symbols from /usr/lib/sane/libsane-coolscan.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-coolscan.so.1
Reading symbols from /usr/lib/sane/libsane-canon630u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-canon630u.so.1
Reading symbols from /usr/lib/sane/libsane-canon.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-canon.so.1
Reading symbols from /usr/lib/sane/libsane-bh.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-bh.so.1
Reading symbols from /usr/lib/sane/libsane-as6e.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-as6e.so.1
Reading symbols from /usr/lib/sane/libsane-artec_eplus48u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-artec_eplus48u.so.1
Reading symbols from /usr/lib/sane/libsane-artec.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-artec.so.1
Reading symbols from /usr/lib/sane/libsane-avision.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-avision.so.1
Reading symbols from /usr/lib/sane/libsane-apple.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-apple.so.1
Reading symbols from /usr/lib/sane/libsane-agfafocus.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-agfafocus.so.1
Reading symbols from /usr/lib/sane/libsane-abaton.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-abaton.so.1
Reading symbols from /usr/lib/sane/libsane-net.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-net.so.1
#0  _IO_default_xsputn (f=0xbf800654, data=0x30, n=1) at genops.c:442
442     {
(gdb) bt
#0  _IO_default_xsputn (f=0xbf800654, data=0x30, n=1) at genops.c:442
#1  0x4017dac1 in _IO_padn (fp=0xbf800654, pad=1076125664, count=1)
     at iopadn.c:68
#2  0x40163e18 in _IO_vfprintf (s=0xbf800654, format=0x4052d929 " 0x%02x",
     ap=0xbf80072c "") at vfprintf.c:1516
#3  0x4017eafb in _IO_vsprintf (
     ng=0xbf800740 " 0x?\026@\200\a\200)?@h\a\200\a",
     format=0x40245fe0 "", args=0x40245fe0 "") at iovsprintf.c:46
#4  0x4016c5db in sprintf (s=0x40245fe0 "", format=0x40245fe0 "")
     at sprintf.c:34
#5  0x4052002d in usb_debug_data () from /usr/lib/sane/libsane-snapscan.so.1
(gdb)
--------------------------------------------------------------

    Till


From till.kamppeter@gmx.net  Wed Oct 20 01:27:38 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 02:27:38 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410200021.37386.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de>
Message-ID: <4175B0FA.6030705@gmx.net>

Oliver Schwartz wrote:
> Hi,
> 
> 
>>Thanks, on the 2480 this was really the case. On the 2580 it was
>>already open.
> 
> 
> It seems the 2580 behaves somewhat different, although it uses the 
> same USB ID. Up to now I have no idea what's going wrong.
> 
> The log you sent for the 2580 indicates an error in 
> snapscani_usb_open() which is only a small wrapper for 
> sanei_usb_open(). Can you provide logs with SANE_DEBUG_SANEI_USB=255 
> as well?
> 
> 
>>Now I have tried to scan with the 2480 and I was even successful
>>sometimes. When it worked the problem was that there were long
>>delays until the scan to start (command line) or the GUI to appear
>>(xsane). 
> 
> 
> The delays are annoying, but it seems that all delays are requested by 
> the scanner. You can try to reduce the number of retries for the 
> test_unit_ready in snapscan-scsi.c, line 1008 and see if that works 
> any better.
> 
> 
>>On all later attempts I got a segmentation fault when the GUI
>>started to open. The command line was the following:
> 
> 
> There's nothing obvious in the log. Can you run xsane in gdb and 
> create a stacktrace (command "bt" IIRC) after the crash?
> 
> /Oliver
> 

Here a backtrace fron xsane with the 2480:

---------------------------------------------------------------------
[root@majax s]# gdb -c ~/core.10148 /usr/bin/xsane
GNU gdb 6.0-2mdk (Mandrake Linux)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-mandrake-linux-gnu"...
(no debugging symbols found)...Using host libthread_db library 
"/lib/tls/libthread_db.so.1".

Core was generated by `xsane'.
Program terminated with signal 11, Segmentation fault.

warning: current_sos: Can't read pathname for load map: Input/output error

Reading symbols from /usr/lib/libsane.so.1...done.
Loaded symbols for /usr/lib/libsane.so.1
Reading symbols from /usr/lib/libusb-0.1.so.4...done.
Loaded symbols for /usr/lib/libusb-0.1.so.4
Reading symbols from /lib/libnsl.so.1...
Reading symbols from /usr/lib/debug//lib/libnsl-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/tls/libm.so.6...
Reading symbols from /usr/lib/debug//lib/tls/libm-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/tls/libm.so.6
Reading symbols from /usr/lib/libjpeg.so.62...done.
Loaded symbols for /usr/lib/libjpeg.so.62
Reading symbols from /usr/lib/libieee1284.so.3...done.
Loaded symbols for /usr/lib/libieee1284.so.3
Reading symbols from /usr/lib/libgphoto2.so.2...done.
Loaded symbols for /usr/lib/libgphoto2.so.2
Reading symbols from /lib/libdl.so.2...
Reading symbols from /usr/lib/debug//lib/libdl-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libdl.so.2
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...done.
Loaded symbols for /usr/lib/libgtk-x11-2.0.so.0
Reading symbols from /usr/lib/libgdk-x11-2.0.so.0...done.
Loaded symbols for /usr/lib/libgdk-x11-2.0.so.0
Reading symbols from /usr/lib/libatk-1.0.so.0...done.
Loaded symbols for /usr/lib/libatk-1.0.so.0
Reading symbols from /usr/lib/libgdk_pixbuf-2.0.so.0...done.
Loaded symbols for /usr/lib/libgdk_pixbuf-2.0.so.0
Reading symbols from /usr/lib/libpangoxft-1.0.so.0...done.
Loaded symbols for /usr/lib/libpangoxft-1.0.so.0
Reading symbols from /usr/lib/libpangox-1.0.so.0...done.
Loaded symbols for /usr/lib/libpangox-1.0.so.0
Reading symbols from /usr/lib/libpango-1.0.so.0...done.
Loaded symbols for /usr/lib/libpango-1.0.so.0
Reading symbols from /usr/lib/libgobject-2.0.so.0...done.
Loaded symbols for /usr/lib/libgobject-2.0.so.0
Reading symbols from /usr/lib/libgmodule-2.0.so.0...done.
Loaded symbols for /usr/lib/libgmodule-2.0.so.0
Reading symbols from /usr/lib/libglib-2.0.so.0...done.
Loaded symbols for /usr/lib/libglib-2.0.so.0
Reading symbols from /usr/lib/libpng.so.3...done.
Loaded symbols for /usr/lib/libpng.so.3
Reading symbols from /usr/lib/libtiff.so.3...done.
Loaded symbols for /usr/lib/libtiff.so.3
Reading symbols from /lib/libz.so.1...done.
Loaded symbols for /lib/libz.so.1
Reading symbols from /lib/tls/libc.so.6...
Reading symbols from /usr/lib/debug//lib/tls/libc-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/libgphoto2_port.so.0...done.
Loaded symbols for /usr/lib/libgphoto2_port.so.0
Reading symbols from /usr/lib/libexif.so.9...done.
Loaded symbols for /usr/lib/libexif.so.9
Reading symbols from /usr/X11R6/lib/libX11.so.6...done.
Loaded symbols for /usr/X11R6/lib/libX11.so.6
Reading symbols from /usr/X11R6/lib/libXrandr.so.2...done.
Loaded symbols for /usr/X11R6/lib/libXrandr.so.2
Reading symbols from /usr/X11R6/lib/libXi.so.6...done.
Loaded symbols for /usr/X11R6/lib/libXi.so.6
Reading symbols from /usr/X11R6/lib/libXinerama.so.1...done.
Loaded symbols for /usr/X11R6/lib/libXinerama.so.1
Reading symbols from /usr/X11R6/lib/libXext.so.6...done.
Loaded symbols for /usr/X11R6/lib/libXext.so.6
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/X11R6/lib/libXft.so.2...done.
Loaded symbols for /usr/X11R6/lib/libXft.so.2
Reading symbols from /usr/lib/libfreetype.so.6...done.
Loaded symbols for /usr/lib/libfreetype.so.6
Reading symbols from /usr/lib/libfontconfig.so.1...done.
Loaded symbols for /usr/lib/libfontconfig.so.1
Reading symbols from /usr/X11R6/lib/libXcursor.so.1...done.
Loaded symbols for /usr/X11R6/lib/libXcursor.so.1
Reading symbols from /usr/X11R6/lib/libXrender.so.1...done.
Loaded symbols for /usr/X11R6/lib/libXrender.so.1
Reading symbols from /usr/lib/libpangoft2-1.0.so.0...done.
Loaded symbols for /usr/lib/libpangoft2-1.0.so.0
Reading symbols from /usr/lib/libexpat.so.0...done.
Loaded symbols for /usr/lib/libexpat.so.0
Reading symbols from 
/usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2...done.
Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2
Reading symbols from /lib/libnss_files.so.2...
Reading symbols from /usr/lib/debug//lib/libnss_files-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /usr/lib/gconv/ISO8859-1.so...
Reading symbols from 
/usr/lib/debug//usr/lib/gconv/ISO8859-1.so.debug...done.
done.
Loaded symbols for /usr/lib/gconv/ISO8859-1.so
Reading symbols from /usr/lib/gtk-2.0/2.4.0/engines/libgalaxy.so...done.
Loaded symbols for /usr/lib/gtk-2.0/2.4.0/engines/libgalaxy.so
Reading symbols from 
/usr/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-xpm.so...
done.
Loaded symbols for /usr/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-xpm.so
Reading symbols from /usr/lib/pango/1.4.0/modules/pango-basic-fc.so...done.
Loaded symbols for /usr/lib/pango/1.4.0/modules/pango-basic-fc.so
Reading symbols from /usr/lib/sane/libsane-hpaio.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpaio.so.1
Reading symbols from /usr/lib/libhpip.so.0...done.
Loaded symbols for /usr/lib/libhpip.so.0
Reading symbols from /usr/lib/sane/libsane-hpoj.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpoj.so.1
Reading symbols from /usr/lib/libptal.so.0...done.
Loaded symbols for /usr/lib/libptal.so.0
Reading symbols from /usr/lib/libhpojip.so.0...done.
Loaded symbols for /usr/lib/libhpojip.so.0
Reading symbols from /usr/lib/libsnmp.so.5...done.
Loaded symbols for /usr/lib/libsnmp.so.5
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/libcrypto.so.0.9.7...done.
Loaded symbols for /usr/lib/libcrypto.so.0.9.7
Reading symbols from /usr/lib/sane/libsane-v4l.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-v4l.so.1
Reading symbols from /usr/lib/sane/libsane-umax1220u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-umax1220u.so.1
Reading symbols from /usr/lib/sane/libsane-umax.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-umax.so.1
Reading symbols from /usr/lib/sane/libsane-u12.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-u12.so.1
Reading symbols from /usr/lib/sane/libsane-teco3.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco3.so.1
Reading symbols from /usr/lib/sane/libsane-teco2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco2.so.1
Reading symbols from /usr/lib/sane/libsane-teco1.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco1.so.1
Reading symbols from /usr/lib/sane/libsane-tamarack.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-tamarack.so.1
Reading symbols from /usr/lib/sane/libsane-sp15c.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sp15c.so.1
Reading symbols from /usr/lib/sane/libsane-snapscan.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-snapscan.so.1
Reading symbols from /usr/lib/sane/libsane-sm3600.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sm3600.so.1
Reading symbols from /usr/lib/sane/libsane-sharp.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sharp.so.1
Reading symbols from /usr/lib/sane/libsane-sceptre.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sceptre.so.1
Reading symbols from /usr/lib/sane/libsane-s9036.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-s9036.so.1
Reading symbols from /usr/lib/sane/libsane-ricoh.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ricoh.so.1
Reading symbols from /usr/lib/sane/libsane-qcam.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-qcam.so.1
Reading symbols from /usr/lib/sane/libsane-plustek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-plustek.so.1
Reading symbols from /usr/lib/sane/libsane-pie.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-pie.so.1
Reading symbols from /usr/lib/sane/libsane-nec.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-nec.so.1
Reading symbols from /usr/lib/sane/libsane-mustek_usb.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-mustek_usb.so.1
Reading symbols from /usr/lib/sane/libsane-mustek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-mustek.so.1
Reading symbols from /usr/lib/sane/libsane-microtek2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-microtek2.so.1
Reading symbols from /usr/lib/sane/libsane-microtek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-microtek.so.1
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/sane/libsane-matsushita.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-matsushita.so.1
Reading symbols from /usr/lib/sane/libsane-ma1509.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ma1509.so.1
Reading symbols from /usr/lib/sane/libsane-leo.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-leo.so.1
Reading symbols from /usr/lib/sane/libsane-ibm.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ibm.so.1
Reading symbols from /usr/lib/sane/libsane-hp5400.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp5400.so.1
Reading symbols from /usr/lib/sane/libsane-hp4200.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp4200.so.1
Reading symbols from /usr/lib/sane/libsane-hpsj5s.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpsj5s.so.1
Reading symbols from /usr/lib/sane/libsane-hp.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp.so.1
Reading symbols from /usr/lib/sane/libsane-gt68xx.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-gt68xx.so.1
Reading symbols from /usr/lib/sane/libsane-fujitsu.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-fujitsu.so.1
Reading symbols from /usr/lib/sane/libsane-epson.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-epson.so.1
Reading symbols from /usr/lib/sane/libsane-dmc.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-dmc.so.1
Reading symbols from /usr/lib/sane/libsane-coolscan2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-coolscan2.so.1
Reading symbols from /usr/lib/sane/libsane-coolscan.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-coolscan.so.1
Reading symbols from /usr/lib/sane/libsane-canon630u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-canon630u.so.1
Reading symbols from /usr/lib/sane/libsane-canon.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-canon.so.1
Reading symbols from /usr/lib/sane/libsane-bh.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-bh.so.1
Reading symbols from /usr/lib/sane/libsane-as6e.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-as6e.so.1
Reading symbols from /usr/lib/sane/libsane-artec_eplus48u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-artec_eplus48u.so.1
Reading symbols from /usr/lib/sane/libsane-artec.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-artec.so.1
Reading symbols from /usr/lib/sane/libsane-avision.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-avision.so.1
Reading symbols from /usr/lib/sane/libsane-apple.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-apple.so.1
Reading symbols from /usr/lib/sane/libsane-agfafocus.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-agfafocus.so.1
Reading symbols from /usr/lib/sane/libsane-abaton.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-abaton.so.1
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/sane/libsane-net.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-net.so.1
#0  0x40c9ab67 in sanei_constrain_value ()
    from /usr/lib/sane/libsane-snapscan.so.1
(gdb) bt
#0  0x40c9ab67 in sanei_constrain_value ()
    from /usr/lib/sane/libsane-snapscan.so.1
#1  0x0823a6a8 in ?? ()
#2  0x0822bc10 in ?? ()
#3  0xbfffe01c in ?? ()
#4  0x40c909a1 in sanei_debug_snapscan_call ()
    from /usr/lib/sane/libsane-snapscan.so.1
#5  0x0000001e in ?? ()
(gdb)
---------------------------------------------------------------------

    Till


From rene@exactcode.de  Wed Oct 20 07:19:41 2004
From: rene@exactcode.de (=?ISO-8859-1?Q?Ren=E9_Rebe?=)
Date: Wed, 20 Oct 2004 08:19:41 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
In-Reply-To: <20041017181209.GH12072@meier-geinitz.de>
References: <20041017181209.GH12072@meier-geinitz.de>
Message-ID: <4176037D.3050307@exactcode.de>

Hi Henning,

Henning Meier-Geinitz wrote:

> Feature freeze for sane-backends 1.0.15 is now active. That means,
> that now new backend or new features for existing backends should be
> committed to CVS. Bug fixes, documentation and translation updates are
> ok.
> 
> Timetable:
> 2004-10-31 Code freeze (snapshot)
> 2004-11-07 Release

Sorry for always beeing late due to workload here ... :-(

I have some more avision updates in the queue, mostly fixes and cleanups 
- but also the button readout code, which would be a new feature ... 
Should I leave it out and seperate the rest of the code, or are those 
few button code lines tiny enought for a "just commit it"? ;-)

I guess committing the normal code changes today is ok?

Sincerely,

-- 
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
             +49 (0)30  255 897 45


From Oliver.Schwartz@gmx.de  Wed Oct 20 18:46:06 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Wed, 20 Oct 2004 19:46:06 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <4175AAA4.1040805@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <4175AAA4.1040805@gmx.net>
Message-ID: <200410201946.07792.Oliver.Schwartz@gmx.de>

On Wednesday 20 October 2004 02.00, Till Kamppeter wrote:
> Oliver Schwartz wrote:
> > The delays are annoying, but it seems that all delays are
> > requested by the scanner. You can try to reduce the number of
> > retries for the test_unit_ready in snapscan-scsi.c, line 1008 and
> > see if that works any better.
>
> Would this really help? The scanners are USB scanners and not SCSI
> scanners.

Yes - some of routines in snapscan-scsi.c are used for usb as well. 

/Oliver


From henning@meier-geinitz.de  Wed Oct 20 18:44:22 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 20 Oct 2004 19:44:22 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
In-Reply-To: <4176037D.3050307@exactcode.de>
References: <20041017181209.GH12072@meier-geinitz.de> <4176037D.3050307@exactcode.de>
Message-ID: <20041020174422.GA7538@meier-geinitz.de>

Hi,

On Wed, Oct 20, 2004 at 08:19:41AM +0200, René Rebe wrote:
> I have some more avision updates in the queue, mostly fixes and cleanups 
> - but also the button readout code, which would be a new feature ... 
> Should I leave it out and seperate the rest of the code, or are those 
> few button code lines tiny enought for a "just commit it"? ;-)

If it's really only a few lines and yiu are sure that these lines
don't break anything I guess it's ok.

Bye,
  Henning


From Oliver.Schwartz@gmx.de  Wed Oct 20 19:51:52 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Wed, 20 Oct 2004 20:51:52 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <4175AA49.9040105@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <4175AA49.9040105@gmx.net>
Message-ID: <200410202051.55687.Oliver.Schwartz@gmx.de>

Hi,

> http://www.linuxprinting.org/till/tmp/eps2580debug2.log
>
> Coomand line was:
>
> SANE_DEBUG_SANEI_USB=255 SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm
> 2> eps2580debug2.log

> [snapscan] snapscani_usb_open(libusb:001:037)
> [sanei_usb] sanei_usb_open: trying to open device `libusb:001:037'
> USB error: failed to open /proc/bus/usb/001/037: No such file or
> directory 
> [sanei_usb] sanei_usb_open: can't open device `libusb:001:037': No
> such file or directory 

hm - it seems the USB device disappeared during firmware upload. That 
certainly shouldn't happen, but there's little that the backend can 
do about it.

I'm not sure if esfw41.bin is the correct file for the 2580 at all. 
Maybe it needs a different firmware file. Is there another one 
installed with the windows driver?

/Oliver


From Oliver.Schwartz@gmx.de  Wed Oct 20 19:53:53 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Wed, 20 Oct 2004 20:53:53 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <4175ADEA.6050500@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <4175ADEA.6050500@gmx.net>
Message-ID: <200410202053.56532.Oliver.Schwartz@gmx.de>

Hi,

the backtraces are quite obscure. Is there any chance that you have 
two versions of SANE installed on your system (e.g. one 
in /usr/lib/sane, another one in /usr/local/lib/sane)?

/Oliver


From till.kamppeter@gmx.net  Wed Oct 20 21:01:24 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 22:01:24 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410202053.56532.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <4175ADEA.6050500@gmx.net> <200410202053.56532.Oliver.Schwartz@gmx.de>
Message-ID: <4176C414.10009@gmx.net>

Impossible, I have installed SANE always by RPM, for a new version I 
have rebuilt the RPM on the compiling machine and then updated the RPM 
on my testing machine.

    Till


Oliver Schwartz wrote:
> Hi,
> 
> the backtraces are quite obscure. Is there any chance that you have 
> two versions of SANE installed on your system (e.g. one 
> in /usr/lib/sane, another one in /usr/local/lib/sane)?
> 
> /Oliver
> 



From till.kamppeter@gmx.net  Wed Oct 20 21:04:09 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 22:04:09 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410202051.55687.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <4175AA49.9040105@gmx.net> <200410202051.55687.Oliver.Schwartz@gmx.de>
Message-ID: <4176C4B9.40708@gmx.net>

There was only this one .bin file in the Windows driver package. The 
whole Windows driver package is exactly the same for both models.

When I llok at the scanners itself, the base parts are identical (only 
exception the "2480" and "2580" printed on them. Only the lids are 
different, the 2480 with only a transparency light and the 2580 with 
automatic film feeder (for 35-mm film).

    Till


Oliver Schwartz wrote:
> Hi,
> 
> 
>>http://www.linuxprinting.org/till/tmp/eps2580debug2.log
>>
>>Coomand line was:
>>
>>SANE_DEBUG_SANEI_USB=255 SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm
>>2> eps2580debug2.log
> 
> 
>>[snapscan] snapscani_usb_open(libusb:001:037)
>>[sanei_usb] sanei_usb_open: trying to open device `libusb:001:037'
>>USB error: failed to open /proc/bus/usb/001/037: No such file or
>>directory 
>>[sanei_usb] sanei_usb_open: can't open device `libusb:001:037': No
>>such file or directory 
> 
> 
> hm - it seems the USB device disappeared during firmware upload. That 
> certainly shouldn't happen, but there's little that the backend can 
> do about it.
> 
> I'm not sure if esfw41.bin is the correct file for the 2580 at all. 
> Maybe it needs a different firmware file. Is there another one 
> installed with the windows driver?
> 
> /Oliver
> 



From henning@meier-geinitz.de  Wed Oct 20 20:43:26 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 20 Oct 2004 21:43:26 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410200021.37386.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de>
Message-ID: <20041020194326.GF7538@meier-geinitz.de>

Hi,

On Wed, Oct 20, 2004 at 12:21:34AM +0200, Oliver Schwartz wrote:
> There's nothing obvious in the log. Can you run xsane in gdb and 
> create a stacktrace (command "bt" IIRC) after the crash?

Why does the frontend want to set the gray gamma table to (nil)?

[snapscan] sane_snapscan_control_option (0x823a6b0, 24, 1, (nil), 0xbfffdffc)

Maybe I don't understand something here but that looks strange.

Bye,
  Henning


From boldra@tiscali.it  Thu Oct 21 08:32:31 2004
From: boldra@tiscali.it (Enrico Boldrini)
Date: Thu, 21 Oct 2004 09:32:31 +0200
Subject: [sane-devel] homepage for "artiscan 9600" scanner
Message-ID: <1098343951.968.10.camel@vicious>

>I the full name of that scanner "Tamarack Artiscan 9600" or "Tamarack
>Artiscan 9600 pro 36"?
>
>Bye,
>  Henning

Theese are two models of the scanner. The scanner we'll try to support
first will be Tamarack Artiscan 9600 pro 36.

I use this message also to inform that:
/!\ The project is moved to http://www.autistici.org/tamarhack /1\

Bye, Enrico



From Oliver.Schwartz@gmx.de  Thu Oct 21 23:59:47 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Fri, 22 Oct 2004 00:59:47 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <20041020194326.GF7538@meier-geinitz.de>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <20041020194326.GF7538@meier-geinitz.de>
Message-ID: <200410220059.49524.Oliver.Schwartz@gmx.de>

Hi,

> Why does the frontend want to set the gray gamma table to (nil)?
>
> [snapscan] sane_snapscan_control_option (0x823a6b0, 24, 1, (nil),
> 0xbfffdffc)
>
> Maybe I don't understand something here but that looks strange.

This seems to cause the crash (which is not that surprising). For some 
reason the frontend passes an invalid pointer.

Can you try another frontend (e.g. xscanimage)? It may also help to 
delete any xsane preferences (stored in ~/.sane/xsane IIRC).

/Oliver


From till.kamppeter@gmx.net  Fri Oct 22 17:03:34 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Fri, 22 Oct 2004 18:03:34 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410220059.49524.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <20041020194326.GF7538@meier-geinitz.de> <200410220059.49524.Oliver.Schwartz@gmx.de>
Message-ID: <41792F56.6090307@gmx.net>

Oliver Schwartz wrote:
> Hi,
> 
> 
>>Why does the frontend want to set the gray gamma table to (nil)?
>>
>>[snapscan] sane_snapscan_control_option (0x823a6b0, 24, 1, (nil),
>>0xbfffdffc)
>>
>>Maybe I don't understand something here but that looks strange.
> 
> 
> This seems to cause the crash (which is not that surprising). For some 
> reason the frontend passes an invalid pointer.
> 

I have tried now with xscanimage and have interesting results:

The 2480 and 2580 consist of a lower part with the glass and scanning 
head and a lid with the transparency unit. The lower parts of both are 
absolutely identical, including the USB vendor/product IDs. The 
difference between the 2480 and 2580 is made up by the lids. The lid of 
the 2480 has a simple light which is turned on in transparency mode. You 
insert the film or slides in a special frame and put this on the glass, 
so film or slide are placed under the light and parallel to the 
scanner's borders. The 2580 has an automatic film feeder. You remove the 
white background from the inner side of the lid, close the lid and open 
a little door on the upper side of the lid. There you insert a piece of 
35-mm film and the scanner pulls it in automatically. For slides there 
is a frame for the scanner glass again, but a different one.

In principle the scanners work with SANE and the "snapscan" driver, but 
there are some problems:

- You need the scanner's firmware, as for all scanners used with the 
"snapscan" driver.

- There are long delays between starting the scanner software and the 
GUI opening or the scan beginning. Messages like

[snapscan] Scanner warming up - waiting 33 seconds

appear on the console from where the scanning frontend was started.

- The biggest problem is that the USB device address (like 
libusb:001:015) changes when the firmware is uploaded, it seems that 
after the upload the scanner is disconnected and then reconnected and so 
it gets a new ID.

This means that the very first start of a frontend (after 
connecting/turning on the scanner) lets the GUI open, but trying to 
preview of to scan gives "Invalid argument". Comparing the output of 
"lsusb" reveals that the USB device address changed at the moment where 
the firmware upload finished. On subsequent runs of scanning frontends 
the firmware is not uploaded again and so the address does not change. 
So one can scan when one closes the frontend and opens it again. Perhaps 
one should do modifications on the "snapscan" backend to take the 
reconnection/address change into account.

- The lid of the 2580 is not compatible with SANE. If the lid is in use 
with any of the two lower parts (2480 and 2580) the preview does not 
work. The head moves shortly and the preview is a stripy dirty white. 
Normal scanning does work at least in flatbed mode. Switching to the 
transparency unit makes the frontend freezing.

Both lower parts work without problems when the lid of the 2480 or no 
lid at all is connected. With the lid of the 2480 one can switch to the 
transparency unit and scan transparent documets correctly. Without lid 
the button for the transparency unit simply does not appear.

    Till


> Can you try another frontend (e.g. xscanimage)? It may also help to 
> delete any xsane preferences (stored in ~/.sane/xsane IIRC).
> 
> /Oliver
> 



From till.kamppeter@gmx.net  Fri Oct 22 19:41:29 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Fri, 22 Oct 2004 20:41:29 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41792F56.6090307@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <20041020194326.GF7538@meier-geinitz.de> <200410220059.49524.Oliver.Schwartz@gmx.de> <41792F56.6090307@gmx.net>
Message-ID: <41795459.8090000@gmx.net>

Here are some more debug logs, all for the 2580 (lower part with film 
feeder lid):

http://www.linuxprinting.org/till/tmp/eps2580debug3.log
http://www.linuxprinting.org/till/tmp/eps2580debug4.log
http://www.linuxprinting.org/till/tmp/eps2580debug5.log

To get these logs the scanner was connected and turned on and then the 
following command lines executed:

------------------------------------------------------------------------
[root@majax g]# SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm 
2>eps2580debug3.log
[root@majax g]# ll 1.pnm
-rw-r--r--  1 root root 0 Oct 22 13:50 1.pnm
[root@majax g]# lsusb
Bus 001 Device 020: ID 04b8:0121 Seiko Epson Corp.
Bus 001 Device 003: ID 0451:2077 Texas Instruments, Inc. TUSB2077 Hub
Bus 001 Device 002: ID 04f9:0016 Brother Industries, Ltd
Bus 001 Device 001: ID 0000:0000
[root@majax g]# SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm 
2>eps2580debug4.log
[root@majax g]# ll 1.pnm
-rw-r--r--  1 root root 26849629 Oct 22 13:58 1.pnm
[root@majax g]# SANE_DEBUG_SNAPSCAN=255 xscanimage >eps2580debug5.log 2>&1
------------------------------------------------------------------------

The scanimage commands are non-interactive and only on the second the 
scan succeeded (file contains the correct image). The first did not 
succeed because there the firmware was uploaded and the scanner 
reconnected with a new address as told already in the previous posting. 
The third command was an interactive xscanimage session. The following 
steps were done:

1. Normal preview, failed as described in the previous posting: fast 
sweep of scan head, no correct image.

2. Scan of a very small part of the image area. Succeeded, file contains 
expected image.

3. Preview with TPU, took VERY long until it started, head sweep sounded 
correct, but color components seem to be misaligned.

4. Scan with TPU, took long but seems correct.

5. Back to normal flatbed mode: Preview scan still broken.

6. Normal scan of full area at 100 dpi absolutely correct.]

    Till



Till Kamppeter wrote:
> Oliver Schwartz wrote:
> 
>> Hi,
>>
>>
>>> Why does the frontend want to set the gray gamma table to (nil)?
>>>
>>> [snapscan] sane_snapscan_control_option (0x823a6b0, 24, 1, (nil),
>>> 0xbfffdffc)
>>>
>>> Maybe I don't understand something here but that looks strange.
>>
>>
>>
>> This seems to cause the crash (which is not that surprising). For some 
>> reason the frontend passes an invalid pointer.
>>
> 
> I have tried now with xscanimage and have interesting results:
> 
> The 2480 and 2580 consist of a lower part with the glass and scanning 
> head and a lid with the transparency unit. The lower parts of both are 
> absolutely identical, including the USB vendor/product IDs. The 
> difference between the 2480 and 2580 is made up by the lids. The lid of 
> the 2480 has a simple light which is turned on in transparency mode. You 
> insert the film or slides in a special frame and put this on the glass, 
> so film or slide are placed under the light and parallel to the 
> scanner's borders. The 2580 has an automatic film feeder. You remove the 
> white background from the inner side of the lid, close the lid and open 
> a little door on the upper side of the lid. There you insert a piece of 
> 35-mm film and the scanner pulls it in automatically. For slides there 
> is a frame for the scanner glass again, but a different one.
> 
> In principle the scanners work with SANE and the "snapscan" driver, but 
> there are some problems:
> 
> - You need the scanner's firmware, as for all scanners used with the 
> "snapscan" driver.
> 
> - There are long delays between starting the scanner software and the 
> GUI opening or the scan beginning. Messages like
> 
> [snapscan] Scanner warming up - waiting 33 seconds
> 
> appear on the console from where the scanning frontend was started.
> 
> - The biggest problem is that the USB device address (like 
> libusb:001:015) changes when the firmware is uploaded, it seems that 
> after the upload the scanner is disconnected and then reconnected and so 
> it gets a new ID.
> 
> This means that the very first start of a frontend (after 
> connecting/turning on the scanner) lets the GUI open, but trying to 
> preview of to scan gives "Invalid argument". Comparing the output of 
> "lsusb" reveals that the USB device address changed at the moment where 
> the firmware upload finished. On subsequent runs of scanning frontends 
> the firmware is not uploaded again and so the address does not change. 
> So one can scan when one closes the frontend and opens it again. Perhaps 
> one should do modifications on the "snapscan" backend to take the 
> reconnection/address change into account.
> 
> - The lid of the 2580 is not compatible with SANE. If the lid is in use 
> with any of the two lower parts (2480 and 2580) the preview does not 
> work. The head moves shortly and the preview is a stripy dirty white. 
> Normal scanning does work at least in flatbed mode. Switching to the 
> transparency unit makes the frontend freezing.
> 
> Both lower parts work without problems when the lid of the 2480 or no 
> lid at all is connected. With the lid of the 2480 one can switch to the 
> transparency unit and scan transparent documets correctly. Without lid 
> the button for the transparency unit simply does not appear.
> 
>    Till
> 
> 
>> Can you try another frontend (e.g. xscanimage)? It may also help to 
>> delete any xsane preferences (stored in ~/.sane/xsane IIRC).
>>
>> /Oliver
>>
> 
> 



From haantc502@sneakemail.com  Fri Oct 22 20:26:14 2004
From: haantc502@sneakemail.com (Brad Johnson)
Date: 22 Oct 2004 19:26:14 -0000
Subject: [sane-devel] Vertical Comb effect on Epson 2580 scan at 2400 dpi
Message-ID: <11334-94068@sneakemail.com>

Hello,



I have an Epson Perfection 2580 Photo and when scanning at 50-1200 dpi I get good scans, but when scanning at 2400 dpi I get a vertical comb effect. Every other line is shifted 4 pixels down.



So when I'm expecting a set of pixels like this:

.....

.....

OOOOO

OOOOO

OOOOO

OOOOO



This is what I get:

.....

O.O.O

O.O.O

O.O.O

O.O.O

OOOOO



I am running sane built from today's CVS.



I know support for this scanner is still being worked on, but any ideas?



thanks,

Brad Johnson


From jb@jblache.org  Fri Oct 22 21:40:47 2004
From: jb@jblache.org (Julien BLACHE)
Date: Fri, 22 Oct 2004 22:40:47 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for
 testing
In-Reply-To: <41792F56.6090307@gmx.net> (Till Kamppeter's message of "Fri,
 22 Oct 2004 18:03:34 +0200")
References: <41740B7F.5040507@gmx.net>
 <200410200021.37386.Oliver.Schwartz@gmx.de>
 <20041020194326.GF7538@meier-geinitz.de>
 <200410220059.49524.Oliver.Schwartz@gmx.de> <41792F56.6090307@gmx.net>
Message-ID: <87vfd2jxkg.fsf@frigate.technologeek.org>

Till Kamppeter <till.kamppeter@gmx.net> wrote:

> - The biggest problem is that the USB device address (like
> libusb:001:015) changes when the firmware is uploaded, it seems that
> after the upload the scanner is disconnected and then reconnected and
> so it gets a new ID.

Doesn't happen here with a 2480.

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb@jblache.org>                                  GPG KeyID 0xF5D65169


From jb@jblache.org  Fri Oct 22 21:40:20 2004
From: jb@jblache.org (Julien BLACHE)
Date: Fri, 22 Oct 2004 22:40:20 +0200
Subject: [sane-devel] Vertical Comb effect on Epson 2580 scan at 2400
 dpi
In-Reply-To: <11334-94068@sneakemail.com> (Brad Johnson's message of "22 Oct
 2004 19:26:14 -0000")
References: <11334-94068@sneakemail.com>
Message-ID: <87zn2ejxl7.fsf@frigate.technologeek.org>

"Brad Johnson" <haantc502@sneakemail.com> wrote:

Hi,

> I have an Epson Perfection 2580 Photo and when scanning at 50-1200 dpi
> I get good scans, but when scanning at 2400 dpi I get a vertical comb
> effect. Every other line is shifted 4 pixels down.

This is a known issue and is due to the scanner design.

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb@jblache.org>                                  GPG KeyID 0xF5D65169


From Oliver.Schwartz@gmx.de  Fri Oct 22 21:41:30 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Fri, 22 Oct 2004 22:41:30 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41792F56.6090307@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410220059.49524.Oliver.Schwartz@gmx.de> <41792F56.6090307@gmx.net>
Message-ID: <200410222241.32972.Oliver.Schwartz@gmx.de>

Hi,

> - There are long delays between starting the scanner software and
> the GUI opening or the scan beginning. Messages like
>
> [snapscan] Scanner warming up - waiting 33 seconds
>
> appear on the console from where the scanning frontend was started.

Did you try reducing the retry counter yet?

> - The biggest problem is that the USB device address (like
> libusb:001:015) changes when the firmware is uploaded, it seems
> that after the upload the scanner is disconnected and then
> reconnected and so it gets a new ID.
>
> This means that the very first start of a frontend (after
> connecting/turning on the scanner) lets the GUI open, but trying to
> preview of to scan gives "Invalid argument". Comparing the output
> of "lsusb" reveals that the USB device address changed at the
> moment where the firmware upload finished. On subsequent runs of
> scanning frontends the firmware is not uploaded again and so the
> address does not change. So one can scan when one closes the
> frontend and opens it again. Perhaps one should do modifications on
> the "snapscan" backend to take the reconnection/address change into
> account.

It's probably easier to set up a hotplug script that downloads the 
firmware once the scanner is connected. In principle this is possible 
using a modified "acerfirm" from the snapscan website. The biggest 
problem is that acerfirm doesn't work with libusb yet.

It would require a lot of tweakings and workarounds to handle changing 
device files within the SANE architecture framework.

> - The lid of the 2580 is not compatible with SANE. If the lid is in
> use with any of the two lower parts (2480 and 2580) the preview
> does not work. The head moves shortly and the preview is a stripy
> dirty white. Normal scanning does work at least in flatbed mode.
> Switching to the transparency unit makes the frontend freezing.
>
> Both lower parts work without problems when the lid of the 2480 or
> no lid at all is connected. With the lid of the 2480 one can switch
> to the transparency unit and scan transparent documets correctly.
> Without lid the button for the transparency unit simply does not
> appear.

If there are fundamental differences in the protocol it would help to 
get usb trace from the windows driver.

/Oliver


From Oliver.Schwartz@gmx.de  Fri Oct 22 21:50:18 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Fri, 22 Oct 2004 22:50:18 +0200
Subject: [sane-devel] Vertical Comb effect on Epson 2580 scan at 2400 dpi
In-Reply-To: <11334-94068@sneakemail.com>
References: <11334-94068@sneakemail.com>
Message-ID: <200410222250.19605.Oliver.Schwartz@gmx.de>

Hi,

> I have an Epson Perfection 2580 Photo and when scanning at 50-1200
> dpi I get good scans, but when scanning at 2400 dpi I get a
> vertical comb effect. Every other line is shifted 4 pixels down.
>
> I know support for this scanner is still being worked on, but any
> ideas?

It's a known issue for both the 2480 and the 2580. See 
https://alioth.debian.org/tracker/index.php?func=detail&aid=300756&group_id=30186&atid=410366 

To be honest I've no idea how to fix it. A trace of the USB 
communication in windows may be helpful.

/Oliver


From Oliver.Schwartz@gmx.de  Fri Oct 22 21:51:30 2004
From: Oliver.Schwartz@gmx.de (Oliver Schwartz)
Date: Fri, 22 Oct 2004 22:51:30 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <87vfd2jxkg.fsf@frigate.technologeek.org>
References: <41740B7F.5040507@gmx.net> <41792F56.6090307@gmx.net> <87vfd2jxkg.fsf@frigate.technologeek.org>
Message-ID: <200410222251.31537.Oliver.Schwartz@gmx.de>

Hi,

> > - The biggest problem is that the USB device address (like
> > libusb:001:015) changes when the firmware is uploaded, it seems
> > that after the upload the scanner is disconnected and then
> > reconnected and so it gets a new ID.
>
> Doesn't happen here with a 2480.

This may depend on the setup (kernel version, hotplug agent used).

/Oliver


From rene@exactcode.de  Thu Oct 21 11:45:37 2004
From: rene@exactcode.de (=?ISO-8859-1?Q?Ren=E9_Rebe?=)
Date: Thu, 21 Oct 2004 12:45:37 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
In-Reply-To: <20041020174422.GA7538@meier-geinitz.de>
References: <20041017181209.GH12072@meier-geinitz.de> <4176037D.3050307@exactcode.de> <20041020174422.GA7538@meier-geinitz.de>
Message-ID: <41779351.1070706@exactcode.de>

Hi,

Henning Meier-Geinitz wrote:
> Hi,
> 
> On Wed, Oct 20, 2004 at 08:19:41AM +0200, René Rebe wrote:
> 
>>I have some more avision updates in the queue, mostly fixes and cleanups 
>>- but also the button readout code, which would be a new feature ... 
>>Should I leave it out and seperate the rest of the code, or are those 
>>few button code lines tiny enought for a "just commit it"? ;-)
> 
> 
> If it's really only a few lines and yiu are sure that these lines
> don't break anything I guess it's ok.

Hm. Ok, then I commit the remaining normal fixes that have queued up 
(those are already big enough) and post a diff with the button stuff 
here, for review (I do not urgently demand to get it into the next 
release, since it is not in wide use yet and I use my svn tree for my 
private stuf anyway).

Sincerely,

-- 
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
             +49 (0)30  255 897 45


From eppesuig@users.sourceforge.net  Sat Oct 23 13:03:57 2004
From: eppesuig@users.sourceforge.net (Giuseppe Sacco)
Date: Sat, 23 Oct 2004 14:03:57 +0200
Subject: [sane-devel] some english words
Message-ID: <1098533036.2770.313.camel@localhost>

Hi all,
I am updating the italian translation for sane-backends and I have a
questiong about radiance and brightness: are these synonims in english?
If they are then I will translate both with "luminosit=E0", otherwise I
have to understand what is the difference between them.

The radiance word is used in saneopts.h microtek2=20
The brightness word is used in saneopts.h epson.c gt68xx matsushita
mustek pnm

Thanks,
Giuseppe



From martin@mkcollins.org  Sat Oct 23 17:43:15 2004
From: martin@mkcollins.org (Martin Collins)
Date: Sat, 23 Oct 2004 17:43:15 +0100
Subject: [sane-devel] some english words
In-Reply-To: <1098533036.2770.313.camel@localhost>
References: <1098533036.2770.313.camel@localhost>
Message-ID: <20041023174315.45fbf2bb.martin@mkcollins.org>

On Sat, 23 Oct 2004 14:03:57 +0200
Giuseppe Sacco <eppesuig@users.sourceforge.net> wrote:

> I am updating the italian translation for sane-backends and I have a
> questiong about radiance and brightness: are these synonims in
> english? If they are then I will translate both with "luminosit=E0",
> otherwise I have to understand what is the difference between them.

Radiance implies the emission of light, brightness could also apply
to reflection.

Depending on context radiance might refer to absolute intensity (i.e
the number of photons emitted) and brightness to apparent intensity
(i.e. the number of photons detected).

Brightness is one coordinate of the HSB colourspace (black-white) or
the mean of R,G and B values.
Strictly speaking it is not a synonym of radiance which is a measure
of the intensity of a light beam.
Luminosity is the power output of a light emitter.

However, in this context I doubt we are dealing with the strict meaning
of radiance so it is fairly safe to assume that brightness, radiance
and luminosity are all referring to the same kind of thing.

Martin


From mattias.ellert@tsl.uu.se  Sat Oct 23 17:57:07 2004
From: mattias.ellert@tsl.uu.se (Mattias Ellert)
Date: Sat, 23 Oct 2004 18:57:07 +0200
Subject: [sane-devel] some english words
In-Reply-To: <20041023174315.45fbf2bb.martin@mkcollins.org>
References: <1098533036.2770.313.camel@localhost> <20041023174315.45fbf2bb.martin@mkcollins.org>
Message-ID: <92B82794-2514-11D9-95B1-0003930D2AFC@tsl.uu.se>

2004-10-23 kl. 18.43 skrev Martin Collins:

> However, in this context I doubt we are dealing with the strict meaning
> of radiance so it is fairly safe to assume that brightness, radiance
> and luminosity are all referring to the same kind of thing.
>
> Martin

If they really, within the sane-backends, mean the same thing, then I 
would strongly suggest to drop one of them and only use a singel term. 
That would be both less confusing for the users and easier to maintain 
for the developers.

	Mattias



From henning@meier-geinitz.de  Sat Oct 23 18:18:54 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 23 Oct 2004 19:18:54 +0200
Subject: [sane-devel] some english words
In-Reply-To: <92B82794-2514-11D9-95B1-0003930D2AFC@tsl.uu.se>
References: <1098533036.2770.313.camel@localhost> <20041023174315.45fbf2bb.martin@mkcollins.org> <92B82794-2514-11D9-95B1-0003930D2AFC@tsl.uu.se>
Message-ID: <20041023171854.GF13573@meier-geinitz.de>

Hi,

On Sat, Oct 23, 2004 at 06:57:07PM +0200, Mattias Ellert wrote:
> If they really, within the sane-backends, mean the same thing, then I 
> would strongly suggest to drop one of them and only use a singel term. 
> That would be both less confusing for the users and easier to maintain 
> for the developers.

saneopts.h already contains a brightness option so this should be used
if radiance is really the same:
#define SANE_NAME_BRIGHTNESS            "brightness"
#define SANE_TITLE_BRIGHTNESS           SANE_I18N("Brightness")
#define SANE_DESC_BRIGHTNESS \
SANE_I18N("Controls the brightness of the acquired image.")

Bye,
  Henning


From mattias.ellert@tsl.uu.se  Sat Oct 23 19:11:15 2004
From: mattias.ellert@tsl.uu.se (Mattias Ellert)
Date: Sat, 23 Oct 2004 20:11:15 +0200
Subject: [sane-devel] some english words
In-Reply-To: <20041023171854.GF13573@meier-geinitz.de>
References: <1098533036.2770.313.camel@localhost> <20041023174315.45fbf2bb.martin@mkcollins.org> <92B82794-2514-11D9-95B1-0003930D2AFC@tsl.uu.se> <20041023171854.GF13573@meier-geinitz.de>
Message-ID: <EDD84FE9-251E-11D9-95B1-0003930D2AFC@tsl.uu.se>

2004-10-23 kl. 19.18 skrev Henning Meier-Geinitz:

> saneopts.h already contains a brightness option so this should be used
> if radiance is really the same:
> #define SANE_NAME_BRIGHTNESS            "brightness"
> #define SANE_TITLE_BRIGHTNESS           SANE_I18N("Brightness")
> #define SANE_DESC_BRIGHTNESS \
> SANE_I18N("Controls the brightness of the acquired image.")

Yes, but it does not contain brightness per channel (as mustek.c):

   s->opt[OPT_BRIGHTNESS_R].name = "brightness-r";
   s->opt[OPT_BRIGHTNESS_R].title = SANE_I18N ("Red brightness");
   s->opt[OPT_BRIGHTNESS_R].desc = SANE_I18N ("Controls the brightness 
of "
                                              "the red channel of the "
                                              "acquired image.");

While we're at it...

What is the difference between blacklevel and shadow resp. whitelevel 
and highlight

For the "one setting for all channels" option the descriptions are the 
same:

#define SANE_DESC_BLACK_LEVEL \
SANE_I18N("Selects what radiance level should be considered \"black\".")

#define SANE_DESC_SHADOW \
SANE_I18N("Selects what radiance level should be considered \"black\".")

#define SANE_DESC_WHITE_LEVEL \
SANE_I18N("Selects what radiance level should be considered \"white\".")

#define SANE_DESC_HIGHLIGHT \
SANE_I18N("Selects what radiance level should be considered \"white\".")

When the channels are split the descriptions differ:

/* SANE_DESC_BLACK_LEVEL_R does not exist */

#define SANE_DESC_SHADOW_R \
SANE_I18N("Selects what red radiance level should be considered 
\"black\".")

#define SANE_DESC_WHITE_LEVEL_R \
SANE_I18N("Selects what red radiance level should be considered 
\"white\".")

#define SANE_DESC_HIGHLIGHT_R \
SANE_I18N("Selects what red radiance level should be considered \"full 
red\".")

The description for SANE_DESC_WHITE_LEVEL_R doesn't make sense to me, 
since 100% red would mean "full red" and not "white". But then it again 
would be the same as the SANE_DESC_HIGHLIGHT_R. But I might have the 
wrong conception here...

If there is some difference between the meanings of the options that 
difference should be made clear in the option description. If there is 
no difference, then one of the option titles should be dropped to avoid 
confusion and ease maintainance.

	Mattias



From martin@mkcollins.org  Sat Oct 23 22:36:35 2004
From: martin@mkcollins.org (Martin Collins)
Date: Sat, 23 Oct 2004 22:36:35 +0100
Subject: [sane-devel] some english words
In-Reply-To: <EDD84FE9-251E-11D9-95B1-0003930D2AFC@tsl.uu.se>
References: <1098533036.2770.313.camel@localhost>
 <20041023174315.45fbf2bb.martin@mkcollins.org>
 <92B82794-2514-11D9-95B1-0003930D2AFC@tsl.uu.se>
 <20041023171854.GF13573@meier-geinitz.de>
 <EDD84FE9-251E-11D9-95B1-0003930D2AFC@tsl.uu.se>
Message-ID: <20041023223635.696e4f27.martin@mkcollins.org>

On Sat, 23 Oct 2004 20:11:15 +0200
Mattias Ellert <mattias.ellert@tsl.uu.se> wrote:

> What is the difference between blacklevel and shadow resp.
> whitelevel and highlight

To me they are the same.
 
> #define SANE_DESC_BLACK_LEVEL \
> SANE_I18N("Selects what radiance level should be considered
> \"black\".")

Brightness would be much better than radiance here.

> The description for SANE_DESC_WHITE_LEVEL_R doesn't make sense to
> me, since 100% red would mean "full red" and not "white". But then
> it again would be the same as the SANE_DESC_HIGHLIGHT_R. But I might
> have the wrong conception here...

I agree. Maybe zero-red and full-red would be clearer.

Martin


From pmacv@telefonica.net  Sun Oct 24 22:05:49 2004
From: pmacv@telefonica.net (Pedro M (Morphix User))
Date: Sun, 24 Oct 2004 21:05:49 +0000
Subject: [sane-devel] Common multifunctional API
In-Reply-To: <200410171311.28511.Oliver.Schwartz@gmx.de>
References: <415BD75B.1060103@bigpond.net.au> <200410062029.50935.Oliver.Schwartz@gmx.de> <Pine.LNX.4.53.0410170707470.1932@localhost.localdomain> <200410171311.28511.Oliver.Schwartz@gmx.de>
Message-ID: <417C192D.6010106@telefonica.net>

I suggest create a common API for XFree86, that can use CUPS and SANE 
for multifunctional users.

It could be a Ncurses GUI that would execute Sane or CUPS .

Regards.


From henning@meier-geinitz.de  Sun Oct 24 20:17:17 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 24 Oct 2004 21:17:17 +0200
Subject: [sane-devel] Common multifunctional API
In-Reply-To: <417C192D.6010106@telefonica.net>
References: <415BD75B.1060103@bigpond.net.au> <200410062029.50935.Oliver.Schwartz@gmx.de> <Pine.LNX.4.53.0410170707470.1932@localhost.localdomain> <200410171311.28511.Oliver.Schwartz@gmx.de> <417C192D.6010106@telefonica.net>
Message-ID: <20041024191717.GH3901@meier-geinitz.de>

Hi,

On Sun, Oct 24, 2004 at 09:05:49PM +0000, Pedro M (Morphix User) wrote:
> I suggest create a common API for XFree86, that can use CUPS and SANE 
> for multifunctional users.
> 
> It could be a Ncurses GUI that would execute Sane or CUPS .

Could you explain in more detail about what you are talking?
Is it somehow related to the Epson 2580 (you are posting in the Epson
2580 thread)?

Why should an API for printers and scanners be created? There already
exist APIs for both kinds of devices. And why should it use X?

And how is a GUI related to that API?

What do you want to do exactly?

Bye,
  Henning


From john@netpurgatory.com  Sun Oct 24 22:53:39 2004
From: john@netpurgatory.com (John C. Vernaleo)
Date: Sun, 24 Oct 2004 17:53:39 -0400 (EDT)
Subject: [sane-devel] Epson Perfection 1640SU
Message-ID: <Pine.LNX.4.50.0410241150360.22494-100000@thales.astro.umd.edu>

I was wondering what the status of the Automatic Document Feeder on the 
Epson Perfection 1640SU.

There is a bug report (#300572) that says it doesn't work with the 
backends 1.0.13, but that is not the most recent version of the backends.

I know it worked with backends 1.0.12 on Fedora Core 1 and that it no 
longer works on Fedora Core 2 with backends 1.0.13 (like the bug report).  
Has anyone tried 1.0.14, or one of the 1.0.15 pre-releases?

I'm willing to compile and install from source if someone has seen it work 
(or if doing so could help us find out what the problem is).

Thanks.

John


From wberrier@myrealbox.com  Mon Oct 25 04:23:02 2004
From: wberrier@myrealbox.com (Wade Berrier)
Date: Sun, 24 Oct 2004 21:23:02 -0600
Subject: [sane-devel] Visioneer 8700
Message-ID: <1098674582.25452.3.camel@crusader>

--=-ePiGda6Ck/MmkW25dog3
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I'm toying with the idea of attempting to write a backend for my
Visioneer Onetouch 8700 Scanner.  Anyone else out there interested in
this?

Sometimes I wonder if it would be worth writing the driver, compared to
going down to Costco and picking up a supported scanner for $100.

I don't have any usb experience, but I was planning on using a usb
sniffer on windows to try to get the protocol down.

Anyone have any info/suggestions for this task?

Wade

--=-ePiGda6Ck/MmkW25dog3
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBfHGWJdBQI46NyjERAgVCAKC6hQB4f7IHI/4lcb3NhWnLowCwFQCgvKs9
Wmc3+w+E6yEri9f5GRdKW/w=
=1TTW
-----END PGP SIGNATURE-----

--=-ePiGda6Ck/MmkW25dog3--



From nteknikk@monet.no  Mon Oct 25 16:29:27 2004
From: nteknikk@monet.no (Terje J. Hanssen)
Date: Mon, 25 Oct 2004 17:29:27 +0200
Subject: [sane-devel] Epson Perfection 1640SU
Message-ID: <417D1BD7.4090906@monet.no>

John C. Vernaleo wrote:

> I was wondering what the status of the Automatic Document Feeder on the
> Epson Perfection 1640SU.
>
> There is a bug report (#300572) that says it doesn't work with the
> backends 1.0.13, but that is not the most recent version of the backends.
>
> I know it worked with backends 1.0.12 on Fedora Core 1 and that it no
> longer works on Fedora Core 2 with backends 1.0.13 (like the bug report).
> Has anyone tried 1.0.14, or one of the 1.0.15 pre-releases?
>
> I'm willing to compile and install from source if someone has seen it 
> work
> (or if doing so could help us find out what the problem is).


I got and posted this Epson 1640SU ADF problem with Sane 1.0.14 on Suse 
Linux 9.1 and on SJDS2/Linux.

Another user replied later that also Sane 1.013 on Suse Linux didn't 
work. However, stepping back to Sane 1.08 did work on Suse. I did the 
same and 1.08 worked for both Suse 9.1 and SJDS/Linux.

Karl Heinz should compare Sane 1.014 vs 1.08 to try to debug the 
problem. I haven't heard more about this ;-) maybe now as this is a 
problem for more of us?

http://lists.alioth.debian.org/pipermail/sane-devel/2004-August/011733.html
http://lists.alioth.debian.org/pipermail/sane-devel/2004-September/012094.html

Regards,
Terje J. Hanssen




From mailanryck@muenster.de  Sun Oct 24 20:48:16 2004
From: mailanryck@muenster.de (Ryck Purschke-Evers)
Date: Sun, 24 Oct 2004 21:48:16 +0200
Subject: [sane-devel] CanoScan D1250U2
Message-ID: <417C0700.4070908@muenster.de>

Hello!

Is there anybody working on a backend for a Canon CanoScan D1250U2?
When not, can someone help me to "build" (is that right, to "build" a 
backend?) the backend?

Greetings
    Ryck



From gerard@gkall.hobby.nl  Mon Oct 25 20:33:56 2004
From: gerard@gkall.hobby.nl (gerard klaver)
Date: Mon, 25 Oct 2004 19:33:56 +0000
Subject: [sane-devel] CanoScan D1250U2
In-Reply-To: <417C0700.4070908@muenster.de>
References: <417C0700.4070908@muenster.de>
Message-ID: <1098732835.2460.1.camel@gk-lex3>

On Sun, 2004-10-24 at 19:48, Ryck Purschke-Evers wrote:
> Hello!
> 
> Is there anybody working on a backend for a Canon CanoScan D1250U2?
> When not, can someone help me to "build" (is that right, to "build" a 
> backend?) the backend?
> 
> Greetings
>     Ryck

For status see the information on this page:

http://www.sane-project.org/unsupported/canon-d1250u2.html

-- 
----------
m.vr.gr.
Gerard Klaver



From the.beauty@adslhome.dk  Tue Oct 26 14:30:00 2004
From: the.beauty@adslhome.dk (Torben Andersen)
Date: Tue, 26 Oct 2004 15:30:00 +0200
Subject: [sane-devel] FC 2, hotplug and sane
Message-ID: <417E5158.2060606@adslhome.dk>

Hi,

I've installed a FC2 and updated. I can use sane, but only as root. I've 
been googling and reading and narrowed the problem to the USB interface 
to my Epson scanner. According to 
http://www.sane-project.org/README.linux, hotplug (which is compiled in 
the kernel) and /etc/hotplug/usb/libusbscanner (pasted in below 
signature) should  enable useracces to the scanner, if

"Usually you must just add the users that are allowed to access the scanner to group "scanner""

I don't know how to do that.

If I unplug and plug the scanner, user acces is allowed, but not on boot up !

Any help will bee appriciated :-)

Regards Torben

Contents af libusbscanner:

#!/bin/bash
# $Id: libusbscanner,v 1.1 2004/05/04 13:05:27 twaugh Exp $
#
# /etc/hotplug/usb/libusbscanner
#
# Sets up newly plugged in USB scanner so that the user who owns
# the console according to pam_console can access it from user space
#
# Note that for this script to work, you'll need all of the following:
# a) a line in the file /etc/hotplug/usermap that corresponds to the 
#    camera you are using.
# b) a setup using pam_console creates the respective lock files
#    containing the name of the respective user. You can check for that
#    by executing "echo `cat /var/{run,lock}/console.lock`" and 
#    verifying the appropriate user is mentioned somewhere there.
# c) a Linux kernel supporting hotplug and usbdevfs
# d) the hotplug package (http://linux-hotplug.sourceforge.net/)
#
# In the usermap file, the first field "usb module" should be named 
# "libusbscanner" like this script.
# 

if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
then
    # New code, using lock files instead of copying /dev/console permissions
    # This also works with non-gdm logins (e.g. on a virtual terminal)
    # Idea and code from Nalin Dahyabhai <nalin@redhat.com>
    if [ -f /var/run/console.lock ]
    then
        CONSOLEOWNER=`cat /var/run/console.lock`
    elif [ -f /var/lock/console.lock ]
    then
        CONSOLEOWNER=`cat /var/lock/console.lock`
    else
        CONSOLEOWNER=
    fi
    if [ -n "$CONSOLEOWNER" ]
    then
        chmod 0000 "${DEVICE}"
        chown "$CONSOLEOWNER" "${DEVICE}"
        chmod 0600 "${DEVICE}"
    fi
fi





-- 
"It's trivial to make fun of Microsoft products,
but it takes a real man to make them work,
and a god to make them do anything useful."



From henning@meier-geinitz.de  Tue Oct 26 17:34:16 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 26 Oct 2004 18:34:16 +0200
Subject: [sane-devel] FC 2, hotplug and sane
In-Reply-To: <417E5158.2060606@adslhome.dk>
References: <417E5158.2060606@adslhome.dk>
Message-ID: <20041026163416.GB19439@meier-geinitz.de>

Hi,

On Tue, Oct 26, 2004 at 03:30:00PM +0200, Torben Andersen wrote:
> I've installed a FC2 and updated. I can use sane, but only as root. I've 
> been googling and reading and narrowed the problem to the USB interface 
> to my Epson scanner. According to 
> http://www.sane-project.org/README.linux, hotplug (which is compiled in 
> the kernel) and /etc/hotplug/usb/libusbscanner (pasted in below 
> signature) should  enable useracces to the scanner, if
> 
> "Usually you must just add the users that are allowed to access the scanner 
> to group "scanner""
> 
> I don't know how to do that.

man gpasswd
man usermod
man groups
man group

> If I unplug and plug the scanner, user acces is allowed,

In this case hotplug is set up correctly.

>but not on boot up !

I have heard rumors about this problem and was told that "coldplug"
would help.

But:

> #!/bin/bash
> # $Id: libusbscanner,v 1.1 2004/05/04 13:05:27 twaugh Exp $

This is not the libusbscanner script from the sane-backends package.
It doesn't seem to work by using groups but by giving access to the
scanner to anyone who is logged-in locally. Quite strange.
Anyway, for details ask your distributor.

I haven't looked at the details but if the device is plugged-in while
nobody is logged in I guess only root can access it. Or do I
misunderstand the script?

Bye,
  Henning


From kpschrage@gmx.de  Tue Oct 26 18:54:11 2004
From: kpschrage@gmx.de (Klaus-Peter Schrage)
Date: Tue, 26 Oct 2004 19:54:11 +0200
Subject: [sane-devel] FC 2, hotplug and sane
In-Reply-To: <417E5158.2060606@adslhome.dk>
References: <417E5158.2060606@adslhome.dk>
Message-ID: <417E8F43.6090701@gmx.de>

Torben Andersen wrote:
> Hi,
> 
> I've installed a FC2 and updated. I can use sane, but only as root. I've 
> been googling and reading and narrowed the problem to the USB interface 
> to my Epson scanner. According to 
> http://www.sane-project.org/README.linux, hotplug (which is compiled in 
> the kernel) and /etc/hotplug/usb/libusbscanner (pasted in below 
> signature) should  enable useracces to the scanner, if

This is a known issue, see
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124053
Klaus


From wolframheider@web.de  Tue Oct 26 19:24:00 2004
From: wolframheider@web.de (Wolfram Heider)
Date: Tue, 26 Oct 2004 20:24:00 +0200
Subject: [sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S
Message-ID: <200410262024.00402.wolframheider@web.de>

Hello list,

when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with kernel 
2.6.5, my scanner, a UMAX Astra 1220 S which had worked well troughout all 
the kernel-versons of the last years, was gone without the slightest trace.  
scanimage -L, sane-find-scanner and the other little helpers remainend silent 
about it.
Maybe it's not a really sane-problem but a controller-problem.
The controller in use is a Dawicontrol DC-2975-C which connected till now over 
the sym53c8xx/ncr53c8xx-module.
The strange thing is that with the kernel 2.6.1 of the knoppix 
3.4-distribution everthing works as usual.
The Suse-Kernel still comes with the sym53c8xx-module, but something seems to 
be wrong with it.
I wasn't very close to the list in the last few months, so perhaps I missed 
some relevant stuff - sorry if I ask those damn old questions.
Is anybody out there who expierienced a similar kind of behaviour and has got 
a solution for it?

Thanks in advance

Wolfram Heider 


From adeuring@gmx.net  Tue Oct 26 21:11:44 2004
From: adeuring@gmx.net (abel deuring)
Date: Tue, 26 Oct 2004 22:11:44 +0200
Subject: [sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S
In-Reply-To: <200410262024.00402.wolframheider@web.de>
References: <200410262024.00402.wolframheider@web.de>
Message-ID: <417EAF80.7030005@gmx.net>

Wolfram Heider wrote:
> Hello list,
> 
> when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with kernel 
> 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well troughout all 
> the kernel-versons of the last years, was gone without the slightest trace.  
> scanimage -L, sane-find-scanner and the other little helpers remainend silent 
> about it.
> Maybe it's not a really sane-problem but a controller-problem.

yes, it's most likely a problem in the Linux SCSI system. To look for 
SCSI scanners, sane-find-scanner reads /proc/scsi/scsi, and the contents 
of this proc file is "managed" by the SCSI system of the kernel.

> The controller in use is a Dawicontrol DC-2975-C which connected till now over 
> the sym53c8xx/ncr53c8xx-module.
> The strange thing is that with the kernel 2.6.1 of the knoppix 
> 3.4-distribution everthing works as usual.
> The Suse-Kernel still comes with the sym53c8xx-module, but something seems to 
> be wrong with it.

Are you sure that the sym/ncr53c8xx module is indeed loaded? And if it 
loaded, do you get any error messages in /var/log/messages?

The sym/ncr53c8xx drivers offer many parameters; perhaps it helps to 
play with some of them. The file
<kernel source dir>/drivers/scsi/README.ncr53c8xx describes these 
parameters quite detailed.

Abel


From kpschrage@gmx.de  Tue Oct 26 21:48:13 2004
From: kpschrage@gmx.de (Klaus-Peter Schrage)
Date: Tue, 26 Oct 2004 22:48:13 +0200
Subject: [sane-devel] FC 2, hotplug and sane  - SOLVED
In-Reply-To: <417EA07C.4020705@adslhome.dk>
References: <417E5158.2060606@adslhome.dk> <417E8F43.6090701@gmx.de> <417EA07C.4020705@adslhome.dk>
Message-ID: <417EB80D.7050901@gmx.de>

Torben Andersen wrote:
> Thanks to Klaus-Peter. His link had a solution: Put
> 
> chmod 0666 "$DEVICE"
> 
> in the bottom of the libusbscanner. I don't know if its a perfect 
> solution, but it certainly worked.
> 

That's what I've done, and nobody ever gave me a good reason why this 
shouln't be done.
Klaus


From wolframheider@web.de  Tue Oct 26 21:59:26 2004
From: wolframheider@web.de (Wolfram Heider)
Date: Tue, 26 Oct 2004 22:59:26 +0200
Subject: [sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S
Message-ID: <200410262259.26185.wolframheider@web.de>

Am Dienstag, 26. Oktober 2004 22:11 schrieben Sie:
> Wolfram Heider wrote:
> > Hello list,
> >
> > when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with
> > kernel 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well
> > troughout all the kernel-versons of the last years, was gone without the
> > slightest trace. scanimage -L, sane-find-scanner and the other little
> > helpers remainend silent about it.
> > Maybe it's not a really sane-problem but a controller-problem.
>
> yes, it's most likely a problem in the Linux SCSI system. To look for
> SCSI scanners, sane-find-scanner reads /proc/scsi/scsi, and the contents
> of this proc file is "managed" by the SCSI system of the kernel.
>
> > The controller in use is a Dawicontrol DC-2975-C which connected till now
> > over the sym53c8xx/ncr53c8xx-module.
> > The strange thing is that with the kernel 2.6.1 of the knoppix
> > 3.4-distribution everthing works as usual.
> > The Suse-Kernel still comes with the sym53c8xx-module, but something
> > seems to be wrong with it.
>
> Are you sure that the sym/ncr53c8xx module is indeed loaded? And if it
> loaded, do you get any error messages in /var/log/messages?
>
> The sym/ncr53c8xx drivers offer many parameters; perhaps it helps to
> play with some of them. The file
> <kernel source dir>/drivers/scsi/README.ncr53c8xx describes these
> parameters quite detailed.
>
> Abel

Good evening; Abel

thanks for your quick reply.
The sym53c8xx modul isn't loadde at boottime. When loaded by hand via
 modprobe it takes suspiciously long time to come up - and finanally nothing
 has changed - everthing dead as the cemetry of Chicago. Only lspci gives a
 hint that there is something in the slot.
I'll take your advice and play around a little bit with the driver
 parameters. See you later.

Wolfram
( I first choosed the wrong reply address - sorry)


From herbr@pfinders.com  Tue Oct 26 22:05:40 2004
From: herbr@pfinders.com (herbr@pfinders.com)
Date: Tue, 26 Oct 2004 14:05:40 -0700 (PDT)
Subject: [sane-devel] feeder for scanner
Message-ID: <3079.144.91.44.131.1098824740.squirrel@144.91.44.131>

Hi,

I would like to buy a nice high end scanner that is supported
that has a document feeder. Any suggestions? Any experiences?

How do you handle a jam? What kind of speed. How many documents
can fit?

Herb
Pathfinders Software




From wolframheider@web.de  Tue Oct 26 22:25:03 2004
From: wolframheider@web.de (Wolfram Heider)
Date: Tue, 26 Oct 2004 23:25:03 +0200
Subject: [sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S
In-Reply-To: <417EAF80.7030005@gmx.net>
References: <200410262024.00402.wolframheider@web.de> <417EAF80.7030005@gmx.net>
Message-ID: <200410262325.03916.wolframheider@web.de>

Am Dienstag, 26. Oktober 2004 22:11 schrieb abel deuring:
> Wolfram Heider wrote:
> > Hello list,
> >
> > when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with
> > kernel 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well
> > troughout all the kernel-versons of the last years, was gone without the
> > slightest trace. scanimage -L, sane-find-scanner and the other little
> > helpers remainend silent about it.
> > Maybe it's not a really sane-problem but a controller-problem.
>
> yes, it's most likely a problem in the Linux SCSI system. To look for
> SCSI scanners, sane-find-scanner reads /proc/scsi/scsi, and the contents
> of this proc file is "managed" by the SCSI system of the kernel.
>
> > The controller in use is a Dawicontrol DC-2975-C which connected till now
> > over the sym53c8xx/ncr53c8xx-module.
> > The strange thing is that with the kernel 2.6.1 of the knoppix
> > 3.4-distribution everthing works as usual.
> > The Suse-Kernel still comes with the sym53c8xx-module, but something
> > seems to be wrong with it.
>
> Are you sure that the sym/ncr53c8xx module is indeed loaded? And if it
> loaded, do you get any error messages in /var/log/messages?
>
> The sym/ncr53c8xx drivers offer many parameters; perhaps it helps to
> play with some of them. The file
> <kernel source dir>/drivers/scsi/README.ncr53c8xx describes these
> parameters quite detailed.
>
> Abel

Hello Abel,

here is the output a "modprobe sym53c8xx" produces in /var/log/messages:

Oct 26 23:11:16 linux su: (to root) ich on /dev/pts/3
Oct 26 23:11:16 linux su: pam_unix2: session started for user root, service su 
Oct 26 23:11:32 linux kernel: sym0: <875> rev 0x26 at pci 0000:00:11.0 irq 12
Oct 26 23:11:32 linux kernel: sym0: No NVRAM, ID 7, Fast-20, SE, parity 
checking
Oct 26 23:11:32 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:11:32 linux kernel: scsi0 : sym-2.1.18i
Oct 26 23:11:38 linux kernel: sym0:0:0: ABORT operation started.
Oct 26 23:11:43 linux kernel: sym0:0:0: ABORT operation timed-out.
Oct 26 23:11:43 linux kernel: sym0:0:0: DEVICE RESET operation started.
Oct 26 23:11:48 linux kernel: sym0:0:0: DEVICE RESET operation timed-out.
Oct 26 23:11:48 linux kernel: sym0:0:0: BUS RESET operation started.
Oct 26 23:11:53 linux kernel: sym0:0:0: BUS RESET operation timed-out.
Oct 26 23:11:53 linux kernel: sym0:0:0: HOST RESET operation started.
Oct 26 23:11:53 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:11:58 linux kernel: sym0:0:0: HOST RESET operation timed-out.
Oct 26 23:11:58 linux kernel: scsi: Device offlined - not ready after error 
recovery: host 0 channel 0 id 0 lun 0
Oct 26 23:12:03 linux kernel: sym0:1:0: ABORT operation started.
Oct 26 23:12:08 linux kernel: sym0:1:0: ABORT operation timed-out.
Oct 26 23:12:08 linux kernel: sym0:1:0: DEVICE RESET operation started.
Oct 26 23:12:13 linux kernel: sym0:1:0: DEVICE RESET operation timed-out.
Oct 26 23:12:13 linux kernel: sym0:1:0: BUS RESET operation started.
Oct 26 23:12:18 linux kernel: sym0:1:0: BUS RESET operation timed-out.
Oct 26 23:12:18 linux kernel: sym0:1:0: HOST RESET operation started.
Oct 26 23:12:18 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:12:23 linux kernel: sym0:1:0: HOST RESET operation timed-out.
Oct 26 23:12:23 linux kernel: scsi: Device offlined - not ready after error 
recovery: host 0 channel 0 id 1 lun 0
Oct 26 23:12:29 linux kernel: sym0:2:0: ABORT operation started.
Oct 26 23:12:34 linux kernel: sym0:2:0: ABORT operation timed-out.
Oct 26 23:12:34 linux kernel: sym0:2:0: DEVICE RESET operation started.
Oct 26 23:12:38 linux su: (to root) ich on /dev/pts/7
Oct 26 23:12:38 linux su: pam_unix2: session started for user root, service su 
Oct 26 23:12:39 linux kernel: sym0:2:0: DEVICE RESET operation timed-out.
Oct 26 23:12:39 linux kernel: sym0:2:0: BUS RESET operation started.
Oct 26 23:12:42 linux su: pam_unix2: session finished for user root, service 
su 
Oct 26 23:12:42 linux su: (to root) ich on /dev/pts/7
Oct 26 23:12:42 linux su: pam_unix2: session started for user root, service su 
Oct 26 23:12:44 linux kernel: sym0:2:0: BUS RESET operation timed-out.
Oct 26 23:12:44 linux kernel: sym0:2:0: HOST RESET operation started.
Oct 26 23:12:44 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:12:49 linux kernel: sym0:2:0: HOST RESET operation timed-out.
Oct 26 23:12:49 linux kernel: scsi: Device offlined - not ready after error 
recovery: host 0 channel 0 id 2 lun 0
Oct 26 23:12:54 linux kernel: sym0:3:0: ABORT operation started.
Oct 26 23:12:59 linux kernel: sym0:3:0: ABORT operation timed-out.
Oct 26 23:12:59 linux kernel: sym0:3:0: DEVICE RESET operation started.
Oct 26 23:13:04 linux kernel: sym0:3:0: DEVICE RESET operation timed-out.
Oct 26 23:13:04 linux kernel: sym0:3:0: BUS RESET operation started.
Oct 26 23:13:09 linux kernel: sym0:3:0: BUS RESET operation timed-out.
Oct 26 23:13:09 linux kernel: sym0:3:0: HOST RESET operation started.
Oct 26 23:13:09 linux kernel: sym0: SCSI BUS has been reset.

Sounds as there is something fundamental going wrong. Can you make it out?

Greetings

Wolfram


From thetargos@slackercentral.com  Wed Oct 27 05:58:49 2004
From: thetargos@slackercentral.com (Gian Paolo Mureddu)
Date: Tue, 26 Oct 2004 23:58:49 -0500
Subject: [sane-devel] feeder for scanner
In-Reply-To: <3079.144.91.44.131.1098824740.squirrel@144.91.44.131>
References: <3079.144.91.44.131.1098824740.squirrel@144.91.44.131>
Message-ID: <417F2B09.9040100@slackercentral.com>

herbr@pfinders.com wrote:

>Hi,
>
>I would like to buy a nice high end scanner that is supported
>that has a document feeder. Any suggestions? Any experiences?
>
>How do you handle a jam? What kind of speed. How many documents
>can fit?
>
>Herb
>Pathfinders Software
>
>
>
>  
>
Interesting question, a friend of mine is also interested on a 
professional scanner for his Linux box, I'm eager to see the suggestions.


From gerard@gkall.hobby.nl  Wed Oct 27 13:36:26 2004
From: gerard@gkall.hobby.nl (gerard klaver)
Date: Wed, 27 Oct 2004 12:36:26 +0000
Subject: [sane-devel] Re: [Lcms-user] monitor profile questions -- adding vcgt to a
 profile?
In-Reply-To: <200410191019.i9JAJu1W025691@web218.megawebservers.com>
References: <200410191019.i9JAJu1W025691@web218.megawebservers.com>
Message-ID: <1098880586.2799.16.camel@gk-lex3>

On Tue, 2004-10-19 at 10:19, marti@littlecms.com wrote:
> Hi,
> 
> > >Are the reasons known? Just curious..
> 
> 
> As Gerhard already noted, I am not allowed to support or maintain 
> the lprof package anymore. The reasons are the company I work 
> for (HP) acquired the sources for its internal use. 
> 
> Moreover, the technology I was using in the latest profilers (not 
> lprof, but what intended to sell as professional package) is 
> "sensible" in terms my non-disclosure agreement. So, I 
> sacrificed this package in order to keep lcms (the CMM) alive 
> and well. 
> 
> HP kindly allow me to continue the development of lcms as 
> open source and even more, they does SUPPORT this development. 
> In such way I have contact with ICC members, access to restricted 
> documents, proposed extensions, etc.
> 
> So, I'm very sorry for that, but lprof is now effectively dead. 
> At least as open source. It would be nice, however, if anybody 
> would take the sources and continue with the development. But as said, 
> I am not allowed to do that anymore.
> 
> King regards,
> Marti.
> 
Hello,

To keep the lprof package available i have placed the lprof files and
other information from Marti old profilers page on my homepage.
See http://gkall.hobby.nl/sane-lprof/sane-lprof.html

Goal is to maintain the package as good as possible but time and/or
knowledge can be a problem. Also if more people are interested in
maintaining this package, let me know.
Then maintenance depends not on a single person and placing it in the
SANE CVS tree (sane-lprof or first sane/experimental/sane-lprof) is a
good option. See als SANE Bugreport 30181.
 
In this way more people are be able to use the package on more platforms
and there is a tracking system for the patches and changes.

And if you have any remarks/comments/updates on/for this page, please
let me know.


-- 
----------
m.vr.gr.
Gerard Klaver



From anoah@pfeiffer.edu  Wed Oct 27 14:04:24 2004
From: anoah@pfeiffer.edu (m. allan noah)
Date: Wed, 27 Oct 2004 09:04:24 -0400 (EDT)
Subject: [sane-devel] feeder for scanner
In-Reply-To: <417F2B09.9040100@slackercentral.com>
References: <3079.144.91.44.131.1098824740.squirrel@144.91.44.131>
 <417F2B09.9040100@slackercentral.com>
Message-ID: <Pine.LNX.4.61.0410270904030.7940@limos.pfeiffer.edu>

try searching the archives of this mailing list. this comes up every few 
months.

allan

On Tue, 26 Oct 2004, Gian Paolo Mureddu wrote:

> herbr@pfinders.com wrote:
>
>> Hi,
>> 
>> I would like to buy a nice high end scanner that is supported
>> that has a document feeder. Any suggestions? Any experiences?
>> 
>> How do you handle a jam? What kind of speed. How many documents
>> can fit?
>> 
>> Herb
>> Pathfinders Software
>> 
>> 
>> 
>> 
> Interesting question, a friend of mine is also interested on a professional 
> scanner for his Linux box, I'm eager to see the suggestions.
>
>

-- 
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera


From artpi@ptic.pl  Wed Oct 27 15:01:43 2004
From: artpi@ptic.pl (Artur Pierscinski)
Date: Wed, 27 Oct 2004 16:01:43 +0200
Subject: [sane-devel] genesys backend - warming up procedure
Message-ID: <417FAA47.2010903@ptic.pl>

Hi!

I have question about warming up procedure in genesys backend (scaner: 
Plustek ST24).

How is proper range of readed values from scaner sensor during warming 
up the lamp procedure?
It seems for me like a 12-bits (sensor), with set other (higher) bit set.
So, calculated average values are about 9600, which in my case
newer pass warming loop exit:

      if (second_average > (110 * 256) && (((double) difference) / 
second_average) < 0.002)
        {
          DBG (DBG_info, "genesys_warmup_lamp: warmup succeeded after %d 
seconds\n",
               seconds);
          break;
         }

Multiply  second_average by 3 in above condition will satisfied it,
and warming up lamp ends with success.
Is those belongs only to  my scanner or happed on others to?

Artur Pierscinski

e-mail: artpi@ptic.pl


From gerhard@gjaeger.de  Wed Oct 27 16:46:29 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Wed, 27 Oct 2004 17:46:29 +0200
Subject: [sane-devel] genesys backend - warming up procedure
In-Reply-To: <417FAA47.2010903@ptic.pl>
References: <417FAA47.2010903@ptic.pl>
Message-ID: <200410271746.29865.gerhard@gjaeger.de>

On Mittwoch 27 Oktober 2004 16:01, Artur Pierscinski wrote:
> Hi!
>
> I have question about warming up procedure in genesys backend (scaner:
> Plustek ST24).
>
> How is proper range of readed values from scaner sensor during warming
> up the lamp procedure?
> It seems for me like a 12-bits (sensor), with set other (higher) bit set.
> So, calculated average values are about 9600, which in my case
> newer pass warming loop exit:
>
>       if (second_average > (110 * 256) && (((double) difference) /
> second_average) < 0.002)
>         {
>           DBG (DBG_info, "genesys_warmup_lamp: warmup succeeded after %d
> seconds\n",
>                seconds);
>           break;
>          }
>
> Multiply  second_average by 3 in above condition will satisfied it,
> and warming up lamp ends with success.
> Is those belongs only to  my scanner or happed on others to?
>

Hi,

I've done some tests here with the ST24 and rewrote some parts of
the code, that the warmup and calibration stuff gets passed on it.
The major problem of the current genesys code is, that it is tied to
a UMAX device. All the settings specific to CCD and DAC (and motor)
are only valid for this scanner. This needs to be tweaked. I did this
here, but the code is not available so far ....

Gerhard




From henning@meier-geinitz.de  Wed Oct 27 17:19:52 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 27 Oct 2004 18:19:52 +0200
Subject: [sane-devel] FC 2, hotplug and sane  - SOLVED
In-Reply-To: <417EB80D.7050901@gmx.de>
References: <417E5158.2060606@adslhome.dk> <417E8F43.6090701@gmx.de> <417EA07C.4020705@adslhome.dk> <417EB80D.7050901@gmx.de>
Message-ID: <20041027161952.GA14330@meier-geinitz.de>

Hi,

On Tue, Oct 26, 2004 at 10:48:13PM +0200, Klaus-Peter Schrage wrote:
> Torben Andersen wrote:
> >Thanks to Klaus-Peter. His link had a solution: Put
> >
> >chmod 0666 "$DEVICE"
> >
> >in the bottom of the libusbscanner. I don't know if its a perfect 
> >solution, but it certainly worked.
> >
> 
> That's what I've done, and nobody ever gave me a good reason why this 
> shouln't be done.

If you are the only user on your system, that's ok.

Bye,
  Henning


From mmotovsk@gnome.sk  Wed Oct 27 21:20:28 2004
From: mmotovsk@gnome.sk (Martin Motovsky)
Date: Wed, 27 Oct 2004 20:20:28 +0000 (GMT)
Subject: [sane-devel] Epson 1250 scanner does not return back after scanning
Message-ID: <1098908428026_29625227@aladarko.gnome.sk>

Dear sirs,

we have a problem with our Epson 1250 scanner. It scans an image correctly,
but after scanning, a lamp remains be switched on and a scanner's header
remains at the "end of the image" position. I.e. it does not return back to
the original home position. Can somebody help us?

We have 
- FreeBSD system
- sane-backends-1.0.14
- only unmarked driver in the dll.conf if a plustek driver

Martin Motovsky


From wolframheider@web.de  Thu Oct 28 03:27:54 2004
From: wolframheider@web.de (Wolfram Heider)
Date: Thu, 28 Oct 2004 04:27:54 +0200
Subject: [sane-devel] Suse9.1, sym53c8xx and umaxscanner, help from Abel
Message-ID: <200410280427.54100.wolframheider@web.de>

Hello list,

with updating to Suse 9.1 I got a lot of trouble with my scanner, a vernerable 
umax 1220 S, connected via the sym53c8xx module, which had worked absolutely 
flawlessly till then. The module wasn't loaded ast boottime, the scanner 
because of this not regonized. Module loading by hand lasted extremely long 
and unloading wasn't just impossible. The same procedure with additional 
parameters brought but little relief - the scanner remained dead.
I talked about this problem and the problems I faced during the initial setup 
of Suse 9.1, when automatic installation didn't work, because Yast searched 
for a scsi-harddrive that didn't exist (the only client of the controller was 
the scanner), with Abel Deuring. He proposed to focus on the coldplug script 
and to switch it off for tresting. And that was it. There must be something 
considerably wrong in the realm of this script. So I would recommend to 
everyone who also faces the Suse9.1/sym53c8xx-problem and can afford to get 
on without USB-support to deactivate the 
startupscript /etc/init.d/rc5./S02coldplug till the folks at Suse have done 
it better.

Greetings

Wolfram Heider
 


From olaf@epkowa.co.jp  Thu Oct 28 04:42:37 2004
From: olaf@epkowa.co.jp (Olaf Meeuwissen)
Date: Thu, 28 Oct 2004 12:42:37 +0900
Subject: [sane-devel] Epson 1250 scanner does not return back after
 scanning
In-Reply-To: <1098908428026_29625227@aladarko.gnome.sk> (Martin Motovsky's
 message of "Wed, 27 Oct 2004 20:20:28 +0000 (GMT)")
References: <1098908428026_29625227@aladarko.gnome.sk>
Message-ID: <87mzy75x02.fsf@zen.epkowa.co.jp>

Martin Motovsky <mmotovsk@gnome.sk> writes:

> Dear sirs,
>
> we have a problem with our Epson 1250 scanner. It scans an image correctly,
> but after scanning, a lamp remains be switched on and a scanner's header
> remains at the "end of the image" position. I.e. it does not return back to
> the original home position. Can somebody help us?

The lamp has to be switched off by the software.  I don't know if the
plustek backend does that.

> We have 
> - FreeBSD system
> - sane-backends-1.0.14
> - only unmarked driver in the dll.conf if a plustek driver

You may want to try the epkowa backend that comes as part of "Image
Scan! for Linux" which is downloadable via:

  http://www.epkowa.co.jp/english/linux_e/dl_scan.html

Hope this helps,
-- 
Olaf Meeuwissen                            EPSON KOWA Corporation, PF1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2


From gerhard@gjaeger.de  Thu Oct 28 08:19:56 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Thu, 28 Oct 2004 09:19:56 +0200
Subject: [sane-devel] Epson 1250 scanner does not return back after scanning
In-Reply-To: <1098908428026_29625227@aladarko.gnome.sk>
References: <1098908428026_29625227@aladarko.gnome.sk>
Message-ID: <200410280919.56899.gerhard@gjaeger.de>

On Mittwoch 27 Oktober 2004 22:20, Martin Motovsky wrote:
> Dear sirs,
>
> we have a problem with our Epson 1250 scanner. It scans an image correctly,
> but after scanning, a lamp remains be switched on and a scanner's header
> remains at the "end of the image" position. I.e. it does not return back to
> the original home position. Can somebody help us?
>
> We have
> - FreeBSD system
> - sane-backends-1.0.14
> - only unmarked driver in the dll.conf if a plustek driver
>
The lamp is switched off by the software and the behaviour can be setup
in the configuration file. Why the sensor gets stucked, I don't know.
Can you please retry and enabling the debug message before, i.e.
export SANE_DEBUG_PLUSTEK=20 ; scanimage [what-ever-parameter-you-need]

--
 Gerhard



From mmotovsk@gnome.sk  Thu Oct 28 10:16:09 2004
From: mmotovsk@gnome.sk (Martin Motovsky)
Date: Thu, 28 Oct 2004 11:16:09 +0200
Subject: [sane-devel] Epson 1250 scanner does not return back after scanning
In-Reply-To: <200410280919.56899.gerhard@gjaeger.de>
References: <1098908428026_29625227@aladarko.gnome.sk> <200410280919.56899.gerhard@gjaeger.de>
Message-ID: <013E3129-28C2-11D9-9806-000393775A6A@gnome.sk>

Thank you for previous advices.

While testing scanimage in the debug mode, I mentioned, that sometimes 
it finished scanning correctly and sometime not. Below is a debug 
output, when lamp remained on and scanner's header did not return back 
to original position.

Martin

---------------------------------------------------
I used this script:
export SANE_DEBUG_PLUSTEK=20 ; scanimage -d plustek:/dev/uscanner0 
--format tiff -l10 -t10 -x100 -y100 --resolution 150dpi --mode Color > 
test.tiff 2>log.txt

---------------------------------------------------
Here is a debug output:

[sanei_debug] Setting debug level of plustek to 20.
[plustek] Plustek backend V0.47-11, part of sane-backends 1.0.14
[plustek] ># Plustek-SANE Backend configuration file<
[plustek] ># For use with LM9831/2/3 based USB scanners<
[plustek] >#<
[plustek] ><
[plustek] ># each device needs at least two lines:<
[plustek] ># - [usb] vendor-ID and product-ID<
[plustek] ># - device devicename<
[plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)<
[plustek] ># [usb] 0x07B3 0x0017<
[plustek] ># device /dev/usbscanner<
[plustek] ># or<
[plustek] ># device libusb:bbb:ddd<
[plustek] ># where bbb is the busnumber and ddd the device number<
[plustek] ># make sure that your user has access to 
/proc/bus/usb/bbb/ddd<
[plustek] >#<
[plustek] ># additionally you can specify some options<
[plustek] ># warmup, lOffOnEnd, lampOff<
[plustek] >#<
[plustek] ># For autodetection use<
[plustek] ># [usb]<
[plustek] ># device /dev/usbscanner<
[plustek] >#<
[plustek] ># or simply<
[plustek] ># [usb]<
[plustek] >#<
[plustek] ># or if you want a specific device but you have no idea 
about the<
[plustek] ># device node or you use libusb, simply set vendor- and 
product-ID<
[plustek] ># [usb] 0x07B3 0x0017<
[plustek] ># device auto<
[plustek] >#<
[plustek] ># NOTE: autodetection is safe, as it uses the info it got<
[plustek] >#       from the USB subsystem. If you're not using the<
[plustek] >#       autodetection, you MUST have attached that device<
[plustek] >#       at your USB-port, that you have specified...<
[plustek] >#<
[plustek] ><
[plustek] >[usb]<
[plustek] next device uses autodetection
[plustek] ... next device
[plustek] ><
[plustek] >#<
[plustek] ># options for the previous USB entry<
[plustek] >#<
[plustek] ># switch lamp off after xxx secs, 0 disables the feature<
[plustek] >option lampOff 309<
[plustek] Decoding option >lampOff<
[plustek] ><
[plustek] ># warmup period in seconds, 0 means no warmup<
[plustek] >option warmup 15<
[plustek] Decoding option >warmup<
[plustek] ><
[plustek] ># 0 means leave lamp-status untouched, not 0 means switch 
off<
[plustek] ># on sane_close<
[plustek] >option lOffOnEnd 1<
[plustek] Decoding option >lOffOnEnd<
[plustek] ><
[plustek] >#<
[plustek] ># options to tweak the image start-position<
[plustek] ># (WARNING: there's no internal range check!!!)<
[plustek] >#<
[plustek] ># for the normal scan area<
[plustek] >#<
[plustek] >option posOffX 0<
[plustek] Decoding option >posOffX<
[plustek] >option posOffY 0<
[plustek] Decoding option >posOffY<
[plustek] ><
[plustek] ># for transparencies<
[plustek] >option tpaOffX 0<
[plustek] Decoding option >tpaOffX<
[plustek] >option tpaOffY 0<
[plustek] Decoding option >tpaOffY<
[plustek] ><
[plustek] ># for negatives<
[plustek] >option negOffX 0<
[plustek] Decoding option >negOffX<
[plustek] >option negOffY 0<
[plustek] Decoding option >negOffY<
[plustek] ><
[plustek] >#<
[plustek] ># for setting the calibration strip position<
[plustek] ># (WARNING: there's no internal range check!!!)<
[plustek] ># -1 means use built in<
[plustek] >#<
[plustek] >option posShadingY -1<
[plustek] Decoding option >posShadingY<
[plustek] >option tpaShadingY -1<
[plustek] Decoding option >tpaShadingY<
[plustek] >option negShadingY -1<
[plustek] Decoding option >negShadingY<
[plustek] ><
[plustek] >#<
[plustek] ># to invert the negatives, 0 disables the feature<
[plustek] >#<
[plustek] >option invertNegatives 0<
[plustek] Decoding option >invertNegatives<
[plustek] ><
[plustek] >#<
[plustek] ># to save/restore coarse calibration data<
[plustek] >#<
[plustek] >option cacheCalData 0<
[plustek] Decoding option >cacheCalData<
[plustek] ><
[plustek] >#<
[plustek] ># use alternate calibration routines<
[plustek] >#<
[plustek] >option altCalibration 0<
[plustek] Decoding option >altCalibration<
[plustek] ><
[plustek] >#<
[plustek] ># for skipping whole calibration step<
[plustek] >#<
[plustek] >option skipCalibration 0<
[plustek] Decoding option >skipCalibration<
[plustek] ><
[plustek] >#<
[plustek] ># for skipping entire fine calibration step<
[plustek] ># coarse calibration is done<
[plustek] >#<
[plustek] >option skipFine 0<
[plustek] Decoding option >skipFine<
[plustek] ><
[plustek] >#<
[plustek] ># discard the result of the fine white calibration<
[plustek] >#<
[plustek] >option skipFineWhite 0<
[plustek] Decoding option >skipFineWhite<
[plustek] ><
[plustek] ># for replacing the gain values found during<
[plustek] ># calibration<
[plustek] >option red_gain   -1<
[plustek] Decoding option >red_gain<
[plustek] >option green_gain -1<
[plustek] Decoding option >green_gain<
[plustek] >option blue_gain  -1<
[plustek] Decoding option >blue_gain<
[plustek] ><
[plustek] >#<
[plustek] >#<
[plustek] >option red_lampoff   -1<
[plustek] Decoding option >red_lampoff<
[plustek] >option green_lampoff -1<
[plustek] Decoding option >green_lampoff<
[plustek] >option blue_lampoff  -1<
[plustek] Decoding option >blue_lampoff<
[plustek] ><
[plustek] >#<
[plustek] ># for adjusting the default gamma values<
[plustek] >#<
[plustek] >option redGamma         1.0<
[plustek] Decoding option >redGamma<
[plustek] >option greenGamma       1.0<
[plustek] Decoding option >greenGamma<
[plustek] >option blueGamma        1.0<
[plustek] Decoding option >blueGamma<
[plustek] >option grayGamma        1.0<
[plustek] Decoding option >grayGamma<
[plustek] ><
[plustek] >#<
[plustek] ># to enable TPA (non Plustek devices only)<
[plustek] ># 0 means default behaviour as specified in the internal 
tables<
[plustek] ># 1 means enable<
[plustek] >#<
[plustek] >option enableTPA 0<
[plustek] Decoding option >enableTPA<
[plustek] ><
[plustek] >#<
[plustek] ># model override functionality, currently only available for<
[plustek] ># Mustek devices, using NSCs' vendor ID: 0x0400 and<
[plustek] ># also their product ID: 0x1000 (LM9831) 0x1001 (LM9832)<
[plustek] >#<
[plustek] ># mov/PID    |    0x1000   |   0x1001<
[plustek] ># ---------------------------------------<
[plustek] ># 0 (default)| BearPaw1200 | BearPaw 2400<
[plustek] ># 1          |   ignored   | BearPaw 1200<
[plustek] >#<
[plustek] >option mov 0<
[plustek] Decoding option >mov<
[plustek] ><
[plustek] >#<
[plustek] ># and of course the device-name<
[plustek] >#<
[plustek] ># device /dev/usbscanner<
[plustek] >device auto<
[plustek] Decoding device name >auto<
[plustek] ><
[plustek] >#<
[plustek] ># to define a new device, start with a new section:<
[plustek] ># [usb]<
[plustek] >#<
[plustek] attach (auto, 0xbfbfed24, 0x0)
[plustek] Device configuration:
[plustek] device name  : >auto<
[plustek] USB-ID       : ><
[plustek] model ovr.   : 0
[plustek] warmup       : 15s
[plustek] lampOff      : 309
[plustek] lampOffOnEnd : yes
[plustek] cacheCalData : no
[plustek] altCalibrate : no
[plustek] skipCalibr.  : no
[plustek] skipFine     : no
[plustek] skipFineWhite: no
[plustek] invertNegs.  : no
[plustek] pos_x        : 0
[plustek] pos_y        : 0
[plustek] pos_shading_y: -1
[plustek] neg_x        : 0
[plustek] neg_y        : 0
[plustek] neg_shading_y: -1
[plustek] tpa_x        : 0
[plustek] tpa_y        : 0
[plustek] tpa_shading_y: -1
[plustek] red gain     : -1
[plustek] green gain   : -1
[plustek] blue gain    : -1
[plustek] red lampoff  : -1
[plustek] green lampoff: -1
[plustek] blue lampoff : -1
[plustek] red Gamma    : 1.00
[plustek] green Gamma  : 1.00
[plustek] blue Gamma   : 1.00
[plustek] gray Gamma   : 1.00
[plustek] ---------------------
[plustek] usbDev_open(auto,)
[plustek] Autodetection...
[plustek] Checking for 0x07b3-0x0010
[plustek] Checking for 0x07b3-0x0011
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0015
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0013
[plustek] Checking for 0x07b3-0x0013
[plustek] Checking for 0x07b3-0x0011
[plustek] Checking for 0x07b3-0x0010
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0015
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0016
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0007
[plustek] Checking for 0x07b3-0x000f
[plustek] Checking for 0x07b3-0x000f
[plustek] Checking for 0x07b3-0x0005
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0012
[plustek] Checking for 0x0400-0x1000
[plustek] Checking for 0x0400-0x1001
[plustek] Checking for 0x0400-0x1001
[plustek] Checking for 0x0458-0x2007
[plustek] Checking for 0x0458-0x2008
[plustek] Checking for 0x0458-0x2009
[plustek] Checking for 0x0458-0x2013
[plustek] Checking for 0x0458-0x2015
[plustek] Checking for 0x0458-0x2016
[plustek] Checking for 0x03f0-0x0505
[plustek] Checking for 0x03f0-0x0605
[plustek] Checking for 0x04b8-0x010f
[plustek] Found device at >/dev/uscanner0<
[plustek] Vendor ID=0x04B8, Product ID=0x010F
[plustek] usbio_DetectLM983x
[plustek] usbio_DetectLM983x: found LM9832/3
[plustek] Detected vendor & product ID: 0x04B8-0x010F
[plustek] Device description for >0x04B8-0x010F< found.
[plustek] usb_initDev(32,0x04b8,-1)
[plustek] Device WAF: 0x00000002
[plustek] usb_switchLampX(ON=0,TPA=1)
[plustek] Switch Lamp: 0, regs[0x59] = 0x00
[plustek] REG[0x02] = 0x81
[plustek] TPA NOT detected
[plustek] Vendor adjusted to: >Epson<
[plustek] REG[0x5b] = 0x14 (msk=0x80)
[plustek] LAMP-STATUS: 0x00000000
[plustek] RESETTING REGISTERS(-1)
[plustek] SETTING THE MISC I/Os
[plustek] MISC I/O after RESET: 0x41, 0x44, 0x14
[plustek] Calibration file-name set to:
[plustek] >/root/.sane/Epson-Perfection_1250_Photo.cal<
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 8.000
[plustek] * XDPI=150, HDPI=8.000
[plustek] * YDPI=150, MinDPIY=150
[plustek] * DataPixelStart=69, LineEnd=69
[plustek] * DataPixelStart=70, LineEnd=70 (ADJ)
[plustek] >> End-Start=0, HDPI=8.00
[plustek] * Full Steps to Skip at Start = 0x0000
[plustek] * StepSize(Preset) = 231 (0x00e7)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 675, 0x46=0x02 0x47=0xa3
[plustek] * DPD =5568 (0x15c0)
[plustek] * DPD =5208 (0x1458), step size=675, steps2rev=30
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 0 (HDPI=8.000,MCLKD=4.000)
[plustek] * Setting GreenPWMDutyCycleLow
[plustek] * Current MCLK Divider = 4.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 260, [0x48] = 0x01, [0x49] = 0x04
[plustek] * PhyBytes   = 2
[plustek] * PhyLines   = 1296834662
[plustek] * TotalBytes = 2593669324
[plustek] * PL=295, coeffsize=216, scaler=1
[plustek] * PauseLimit = 295, [0x4e] = 0x91, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] usbDev_getCaps()
[plustek] Scanner information:
[plustek] Vendor : Epson
[plustek] Model  : Perfection 1250/Photo
[plustek] Flags  : 0x00000000
[plustek] drvclose()
[plustek] usbDev_stopScan()
[plustek] usbDev_ScanEnd(), start=0, park=0
[plustek] usbDev_close()
[plustek] attach: model = >Perfection 1250/Photo<
[plustek] sane_open - /dev/uscanner0
[plustek] Presetting Gamma tables (len=4096)
[plustek] * Channel[0], gamma 1.000
[plustek] * Channel[1], gamma 1.000
[plustek] * Channel[2], gamma 1.000
[plustek] * Channel[3], gamma 1.000
[plustek] ----------------------------------
[plustek] sane_start
[plustek] usbDev_open(/dev/uscanner0,)
[plustek] Vendor ID=0x04B8, Product ID=0x010F
[plustek] usbio_DetectLM983x
[plustek] usbio_DetectLM983x: found LM9832/3
[plustek] Detected vendor & product ID: 0x04B8-0x010F
[plustek] Device description for >0x04B8-0x010F< found.
[plustek] usb_initDev(32,0x04b8,32)
[plustek] Device WAF: 0x00000002
[plustek] Vendor adjusted to: >Epson<
[plustek] REG[0x5b] = 0x14 (msk=0x80)
[plustek] REG[0x59] = 0x41 (msk=0x08)
[plustek] LAMP-STATUS: 0x00000000
[plustek] RESETTING REGISTERS(32)
[plustek] USING MISC I/O settings
[plustek] MISC I/O after RESET: 0x41, 0x44, 0x14
[plustek] usbDev_getCaps()
[plustek] scanmode = 3
[plustek] usbDev_getCropInfo()
[plustek] usb_GetImageInfo()
[plustek] PPL = 590
[plustek] LPA = 590
[plustek] BPL = 1770
[plustek] brightness 0, contrast 0
[plustek] usbDev_setScanEnv()
[plustek] usb_SaveImageInfo()
[plustek] dwFlag = 0x00000400
[plustek] usb_GetImageInfo()
[plustek] * Preview Mode NOT set!
[plustek] Setting map[0] at 0x08061094
[plustek] Setting map[1] at 0x08065094
[plustek] Setting map[2] at 0x08069094
[plustek] usbDev_startScan()
[plustek] * HDPI: 8.000
[plustek] * XDPI=150, HDPI=8.000
[plustek] * YDPI=150, MinDPIY=150
[plustek] REG[0x5b] = 0x14 (msk=0x80)
[plustek] REG[0x59] = 0x41 (msk=0x08)
[plustek] LAMP-STATUS: 0x00000000
[plustek] Switching Lamp on
[plustek] usb_switchLampX(ON=0,TPA=1)
[plustek] Switch Lamp: 0, regs[0x59] = 0x41
[plustek] usb_switchLampX(ON=1,TPA=0)
[plustek] Switch Lamp: 1, regs[0x5b] = 0x94
[plustek] Warmup-Timer started
[plustek] REG[0x5b] = 0x94 (msk=0x80)
[plustek] REG[0x59] = 0x41 (msk=0x08)
[plustek] LAMP-STATUS: 0x00000001
[plustek] Lamp-Timer stopped
[plustek] dwflag = 0x40000400 dwBytesPerLine = 1770
[plustek] TIME START
[plustek] sane_start done
[plustek] reader_process started (forked)
[plustek] reader_process:starting to READ data (1044300 bytes)
[plustek] buf = 0x0886e000
[plustek] usbDev_PrepareScan()
[plustek] usb_DoCalibration()
[plustek] goto shading position
[plustek] ShadingOriginY=10
[plustek] MotorDPI=600, MaxMoveSpeed=0.800, FFStepSize=520, Steps=20
[plustek] MOTOR: PWM=0x02, PWM_DUTY=0x01 0x45=0x13 0x48=0x02, 0x49=0x08
[plustek] MCLK_FFW = 6 --> 0x0a
[plustek] shading position reached
[plustek] kEPSON adjustments
[plustek] SETMCLK[3/2], using entry 8: 6.000000, 1200
[plustek] No Plustek model: 150dpi
[plustek] SETMCLK[3/2], using entry 2: 2.000000, 150
[plustek] Settings done, so start...
[plustek] ###### ADJUST GAIN (COARSE)#######
[plustek] usb_AdjustGain()
[plustek] Coarse Calibration Strip:
[plustek] Lines    = 1
[plustek] Pixels   = 10200
[plustek] Bytes    = 61200
[plustek] Origin.X = 17
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 1.000
[plustek] * XDPI=1200, HDPI=1.000
[plustek] * YDPI=1200, MinDPIY=150
[plustek] * DataPixelStart=68, LineEnd=10268
[plustek] >> End-Start=10200, HDPI=1.00
[plustek] * Full Steps to Skip at Start = 0x0000
[plustek] * StepSize(Preset) = 462 (0x01ce)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 5406, 0x46=0x15 0x47=0x1e
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=5406, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 3 (HDPI=1.000,MCLKD=2.000)
[plustek] * Stepsize = 7208, 0x46=0x1c 0x47=0x28
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=7208, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] * Setting GreenPWMDutyCycleHigh
[plustek] * Current MCLK Divider = 2.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 173, [0x48] = 0x00, [0x49] = 0xad
[plustek] * PhyBytes   = 61202
[plustek] * PhyLines   = 1
[plustek] * TotalBytes = 61202
[plustek] * PL=260, coeffsize=192, scaler=1
[plustek] * PauseLimit = 60, [0x4e] = 0x1c, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] Warmup: Waiting 15 seconds
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(1)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 20 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 44 28 1c 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  00 00 00 01 01 01 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 1c 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 00 65 18 e1 02 06 a8 48  00 04 00 00 50 00 00 02
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] PhyBytes  = 61202
[plustek] PhyPixels = 10200
[plustek] Creating file 'coarse-gain-0.raw'
[plustek] > X=10200, Y=1, depth=16
[plustek] MAX(R,G,B)= 0x2935(10549), 0x23a5(9125), 0x268e(9870)
[plustek] MIN(R,G,B)= 0x000e(14), 0x0015(21), 0x030e(782)
[plustek] CUR(R,G,B)= 0x2935(10549), 0x23a5(9125), 0x268e(9870)
[plustek] REG[0x3b] = 47
[plustek] REG[0x3c] = 51
[plustek] REG[0x3d] = 48
[plustek] after tweaking:
[plustek] REG[0x3b] = 47
[plustek] REG[0x3c] = 51
[plustek] REG[0x3d] = 48
[plustek] red_lamp_on    = 16383
[plustek] red_lamp_off   = 0
[plustek] green_lamp_on  = 16383
[plustek] green_lamp_off = 0
[plustek] blue_lamp_on   = 16383
[plustek] blue_lamp_off  = 0
[plustek] usb_AdjustGain() done.
[plustek] ###### ADJUST OFFSET (COARSE) ####
[plustek] usb_AdjustOffset()
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 1.000
[plustek] * XDPI=1200, HDPI=1.000
[plustek] * YDPI=1200, MinDPIY=150
[plustek] * DataPixelStart=0, LineEnd=2550
[plustek] >> End-Start=2550, HDPI=1.00
[plustek] * Full Steps to Skip at Start = 0x0000
[plustek] * StepSize(Preset) = 462 (0x01ce)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 5406, 0x46=0x15 0x47=0x1e
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=5406, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 3 (HDPI=1.000,MCLKD=2.000)
[plustek] * Stepsize = 7208, 0x46=0x1c 0x47=0x28
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=7208, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] * Setting GreenPWMDutyCycleHigh
[plustek] * Current MCLK Divider = 2.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 173, [0x48] = 0x00, [0x49] = 0xad
[plustek] * PhyBytes   = 15302
[plustek] * PhyLines   = 1
[plustek] * TotalBytes = 15302
[plustek] * PL=305, coeffsize=192, scaler=1
[plustek] * PauseLimit = 15, [0x4e] = 0x05, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] S.dwPixels  = 2550
[plustek] dwPixels    = 66
[plustek] dwPhyBytes  = 15302
[plustek] dwPhyPixels = 2550
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(4)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 00 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 00 09 f6 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  00 00 00 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 05 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 50 60 28 5c 02 04 a8 48  00 04 00 00 50 00 00 02
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Creating file 'coarse-off-0.raw'
[plustek] > X=2550, Y=1, depth=16
[plustek] RedSum   = 327621, ave = 4963
[plustek] GreenSum = 430626, ave = 6524
[plustek] BlueSum  = 528886, ave = 8013
[plustek] RedExpect   = 0
[plustek] GreenExpect = 0
[plustek] BlueExpect  = 0
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(4)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 10 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 00 09 f6 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  30 30 30 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 05 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 60 60 18 60 32 46 a4 48  00 04 00 00 50 00 00 02
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Creating file 'coarse-off-1.raw'
[plustek] > X=2550, Y=1, depth=16
[plustek] RedSum   = 0, ave = 0
[plustek] GreenSum = 0, ave = 0
[plustek] BlueSum  = 0, ave = 0
[plustek] RedExpect   = 0
[plustek] GreenExpect = 0
[plustek] BlueExpect  = 0
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(4)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 10 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 00 09 f6 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  28 28 28 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 05 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 60 62 18 48 6e 06 00 48  00 04 00 00 70 00 00 06
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Creating file 'coarse-off-2.raw'
[plustek] > X=2550, Y=1, depth=16
[plustek] RedSum   = 15116, ave = 229
[plustek] GreenSum = 67860, ave = 1028
[plustek] BlueSum  = 201515, ave = 3053
[plustek] RedExpect   = 0
[plustek] GreenExpect = 0
[plustek] BlueExpect  = 40
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(4)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 00 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 00 09 f6 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  24 24 24 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 05 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 50 22 2a 30 68 04 00 80  00 04 00 00 90 00 00 08
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Creating file 'coarse-off-3.raw'
[plustek] > X=2550, Y=1, depth=16
[plustek] RedSum   = 162770, ave = 2466
[plustek] GreenSum = 247130, ave = 3744
[plustek] BlueSum  = 365514, ave = 5538
[plustek] RedExpect   = 0
[plustek] GreenExpect = 36
[plustek] BlueExpect  = 40
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(4)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 10 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 00 09 f6 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  22 22 26 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 05 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 60 65 18 87 62 06 40 48  00 04 00 00 10 00 00 04
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Creating file 'coarse-off-4.raw'
[plustek] > X=2550, Y=1, depth=16
[plustek] RedSum   = 245858, ave = 3725
[plustek] GreenSum = 329596, ave = 4993
[plustek] BlueSum  = 284178, ave = 4305
[plustek] RedExpect   = 34
[plustek] GreenExpect = 36
[plustek] BlueExpect  = 38
[plustek] REG[0x38] = 34
[plustek] REG[0x39] = 36
[plustek] REG[0x3a] = 38
[plustek] usb_AdjustOffset() done.
[plustek] ###### ADJUST DARK (FINE) ########
[plustek] usb_AdjustDarkShading()
[plustek] MCLK = 2.000000 (scanparam-MCLK=2.000000)
[plustek] usb_switchLampX(ON=0,TPA=0)
[plustek] Switch Lamp: 0, regs[0x5b] = 0x14
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 8.000
[plustek] * XDPI=150, HDPI=8.000
[plustek] * YDPI=1200, MinDPIY=150
[plustek] * DataPixelStart=641, LineEnd=5361
[plustek] * DataPixelStart=642, LineEnd=5362 (ADJ)
[plustek] >> End-Start=4720, HDPI=8.00
[plustek] * Full Steps to Skip at Start = 0x0000
[plustek] * StepSize(Preset) = 462 (0x01ce)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 5406, 0x46=0x15 0x47=0x1e
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=5406, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 0 (HDPI=8.000,MCLKD=2.000)
[plustek] * Setting GreenPWMDutyCycleHigh
[plustek] * Current MCLK Divider = 2.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 520, [0x48] = 0x02, [0x49] = 0x08
[plustek] * PhyBytes   = 3542
[plustek] * PhyLines   = 1
[plustek] * TotalBytes = 3542
[plustek] * PL=316, coeffsize=192, scaler=1
[plustek] * PauseLimit = 4, [0x4e] = 0x01, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(2)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 87 00 01 XX XX 03  02 26 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 00 00 01 00 00 00 00
[plustek] 0x20: 2a 06 02 82 14 f2 00 40  03 00 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  22 24 26 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 15 1e  02 08 00 00 00 00 01 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 14 00 00 00 00
[plustek] 0x60: 60 25 18 eb 32 46 28 80  00 04 00 00 d0 00 00 0e
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] usb_switchLampX(ON=1,TPA=0)
[plustek] Switch Lamp: 1, regs[0x5b] = 0x94
[plustek] Creating file 'fine-black.raw'
[plustek] > X=590, Y=1, depth=16
[plustek] Color[0] (Dark) : min=56352(0) max=56352(0) ave=56352
[plustek] 5%: 53534 (0), 59169 (0)
[plustek] Color[1] (Dark) : min=8994(0) max=8994(0) ave=8994
[plustek] 5%: 8544 (0), 9443 (0)
[plustek] Color[2] (Dark) : min=38436(0) max=38436(0) ave=38436
[plustek] 5%: 36514 (0), 40357 (0)
[plustek] ###### ADJUST WHITE (FINE) #######
[plustek] FINE WHITE Calibration Strip: fine-white.raw
[plustek] Shad.-Lines = 64
[plustek] Lines       = 64
[plustek] Pixels      = 590
[plustek] Bytes       = 3540
[plustek] Origin.X    = 143
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 8.000
[plustek] * XDPI=150, HDPI=8.000
[plustek] * YDPI=1200, MinDPIY=150
[plustek] * DataPixelStart=641, LineEnd=5361
[plustek] * DataPixelStart=642, LineEnd=5362 (ADJ)
[plustek] >> End-Start=4720, HDPI=8.00
[plustek] * Full Steps to Skip at Start = 0x0000
[plustek] * StepSize(Preset) = 462 (0x01ce)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 5406, 0x46=0x15 0x47=0x1e
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=5406, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 0 (HDPI=8.000,MCLKD=2.000)
[plustek] * Setting GreenPWMDutyCycleHigh
[plustek] * Current MCLK Divider = 2.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 520, [0x48] = 0x02, [0x49] = 0x08
[plustek] * PhyBytes   = 3542
[plustek] * PhyLines   = 64
[plustek] * TotalBytes = 226688
[plustek] * PL=316, coeffsize=192, scaler=1
[plustek] * PauseLimit = 222, [0x4e] = 0x6d, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(3)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 08 00 XX XX 03  02 26 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 00 00 01 00 00 00 00
[plustek] 0x20: 2a 06 02 82 14 f2 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  22 24 26 2f 33 30 00 00
[plustek] 0x40: 40 00 24 00 00 13 15 1e  02 08 00 00 00 00 6d 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 50 20 2b f3 32 44 a8 80  00 04 00 00 d0 00 00 00
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] TotalBytes = 226688
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] Creating file 'fine-white.raw'
[plustek] > X=590, Y=64, depth=16
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Color[0] (White) : min=81(155) max=65360(163) ave=35351
[plustek] 5%: 33583 (264), 37118 (299)
[plustek] Color[1] (White) : min=85(193) max=65107(84) ave=31459
[plustek] 5%: 29886 (291), 33031 (263)
[plustek] Color[2] (White) : min=82(500) max=65369(327) ave=32522
[plustek] 5%: 30895 (278), 34148 (278)
[plustek] MotorDPI=600, MaxMoveSpeed=0.800, FFStepSize=520, Steps=2
[plustek] MOTOR: PWM=0x02, PWM_DUTY=0x01 0x45=0x13 0x48=0x02, 0x49=0x08
[plustek] MCLK_FFW = 6 --> 0x0a
[plustek] MotorDPI=600, MaxMotorSpeed=0.900, FFStepSize=462
[plustek] MOTOR: PWM=0x02, PWM_DUTY=0x01 0x45=0x13 0x48=0x01, 0x49=0xce
[plustek] MCLK_FFW = 6 --> 0x0a
[plustek] Calibration done
[plustek] -----------------------
[plustek] Static Gain:
[plustek] REG[0x3b] = 47
[plustek] REG[0x3c] = 51
[plustek] REG[0x3d] = 48
[plustek] Static Offset:
[plustek] REG[0x38] = 34
[plustek] REG[0x39] = 36
[plustek] REG[0x3a] = 38
[plustek] -----------------------
[plustek] calibration done.
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 8.000
[plustek] * XDPI=150, HDPI=8.000
[plustek] * YDPI=150, MinDPIY=150
[plustek] * DataPixelStart=641, LineEnd=5361
[plustek] * DataPixelStart=642, LineEnd=5362 (ADJ)
[plustek] >> End-Start=4720, HDPI=8.00
[plustek] * Full Steps to Skip at Start = 0x0196
[plustek] * StepSize(Preset) = 462 (0x01ce)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 675, 0x46=0x02 0x47=0xa3
[plustek] * DPD =5568 (0x15c0)
[plustek] * DPD =5208 (0x1458), step size=675, steps2rev=30
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 0 (HDPI=8.000,MCLKD=2.000)
[plustek] * Setting GreenPWMDutyCycleHigh
[plustek] * Current MCLK Divider = 2.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 520, [0x48] = 0x02, [0x49] = 0x08
[plustek] * PhyBytes   = 1772
[plustek] * PhyLines   = 592
[plustek] * TotalBytes = 1049024
[plustek] * PL=294, coeffsize=216, scaler=1
[plustek] * PauseLimit = 294, [0x4e] = 0x91, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] ImageProc is: ColorDuplicate8
[plustek] usb_ScanBegin()
[plustek] usb_MapDownload()
[plustek] * brightness = 0 -> 0
[plustek] * contrast   = 0 -> 1.000
[plustek] * downloading map 0...
[plustek] * downloading map 1...
[plustek] * downloading map 2...
[plustek] usb_MapDownload() done.
[plustek] usb_DownloadShadingData(0)
[plustek] Downloading 590 pixels
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 06 09 00 XX XX 03  02 1e 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 00 00 01 00 00 00 00
[plustek] 0x20: 2a 06 02 82 14 f2 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  22 24 26 2f 33 30 00 00
[plustek] 0x40: 40 00 26 00 00 13 02 a3  02 08 01 96 00 00 91 01
[plustek] 0x50: 1e 0c 14 58 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 40 20 0c c7 32 44 26 48  00 04 00 00 b0 00 00 00
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] Creating file 'plustek-pic.raw'
[plustek] > X=590, Y=590, depth=8
[plustek] Reading the data now!
[plustek] PhyDpi.x         = 150
[plustek] PhyDpi.y         = 150
[plustek] UserDpi.x        = 150
[plustek] UserDpi.y        = 150
[plustek] NumberOfScanBufs = 2366
[plustek] LinesPerScanBufs = 4732
[plustek] dwPhyBytes       = 1772
[plustek] dwPhyPixels      = 590
[plustek] dwTotalBytes     = 1049024
[plustek] dwPixels         = 590
[plustek] dwBytes          = 1770
[plustek] dwValidPixels    = 590
[plustek] dwBytesScanBuf   = 3544
[plustek] dwLinesDiscard   = 2
[plustek] dwLinesToSkip    = 3
[plustek] dwLinesUser      = 590
[plustek] dwBytesLine      = 1770
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] drvclose()
[plustek] TIME END 1: 31s
[plustek] usbDev_stopScan()
[plustek] usbDev_ScanEnd(), start=1, park=1
[plustek] reader_process: finished reading data
[plustek] (SIG) Child is down (signal=20)
scanimage: received signal 2
scanimage: trying to stop scanner
[plustek] sane_cancel
[plustek] do_cancel
[plustek] >>>>>>>> killing reader_process <<<<<<<<
[plustek] reader_process killed
[plustek] drvclose()
[plustek] TIME END 1: 260s
[plustek] usbDev_stopScan()
[plustek] usbDev_ScanEnd(), start=1, park=1
[plustek] UIO error
[plustek] UIO error
[plustek] UIO error
[plustek] Lamp-Timer started (using ITIMER)
[plustek] usbDev_close()
[plustek] TIME END 2: 268s
scanimage: received signal 2
scanimage: aborting



From artpi@ptic.pl  Thu Oct 28 11:43:08 2004
From: artpi@ptic.pl (Artur Pierscinski)
Date: Thu, 28 Oct 2004 12:43:08 +0200
Subject: [sane-devel] genesys backend - warming up procedure
In-Reply-To: <200410271746.29865.gerhard@gjaeger.de>
References: <417FAA47.2010903@ptic.pl> <200410271746.29865.gerhard@gjaeger.de>
Message-ID: <4180CD3C.5090705@ptic.pl>

Gerhard Jaeger wrote:

>On Mittwoch 27 Oktober 2004 16:01, Artur Pierscinski wrote:
>  
>
>> <>
>> Hi,
>>
>> I've done some tests here with the ST24 and rewrote some parts of
>> the code, that the warmup and calibration stuff gets passed on it.
>> The major problem of the current genesys code is, that it is tied to
>> a UMAX device. All the settings specific to CCD and DAC (and motor)
>> are only valid for this scanner. This needs to be tweaked. I did this
>> here, but the code is not available so far ....
>>
>> Gerhard
>>
Thats is fine. May I help in something?
So there is almost no traffic in experimental cvs, so its like as no any 
progress.

So, the matter is I as expected---code is device (UMAX) expected; Your 
answer
clears my assumptions.

Artur Pierscinski


From whitemanor@netzero.net  Thu Oct 28 14:26:12 2004
From: whitemanor@netzero.net (Bensel)
Date: Thu, 28 Oct 2004 09:26:12 -0400
Subject: [sane-devel] Help with compiler error
Message-ID: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>

This is a multi-part message in MIME format.

------=_NextPart_000_0012_01C4BCD0.2A61F9E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

We are trying to get a Memorex MEM 48u scanner working with Linspire =
4.5.393.  It is suppose to work with the artec_eplus48u backend so we =
downloaded sane-backends-1.0.14.  When we run ./configure, we get the =
error: no acceptable C compiler found in $PATH.  We understand the ANSI =
C Compiler: GNU C (gcc) is recommended.  Could someone advise how we =
should proceed from here.  Thanks for your advice and help.

------=_NextPart_000_0012_01C4BCD0.2A61F9E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>We are trying to get a Memorex MEM 48u scanner =
working with=20
Linspire 4.5.393.&nbsp; It is suppose to work with the artec_eplus48u =
backend so=20
we downloaded sane-backends-1.0.14.&nbsp; When we run ./configure, we =
get the=20
error: no acceptable C compiler found in $PATH.&nbsp; We understand the =
ANSI C=20
Compiler: GNU C (gcc) is recommended.&nbsp; Could someone advise how we =
should=20
proceed from here.&nbsp; Thanks for your advice and=20
help.</FONT></DIV></BODY></HTML>

------=_NextPart_000_0012_01C4BCD0.2A61F9E0--



From anoah@pfeiffer.edu  Thu Oct 28 14:40:27 2004
From: anoah@pfeiffer.edu (m. allan noah)
Date: Thu, 28 Oct 2004 09:40:27 -0400 (EDT)
Subject: [sane-devel] Help with compiler error
In-Reply-To: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>
References: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>
Message-ID: <Pine.LNX.4.61.0410280938500.17000@limos.pfeiffer.edu>

umm, install a compiler package for your os? if you have one, and 
comfigure could not find it, then you either need to change your path. you 
might also need to see the CC= environment var if your compiler has a 
funny name.

allan

On Thu, 28 Oct 2004, Bensel wrote:

> We are trying to get a Memorex MEM 48u scanner working with Linspire 4.5.393.  It is suppose to work with the artec_eplus48u backend so we downloaded sane-backends-1.0.14.  When we run ./configure, we get the error: no acceptable C compiler found in $PATH.  We understand the ANSI C Compiler: GNU C (gcc) is recommended.  Could someone advise how we should proceed from here.  Thanks for your advice and help.
>

-- 
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera


From gerhard@gjaeger.de  Thu Oct 28 13:54:09 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Thu, 28 Oct 2004 14:54:09 +0200
Subject: [sane-devel] genesys backend - warming up procedure
In-Reply-To: <4180CD3C.5090705@ptic.pl>
References: <417FAA47.2010903@ptic.pl> <200410271746.29865.gerhard@gjaeger.de> <4180CD3C.5090705@ptic.pl>
Message-ID: <200410281454.09348.gerhard@gjaeger.de>

On Donnerstag 28 Oktober 2004 12:43, Artur Pierscinski wrote:
> Gerhard Jaeger wrote:
> >On Mittwoch 27 Oktober 2004 16:01, Artur Pierscinski wrote:
> >> <>
> >> Hi,
> >>
> >> I've done some tests here with the ST24 and rewrote some parts of
> >> the code, that the warmup and calibration stuff gets passed on it.
> >> The major problem of the current genesys code is, that it is tied to
> >> a UMAX device. All the settings specific to CCD and DAC (and motor)
> >> are only valid for this scanner. This needs to be tweaked. I did this
> >> here, but the code is not available so far ....
> >>
> >> Gerhard
>
> Thats is fine. May I help in something?
> So there is almost no traffic in experimental cvs, so its like as no any
> progress.

That's probably not true, I think Henning is still working on that.
I didn't want to check in my code, as there are too much changes, that
have not been discussed with Henning. Maybe I add a new directory

> So, the matter is I as expected---code is device (UMAX) expected; Your
> answer clears my assumptions.
--
  Gerhard



From gerard@gkall.hobby.nl  Thu Oct 28 17:02:45 2004
From: gerard@gkall.hobby.nl (gerard klaver)
Date: Thu, 28 Oct 2004 16:02:45 +0000
Subject: [sane-devel] Help with compiler error
In-Reply-To: <Pine.LNX.4.61.0410280938500.17000@limos.pfeiffer.edu>
References: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>
 <Pine.LNX.4.61.0410280938500.17000@limos.pfeiffer.edu>
Message-ID: <1098979365.4560.8.camel@gk-lex3>

check the linspire website and search for gcc

which version you should install?

their sane-backends (libsane) version is 1.0.12 ..... a bit old, don't
know if the support for your scanner is included.


On Thu, 2004-10-28 at 13:40, m. allan noah wrote:
> umm, install a compiler package for your os? if you have one, and 
> comfigure could not find it, then you either need to change your path. you 
> might also need to see the CC= environment var if your compiler has a 
> funny name.
> 
> allan
> 
> On Thu, 28 Oct 2004, Bensel wrote:
> 
> > We are trying to get a Memorex MEM 48u scanner working with Linspire 4.5.393.  It is suppose to work with the artec_eplus48u backend so we downloaded sane-backends-1.0.14.  When we run ./configure, we get the error: no acceptable C compiler found in $PATH.  We understand the ANSI C Compiler: GNU C (gcc) is recommended.  Could someone advise how we should proceed from here.  Thanks for your advice and help.
> >
> 


-- 
----------
m.vr.gr.
Gerard Klaver



From marc@electronics-design.nl  Thu Oct 28 16:24:24 2004
From: marc@electronics-design.nl (Marc Dirix)
Date: Thu, 28 Oct 2004 17:24:24 +0200
Subject: [sane-devel] Parallel Scanning and Printing
Message-ID: <20041028152424.GB26359@angus.electronics-design.nl>

I have an Canoscan N640P, which works fine with sane/xsane.
The interface is parallel, and on the scanner there is printer
throughput which also is working fine.

However, and I don't know if this should be solved in the backend
or in sane, when I use the copy mode of Xsane, or even if Xsane
is opened the printer doesn't work anymore. I need to close xsane 
and then te printjob starts. Probably xsane opens the backend and keeps 
the connecting live with the scanner while open.

I can think of 2 sollutions for this problem, either xsane let's go of the 
scanner when it isn't using the device, or the backend should detect 
a printjob is waiting and disconnect from the scanner.

Is there anyone else experiencing this problem? Is there already a sollution
for this? If not, which sollution is best, and where should I start looking?

versions:
sane  1.0.13-1 (Debian unstable)
xsane 0.96-1 (Debian unstable)

Kind regards,

Marc


From alej82@yahoo.es  Thu Oct 28 17:32:06 2004
From: alej82@yahoo.es (=?iso-8859-1?q?Alejandro=20Reche=20P=E9rez?=)
Date: Thu, 28 Oct 2004 18:32:06 +0200 (CEST)
Subject: [sane-devel] HP ScanJet 3670
Message-ID: <20041028163206.82423.qmail@web20925.mail.yahoo.com>

Hi,

we would like to make a driver for the Hewlett Packard
 ScanJet 3670 which is currently unsuported by sane.

So we would like to know where to find more
information than the one that can be found in the sane
site. Also if we can find the scanner especifications
somewhere or we have to ask them to HP.
Finally if there is anybdoy else also trying to do
this driver, please tell us.

Thanks in advance and sorry for our bad english.
Greetings.




		
______________________________________________
Renovamos el Correo Yahoo!: Ħ100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es


From gerard@gkall.hobby.nl  Thu Oct 28 20:07:02 2004
From: gerard@gkall.hobby.nl (gerard klaver)
Date: Thu, 28 Oct 2004 19:07:02 +0000
Subject: [sane-devel] HP ScanJet 3670
In-Reply-To: <20041028163206.82423.qmail@web20925.mail.yahoo.com>
References: <20041028163206.82423.qmail@web20925.mail.yahoo.com>
Message-ID: <1098990422.4560.17.camel@gk-lex3>

On Thu, 2004-10-28 at 16:32, Alejandro Reche P=E9rez wrote:
> Hi,
>=20
> we would like to make a driver for the Hewlett Packard
>  ScanJet 3670 which is currently unsuported by sane.
>=20
> So we would like to know where to find more
> information than the one that can be found in the sane
> site. Also if we can find the scanner especifications
> somewhere or we have to ask them to HP.
> Finally if there is anybdoy else also trying to do
> this driver, please tell us.
>=20
You mist some pages i think?

Did you check this page (with link to datasheet scanner chip):
http://www.meier-geinitz.de/sane/genesys-backend/

and links on this page?

http://www.sane-project.org/unsupported/hp-scanjet-3670c.html

and the files on

http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/experimental/genesys/?cvs=
root=3Dsane

But i could be wrong.

--=20
----------
m.vr.gr.
Gerard Klaver



From hvengel@astound.net  Wed Oct 27 21:04:00 2004
From: hvengel@astound.net (Hal V. Engel)
Date: Wed, 27 Oct 2004 13:04:00 -0700
Subject: [sane-devel] lprof and sane, was [Lcms-user] monitor profile questions -- adding vcgt to a profile?
In-Reply-To: <1098880586.2799.16.camel@gk-lex3>
References: <200410191019.i9JAJu1W025691@web218.megawebservers.com> <1098880586.2799.16.camel@gk-lex3>
Message-ID: <200410271304.08843.hvengel@astound.net>

--nextPart1390640.EdZTmjI0ub
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

In the sane-devel mailing list on 27 Jul, 2003 Gerard Klaver wrote (see=20
http://www.mostang.com/pipermail/sane-devel/2003-July/008334.html):

=C2=A8I think it (meaning lprof) should be nice if this package could be=20
used as a short of plugin package in the sane frontends. But maybe i=20
am wrong?=C2=A8

I think this is right on the money.  The lprof scanner profiler would=20
likely need some modification to make it a plugin but most of the=20
functionality would be usable as is.  In addition the front end(s)=20
would need to be enhanced to embed profiles and do conversions between=20
profiles. =20

I have two scanner packages that are ICC aware.  On Windows I have=20
SilverFast AI.  SilverFast AI will use the device profile to convert=20
the image to your selected working profile as part of the scanning=20
process.  It also has an optional feature that will let you create=20
custom profiles using an IT8 target.  I also have Vuescan Professional=20
on both Windows and Linux.  Vuescan Pro has the ability to use ICC=20
profiles and functions like SilverFast where you specify both a device=20
and working profile and your images are output having been converted=20
to the working profile.  Vuescan Pro can also create scanner profiles=20
using an IT8 target.  I believe that Vuescan uses the SANE back end on=20
linux.  So this functionality belongs in the front end.

Also scanners and cameras are almost trivial to profile.  All you need=20
is a good target, the targets data file and some software and almost=20
any user can get a good profile.  With a properly designed front end=20
it should be easy for almost any user to use this functionality.

Hal


On Wednesday 27 October 2004 05:36, gerard klaver wrote:
> On Tue, 2004-10-19 at 10:19, marti@littlecms.com wrote:
> > Hi,
> >=20
> > > >Are the reasons known? Just curious..
> >=20
> >=20
> > As Gerhard already noted, I am not allowed to support or maintain=20
> > the lprof package anymore. The reasons are the company I work=20
> > for (HP) acquired the sources for its internal use.=20
> >=20
> > Moreover, the technology I was using in the latest profilers (not=20
> > lprof, but what intended to sell as professional package) is=20
> > "sensible" in terms my non-disclosure agreement. So, I=20
> > sacrificed this package in order to keep lcms (the CMM) alive=20
> > and well.=20
> >=20
> > HP kindly allow me to continue the development of lcms as=20
> > open source and even more, they does SUPPORT this development.=20
> > In such way I have contact with ICC members, access to restricted=20
> > documents, proposed extensions, etc.
> >=20
> > So, I'm very sorry for that, but lprof is now effectively dead.=20
> > At least as open source. It would be nice, however, if anybody=20
> > would take the sources and continue with the development. But as=20
said,=20
> > I am not allowed to do that anymore.
> >=20
> > King regards,
> > Marti.
> >=20
> Hello,
>=20
> To keep the lprof package available i have placed the lprof files and
> other information from Marti old profilers page on my homepage.
> See http://gkall.hobby.nl/sane-lprof/sane-lprof.html
>=20
> Goal is to maintain the package as good as possible but time and/or
> knowledge can be a problem. Also if more people are interested in
> maintaining this package, let me know.
> Then maintenance depends not on a single person and placing it in the
> SANE CVS tree (sane-lprof or first sane/experimental/sane-lprof) is a
> good option. See als SANE Bugreport 30181.
> =20
> In this way more people are be able to use the package on more=20
platforms
> and there is a tracking system for the patches and changes.
>=20
> And if you have any remarks/comments/updates on/for this page, please
> let me know.
>=20
>=20
> --=20
> ----------
> m.vr.gr.
> Gerard Klaver
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=3D5588&alloc_id=3D12065&op=3Dclick
> _______________________________________________
> Lcms-user mailing list
> Lcms-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lcms-user
>=20

--nextPart1390640.EdZTmjI0ub
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iQIVAwUAQX//OMmrznPD2JtJAQKY0g/+MqmDsHfAANjGfZ3MVdvrfmoCHc3IrYYf
dv/Xu5d8m1VMhU6kEdgrshcFAEs5nwKKtBtJvaDaTAr/mnZ55MGrKWzEGWZHSGyi
vMaWv6SbPPzpmmdI45rm21c9ACIpnTsacUPgMbIveg3wn2y+ZYGwC2W0MLoB5Bdt
AntycXzA2pbObNVZ1RapyvDdmYUkb1Kp+rF/5qt6ida4qdGF1KPDoBkHUIwgZxpx
ulone3q7YL8vv4yAfB2uavL3o+keFMGQcQzyPgyNBD1z0MFMrhAIWvesJtymDllM
vbEk9FwWqxLa++SMryIGsUXiWsYFz090XyLJYM8Nm0AXHSgW41vmwS6n/VhNeqr6
MUYrmOTcO+0nD4HNzjIPRrTzoPK49BQZXtgGXdb5h6+gUmUyh7KQtH9aKOjNjaOT
peZ5gj4tpdJVJh80U4uNwC50v+JwAY1o7hKdvEJ/m71x6Dj1neNERYlLbH8n4R4/
ZRbTMQefNvdPKgchippaff1ACiWm2v3VEPPpplWOJdaYPhN9Gtz6JE9pomTKgfCk
fIl/6586sc1BwzQDtbRLCwIVMAUPOG6W5b9Ua+aMI6IXljQUOuQAa7K6Ey8gh928
FyH0glUTXL+RpExZd14k7oDuSPxUhJxLKZ/ZxGWB+xPQACGIO5DQEkjtDKruHHew
i3+xwzBrdeE=
=O7PH
-----END PGP SIGNATURE-----

--nextPart1390640.EdZTmjI0ub--


From PaulR.Cormier  Thu Oct 28 15:15:34 2004
From: PaulR.Cormier (PaulR.Cormier)
Date: Thu, 28 Oct 2004 10:15:34 -0400
Subject: [sane-devel] Help with compiler error
In-Reply-To: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>
References: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>
Message-ID: <20041028101534.3abb0e8d.prcormier@adelphia.net>

On Thu, 28 Oct 2004 09:26:12 -0400
"Bensel" <whitemanor@netzero.net> wrote:

> We are trying to get a Memorex MEM 48u scanner working with Linspire 4.5.393.  It is suppose to work with the artec_eplus48u backend so we downloaded sane-backends-1.0.14.  When we run ./configure, we get the error: no acceptable C compiler found in $PATH.  We understand the ANSI C Compiler: GNU C (gcc) is recommended.  Could someone advise how we should proceed from here.  Thanks for your advice and help.
> 

If you have access to Linspire's Click-N-Run library, you can get the compilers and other tools there.
If not, you might try using the Debian Package tools (Linspire is based on the Debian distribution).

-- 
Best regards,

Paul R. Cormier
prcormier@adelphia.net



From henning@meier-geinitz.de  Thu Oct 28 19:48:16 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 28 Oct 2004 20:48:16 +0200
Subject: [sane-devel] genesys backend - warming up procedure
In-Reply-To: <200410281454.09348.gerhard@gjaeger.de>
References: <417FAA47.2010903@ptic.pl> <200410271746.29865.gerhard@gjaeger.de> <4180CD3C.5090705@ptic.pl> <200410281454.09348.gerhard@gjaeger.de>
Message-ID: <20041028184816.GA4740@meier-geinitz.de>

Hi,

On Thu, Oct 28, 2004 at 02:54:09PM +0200, Gerhard Jaeger wrote:
> That's probably not true, I think Henning is still working on that.
> I didn't want to check in my code, as there are too much changes, that
> have not been discussed with Henning. Maybe I add a new directory

At the moment I don't have enough time to work on that code. All my
local changes are in CVS. The last thing I did was to start a debug
print of all the registers so it's easier to find out what's actually
wrong. It's not complete yet, however. That debug printout is based on
the GL646 docu, so it should fit all scanners based on that chip.

So I don't mind if someone goes ahead and works on that code. It needs
generalization anyway. Most chipset settings are at least somewhat
commented so it should be possible to put the device specific values
in the device settings of each device.

If by a commit snathingy breaks for the UMAX 4500 (breaks more than it
already is :-) I'll try to fix it.

Status for the UMAX 4500: Works upto the start of fine claibration,
fine calibration times out (waits for too much data, maybe?). Coarse
calibration goes wrong, also. It actually scans data but the setting
gets worse with each calibration step.

Bye,
  Henning


From ulrick2@faith4miracle.org  Fri Oct 29 06:39:16 2004
From: ulrick2@faith4miracle.org (Steven P. Ulrick)
Date: Fri, 29 Oct 2004 00:39:16 -0500
Subject: [sane-devel] Problem scanning with Kooka/Epson Perfection 2400
Message-ID: <200410290039.16664.ulrick2@faith4miracle.org>

Hello, Everyone
I am having a problem scanning with our Epson Perfection 2400 scanner. =A0I=
=20
don't know for sure if this is a KDE issue or not.  But I figured that sinc=
e=20
the Scanner Guru's are here, that at the very least you could tell me if th=
is=20
is a problem with SANE or not.

This problem only occurs when I use Kooka (doesn't matter whether it's the=
=20
version that ships with Fedora Core 2, or the one on CVS HEAD.) =A0I tried=
=20
scanning an image earlier using xsane, and it worked just fine.
Here is a link to an image that I Just scanned (using "xsane", to show that=
=20
the scanner works just fine:
http://www.faith4miracle.org/kooka/JoeyRamone.jpg

When I start any version of Kooka (for this experiment, I will start Kooka=
=20
while su'd into root. =A0This is what the GUI looks like:
http://www.faith4miracle.org/kooka/kooka-1.jpg

Then I proceed to do a "Preview Scan" =A0This is what the GUI looks like th=
en:
http://www.faith4miracle.org/kooka/kooka-2.jpg

If I try to do a "Final Scan", this is what the GUI looks like:
http://www.faith4miracle.org/kooka/kooka-3.jpg

You will notice that these are identical screen shots. =A0This is because=20
whether I choose "Preview Scan" or "Final Scan", nothing appears to be=20
scanned.

The only configuration file I could find was in "~/.kde/share/config" =A0I =
tried=20
deleting that and retrying what I described above, to no avail.

At the following location, you will find a tarball of the terminal window=20
outputs that I got when I tried a Preview and a Final scan. =A0In the same=
=20
tarball, you will find straces of attempts at Preview and Final scans.
http://www.faith4miracle.org/kooka/kooka-logs.tar.bz2

Root is the group and user of /proc/bus/usb/001/013
Also, root does have read, write and execute permissions on this device.
One thing I just thought of: I can't remember for sure, but should I have=20
a /dev/scanner? =A0I can't remember if I had one in the past, or if that is=
=20
relevant with a USB scanner. =A0All I know is that I don't have one now.

Operating System: Fedora Core 2, All Packages installed, All official Updat=
es=20
installed (Except the kernel)
QT: 3.3.3 from TrollTech source tarball
KDE: CVS HEAD

QT and KDE paths are both exported in my ~/.bash_profile. =A0I did not over=
write=20
the FC2 default KDE.

In closing, this same scanner, using Kooka from the CVS HEAD version of KDE=
,=20
used to work perfectly, never giving me a moment of trouble. =A0Like I stat=
ed=20
earlier, and proved with an example for your viewing, this same scanner tha=
t=20
does not work with kooka, does work just fine with xsane.

I will be glad to answer any questions that this problem might require.

Have a Great Day
Steven P. Ulrick
=2D-=20
 00:36:39 up 16 days, 10:06, 45 users,  load average: 0.34, 0.33, 0.67


From olaf@epkowa.co.jp  Fri Oct 29 09:29:23 2004
From: olaf@epkowa.co.jp (Olaf Meeuwissen)
Date: Fri, 29 Oct 2004 17:29:23 +0900
Subject: [sane-devel] Problem scanning with Kooka/Epson Perfection 2400
In-Reply-To: <200410290039.16664.ulrick2@faith4miracle.org> (Steven P.
 Ulrick's message of "Fri, 29 Oct 2004 00:39:16 -0500")
References: <200410290039.16664.ulrick2@faith4miracle.org>
Message-ID: <87is8uhqqk.fsf@zen.epkowa.co.jp>

"Steven P. Ulrick" <ulrick2@faith4miracle.org> writes:

> Hello, Everyone
> I am having a problem scanning with our Epson Perfection 2400 scanner. =
=C2=A0I=20
> don't know for sure if this is a KDE issue or not.  But I figured that si=
nce=20
> the Scanner Guru's are here, that at the very least you could tell me if =
this=20
> is a problem with SANE or not.
> [...]
> In closing, this same scanner, using Kooka from the CVS HEAD version of K=
DE,=20
> used to work perfectly, never giving me a moment of trouble. =C2=A0Like I=
 stated=20
> earlier, and proved with an example for your viewing, this same scanner t=
hat=20
> does not work with kooka, does work just fine with xsane.

It's not a SANE problem if everything works just fine with xsane.
Both xsane and kooka communicate with your scanner with the same
mechanism.  Something in kooka is screwing around with the scanner
data.

Check what has changed in CVS since your last working version of
kooka.
--=20
Olaf Meeuwissen                            EPSON KOWA Corporation, PF1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2


From artpi@ptic.pl  Fri Oct 29 11:43:39 2004
From: artpi@ptic.pl (Artur Pierscinski)
Date: Fri, 29 Oct 2004 12:43:39 +0200
Subject: [sane-devel] genesys backend - warming up procedure
In-Reply-To: <200410281454.09348.gerhard@gjaeger.de>
References: <417FAA47.2010903@ptic.pl> <200410271746.29865.gerhard@gjaeger.de> <4180CD3C.5090705@ptic.pl> <200410281454.09348.gerhard@gjaeger.de>
Message-ID: <41821EDB.60204@ptic.pl>

Gerhard Jaeger wrote:

>On Donnerstag 28 Oktober 2004 12:43, Artur Pierscinski wrote:
>  
>
>>Gerhard Jaeger wrote:
>>    
>>
>>>On Mittwoch 27 Oktober 2004 16:01, Artur Pierscinski wrote:
>>>      
>>>
>>>><>
>>>>Hi,
>>>>
>>>>I've done some tests here with the ST24 and rewrote some parts of
>>>>the code, that the warmup and calibration stuff gets passed on it.
>>>>The major problem of the current genesys code is, that it is tied to
>>>>a UMAX device. All the settings specific to CCD and DAC (and motor)
>>>>are only valid for this scanner. This needs to be tweaked. I did this
>>>>here, but the code is not available so far ....
>>>>
>>>>Gerhard
>>>>        
>>>>
>>Thats is fine. May I help in something?
>>So there is almost no traffic in experimental cvs, so its like as no any
>>progress.
>>    
>>
>
>That's probably not true, I think Henning is still working on that.
>I didn't want to check in my code, as there are too much changes, that
>have not been discussed with Henning. Maybe I add a new directory
>  
>
Henning, as he wrote in other post, have not enough time to work on that 
code.

That seems, as exists some independent from each other code, which try 
to solve genesys devices to work.

Artur Pierscinski
e-mail: artpi@ptic.pl



From john@jcoppens.com  Fri Oct 29 15:52:50 2004
From: john@jcoppens.com (John Coppens)
Date: Fri, 29 Oct 2004 11:52:50 -0300
Subject: [sane-devel] Strange file save problem
Message-ID: <20041029115250.5c5cf8cf.john@jcoppens.com>

Hi all.

At a friendly non-profit foundation, I installed Xsane/Sane quite a while
ago. I installed it as saned, so that I can access it from another (WinXP)
machine too, but the problems below are on the local (linux) machine.

Just to be sure I installed the latest versions of sane-backends
(1.0.14?) and Xsane (.96).

1) I still get erratic 'argument error' messages when trying to change
from, eg., binary to gray or to color modes. After a while, for some
reason, the command gets accepted... I reported this problem a long time
ago, but never really got it solved.

2) When saving a file from the viewer in some directories, I get a message
like:

Could not create secure file (may be a link does exist):

In other directories, there is no problem. I checked the priviledges of
the directories and the owners - they're the same. I found a few
references in the mailing list, but no real solution... In the failing
directory no file is present of the same name. It's not part of a project
either - just saving a scanned document.

Thanks in advance.
John


From henning@meier-geinitz.de  Fri Oct 29 16:38:53 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 29 Oct 2004 17:38:53 +0200
Subject: [sane-devel] Strange file save problem
In-Reply-To: <20041029115250.5c5cf8cf.john@jcoppens.com>
References: <20041029115250.5c5cf8cf.john@jcoppens.com>
Message-ID: <20041029153853.GA11940@meier-geinitz.de>

Hi,

On Fri, Oct 29, 2004 at 11:52:50AM -0300, John Coppens wrote:
> At a friendly non-profit foundation, I installed Xsane/Sane quite a while
> ago. I installed it as saned, so that I can access it from another (WinXP)
> machine too, but the problems below are on the local (linux) machine.
> 
> Just to be sure I installed the latest versions of sane-backends
> (1.0.14?) and Xsane (.96).
> 
> 1) I still get erratic 'argument error' messages when trying to change
> from, eg., binary to gray or to color modes. After a while, for some
> reason, the command gets accepted... I reported this problem a long time
> ago, but never really got it solved.

I rember that problem but unfortunately nobody could really reproduce
it as far as I know and such kind of network problems are quite
impossible to debug without reproducing them.

But the problem only happens over the (localhost) network?

Bye,
  Henning


From john@jcoppens.com  Sat Oct 30 05:19:22 2004
From: john@jcoppens.com (John Coppens)
Date: Sat, 30 Oct 2004 01:19:22 -0300
Subject: [sane-devel] Strange file save problem
In-Reply-To: <20041029153853.GA11940@meier-geinitz.de>
References: <20041029115250.5c5cf8cf.john@jcoppens.com>
 <20041029153853.GA11940@meier-geinitz.de>
Message-ID: <20041030011922.67769fe0.john@jcoppens.com>

On Fri, 29 Oct 2004 17:38:53 +0200
Henning Meier-Geinitz <henning@meier-geinitz.de> wrote:

> Hi,
> 
> On Fri, Oct 29, 2004 at 11:52:50AM -0300, John Coppens wrote:
> > At a friendly non-profit foundation, I installed Xsane/Sane quite a
> > while ago. I installed it as saned, so that I can access it from
> > another (WinXP) machine too, but the problems below are on the local
> > (linux) machine.
> > 
> > Just to be sure I installed the latest versions of sane-backends
> > (1.0.14?) and Xsane (.96).
> > 
> > 1) I still get erratic 'argument error' messages when trying to change
> > from, eg., binary to gray or to color modes. After a while, for some
> > reason, the command gets accepted... I reported this problem a long
> > time ago, but never really got it solved.
> 
> I rember that problem but unfortunately nobody could really reproduce
> it as far as I know and such kind of network problems are quite
> impossible to debug without reproducing them.
> 
> But the problem only happens over the (localhost) network?

  I didn't try this time around, after updating. I'll do so tomorrow. I
seem to recall the problem also exists from the XP end.

  Any suggestions on the 'secure' file problem?

  Thanks,

  John

> 
> Bye,
>   Henning
> 
> -- 
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request@lists.alioth.debian.org


From Oliver.Rauch@Rauch-Domain.DE  Sat Oct 30 08:37:26 2004
From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch)
Date: 30 Oct 2004 09:37:26 +0200
Subject: [sane-devel] Strange file save problem
In-Reply-To: <20041030011922.67769fe0.john@jcoppens.com>
References: <20041029115250.5c5cf8cf.john@jcoppens.com>
 <20041029153853.GA11940@meier-geinitz.de>
 <20041030011922.67769fe0.john@jcoppens.com>
Message-ID: <1099121846.2131.2.camel@Babylon7>

Am Sam, 2004-10-30 um 06.19 schrieb John Coppens:

>   Any suggestions on the 'secure' file problem?

When this happens on the linux machine then please do:

export XSANE_DEBUG=12
xsane 2>debug.txt

and make taht the problem occurs, then close xsane

gzip debug.txt

and send debug.txt.gz to me.
Oliver



From henning@meier-geinitz.de  Sat Oct 30 12:23:51 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 30 Oct 2004 13:23:51 +0200
Subject: [sane-devel] Strange file save problem
In-Reply-To: <20041030011922.67769fe0.john@jcoppens.com>
References: <20041029115250.5c5cf8cf.john@jcoppens.com> <20041029153853.GA11940@meier-geinitz.de> <20041030011922.67769fe0.john@jcoppens.com>
Message-ID: <20041030112351.GA9541@meier-geinitz.de>

Hi,

On Sat, Oct 30, 2004 at 01:19:22AM -0300, John Coppens wrote:
>   I didn't try this time around, after updating. I'll do so tomorrow. I
> seem to recall the problem also exists from the XP end.

What I meant to ask was if it only happens over saned, i.e. does scanning
without saned always work?

Bye,
  Henning


From henning@meier-geinitz.de  Sat Oct 30 17:17:58 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 30 Oct 2004 18:17:58 +0200
Subject: [sane-devel] update net.tex for sane1 documentation
In-Reply-To: <1098123627.5219.23.camel@johannes>
References: <1098123627.5219.23.camel@johannes>
Message-ID: <20041030161758.GG9541@meier-geinitz.de>

Hi,

On Mon, Oct 18, 2004 at 08:20:26PM +0200, Johannes Berg wrote:
> +The data transferred from the client to the server is compromised of

I guess you mean "comprised"?

> +the RPC code (as a \code{SANE\_WORD}), followed by the arguments in the
> +order listed. The server reply consists only of the data given below.

I'd also mention that the data sent to the server is the "request".

I guess we can add that to the sane 1 standard after the release.

Bye,
  Henning


From henning@meier-geinitz.de  Sat Oct 30 17:07:31 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 30 Oct 2004 18:07:31 +0200
Subject: [sane-devel] saned array memory limit
In-Reply-To: <87pt3k3geh.fsf@zen.epkowa.co.jp>
References: <20041014172115.GE12141@meier-geinitz.de> <87oej5qgea.fsf@frigate.technologeek.org> <20041014185842.GG12141@meier-geinitz.de> <87fz4hqbii.fsf@frigate.technologeek.org> <87pt3k3geh.fsf@zen.epkowa.co.jp>
Message-ID: <20041030160731.GF9541@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 10:43:18AM +0900, Olaf Meeuwissen wrote:
> Hmm, iscan still uses the build infra-structure (Makefile.in etc) from
> sane-backends, but in my free time I've switched it over to use
> automake (and I'm trying to get it included in our official releases).
> 
> Maybe, just maybe, I could see if generalising to multiple backends is
> feasible.  Let me know if you're interested.

Yes, I am. If that's feasable, it would really make development of
multi-file backends easier. I really hate to always do "touch
backend/gt68xx.c" after a change in one of those other gt68xx files.

I'm rather clueless about automake and/or depend files so if anyone
has more experience with this topic please go ahead and tell us what
the easiest solution is.

> BTW, I'll also try to update epkowa.desc before sane-backends-1.0.15
> comes out.

That would be good. On the other hand that file can be changed at any
time as the external backends list is updated immediately and not only
at releases.

Bye,
  henning


From herbr@pfinders.com  Sat Oct 30 17:24:36 2004
From: herbr@pfinders.com (Herb Rubin)
Date: Sat, 30 Oct 2004 09:24:36 -0700
Subject: [sane-devel] Visionshape support?
Message-ID: <1099153476.20930.4.camel@fred.sf.pfinders.com>

Is this supported at all? Visionshape Millenium DS-50/75 that can
scan over 60 pages per minute?

http://www.visionshape.com/millennium.html

It says it has USB and SCSI interface.

Herb




From johannes@sipsolutions.net  Sat Oct 30 18:17:45 2004
From: johannes@sipsolutions.net (Johannes Berg)
Date: Sat, 30 Oct 2004 19:17:45 +0200
Subject: [sane-devel] update net.tex for sane1 documentation
In-Reply-To: <20041030161758.GG9541@meier-geinitz.de>
References: <1098123627.5219.23.camel@johannes>
 <20041030161758.GG9541@meier-geinitz.de>
Message-ID: <1099156665.4294.4.camel@johannes.sipsolutions.net>

--=-OWWnRAB/Oj8PK0vnha34
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2004-10-30 at 18:17 +0200, Henning Meier-Geinitz wrote:
> > +The data transferred from the client to the server is compromised of
>=20
> I guess you mean "comprised"?

Um, yes :)

johannes

--=-OWWnRAB/Oj8PK0vnha34
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (SIP Solutions)

iQIVAwUAQYPMtqVg1VMiehFYAQJp2hAAq1FMhzo8V3gbvPhRIk3NWTdlPgCImW2D
jny2NEusFeBFCMn8S7nh5ku6nUlTm/YEZkDpqXK8oHLTOeMLmZmWETaUU92+9PDS
R346VonCwrEE+WC9YvPEkC1n48wOURYhg02WAH2zo2rY9hKuSZojAFwjPm7vwhcS
f83z6rSQin0jsww/HA5mP+vxvWUBLOs/RGbR0IojAG6w9EnqWfdvQ9QQbLOXy1+c
RnMMK2z+3tKiS3gh+OGgUnjYj+typsn7hAf6HnuhxsWkI0s2TA6OCYxexCceKeJh
6/84XsXhQ50Q3aBw7/qP4Q3TQccT7U51fQHF/jlTECVxeTFomwvp4nuinp5Ztf8w
6sSwbfFjA735PA4bAXbsyDgi+CzBe6IBawddfypKgpmhJpAN501HourI+ciRvhkg
FT98hIh2q4IopRHMMEq7TQTto7U83K04FrlO76FMrElatSz4SmMmNPYFetPdVDiB
t3OvnTpNBdJpl08JSfJLzz2XSa62tlvIVX9CiiqunStwqVHfhy+ZYZbVyluYeE40
E0BjBGFuCLb51Tyk+fqmkm8szRwwpy29B8/iR7RcOMoiO4TAo6Gae7Wc6AmL5+tW
cg/MYC60LPMPetjKdHIc5IzcvWFs5uQecbQDT3IkGLNl5nm9crA+kRjeGi38QCYQ
NXtd/dhdz00=
=EYkj
-----END PGP SIGNATURE-----

--=-OWWnRAB/Oj8PK0vnha34--




From henning@meier-geinitz.de  Sat Oct 30 17:32:08 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 30 Oct 2004 18:32:08 +0200
Subject: [sane-devel] Epson 1250 scanner does not return back after scanning
In-Reply-To: <013E3129-28C2-11D9-9806-000393775A6A@gnome.sk>
References: <1098908428026_29625227@aladarko.gnome.sk> <200410280919.56899.gerhard@gjaeger.de> <013E3129-28C2-11D9-9806-000393775A6A@gnome.sk>
Message-ID: <20041030163207.GI9541@meier-geinitz.de>

Hi,

On Thu, Oct 28, 2004 at 11:16:09AM +0200, Martin Motovsky wrote:
> [plustek] drvclose()
> [plustek] TIME END 1: 31s
> [plustek] usbDev_stopScan()
> [plustek] usbDev_ScanEnd(), start=1, park=1
> [plustek] reader_process: finished reading data
> [plustek] (SIG) Child is down (signal=20)
> scanimage: received signal 2
> scanimage: trying to stop scanner
> [plustek] sane_cancel

Looks like SIGCHILD called the plustek signal handler. However, also
the scanimage signal handler was called. What is sig 2 and sig 20 on
FreeBSD?

scanimage calls sane_cancel() in its own signal handler.

Bye,
  Henning


From henning@meier-geinitz.de  Sat Oct 30 17:22:18 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 30 Oct 2004 18:22:18 +0200
Subject: [sane-devel] homepage for "artiscan 9600" scanner
In-Reply-To: <1098343951.968.10.camel@vicious>
References: <1098343951.968.10.camel@vicious>
Message-ID: <20041030162218.GH9541@meier-geinitz.de>

Hi,

On Thu, Oct 21, 2004 at 09:32:31AM +0200, Enrico Boldrini wrote:
> Theese are two models of the scanner. The scanner we'll try to support
> first will be Tamarack Artiscan 9600 pro 36.
> 
> I use this message also to inform that:
> /!\ The project is moved to http://www.autistici.org/tamarhack /1\

Thanks. I'll update the links.

Bye,
  Henning


From jb@jblache.org  Sun Oct 31 10:42:46 2004
From: jb@jblache.org (Julien BLACHE)
Date: Sun, 31 Oct 2004 11:42:46 +0100
Subject: [sane-devel] Makefile.in : libsane.la should use $(libdir) instead of
 $(libsanedir)
Message-ID: <87fz3v4195.fsf@frigate.technologeek.org>

Hi,

>From Makefile.in :

libsane.la: dll.lo dll-s.lo $(EXTRA) $(addsuffix .lo,$(DLL_PRELOAD)) $(LIBOBJS) 
        @$(LIBTOOL) $(MLINK) $(CC) -o $@ $(LDFLAGS) $(BACKENDLIBS)  $^ \ 
                $(addsuffix .lo,$(DLL_PRELOAD_EXTRAS)) @LIBTOOL_LINK_EXTRA@ \ 
                -rpath $(libsanedir) -version-info $(V_MAJOR):$(V_REV):$(V_MINOR) 
                       ^^^^^^^^^^^^^

This causes libsane.la to contain /usr/lib/sane as its libdir,
although libsane.so is installed into /usr/lib.

libtool will then complain that libsane.la got moved, and will fail to
link any dependent library (itself using libtool).

$(libsanedir) should be changed to $(libdir) in the above; Henning,
can this go in for 1.0.15 ?

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb@jblache.org>                                  GPG KeyID 0xF5D65169


From jb@jblache.org  Sun Oct 31 16:52:03 2004
From: jb@jblache.org (Julien BLACHE)
Date: Sun, 31 Oct 2004 17:52:03 +0100
Subject: [sane-devel] Makefile.in : libsane.la should use $(libdir)
 instead of $(libsanedir)
In-Reply-To: <87fz3v4195.fsf@frigate.technologeek.org> (Julien BLACHE's
 message of "Sun, 31 Oct 2004 11:42:46 +0100")
References: <87fz3v4195.fsf@frigate.technologeek.org>
Message-ID: <87brei4yq4.fsf@frigate.technologeek.org>

Julien BLACHE <jb@jblache.org> wrote:

> libsane.la: dll.lo dll-s.lo $(EXTRA) $(addsuffix .lo,$(DLL_PRELOAD)) $(LIBOBJS) 
>         @$(LIBTOOL) $(MLINK) $(CC) -o $@ $(LDFLAGS) $(BACKENDLIBS)  $^ \ 
>                 $(addsuffix .lo,$(DLL_PRELOAD_EXTRAS)) @LIBTOOL_LINK_EXTRA@ \ 
>                 -rpath $(libsanedir) -version-info $(V_MAJOR):$(V_REV):$(V_MINOR) 
>                        ^^^^^^^^^^^^^

Actually, this comes from one of my patches, and isn't in the vanilla
sane-backends sources.

Looks like a copy&paste error, as I can't remember doing any changes
to that part of the Makefile.

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb@jblache.org>                                  GPG KeyID 0xF5D65169


From jb@jblache.org  Sun Oct 31 18:00:35 2004
From: jb@jblache.org (Julien BLACHE)
Date: Sun, 31 Oct 2004 19:00:35 +0100
Subject: Source dependency tracking (was: Re: [sane-devel] saned array
 memory limit)
In-Reply-To: <20041030160731.GF9541@meier-geinitz.de> (Henning
 Meier-Geinitz's message of "Sat, 30 Oct 2004 18:07:31 +0200")
References: <20041014172115.GE12141@meier-geinitz.de>
 <87oej5qgea.fsf@frigate.technologeek.org>
 <20041014185842.GG12141@meier-geinitz.de>
 <87fz4hqbii.fsf@frigate.technologeek.org>
 <87pt3k3geh.fsf@zen.epkowa.co.jp>
 <20041030160731.GF9541@meier-geinitz.de>
Message-ID: <877jp64vjw.fsf_-_@frigate.technologeek.org>

--=-=-=

Henning Meier-Geinitz <henning@meier-geinitz.de> wrote:

Hi,

> I'm rather clueless about automake and/or depend files so if anyone
> has more experience with this topic please go ahead and tell us what
> the easiest solution is.

Here's a proposed solution... It uses makedepend (from XFree86, in the
xutils package for Debian users) to generate backend/.depend.

The depend rule could be made a noop if makedepend isn't found or by a
configure switch (could be disabled in releases by default, and
reenabled by a configure switch).

The makedepend run takes less than a second on my workstation.

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb@jblache.org>                                  GPG KeyID 0xF5D65169


--=-=-=
Content-Type: text/x-patch
Content-Disposition: attachment;
  filename=sane-backends_makedepend.patch
Content-Description: Add a working depend rule to backend/Makefile.in and use it

--- Makefile.in.orig	2004-10-31 18:51:24.155645568 +0100
+++ Makefile.in	2004-10-31 18:52:33.919039920 +0100
@@ -174,7 +174,7 @@
 # Don't delete any intermediate files.
 .PRECIOUS: %-s.c %-s.lo %.lo dll-preload.c
 
-all:	$(LIBS) libsane.la
+all:	depend $(LIBS) libsane.la
 
 install:
 	$(MKDIR) $(DESTDIR)$(libdir) $(DESTDIR)$(libsanedir) $(DESTDIR)$(configdir)
@@ -461,10 +461,12 @@
 
 
 depend:
-	makedepend $(INCLUDES) *.c
+	@echo "Regenerating source tree dependencies ..."
+	@echo "# DO NOT DELETE THIS LINE -- make depend depends on it." > .depend
+	@makedepend -f .depend -o.lo $(INCLUDES) -- $(CFLAGS) $(CPPFLAGS) $(DEFS) -- *.c 2> /dev/null
 
 clean:
-	rm -f *.lo *.o *.la libsane.la dll-preload.c
+	rm -f *.lo *.o *.la libsane.la dll-preload.c .depend
 	find . -type l -name \*-s.c | xargs rm -f
 	rm -rf .libs
 
@@ -477,3 +479,6 @@
 	  ln $$file $(distdir)/backend 2> /dev/null \
 	    || cp -p $$file $(distdir)/backend ; \
 	done
+
+# Include dependency information
+-include .depend

--=-=-=--


From henning@meier-geinitz.de  Sun Oct 31 19:17:37 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 31 Oct 2004 20:17:37 +0100
Subject: [sane-devel] Code freeze for sane-backends 1.0.15
Message-ID: <20041031191737.GB5937@meier-geinitz.de>

Hi everyone,

Code freeze for sane-backends 1.0.15 is now active. This means,
that no changes to the code should be committed. The only exceptions
are bugs that may render a backend completely useless, that may
destroy hardware, or that break compilation on at least one platform.
If in doubt, ask sane-devel.
Documentation and translation updates are still allowed.

Timetable:
2004-11-07 Release

Bye,
  Henning


From PaulR.Cormier  Sun Oct 31 17:36:19 2004
From: PaulR.Cormier (PaulR.Cormier)
Date: Sun, 31 Oct 2004 12:36:19 -0500
Subject: [sane-devel] Re: Debian confusion
In-Reply-To: <000001c4bf5c$4895f4a0$ca88ee04@NetZeroUser>
References: <000001c4bf5c$4895f4a0$ca88ee04@NetZeroUser>
Message-ID: <20041031123619.0c2bf24f.prcormier@adelphia.net>

You're welcome.
I checked the Readme file that comes with the sane package in question.  I was surprised that it did not specify a version requirement for GCC.
Versions 2.95.4 and 3.0.4 have worked with Lindows/Linspire, and versions 3.2 and 3.3 may work.
You will also want to check the Readme file for other requirements.
The debian web site will also have instructions on how to use their package tools.  Using those will help to check for other dependencies that need to be addressed.  One note of caution:  Linspire is not yet working at the same release level as debian, so avoid updating things that are not necessary to your goals (or join Linspire's Click-n-Run library program - works fairly well, but up to date releases are not always available).

-- 
Best regards,

Paul R. Cormier
prcormier@adelphia.net


On Sun, 31 Oct 2004 10:08:36 -0500
"Bensel" <whitemanor@netzero.net> wrote:

> Thanks for your help.
> We went to debian.org and are confused with all the gcc packages.  Can you give us any guidelines to help sort out which package we should download to get a working compiler on our system?
> Thank you very much.
> Howard
> 
> On Thu, 28 Oct 2004 09:26:12 -0400
> "Bensel" <whitemanor@netzero.net> wrote:
> 
> > We are trying to get a Memorex MEM 48u scanner working with Linspire 4.5.393.  It is suppose to work with the artec_eplus48u backend so we downloaded sane-backends-1.0.14.  When we run ./configure, we get the error: no acceptable C compiler found in $PATH.  We understand the ANSI C Compiler: GNU C (gcc) is recommended.  Could someone advise how we should proceed from here.  Thanks for your advice and help.
> > 
> 
> If you have access to Linspire's Click-N-Run library, you can get the compilers and other tools there.
> If not, you might try using the Debian Package tools (Linspire is based on the Debian distribution).
> 
> -- 
> Best regards,
> 
> Paul R. Cormier
> prcormier@adelphia.net
> 
> 
> 


From henning@meier-geinitz.de  Sun Oct 31 19:14:55 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 31 Oct 2004 20:14:55 +0100
Subject: [sane-devel] [ANNOUNCE] Second pre-release of sane-backends 1.0.15 available
Message-ID: <20041031191455.GA5937@meier-geinitz.de>

Hi everyone,

The second pre-release of sane-backends 1.0.15 is available at
the usual locations as mentioned on
http://www.sane-project.org/source.html

The md5sum is:
be835c68cb6a387d50ca250755031983  sane-backends-1.0.15-pre2.tar.gz

We are in code freeze currently. Release is planned for 2004-11-07.

I'll append the NEWS file for 1.0.15.

Please test this prerelease and tell us about any bugs.

Happy scanning!

Henning

New with 1.0.15, released 2004-11-07:

* New backends: niash.
* Updated backends: agfafocus, artec_eplus48u.c, avision, canon, canon_pp,
  coolscan, dll, epson, fujitsu, gt68xx, hp, hp5400, leo, microtek2, mustek,
  mustek_pp, net, pie, plustek, plustek_pp, snapscan, sp15c, tamarack, teco2,
  umax, umax_pp, u12, v4l.
* Portability fixes (especially for MacOS X, NetBSD, OS/2, 64 bit platforms).
* sane-find-scanner detects more chipsets now.
* Added Finnish translation. Updated other translations.
* Several saned fixes.
* Build system updates.
* Documentation updates.
* Bugfixes.



From svoltz at wanadoo.fr  Fri Oct  1 05:27:33 2004
From: svoltz at wanadoo.fr (svoltz at wanadoo.fr)
Date: Fri, 1 Oct 2004 06:27:33 +0200
Subject: [sane-devel] umax_pp slow
In-Reply-To: <415C7DD3.3090102@kc.rr.com>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com>
Message-ID: <20041001042733.GA2166@wanadoo.fr>

On Thu, Sep 30, 2004 at 04:42:43PM -0500, Joe Henley wrote:
> Stef,
> 
> Thanks very much for your reply.  I changed my umax_pp.conf file to read:
> -------------------------------
> option buffer 8388608
> port 0x378
> option astra 2000
> 
> Then I ran the export command, then the scanimage command.  The log 
> contents are:
> -------------------------------------------------------------
> [sanei_debug] Setting debug level of umax_pp_low to 1.
> [umax_pp_low] SANE_INB level 3
> [umax_pp_low] sanei_umax_pp_InitPort(0x378,)
> [umax_pp_low] sanei_ioperm(0x378, 8, 1) OK ...
> [umax_pp_low] UMAX Astra 1220/1600/2000 P ASIC detected (mode=31)
> [umax_pp_low] registerRead, found 0xFF expected 0x00 (umax_pp_low.c:6633)

	Weird, your paralle port can't do EPP when used directly, while it
works with ppdev.

> [umax_pp_low] *** It appears that EPP data transfer doesn't work    ***
> [umax_pp_low] *** Please read SETTING EPP section in sane-umax_pp.5 ***
> [umax_pp_low] Hardware can't do ECP, giving up (umax_pp_low.c:6856) ...
> [umax_pp_low] No EPP or ECP mode working, giving up ... (umax_pp_low.c:7475)
> 
> The results surprised me.  I ran ppdiag to check and got:
> ---------------------------------------------------
> S01: parport built as module
> S02: parport0:
> S02:    modes:PCSPP,TRISTATE,EPP
> S02:    ADDR :0x378
> S02:    IRQ  :no IRQ used
> S02:    DMA  :no DMA used
> S03: no parport parameters
> S10: ppdev built as module
> S12: /dev/parport0 exists ...
> S12: /dev/parport0 is readable ...
> S12: /dev/parport0 is writable ...
> successfull end ....
> 
> I double checked my BIOS and it's set to EPP, port 378 and IRQ 7.
> 
> So now I'm really stumped.  Please point me in the right direction.
> 
> If it's relevant:  using RedHat 9, kernel is 2.4.20-20.9, xsane is 
> version 0.96, sane-backend is: 1.0.14 with the 6.3 patch for umax_pp, 
> mobo is an Intel 875PBZ.
> 
> Joe
> 
> PS:  Sorry about RoadRunner blocking your replies.  I don't know why.

	Try tweaking the parport parameters in /etc/modules.conf :

alias parport_lowlevel parport_pc
options parport_pc io=0x378 io_hi=0x778 irq=7 dma=none

	Another thing to try is to check is the kernel you use is
compiled with the followwing options in 'Parallel port support':

    <M> Parallel port support
    <M> PC-style hardware
    < > Multi-IO cards (parallel and serial)
    [*] Use FIFO/DMA if available (EXPERIMENTAL)
    [*] SuperIO chipset support (EXPERIMENTAL)
    < > Support for PCMCIA management for PC-style ports
    [ ] Support foreign hardware
    [*] IEEE 1284 transfer modes 

	What other parallel port BIOS setting do you have ?

Regards,
	Stef



From gerhard at gjaeger.de  Fri Oct  1 07:49:00 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Fri, 1 Oct 2004 08:49:00 +0200
Subject: [sane-devel] sane-find-scanner finds Lide20, plustek backend does not
In-Reply-To: <415C3AA4.7020508@lynx.net>
References: <4152FD0F.6070103@lynx.net> <20040929162241.GA8559@meier-geinitz.de> <415C3AA4.7020508@lynx.net>
Message-ID: <200410010849.00927.gerhard@gjaeger.de>

On Thursday 30 September 2004 18:56, Lloyd Sumpter wrote:
> Henning Meier-Geinitz wrote:
> > Hi,
> >
> > On Tue, Sep 28, 2004 at 01:22:01PM -0700, Lloyd Sumpter wrote:
> >>[sanei_debug] Setting debug level of sanei_usb to 255.
> >>[sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such
> >> device [sanei_usb] sanei_usb_init: found 0 devices
> >
> > Oh. That means that SANE isn't built with libusb support. It only
> > searches for /dev/usb/ but not for libusb devices.
>
> Ah...THAT would explain a lot!
>
> > As your sane-find-scanner program finds libusb devices, maybe you have
> > an old installation of the SANE backends without libusb support that's
> > used by scanimage?
>
> I'm using the backends that came with Mandrake 10.0, which claim to be
> 1.0.13. Sounds like I should un-install the Mandrake version of sane and
> install from another source (hopefully I won't have to compile...)
>
> Can I just change the backends, or should I change the whole thing?

Always change the whole thing, only by that you're guaranteed that it'll
work together. For the LiDE20 try to get the latest 1.0.14 stuff, because
of some missing calibration stuff in 1.0.13.

Ciao,
  Gerhard




From gerhard at gjaeger.de  Fri Oct  1 08:43:03 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Fri, 1 Oct 2004 09:43:03 +0200
Subject: [sane-devel] USB: scanimage bails out
In-Reply-To: <415BF7E9.7080209@gmx.de>
References: <415BF7E9.7080209@gmx.de>
Message-ID: <200410010943.03758.gerhard@gjaeger.de>

Hi,

On Thursday 30 September 2004 14:11, Cornelius Koelbel wrote:
> Hello all,
>
> I am running a SuSE 9.1 with a Canon USB Scanner attached.
>
> sane-find-scanner tells me this:
> found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan],
> chip=LM983x?) at libusb:002:003

Try to run it as root and the "?" in "chip=LM983x" will disappear...
>
> and I set up the scanner with yast.
>
> Wenn I log into X and start xsane, I am able to scan.
> But when I got to a terminal and do a "/usr/bin/scanimage", I get this
> message:
> "scanimage: no SANE devices found"

This is somewhat strange. What's the output of:
export SANE_DEBUG_PLUSTEK=20; scanimage -L

[SNIPSNAP]
> The device in the proc filesystem exists:
> --snip--
> linux:~ # ls /proc/bus/usb/002/003  -l
> -rw-rw-rw-  1 root root 57 Sep 30 11:20 /proc/bus/usb/002/003
> --snip--

So there should be no problem in accessing the scanner.

>
> I get such a message in the /var/log/messages:
> --snip--
> Sep 30 11:26:16 linux scanimage: resmgr: server response code 200
> Sep 30 11:26:16 linux scanimage: resmgr: server response code 200
> --snip--

Hmmm, not quite sure about that - maybe here's the problem.
Anybody else?

Gerhard





From cornelius.koelbel at gmx.de  Fri Oct  1 08:52:40 2004
From: cornelius.koelbel at gmx.de (Cornelius Koelbel)
Date: Fri, 01 Oct 2004 09:52:40 +0200
Subject: [sane-devel] USB: scanimage bails out
In-Reply-To: <200410010943.03758.gerhard@gjaeger.de>
References: <415BF7E9.7080209@gmx.de> <200410010943.03758.gerhard@gjaeger.de>
Message-ID: <415D0CC8.4050900@gmx.de>

Hello,

I set the /usr/bin/scanimage suid and now it works (at the moment).
But I was so much fiddling about, that I am not sure, if it works, when 
I install it anew.
Hm, we will see. I guess this thread isn't closed yet ;-)

I will check your hints!

Regards
Cornelius

Gerhard Jaeger wrote:
> Hi,
> 
> On Thursday 30 September 2004 14:11, Cornelius Koelbel wrote:
> 
>>Hello all,
>>
>>I am running a SuSE 9.1 with a Canon USB Scanner attached.
>>
>>sane-find-scanner tells me this:
>>found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan],
>>chip=LM983x?) at libusb:002:003
> 
> 
> Try to run it as root and the "?" in "chip=LM983x" will disappear...
> 
>>and I set up the scanner with yast.
>>
>>Wenn I log into X and start xsane, I am able to scan.
>>But when I got to a terminal and do a "/usr/bin/scanimage", I get this
>>message:
>>"scanimage: no SANE devices found"
> 
> 
> This is somewhat strange. What's the output of:
> export SANE_DEBUG_PLUSTEK=20; scanimage -L
> 
> [SNIPSNAP]
> 
>>The device in the proc filesystem exists:
>>--snip--
>>linux:~ # ls /proc/bus/usb/002/003  -l
>>-rw-rw-rw-  1 root root 57 Sep 30 11:20 /proc/bus/usb/002/003
>>--snip--
> 
> 
> So there should be no problem in accessing the scanner.
> 
> 
>>I get such a message in the /var/log/messages:
>>--snip--
>>Sep 30 11:26:16 linux scanimage: resmgr: server response code 200
>>Sep 30 11:26:16 linux scanimage: resmgr: server response code 200
>>--snip--
> 
> 
> Hmmm, not quite sure about that - maybe here's the problem.
> Anybody else?
> 
> Gerhard
> 
> 
> 

-- 
Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte untersucht
und ist - aktuelle Virenscanner vorausgesetzt - sauber.
MailScanner dankt transtec fur die freundliche Unterstutzung.




From cornelius.koelbel at gmx.de  Fri Oct  1 10:17:00 2004
From: cornelius.koelbel at gmx.de (Cornelius Koelbel)
Date: Fri, 01 Oct 2004 11:17:00 +0200
Subject: [sane-devel] scanimage does not scan the whole page
Message-ID: <415D208C.3090103@gmx.de>

Hello,

here I am again with a new problem.
I got my scanner a USB Cannon CanoScan N670/676U  with the plustek 
backend, scanning now.

But when I issue the command scanimage --format tiff --mode Color > 
test.tif,

I get only a small portion of the image (240x160), not the whole page.

What do I have to do to get the whole page?

Thanks
Cornelius



From henning at meier-geinitz.de  Fri Oct  1 10:57:14 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 1 Oct 2004 11:57:14 +0200
Subject: [sane-devel] scanimage does not scan the whole page
In-Reply-To: <415D208C.3090103@gmx.de>
References: <415D208C.3090103@gmx.de>
Message-ID: <20041001095714.GA8035@meier-geinitz.de>

Hi,

On Fri, Oct 01, 2004 at 11:17:00AM +0200, Cornelius Koelbel wrote:
> But when I issue the command scanimage --format tiff --mode Color > 
> test.tif,
> 
> I get only a small portion of the image (240x160), not the whole page.
> 
> What do I have to do to get the whole page?

"scanimage --help" prints all the available options.

Bye,
  HJenning



From gerard at gkall.hobby.nl  Fri Oct  1 12:51:08 2004
From: gerard at gkall.hobby.nl (gerard klaver)
Date: Fri, 01 Oct 2004 11:51:08 +0000
Subject: [sane-devel] scanimage does not scan the whole page
In-Reply-To: <1096631360.2324.21.camel@gk-lex3>
References: <415D208C.3090103@gmx.de>  <1096631360.2324.21.camel@gk-lex3>
Message-ID: <1096631467.1597.23.camel@gk-lex3>

On Fri, 2004-10-01 at 11:49, gerard klaver wrote:
> On Fri, 2004-10-01 at 09:17, Cornelius Koelbel wrote:
> > Hello,
> > 
> > here I am again with a new problem.
> > I got my scanner a USB Cannon CanoScan N670/676U  with the plustek 
> > backend, scanning now.
> > 
> > But when I issue the command scanimage --format tiff --mode Color > 
> > test.tif,
> > 
> > I get only a small portion of the image (240x160), not the whole page.
> > 
> > What do I have to do to get the whole page?
> > 
> > Thanks
> > Cornelius
> 
> scanimage -h -d plustek
> 
> see the options for Geometry
-- 
----------
m.vr.gr.
Gerard Klaver




From gerhard at gjaeger.de  Fri Oct  1 14:03:17 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Fri, 1 Oct 2004 15:03:17 +0200
Subject: [sane-devel] scanimage does not scan the whole page
In-Reply-To: <415D208C.3090103@gmx.de>
References: <415D208C.3090103@gmx.de>
Message-ID: <200410011503.18059.gerhard@gjaeger.de>

On Friday 01 October 2004 11:17, Cornelius Koelbel wrote:
> Hello,
>
> here I am again with a new problem.
> I got my scanner a USB Cannon CanoScan N670/676U  with the plustek
> backend, scanning now.
>
> But when I issue the command scanimage --format tiff --mode Color >
> test.tif,
>
> I get only a small portion of the image (240x160), not the whole page.

That's the default scanarea of the plustek backend.

>
> What do I have to do to get the whole page?

Set the scanarea dimensions correctly ;)

Gerhard




From thereidos at gmail.com  Fri Oct  1 18:19:48 2004
From: thereidos at gmail.com (Thereidos)
Date: Fri, 1 Oct 2004 19:19:48 +0200
Subject: [sane-devel] Plustek OpticPro UT16
Message-ID: <872262d404100110195dc588ba@mail.gmail.com>

Hi there.

I'm new round here. I have bought Plustek OpticPro UT16 USB scanner
which is marked on sane's webpage as being supported. Unfortunatelly
sane (or actually xsane) cannot detect it. Neither doesn any other
scanning app.

I'm running Mandrake 10.0, sane 1.0.14 and 2.6.3 kernel.

I've just heard that 2.6.x series kernel have problems with usb. May
it be the reason?
-- 
Cezary 'Thereidos' Morga <thereidos at gmail.com>
Registered Linux User No. 362185 <http://counter.li.org>
GG# 169903 ICQ# 328-700-565 Jabber: thereidos at ebox.pl
backup email addresses: cezarym at pf.pl, cezarymorga at o2.pl



From gerard at gkall.hobby.nl  Fri Oct  1 20:40:47 2004
From: gerard at gkall.hobby.nl (gerard klaver)
Date: Fri, 01 Oct 2004 19:40:47 +0000
Subject: [sane-devel] Plustek OpticPro UT16
In-Reply-To: <872262d404100110195dc588ba@mail.gmail.com>
References: <872262d404100110195dc588ba@mail.gmail.com>
Message-ID: <1096659647.1588.31.camel@gk-lex3>

On Fri, 2004-10-01 at 17:19, Thereidos wrote:
> Hi there.
> 
> I'm new round here. I have bought Plustek OpticPro UT16 USB scanner
> which is marked on sane's webpage as being supported. Unfortunatelly
> sane (or actually xsane) cannot detect it. Neither doesn any other
> scanning app.
> 
> I'm running Mandrake 10.0, sane 1.0.14 and 2.6.3 kernel.
> 
> I've just heard that 2.6.x series kernel have problems with usb. May
> it be the reason?
> -- 
> Cezary 'Thereidos' Morga <thereidos at gmail.com>
> Registered Linux User No. 362185 <http://counter.li.org>
> GG# 169903 ICQ# 328-700-565 Jabber: thereidos at ebox.pl
> backup email addresses: cezarym at pf.pl, cezarymorga at o2.pl

Read www.project-sane.org/README.linux,

Check your hotplug setup
check (path can be different) /etc/hotplug/usb/libsane.usermap for
presence or you scanner vid and pid.

check your plustek.conf file (for example etc/sane.d/plustek.conf)

sane-find-scanner -v -v  first check if scanner is found.

export SANE_DEBUG_PLUSTEK=128
xscanimage
or 
xsane

check error log

-- 
----------
m.vr.gr.
Gerard Klaver




From joehenley at kc.rr.com  Fri Oct  1 16:56:51 2004
From: joehenley at kc.rr.com (Joe Henley)
Date: Fri, 01 Oct 2004 10:56:51 -0500
Subject: [sane-devel] umax_pp slow
In-Reply-To: <20041001042733.GA2166@wanadoo.fr>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com> <20041001042733.GA2166@wanadoo.fr>
Message-ID: <415D7E43.8080907@kc.rr.com>

Stef,

New results after the changes you suggested to modules.conf.  At the end 
are some more info.

So added the following to /etc/modules.conf and then rebooted:

alias parport_lowlevel parport_pc
options parport_pc io=0x378 io_hi=0x778 irq=7 dma=none

svoltz at wanadoo.fr wrote:
> On Thu, Sep 30, 2004 at 04:42:43PM -0500, Joe Henley wrote:
> 
>>Stef,
>>
>>Thanks very much for your reply.  I changed my umax_pp.conf file to read:
>>-------------------------------
>>option buffer 8388608
>>port 0x378
>>option astra 2000
>>

No changes to the above

>>Then I ran the export command, then the scanimage command.  The log 
>>contents are:
>>-------------------------------------------------------------
>>[sanei_debug] Setting debug level of umax_pp_low to 1.
>>[umax_pp_low] SANE_INB level 3
>>[umax_pp_low] sanei_umax_pp_InitPort(0x378,)
>>[umax_pp_low] sanei_ioperm(0x378, 8, 1) OK ...
>>[umax_pp_low] UMAX Astra 1220/1600/2000 P ASIC detected (mode=31)
>>[umax_pp_low] registerRead, found 0xFF expected 0x00 (umax_pp_low.c:6633)
> 
> 
> 	Weird, your paralle port can't do EPP when used directly, while it
> works with ppdev.
> 

The new results are esssentially the same; except for the line I marked
with asterisks:

[sanei_debug] Setting debug level of umax_pp_low to 1.
[umax_pp_low] SANE_INB level 3
[umax_pp_low] sanei_umax_pp_InitPort(0x378,)
[umax_pp_low] sanei_ioperm(0x378, 8, 1) OK ...
[umax_pp_low] UMAX Astra 1220/1600/2000 P ASIC detected (mode=31)
[umax_pp_low] Unexpected value for for register 0x0D, expected 0x00 or
0x40, got 0x18 ! (umax_pp_low.c:7406) ********New line*****************
[umax_pp_low] registerRead, found 0xFF expected 0x00 (umax_pp_low.c:6633)
[umax_pp_low] *** It appears that EPP data transfer doesn't work    ***
[umax_pp_low] *** Please read SETTING EPP section in sane-umax_pp.5 ***
[umax_pp_low] Hardware can't do ECP, giving up (umax_pp_low.c:6856) ...
[umax_pp_low] No EPP or ECP mode working, giving up ... (umax_pp_low.c:7475)

> 
>>[umax_pp_low] *** It appears that EPP data transfer doesn't work    ***
>>[umax_pp_low] *** Please read SETTING EPP section in sane-umax_pp.5 ***
>>[umax_pp_low] Hardware can't do ECP, giving up (umax_pp_low.c:6856) ...
>>[umax_pp_low] No EPP or ECP mode working, giving up ... (umax_pp_low.c:7475)
>>
>>The results surprised me.  I ran ppdiag to check and got:
>>---------------------------------------------------
>>S01: parport built as module
>>S02: parport0:
>>S02:    modes:PCSPP,TRISTATE,EPP
>>S02:    ADDR :0x378
>>S02:    IRQ  :no IRQ used
>>S02:    DMA  :no DMA used
>>S03: no parport parameters
>>S10: ppdev built as module
>>S12: /dev/parport0 exists ...
>>S12: /dev/parport0 is readable ...
>>S12: /dev/parport0 is writable ...
>>successfull end ....
>>

Then reran ppdiag and got:
S01: parport built as module
S02: parport0:
S02:    modes:PCSPP,TRISTATE,EPP
S02:    ADDR :0x378
S02:    IRQ  :7
S02:    DMA  :no DMA used
S03: parport parameters are: options parport_pc io=0x378 io_hi=0x778
irq=7 dma=none
S10: ppdev built as module
S12: /dev/parport0 exists ...
S12: /dev/parport0 is readable ...
S12: /dev/parport0 is writable ...
successfull end ...


>>I double checked my BIOS and it's set to EPP, port 378 and IRQ 7.
>>
>>So now I'm really stumped.  Please point me in the right direction.
>>
>>If it's relevant:  using RedHat 9, kernel is 2.4.20-20.9, xsane is 
>>version 0.96, sane-backend is: 1.0.14 with the 6.3 patch for umax_pp, 
>>mobo is an Intel 875PBZ.
>>
>>Joe
>>
>>PS:  Sorry about RoadRunner blocking your replies.  I don't know why.
> 
> 
> 	Try tweaking the parport parameters in /etc/modules.conf :
> 
> alias parport_lowlevel parport_pc
> options parport_pc io=0x378 io_hi=0x778 irq=7 dma=none
> 
> 	Another thing to try is to check is the kernel you use is
> compiled with the followwing options in 'Parallel port support':
> 
>     <M> Parallel port support
>     <M> PC-style hardware
>     < > Multi-IO cards (parallel and serial)
>     [*] Use FIFO/DMA if available (EXPERIMENTAL)
>     [*] SuperIO chipset support (EXPERIMENTAL)
>     < > Support for PCMCIA management for PC-style ports
>     [ ] Support foreign hardware
>     [*] IEEE 1284 transfer modes 
> 

In my compile config file (it's Red Hat, so there's abit of translation)
is the following.  I think I have all but the two experimental options
set as you'd suugest:
#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
CONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
CONFIG_PARPORT_PC_PCMCIA=m
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

With all these changes, I tried to do a scan and it failed with
essentially the same messages as in the log entry above.

> 	What other parallel port BIOS setting do you have ?

In the BIOS set up screen, it says I have "Output only,"
"Bi-directional," "EPP," and "ECP".  I had forgotten I had ECP.  Oddly
it's in the BIOS, but ppdiag doesn't see it as an option.

So I rebooted and set the BIOS to ECP.  All other settings the same
(including the "export" command).  The scanimage command hung in a loop
with the following:

[sanei_debug] Setting debug level of umax_pp_low to 1.
[umax_pp_low] SANE_INB level 3
[umax_pp_low] sanei_umax_pp_InitPort(0x378,)
[umax_pp_low] sanei_ioperm(0x378, 8, 1) OK ...
[umax_pp_low] UMAX Astra 1220/1600/2000 P ASIC detected (mode=31)
[umax_pp_low] Unexpected value for for register 0x0D, expected 0x00 or
0x40, got 0x18 ! (umax_pp_low.c:7406)
[umax_pp_low] registerRead, found 0xFF expected 0x00 (umax_pp_low.c:6633)
[umax_pp_low] *** It appears that EPP data transfer doesn't work    ***
[umax_pp_low] *** Please read SETTING EPP section in sane-umax_pp.5 ***
[umax_pp_low] ECPregisterRead failed, expecting 0x20, got 0x22
(umax_pp_low.c:2850)
[umax_pp_low] ECPregisterRead failed, expecting 0x20, got 0x22
(umax_pp_low.c:2850)
[umax_pp_low] ECPregisterRead failed, expecting 0x20, got 0x22
(umax_pp_low.c:2850)
.........................the avove line just keeps going, over and over
.....

The results for ppdiag (under ECP) are:
S01: parport built as module
S02: parport0:
S02:    modes:PCSPP,TRISTATE
S02:    ADDR :0x378
S02:    IRQ  :7
S02:    DMA  :no DMA used
S03: parport parameters are: options parport_pc io=0x378 io_hi=0x778
irq=7 dma=none
S10: ppdev built as module
S12: /dev/parport0 exists ...
S12: /dev/parport0 is readable ...
S12: /dev/parport0 is writable ...
successfull end ....

Perhaps it's relevant, I looked in the messages boot log and saw the
following:
Oct  1 10:26:30 Eddie kernel: parport0: PC-style at 0x378 (0x778), irq 7
[PCSPP,TRISTATE]
Oct  1 10:26:40 Eddie kernel: parport0: PC-style at 0x378 (0x778), irq 7
[PCSPP,TRISTATE]
Oct  1 10:26:40 Eddie kernel: lp0: using parport0 (interrupt-driven).
Oct  1 10:26:40 Eddie kernel: lp0: console ready
Oct  1 10:38:56 Eddie kernel: ppdev: user-space parallel port driver

Again I tried to do a scan, it crapped out with messages as in the log file.

Does all this tell you something (other than my parallel port is screwed 
up)?  Any further thoughts or suggestions?

Again, thanks for all your help.

Joe Henley


> 
> Regards,
> 	Stef
> 





From thereidos at gmail.com  Sat Oct  2 00:39:54 2004
From: thereidos at gmail.com (Thereidos)
Date: Sat, 2 Oct 2004 01:39:54 +0200
Subject: [sane-devel] Plustek OpticPro UT16
In-Reply-To: <1096659647.1588.31.camel@gk-lex3>
References: <872262d404100110195dc588ba@mail.gmail.com>
	 <1096659647.1588.31.camel@gk-lex3>
Message-ID: <872262d404100116393ebdf725@mail.gmail.com>

On Fri, 01 Oct 2004 19:40:47 +0000, gerard klaver <gerard at gkall.hobby.nl> wrote:
> Read www.project-sane.org/README.linux,

Alright. The problem was in missing usb interface module in modprobe.conf.

Now I'm having another problem - all the scans are too dark. I've
tried gamma and brightness correction but it didn't help. Anyone got
any idea?
-- 
Cezary 'Thereidos' Morga <thereidos at gmail.com>
Registered Linux User No. 362185 <http://counter.li.org>
GG# 169903 ICQ# 328-700-565 Jabber: thereidos at ebox.pl
backup email addresses: cezarym at pf.pl, cezarymorga at o2.pl



From Francois.Patte at math-info.univ-paris5.fr  Sat Oct  2 15:25:14 2004
From: Francois.Patte at math-info.univ-paris5.fr (=?iso-8859-1?b?RnJhbudvaXM=?= Patte)
Date: Sat,  2 Oct 2004 16:25:14 +0200
Subject: [sane-devel] scanner hp5400
Message-ID: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr>

Bonjour,

I am unable to have the scanner hp5400c working under linux. Here the result of:

***
lsusb:

Bus 003 Device 002: ID 03f0:1005 Hewlett-Packard ScanJet 5400c

*****
sane-find-scanner:

found SCSI scanner "Nikon LS-2000 1.31" at /dev/scanner
found SCSI scanner "Nikon LS-2000 1.31" at /dev/sg0
found SCSI scanner "Nikon LS-2000 1.31" at /dev/sga
  # Your SCSI scanner was detected. It may or may not be supported by SANE. Try
  # scanimage -L and read the backend's manpage.

found USB scanner (vendor=0x03f0, product=0x1005) at /dev/usb/scanner0
found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1005 [HP Scanjet
5400C Series]) at libusb:003:002
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

*********
scanimage -L:

device `coolscan2:scsi:/dev/scanner' is a Nikon    LS-2000          film scanner
device `coolscan:/dev/sg0' is a Nikon    LS-2000          slide scanner

SANE_DEBUG_HP5400=255 scanimage -L

[sanei_debug] Setting debug level of hp5400 to 255.
[hp5400] sane_init: SANE hp5400 backend version 1.0-3 (from sane-backends
1.0.14)
[hp5400] Reading config file
[hp5400] Discarding line 1
[hp5400] Discarding line 2
[hp5400] Discarding line 3
[hp5400] Discarding line 4
[hp5400] Trying to attach usb 0x03f0 0x1005
[hp5400] vendor/product 0x03F0-0x1005 opened
[hp5400] Read: reqtype = 0xC0, req = 0x04, value = 1200
[hp5400] Read: reqtype = 0xC0, req = 0x04, value = C500
[hp5400] Command 12 verified
[hp5400] Sorry, unknown scanner version. Attempted match on :
[hp5400] * 'SilitekIBlizd C3 ScannerV0.84'
[hp5400] * 'SilitekIBlizd C3 ScannerV0.86'
[hp5400] * 'SilitekIBlizd C3 ScannerV0.87'
[hp5400] Version is ''
[hp5400] attach_one_device: attached /dev/usb/scanner0 successfully
[hp5400] hp5400_open: open returned Device busy
[hp5400] hp5400_open failed
[hp5400] attach_one_device: couldn't attach libusb:003:002
[hp5400] Discarding line 6
[hp5400] Discarding line 7
[hp5400] Discarding line 8
[hp5400] Discarding line 9
[hp5400] Discarding line 10
[hp5400] Discarding line 11
[hp5400] Discarding line 12
[hp5400] Discarding line 13
[hp5400] Trying to attach /dev/usb/scanner0
[hp5400] vendor/product 0x03F0-0x1005 opened
[hp5400] Read: reqtype = 0xC0, req = 0x04, value = 1200
[hp5400] Read: reqtype = 0xC0, req = 0x04, value = C500
[hp5400] Command 12 verified
[hp5400] Sorry, unknown scanner version. Attempted match on :
[hp5400] * 'SilitekIBlizd C3 ScannerV0.84'
[hp5400] * 'SilitekIBlizd C3 ScannerV0.86'
[hp5400] * 'SilitekIBlizd C3 ScannerV0.87'
[hp5400] Version is ''
[hp5400] attach_one_device: attached /dev/usb/scanner0 successfully
[hp5400] Discarding line 15
[hp5400] Discarding line 16
[hp5400] sane_get_devices
device `coolscan2:scsi:/dev/scanner' is a Nikon    LS-2000          film scanner
device `coolscan:/dev/sg0' is a Nikon    LS-2000          slide scanner
[hp5400] sane_exit

********
The /etc/sane.d/hp5400.conf is:

# hp5400.conf
# See man sane-hp5400 for a description.
#
# HP 5400C
usb 0x03f0 0x1005
#
# HP 5470C
#usb 0x03F0 0x1105
#
# Device filename to use for scanner access
#
# Uncomment the following line if autodetection fails
#
/dev/usb/scanner0
#libusb:003:002
#option connect-device


What can I do else?

Thank you.
--
Fran?ois Patte

Ecole fran?aise d'Extr?me-Orient - Pune - Inde
Universit? Ren? Descartes - Paris 5
UFR de math?matiques et informatique
http://www.math-info.univ-paris5.fr/~patte



From henning at meier-geinitz.de  Sat Oct  2 15:31:04 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 2 Oct 2004 16:31:04 +0200
Subject: [sane-devel] account problem
In-Reply-To: <20040930103929.51775.qmail@web17810.mail.tpe.yahoo.com>
References: <20040930103929.51775.qmail@web17810.mail.tpe.yahoo.com>
Message-ID: <20041002143104.GF10327@meier-geinitz.de>

Hi,

On Thu, Sep 30, 2004 at 06:39:29PM +0800, sean035 at yahoo.com.tw wrote:
> I have a big problem about account. I am developing a
> new scanner driver for Xsane and backend. But I meet a
> bug about account that I just can work normally as
> root not other user account. When I log in as user
> account I can't use scan and preview as Xsane
> applicaiton. It's always say "Operation was
> cancelled".

While I'm surprised about the error message that's most probably a
permission problem. See README.linux (e.g. here:
http://www.sane-project.org/README.linux) for details.

For which scanner are you developping a backend? Can you give some
details?

Bye,
  Henning




From Oliver.Schwartz at gmx.de  Sat Oct  2 16:16:44 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Sat, 2 Oct 2004 17:16:44 +0200
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <415BD75B.1060103@bigpond.net.au>
References: <415BD75B.1060103@bigpond.net.au>
Message-ID: <200410021716.46218.Oliver.Schwartz@gmx.de>

Hi,

> - "scanimage > /tmp/junkimage.bin" gives me :
>
> [snapscan] Scanner warming up - waiting 9 seconds.
> [snapscan] Scanner warming up - waiting 33 seconds.
> scanimage: sane_start: Error during device I/O
>
> This usually takes more than 9 + 33 seconds to happen

please repeat the test by running 
"SANE_DEBUG_SNAPSCAN=255 scanimage >/tmp/junk.bin 2>debug.log" 
and send me the debug.log file.

/Oliver



From henning at meier-geinitz.de  Sat Oct  2 16:37:19 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 2 Oct 2004 17:37:19 +0200
Subject: [sane-devel] Troubles with sniffusb 1.8
In-Reply-To: <20040928165005.GB858@wanadoo.fr>
References: <20040928165005.GB858@wanadoo.fr>
Message-ID: <20041002153719.GI10327@meier-geinitz.de>

Hi,

On Tue, Sep 28, 2004 at 06:50:05PM +0200, svoltz at wanadoo.fr wrote:
> 	Did anyone get into this ?

I don't remeber having seen such messages.

> 	- last, I see that that the usbsnoop.log isn't used directly, but 
> 	parsed with some awk scripts. Would it be worth to have a 
> 	modified version of sniffusb to output in 'the right format'
> 	directly ?

I don't think so. The log should contain all available information.
Then, the developer can chose which information is needed for his
specific task. Maybe inerrupt tarffic can be ignored, maybe not.
Sometimes you only need contorl messages, sometimes only bulk.

So that really depends on the chipset and the task that should be
performed.

Bye,
  Henning



From henning at meier-geinitz.de  Sat Oct  2 16:39:57 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 2 Oct 2004 17:39:57 +0200
Subject: [sane-devel] HP Scanjet 3670
In-Reply-To: <33041.200.205.218.14.1096404835.squirrel@webmail.novalinux.com.br>
References: <33041.200.205.218.14.1096404835.squirrel@webmail.novalinux.com.br>
Message-ID: <20041002153957.GJ10327@meier-geinitz.de>

Hi,

On Tue, Sep 28, 2004 at 05:53:55PM -0300, anderson at novalinux.com.br wrote:
> I'm migrating all M$ Windows for LINUX in a football club (soccer team)
> but I'm stuck in this HP SCANJET 3670!!!
> 
> Did any one get this thing work on Linux???

Most probably not, at least not with SANE.

> I contact the HP in USA but whithout no result, just the promess of "the
> driver is being developed by our engineers and as soon it is done it'll be
> in the homepage"

Interesting. But I rather think that means "never".

> I am not a developer, I am consultant of computer science and free software.
> but I can understand codes, so, if you need me, I'll be here.

Well, the code is in CVS. So just go ahead and fix it.

http://www.meier-geinitz.de/sane/genesys-backend/

Bye,
  Henning



From henning at meier-geinitz.de  Sat Oct  2 16:49:47 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 2 Oct 2004 17:49:47 +0200
Subject: [sane-devel] scanner hp5400
In-Reply-To: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr>
References: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr>
Message-ID: <20041002154946.GK10327@meier-geinitz.de>

Hi,

On Sat, Oct 02, 2004 at 04:25:14PM +0200, Fran?ois Patte wrote:
> I am unable to have the scanner hp5400c working under linux. Here the result of:

[...]

> [hp5400] vendor/product 0x03F0-0x1005 opened
> [hp5400] Read: reqtype = 0xC0, req = 0x04, value = 1200
> [hp5400] Read: reqtype = 0xC0, req = 0x04, value = C500
> [hp5400] Command 12 verified
> [hp5400] Sorry, unknown scanner version. Attempted match on :
> [hp5400] * 'SilitekIBlizd C3 ScannerV0.84'
> [hp5400] * 'SilitekIBlizd C3 ScannerV0.86'
> [hp5400] * 'SilitekIBlizd C3 ScannerV0.87'
> [hp5400] Version is ''

> What can I do else?

Rebuild sane-backends like this:

CFLAGS="-DNO_STRING_VERSION_MATCH" ./configure
make
make install

That's untested but I think it disables the version test.

See bug report:
https://alioth.debian.org/tracker/index.php?func=detail&aid=300542&group_id=30186&atid=410366

Thomas: As this issue pops up from time to time can't the version test
be disabled completely?

bye,
  Henning




From eppesuig at users.sourceforge.net  Sat Oct  2 15:27:11 2004
From: eppesuig at users.sourceforge.net (Giuseppe Sacco)
Date: Sat, 02 Oct 2004 16:27:11 +0200
Subject: [sane-devel] is coolscan2 maintained?
Message-ID: <1096727231.3040.561.camel@localhost>

Hi,
I am trying to get in touch with the coolscan2 backend author but I got
no replies neither to private emails, neither in this list.
I even checked that his last commit is dated january 2003, so I am
wondering if he is still working at this project.

Is anyone in contact with him?

Thanks,
Giuseppe




From henning at meier-geinitz.de  Sat Oct  2 17:08:03 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 2 Oct 2004 18:08:03 +0200
Subject: [sane-devel] Releases of sane-backends and sane-frontends planned
Message-ID: <20041002160803.GL10327@meier-geinitz.de>

Hi everyone,

I intend to start the release process for sane-backends 1.0.15 soon if
nobody objects. If there are any external backends that should be
included into sane-backends 1.0.15 please send patches now.

I also intend to make a release of sane-frontends soon. If there is
anything that should be included into the next release please commit
it soon.

I'll post timetables in the next few days.

Happy hacking!

Bye,
  Henning



From afb at paradise.net.nz  Sun Oct  3 10:07:20 2004
From: afb at paradise.net.nz (Adam Felix Bogacki)
Date: Sun, 03 Oct 2004 22:07:20 +1300
Subject: [sane-devel] xsane-win32 config : "no devices available"
Message-ID: <415FC148.3000708@paradise.net.nz>

re."C:\sane\bin\xsane.exe"

.... after considerable head-scratching I finally RTFM and realised I 
had put it in
the wrong directory. Re-installing and unzipping in C:, it now works but 
after following
SANE webpage config directions keeps telling me "no devices available".

The scanner works well with xsane on the Deb unstable drive.

I looked at the 'sane-config' file, but it does not seem to have the same
functions as the linux version.

I edited 'C:\sane\etc\sane.d\net.conf' to include the IP adresses of both
my server (midi tower) and my ISP ...
made sure that 'C:\sane\etc\sane.d\dll.conf' contains the uncommented 
line 'net',
and that 'C:\sane\etc\sane.d\epson.conf'  contains

> # For libusb support for unknown scanners use the following command
> # usb <product ID> <device ID>
> # e.g.:
>  usb 0x04b8 0x010c
> # And for the scanner module, use the following configuration:
> #usb /dev/usbscanner0
> usb /dev/usb/scanner0

I'm a bit unsure about the last bit because this is being done in WinXP.

Constructive ideas appreciated.

Adam Bogacki,
afb at paradise.net.nz





From thomas.soumarmon at cogitae.net  Sat Oct  2 17:09:31 2004
From: thomas.soumarmon at cogitae.net (Thomas Soumarmon)
Date: Sat, 02 Oct 2004 18:09:31 +0200
Subject: [sane-devel] scanner hp5400
In-Reply-To: <20041002154946.GK10327@meier-geinitz.de>
References: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr> <20041002154946.GK10327@meier-geinitz.de>
Message-ID: <415ED2BB.1000403@cogitae.net>

Hi Henning,

I have been far away from hp5400 stuff for a while.
I agree with you that the version match test is more an annoyance than a 
killing feature.
Could you give me back a pointer to the parameters for CVS developper 
access ?
I shall do this during the week-end.

Have a nice day.

Henning Meier-Geinitz a ?crit :

>Hi,
>
>On Sat, Oct 02, 2004 at 04:25:14PM +0200, Fran?ois Patte wrote:
>  
>
>>I am unable to have the scanner hp5400c working under linux. Here the result of:
>>    
>>
>
>[...]
>
>  
>
>>[hp5400] vendor/product 0x03F0-0x1005 opened
>>[hp5400] Read: reqtype = 0xC0, req = 0x04, value = 1200
>>[hp5400] Read: reqtype = 0xC0, req = 0x04, value = C500
>>[hp5400] Command 12 verified
>>[hp5400] Sorry, unknown scanner version. Attempted match on :
>>[hp5400] * 'SilitekIBlizd C3 ScannerV0.84'
>>[hp5400] * 'SilitekIBlizd C3 ScannerV0.86'
>>[hp5400] * 'SilitekIBlizd C3 ScannerV0.87'
>>[hp5400] Version is ''
>>    
>>
>
>  
>
>>What can I do else?
>>    
>>
>
>Rebuild sane-backends like this:
>
>CFLAGS="-DNO_STRING_VERSION_MATCH" ./configure
>make
>make install
>
>That's untested but I think it disables the version test.
>
>See bug report:
>https://alioth.debian.org/tracker/index.php?func=detail&aid=300542&group_id=30186&atid=410366
>
>Thomas: As this issue pops up from time to time can't the version test
>be disabled completely?
>
>bye,
>  Henning
>
>  
>


-- 
---------------------------------------------
Thomas Soumarmon.
Ing?nieur D?veloppement & Logiciels Libres
---------------------------------------------
      COGITAE    //www.cogitae.net/
---------------------------------------------
  tel: 05.34.14.39.39 - fax: 05.34.14.39.31
---------------------------------------------





From eppesuig at users.sourceforge.net  Sat Oct  2 18:15:16 2004
From: eppesuig at users.sourceforge.net (Giuseppe Sacco)
Date: Sat, 02 Oct 2004 19:15:16 +0200
Subject: [sane-devel] Releases of sane-backends and sane-frontends
	planned
In-Reply-To: <20041002160803.GL10327@meier-geinitz.de>
References: <20041002160803.GL10327@meier-geinitz.de>
Message-ID: <1096737316.3040.582.camel@localhost>

Il sab, 2004-10-02 alle 18:08, Henning Meier-Geinitz ha scritto:
> Hi everyone,
> 
> I intend to start the release process for sane-backends 1.0.15 soon if
> nobody objects. If there are any external backends that should be
> included into sane-backends 1.0.15 please send patches now.

Hi,
I would like to update the italian translation of sane-backend. I
contacted the translator that worked on it during 2003 and may send the
complete po in one week.

Is there any string freeze planned during the release? Should I get the
original pot at any specific date?

Bye,
Giuseppe




From henning at meier-geinitz.de  Sun Oct  3 10:58:59 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 11:58:59 +0200
Subject: [sane-devel] Releases of sane-backends and sane-frontends planned
In-Reply-To: <1096737316.3040.582.camel@localhost>
References: <20041002160803.GL10327@meier-geinitz.de> <1096737316.3040.582.camel@localhost>
Message-ID: <20041003095859.GB7885@meier-geinitz.de>

Hi,

On Sat, Oct 02, 2004 at 07:15:16PM +0200, Giuseppe Sacco wrote:
> Is there any string freeze planned during the release? Should I get the
> original pot at any specific date?

There shouldn't be any major changes to the strings after feature
freeze. Wait for the timetable for the actual date. Using the po from
after feature freeze should be ok.

Translations can be added at any time as their risk of breaking
anything is rather low. The same is true for documentation updates.

Bye,
  Henning



From henning at meier-geinitz.de  Sun Oct  3 11:03:15 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 12:03:15 +0200
Subject: [sane-devel] xsane-win32 config : "no devices available"
In-Reply-To: <415FC148.3000708@paradise.net.nz>
References: <415FC148.3000708@paradise.net.nz>
Message-ID: <20041003100315.GC7885@meier-geinitz.de>

Hi,

On Sun, Oct 03, 2004 at 10:07:20PM +1300, Adam Felix Bogacki wrote:
> The scanner works well with xsane on the Deb unstable drive.

Which scanner?

> I looked at the 'sane-config' file, but it does not seem to have the same
> functions as the linux version.

sane-config just shows the installation directories and the
compiler/linker flags of the installed SANE version.

> I edited 'C:\sane\etc\sane.d\net.conf' to include the IP adresses of both
> my server (midi tower) and my ISP ...

What do you intend to do? Is the scanner connected to the same
computer? Or do you want to scan over the network?

> made sure that 'C:\sane\etc\sane.d\dll.conf' contains the uncommented 
> line 'net',

That's for scanning over the net.

> and that 'C:\sane\etc\sane.d\epson.conf'  contains

That's for local scanning.

Bye,
  Henning



From uli.e at gmx.de  Sun Oct  3 11:46:44 2004
From: uli.e at gmx.de (Ulrich Eckhardt)
Date: Sun, 03 Oct 2004 12:46:44 +0200
Subject: [sane-devel] is coolscan2 maintained?
In-Reply-To: <1096727231.3040.561.camel@localhost>
References: <1096727231.3040.561.camel@localhost>
Message-ID: <415FD894.1090507@gmx.de>

Giuseppe Sacco wrote:

> I even checked that his last commit is dated january 2003, so I am
> wondering if he is still working at this project.
> 
> Is anyone in contact with him?

Hi,

the last time i heard about him was in July. I had send him
some logs from my Coolscan 5 and he replied, that he is now
working on a backend.

Uli
-- 
Ulrich Eckhardt                  http://www.uli-eckhardt.de

Ein Blizableiter auf dem Kirchturm ist das denkbar st?rkste
Misstrauensvotum gegen den lieben Gott. (Karl Krauss)



From henning at meier-geinitz.de  Sun Oct  3 13:34:40 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 14:34:40 +0200
Subject: [sane-devel] Fix for net/saned on 64 bit systems: please test
Message-ID: <20041003123440.GF7885@meier-geinitz.de>

Hi,

I've just applied a oneliner fix to the CVS version of the net
backend. Please test net/saned especially on 64 bit platforms.

Here is a description of the bug:
https://alioth.debian.org/tracker/index.php?func=detail&aid=300837&group_id=30186&atid=410366

Bye,
  Henning



From eppesuig at users.sourceforge.net  Sun Oct  3 13:01:56 2004
From: eppesuig at users.sourceforge.net (Giuseppe Sacco)
Date: Sun, 3 Oct 2004 14:01:56 +0200
Subject: [sane-devel] is coolscan2 maintained?
In-Reply-To: <415FD894.1090507@gmx.de>
References: <1096727231.3040.561.camel@localhost> <415FD894.1090507@gmx.de>
Message-ID: <20041003120156.GA21739@libero.it>

Il Sun, Oct 03, 2004 at 12:46:44PM +0200, Ulrich Eckhardt ha scritto:
[...]
> the last time i heard about him was in July. I had send him
> some logs from my Coolscan 5 and he replied, that he is now
> working on a backend.

Ok, thanks. I will wait some more then.

Bye,
Giusepe



From henning at meier-geinitz.de  Sun Oct  3 13:58:57 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 14:58:57 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
Message-ID: <20041003125857.GG7885@meier-geinitz.de>

Hi,

I've just fixed some remaining compilation warnings of the microtek2
backend in SANE CVS. As I don't have any scanner that's supported by
the microtek2 backend: Could users of such scanners please test the
latest version? Especially check if calibration still works as
expected. Thanks.

For details see bug report:
https://alioth.debian.org/tracker/index.php?func=detail&aid=300823&group_id=30186&atid=410366

Bye,
  Henning



From henning at meier-geinitz.de  Sun Oct  3 14:20:48 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 15:20:48 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <20041003125857.GG7885@meier-geinitz.de>
References: <20041003125857.GG7885@meier-geinitz.de>
Message-ID: <20041003132048.GH7885@meier-geinitz.de>

Hi again,

Also a work-around to fix scanning on the microtek phantom c6 on big
endian platforms has been committed to SANE CVS. Please everyone check
if that doesn't break anything.

I'm especially interested in reports from users of big endian systems.

Here is the bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23274523

Karsten: I've applied both patches as you don't seem to have committed
changes to the microtek2 backend for quite some time. If you want to
become active again, details on getting CVS access are here:
http://www.sane-project.org/cvs.html

Bye,
  Henning



From henning at meier-geinitz.de  Sun Oct  3 15:04:39 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 16:04:39 +0200
Subject: [sane-devel] Fixing 64 bit problems in sanei code and several backends
Message-ID: <20041003140439.GI7885@meier-geinitz.de>

Hi everyone,

I'm currently trying to fix bug #300814:
https://alioth.debian.org/tracker/index.php?func=detail&aid=300814&group_id=30186&atid=410366
and #300799:
https://alioth.debian.org/tracker/index.php?func=detail&aid=300799&group_id=30186&atid=410366

Most of these warnings are caused by the assumption that size_t is
always 4 bits. E.g.:

size_t hubba;
...
printf ("hubba=%d\n", hubba);

See doc/backend-writing.txt for details.

Unfortunately the patch attached to the bug report can't be used
directly as it assumes that all platforms are 64 bit. So I'll try to
fix all the obvious problems manually like this:

printf ("hubba=%lu\n", (u_long) hubba);

As there are many size_t = 4 byte assumptions throughout the code of
SANE, the changes will touch many backends. Instead of creating bug
reports or mailing every single maintainer for some on e liner patches
I intend to change the code in CVS directly also for the backends.

If anybody doesn't like this approach please tell me.

Bye,
  Henning



From henning at meier-geinitz.de  Sun Oct  3 18:32:14 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 3 Oct 2004 19:32:14 +0200
Subject: [sane-devel] Fixing 64 bit problems in sanei code and several backends
In-Reply-To: <20041003140439.GI7885@meier-geinitz.de>
References: <20041003140439.GI7885@meier-geinitz.de>
Message-ID: <20041003173214.GJ7885@meier-geinitz.de>

Hi,

On Sun, Oct 03, 2004 at 04:04:39PM +0200, Henning Meier-Geinitz wrote:
> As there are many size_t = 4 byte assumptions throughout the code of
> SANE, the changes will touch many backends. Instead of creating bug
> reports or mailing every single maintainer for some on e liner patches
> I intend to change the code in CVS directly also for the backends.

The changes are in CVS now. Please test. As I can't test on 64 bit
platforms myself I'm especially interested in reports about
compilation warnings and errors from such platforms.

Bye,
  Henning



From svoltz at wanadoo.fr  Mon Oct  4 05:46:44 2004
From: svoltz at wanadoo.fr (svoltz at wanadoo.fr)
Date: Mon, 4 Oct 2004 06:46:44 +0200
Subject: [sane-devel] umax_pp slow
In-Reply-To: <415D7E43.8080907@kc.rr.com>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com> <20041001042733.GA2166@wanadoo.fr> <415D7E43.8080907@kc.rr.com>
Message-ID: <20041004044644.GA6220@wanadoo.fr>

	Hello,

	I think you should try again ECP. I think the message you get is
harmless. You can comment it out in the sourcecode before doing tests
again. 
	But until you see ECP mode detected by ythe linux kernel, I'm
afraid you'll have troubles.

Regards,
	Stef



From cornelius.koelbel at gmx.de  Mon Oct  4 09:05:29 2004
From: cornelius.koelbel at gmx.de (Cornelius Koelbel)
Date: Mon, 04 Oct 2004 10:05:29 +0200
Subject: [sane-devel] scanning for faxes
Message-ID: <41610449.10304@gmx.de>

Hello,

I want to scan a A4 page, that I want to fax then.

I read that using the lineart-mode is the best solution.
But when I use the option --mode lineart with my plustek-driver, I get 
an error, that setting of --mode failed due to a wrong argument.

Any hints how I could best scan for faxes?

Regards
Cornelius

-- 
Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte untersucht
und ist - aktuelle Virenscanner vorausgesetzt - sauber.
MailScanner dankt transtec fur die freundliche Unterstutzung.




From scottf at bigpond.net.au  Mon Oct  4 09:06:50 2004
From: scottf at bigpond.net.au (scott fagg)
Date: Mon, 4 Oct 2004 18:06:50 +1000
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <200410021716.46218.Oliver.Schwartz@gmx.de>
References: <415BD75B.1060103@bigpond.net.au> <200410021716.46218.Oliver.Schwartz@gmx.de>
Message-ID: <Pine.LNX.4.53.0410041806350.16694@localhost.localdomain>

On Sat, 2 Oct 2004, Oliver Schwartz wrote:

> Date: Sat, 02 Oct 2004 17:16:44 +0200
> From: Oliver Schwartz <Oliver.Schwartz at gmx.de>
> To: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] epson 2580 problems
>
> Hi,
>
> > - "scanimage > /tmp/junkimage.bin" gives me :
> >
> > [snapscan] Scanner warming up - waiting 9 seconds.
> > [snapscan] Scanner warming up - waiting 33 seconds.
> > scanimage: sane_start: Error during device I/O
> >
> > This usually takes more than 9 + 33 seconds to happen
>
> please repeat the test by running
> "SANE_DEBUG_SNAPSCAN=255 scanimage >/tmp/junk.bin 2>debug.log"
> and send me the debug.log file.

I've sent you a copy directly.

>
> /Oliver
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org
>

--
scottf at bigpond.net.au




From us at bernafon.ch  Mon Oct  4 09:18:53 2004
From: us at bernafon.ch (Ullrich Sigwanz)
Date: Mon, 4 Oct 2004 10:18:53 +0200 
Subject: [sane-devel] XSane: Grey-scale and line-art for "color-only" scanners?
Message-ID: <2ED257AB11E3D84B8526737E255288EE14FCD7@brnnt12.bernafon.ch>

Hi all,

Is there a way to let XSane scan/view/store grey-scale or line-art, 
when there are only color scan modes for the backend available 
(as it is with the "niash" backend), 
or must the backend itself supply 
at least a grey-scale scan mode.

Thank you in advance

Ullrich



From afb at paradise.net.nz  Mon Oct  4 09:45:35 2004
From: afb at paradise.net.nz (Adam Felix Bogacki)
Date: Mon, 04 Oct 2004 21:45:35 +1300
Subject: [sane-devel] xsane-win32
Message-ID: <41610DAF.8050108@paradise.net.nz>

Thanks Oliver,

    My server is 203.79.110.81, ISP is 203.96.152.4

I've played around with commenting out  'localhost' or local server but  
all options give me
'no devices available'.

trying 'C:\sane\bin\xsane  net:localhost (with 'localhost' enabled) gave 
me the response

"Failed to open device 'net:localhost'
Error during device I/O."

Adam Bogacki,
afb at paradise.net.nz


> # This is the net config file.  Each line names a host to attach to.
> # If you list "localhost" then your backends can be accessed either
> # directly or through the net backend.  Going through the net backend
> # may be necessary to access devices that need special privileges.
>  localhost
> #192.168.0.7
> #203.79.110.81
> #203.96.152.4






From henning at meier-geinitz.de  Mon Oct  4 10:54:16 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 4 Oct 2004 11:54:16 +0200
Subject: [sane-devel] scanning for faxes
In-Reply-To: <41610449.10304@gmx.de>
References: <41610449.10304@gmx.de>
Message-ID: <20041004095416.GB9814@meier-geinitz.de>

Hi,

On Mon, Oct 04, 2004 at 10:05:29AM +0200, Cornelius Koelbel wrote:
> I read that using the lineart-mode is the best solution.
> But when I use the option --mode lineart with my plustek-driver, I get 
> an error, that setting of --mode failed due to a wrong argument.

That's because "lineart" is not a mode the plustek backend knows
about. Run "scanimage --help". It will print all options. I guess
"Binary" is the right one.

Maybe the Plustek backend can be changed to use the
SANE_VALUE_SCAN_MODE_* macros from saneopts.h?

Bye,
  Henning



From Oliver.Rauch at Rauch-Domain.DE  Mon Oct  4 14:32:50 2004
From: Oliver.Rauch at Rauch-Domain.DE (Oliver Rauch)
Date: 04 Oct 2004 15:32:50 +0200
Subject: [sane-devel] XSane: Grey-scale and line-art for "color-only"
	scanners?
In-Reply-To: <2ED257AB11E3D84B8526737E255288EE14FCD7@brnnt12.bernafon.ch>
References: <2ED257AB11E3D84B8526737E255288EE14FCD7@brnnt12.bernafon.ch>
Message-ID: <1096896770.2141.2.camel@Babylon7>

XSane does not allow color->grayscale->lineart transformation.
That is something that all scanners/backends should make available.

I will think about adding such a feature to xsane.

Oliver

Am Mon, 2004-10-04 um 10.18 schrieb Ullrich Sigwanz:
> Hi all,
> 
> Is there a way to let XSane scan/view/store grey-scale or line-art, 
> when there are only color scan modes for the backend available 
> (as it is with the "niash" backend), 
> or must the backend itself supply 
> at least a grey-scale scan mode.
> 
> Thank you in advance
> 
> Ullrich




From gerard at gkall.hobby.nl  Mon Oct  4 17:22:55 2004
From: gerard at gkall.hobby.nl (gerard klaver)
Date: Mon, 04 Oct 2004 16:22:55 +0000
Subject: [sane-devel] XSane: Grey-scale and line-art for "color-only"
	scanners?
In-Reply-To: <1096896770.2141.2.camel@Babylon7>
References: <2ED257AB11E3D84B8526737E255288EE14FCD7@brnnt12.bernafon.ch>
	 <1096896770.2141.2.camel@Babylon7>
Message-ID: <1096906974.2067.52.camel@gk-lex3>

On Mon, 2004-10-04 at 13:32, Oliver Rauch wrote:
> XSane does not allow color->grayscale->lineart transformation.
> That is something that all scanners/backends should make available.
> 
> I will think about adding such a feature to xsane.
> 
> Oliver
> 
> Am Mon, 2004-10-04 um 10.18 schrieb Ullrich Sigwanz:
> > Hi all,
> > 
> > Is there a way to let XSane scan/view/store grey-scale or line-art, 
> > when there are only color scan modes for the backend available 
> > (as it is with the "niash" backend), 
> > or must the backend itself supply 
> > at least a grey-scale scan mode.
> > 
> > Thank you in advance
> > 
> > Ullrich

Workaround:
Use GIMP to startup XSANE then after scanning in submenu Gimp choice
image then choice mode and then choice color, gray or b/w to change 
scanning object.
-- 
----------
m.vr.gr.
Gerard Klaver




From boldra at tiscali.it  Mon Oct  4 17:44:37 2004
From: boldra at tiscali.it (Enrico Boldrini)
Date: Mon, 04 Oct 2004 18:44:37 +0200
Subject: [sane-devel] homepage for "artiscan 9600" scanner
Message-ID: <1096908276.936.26.camel@vicious>

Hi everyone,
It's online a site for artiscan 9600 scanner at:
http://home.pages.at/artiscann9600/
Here you'll find some instructions to make the scanner work under wine
and a place where developers of artiscan9600 may exchange their ideas.
current status of project:
developers of windows driver(documan) don't want to give us the
documentation; we have to do reverse engineering job to make it work.

Bye, enrico





From Oliver.Schwartz at gmx.de  Mon Oct  4 19:26:57 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Mon, 4 Oct 2004 20:26:57 +0200
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <Pine.LNX.4.53.0410041806350.16694@localhost.localdomain>
References: <415BD75B.1060103@bigpond.net.au> <200410021716.46218.Oliver.Schwartz@gmx.de> <Pine.LNX.4.53.0410041806350.16694@localhost.localdomain>
Message-ID: <200410042026.59822.Oliver.Schwartz@gmx.de>

Hi,

> > please repeat the test by running
> > "SANE_DEBUG_SNAPSCAN=255 scanimage >/tmp/junk.bin 2>debug.log"
> > and send me the debug.log file.
>
> I've sent you a copy directly.

The first three lines of the log read

[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.35

And later

[snapscan] sane_snapscan_open (after firmware upload): "EPSON 
Scanner1" is not a supported scanner

It seems you're using an old version of the snapscan backend. The 
backend revision should say "1.4.40" if you use the CVS version. 
Since you wrote earlier that you're using a fairly recent CVS 
snapshot you probably have two versions of SANE installed (e.g. one 
in /usr/lib/sane and one in /usr/local/lib/sane).

/Oliver



From henning at meier-geinitz.de  Mon Oct  4 19:28:57 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 4 Oct 2004 20:28:57 +0200
Subject: [sane-devel] homepage for "artiscan 9600" scanner
In-Reply-To: <1096908276.936.26.camel@vicious>
References: <1096908276.936.26.camel@vicious>
Message-ID: <20041004182857.GA2294@meier-geinitz.de>

Hi,

On Mon, Oct 04, 2004 at 06:44:37PM +0200, Enrico Boldrini wrote:
> It's online a site for artiscan 9600 scanner at:
> http://home.pages.at/artiscann9600/

I the full name of that scanner "Tamarack Artiscan 9600" or "Tamarack
Artiscan 9600 pro 36"?

Bye,
  Henning



From scottf at bigpond.net.au  Mon Oct  4 21:25:57 2004
From: scottf at bigpond.net.au (scott fagg)
Date: Tue, 05 Oct 2004 06:25:57 +1000
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <200410042026.59822.Oliver.Schwartz@gmx.de>
References: <415BD75B.1060103@bigpond.net.au>
 <200410021716.46218.Oliver.Schwartz@gmx.de>
 <Pine.LNX.4.53.0410041806350.16694@localhost.localdomain>
 <200410042026.59822.Oliver.Schwartz@gmx.de>
Message-ID: <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain>

On Mon, 4 Oct 2004, Oliver Schwartz wrote:

> Date: Mon, 04 Oct 2004 20:26:57 +0200
> From: Oliver Schwartz <Oliver.Schwartz at gmx.de>
> To: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] epson 2580 problems
>
> Hi,
>
> > > please repeat the test by running
> > > "SANE_DEBUG_SNAPSCAN=255 scanimage >/tmp/junk.bin 2>debug.log"
> > > and send me the debug.log file.
> >
> > I've sent you a copy directly.
>
> The first three lines of the log read
>
> [sanei_debug] Setting debug level of snapscan to 255.
> [snapscan] sane_snapscan_init
> [snapscan] sane_snapscan_init: Snapscan backend version 1.4.35
>
> And later
>
> [snapscan] sane_snapscan_open (after firmware upload): "EPSON
> Scanner1" is not a supported scanner
>
> It seems you're using an old version of the snapscan backend. The
> backend revision should say "1.4.40" if you use the CVS version.
> Since you wrote earlier that you're using a fairly recent CVS
> snapshot you probably have two versions of SANE installed (e.g. one
> in /usr/lib/sane and one in /usr/local/lib/sane).

That might explain why i had some success earlier on, but none now. I'll
track down all copies, clean up and try again.

>
> /Oliver
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org
>

--
scottf at bigpond.net.au




From shirshegsm at delfi.lt  Mon Oct  4 21:46:43 2004
From: shirshegsm at delfi.lt (Linas Valiukas)
Date: Mon, 4 Oct 2004 23:46:43 +0300
Subject: [sane-devel] FreeBSD 5.2.1 and Mustek 2400CU Plus
Message-ID: <200410042346.43883.shirshegsm@delfi.lt>

Hello.

I'm using FreeBSD 5.2.1-RELEASE on i386 and sane-backends-1.0.14_1 (from 
ports). Also I have Mustek 2400CU Plus connected to USB port.

My problem is that after scanning something I have to reattach my scanner 
(detach and attach again the USB cable), because SANE doesn't find my scanner 
anymore.

Here's what I get when plugging in my scanner at the first time:

%scanimage -L
device `gt68xx:libusb:/dev/usb0:/dev/ugen0' is a Mustek BearPaw 2400 CU Plus 
flatbed scanner

And then I scan something...

%scanimage > picture.pnm

...and when I'm trying to try scanning again I get:

%scanimage -L
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

I've checked output of usbdevs (command, which shows attached USB devices). 
Before scanning:

%usbdevs
addr 1: UHCI root hub, VIA
 addr 2: USB Scanner, Mustek Systems

...and after:
%usbdevs
addr 1: UHCI root hub, VIA
 addr 2: ?????, Mustek Systems

It looks like that after using my BearPaw, system can't find out that device 
on addr 1 is a scanner. Also, when I'm scanning multiple pages with scanadf, 
I can scan them all (I don't get "No scanners were identified" error between 
scans).

Here's some debug output:

first scan:
%env SANE_DEBUG_GT68XX=255 scanimage > /dev/null
<...>
[gt68xx] sane_read: scan complete: 3973 bytes, 9080709 total
[gt68xx] sane_read: start (line 3543 of 3543, byte_count 2563 of 2563)
[gt68xx] sane_read: nothing more to scan: EOF
[gt68xx] sane_cancel: start
[gt68xx] sane_cancel: scan finished, scanned 9080709 bytes in 56 seconds
[gt68xx] gt68xx_line_reader_free: enter
[gt68xx] gt68xx_device_read_finish: read_bytes_left = 0
[gt68xx] gt68xx_line_reader_free: leave
[gt68xx] gt68xx_device_generic_req: command=0x41
[gt68xx] >> 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 
00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 0000 00 00 00 00 
41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00
[gt68xx] << 00 41 b3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] gt68xx_device_generic_req: command=0x17
[gt68xx] >> 17 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] << 00 17 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] gt68xx_device_generic_req: command=0x24
[gt68xx] >> 24 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] << 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] sane_cancel: exit
[gt68xx] sane_close: start
[gt68xx] gt68xx_device_generic_req: command=0x25
[gt68xx] >> 25 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] << 00 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[gt68xx] gt68xx_device_close: enter: dev=0x8059800
[gt68xx] gt68xx_device_close: leave: ok
[gt68xx] gt68xx_calibrator_free: enter
[gt68xx] gt68xx_calibrator_free: min_clip_count=0, max_clip_count=0
[gt68xx] gt68xx_calibrator_free: leave: ok
[gt68xx] gt68xx_calibrator_free: enter
[gt68xx] gt68xx_calibrator_free: min_clip_count=518050, max_clip_count=4
[gt68xx] gt68xx_calibrator_free: leave: ok
[gt68xx] gt68xx_calibrator_free: enter
[gt68xx] gt68xx_calibrator_free: min_clip_count=0, max_clip_count=0
[gt68xx] gt68xx_calibrator_free: leave: ok
[gt68xx] sane_close: exit
[gt68xx] sane_exit: start
[gt68xx] gt68xx_device_free: enter: dev=0x8059800
[gt68xx] gt68xx_device_free: freeing dev
[gt68xx] gt68xx_device_free: leave: ok
[gt68xx] sane_exit: exit

second scan:
%env SANE_DEBUG_GT68XX=255 scanimage > /dev/null
[sanei_debug] Setting debug level of gt68xx to 255.
[gt68xx] SANE GT68xx backend version 1.0 build 60 from sane-backends 1.0.14
[gt68xx] sane_init: authorize != null
[gt68xx] sane_init: debug options are enabled, handle with care
[gt68xx] sane_init: little endian machine
[gt68xx] sane_init: reading config file `gt68xx.conf'
<...>
[gt68xx] sane_init: config file line 96: trying to attach `usb 0x055f 0x021d'
<...>
[gt68xx] sane_init: exit
[gt68xx] sane_get_devices: start: local_only = false
[gt68xx] sane_get_devices: exit
scanimage: no SANE devices found
[gt68xx] sane_exit: start
[gt68xx] sane_exit: exit

I'm using PS2Dfw.usb backend (which is identical to Mustek's provided in 
installation CD - by the way, my BearPaw on Windows works just fine).

Yes, I know that reattaching the cable is not a big deal. But I want to know 
what's wrong, how to fix it and what can I do to work it properly... ;-)

Can you help me with this?

Respectfully Yours,

Linas Valiukas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x692E662F8F8ECEFE588CC55CDBA23BED89508A29.asc
Type: application/pgp-keys
Size: 1351 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041004/3a5b84a4/attachment.key>

From karsten.festag at gmx.de  Mon Oct  4 22:52:55 2004
From: karsten.festag at gmx.de (Karsten Festag)
Date: Mon, 4 Oct 2004 23:52:55 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <20041003132048.GH7885@meier-geinitz.de>
References: <20041003125857.GG7885@meier-geinitz.de> <20041003132048.GH7885@meier-geinitz.de>
Message-ID: <200410042352.55031.karsten.festag@gmx.de>

Hi,

Henning, thanks for updating the backend.
I recently replaced my old microtek parallelport scannner with an Epson 2480 
(what a difference!) and I think I will stop working on the microtek2 
backend. But finally I would like to commit the changes I collected in the 
last time so they don't get lost. Henning, I'll send you the current files 
for the CVS, (I don't think I will need CVS access). They include the changes 
you made.
I tried to test todays CVS version on my old machine with the old scanner and 
I experienced a compilation problem:

make[1]: Wechsel in das Verzeichnis 
Verzeichnis /home/karsten/tmp/sane-backends/tools
gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes 
-pedantic -ansi -DHAVE_CONFIG_H -I. -I. -I../include -I../include 
-DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d      
-DPATH_SANE_DATA_DIR=/usr/local/share           -DV_MAJOR=1 -DV_MINOR=0 
sane-find-scanner.c
sane-find-scanner.c: In function `parse_file':
sane-find-scanner.c:973: warning: implicit declaration of function 
`check_libusb_device'
sane-find-scanner.c:974: sizeof applied to an incomplete type
[...much more of this...]
sane-find-scanner.c:1070: dereferencing pointer to incomplete type
sane-find-scanner.c:1073: dereferencing pointer to incomplete type
make[1]: *** [sane-find-scanner.o] Fehler 1
make[1]: Verlassen des Verzeichnisses 
Verzeichnis /home/karsten/tmp/sane-backends/tools
make: *** [all-recursive] Fehler 1

Looks like a libusb issue? I don't have libusb installed on the old machine 
but I ran configure with --disable-libusb so I expected no problems. 
Compiling on the new machine (which has libusb) works, but the 2.6 Kernel 
doesn't have ppscsi support so I can't test the backend right now.

Regards,

Karsten


On Sunday 03 October 2004 15:20, Henning Meier-Geinitz wrote:
> Hi again,
>
> Also a work-around to fix scanning on the microtek phantom c6 on big
> endian platforms has been committed to SANE CVS. Please everyone check
> if that doesn't break anything.
>
> I'm especially interested in reports from users of big endian systems.
>
> Here is the bug report:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23274523
>
> Karsten: I've applied both patches as you don't seem to have committed
> changes to the microtek2 backend for quite some time. If you want to
> become active again, details on getting CVS access are here:
> http://www.sane-project.org/cvs.html
>
> Bye,
>   Henning



From janer at mail.datanet.hu  Mon Oct  4 19:47:03 2004
From: janer at mail.datanet.hu (Jeney =?iso-8859-1?q?J=E1nos?=)
Date: Mon, 4 Oct 2004 20:47:03 +0200
Subject: [sane-devel] Lide 80
Message-ID: <200410042047.03317.janer@mail.datanet.hu>

Has anyone tried the Canon LIDE 80 with sane? Is any other scanner supported 
that scans negatives??
Janos



From henning at meier-geinitz.de  Tue Oct  5 10:46:03 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 11:46:03 +0200
Subject: [sane-devel] FreeBSD 5.2.1 and Mustek 2400CU Plus
In-Reply-To: <200410042346.43883.shirshegsm@delfi.lt>
References: <200410042346.43883.shirshegsm@delfi.lt>
Message-ID: <20041005094603.GA7772@meier-geinitz.de>

Hi,

On Mon, Oct 04, 2004 at 11:46:43PM +0300, Linas Valiukas wrote:
> I'm using FreeBSD 5.2.1-RELEASE on i386 and sane-backends-1.0.14_1 (from 
> ports). Also I have Mustek 2400CU Plus connected to USB port.
> 
> My problem is that after scanning something I have to reattach my scanner 
> (detach and attach again the USB cable), because SANE doesn't find my scanner 
> anymore.

That's a known issue. It happens with all scanners supported by the
gt68xx backend on all *BSD systems I've tested. I've tried to find the
reason for this but haven't been successful until now. But I'll try
again.

> I've checked output of usbdevs (command, which shows attached USB devices). 
> Before scanning:
> 
> %usbdevs
> addr 1: UHCI root hub, VIA
>  addr 2: USB Scanner, Mustek Systems
> 
> ...and after:
> %usbdevs
> addr 1: UHCI root hub, VIA
>  addr 2: ?????, Mustek Systems

If you enable debugging for USB (SANE_DEBUG_SANEI_USB=255) you'll see
that the scanner doesn't respond to a request sending its descriptors
after the first scan.

> It looks like that after using my BearPaw, system can't find out that device 
> on addr 1 is a scanner. Also, when I'm scanning multiple pages with scanadf, 
> I can scan them all (I don't get "No scanners were identified" error between 
> scans).

The error happens after the scanner is accessed AND its file
descriptor is closed for the first time. E.g. you can scan using xsane
for multiple times as long as you don't close xsane.

Bye,
  Henning



From henning at meier-geinitz.de  Tue Oct  5 10:49:36 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 11:49:36 +0200
Subject: [sane-devel] Lide 80
In-Reply-To: <200410042047.03317.janer@mail.datanet.hu>
References: <200410042047.03317.janer@mail.datanet.hu>
Message-ID: <20041005094936.GB7772@meier-geinitz.de>

Hi,

On Mon, Oct 04, 2004 at 08:47:03PM +0200, Jeney J?nos wrote:
> Has anyone tried the Canon LIDE 80 with sane?

It's unsupported, see out scanner lists.

> Is any other scanner supported 
> that scans negatives??

E.g. the some of the Mustek BearPaw TA scanners are supported and can
scan negatives. But as they are flatbed scanners, scan quality won't
be as good as with "real" slide/negative scanners.

Bye,
  Henning



From henning at meier-geinitz.de  Tue Oct  5 11:50:18 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 12:50:18 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <200410042352.55031.karsten.festag@gmx.de>
References: <20041003125857.GG7885@meier-geinitz.de> <20041003132048.GH7885@meier-geinitz.de> <200410042352.55031.karsten.festag@gmx.de>
Message-ID: <20041005105018.GE7772@meier-geinitz.de>

Hi,

On Mon, Oct 04, 2004 at 11:52:55PM +0200, Karsten Festag wrote:
> I recently replaced my old microtek parallelport scannner with an Epson 2480 
> (what a difference!) and I think I will stop working on the microtek2 
> backend. But finally I would like to commit the changes I collected in the 
> last time so they don't get lost. Henning, I'll send you the current files 
> for the CVS, (I don't think I will need CVS access). They include the changes 
> you made.

One issue:
(line 4657):
    if ( !(md->revision=='2.70') && (md->model_flags & MD_RII_TWO_BYTES) )

That looks strange. I've removed the quotes around the 2.70 but you
should double-check if that works.

I've committed your backend to CVS now.

What about the microtek2.desc file? Shouldn't at least the version
number (currently 0.95) be increased? Why not just use the build number?

Is the Microtek Colorpage-EP a newly supported scanner? That one
should also show up in our scanner lists. Is it support complete,
good, basic or minimal?


> I tried to test todays CVS version on my old machine with the old scanner and 
> I experienced a compilation problem:

That was my fault. It's fixed now.

By the way: Could you change all references (e.g. on your website) to
mostang.com to www.sane-project.org? 

Bye,
  Henning



From henning at meier-geinitz.de  Tue Oct  5 12:24:31 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 13:24:31 +0200
Subject: [sane-devel] Timetable for release of sane-frontends 1.0.13
Message-ID: <20041005112430.GF7772@meier-geinitz.de>

Hi,

That's the timetable for the release of sane-frontends 1.0.13:

2004-10-10 Feature freeze (a snapshot will be made)
2004-10-17 Release

Please test sane-frontends and add any fixes to CVS now.

Bye,
  Henning



From henning at meier-geinitz.de  Tue Oct  5 12:32:02 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 13:32:02 +0200
Subject: [sane-devel] Timetable for the release of sane-backends-1.0.15
Message-ID: <20041005113202.GG7772@meier-geinitz.de>

Hi,

This is the timetable for the release of sane-backends 1.0.15

2004-10-17 Feature freeze (snapshot)
2004-10-31 Code freeze (snapshot)
2004-11-07 Release

Feature freeze means that only bug fixes and documentation updates are
allowed. After code freeze only fixes of grave bugs that render a
backend completely unusable or break compilation and documentation
updates are accepted.

If there are any new backends that should be included in that release
please tell us NOW.

Please everyone have a look at out growing list of bugs and fix as
many bugs as possible:
http://alioth.debian.org/tracker/index.php?group_id=30186&atid=410366

Or, if the bug report is bogus, close it.
You can view only bugs assigned to you to reduce the number of visible
bugs. Having a look at bugs assigned to nobody is also worth a try as
some bugs affect several backends/maintainers. You can also sort by
topic ("Summary").

Bye,
  Henning



From jb at jblache.org  Tue Oct  5 12:37:53 2004
From: jb at jblache.org (Julien BLACHE)
Date: Tue, 05 Oct 2004 13:37:53 +0200
Subject: [sane-devel] Timetable for release of sane-frontends 1.0.13
In-Reply-To: <20041005112430.GF7772@meier-geinitz.de> (Henning
 Meier-Geinitz's message of "Tue, 5 Oct 2004 13:24:31 +0200")
References: <20041005112430.GF7772@meier-geinitz.de>
Message-ID: <874ql9cs4u.fsf@frigate.technologeek.org>

Henning Meier-Geinitz <henning at meier-geinitz.de> wrote:

Hi,

> 2004-10-10 Feature freeze (a snapshot will be made)
> 2004-10-17 Release
>
> Please test sane-frontends and add any fixes to CVS now.

I have icons for xscanimage and xcam sitting in my inbox. I'll dig
them up and eventually add them to the CVS (more on that on IRC).

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb at jblache.org>                                  GPG KeyID 0xF5D65169



From david at phenix.fr  Tue Oct  5 14:52:28 2004
From: david at phenix.fr (Dave Neary)
Date: Tue, 05 Oct 2004 15:52:28 +0200
Subject: [sane-devel] Re: Timetable for the release of sane-backends-1.0.15 (Henning Meier-Geinitz)
In-Reply-To: <20041005133248.27973.49959.Mailman@haydn.debian.org>
References: <20041005133248.27973.49959.Mailman@haydn.debian.org>
Message-ID: <4162A71C.5090101@phenix.fr>

Hi,

Henning said:
> 2004-10-17 Feature freeze (snapshot)
> 2004-10-31 Code freeze (snapshot)
> 2004-11-07 Release
> 
> Feature freeze means that only bug fixes and documentation updates are
> allowed. After code freeze only fixes of grave bugs that render a
> backend completely unusable or break compilation and documentation
> updates are accepted.

I would like to have a go at fitting the changes we made to the Windows 
version of net into CVS before this. Is there a bugzilla where I can 
attach a final patch file? Or should I send it here?

Cheers,
Dave.

-- 
David Neary
Phenix Engineering
110 ave Jean Jaures, 69007 Lyon



From henning at meier-geinitz.de  Tue Oct  5 15:01:42 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 5 Oct 2004 16:01:42 +0200
Subject: [sane-devel] Re: Timetable for the release of sane-backends-1.0.15 (Henning Meier-Geinitz)
In-Reply-To: <4162A71C.5090101@phenix.fr>
References: <20041005133248.27973.49959.Mailman@haydn.debian.org> <4162A71C.5090101@phenix.fr>
Message-ID: <20041005140142.GI7772@meier-geinitz.de>

Hi,

On Tue, Oct 05, 2004 at 03:52:28PM +0200, Dave Neary wrote:
> I would like to have a go at fitting the changes we made to the Windows 
> version of net into CVS before this. Is there a bugzilla where I can 
> attach a final patch file?

https://alioth.debian.org/tracker/?atid=410366&group_id=30186&func=browse

Please use a unified diff.

Bye,
  Henning



From kpeters at LHSolutions.com  Tue Oct  5 19:38:36 2004
From: kpeters at LHSolutions.com (Kenneth H. Peters)
Date: Tue, 5 Oct 2004 14:38:36 -0400
Subject: [sane-devel] Interesting image problem when scanning color ...
Message-ID: <00cb01c4ab0a$8731ff80$6601a8c0@khp5000elaptop>

Folks:

 

I am using the following:

 

*	IXP425 Big-endian
*	MontaVista 2.4.18 kernel
*	SANE 1.0.14
*	Plustek backend
*	Scanimage as frontend
*	Canon LiDE 30
*	USB 1.1

 

Issue: Able to scan with "-mode Gray" and "-mode Binary", however using
"Color" produces images as shown in image-segment below. 

 



 

Analysis: Seems to be getting 1/3 more data in the X direction that is
"wrapping" around the image in the X direction.

 

I am interested in learning if anyone has seen this behavior. 

 

I thank you in advance for any insights you can provide. 

 

Thanks,

K.P.

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041005/1ee680f4/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 14708 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041005/1ee680f4/attachment.jpg>

From karsten.festag at gmx.de  Tue Oct  5 21:44:47 2004
From: karsten.festag at gmx.de (Karsten Festag)
Date: Tue, 5 Oct 2004 22:44:47 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <20041005105018.GE7772@meier-geinitz.de>
References: <20041003125857.GG7885@meier-geinitz.de> <200410042352.55031.karsten.festag@gmx.de> <20041005105018.GE7772@meier-geinitz.de>
Message-ID: <200410052244.47533.karsten.festag@gmx.de>

Hi,

On Tuesday 05 October 2004 12:50, Henning Meier-Geinitz wrote:
> Hi,
>
> On Mon, Oct 04, 2004 at 11:52:55PM +0200, Karsten Festag wrote:
> > I recently replaced my old microtek parallelport scannner with an Epson
> > 2480 (what a difference!) and I think I will stop working on the
> > microtek2 backend. But finally I would like to commit the changes I
> > collected in the last time so they don't get lost. Henning, I'll send you
> > the current files for the CVS, (I don't think I will need CVS access).
> > They include the changes you made.
>
> One issue:
> (line 4657):
>     if ( !(md->revision=='2.70') && (md->model_flags & MD_RII_TWO_BYTES) )
>
> That looks strange. I've removed the quotes around the 2.70 but you
> should double-check if that works.

It's o.k., the quotes were a mistake.

>
> I've committed your backend to CVS now.

Thanks! 
>
> What about the microtek2.desc file? Shouldn't at least the version
> number (currently 0.95) be increased? Why not just use the build number?
>
> Is the Microtek Colorpage-EP a newly supported scanner? That one
> should also show up in our scanner lists. Is it support complete,
> good, basic or minimal?

The Genius ColorPage-EP is a OEM version of the Microtek Scanmaker V300. It 
has an additional firmware peculiarity I had to handle so that the support is 
good, like the V300.
I attach the updated microtek2.desc file. I called the recent version 0.96, I 
used the build number only for internal referencing. Could you please change 
MICROTEK2_MINOR in microtek2.h accordingly?

>
> > I tried to test todays CVS version on my old machine with the old scanner
> > and I experienced a compilation problem:
>
> That was my fault. It's fixed now.

I tested again and I get some other errors:

gcc -o sane-find-scanner sane-find-scanner.o 
check-usb-chip.o ../backend/.libs/sane_strstatus.o  ../sanei/libsanei.a ../lib/liblib.a 
-lnsl -lm /usr/lib/libjpeg.so
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
.../sanei/libsanei.a(sanei_scsi.o): In function `lx_mk_devicename':
:2491: undefined reference to `rsm_open_device'
:2491: undefined reference to `rsm_open_device'
.../sanei/libsanei.a(sanei_scsi.o): In function `get_max_buffer_size':
:781: undefined reference to `rsm_open_device'
.../sanei/libsanei.a(sanei_scsi.o): In function `sanei_scsi_open_extended':
:1245: undefined reference to `rsm_open_device'
:1245: undefined reference to `rsm_open_device'
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Could not find abbrev number 186.
.../sanei/libsanei.a(sanei_config.o): In function `sanei_config_read':
sanei_config.o(.text+0x36): undefined reference to `__ctype_b_loc'
sanei_config.o(.text+0x51): undefined reference to `__ctype_b_loc'
.../sanei/libsanei.a(sanei_config.o): In function 
`sanei_config_skip_whitespace':
sanei_config.o(.text+0xaa): undefined reference to `__ctype_b_loc'
.../sanei/libsanei.a(sanei_config.o): In function `sanei_config_get_string':
sanei_config.o(.text+0xf3): undefined reference to `__ctype_b_loc'
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
.../sanei/libsanei.a(sanei_usb.o): In function `sanei_usb_open':
:720: undefined reference to `rsm_open_device'
.../sanei/libsanei.a(sanei_usb.o): In function `sanei_usb_init':
:276: undefined reference to `rsm_open_device'
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
/usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
.../sanei/libsanei.a(sanei_init_debug.o): In function `sanei_init_debug':
:81: undefined reference to `__ctype_toupper_loc'
collect2: ld returned 1 exit status
make[1]: *** [sane-find-scanner] Fehler 1
make[1]: Verlassen des Verzeichnisses 
Verzeichnis /home/karsten/tmp/sane-backends/tools
make: *** [all-recursive] Fehler 1


>
> By the way: Could you change all references (e.g. on your website) to
> mostang.com to www.sane-project.org?

If I didn't forget something, this is done now.

Bye, Karsten
-------------- next part --------------
;
; SANE Backend specification file
;
; It's basically emacs-lisp --- so ";" indicates comment to end of line.
; All syntactic elements are keyword tokens, followed by a string or
;  keyword argument, as specified.
;
; ":backend" *must* be specified.
; All other information is optional (but what good is the file without it?).
;

:backend "microtek2"              ; name of backend
:version "0.96"                   ; version of backend
;:status :alpha                   ; :alpha, :beta, :stable, :new
:manpage "sane-microtek2"         ; name of manpage (if it exists)
:url "http://karstenfestag.gmxhome.de"

:devicetype :scanner              ; start of a list of devices....

:mfg "Microtek"                   ; name a manufacturer
:url "http://www.microtek.com/"

:model "ScanMaker E3plus"
:interface "Parport"
:status :complete

:model "ScanMaker E3plus"         ; name models for above-specified mfg.
:interface "SCSI"
:status :complete

:model "ScanMaker X6"
:interface "SCSI"
:status :complete

:model "ScanMaker X6EL"
:interface "SCSI"
:status :basic

:model "ScanMaker X6USB"
:interface "USB"
:status :good

:model "ScanMaker V300"
:interface "SCSI"
:status :good

:model "ScanMaker V300"
:interface "Parport"
:status :good

:model "ScanMaker V310"
:interface "SCSI"
:status :basic

:model "ScanMaker V310"
:interface "Parport"
:status :basic

:model "ScanMaker V600"
:interface "SCSI"
:status :basic

:model "ScanMaker V600"
:interface "Parport"
:status :basic

:model "ScanMaker 330"
:interface "SCSI"
:status :basic

:model "ScanMaker 630"
:interface "SCSI"
:status :basic

:model "ScanMaker 636"
:interface "SCSI"
:status :complete

:model "ScanMaker 9600XL"
:interface "SCSI"
:comment "only flatbed mode ?"
:status :good

;:model "ScanMaker 9600XL"
;:interface "SCSI"
;:status :minimal

:model "Phantom 330CX"
:interface "Parport"
:status :complete

:model "SlimScan C3"
:interface "Parport"
:status :complete

:model "Phantom 636"
:interface "SCSI"
:status :complete

:model "Phantom 636CX"
:interface "Parport"
:status :complete

:model "SlimScan C6"
:interface "USB"
:status :complete

:model "ScanMaker V6USL"
:interface "SCSI"
:status :complete

:model "ScanMaker V6USL"
:interface "USB"
:status :complete

:model "ScanMaker X12USL"
:interface "SCSI"
:comment "only Flatbed mode ?"
:status :good

:mfg "Vobis"
:url "http://www.vobis.de/"

:model "HighScan"                 ; name models for above-specified mfg.
:interface "SCSI"
:comment "only E3plus based models"
:status :complete

:mfg "Scanport"
:url "http://www.scanport.com/"
:model "SQ300"
:interface "Parport?"
:status :basic

:model "SQ2030"
:interface "Parport"
:status :basic

:model "SQ4836"
:interface "SCSI"
:status :basic

:mfg "Genius"
:url "http://www.geniusmouse.co.uk/"
:model "ColorPage-EP"
:interface "Parport"
:status :good


From gerhard at gjaeger.de  Wed Oct  6 07:42:50 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Wed, 6 Oct 2004 08:42:50 +0200
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <00cb01c4ab0a$8731ff80$6601a8c0@khp5000elaptop>
References: <00cb01c4ab0a$8731ff80$6601a8c0@khp5000elaptop>
Message-ID: <200410060842.50352.gerhard@gjaeger.de>

Hi,

On Tuesday 05 October 2004 20:38, Kenneth H. Peters wrote:
> I am using the following:
> *	IXP425 Big-endian
> *	MontaVista 2.4.18 kernel
> *	SANE 1.0.14
> *	Plustek backend
> *	Scanimage as frontend
> *	Canon LiDE 30
> *	USB 1.1
> Issue: Able to scan with "-mode Gray" and "-mode Binary", however using
> "Color" produces images as shown in image-segment below.
> Analysis: Seems to be getting 1/3 more data in the X direction that is
> "wrapping" around the image in the X direction.
>
> I am interested in learning if anyone has seen this behavior.
>
looks strange, can you please test again with the latest CVS snapshot?
I've no problems here.

Gerhard




From gerhard at gjaeger.de  Wed Oct  6 07:57:42 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Wed, 6 Oct 2004 08:57:42 +0200
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <00cb01c4ab0a$8731ff80$6601a8c0@khp5000elaptop>
References: <00cb01c4ab0a$8731ff80$6601a8c0@khp5000elaptop>
Message-ID: <200410060857.42745.gerhard@gjaeger.de>

Hi,

On Tuesday 05 October 2004 20:38, Kenneth H. Peters wrote:
> I am using the following:
> *	IXP425 Big-endian
> *	MontaVista 2.4.18 kernel
> *	SANE 1.0.14
> *	Plustek backend
> *	Scanimage as frontend
> *	Canon LiDE 30
> *	USB 1.1
>
in my first post, I missed the "Big-endian" issue!!!!
As I don't have a big endian machine available, it might be, that
there's such a problem.
Can you please do a scan @ 50dpi and @300dpi, always with
SANE_DEBUG_PLUSTEK=20 ?
Send us these outputs. 

Ciao, 
  Gerhard




From scottf at bigpond.net.au  Wed Oct  6 09:59:47 2004
From: scottf at bigpond.net.au (scott fagg)
Date: Wed, 6 Oct 2004 18:59:47 +1000
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain>
References: <415BD75B.1060103@bigpond.net.au> <200410021716.46218.Oliver.Schwartz@gmx.de>
 <Pine.LNX.4.53.0410041806350.16694@localhost.localdomain>
 <200410042026.59822.Oliver.Schwartz@gmx.de> <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain>
Message-ID: <Pine.LNX.4.53.0410061856300.13865@localhost.localdomain>

On Tue, 5 Oct 2004, scott fagg wrote:

> Date: Tue, 05 Oct 2004 06:25:57 +1000
> From: scott fagg <scottf at bigpond.net.au>
> To: Oliver Schwartz <Oliver.Schwartz at gmx.de>
> Cc: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] epson 2580 problems
>
> On Mon, 4 Oct 2004, Oliver Schwartz wrote:
>
> > Date: Mon, 04 Oct 2004 20:26:57 +0200
> > From: Oliver Schwartz <Oliver.Schwartz at gmx.de>
> > To: sane-devel at lists.alioth.debian.org
> > Subject: Re: [sane-devel] epson 2580 problems
> >
> > Hi,
> >
> > > > please repeat the test by running
> > > > "SANE_DEBUG_SNAPSCAN=255 scanimage >/tmp/junk.bin 2>debug.log"
> > > > and send me the debug.log file.
> > >
> > > I've sent you a copy directly.
> >
> > The first three lines of the log read
> >
> > [sanei_debug] Setting debug level of snapscan to 255.
> > [snapscan] sane_snapscan_init
> > [snapscan] sane_snapscan_init: Snapscan backend version 1.4.35
> >
> > And later
> >
> > [snapscan] sane_snapscan_open (after firmware upload): "EPSON
> > Scanner1" is not a supported scanner
> >
> > It seems you're using an old version of the snapscan backend. The
> > backend revision should say "1.4.40" if you use the CVS version.
> > Since you wrote earlier that you're using a fairly recent CVS
> > snapshot you probably have two versions of SANE installed (e.g. one
> > in /usr/lib/sane and one in /usr/local/lib/sane).
>
> That might explain why i had some success earlier on, but none now. I'll
> track down all copies, clean up and try again.

Using the latest drivers helps and i can now scan, however preview doesn't
work. At least i can get an image out of it now.

It seems to only preview either the area of the most recent scan or
nothing, and then stretches that image vertically to fit the A4 scannable
area and shows that as a preview.

>
> >
> > /Oliver
> >
> > --
> > sane-devel mailing list: sane-devel at lists.alioth.debian.org
> > http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> > Unsubscribe: Send mail with subject "unsubscribe your_password"
> >              to sane-devel-request at lists.alioth.debian.org
> >
>
> --
> scottf at bigpond.net.au
>
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org
>

--
scottf at bigpond.net.au




From henning at meier-geinitz.de  Wed Oct  6 12:09:02 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 6 Oct 2004 13:09:02 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <200410052244.47533.karsten.festag@gmx.de>
References: <20041003125857.GG7885@meier-geinitz.de> <200410042352.55031.karsten.festag@gmx.de> <20041005105018.GE7772@meier-geinitz.de> <200410052244.47533.karsten.festag@gmx.de>
Message-ID: <20041006110901.GC10804@meier-geinitz.de>

Hi,

On Tue, Oct 05, 2004 at 10:44:47PM +0200, Karsten Festag wrote:
> The Genius ColorPage-EP is a OEM version of the Microtek Scanmaker V300. It 
> has an additional firmware peculiarity I had to handle so that the support is 
> good, like the V300.
> I attach the updated microtek2.desc file. I called the recent version 0.96, I 
> used the build number only for internal referencing. Could you please change 
> MICROTEK2_MINOR in microtek2.h accordingly?

Done. I've also removed the Genius from the unsupported scanners list.

> > > I tried to test todays CVS version on my old machine with the old scanner
> > > and I experienced a compilation problem:
> >
> > That was my fault. It's fixed now.
> 
> I tested again and I get some other errors:
> 
> gcc -o sane-find-scanner sane-find-scanner.o 
> check-usb-chip.o ../backend/.libs/sane_strstatus.o  ../sanei/libsanei.a ../lib/liblib.a 
> -lnsl -lm /usr/lib/libjpeg.so
> /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.

Check what the dwarfs are doing inside your computer :-)
I've never seen such an error message.

> /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
> /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
> .../sanei/libsanei.a(sanei_scsi.o): In function `lx_mk_devicename':
> :2491: undefined reference to `rsm_open_device'

Looks like linking to the resource manage library failed. In fact,
it's not in the list of linked libraries after the gcc command.

However, the call is inside #ifdef HAVE_RESMGR so something must have
defined that.

Does the same happen after "make distclean; ./configure; make"?

In this case, check config.log for "resmgr".

There is a small error in the configure script that I've fixed now in
CVS. However, I'm not sure if it can cause that misdetection.


> .../sanei/libsanei.a(sanei_config.o): In function `sanei_config_read':
> sanei_config.o(.text+0x36): undefined reference to `__ctype_b_loc'
> sanei_config.o(.text+0x51): undefined reference to `__ctype_b_loc'

That's even more strange. Looks like some internal error?

Can you please show us the compilation warnings you get in sanei/ (not
only the linker errors)?


Bye,
  Henning



From vsu at altlinux.ru  Wed Oct  6 12:47:52 2004
From: vsu at altlinux.ru (Sergey Vlasov)
Date: Wed, 6 Oct 2004 15:47:52 +0400
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <200410052244.47533.karsten.festag@gmx.de>
References: <20041003125857.GG7885@meier-geinitz.de> <200410042352.55031.karsten.festag@gmx.de> <20041005105018.GE7772@meier-geinitz.de> <200410052244.47533.karsten.festag@gmx.de>
Message-ID: <20041006114752.GA14845@master.mivlgu.local>

On Tue, Oct 05, 2004 at 10:44:47PM +0200, Karsten Festag wrote:
> .../sanei/libsanei.a(sanei_config.o): In function `sanei_config_read':
> sanei_config.o(.text+0x36): undefined reference to `__ctype_b_loc'
> sanei_config.o(.text+0x51): undefined reference to `__ctype_b_loc'

Looks like this object file was compiled with glibc-2.3.x headers, but is
being linked with an older glibc.  This won't work - run "make clean" and
recompile everything with the proper headers.

> /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.

This also might be caused by "too recent" object files from another
machine.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041006/a56d27e3/attachment.sig>

From techjedi at gmail.com  Wed Oct  6 19:22:31 2004
From: techjedi at gmail.com (Chris McKeever)
Date: Wed, 6 Oct 2004 13:22:31 -0500
Subject: [sane-devel] strange problems
Message-ID: <d9aa9070410061122270e5a94@mail.gmail.com>

I have been wrestling with this for a while now, and not turning up
much through searching the web.  I have installed SANE 
sane-backends-1.0.14 and have a CANON lide30 scanner.
At low resolutions it will process fine.  If I go to 300 is fails at
about 75% and anyhting higher wont even start.

I had it working with an LIDE20 - until that unit crapped out - the
optic bar would just pin itself to the edge and grind.

I am connecting to the SANE backend via XSANE from a remote linux box
as well as a remote windows box - very similar results (the connection
itself works, just scanning isnt working well)

Any suggestions?

thanks



From Oliver.Schwartz at gmx.de  Wed Oct  6 19:29:47 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Wed, 6 Oct 2004 20:29:47 +0200
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <Pine.LNX.4.53.0410061856300.13865@localhost.localdomain>
References: <415BD75B.1060103@bigpond.net.au> <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain> <Pine.LNX.4.53.0410061856300.13865@localhost.localdomain>
Message-ID: <200410062029.50935.Oliver.Schwartz@gmx.de>

Hi,

> Using the latest drivers helps and i can now scan, however preview
> doesn't work. At least i can get an image out of it now.
>
> It seems to only preview either the area of the most recent scan or
> nothing, and then stretches that image vertically to fit the A4
> scannable area and shows that as a preview.

Please send me a debug log of a preview scan.

/Oliver



From techjedi at gmail.com  Wed Oct  6 20:29:33 2004
From: techjedi at gmail.com (Chris McKeever)
Date: Wed, 6 Oct 2004 14:29:33 -0500
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <d9aa9070410061122270e5a94@mail.gmail.com>
References: <d9aa9070410061122270e5a94@mail.gmail.com>
Message-ID: <d9aa90704100612297776dd31@mail.gmail.com>

some more tests get me some new results.

1 - I have noticed that with 3 different USB 2.0 cards, that the
scanner will not register itself as a USB 2.0 device, it only
registers as a 1.1 (CD Wiriters register as 2.0, so I know that the
card and the kernel are recognizing it properly)

2 - I moved the scanner to the built-in USB 1.1 port, and I was able
to finish a scan at 300 DPI and 600 DPI (although it takes quite some
time)
3

3 - 1200 DPI still hangs, and letting it sit, I get: error during
read: error during device I/O.

any suggestions?

thanks




On Wed, 6 Oct 2004 13:22:31 -0500, Chris McKeever <techjedi at gmail.com> wrote:
> I have been wrestling with this for a while now, and not turning up
> much through searching the web.  I have installed SANE
> sane-backends-1.0.14 and have a CANON lide30 scanner.
> At low resolutions it will process fine.  If I go to 300 is fails at
> about 75% and anyhting higher wont even start.
> 
> I had it working with an LIDE20 - until that unit crapped out - the
> optic bar would just pin itself to the edge and grind.
> 
> I am connecting to the SANE backend via XSANE from a remote linux box
> as well as a remote windows box - very similar results (the connection
> itself works, just scanning isnt working well)
> 
> Any suggestions?
> 
> thanks
>



From karsten.festag at gmx.de  Wed Oct  6 20:34:07 2004
From: karsten.festag at gmx.de (Karsten Festag)
Date: Wed, 6 Oct 2004 21:34:07 +0200
Subject: [sane-devel] microtek2 backend users: please test CVS version of backend
In-Reply-To: <20041006110901.GC10804@meier-geinitz.de>
References: <20041003125857.GG7885@meier-geinitz.de> <200410052244.47533.karsten.festag@gmx.de> <20041006110901.GC10804@meier-geinitz.de>
Message-ID: <200410062134.07871.karsten.festag@gmx.de>

Hi,

>
> Check what the dwarfs are doing inside your computer :-)
> I've never seen such an error message.
>
> > /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM
....
> Does the same happen after "make distclean; ./configure; make"?
>
The dwarfs went back to work after "make distclean"! ;-) Sorry, that should 
have been my idea.
Testing with my scanner (Phantom330CX, Parport) was successful, so I 
personally have no objections against releasing this code.

all the best,

Karsten



From jurekt at kabatnet.waw.pl  Wed Oct  6 21:50:28 2004
From: jurekt at kabatnet.waw.pl (jurek Ela Tryjarscy)
Date: Wed, 06 Oct 2004 22:50:28 +0200
Subject: [sane-devel] No device available
Message-ID: <41645A94.1060007@kabatnet.waw.pl>

Hi ,
In my box I have Redhat 9.
I must connect via SCSI Interface Umax Mirage II scanner.
SCSI adapter is Acard AEC-6712TU.


During startup of computer the following communique appears:

    ROM Address: C800h
    I/O Port :           1000h
    IRQ Number  :    11(level)

SCANNING SCSI DEVICE

ID=    1    06(scanner)        UMAX    MIRAGE II    v1.4
ID=    7    * Host Adapter

NO HARD DIASK DETECT.    ON-BOARD BIOS DISABLE ...

( On the same box on another disk I've intalled Windows 98 and 
MgicScan32 V4.3 - scaner function well. )

Linux System logs contain:

Oct  4 19:19:05 localhost kernel:    ACARD AEC-671X PCI Ultra/W SCSI-3 
Host Adapter: 0    IO:1000, IRQ:11.
Oct  4 19:19:05 localhost kernel:          ID:  7  Host Adapter
Oct  4 19:19:05 localhost kernel: scsi0 : ACARD AEC-6710/6712/67160 PCI 
Ultra/W/LVD SCSI-3 Adapter Driver V2.6+ac

information.

Driver is atp870u.

My qustion is:
How to install correctly the scanner and the scsi adapter - I must make 
any mistake.
I do:
modprobe sg
modprobe atp870u

[root at localhost scsi]# lsmod
Module                  Size  Used by    Not tainted
atp870u                23856   0  (unused)
sg                     36524   0  (unused)
scsi_mod              107160   2  [atp870u sg]
ide-cd                 35676   0  (autoclean)
cdrom                  33728   0  (autoclean) [ide-cd]
parport_pc             19076   1  (autoclean)
lp                      8996   0  (autoclean)
parport                37056   1  (autoclean) [parport_pc lp]
autofs                 13268   0  (autoclean) (unused)
8139too                18120   1
mii                     3976   0  [8139too]
keybdev                 2976   0  (unused)
mousedev                5492   1
hid                    22148   0  (unused)
input                   5888   0  [keybdev mousedev hid]
usb-uhci               26348   0  (unused)
usbcore                78816   1  [hid usb-uhci]
ext3                   70784   2
jbd                    51892   2  [ext3]

[root at localhost root]# ls  /proc/scsi
atp870u  scsi

[root at localhost scsi]# more  scsi
Attached devices: none

I think it should be also sg directory in  /proc/scsi

[root at localhost root]# sane-find-scanner

# No SCSI scanners found. If you expected something different, make sure 
that
# you have loaded a SCSI driver for your SCSI adapter.
# Also you need support for SCSI Generic (sg) in your operating system.
# If using Linux, try "modprobe sg".

Can anyone help me ?

Jurek




From brian at aljex.com  Wed Oct  6 22:07:46 2004
From: brian at aljex.com (Brian K. White)
Date: Wed, 6 Oct 2004 17:07:46 -0400
Subject: [sane-devel] Re: strange problems LIDE30
References: <d9aa9070410061122270e5a94@mail.gmail.com> <d9aa90704100612297776dd31@mail.gmail.com>
Message-ID: <00af01c4abe8$98a1f610$6800000a@venti>

Chris McKeever wrote:
> some more tests get me some new results.
>
> 1 - I have noticed that with 3 different USB 2.0 cards, that the
> scanner will not register itself as a USB 2.0 device, it only
> registers as a 1.1 (CD Wiriters register as 2.0, so I know that the
> card and the kernel are recognizing it properly)
>
> 2 - I moved the scanner to the built-in USB 1.1 port, and I was able
> to finish a scan at 300 DPI and 600 DPI (although it takes quite some
> time)
> 3
>
> 3 - 1200 DPI still hangs, and letting it sit, I get: error during
> read: error during device I/O.
>
> any suggestions?
>
> thanks
>
>
>
>
> On Wed, 6 Oct 2004 13:22:31 -0500, Chris McKeever
> <techjedi at gmail.com> wrote:
>> I have been wrestling with this for a while now, and not turning up
>> much through searching the web.  I have installed SANE
>> sane-backends-1.0.14 and have a CANON lide30 scanner.
>> At low resolutions it will process fine.  If I go to 300 is fails at
>> about 75% and anyhting higher wont even start.
>>
>> I had it working with an LIDE20 - until that unit crapped out - the
>> optic bar would just pin itself to the edge and grind.
>>
>> I am connecting to the SANE backend via XSANE from a remote linux box
>> as well as a remote windows box - very similar results (the
>> connection itself works, just scanning isnt working well)
>>
>> Any suggestions?
>>
>> thanks

LiDE 30  _IS_ only a usb 1.1 device.
There are sloppily written advertisements on various shopping sites that 
list it as usb2.0 but in truth, the lide30 is usb1.1
Later lide50 is usb2.0
go to the canon site instead of guessing or trusting others (hey, including 
me :)

I have a 30 and a 2.0 card and went through the same motions you are and 
finally I did what I should have done first and consulted the only 
authoritative source and all mysteries were solved.

I never tried to scan at 1200 though, trying now...
Working...
It's going but incredibly slowly at 2400 full color (what bit depth is "full 
color"?)
The manufacturer says that it does 1200x2400 optically, but xsane only 
offers a listbox that says a single value from 0 to 2400, no XXXxYYY 
choices, so I picked 2400 just to go for a worst case scenario but I have no 
idea what it's actually going to do.
A lie, only actualy produce 1200x1200? a distorted image? silently double 
every pixel in one direction? silently double every pixel in both 
directions? or maybe the scanner will do the doubling in one direction in 
firmware and present sane with 2400x2400 data?

It's only at about 10 or 15% progress after 20 minutes so I'll send another 
post when it's done, or when it crashes.
This box has a gig of ram so hopefully it's enough for this worst-case 
scenario if sane doesn't open a file and work with smaller chunks in ram. 
This is a dual 1gig p3 too. That might be relevant by making it more likely 
that there is always a cpu available to service the usb interrups? Or 
rather, that the one cpu that seems to be the only one that even sees 
interrupts, is more likely to be able to keep up.

It's basically a straight suse personal 9.1 with yast configured to use 
ftp.ale.org

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani




From henning at meier-geinitz.de  Wed Oct  6 22:19:27 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 6 Oct 2004 23:19:27 +0200
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <00af01c4abe8$98a1f610$6800000a@venti>
References: <d9aa9070410061122270e5a94@mail.gmail.com> <d9aa90704100612297776dd31@mail.gmail.com> <00af01c4abe8$98a1f610$6800000a@venti>
Message-ID: <20041006211926.GA4132@meier-geinitz.de>

Hi,

On Wed, Oct 06, 2004 at 05:07:46PM -0400, Brian K. White wrote:
> The manufacturer says that it does 1200x2400 optically, but xsane only 
> offers a listbox that says a single value from 0 to 2400, no XXXxYYY 
> choices, so I picked 2400 just to go for a worst case scenario but I have 
> no idea what it's actually going to do.
> A lie, only actualy produce 1200x1200? a distorted image? silently double 
> every pixel in one direction? silently double every pixel in both 
> directions? or maybe the scanner will do the doubling in one direction in 
> firmware and present sane with 2400x2400 data?

As it doesn't make sense to crete distorted images SANE backends
usually either duplicate pixels or interpolate them.

I've seen several Windows drivers that interpolate even if it's not
necessary: E.g. harware resolution 100 and 200 dpi, driver uses 100
dpi when asked for 200.

Also some scanners are advertized to make 600x1200 dpi but can't do
(and don't do) 1200 dpi even vertically. It looks like nobody ever
checked what the Windows driver really scans.

I don't know what's the case with the LiDEs, however.

> It's only at about 10 or 15% progress after 20 minutes so I'll send another 
> post when it's done, or when it crashes.

At least with the scanners supported by the gt68xx backend, a low scan
width is important for higher speed at high resolutions. As you
usually use high resolutions for smaller sections of photos or slides
that's not that unreasonable.

> This box has a gig of ram so hopefully it's enough for this worst-case 
> scenario if sane doesn't open a file and work with smaller chunks in ram. 
> This is a dual 1gig p3 too. That might be relevant by making it more likely 
> that there is always a cpu available to service the usb interrups? Or 
> rather, that the one cpu that seems to be the only one that even sees 
> interrupts, is more likely to be able to keep up.

One of the problems is that libusb doesn't allow async i/o. So you
can't send some buffers to be filled and wait for their completion.

Bye,
  Henning



From adeuring at gmx.net  Wed Oct  6 22:30:46 2004
From: adeuring at gmx.net (abel deuring)
Date: Wed, 06 Oct 2004 23:30:46 +0200
Subject: [sane-devel] No device available
In-Reply-To: <41645A94.1060007@kabatnet.waw.pl>
References: <41645A94.1060007@kabatnet.waw.pl>
Message-ID: <41646406.6060704@gmx.net>

jurek Ela Tryjarscy wrote:
> Hi ,
> In my box I have Redhat 9.
> I must connect via SCSI Interface Umax Mirage II scanner.
> SCSI adapter is Acard AEC-6712TU.

> Linux System logs contain:
> 
> Oct  4 19:19:05 localhost kernel:    ACARD AEC-671X PCI Ultra/W SCSI-3 
> Host Adapter: 0    IO:1000, IRQ:11.
> Oct  4 19:19:05 localhost kernel:          ID:  7  Host Adapter
> Oct  4 19:19:05 localhost kernel: scsi0 : ACARD AEC-6710/6712/67160 PCI 
> Ultra/W/LVD SCSI-3 Adapter Driver V2.6+ac

I have never used the atp870u driver, but I assume that this driver 
should print some message about the devices it detected on the bus as 
other drivers do. In other words: for some reason it could not find the 
scanner.

> My qustion is:
> How to install correctly the scanner and the scsi adapter - I must make 
> any mistake.
> I do:
> modprobe sg
> modprobe atp870u
> 
> [root at localhost scsi]# lsmod
> Module                  Size  Used by    Not tainted
> atp870u                23856   0  (unused)
> sg                     36524   0  (unused)
> scsi_mod              107160   2  [atp870u sg]
> ide-cd                 35676   0  (autoclean)
> cdrom                  33728   0  (autoclean) [ide-cd]
> parport_pc             19076   1  (autoclean)
> lp                      8996   0  (autoclean)
> parport                37056   1  (autoclean) [parport_pc lp]
> autofs                 13268   0  (autoclean) (unused)
> 8139too                18120   1
> mii                     3976   0  [8139too]
> keybdev                 2976   0  (unused)
> mousedev                5492   1
> hid                    22148   0  (unused)
> input                   5888   0  [keybdev mousedev hid]
> usb-uhci               26348   0  (unused)
> usbcore                78816   1  [hid usb-uhci]
> ext3                   70784   2
> jbd                    51892   2  [ext3]
> 
> [root at localhost root]# ls  /proc/scsi
> atp870u  scsi
> 
> [root at localhost scsi]# more  scsi
> Attached devices: none

here you should get 3 lines describing the scanner.

> 
> I think it should be also sg directory in  /proc/scsi

yes -- but I don't know, if the SG driver creates this directory, if it 
does not see any devices.

> 
> [root at localhost root]# sane-find-scanner
> 
> # No SCSI scanners found. If you expected something different, make sure 
> that

that's because sane-find-scanner simply reads /proc/scsi/scsi, and this 
file is empty.

> # you have loaded a SCSI driver for your SCSI adapter.
> # Also you need support for SCSI Generic (sg) in your operating system.
> # If using Linux, try "modprobe sg".
> 
> Can anyone help me ?

I don't have a really good hint. The core problem is that the atp870u 
driver does not find the scanner, hence any attempt to access it will 
fail. Unfortunately the kernel sources don't seem to contain useful 
documentation e.g. about module parameters.

A very simple attempt could be to issue the command

	echo "scsi add-single-device 0 0 6 0" > /proc/scsi/scsi

If the atp870u driver performs a bus reset and does not wait long enough 
for SCSI devices to finish their "reset procedure", it will not find the 
scanner, when it scans the bus for devices after the reset.

Abel



From techjedi at gmail.com  Wed Oct  6 22:45:05 2004
From: techjedi at gmail.com (Chris McKeever)
Date: Wed, 6 Oct 2004 16:45:05 -0500
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <20041006211926.GA4132@meier-geinitz.de>
References: <d9aa9070410061122270e5a94@mail.gmail.com>
	 <d9aa90704100612297776dd31@mail.gmail.com>
	 <00af01c4abe8$98a1f610$6800000a@venti>
	 <20041006211926.GA4132@meier-geinitz.de>
Message-ID: <d9aa9070410061445229ab527@mail.gmail.com>

On Wed, 6 Oct 2004 23:19:27 +0200, Henning Meier-Geinitz
<henning at meier-geinitz.de> wrote:
> Hi,
> 
> On Wed, Oct 06, 2004 at 05:07:46PM -0400, Brian K. White wrote:
> > The manufacturer says that it does 1200x2400 optically, but xsane only
> > offers a listbox that says a single value from 0 to 2400, no XXXxYYY
> > choices, so I picked 2400 just to go for a worst case scenario but I have
> > no idea what it's actually going to do.
> > A lie, only actualy produce 1200x1200? a distorted image? silently double
> > every pixel in one direction? silently double every pixel in both
> > directions? or maybe the scanner will do the doubling in one direction in
> > firmware and present sane with 2400x2400 data?
> 
> As it doesn't make sense to crete distorted images SANE backends
> usually either duplicate pixels or interpolate them.
> 
> I've seen several Windows drivers that interpolate even if it's not
> necessary: E.g. harware resolution 100 and 200 dpi, driver uses 100
> dpi when asked for 200.
> 
> Also some scanners are advertized to make 600x1200 dpi but can't do
> (and don't do) 1200 dpi even vertically. It looks like nobody ever
> checked what the Windows driver really scans.
> 
> I don't know what's the case with the LiDEs, however.
> 
> > It's only at about 10 or 15% progress after 20 minutes so I'll send another
> > post when it's done, or when it crashes.
> 


Thanks for the input thus far - I have some new results/information


I did some remote scanning tests with the scanner hooked up to a
mandrake10 box (2.6.xx kernel).  The delay in starting to scan was not
as intrusive as it is on the RH7.3 box (2.4.18 kernel).

In fact - it was able to scan at 1200 DPI, whereas when using the
RH7.3 box it just would timeout

I upped the memory in the RH box - and still the same result.  SO now
there are three main differences with the MDK and RH box - the kernel
and the CPU:

1 - the RH box has 1.0.14 and the MDK box 1.0.13
2 - the kernel - 2.4 uses scanner.o and 2.6 uses libusb
3 - the RH box is a 500Mhz and the MDK box is an 800

would any of these be a direct reason for the delay in starting the
scan?  I understand that there are 3 variables - but if libusb is the
main key - that would be good to know


I am going to try to revert to 1.0.13 and see what happens
I can then try rolling out a more CPU equivalent box

so the real variable is the LIBUSB - does anyone know if that is a
module in 2.4.xx?

thanks





> At least with the scanners supported by the gt68xx backend, a low scan
> width is important for higher speed at high resolutions. As you
> usually use high resolutions for smaller sections of photos or slides
> that's not that unreasonable.
> 
> > This box has a gig of ram so hopefully it's enough for this worst-case
> > scenario if sane doesn't open a file and work with smaller chunks in ram.
> > This is a dual 1gig p3 too. That might be relevant by making it more likely
> > that there is always a cpu available to service the usb interrups? Or
> > rather, that the one cpu that seems to be the only one that even sees
> > interrupts, is more likely to be able to keep up.
> 
> One of the problems is that libusb doesn't allow async i/o. So you
> can't send some buffers to be filled and wait for their completion.
> 
> Bye,
>   Henning
> 
> 
> 
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org
>



From brian at aljex.com  Wed Oct  6 23:26:14 2004
From: brian at aljex.com (Brian K. White)
Date: Wed, 6 Oct 2004 18:26:14 -0400
Subject: [sane-devel] Re: strange problems LIDE30
References: <d9aa9070410061122270e5a94@mail.gmail.com> <d9aa90704100612297776dd31@mail.gmail.com> <00af01c4abe8$98a1f610$6800000a@venti>
Message-ID: <010b01c4abf3$8d8b0f40$6800000a@venti>

> It's only at about 10 or 15% progress after 20 minutes so I'll send

still cranking away
just over 50%

Now I wish I'd used the time command so I can see just how long this will 
take even if I go out to eat and it finishes while I'm gone. Then we could 
look at the total data and total time and see if it transferred at full usb 
1.1 speed. Seems like it should be able to go a lot faster than this with 12 
megabit available.

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani




From andras at users.sourceforge.net  Wed Oct  6 23:41:03 2004
From: andras at users.sourceforge.net (Major A)
Date: Wed, 6 Oct 2004 23:41:03 +0100
Subject: [sane-devel] is coolscan2 maintained?
In-Reply-To: <1096727231.3040.561.camel@localhost>
References: <1096727231.3040.561.camel@localhost>
Message-ID: <20041006224102.GA11406@ventus.lan>

> I am trying to get in touch with the coolscan2 backend author but I got
> no replies neither to private emails, neither in this list.
> I even checked that his last commit is dated january 2003, so I am
> wondering if he is still working at this project.

Sorry for not replying, I've had a busy time at work. I'm maintaining
coolscan2, but I need help with a few things. Here's the list of the
most important tasks still to be done:

- get LS50 and LS5000 to work, maybe LS9000 too.

- fix frame offset on LS4000 (should be easy, I just haven't had the
  time yet).

- add multiscan for those models that support it.

- fix positioning with LS8000.

I tried to get the first point done a few times, but it has proved a
bit difficult with no direct access to a scanner. If anyone could work
out what needs to be done, I'd be happy to incorporate it into the
code. Same goes for all other tasks. Since I have an LS4000, I'll
probably do points 2 and 3 myself.

With respect to all points above except multiscanning, there is no
more information that I can find in the Nikon specs that could
help. These things have to be solved via reverse engineering (looking
at logs).

Please do NOT contact me privately. If you have a question, please
post it on the list, I subscribe to it, and even if I don't reply,
someone else might help you.

  Andras



From techjedi at gmail.com  Thu Oct  7 00:10:12 2004
From: techjedi at gmail.com (Chris McKeever)
Date: Wed, 6 Oct 2004 18:10:12 -0500
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <010b01c4abf3$8d8b0f40$6800000a@venti>
References: <d9aa9070410061122270e5a94@mail.gmail.com>
	 <d9aa90704100612297776dd31@mail.gmail.com>
	 <00af01c4abe8$98a1f610$6800000a@venti>
	 <010b01c4abf3$8d8b0f40$6800000a@venti>
Message-ID: <d9aa90704100616102dac4784@mail.gmail.com>

well - did some more testing - downgraded the RH 7.3 box to SANE
1.0.13 - same delay in in starting the scan (+2 min. @ 600 DPI).. I
think tried it on a slightly more powerful CPU and had the same
result.  This is leaning me towards that the 2.6 kernel with its
implemenation of LIBUSB works a lot better - I am going to give SuSE
9.1 a shot in a little and see if results are coincide with MANDRAKE
tests earlier

can anyone confirm that LIBUSB implementation would create this type of result?


On Wed, 6 Oct 2004 18:26:14 -0400, Brian K. White <brian at aljex.com> wrote:
> > It's only at about 10 or 15% progress after 20 minutes so I'll send
> 
> still cranking away
> just over 50%
> 
> Now I wish I'd used the time command so I can see just how long this will
> take even if I go out to eat and it finishes while I'm gone. Then we could
> look at the total data and total time and see if it transferred at full usb
> 1.1 speed. Seems like it should be able to go a lot faster than this with 12
> megabit available.
> 
> 
> 
> Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani
> 
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org
>



From brian at aljex.com  Thu Oct  7 02:09:50 2004
From: brian at aljex.com (Brian K. White)
Date: Wed, 6 Oct 2004 21:09:50 -0400
Subject: [sane-devel] Re: strange problems LIDE30
References: <d9aa9070410061122270e5a94@mail.gmail.com> <d9aa90704100612297776dd31@mail.gmail.com> <00af01c4abe8$98a1f610$6800000a@venti> <010b01c4abf3$8d8b0f40$6800000a@venti>
Message-ID: <015401c4ac0a$684c5560$6800000a@venti>

Brian K. White wrote:
>> It's only at about 10 or 15% progress after 20 minutes so I'll send
>
> still cranking away
> just over 50%
>
> Now I wish I'd used the time command so I can see just how long this
> will take even if I go out to eat and it finishes while I'm gone.
> Then we could look at the total data and total time and see if it
> transferred at full usb 1.1 speed. Seems like it should be able to go a 
> lot faster than this
> with 12 megabit available.

Just crashed, 8:07 pm
I sent my original mail at 5:07 pm
I probably started that email (and the xsane process) at about 4:30 pm

It was xsane in kde so I don't have any error message. It just winked out.
It was somewhere near 90% but I don't think it was done.
It's speed was constant the whole time and I had looked at it a few minutes 
before and it was still just under 90% and I don't think it was nearly 
enough time for it to have gone the rest of the way, maybe only another 1 or 
2 %.
So I will tentatively say it failed while in progress, not after it was done 
scanning and tried to do whatever it does next.
I was scanning "to viewer".

This box is not overclocked at all and has not exhibited any other signs of 
flaky hardware so I don't suspect ram/cpu/etc
It's running 2 seti at home processes 24/7 and I do a fair/medium amount of 
work on it, lots of rxvt & ssh to other boxes, some gimp, lots of konquerer, 
xmms is playing some 128 kbit shoutcast stream almost 24/7, I have a fairly 
large java app that runs 24/7 that interfaces with our voip phone system, I 
play the occasional dvd. None of these has yet surprised me.
I have not used the adaptec usb 2.0 pci card for very much at all although 
the optical mouse is plugged in to it and the scanner, and I have used the 
scanner and xsane without incident several times before but only at 
300dpi-gray and 200dpi-bw.

I wasn't touching the machine at the time. xmms was not playing, the mouse 
was not moving, the screensaver was up.
(I'm working on my laptop but I'm at the same desk)

At least I can go eat now and know I won't miss anything :)

I'm not above suspecting the usb card. I have not been able to get my 
unpowered usb2.0 2.5" hard drive to work on it.
Sorry, I can't define "not work" since I gave up a few months ago and by now 
I don't recall what I tried and what I saw because it was never actually 
important to me.
But that could just as easily be the enclosure or drive and not the usb 
card. The drive & enclosure works on my laptop, but it does give windows 
delayed write failed error messages once in a while if it's left plugged in 
and idle a long time. *shrug*

I could do some transfers to a 512 meg sd card in a jump drive trio and see 
if that is reliable.
sd cards are normally only about 1 megabit, but I have a 10/9 mb read/write 
card. that should be an ok test.
I'll just to simple large monolithic transfers so as to minimize the number 
of write cycles I use up.
I'll dd 500 megs directly to it a few times, and same thing to read.
I'll start with a given file, dd it on, dd it back to a new file and cmp the 
files to verify that the writes & reads didn't have a silent error that 
corrupted the data.
If that works I'll call the usb card stable at least in usb1 mode.


Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani




From gerhard at gjaeger.de  Thu Oct  7 08:01:59 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Thu, 7 Oct 2004 09:01:59 +0200
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <015401c4ac0a$684c5560$6800000a@venti>
References: <d9aa9070410061122270e5a94@mail.gmail.com> <010b01c4abf3$8d8b0f40$6800000a@venti> <015401c4ac0a$684c5560$6800000a@venti>
Message-ID: <200410070901.59917.gerhard@gjaeger.de>

Hi,

let's try and shed some light on the plustek-backend and the LiDE30
scanner:

- The scanner is a USB1.1 device, as the used chipset, a LM9833 is only
  capable to do USB1.1. 
- The LM9833 is able to scan @ 8bit per color-channel or @ 16bit
  where did you get the "full-color" from? You either scan with the
  "color" option, then it's 8bit per channel or you scan with the
  "color 42/48" option, then it's 16bit.
- The LiDE30 is able to scan @1200dpi in X direction, because it's the
  native resolution of the sensor, and the motor is able to do 2400dpi
  steps. Therefore X direction information is doubled.
- The backend does some calibration @ the start of each scan, this might
  take a while. This time has also been increased from 1.0.13 up to 1.0.14
  This is necessary to avoid stripes. To reduce the time, it's now possible
  to let the backend save the information of the coarse calibration 
  (option cacheCalData in the config file, or --calibration-cache=yes for
   scanimage). This is working for the latest CVs snapshots.

Please note, all backend before 1.0.14 are not recommendend for use with the
LiDE devices, as the calibration does not work correctly!
Also using kernel 2.6.x (x < 8) might cause problems with the USB.

Also note, that full-size scanning using the 2400dpi might not work. At least
I've never tested, because I've not that much memory in my boxes. 
2400dpi also create that much data, that a USB1.1 device really needs some
time to send the data to the box. Here the bandwidth is the limiting factor.
We might can tweak the motor settings for the 2400dpi to avoid backtracking.

Before continuing, I suggest to use the latest CVS snapshots, a kernel > 2.6.7
and the latests libusb. The next step will be to check if you really need to
do scans @2400dpi, at least full-size ones.

Ciao,
  Gerhard




From Francois.Patte at math-info.univ-paris5.fr  Thu Oct  7 12:11:42 2004
From: Francois.Patte at math-info.univ-paris5.fr (=?iso-8859-1?b?RnJhbudvaXM=?= Patte)
Date: Thu,  7 Oct 2004 13:11:42 +0200
Subject: [sane-devel] scanner hp5400
In-Reply-To: <20041002154946.GK10327@meier-geinitz.de>
References: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr> <20041002154946.GK10327@meier-geinitz.de>
Message-ID: <1097147502.4165246ea080a@www.math-info.univ-paris5.fr>

Selon Henning Meier-Geinitz <henning at meier-geinitz.de>:

> Hi,
>
> On Sat, Oct 02, 2004 at 04:25:14PM +0200, Fran?ois Patte wrote:
> > I am unable to have the scanner hp5400c working under linux. Here the
> result of:
>
> [...]
>
> > [hp5400] vendor/product 0x03F0-0x1005 opened
> > [hp5400] Read: reqtype = 0xC0, req = 0x04, value = 1200
> > [hp5400] Read: reqtype = 0xC0, req = 0x04, value = C500
> > [hp5400] Command 12 verified
> > [hp5400] Sorry, unknown scanner version. Attempted match on :
> > [hp5400] * 'SilitekIBlizd C3 ScannerV0.84'
> > [hp5400] * 'SilitekIBlizd C3 ScannerV0.86'
> > [hp5400] * 'SilitekIBlizd C3 ScannerV0.87'
> > [hp5400] Version is ''
>
> > What can I do else?
>
> Rebuild sane-backends like this:
>
> CFLAGS="-DNO_STRING_VERSION_MATCH" ./configure
> make
> make install
>
> That's untested but I think it disables the version test.

This has solved the problem: scanner is now working.

Please include this change in the next version of sane-backends. I hope that
linux distributors will make the change too: it is not so easy to compile only
one package when several packages depend on it and that all where installed by
the way of rpm....

Thank you.
--
Fran?ois Patte

Ecole fran?aise d'Extr?me-Orient - Pune - Inde
Universit? Ren? Descartes - Paris 5
UFR de math?matiques et informatique
http://www.math-info.univ-paris5.fr/~patte



From henning at meier-geinitz.de  Thu Oct  7 12:33:36 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 13:33:36 +0200
Subject: [sane-devel] scanner hp5400
In-Reply-To: <1097147502.4165246ea080a@www.math-info.univ-paris5.fr>
References: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr> <20041002154946.GK10327@meier-geinitz.de> <1097147502.4165246ea080a@www.math-info.univ-paris5.fr>
Message-ID: <20041007113336.GC8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 01:11:42PM +0200, Fran?ois Patte wrote:
> This has solved the problem: scanner is now working.
> 
> Please include this change in the next version of sane-backends. I hope that
> linux distributors will make the change too: it is not so easy to compile only
> one package when several packages depend on it and that all where installed by
> the way of rpm....

The version check has already been disabled in CVS so the change will
be in sane-backends 1.0.14.

Bye,
  Henning



From henning at meier-geinitz.de  Thu Oct  7 12:57:51 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 13:57:51 +0200
Subject: [sane-devel] scanner hp5400
In-Reply-To: <20041007113336.GC8083@meier-geinitz.de>
References: <1096727114.415eba4a5a050@www.math-info.univ-paris5.fr> <20041002154946.GK10327@meier-geinitz.de> <1097147502.4165246ea080a@www.math-info.univ-paris5.fr> <20041007113336.GC8083@meier-geinitz.de>
Message-ID: <20041007115751.GD8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 01:33:36PM +0200, Henning Meier-Geinitz wrote:
> The version check has already been disabled in CVS so the change will
> be in sane-backends 1.0.14.

1.0.15 obviously.

> Bye,
>   Henning



From eppesuig at users.sourceforge.net  Thu Oct  7 14:00:50 2004
From: eppesuig at users.sourceforge.net (Giuseppe Sacco)
Date: Thu, 07 Oct 2004 15:00:50 +0200
Subject: [sane-devel] is coolscan2 maintained?
In-Reply-To: <20041006224102.GA11406@ventus.lan>
References: <1096727231.3040.561.camel@localhost>
	 <20041006224102.GA11406@ventus.lan>
Message-ID: <1097154050.1604.24.camel@casa>

Il gio, 2004-10-07 alle 00:41, Major A ha scritto:
[...]
> I tried to get the first point done a few times, but it has proved a
> bit difficult with no direct access to a scanner. If anyone could work
> out what needs to be done, I'd be happy to incorporate it into the
> code. Same goes for all other tasks. Since I have an LS4000, I'll
> probably do points 2 and 3 myself.

I may give you ssh access to a linux machine connected to an LS-50. I
may do it only for one week, just send me an ssh public key, a disk
quota requirement, a username, a start date and specify if you need a
color slide or a color/b&W film loaded.

If I might help in any other way, just tell me.

Bye,
Giuseppe




From brian at aljex.com  Thu Oct  7 16:19:38 2004
From: brian at aljex.com (Brian K. White)
Date: Thu, 7 Oct 2004 11:19:38 -0400
Subject: [sane-devel] Re: strange problems LIDE30
References: <d9aa9070410061122270e5a94@mail.gmail.com> <010b01c4abf3$8d8b0f40$6800000a@venti> <015401c4ac0a$684c5560$6800000a@venti> <200410070901.59917.gerhard@gjaeger.de>
Message-ID: <005e01c4ac81$1f563ac0$6800000a@venti>

Gerhard Jaeger wrote:
> Hi,
>
> let's try and shed some light on the plustek-backend and the LiDE30
> scanner:
>
> - The scanner is a USB1.1 device, as the used chipset, a LM9833 is
>  only capable to do USB1.1.
> - The LM9833 is able to scan @ 8bit per color-channel or @ 16bit
>  where did you get the "full-color" from? You either scan with the
>  "color" option, then it's 8bit per channel or you scan with the
>  "color 42/48" option, then it's 16bit.
> - The LiDE30 is able to scan @1200dpi in X direction, because it's the
>  native resolution of the sensor, and the motor is able to do 2400dpi
>  steps. Therefore X direction information is doubled.
> - The backend does some calibration @ the start of each scan, this
>  might take a while. This time has also been increased from 1.0.13 up
>  to 1.0.14 This is necessary to avoid stripes. To reduce the time,
>  it's now possible to let the backend save the information of the
>  coarse calibration (option cacheCalData in the config file, or
>   --calibration-cache=yes for scanimage). This is working for the
> latest CVs snapshots.
>
> Please note, all backend before 1.0.14 are not recommendend for use
> with the LiDE devices, as the calibration does not work correctly!
> Also using kernel 2.6.x (x < 8) might cause problems with the USB.
>
> Also note, that full-size scanning using the 2400dpi might not work.
> At least I've never tested, because I've not that much memory in my
> boxes. 2400dpi also create that much data, that a USB1.1 device
> really needs some time to send the data to the box. Here the
> bandwidth is the limiting factor. We might can tweak the motor
> settings for the 2400dpi to avoid backtracking.
>
> Before continuing, I suggest to use the latest CVS snapshots, a
> kernel > 2.6.7 and the latests libusb. The next step will be to check
> if you really need to do scans @2400dpi, at least full-size ones.
>
> Ciao,
>  Gerhard

Very informative
Thanks much

No, I at least have no real use for scanning full sheets in color at 
2400dpi.
I only did it for the purpose of testing the system, it's the worst case 
combination of all offered options.
I never had a problem with "normal" jobs.
I've done a few partial pages at 600dpi color, many full pages at 100-600 
gray & b&w
Never had a problem.

Even though I'm just under your recommendation on several fronts.
These are all what's currently available from suse pre-built and 
Yast-installable:

bwlin1:~ # uname -a
Linux bwlin1 2.6.5-7.108-smp #1 SMP Wed Aug 25 13:34:40 UTC 2004 i686 i686 
i386 GNU/Linux
bwlin1:~ # scanimage --version
scanimage (sane-backends) 1.0.13; backend version 1.0.13
bwlin1:~ # ls /usr/lib/*usb*
/usr/lib/libusb-0.1.so.4      /usr/lib/libusb.a   /usr/lib/libusb.so
/usr/lib/libusb-0.1.so.4.4.0  /usr/lib/libusb.la
bwlin1:~ #

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani




From sirius-c at iname.com  Thu Oct  7 16:21:10 2004
From: sirius-c at iname.com (Jason Anderson)
Date: Thu, 07 Oct 2004 10:21:10 -0500
Subject: [sane-devel] Compiling problems
Message-ID: <20041007152110.E41FE4BDA9@ws1-1.us4.outblaze.com>

Hello everyone.

Here's my problem.  When I try to compile the latest sane backends with the Genesys files, it returns an error about not being able to find genesys.o in the "lib" folder.  Now I read the README file, but it still won't compile properly.  Does anyone have a suggestion?

Thank you,

----------
Jason A.
ICQ# 148434286
-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm




From henning at meier-geinitz.de  Thu Oct  7 16:49:03 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 17:49:03 +0200
Subject: [sane-devel] Compiling problems
In-Reply-To: <20041007152110.E41FE4BDA9@ws1-1.us4.outblaze.com>
References: <20041007152110.E41FE4BDA9@ws1-1.us4.outblaze.com>
Message-ID: <20041007154903.GF8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 10:21:10AM -0500, Jason Anderson wrote:
> Here's my problem.  When I try to compile the latest sane backends
> with the Genesys files, it returns an error about not being able to
> find genesys.o in the "lib" folder.  Now I read the README file, but
> it still won't compile properly.  Does anyone have a suggestion?

You have changed configure.in and backend/Makefile.in, ran "autoconf",
make distclean, ./configure, make?

If yes, please post the esact error message (and some more lines of
context).

Bye,
  Henning



From christoph.knauer at web.de  Thu Oct  7 18:46:20 2004
From: christoph.knauer at web.de (Christoph Knauer)
Date: Thu, 7 Oct 2004 19:46:20 +0200
Subject: [sane-devel] scanning via network
Message-ID: <200410071946.25043.christoph.knauer@web.de>

Hi People,

I've just build me a new backend-package from sourcen, where I used newer code 
for microtek2 (from karsten festag) which works now with SM X6 and LightLid35 
(the scannerlamp now is of if I use the lightlid).

But now there is a network-problem since I'm using this "new" backend-package: 
I can't scan on my network anymore. To compile only the microtek2-code was 
changed, all other stuff was used before, too.

When I've a look into my xinetd.log, there are these entries:

> 04/10/5 at 17:49:02: START: sane from=192.168.10.1
> 04/10/5 at 23:39:51: EXIT: sane status=0 duration=21049(sec)
> --------------------------^ before using the "new" microtek2
> 04/10/6 at 10:15:59: START: sane from=192.168.10.1
> 04/10/6 at 10:15:59: EXIT: sane status=127 duration=0(sec)
> --------------------------^ after using the "new" microtek2

I've looked for all my conf-files, and they seems to be unchanged.

Any Ideas?

Thanx, Christoph

PS: I'm sorry, but my english is not very well
-- 
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
-----
alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
unter http://www.profiseller.de/shop/christoph-knauer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041007/6b3db7be/attachment.sig>

From ukd at xenon.pc.Uni-Koeln.DE  Thu Oct  7 19:24:45 2004
From: ukd at xenon.pc.Uni-Koeln.DE (Ulrich Deiters)
Date: Thu, 07 Oct 2004 19:24:45 METDST
Subject: [sane-devel] No device available
Message-ID: <200410071724.TAA02695@xenon.pc.Uni-Koeln.DE>

Are you sure that the SCSI ID of the scanner is different
from any other ID on the bus? Is the bus properly
terminated? Is the SCSI cable of permissible length?
If the SCSI controller cannot initialize its bus, it
might declare itself as offline at boot time.

Regards,

Ulrich Deiters



From henning at meier-geinitz.de  Thu Oct  7 18:59:09 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 19:59:09 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <200410071946.25043.christoph.knauer@web.de>
References: <200410071946.25043.christoph.knauer@web.de>
Message-ID: <20041007175909.GH8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 07:46:20PM +0200, Christoph Knauer wrote:
> But now there is a network-problem since I'm using this "new" backend-package: 
> I can't scan on my network anymore. To compile only the microtek2-code was 
> changed, all other stuff was used before, too.

If that's true, it's not a network problem.

> When I've a look into my xinetd.log, there are these entries:
> 
> > 04/10/5 at 17:49:02: START: sane from=192.168.10.1
> > 04/10/5 at 23:39:51: EXIT: sane status=0 duration=21049(sec)
> > --------------------------^ before using the "new" microtek2
> > 04/10/6 at 10:15:59: START: sane from=192.168.10.1
> > 04/10/6 at 10:15:59: EXIT: sane status=127 duration=0(sec)
> > --------------------------^ after using the "new" microtek2
> 
> I've looked for all my conf-files, and they seems to be unchanged.
> 
> Any Ideas?

First describe what you do and what your problem actually is. Is the
network scanner not detected or doesn't it scan?

Log messages from saned?

Bye,
  Henning



From tomasz.orlinski at wp.pl  Thu Oct  7 19:26:50 2004
From: tomasz.orlinski at wp.pl (=?iso-8859-2?Q?Tomasz_Orli=F1ski?=)
Date: Thu, 7 Oct 2004 20:26:50 +0200
Subject: [sane-devel] USB scanners DO work on Solaris 10 x86
Message-ID: <002501c4ac9d$8be2b530$0100a8c0@athlon64>

I would like to inform you, that I have compiled SANE on Sun Solaris 10 x86
with built-in USB scanner support. It was possible, because Sun had prepared
libusb library wrapper for Solaris 10. I know, that Solaris 10 Software
Express Release 08/04 is required. I have done it in that way:
LD_LIBRARY_PATH=/usr/sfw/lib:$LD_LIBRARY_PATH
CFLAGS="-I/usr/sfw/include"
CPPFLAGS="-I/usr/sfw/include"
LDFLAGS="-L/usr/sfw/lib -R/usr/sfw/lib -lusb"
export LD_LIBRARY_PATH CFLAGS CPPFLAGS LDFLAGS
./configure --prefix=/opt/sane --disable-fork-process
make
make install
It was also required to add a generic USB kernel driver. I had to look for
my scanner device name in output of
prtconf -D -v
command. My scanner is Plustek UT24 and the apropriate part of output looked
like this:
name='compatible' type=string items=8 value='usb7b3,17.100' + ...
I had to remove the not used kernel driver
rem_drv ugen
And add it again:
add_drv -i 'usb7b3,17.100' ugen
Then, /opt/sane/bin/sane-find-scanner detected my scanner and everything
worked fine. I to add " " signs around usb7b3,17.100 name in
/etc/driver_aliases to have the scanner working after reboot.
To compile this packages SUNWlibusb and SUNWlibusbugen were needed. I used
Solaris Software Companion CD gcc 2.95.3 compiler and Sun's /usr/ccs/bin/ld
linker. USB support DOES NOT work in Solaris 9 and earlier versions.
I hope, that this information would be useful for other USB scanner users.

Tomasz Orlinski




From henning at meier-geinitz.de  Thu Oct  7 20:02:33 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 21:02:33 +0200
Subject: [sane-devel] USB scanners DO work on Solaris 10 x86
In-Reply-To: <002501c4ac9d$8be2b530$0100a8c0@athlon64>
References: <002501c4ac9d$8be2b530$0100a8c0@athlon64>
Message-ID: <20041007190233.GI8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 08:26:50PM +0200, Tomasz Orli?ski wrote:
> I would like to inform you, that I have compiled SANE on Sun Solaris 10 x86
> with built-in USB scanner support.

Very nice. I'd like to place your mail in README.solaris in SANE CVS
so it can be easily find. What's your opinion on this?

I guess you used sane-backends 1.0.14? I'll update our "supported
platforms list" accordingly.

Thanks for your report. It looks like a real adventure to use
Solaris/x86 :-)

Bye,
  Henning

> -- 
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org



From christoph.knauer at web.de  Thu Oct  7 20:31:15 2004
From: christoph.knauer at web.de (Christoph Knauer)
Date: Thu, 7 Oct 2004 21:31:15 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <20041007175909.GH8083@meier-geinitz.de>
References: <200410071946.25043.christoph.knauer@web.de> <20041007175909.GH8083@meier-geinitz.de>
Message-ID: <200410072131.20022.christoph.knauer@web.de>

Hi,

I can scan from my server, where the scanner is connected, but i can't scan 
from my network-pc. The only change on the system is a backend-update on the 
server by using the last sorces of karsten festag.

It seems to be an error in the updatet files, I've just reinstalled the last 
version before, and suddenly there is no error ...

Thanks

Am Donnerstag, 7. Oktober 2004 19:59 schrieb Henning Meier-Geinitz:
> Hi,
>
> On Thu, Oct 07, 2004 at 07:46:20PM +0200, Christoph Knauer wrote:
> > But now there is a network-problem since I'm using this "new"
> > backend-package: I can't scan on my network anymore. To compile only the
> > microtek2-code was changed, all other stuff was used before, too.
>
> If that's true, it's not a network problem.
>
> > When I've a look into my xinetd.log, there are these entries:
> > > 04/10/5 at 17:49:02: START: sane from=192.168.10.1
> > > 04/10/5 at 23:39:51: EXIT: sane status=0 duration=21049(sec)
> > > --------------------------^ before using the "new" microtek2
> > > 04/10/6 at 10:15:59: START: sane from=192.168.10.1
> > > 04/10/6 at 10:15:59: EXIT: sane status=127 duration=0(sec)
> > > --------------------------^ after using the "new" microtek2
> >
> > I've looked for all my conf-files, and they seems to be unchanged.
> >
> > Any Ideas?
>
> First describe what you do and what your problem actually is. Is the
> network scanner not detected or doesn't it scan?
>
> Log messages from saned?
>
> Bye,
>   Henning

-- 
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
-----
alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
unter http://www.profiseller.de/shop/christoph-knauer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041007/292a8284/attachment.sig>

From henning at meier-geinitz.de  Thu Oct  7 20:34:58 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 7 Oct 2004 21:34:58 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <200410072131.20022.christoph.knauer@web.de>
References: <200410071946.25043.christoph.knauer@web.de> <20041007175909.GH8083@meier-geinitz.de> <200410072131.20022.christoph.knauer@web.de>
Message-ID: <20041007193458.GJ8083@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 09:31:15PM +0200, Christoph Knauer wrote:
> I can scan from my server, where the scanner is connected, but i can't scan 
> from my network-pc. The only change on the system is a backend-update on the 
> server by using the last sorces of karsten festag.
> 
> It seems to be an error in the updatet files, I've just reinstalled the last 
> version before, and suddenly there is no error ...

Ok. So I'll ask again:

> > First describe what you do and what your problem actually is. Is the
> > network scanner not detected or doesn't it scan?

If it doesn't scan, which error message do you get and when?

Bye,
  Henning



From bertrik at zonnet.nl  Thu Oct  7 21:49:09 2004
From: bertrik at zonnet.nl (Bertrik Sikken)
Date: Thu, 07 Oct 2004 22:49:09 +0200
Subject: [sane-devel] niash backend dependencies in backend/Makefile.in
Message-ID: <4165ABC5.5040406@zonnet.nl>

Hi all,

I just tried sane-backends CVS and found that it did not work
for my hp3300 (niash backend). Scanimage -L complains about
missing 'sanei_scsi_find_devices'. I think this is somehow
pulled in from another sanei function.

I noticed that nearly all other backends have a line in
backend/Makefile.in that declares dependency on sanei_scsi.lo
(the niash backend does not have it)
Adding the following line to backend/Makefile.in made it work
for me:
libsane-niash.la: ../sanei/sanei_scsi.lo

I'm not sure what is going on, perhaps I'm overlooking something.
The patch to sane-backends that we used before the niash backend
was integrated into sane CVS didn't have the
'libsane-niash.la: ../sanei/sanei_scsi.lo'
line either, yet it seemed to work.

Can someone review the correctness of the dependencies in
backend/Makefile.in for the niash backend?
What dependencies are needed for what sanei_functions?

All the best,
Bertrik



From christoph.knauer at web.de  Thu Oct  7 22:13:05 2004
From: christoph.knauer at web.de (Christoph Knauer)
Date: Thu, 7 Oct 2004 23:13:05 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <20041007193458.GJ8083@meier-geinitz.de>
References: <200410071946.25043.christoph.knauer@web.de> <200410072131.20022.christoph.knauer@web.de> <20041007193458.GJ8083@meier-geinitz.de>
Message-ID: <200410072313.05389.christoph.knauer@web.de>

Hi,

the problem is not in network-scanning. Please forget this thead, thanks

For info: it seems to be a problem with the last build on my system ... using 
the package before (which I know as good) -> ok, all is working fine
Using the last builded package -> nothing works, only error: 

Julia2002:~ # scanimage -L
scanimage: relocation error: /usr/local/lib/sane/libsane-microtek2.so.1: 
undefined symbol: sanei_thread_init

On the weekend perhaps I've more time to search the solution ...

Thanks,

Christoph

Am Donnerstag, 7. Oktober 2004 21:34 schrieb Henning Meier-Geinitz:
> > > First describe what you do and what your problem actually is. Is the
> > > network scanner not detected or doesn't it scan?
>
> If it doesn't scan, which error message do you get and when?

-- 
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
-----
alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
unter http://www.profiseller.de/shop/christoph-knauer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041007/5da39059/attachment.sig>

From peder at park.se  Fri Oct  8 10:29:19 2004
From: peder at park.se (peder)
Date: Fri, 8 Oct 2004 11:29:19 +0200 (CEST)
Subject: [sane-devel] Two xsane-Win32-0.96 annoyancies
Message-ID: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>

 Thanx for a nifty port.

 I've been happlily using xsane in out school network for a couple of
 years. We have 5 old linux boxes scattered around the place as scanner
 servers and the WinXP/Win98-clients use xsane to connect.

 However there are two issues.

 The minor one: Is there a technical reason why the program has to
 be installed to c:\sane? Can't the program search for it's files
 using perhaps a XSANE variable or in current directory?
 I like to have the program installed on the server so I can upgrade
 it for every user and not having to walk around 300+ PC's.
 This works in 0.90 on Win98 but not on WinXP for some reason.
 In 0.96 it works on neither.

 I found out you only have to put some files in c:\sane so I can
 distribute those every time, so this issue is not a biggie.

 The major one: In xsane-0.83 and 0.90 I could run
 'xsane.exe ip-of-scan-server:device'. In 0.96 this doesn't work; I have
 to add all my servers in net.conf, wait for xsane to "scan for devices"
 and choose the right one from five nearly identical entries.
 Maybe I can pick the right one but definitely not my users.
 Can we please have the scan-server argument back?

 FYI, version 0.90 was much faster than 0.96. I tried them on a
 400MHz and 0.96 was really sluggish, perhaps due to newer gtk versions.


 Regards,

 Peder Hedlund



From henning at meier-geinitz.de  Fri Oct  8 11:00:43 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 8 Oct 2004 12:00:43 +0200
Subject: [sane-devel] Two xsane-Win32-0.96 annoyancies
In-Reply-To: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>
References: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>
Message-ID: <20041008100043.GB9991@meier-geinitz.de>

Hi,

On Fri, Oct 08, 2004 at 11:29:19AM +0200, peder wrote:
>  The major one: In xsane-0.83 and 0.90 I could run
>  'xsane.exe ip-of-scan-server:device'. In 0.96 this doesn't work; I have
>  to add all my servers in net.conf, wait for xsane to "scan for devices"
>  and choose the right one from five nearly identical entries.

Just a wild guess: If xsane 0.83 was linked directly against the net
backend and 0.96 was linked against the dll backend the format would be:
xsane.exe net:ip-of-scan-server:device

>  Maybe I can pick the right one but definitely not my users.

At least on Unix systems there is the SANE_DEFAULT_DEVICE varaiable
that preselects the device to use. That means you only have to press
enter.

Bye,
  Henning



From henning at meier-geinitz.de  Fri Oct  8 10:52:56 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 8 Oct 2004 11:52:56 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <200410072313.05389.christoph.knauer@web.de>
References: <200410071946.25043.christoph.knauer@web.de> <200410072131.20022.christoph.knauer@web.de> <20041007193458.GJ8083@meier-geinitz.de> <200410072313.05389.christoph.knauer@web.de>
Message-ID: <20041008095256.GA9991@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 11:13:05PM +0200, Christoph Knauer wrote:
> For info: it seems to be a problem with the last build on my system ... using 
> the package before (which I know as good) -> ok, all is working fine
> Using the last builded package -> nothing works, only error: 
> 
> Julia2002:~ # scanimage -L
> scanimage: relocation error: /usr/local/lib/sane/libsane-microtek2.so.1: 
> undefined symbol: sanei_thread_init
> 
> On the weekend perhaps I've more time to search the solution ...

The reason is that you only use a new microtek2 backend.
backend/Makefile.in also must be updated.

As the latest microtek2 code is now in CVS I recommend using a CVS
snapshot.

Bye,
  Henning



From henning at meier-geinitz.de  Fri Oct  8 12:03:25 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 8 Oct 2004 13:03:25 +0200
Subject: [sane-devel] niash backend dependencies in backend/Makefile.in
In-Reply-To: <4165ABC5.5040406@zonnet.nl>
References: <4165ABC5.5040406@zonnet.nl>
Message-ID: <20041008110325.GA23598@meier-geinitz.de>

Hi,

On Thu, Oct 07, 2004 at 10:49:09PM +0200, Bertrik Sikken wrote:
> I just tried sane-backends CVS and found that it did not work
> for my hp3300 (niash backend). Scanimage -L complains about
> missing 'sanei_scsi_find_devices'. I think this is somehow
> pulled in from another sanei function.

That's called from sanei_config_attach_matching_devices.

However, at least in current CVS niash doesn't seem to use that
function.

> I noticed that nearly all other backends have a line in
> backend/Makefile.in that declares dependency on sanei_scsi.lo
> (the niash backend does not have it)
> Adding the following line to backend/Makefile.in made it work
> for me:
> libsane-niash.la: ../sanei/sanei_scsi.lo

That's only needed for SCSI backends. USB backends should use
sanei_usb_attach_matching_devices (which is in sanei_usb.lo).

> Can someone review the correctness of the dependencies in
> backend/Makefile.in for the niash backend?

It's correct as far as I can see.

If it still happens after "cvs update ; make distclean; ./congigure ;
make ; make install" could you show us some more details (e.g. if it's
really the niash backend that uses this function)?

I don't get any errors with scanimage -L.

Bye,
  Henning



From peder at park.se  Fri Oct  8 12:09:21 2004
From: peder at park.se (peder)
Date: Fri, 8 Oct 2004 13:09:21 +0200 (CEST)
Subject: [sane-devel] Two xsane-Win32-0.96 annoyancies
In-Reply-To: <20041008100043.GB9991@meier-geinitz.de>
References: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>
 <20041008100043.GB9991@meier-geinitz.de>
Message-ID: <Pine.LNX.4.58.0410081302550.19226@tux.park.se>

On Fri, 8 Oct 2004, Henning Meier-Geinitz wrote:

> Hi,
>
> On Fri, Oct 08, 2004 at 11:29:19AM +0200, peder wrote:
> >  The major one: In xsane-0.83 and 0.90 I could run
> >  'xsane.exe ip-of-scan-server:device'. In 0.96 this doesn't work; I have
> >  to add all my servers in net.conf, wait for xsane to "scan for devices"
> >  and choose the right one from five nearly identical entries.
>
> Just a wild guess: If xsane 0.83 was linked directly against the net
> backend and 0.96 was linked against the dll backend the format would be:
> xsane.exe net:ip-of-scan-server:device

 Pretty accurate wild guess! Thanx.

 Peder



From techjedi at gmail.com  Fri Oct  8 14:48:22 2004
From: techjedi at gmail.com (Chris McKeever)
Date: Fri, 8 Oct 2004 08:48:22 -0500
Subject: [sane-devel] Re: strange problems LIDE30
In-Reply-To: <200410070901.59917.gerhard@gjaeger.de>
References: <d9aa9070410061122270e5a94@mail.gmail.com>
	 <010b01c4abf3$8d8b0f40$6800000a@venti>
	 <015401c4ac0a$684c5560$6800000a@venti>
	 <200410070901.59917.gerhard@gjaeger.de>
Message-ID: <d9aa907041008064815c04b9e@mail.gmail.com>

n Thu, 7 Oct 2004 09:01:59 +0200, Gerhard Jaeger <gerhard at gjaeger.de> wrote:
> Hi,
> 
> let's try and shed some light on the plustek-backend and the LiDE30
> scanner:
> 
> - The scanner is a USB1.1 device, as the used chipset, a LM9833 is only
>   capable to do USB1.1.
> - The LM9833 is able to scan @ 8bit per color-channel or @ 16bit
>   where did you get the "full-color" from? You either scan with the
>   "color" option, then it's 8bit per channel or you scan with the
>   "color 42/48" option, then it's 16bit.
> - The LiDE30 is able to scan @1200dpi in X direction, because it's the
>   native resolution of the sensor, and the motor is able to do 2400dpi
>   steps. Therefore X direction information is doubled.
> - The backend does some calibration @ the start of each scan, this might
>   take a while. This time has also been increased from 1.0.13 up to 1.0.14
>   This is necessary to avoid stripes. To reduce the time, it's now possible
>   to let the backend save the information of the coarse calibration
>   (option cacheCalData in the config file, or --calibration-cache=yes for
>    scanimage). This is working for the latest CVs snapshots.
> 

Thanks everyone for all your information! - I have gotten it all
working, and just want to summarize (again) what was laerned found

- yes the canon 30 is only 1.1USB
- when moving from a 2.4 kernel to a 2.6 kernel the startup time for the scanner
decreased significantly (I think the is a libusb v. scanner.o issue). 
I am now able to remote scan @ 1200 (it is however slow)
- originally I had a generic USB2 card - that was causing me some
grief in-and-of-itself with the scanner, dropping it to the onboard
1.1 solved at least some of the issue
- I am using the stock kernel and libusb from SUSE 9.1 (2.6.5) - I am
not having any issue thus far w/ 1.0.14

once again - thanks





> Please note, all backend before 1.0.14 are not recommendend for use with the
> LiDE devices, as the calibration does not work correctly!
> Also using kernel 2.6.x (x < 8) might cause problems with the USB.
> 
> Also note, that full-size scanning using the 2400dpi might not work. At least
> I've never tested, because I've not that much memory in my boxes.
> 2400dpi also create that much data, that a USB1.1 device really needs some
> time to send the data to the box. Here the bandwidth is the limiting factor.
> We might can tweak the motor settings for the 2400dpi to avoid backtracking.
> 
> Before continuing, I suggest to use the latest CVS snapshots, a kernel > 2.6.7
> and the latests libusb. The next step will be to check if you really need to
> do scans @2400dpi, at least full-size ones.
> 
> Ciao,
>   Gerhard
> 
> 
> 
> 
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org
>



From anton.mazkovoi at gmail.com  Sat Oct  9 06:37:06 2004
From: anton.mazkovoi at gmail.com (Anton Mazkovoi)
Date: Sat, 9 Oct 2004 15:37:06 +1000
Subject: [sane-devel] SaneTwain - windows losing connection
Message-ID: <9647569f0410082237451ebb75@mail.gmail.com>

Hi,

I have a epson cx6500 scanner/printer which I have working with epkowa
drivers and sane-backends-1.0.12-2 on a RedHat 9 box. Saned is started
through xinetd and I have a Windows XP SP1 machine running SaneTwain
1.25 and scanning images with no problem.

Another Windows XP SP1 machine on the same local network refuses to
scan. Its running the same version of SaneTwain. When scanimage.exe is
started it tries to retrieve the scanners from the server and I see
the saned process started on the server (and a connection reported on
both windows and linux boxes using "netstat -na"). The scanimage
window is unusable (unclickable) for a while. After some time  the
window becomes usable and the devices dropdown is correctly populated
with the scanner's device.

Clicking "preview" or "scan", results in a pop-up which says: "Write
error 64, the specified network name is no longer available". When I
do a "netstat -na" on a windows box I can see that the tcp connection
is NOT there. The linux box (netstat -na) thinks the connection IS
there, the saned process is still running and is doing a read from the
socket which is (was) connected to the windows box.

Also, the "options" tab of the scanimage window is completely empty.
(On the working windows XP box it shows options).

Also, printing to the scanner/printer device from both windows boxes
causes no problems. The linux box also acts as the gateway to the
internet for both windows boxes. Surfing the web and downloading files
from both machines seems to have no problems.

I am attaching the log produced by running scanimage --debug on the
non-working windows box.

Is this a known windows problem? Has anyone seen anything like this before?

Any help is very much appreciated!

Thanks in advance,
Anton
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sanetwain.dbg
Type: application/octet-stream
Size: 3916 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041009/a10d6b9b/attachment.obj>

From usigwanz at lycos.de  Sat Oct  9 14:50:32 2004
From: usigwanz at lycos.de (Ullrich Sigwanz)
Date: Sat, 09 Oct 2004 13:50:32 GMT 
Subject: [sane-devel] Scanner Button
Message-ID: <1097329832013643@lycos-europe.com>

An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041009/cd26c5cf/attachment.htm>

From christoph.knauer at web.de  Sat Oct  9 16:08:28 2004
From: christoph.knauer at web.de (Christoph Knauer)
Date: Sat, 9 Oct 2004 17:08:28 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <20041008095256.GA9991@meier-geinitz.de>
References: <200410071946.25043.christoph.knauer@web.de> <200410072313.05389.christoph.knauer@web.de> <20041008095256.GA9991@meier-geinitz.de>
Message-ID: <200410091708.34359.christoph.knauer@web.de>

Hi,

ok, I'm trying the snapshot from today ...

Bye,
Christoph

Am Freitag, 8. Oktober 2004 11:52 schrieb Henning Meier-Geinitz:
> Hi,
>
> On Thu, Oct 07, 2004 at 11:13:05PM +0200, Christoph Knauer wrote:
> > For info: it seems to be a problem with the last build on my system ...
> > using the package before (which I know as good) -> ok, all is working
> > fine Using the last builded package -> nothing works, only error:
> >
> > Julia2002:~ # scanimage -L
> > scanimage: relocation error: /usr/local/lib/sane/libsane-microtek2.so.1:
> > undefined symbol: sanei_thread_init
> >
> > On the weekend perhaps I've more time to search the solution ...
>
> The reason is that you only use a new microtek2 backend.
> backend/Makefile.in also must be updated.
>
> As the latest microtek2 code is now in CVS I recommend using a CVS
> snapshot.
>
> Bye,
>   Henning

-- 
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
-----
alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
unter http://www.profiseller.de/shop/christoph-knauer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041009/7b6af962/attachment.sig>

From anoah at pfeiffer.edu  Sat Oct  9 16:34:43 2004
From: anoah at pfeiffer.edu (m. allan noah)
Date: Sat, 9 Oct 2004 11:34:43 -0400 (EDT)
Subject: [sane-devel] Scanner Button
In-Reply-To: <1097329832013643@lycos-europe.com>
References: <1097329832013643@lycos-europe.com>
Message-ID: <Pine.LNX.4.61.0410091126330.30301@limos.pfeiffer.edu>

there has been much discussion in the past, but everyone seems too busy to 
actually get anything in writing. search the archives of the sane mailing 
list, there where several threads about it in the earlier part of this 
year, IIRC.

basically:

front end polling a backend via asking for updates on certain OPTs seems 
to be the consensus. details that need work: how to identify which opts, 
recommendations for how frontends could display that data, and does the 
backend need to be able to specify the polling interval. how the buttons 
are affected by the network scanner locking code also seems like a good 
topic for discussion.

allan

On Sat, 9 Oct 2004, Ullrich Sigwanz wrote:

> Hi all,
> 
> Are there thoughts /ideas/implementations for including the button
> handling in SANE (resp. SANE2) in a standardized way?
> 
> (e.g. a polling daemon, callbacks to start applications etc.)
> 
> Regards
> 
> Ullrich
> 
> 
> 2,90 EUR geschenkt: kostenloser Probemonat bei Lycos Premium Mail: 250
> MB, Super Antispam, Pop3, SSL uvm - jetzt kostenlos testen!
> 
>

-- 
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera



From mattias.ellert at tsl.uu.se  Sat Oct  9 19:59:23 2004
From: mattias.ellert at tsl.uu.se (Mattias Ellert)
Date: Sat, 9 Oct 2004 20:59:23 +0200
Subject: [sane-devel] niash backend dependencies in backend/Makefile.in
In-Reply-To: <20041008110325.GA23598@meier-geinitz.de>
References: <4165ABC5.5040406@zonnet.nl> <20041008110325.GA23598@meier-geinitz.de>
Message-ID: <55B42F66-1A25-11D9-9296-0003930D2AFC@tsl.uu.se>

2004-10-08 kl. 13.03 skrev Henning Meier-Geinitz:

> Hi,
>
> On Thu, Oct 07, 2004 at 10:49:09PM +0200, Bertrik Sikken wrote:
>> I just tried sane-backends CVS and found that it did not work
>> for my hp3300 (niash backend). Scanimage -L complains about
>> missing 'sanei_scsi_find_devices'. I think this is somehow
>> pulled in from another sanei function.

I have the same problem with the CVS version...

  gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes 
-pedantic -DHAVE_CONFIG_H -I. -I. -I../include -I../include 
-DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d 
-DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 
-D_REENTRANT -DBACKEND_NAME=niash -DLIBDIR=/usr/local/lib/sane niash.c  
-fno-common -DPIC -o .libs/niash.o
niash.c: In function `sane_niash_exit':
niash.c:805: warning: cast discards qualifiers from pointer target type
rm -f niash-s.c
ln -s ./stubs.c niash-s.c
  gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes 
-pedantic -DHAVE_CONFIG_H -I. -I. -I../include -I../include 
-DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d 
-DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 
-D_REENTRANT -DSTUBS -DBACKEND_NAME=niash niash-s.c  -fno-common -DPIC 
-o .libs/niash-s.o
gcc -bundle  -o .libs/libsane-niash.1.0.14.so  .libs/niash.o 
.libs/niash-s.o .libs/sane_strstatus.o 
../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o 
../lib/.libs/isfdtype.o ../lib/.libs/strndup.o 
../sanei/.libs/sanei_config2.o ../sanei/.libs/sanei_constrain_value.o 
../sanei/.libs/sanei_usb.o  /usr/local/lib/libusb-0.1.4.4.1.dylib 
-lpthread -lm -framework CoreFoundation -framework IOKit
ld: Undefined symbols:
_sanei_scsi_find_devices
make[1]: *** [libsane-niash.la] Error 1
make: *** [all-recursive] Error 1

> That's called from sanei_config_attach_matching_devices.
>
> However, at least in current CVS niash doesn't seem to use that
> function.
>
>> I noticed that nearly all other backends have a line in
>> backend/Makefile.in that declares dependency on sanei_scsi.lo
>> (the niash backend does not have it)
>> Adding the following line to backend/Makefile.in made it work
>> for me:
>> libsane-niash.la: ../sanei/sanei_scsi.lo

Well, the correct fix is to remove the line asking for linking against 
sanei_config2.lo

--- sane-backends-2004-10-09-cvs.orig/backend/Makefile.in       Sun Oct 
  3 19:39:43 2004
+++ sane-backends-2004-10-09-cvs/backend/Makefile.in    Sat Oct  9 
20:09:03 2004
@@ -365,7 +365,6 @@
  libsane-net.la: ../sanei/sanei_codec_bin.lo
  libsane-net.la: ../sanei/sanei_net.lo
  libsane-net.la: ../sanei/sanei_wire.lo
-libsane-niash.la: ../sanei/sanei_config2.lo
  libsane-niash.la: ../sanei/sanei_constrain_value.lo
  libsane-niash.la: ../sanei/sanei_usb.lo
  libsane-pint.la: ../sanei/sanei_constrain_value.lo

If this line is removed the linking works...

	Mattias




From christoph.knauer at web.de  Sat Oct  9 22:18:31 2004
From: christoph.knauer at web.de (Christoph Knauer)
Date: Sat, 9 Oct 2004 23:18:31 +0200
Subject: [sane-devel] scanning via network
In-Reply-To: <20041008095256.GA9991@meier-geinitz.de>
References: <200410071946.25043.christoph.knauer@web.de> <200410072313.05389.christoph.knauer@web.de> <20041008095256.GA9991@meier-geinitz.de>
Message-ID: <200410092318.37609.christoph.knauer@web.de>

Hi,

Ive just testet with the todays snapshot. The Lightlid will work, but there is 
the wrong-color-problem again.

I've modified the microtek2.c with the change I got from Karsten 1,5 years 
ago, and now it works fine, with right colors.

Bye,

Christoph

Am Freitag, 8. Oktober 2004 11:52 schrieb Henning Meier-Geinitz:
> Hi,
>
> On Thu, Oct 07, 2004 at 11:13:05PM +0200, Christoph Knauer wrote:
> > For info: it seems to be a problem with the last build on my system ...
> > using the package before (which I know as good) -> ok, all is working
> > fine Using the last builded package -> nothing works, only error:
> >
> > Julia2002:~ # scanimage -L
> > scanimage: relocation error: /usr/local/lib/sane/libsane-microtek2.so.1:
> > undefined symbol: sanei_thread_init
> >
> > On the weekend perhaps I've more time to search the solution ...
>
> The reason is that you only use a new microtek2 backend.
> backend/Makefile.in also must be updated.
>
> As the latest microtek2 code is now in CVS I recommend using a CVS
> snapshot.
>
> Bye,
>   Henning

-- 
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
-----
alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
unter http://www.profiseller.de/shop/christoph-knauer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041009/20e8fb81/attachment.sig>

From anton.mazkovoi at gmail.com  Sun Oct 10 08:55:27 2004
From: anton.mazkovoi at gmail.com (Anton Mazkovoi)
Date: Sun, 10 Oct 2004 17:55:27 +1000
Subject: [sane-devel] Re: SaneTwain - windows losing connection
In-Reply-To: <9647569f0410082237451ebb75@mail.gmail.com>
References: <9647569f0410082237451ebb75@mail.gmail.com>
Message-ID: <9647569f04101000552a199d27@mail.gmail.com>

I have updated the driver for my network card and everything works
flawlessly  now.

Thanks,
Anton



On Sat, 9 Oct 2004 15:37:06 +1000, Anton Mazkovoi
<anton.mazkovoi at gmail.com> wrote:
> Hi,
> 
> I have a epson cx6500 scanner/printer which I have working with epkowa
> drivers and sane-backends-1.0.12-2 on a RedHat 9 box. Saned is started
> through xinetd and I have a Windows XP SP1 machine running SaneTwain
> 1.25 and scanning images with no problem.
> 
> Another Windows XP SP1 machine on the same local network refuses to
> scan. Its running the same version of SaneTwain. When scanimage.exe is
> started it tries to retrieve the scanners from the server and I see
> the saned process started on the server (and a connection reported on
> both windows and linux boxes using "netstat -na"). The scanimage
> window is unusable (unclickable) for a while. After some time  the
> window becomes usable and the devices dropdown is correctly populated
> with the scanner's device.
> 
> Clicking "preview" or "scan", results in a pop-up which says: "Write
> error 64, the specified network name is no longer available". When I
> do a "netstat -na" on a windows box I can see that the tcp connection
> is NOT there. The linux box (netstat -na) thinks the connection IS
> there, the saned process is still running and is doing a read from the
> socket which is (was) connected to the windows box.
> 
> Also, the "options" tab of the scanimage window is completely empty.
> (On the working windows XP box it shows options).
> 
> Also, printing to the scanner/printer device from both windows boxes
> causes no problems. The linux box also acts as the gateway to the
> internet for both windows boxes. Surfing the web and downloading files
> from both machines seems to have no problems.
> 
> I am attaching the log produced by running scanimage --debug on the
> non-working windows box.
> 
> Is this a known windows problem? Has anyone seen anything like this before?
> 
> Any help is very much appreciated!
> 
> Thanks in advance,
> Anton
> 
> 
>



From nr19ch at freesurf.ch  Sun Oct 10 13:35:28 2004
From: nr19ch at freesurf.ch (nr19ch)
Date: Sun, 10 Oct 2004 14:35:28 +0200
Subject: [sane-devel] Agfa Snapscan e40 and Suse9.1
Message-ID: <200410101435.28178.nr19ch@freesurf.ch>

Hello
I try to install Snapscan e40. I've installed it with Yast but when I launch 
xsane I get the error message "failed to open device 
'snapscan:libusb:001:003'.
I've had a Mustek Scanner 1200Cu plus installed and it worked fine. Do I have 
to uninstall somethig before using my new scanner (cause after I've installed 
the new scaner my old mustek still works fine.)
I don't know much about linux and hope that there is anybody who can provide 
help for my problem.
Thanks! D.S.



From tomasz.orlinski at wp.pl  Fri Oct  8 15:06:14 2004
From: tomasz.orlinski at wp.pl (Tomasz Orlinski)
Date: Fri, 8 Oct 2004 16:06:14 +0200
Subject: [sane-devel] USB scanners DO work on Solaris 10 x86
References: <002501c4ac9d$8be2b530$0100a8c0@athlon64> <20041007190233.GI8083@meier-geinitz.de>
Message-ID: <001f01c4ad40$59044220$0100a8c0@athlon64>

Yes, I think it would be a good idea to include this information to
README.solaris file. I have used 1.0.14 release of sane-backends. Sun in
Driver Development Kit v. 0.9 writes how to compile SANE, but it does not
really work :) They write about compiling with gcc and give options for Sun
Forte compiler (cc) and forget about attaching a kernel driver. But they
write, that versions earlier than 1.0.14 cannot be used. They want also to
build SANE with Posix threads enabled. So I think that can be true. Sun
writes also, that Solaris Software Express release at least S10_62 is needed
to use libusb. Release number can be checked in /etc/release. The newest
version can be downloaded from www.sun.com/solaris for free.
In my opinion it is important to be cautious when using scanner or just
libusb on important Solaris machines (especially multi-processor ones),
because unlike in other systems, Solaris kernel is fully preemtible, what
means, that many instances of the same driver can ran simultanously - it's
dangerous, when drivers are not perfect. And Solaris USB framework is
absolutely new, so it can contain bugs. I tried to crash my Solaris using
USB subsystem and SANE, I didn't manage to, but it doesn't mean, it's
impossible.
SANE frontends work without any problems with Xsun and GIMP included in
Solaris Software Companion CD.




From marc53shapiro at hotmail.com  Sat Oct  9 10:06:06 2004
From: marc53shapiro at hotmail.com (Marc)
Date: Sat, 9 Oct 2004 10:06:06 +0100
Subject: [sane-devel] scanning on Epson Stylus Scan 2500 works
Message-ID: <7409F833-19D2-11D9-81EF-000393CD04D6@hotmail.com>

A message from a happy user: even though the all-in-one Epson Stylus 
Scan 2500 is not listed on your list of supported scanners, it works 
for me (on MacOS X 10.3.5, flatpanel iMac).  Thanks!!!

												Marc





From dwhysong at gmail.com  Sun Oct 10 05:07:07 2004
From: dwhysong at gmail.com (David Whysong)
Date: Sat, 9 Oct 2004 21:07:07 -0700
Subject: [sane-devel] Epson 2480 not detected
Message-ID: <34eaeeaa0410092107abeda33@mail.gmail.com>

Hi,

I read the previous reports about making this scanner work, but I have
had no luck.

I removed the SANE frontend and backend RPMs, then downloaded and
compiled the current CVS backend. I copied the hotplug scripts to
/etc/hotplug/usb, extracted the firmware and put the proper path and
the vendor/device ID line in the /usr/local/etc/sane.d/snapscan.conf
file.

Here is what I have:

[dwhysong at sleepy sane-backends]$ sane-find-scanner
[...]
found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON
Scanner]) at libusb:001:011
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.
[...]

[dwhysong at sleepy sane-backends]$ scanimage -L
                                                                                
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).


I have rw permissions for the /proc/bus/usb/001/011 file.

The other "curiosity" is this. Upon connecting the USB cable, I see:

Oct  9 21:04:22 sleepy kernel: usb 1-1: new full speed USB device
using address 12
Oct  9 21:04:22 sleepy /etc/hotplug/usb.agent: Bad USB agent invocation
Oct  9 21:04:25 sleepy /etc/hotplug/usb.agent: Setup libusbscanner for
USB product 4b8/121/110
Oct  9 21:04:25 sleepy /etc/hotplug/usb.agent: Module setup
libusbscanner for USB product 4b8/121/110
Oct  9 21:04:26 sleepy devlabel: devlabel service started/restarted

I'm not sure why I'm getting "Bad USB agent invocation" -- that
happens when the $PRODUCT or $ACTION variables are not defined for
usb.agent (and I verified that neither are defined). But it seems to
run the libusbscanner script, so I'm guessing the real problem does
not lie with the hotplug scritps.

Kernel 2.6.6-rc1, x86_64 architecture.

Any suggestions?

-- 
David



From nr19ch at freesurf.ch  Sun Oct 10 14:04:39 2004
From: nr19ch at freesurf.ch (nr19ch)
Date: Sun, 10 Oct 2004 15:04:39 +0200
Subject: [sane-devel] Again Agfa Snapscan e40 and Suse9.1
Message-ID: <200410101504.39487.nr19ch@freesurf.ch>

Hello everybody again
Finally managed to solve my problem and the scanner now works fine (there was 
no read or write permission for the firmware file). Sorry for my disturbing 
mail and have a good time enjoying Linux.
D.S.



From henning at meier-geinitz.de  Sun Oct 10 14:16:39 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 15:16:39 +0200
Subject: [sane-devel] scanning on Epson Stylus Scan 2500 works
In-Reply-To: <7409F833-19D2-11D9-81EF-000393CD04D6@hotmail.com>
References: <7409F833-19D2-11D9-81EF-000393CD04D6@hotmail.com>
Message-ID: <20041010131639.GD3144@meier-geinitz.de>

Hi,

On Sat, Oct 09, 2004 at 10:06:06AM +0100, Marc wrote:
> A message from a happy user: even though the all-in-one Epson Stylus 
> Scan 2500 is not listed on your list of supported scanners, it works 
> for me (on MacOS X 10.3.5, flatpanel iMac).  Thanks!!!

Thanks for your report. Can you give some more details, i.e. what's
teh output of:

scanimage -L
and
scanimage --version

Bye,
  Henning




From henning at meier-geinitz.de  Sun Oct 10 14:20:12 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 15:20:12 +0200
Subject: [sane-devel] Scanner Button
In-Reply-To: <1097329832013643@lycos-europe.com>
References: <1097329832013643@lycos-europe.com>
Message-ID: <20041010132012.GE3144@meier-geinitz.de>

Hi,

On Sat, Oct 09, 2004 at 01:50:32PM +0000, Ullrich Sigwanz wrote:
> <html><head><style type="text/css">body{font:12px Arial;margin:3px;overflow-y:auto;overflow-x:auto}p{margin:0px;}blockquote, ol, ul{margin-top:0px;margin-bottom:0px;}</style></head>

Buh, HTML.


> Are there thoughts /ideas/implementations for including the button
> handling in SANE (resp. SANE2) in a standardized way?<br>

See chapter 4.5.14 of the latest SANE2 draft for a possible interface.
Also see lots of discussions on sane-devel. If you want to discuss the
way how to implement the SANE interface (backend/frontend) for
buttons, the sane-standard list is the right one.

Bye,
  Henning




From henning at meier-geinitz.de  Sun Oct 10 14:23:39 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 15:23:39 +0200
Subject: [sane-devel] Epson 2480 not detected
In-Reply-To: <34eaeeaa0410092107abeda33@mail.gmail.com>
References: <34eaeeaa0410092107abeda33@mail.gmail.com>
Message-ID: <20041010132339.GF3144@meier-geinitz.de>

Hi,

On Sat, Oct 09, 2004 at 09:07:07PM -0700, David Whysong wrote:
> [dwhysong at sleepy sane-backends]$ scanimage -L
>                                                                                 
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
> 
> 
> I have rw permissions for the /proc/bus/usb/001/011 file.

Does scanimage -L find the scanner as root? If it doesn't, it's not a
permissions nor hotplug issue.

Enable debugging like this:
export SANE_DEBUG_SNAPSCAN=255 
and run scanimage -L again. Please show us the debug output.

Bye,
  Henning



From henning at meier-geinitz.de  Sun Oct 10 14:34:45 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 15:34:45 +0200
Subject: [sane-devel] Upgrading sane-backend on Mandrake 10.0
In-Reply-To: <3DDE554B.2030606@dccnet.com>
References: <3DDE554B.2030606@dccnet.com>
Message-ID: <20041010133445.GG3144@meier-geinitz.de>

Hi,

On Fri, Nov 22, 2002 at 08:03:23AM -0800, Lloyd Sumpter wrote:

Strange date.

> <RANT MODE ON>
> This is what bugs me about Linux packages! In order to upgrade one 
> simple program, you end up upgrading your entire OS!!

You don't need to do that. At least I haven't ever needed to do that.
Just get the latest package and install it. Well it's mandrake so ...
:-)

> What the H*LL does sane-backends have to do with harddrake, anyway?

sane-backends doesn't know anything about harddrake and couldn't care
less :-)

> So, apparently libsane1-1.0.13 is required by kdegraphics, and 
> sane-backends-1.0.13 is required by harddrake. I looked at kdegraphics 
> and decide I don't need it, so erase it. Then I go ahead and upgrade to 
> libsane1-1.0.14-3mdk and sane-backends-1.0.14-3mdk.

I don't know these details but I'm surprised that they need a specific
version of sane-backends.

> Next thing I know, my CPU meter is pinned and performance is fast 
> disappearing. I manage to reboot before it goes away altogether. Next 
> boot, same thing starts, but I manage to find out it's "scannerdrake", 
> along with sane-find-scanner and several usb utilities (*I* didn't run 
> these programs!) are using all the resources. I manage to erase the 
> sane-backends, which stops the bleeding. I re-install 1.0.13 and all is 
> well again.

I have never heard that anything from sane-backends does this. So I
think it's one of the Mandrake tools.

> No man pages for harddrake or scannerdrake.
> 
> So...How do I upgrade sane-backends on Mandrake 10.0 without sending 
> harddrake (I assume that's what's launching scannerdrake?) into a 
> tailspin? Also, what is "libsane"? It seems to be required in Mandrake, 
> but I don't see it in the source code packages - is it normally just 
> included in the sane-backend package?

The package "libsane" seems to be an invention of distributors. I know
that debian has the source package "sane-backends" and binary package
"libsane" (the SANE libraries) and "sane-utils" (e.g. scanimage).
Maybe it's similar with Mandrake?

Most of your questions are better suited in a Mandrake forum as they
aren't really related to SANE itsself but the packages created by
Mandrake.

> BTW: The reason I have to upgrade is that apparently the sane-backends 
> included with Mandrake 10.0 do NOT support libusb (but since the kernel 
> is 2.6.x, there's no scanner.o to use instead...)

sane-backends supports libusb since quite some time. And it was needed
before kernel 2.6 at least for some scanners. So I'd be surprised if
the Mandrake version had no libusb support.

You can check by running "sane-find-scanner -v -v". It should print
messages about using libusb.

Bye,
  Henning



From henning at meier-geinitz.de  Sun Oct 10 15:15:16 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 16:15:16 +0200
Subject: [sane-devel] Feature Freeze for sane-frontends 1.0.13: Snapshot
Message-ID: <20041010141516.GI3144@meier-geinitz.de>

Hi everyone,

Feature freeze for sane-frontends 1.0.13 is active now. If no grave
bugs are found, the package will be released 2004-10-17 (next Sunday).

There is a 1.0.13-pre1 snapshot. Please test it and report any bugs to
the bug tracking system.

Download:
http://alioth.debian.org/project/showfiles.php?group_id=30186
ftp://ftp.sane-project.org/pub/sane/

The Changelog is attached.

Bye,
  Henning

-- snapshot 1.0.13-pre1

2004-10-10  Henning Meier-Geinitz <henning at meier-geinitz.de>

	* Makefile.in: Added xscanimage-icon-48x48-2.png to DISTFILES.

2004-10-05  Henning Meier-Geinitz <henning at meier-geinitz.de>

	* xscanimage-icon-48x48-2.png: Added xscanimage icon (from Maciek
	  Podkomorzy <gammaray at satfilm.net.pl>).

2004-10-03  Henning Meier-Geinitz <henning at meier-geinitz.de>

	* src/gtkglue.c: Don't try to print non-readable options. Don't
	  try to write non-writable options (bug #300621). Don't print
	  warnings for options without constraints.

2004-07-09  Henning Meier-Geinitz <henning at meier-geinitz.de>

	* doc/scanadf.man src/scanadf.c: Added -N option to stop scanadf
	  from overwriting files (patch from Paul Walmsley
	  <paul at booyaka.com>). 

2004-05-12  Henning Meier-Geinitz <henning at meier-geinitz.de>

	* acinclude.m4 aclocal.m4 configure sane-frontends.lsm: Removed
	  old links to ftp.mostang.com.

2004-04-29  Julien Blache <jb at jblache.org>
	* src/gtkglue.h: looks like someone wanted GSGDialog.twocolumn to
	an int rather than a GtkWidget *. Fixed.

2004-04-24  Henning Meier-Geinitz <henning at meier-geinitz.de>

	* Makefile.in: Remove autoconf temp files in distclean.

2004-04-20  Julien Blache <jb at jblache.org>

	* src/preview.c: make the preview work when it's resized.

2004-04-19  Julien Blache <jb at jblache.org>

	* src/xcam.c: fixed xcam layout.

2004-04-17  Henning Meier-Geinitz <henning at meier-geinitz.de>

	* configure configure.in: Set version to 1.0.12-cvs.
	




From mogensjaeger at get2net.dk  Sun Oct 10 15:59:10 2004
From: mogensjaeger at get2net.dk (Mogens Jaeger)
Date: Sun, 10 Oct 2004 16:59:10 +0200
Subject: [sane-devel] Translation
Message-ID: <41694E3E.7080109@get2net.dk>

Hello
I was looking in the cvs at: 
http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/sane-frontends/?cvsroot=sane, 
for a po/pot file for the 'sane-frontends 1.0.13' but I did not find any 
- is it not aviable, or am I looking a wrong place?

-- 
mvh Mogens J?ger




From henning at meier-geinitz.de  Sun Oct 10 16:32:05 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 10 Oct 2004 17:32:05 +0200
Subject: [sane-devel] Translation
In-Reply-To: <41694E3E.7080109@get2net.dk>
References: <41694E3E.7080109@get2net.dk>
Message-ID: <20041010153205.GJ3144@meier-geinitz.de>

Hi,

On Sun, Oct 10, 2004 at 04:59:10PM +0200, Mogens Jaeger wrote:
> I was looking in the cvs at: 
> http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/sane-frontends/?cvsroot=sane, 
> for a po/pot file for the 'sane-frontends 1.0.13' but I did not find any - 
> is it not aviable, or am I looking a wrong place?

None of the frontends included in the sane-frontends package has
internationalization support.

Bye,
  Henning



From joehenley at kc.rr.com  Sun Oct 10 21:40:10 2004
From: joehenley at kc.rr.com (Joe Henley)
Date: Sun, 10 Oct 2004 15:40:10 -0500
Subject: [sane-devel] umax_pp slow
In-Reply-To: <20041004044644.GA6220@wanadoo.fr>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com> <20041001042733.GA2166@wanadoo.fr> <415D7E43.8080907@kc.rr.com> <20041004044644.GA6220@wanadoo.fr>
Message-ID: <41699E2A.5010109@kc.rr.com>

Hi Stef,

Sorry for the delay in responding.  I was out of town on business.

svoltz at wanadoo.fr wrote:
> 	Hello,
> 
> 	I think you should try again ECP. I think the message you get is
> harmless. You can comment it out in the sourcecode before doing tests
> again. 

I'm not sure I understand which message you're referring to.  With the 
BIOS set for ECP, it (scanimage -L 2>log) just runs on without stopping. 
  I have to use ^C to stop it.  Is that the message you refer to?

The BIOS says it's ECP, but Linux doesn't report it that way in the 
/var/log/messages or kernel files.  Very odd!  Even more odd is that I 
run Win4Lin on this machine, using Win98.  I can run Linux running 
Win4Lin, running Win98, running the VistaScan copier program, and it 
runs just fine.  The speed is very good.  So somehow it's figuring out 
to run quickly thru the parallel port.  If I shut down 
VistaScan/Win98/Win4Lin and without rebooting, load up sane and try it, 
it's very slow.  Arrrgh!

Any suggestions?

> 	But until you see ECP mode detected by ythe linux kernel, I'm
> afraid you'll have troubles.
> 
> Regards,
> 	Stef
> 
Thanks!

Joe Henley



From Oliver.Rauch at Rauch-Domain.DE  Sun Oct 10 21:36:43 2004
From: Oliver.Rauch at Rauch-Domain.DE (Oliver Rauch)
Date: 10 Oct 2004 22:36:43 +0200
Subject: [sane-devel] Two xsane-Win32-0.96 annoyancies
In-Reply-To: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>
References: <Pine.LNX.4.58.0410080933470.26675@tux.park.se>
Message-ID: <1097440603.2148.4.camel@Babylon7>

Am Fre, 2004-10-08 um 11.29 schrieb peder:
>  Thanx for a nifty port.
> 
>  I've been happlily using xsane in out school network for a couple of
>  years. We have 5 old linux boxes scattered around the place as scanner
>  servers and the WinXP/Win98-clients use xsane to connect.
> 
>  However there are two issues.
> 
>  The minor one: Is there a technical reason why the program has to
>  be installed to c:\sane? Can't the program search for it's files
>  using perhaps a XSANE variable or in current directory?
>  I like to have the program installed on the server so I can upgrade
>  it for every user and not having to walk around 300+ PC's.
>  This works in 0.90 on Win98 but not on WinXP for some reason.
>  In 0.96 it works on neither.

XSane uses hardcoded paths. This is a usual way on unix systems.
The paths are created while configurating xsane and are compiled in.
When you compile xsane-win32 yourself then you can compile in your own
paths.

> 
>  I found out you only have to put some files in c:\sane so I can
>  distribute those every time, so this issue is not a biggie.
> 
>  The major one: In xsane-0.83 and 0.90 I could run
>  'xsane.exe ip-of-scan-server:device'. In 0.96 this doesn't work; I have
>  to add all my servers in net.conf, wait for xsane to "scan for devices"
>  and choose the right one from five nearly identical entries.
>  Maybe I can pick the right one but definitely not my users.
>  Can we please have the scan-server argument back?
> 

The differences between 0.95/0.96 and the previous xsane-win32 versions
are that the new versions are linked against sane-dll, the old versions
were linked agains sane-net.

You have to use the same syntax as in linux:

xsane net:192.168.0.1



>  FYI, version 0.90 was much faster than 0.96. I tried them on a
>  400MHz and 0.96 was really sluggish, perhaps due to newer gtk versions.

On my systems I had the feeling that xsane-0.96 is much faster. Do you
use the same settings in preferences and view?

Oliver




From sean035 at yahoo.com.tw  Mon Oct 11 01:52:22 2004
From: sean035 at yahoo.com.tw (sean035 at yahoo.com.tw)
Date: Mon, 11 Oct 2004 08:52:22 +0800 (CST)
Subject: [sane-devel] permission problem
Message-ID: <20041011005222.87323.qmail@web17807.mail.tpe.yahoo.com>

Hello everybody,
I had meet a strange things when I developing new
scanner backend. I can make my scanner work fine as
root account or super user, but didn't as the others
account. Now, my new scanner backend can work fine and
support Xsane as log in root this super user but I
can't use "scanimage -L" to find my scanner device. Is
problem about permission or another situation? If is,
which permission of device file I have to setup?
Thanks a lot for everyone.
Walker,  

-----------------------------------------------------------------
Yahoo!??????
100MB ?????????????????
http://mail.yahoo.com.tw/



From gerhard at gjaeger.de  Mon Oct 11 07:43:56 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Mon, 11 Oct 2004 08:43:56 +0200
Subject: [sane-devel] permission problem
In-Reply-To: <20041011005222.87323.qmail@web17807.mail.tpe.yahoo.com>
References: <20041011005222.87323.qmail@web17807.mail.tpe.yahoo.com>
Message-ID: <200410110843.56481.gerhard@gjaeger.de>

On Monday 11 October 2004 02:52, sean035 at yahoo.com.tw wrote:
> Hello everybody,
> I had meet a strange things when I developing new
> scanner backend. I can make my scanner work fine as
> root account or super user, but didn't as the others
> account. Now, my new scanner backend can work fine and
> support Xsane as log in root this super user but I
> can't use "scanimage -L" to find my scanner device. Is
> problem about permission or another situation? If is,
> which permission of device file I have to setup?

See README.linux.
BTW: On what "new"-backend are you working? Which is the supported
scanner?

--
  Gerhard




From afb at paradise.net.nz  Mon Oct 11 10:41:33 2004
From: afb at paradise.net.nz (Adam Felix Bogacki)
Date: Mon, 11 Oct 2004 22:41:33 +1300
Subject: [sane-devel] xsane-win32
Message-ID: <416A554D.6000509@paradise.net.nz>

Sorry Oliver. I removed and re-installed  Epson Smart Panel for Scanner 
and Twain and it
recognised the scanner and was usable. However, xsane springs into action,
shows me the 'Xsane End User Licence Agreement', and after I click the 
'I accept' panel
searches around and quickly gives me  'no devices available'.

It was doing this when Smart Panel and Twain were not working so I don't 
think it may be
a case of the scanner being assigned to one program and denied to 
another. I could be wrong.

I have gone through the 'help' list of  possible reasons for this and 
the only thing which looks
plausible is  'backend is not configured correct'.

In 'C:\sane\etc\sane.d\net.conf' I used 'localhost' and '192.168.0.1' - 
the localhost TCP/IP address ..

In 'C:\sane\etc\sane.d\dll.conf' the only lines enabled are 'epson' and 
'gphoto2' (in case of future digital camera use) , and in

'C:\sane\etc\sane.d\epson.conf' the only uncommented lines are

'usb 0x04b8 0x010c' and 'usb /dev/usb/scanner0'

Are there any obvious errors here ? Confusion of backward and forward slashes ?

One thing I came across in reading WinXP help files was that Twain does not work
after the scanner is disconnected (as in re-plugging with Linux hotplug). It then has to be
reinstalled via XP's 'New Hardware Install' wizard. 

Could this be contributing here ?

It's frustrating having a fine program like xsane not working in XP. 

Adam Bogacki,
afb at paradise.net.nz





From afb at paradise.net.nz  Mon Oct 11 11:06:30 2004
From: afb at paradise.net.nz (Adam Felix Bogacki)
Date: Mon, 11 Oct 2004 23:06:30 +1300
Subject: [sane-devel] xsane-win32: 'cygwin1.dll was not found'
Message-ID: <416A5B26.3040803@paradise.net.nz>

Hi, trying 'sane-find-scanner' gave the error message

'This application has failed to start because cygwin1.dll was not found.
Re-installing the application may fix this problem'.

I'll keep trying.

Adam.





From karsten.festag at gmx.de  Mon Oct 11 13:16:20 2004
From: karsten.festag at gmx.de (Karsten Festag)
Date: Mon, 11 Oct 2004 14:16:20 +0200 (MEST)
Subject: [sane-devel] scanning via network
References: <200410092318.37609.christoph.knauer@web.de>
Message-ID: <23810.1097496980@www47.gmx.net>

Hi,

I thought I had merged the fix for the wrong color problem into the latest
backend but obviously not :-(
Unfortunately I have not much time this week, so:
Christoph, could you please re-send my modification to me to make sure I'm
not mixing something? Thanks! I'll check what's going on.

Karsten

> Hi,
> 
> Ive just testet with the todays snapshot. The Lightlid will work, but
> there is 
> the wrong-color-problem again.
> 
> I've modified the microtek2.c with the change I got from Karsten 1,5 years
> ago, and now it works fine, with right colors.
> 
> Bye,
> 
> Christoph
> 
> Am Freitag, 8. Oktober 2004 11:52 schrieb Henning Meier-Geinitz:
> > Hi,
> >
> > On Thu, Oct 07, 2004 at 11:13:05PM +0200, Christoph Knauer wrote:
> > > For info: it seems to be a problem with the last build on my system
> ...
> > > using the package before (which I know as good) -> ok, all is working
> > > fine Using the last builded package -> nothing works, only error:
> > >
> > > Julia2002:~ # scanimage -L
> > > scanimage: relocation error:
> /usr/local/lib/sane/libsane-microtek2.so.1:
> > > undefined symbol: sanei_thread_init
> > >
> > > On the weekend perhaps I've more time to search the solution ...
> >
> > The reason is that you only use a new microtek2 backend.
> > backend/Makefile.in also must be updated.
> >
> > As the latest microtek2 code is now in CVS I recommend using a CVS
> > snapshot.
> >
> > Bye,
> >   Henning
> 
> -- 
> GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
> -----
> alles rund um 1&1 Internet (ISDN, DSL, und vieles mehr)
> unter http://www.profiseller.de/shop/christoph-knauer
> 

-- 
GMX ProMail mit bestem Virenschutz http://www.gmx.net/de/go/mail
+++ Empfehlung der Redaktion +++ Internet Professionell 10/04 +++




From marc53shapiro at hotmail.com  Sun Oct 10 14:51:48 2004
From: marc53shapiro at hotmail.com (Marc)
Date: Sun, 10 Oct 2004 14:51:48 +0100
Subject: [sane-devel] scanning on Epson Stylus Scan 2500 works
In-Reply-To: <20041010131639.GD3144@meier-geinitz.de>
References: <7409F833-19D2-11D9-81EF-000393CD04D6@hotmail.com> <20041010131639.GD3144@meier-geinitz.de>
Message-ID: <87A94C23-1AC3-11D9-A0FB-000393CD04D6@hotmail.com>

Le 10 oct. 04, ? 14:16, Henning Meier-Geinitz a ?crit :

>> A message from a happy user: even though the all-in-one Epson Stylus
>> Scan 2500 is not listed on your list of supported scanners, it works
>> for me (on MacOS X 10.3.5, flatpanel iMac).  Thanks!!!
>
> Thanks for your report. Can you give some more details, i.e. what's
> teh output of:
>
> scanimage -L

device `epson:libusb:001:006-04b8-0106-ff-ff' is a Epson StylusScan2500 
flatbed
scanner

> and
> scanimage --version

scanimage (sane-backends) 1.0.14-cvs; backend version 1.0.14

											Marc






From dwhysong at gmail.com  Sun Oct 10 19:13:11 2004
From: dwhysong at gmail.com (David Whysong)
Date: Sun, 10 Oct 2004 11:13:11 -0700
Subject: [sane-devel] Epson 2480 not detected
In-Reply-To: <20041010132339.GF3144@meier-geinitz.de>
References: <34eaeeaa0410092107abeda33@mail.gmail.com>
	 <20041010132339.GF3144@meier-geinitz.de>
Message-ID: <34eaeeaa04101011133f9b735c@mail.gmail.com>

Thanks, but I solved the problem. Sane-backend wasn't building shared
libraries. The libtool script really needs to look in /usr/local/lib
for stuff... (and /usr/lib64 on x86_64 machines!).

BTW, I had already tried scanimage -L as root with various debug
environment variables, and it never gave any extra output (of course,
since it didn't have any drivers to load).

It works nicely now. Thanks!

- David


On Sun, 10 Oct 2004 15:23:39 +0200, Henning Meier-Geinitz
<henning at meier-geinitz.de> wrote:
> Hi,
> 
> On Sat, Oct 09, 2004 at 09:07:07PM -0700, David Whysong wrote:
> > [dwhysong at sleepy sane-backends]$ scanimage -L
> >
> > No scanners were identified. If you were expecting something different,
> > check that the scanner is plugged in, turned on and detected by the
> > sane-find-scanner tool (if appropriate). Please read the documentation
> > which came with this software (README, FAQ, manpages).
> >
> >
> > I have rw permissions for the /proc/bus/usb/001/011 file.
> 
> Does scanimage -L find the scanner as root? If it doesn't, it's not a
> permissions nor hotplug issue.
> 
> Enable debugging like this:
> export SANE_DEBUG_SNAPSCAN=255
> and run scanimage -L again. Please show us the debug output.
> 
> Bye,
>   Henning
>



From andreas_klinger at debitel.net  Sun Oct 10 19:21:54 2004
From: andreas_klinger at debitel.net (Klinger)
Date: Sun, 10 Oct 2004 20:21:54 +0200
Subject: [sane-devel] unsubscribe moasta27
In-Reply-To: <20041010153205.GJ3144@meier-geinitz.de>
Message-ID: <000001c4aef6$077d5a60$0100a8c0@BLANCA>

I wanted to develop a backend for my hp scanjet 4500 scanner, but i've seen
it'll take about 4 weeks or more just to analyze the protocol. My wife will
kill me if i'm doing it ;)

Thanks for your mails

Andreas





From henning at meier-geinitz.de  Mon Oct 11 13:23:52 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 11 Oct 2004 14:23:52 +0200
Subject: [sane-devel] scanning on Epson Stylus Scan 2500 works
In-Reply-To: <87A94C23-1AC3-11D9-A0FB-000393CD04D6@hotmail.com>
References: <7409F833-19D2-11D9-81EF-000393CD04D6@hotmail.com> <20041010131639.GD3144@meier-geinitz.de> <87A94C23-1AC3-11D9-A0FB-000393CD04D6@hotmail.com>
Message-ID: <20041011122352.GC8269@meier-geinitz.de>

Hi,

On Sun, Oct 10, 2004 at 02:51:48PM +0100, Marc wrote:
> Le 10 oct. 04, ? 14:16, Henning Meier-Geinitz a ?crit :
> 
> >>A message from a happy user: even though the all-in-one Epson Stylus
> >>Scan 2500 is not listed on your list of supported scanners, it works
> >>for me (on MacOS X 10.3.5, flatpanel iMac).  Thanks!!!
> >
> >Thanks for your report. Can you give some more details, i.e. what's
> >teh output of:
> >
> >scanimage -L
> 
> device `epson:libusb:001:006-04b8-0106-ff-ff' is a Epson StylusScan2500 
> flatbed
> scanner
> 
> >and
> >scanimage --version
> 
> scanimage (sane-backends) 1.0.14-cvs; backend version 1.0.14

Ok, so it's supported by the epson backend.

Karl-Heinz, could you add that scanner to epson.desc?

Also, what about the "Epson ES-300GS"?
https://alioth.debian.org/tracker/index.php?func=detail&aid=300682&group_id=30186&atid=410366

By the way, I guess some of "your" bugs can be closed (#300598,
#300490?, #300179). Could you have a look at these bug reports?


Bye,
  Henning




From henning at meier-geinitz.de  Mon Oct 11 13:26:18 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 11 Oct 2004 14:26:18 +0200
Subject: [sane-devel] Epson 2480 not detected
In-Reply-To: <34eaeeaa04101011133f9b735c@mail.gmail.com>
References: <34eaeeaa0410092107abeda33@mail.gmail.com> <20041010132339.GF3144@meier-geinitz.de> <34eaeeaa04101011133f9b735c@mail.gmail.com>
Message-ID: <20041011122618.GD8269@meier-geinitz.de>

Hi,

On Sun, Oct 10, 2004 at 11:13:11AM -0700, David Whysong wrote:
> Thanks, but I solved the problem. Sane-backend wasn't building shared
> libraries. The libtool script really needs to look in /usr/local/lib
> for stuff... (and /usr/lib64 on x86_64 machines!).

I'll have a look for is a more current libtool version.

> BTW, I had already tried scanimage -L as root with various debug
> environment variables, and it never gave any extra output (of course,
> since it didn't have any drivers to load).

SANE_DEBUG_DLL=255 may help in such a case.

Bye,
  Henning



From sirius-c at iname.com  Mon Oct 11 19:02:57 2004
From: sirius-c at iname.com (Jason Anderson)
Date: Mon, 11 Oct 2004 13:02:57 -0500
Subject: [sane-devel] Trying to work out the Genesys backend
Message-ID: <20041011180257.26616101D8@ws1-3.us4.outblaze.com>

Hello everyone.

I'm trying to figure out how to make the Genesys backend work, but I don't even know where to start.  Is it in the conf file?  Or is it in the source files?  If anyone has been working on it for a while could please contact me, that would be greatly appreciated.

----------
Jason A.
ICQ# 148434286
-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm




From henning at meier-geinitz.de  Mon Oct 11 19:43:04 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 11 Oct 2004 20:43:04 +0200
Subject: [sane-devel] Trying to work out the Genesys backend
In-Reply-To: <20041011180257.26616101D8@ws1-3.us4.outblaze.com>
References: <20041011180257.26616101D8@ws1-3.us4.outblaze.com>
Message-ID: <20041011184304.GE17236@meier-geinitz.de>

Hi,

On Mon, Oct 11, 2004 at 01:02:57PM -0500, Jason Anderson wrote:
> I'm trying to figure out how to make the Genesys backend work, but I
> don't even know where to start.  Is it in the conf file?  Or is it in
> the source files?  If anyone has been working on it for a while could
> please contact me, that would be greatly appreciated.

Which scanner do you have and what do you want to achieve?

The README files explains how to install/use it. If you want to add a
scanner, you must change both the source code and the config file.

Bye,
  Henning



From henning at meier-geinitz.de  Mon Oct 11 13:27:42 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 11 Oct 2004 14:27:42 +0200
Subject: [sane-devel] unsubscribe moasta27
In-Reply-To: <000001c4aef6$077d5a60$0100a8c0@BLANCA>
References: <20041010153205.GJ3144@meier-geinitz.de> <000001c4aef6$077d5a60$0100a8c0@BLANCA>
Message-ID: <20041011122742.GE8269@meier-geinitz.de>

Hi,

On Sun, Oct 10, 2004 at 08:21:54PM +0200, Klinger wrote:
> I wanted to develop a backend for my hp scanjet 4500 scanner, but i've seen
> it'll take about 4 weeks or more just to analyze the protocol. My wife will
> kill me if i'm doing it ;)

Please read the footer added to each message sent to sane-devel to
find out how to unsubscribe:

> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org


Bye,
  Henning



From georg.halfas at gmx.net  Mon Oct 11 18:51:04 2004
From: georg.halfas at gmx.net (Georg Halfas)
Date: Mon, 11 Oct 2004 19:51:04 +0200
Subject: [sane-devel] Unsubscribe
Message-ID: <200410111951.04689.georg.halfas@gmx.net>

sorry I forgot my password so I cannot unsubscribe
-- 
Mit freundlichen Gr??en

Georg Halfas
_____________________________________________________________________________
Dipl.-Ing. Georg Halfas
Landschaftsarchitekt
Preystra?e 11
22303 Hamburg
info.hamburg at architektur-und-landschaft.de



From henning at meier-geinitz.de  Mon Oct 11 19:51:15 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 11 Oct 2004 20:51:15 +0200
Subject: [sane-devel] Unsubscribe
In-Reply-To: <200410111951.04689.georg.halfas@gmx.net>
References: <200410111951.04689.georg.halfas@gmx.net>
Message-ID: <20041011185115.GF17236@meier-geinitz.de>

Hi,

On Mon, Oct 11, 2004 at 07:51:04PM +0200, Georg Halfas wrote:
> sorry I forgot my password so I cannot unsubscribe

Well, I repeat: Read the footer! :-)
There is a link at the bottom of the web site page linked to in the
footer where you can enter your mail address address and get a
password reminder mail.

> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org

If you still can't unsubscribe please tell me (privately) the email
address you used to subscribe and I'll try to find and delete your
address from the list.

bye,
  Henning



From rene at exactcode.de  Mon Oct 11 21:54:06 2004
From: rene at exactcode.de (=?ISO-8859-1?Q?Ren=E9_Rebe?=)
Date: Mon, 11 Oct 2004 22:54:06 +0200
Subject: [sane-devel] Scanner Button
In-Reply-To: <Pine.LNX.4.61.0410091126330.30301@limos.pfeiffer.edu>
References: <1097329832013643@lycos-europe.com> <Pine.LNX.4.61.0410091126330.30301@limos.pfeiffer.edu>
Message-ID: <416AF2EE.3000407@exactcode.de>

Hi,

m. allan noah wrote:

> there has been much discussion in the past, but everyone seems too busy 
> to actually get anything in writing. search the archives of the sane 
> mailing list, there where several threads about it in the earlier part 
> of this year, IIRC.
> 
> basically:
> 
> front end polling a backend via asking for updates on certain OPTs seems 
> to be the consensus. details that need work: how to identify which opts, 
> recommendations for how frontends could display that data, and does the 
> backend need to be able to specify the polling interval. how the buttons 
> are affected by the network scanner locking code also seems like a good 
> topic for discussion.
> 
> allan
> 
> On Sat, 9 Oct 2004, Ullrich Sigwanz wrote:
> 
>> Hi all,
>>
>> Are there thoughts /ideas/implementations for including the button
>> handling in SANE (resp. SANE2) in a standardized way?
>>
>> (e.g. a polling daemon, callbacks to start applications etc.)

Proof of concept implemented in the Avision backend (might not yet be in 
CVS - I merge in the next days). Code is here:

   http://svn.exactcode.de/sane-avision/trunk/

An example "how to poll the buttons":

   http://svn.exactcode.de/sane-avision/trunk/sanebuttonsd/

Have fun,

PS: I might mail with the wrong From: address for the list - sorry.

-- 
Ren? Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
             +49 (0)30  255 897 45



From joehenley at kc.rr.com  Mon Oct 11 23:23:08 2004
From: joehenley at kc.rr.com (Joe Henley)
Date: Mon, 11 Oct 2004 17:23:08 -0500
Subject: [sane-devel] umax_pp slow
In-Reply-To: <41699E2A.5010109@kc.rr.com>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com> <20041001042733.GA2166@wanadoo.fr> <415D7E43.8080907@kc.rr.com> <20041004044644.GA6220@wanadoo.fr> <41699E2A.5010109@kc.rr.com>
Message-ID: <416B07CC.2040302@kc.rr.com>

Stef,

I made some changes.  In looking on Google I see that RedHat 9 doesn't 
activate ECP as a default.  I recompiled the parport module section and 
now I'm getting ECP!  Cool.  Now the data is:

run export ....
run scanimage -L 2>log
-------------------------------------------------------------
[sanei_debug] Setting debug level of umax_pp_low to 1.
[umax_pp_low] SANE_INB level 3
[umax_pp_low] sanei_umax_pp_InitPort(0x378,)
[umax_pp_low] sanei_ioperm(0x378, 8, 1) OK ...
[umax_pp_low] status 128 doesn't match! umax_pp_low.c:4927
[umax_pp_low] No scanner detected by 'ringScanner(2,0)'...
[umax_pp_low] status 128 doesn't match! umax_pp_low.c:4927
[umax_pp_low] No scanner detected by 'ringScanner(5,0)'...
[umax_pp_low] status 128 doesn't match! umax_pp_low.c:4927
[umax_pp_low] No scanner detected by 'ringScanner(5,10000)'...
[umax_pp_low] status 128 doesn't match! umax_pp_low.c:4927
[umax_pp_low] No scanner detected by 'ringScanner(5,10000)'...
[umax_pp_low] No 1220P/2000P scanner detected by 'ringScanner()'...
[umax_pp_low] Trying 610p (umax_pp_low.c:7346)
[umax_pp_low] connect610p control=0F, expected 0x0E (umax_pp_low.c:3860)
[umax_pp_low] connect610p control=0F, expected 0x0C (umax_pp_low.c:3870)
[umax_pp_low] connect610p control=0F, expected 0x0E (umax_pp_low.c:3880)
[umax_pp_low] connect610p control=0F, expected 0x0C (umax_pp_low.c:3890)
[umax_pp_low] connect610p control=07, expected 0x04 (umax_pp_low.c:3899)
[umax_pp_low] sync610p failed (got 0x80 expected 0x38)! (umax_pp_low.c:3683)
[umax_pp_low] sync610p failed! Scanner not present or powered off ... 
(umax_pp_low.c:6232)
[umax_pp_low] initTransport610p() failed (umax_pp_low.c:6536)


run ./ppdiag
----------------------------------------------------------------
[root at Eddie tools]# ./ppdiag
S01: parport built as module
S02: parport0:
S02:    modes:PCSPP,TRISTATE,COMPAT,ECP
S02:    ADDR :0x378
S02:    IRQ  :7
S02:    DMA  :no DMA used
S03: parport parameters are: options parport_pc io=0x378 io_hi=0x778 
irq=7 dma=none
S10: ppdev built as module
S12: /dev/parport0 exists ...
S12: /dev/parport0 is readable ...
S12: /dev/parport0 is writable ...
successfull end ....

The contents of umax_pp.conf are:
-------------------------------------------
option buffer 8388608
port 0x378
option astra 2000

The /etc/modules.conf includes:
-------------------------------------------
alias parport_lowlevel parport_pc
options parport_pc io=0x378 io_hi=0x778 irq=7 dma=none

When I run lsmod, I get the following relevant items:
------------------------------------------------------
ppdev                   6796   0  (unused)
parport_pc             31848   1  (autoclean)
lp                      8996   0  (autoclean)
parport                37056   1  (autoclean) [ppdev parport_pc lp]

The BIOS is set to ECP, IRQ=7, Addr=0x378, DMA=3

I reset (pc off, scanner off, scanner on, pc on) the scanner before 
these runs of the tests.

The scanner is on, despite the messages when I ran these.

OK, so now I've got ECP; what's next?   ... thanks for all your help!

Joe Henley

Joe Henley wrote:
> Hi Stef,
> 
> Sorry for the delay in responding.  I was out of town on business.
> 
> svoltz at wanadoo.fr wrote:
> 
>>     Hello,
>>
>>     I think you should try again ECP. I think the message you get is
>> harmless. You can comment it out in the sourcecode before doing tests
>> again. 
> 
> 
> I'm not sure I understand which message you're referring to.  With the 
> BIOS set for ECP, it (scanimage -L 2>log) just runs on without stopping. 
>  I have to use ^C to stop it.  Is that the message you refer to?
> 
> The BIOS says it's ECP, but Linux doesn't report it that way in the 
> /var/log/messages or kernel files.  Very odd!  Even more odd is that I 
> run Win4Lin on this machine, using Win98.  I can run Linux running 
> Win4Lin, running Win98, running the VistaScan copier program, and it 
> runs just fine.  The speed is very good.  So somehow it's figuring out 
> to run quickly thru the parallel port.  If I shut down 
> VistaScan/Win98/Win4Lin and without rebooting, load up sane and try it, 
> it's very slow.  Arrrgh!
> 
> Any suggestions?
> 
>>     But until you see ECP mode detected by ythe linux kernel, I'm
>> afraid you'll have troubles.
>>
>> Regards,
>>     Stef
>>
> Thanks!
> 
> Joe Henley
> 



From afb at paradise.net.nz  Tue Oct 12 04:20:31 2004
From: afb at paradise.net.nz (Adam Bogacki)
Date: Tue, 12 Oct 2004 16:20:31 +1300
Subject: [sane-devel] xsane-win32
In-Reply-To: <1097513065.2140.1.camel@Babylon7>
References: <416A554D.6000509@paradise.net.nz>
 <1097513065.2140.1.camel@Babylon7>
Message-ID: <416B4D7F.4000901@paradise.net.nz>

I should have mentioned that I have just set up a network - an old P I 
running Win 98 configured
with the XP drive on my PIII machine to give an 80 yr old lady some 
email and browser access.

I intend to also try setting up a Linux network using Tulip when I get 
around to it.

This could be used to access Xsane on the PIII server.
I presume I would use 'net' and appropriate DNS settings.

 Any tips on config ?

Adam.

Oliver Rauch wrote:

>Hello Adam,
>
>it looks like you want to use xsane-win32 to work with a scanner that
>is locally connected to the windows machine. This does not work yet.
>
>Oliver
>
>Am Mon, 2004-10-11 um 11.41 schrieb Adam Felix Bogacki:
>  
>
>>Sorry Oliver. I removed and re-installed  Epson Smart Panel for Scanner 
>>and Twain and it
>>recognised the scanner and was usable. However, xsane springs into action,
>>shows me the 'Xsane End User Licence Agreement', and after I click the 
>>'I accept' panel
>>searches around and quickly gives me  'no devices available'.
>>
>>It was doing this when Smart Panel and Twain were not working so I don't 
>>think it may be
>>a case of the scanner being assigned to one program and denied to 
>>another. I could be wrong.
>>
>>I have gone through the 'help' list of  possible reasons for this and 
>>the only thing which looks
>>plausible is  'backend is not configured correct'.
>>
>>In 'C:\sane\etc\sane.d\net.conf' I used 'localhost' and '192.168.0.1' - 
>>the localhost TCP/IP address ..
>>
>>In 'C:\sane\etc\sane.d\dll.conf' the only lines enabled are 'epson' and 
>>'gphoto2' (in case of future digital camera use) , and in
>>
>>'C:\sane\etc\sane.d\epson.conf' the only uncommented lines are
>>
>>'usb 0x04b8 0x010c' and 'usb /dev/usb/scanner0'
>>
>>Are there any obvious errors here ? Confusion of backward and forward slashes ?
>>
>>One thing I came across in reading WinXP help files was that Twain does not work
>>after the scanner is disconnected (as in re-plugging with Linux hotplug). It then has to be
>>reinstalled via XP's 'New Hardware Install' wizard. 
>>
>>Could this be contributing here ?
>>
>>It's frustrating having a fine program like xsane not working in XP. 
>>
>>Adam Bogacki,
>>afb at paradise.net.nz
>>
>>
>>    
>>
>
>
>
>  
>




From gerhard at gjaeger.de  Tue Oct 12 09:52:25 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Tue, 12 Oct 2004 10:52:25 +0200
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <00f201c4abaa$23c46500$6601a8c0@khp5000elaptop>
References: <00f201c4abaa$23c46500$6601a8c0@khp5000elaptop>
Message-ID: <200410121052.25872.gerhard@gjaeger.de>

Hi,

On Wednesday 06 October 2004 15:41, Kenneth H. Peters wrote:
> Gergard, thanks for the assist ... :) ...
>
> As you requested, below is output from two scan sessions:
>
> 	1.) scanimage -x 10 -y 10 --format=tiff --resolution 50
> 	2.) scanimage -x 10 -y 10 --format=tiff --resolution 300
>
> I am curious to know what specifically you are look for? An engineer here
> believes this is a Big-Endian issue, but I have not been able to nail it
> down.

sorry for ignoring your mail so far - I'm short of time (anyway who is not ;)
First I thought, that there's really something wrong with BE/LE on the
backend, but when comparing the register settings on my box and on your box
everything looks fine. The picture data are 8bit wide and therefore I guess
there's no problem.
Did you do all scans using TIFF? Can you please check PNM output too?

Ciao,
  Gerhard




From svoltz at wanadoo.fr  Tue Oct 12 20:07:12 2004
From: svoltz at wanadoo.fr (svoltz at wanadoo.fr)
Date: Tue, 12 Oct 2004 21:07:12 +0200
Subject: [sane-devel] umax_pp slow
In-Reply-To: <416B07CC.2040302@kc.rr.com>
References: <415B239D.5010808@kc.rr.com> <20040930190010.GA2152@wanadoo.fr> <415C7DD3.3090102@kc.rr.com> <20041001042733.GA2166@wanadoo.fr> <415D7E43.8080907@kc.rr.com> <20041004044644.GA6220@wanadoo.fr> <41699E2A.5010109@kc.rr.com> <416B07CC.2040302@kc.rr.com>
Message-ID: <20041012190712.GA2278@wanadoo.fr>

	Hello, 

	I checked that ECP was still working on my laptop. I'll try
on my other linux box to see if I get the same. Can you raise trace 
level to 255 and send me the output of the test program ?

Regards,
	Stef



From mogensjaeger at get2net.dk  Tue Oct 12 22:32:55 2004
From: mogensjaeger at get2net.dk (Mogens Jaeger)
Date: Tue, 12 Oct 2004 23:32:55 +0200
Subject: [sane-devel] Translation
In-Reply-To: <20041010153205.GJ3144@meier-geinitz.de>
References: <41694E3E.7080109@get2net.dk> <20041010153205.GJ3144@meier-geinitz.de>
Message-ID: <416C4D87.4050807@get2net.dk>

Hello

I have been working on the Danish translation of Sane-backends-1.0.15 - 
from cvs.

I don't understand the meaning of:

Red-gain value of the AFE

This AFE - is it a professional term that's not needed to translate, or????

sincerely

-- 
mvh Mogens J?ger




From bertrik at zonnet.nl  Tue Oct 12 23:57:35 2004
From: bertrik at zonnet.nl (Bertrik Sikken)
Date: Wed, 13 Oct 2004 00:57:35 +0200
Subject: [sane-devel] Translation
In-Reply-To: <416C4D87.4050807@get2net.dk>
References: <41694E3E.7080109@get2net.dk> <20041010153205.GJ3144@meier-geinitz.de> <416C4D87.4050807@get2net.dk>
Message-ID: <416C615F.8010309@zonnet.nl>

Mogens Jaeger wrote:
> Hello
> 
> I have been working on the Danish translation of Sane-backends-1.0.15 - 
> from cvs.
> 
> I don't understand the meaning of:
> 
> Red-gain value of the AFE
> 
> This AFE - is it a professional term that's not needed to translate, or????

AFE means analog front-end.

This is an electronic circuit that processes the analog signals from
the CCD. The AFE chip that I have some knowledge about, contains an
amplifier for each color channel that can be configured in coarse steps.
It is used to make the dynamic range of the CCD signal roughly equal
(but slightly lower) than the dynamic range of the A/D converter
(hope this still makes sense)
The gain of the amplifier for the red color channel is probably what is
meant here.

I don't know how to translate it. I think it's a very technical term
that end users probably should not even need to know about.

Regards,
Bertrik




From kpeters at lhsolutions.com  Wed Oct 13 00:46:32 2004
From: kpeters at lhsolutions.com (Ken Peters (NEW))
Date: Tue, 12 Oct 2004 19:46:32 -0400
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <200410121052.25872.gerhard@gjaeger.de>
Message-ID: <004001c4b0b5$b48b3e50$6400a8c0@kpdesktop>

Gerhard:

I figure you are pretty busy! ... I appreciate any support you provide. 

I get the same results for both TIFF and PNG. 

I am currently going through the process of looking at the raw data from the
scanner. I'll keep plug-in away ... 

Thanks,
K.P.

-----Original Message-----
From: sane-devel-admin at lists.alioth.debian.org
[mailto:sane-devel-admin at lists.alioth.debian.org] On Behalf Of Gerhard
Jaeger
Sent: Tuesday, October 12, 2004 3:52 AM
To: Kenneth H. Peters
Cc: sane-devel at lists.alioth.debian.org
Subject: Re: [sane-devel] Interesting image problem when scanning color ...

Hi,

On Wednesday 06 October 2004 15:41, Kenneth H. Peters wrote:
> Gergard, thanks for the assist ... :) ...
>
> As you requested, below is output from two scan sessions:
>
> 	1.) scanimage -x 10 -y 10 --format=tiff --resolution 50
> 	2.) scanimage -x 10 -y 10 --format=tiff --resolution 300
>
> I am curious to know what specifically you are look for? An engineer here
> believes this is a Big-Endian issue, but I have not been able to nail it
> down.

sorry for ignoring your mail so far - I'm short of time (anyway who is not
;)
First I thought, that there's really something wrong with BE/LE on the
backend, but when comparing the register settings on my box and on your box
everything looks fine. The picture data are 8bit wide and therefore I guess
there's no problem.
Did you do all scans using TIFF? Can you please check PNM output too?

Ciao,
  Gerhard


-- 
sane-devel mailing list: sane-devel at lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request at lists.alioth.debian.org




From sean035 at yahoo.com.tw  Wed Oct 13 02:56:18 2004
From: sean035 at yahoo.com.tw (sean035 at yahoo.com.tw)
Date: Wed, 13 Oct 2004 09:56:18 +0800 (CST)
Subject: [sane-devel] scanimage can't detect my scanner.
Message-ID: <20041013015618.51521.qmail@web17808.mail.tpe.yahoo.com>

Hi everyone,
I have a question about scanimage.
How do I edit my scanner backend source code to make
the scanimage can detect my new scanner device?
Because my scanner can work on my new backend, but
scanimage can't detect it.
Anybody can tell me why?
Thanks a lot.

Walker,

-----------------------------------------------------------------
Yahoo!??????
100MB ?????????????????
http://mail.yahoo.com.tw/



From gerhard at gjaeger.de  Wed Oct 13 07:56:05 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Wed, 13 Oct 2004 08:56:05 +0200
Subject: [sane-devel] scanimage can't detect my scanner.
In-Reply-To: <20041013015618.51521.qmail@web17808.mail.tpe.yahoo.com>
References: <20041013015618.51521.qmail@web17808.mail.tpe.yahoo.com>
Message-ID: <200410130856.05124.gerhard@gjaeger.de>

On Wednesday 13 October 2004 03:56, sean035 at yahoo.com.tw wrote:
> Hi everyone,
> I have a question about scanimage.
> How do I edit my scanner backend source code to make
> the scanimage can detect my new scanner device?
> Because my scanner can work on my new backend, but
> scanimage can't detect it.
> Anybody can tell me why?

Tell us more about your backend. Is it integrated in SANE? Is it enabled
in /<your sysconfig path>/sane.d/dll.conf?
Have you red sane-backends/doc/backend-writing.txt?

Again my question, what scanner-backend are your working on?

Regards,
  Gerhard




From eppesuig at users.sourceforge.net  Tue Oct 12 23:02:21 2004
From: eppesuig at users.sourceforge.net (Giuseppe Sacco)
Date: Wed, 13 Oct 2004 00:02:21 +0200
Subject: [sane-devel] Translation
In-Reply-To: <416C4D87.4050807@get2net.dk>
References: <41694E3E.7080109@get2net.dk>
	 <20041010153205.GJ3144@meier-geinitz.de>  <416C4D87.4050807@get2net.dk>
Message-ID: <1097618540.9579.8.camel@casa>

Il mar, 2004-10-12 alle 23:32, Mogens Jaeger ha scritto:
> Hello
> 
> I have been working on the Danish translation of Sane-backends-1.0.15 - 
> from cvs.
> 
> I don't understand the meaning of:
> 
> Red-gain value of the AFE
> 
> This AFE - is it a professional term that's not needed to translate, or????

I hope that it is the "Analog FrontEnd" mentioned two string earlier,
otherwise I made a wrong translation :-(

Bye,
Giuseppe




From mogensjaeger at get2net.dk  Wed Oct 13 15:33:59 2004
From: mogensjaeger at get2net.dk (Mogens Jaeger)
Date: Wed, 13 Oct 2004 16:33:59 +0200
Subject: [sane-devel] Error at translation
Message-ID: <416D3CD7.8020900@get2net.dk>

Hello

When I in emacs runs the 'Validate' command, on the sane-backends da.po 
file, I get the folloving error:

cd ~/Oversaettelse/Sane-backends-1.0.15/
msgfmt --statistics -c -v -o /dev/null
/home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po
/home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po:1268:
'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the
directive number 1, the character 'b' is not a valid conversion specifier.

The message looks this way:

#: .tmp/microtek2.h:697
#, c-format
msgid "Balance factor for red. A value of 100% means no correction."
msgstr "Balancefaktor for roed. Vaerdien 100% betyder ingen korrektion."

I have asked in my Language-Team, and one said that there should not be 
a '#, c-format' up front???????

I had 3 messages with errors like this, lines in da.po file : 1268 
(above), 1277 and 1268, all with the same errormessage.

-- 
mvh Mogens J?ger




From mogensjaeger at get2net.dk  Wed Oct 13 15:36:16 2004
From: mogensjaeger at get2net.dk (Mogens Jaeger)
Date: Wed, 13 Oct 2004 16:36:16 +0200
Subject: [sane-devel] Translation
In-Reply-To: <1097618540.9579.8.camel@casa>
References: <41694E3E.7080109@get2net.dk>	 <20041010153205.GJ3144@meier-geinitz.de>  <416C4D87.4050807@get2net.dk> <1097618540.9579.8.camel@casa>
Message-ID: <416D3D60.7020807@get2net.dk>

Giuseppe Sacco skrev:

>Il mar, 2004-10-12 alle 23:32, Mogens Jaeger ha scritto:
>  
>
>>Hello
>>
>>I have been working on the Danish translation of Sane-backends-1.0.15 - 
>>from cvs.
>>
>>I don't understand the meaning of:
>>
>>Red-gain value of the AFE
>>
>>This AFE - is it a professional term that's not needed to translate, or????
>>    
>>
>
>I hope that it is the "Analog FrontEnd" mentioned two string earlier,
>otherwise I made a wrong translation :-(
>
>Bye,
>Giuseppe
>
>
>  
>
You are right - sorry for missing the connection betwen Analog Frontend 
and AFE :-!

-- 
mvh Mogens J?ger




From fzago at austin.rr.com  Wed Oct 13 16:18:51 2004
From: fzago at austin.rr.com (Frank Zago)
Date: Wed, 13 Oct 2004 10:18:51 -0500
Subject: [sane-devel] Error at translation
In-Reply-To: <416D3CD7.8020900@get2net.dk>
References: <416D3CD7.8020900@get2net.dk>
Message-ID: <416D475B.9030303@austin.rr.com>

Mogens Jaeger wrote:
> Hello
> 
> When I in emacs runs the 'Validate' command, on the sane-backends da.po 
> file, I get the folloving error:
> 
> cd ~/Oversaettelse/Sane-backends-1.0.15/
> msgfmt --statistics -c -v -o /dev/null
> /home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po
> /home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po:1268:
> 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the
> directive number 1, the character 'b' is not a valid conversion specifier.
> 
> The message looks this way:
> 
> #: .tmp/microtek2.h:697
> #, c-format
> msgid "Balance factor for red. A value of 100% means no correction."
> msgstr "Balancefaktor for roed. Vaerdien 100% betyder ingen korrektion."
> 
> I have asked in my Language-Team, and one said that there should not be 
> a '#, c-format' up front???????
> 
> I had 3 messages with errors like this, lines in da.po file : 1268 
> (above), 1277 and 1268, all with the same errormessage.
> 

It's a bug in the original string "...100% means". The "%" should be "%%". The 
source code must be updated.

Frank.



From henning at meier-geinitz.de  Wed Oct 13 16:19:27 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 13 Oct 2004 17:19:27 +0200
Subject: [sane-devel] Error at translation
In-Reply-To: <416D3CD7.8020900@get2net.dk>
References: <416D3CD7.8020900@get2net.dk>
Message-ID: <20041013151927.GF8948@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 04:33:59PM +0200, Mogens Jaeger wrote:
> When I in emacs runs the 'Validate' command, on the sane-backends da.po 
> file, I get the folloving error:
> 
> cd ~/Oversaettelse/Sane-backends-1.0.15/
> msgfmt --statistics -c -v -o /dev/null
> /home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po
> /home/mogens/Oversaettelse/Sane-backends-1.0.15/sane-backends.da.po:1268:
> 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the
> directive number 1, the character 'b' is not a valid conversion specifier.

I have also gotten similar messages while updating .de.po.

As far as I can see xgettext tries to be intelligent by marking
everything that containts a % as c-format. It's not intelligent
enough to really find out which string is intended as a format string
and which is not.

We could use the flag option for xgettext:

$(XGETTEXT) -dsane-backends -kSANE_I18N --flag=SANE_I18N:1:no-c-format $(TMP_FILE_DIR)/*.*

That marks all strings as "no-c-format". However, I don't know how
compatible that is.

Other ideas?

Bye,
  Henning



From stan at saticed.me.uk  Wed Oct 13 16:23:29 2004
From: stan at saticed.me.uk (Tristan Hill)
Date: Wed, 13 Oct 2004 16:23:29 +0100
Subject: [sane-devel] scanadf: waiting for child processes to finish
Message-ID: <20041013152329.GA28252@marge.cehill.co.uk>


I use the --scan-script option with scanadf, however, if I want to do
some work on all the files processed by the script is it difficult
because scanadf may finish before one or more of the script processes
do.  For example, I want to use it to combine the processed images into
a single file.  As scanadf knows what processes it has forked I thought
it easiest to use wait(), implemented as per attached patch.  However, I
am open to other suggestions.

Thanks
-------------- next part --------------
--- scanadf.c.orig	2004-10-11 08:52:34.000000000 +0100
+++ scanadf.c	2004-10-13 15:47:42.000000000 +0100
@@ -39,6 +39,7 @@
 #include <string.h>
 #include <sys/types.h>
 #include <sys/stat.h>
+#include <sys/wait.h>
 
 #include "sane/sane.h"
 #include "sane/sanei.h"
@@ -102,6 +103,7 @@
   { "start-count", required_argument, 0, 's' },
   { "end-count", required_argument, 0, 'e' },
   { "scan-script", required_argument, 0, 'S' },
+  { "script-wait", no_argument, 0, 128 },
   { "raw", no_argument, 0, 'r' },
   {0, }
 };
@@ -137,6 +139,7 @@
    [ -o | --output-file <name> ]     name of file to write image data\n\
                                      (%%d replacement in output file name).\n\
    [ -S | --scan-script <name> ]     name of script to run after every scan.\n\
+   [ --script-wait ]                 wait for scripts to finish before exit\n\
    [ -s | --start-count <num> ]      page count of first scanned image.\n\
    [ -e | --end-count <num> ]        last page number to scan.\n\
    [ -r | --raw ]                    write raw image data to file.\n";
@@ -1281,6 +1284,7 @@
   char *full_optstring;
   SANE_Bool raw = SANE_FALSE;
   const char *scanScript = NULL;		/* script to run at end of scan */
+  int scriptWait = 0;
   const char *outputFile = "image-%04d";	/* file name(format) to write output to */
   int startNum = 1, endNum = -1;		/* start/end numbers of pages to scan */
   int no_overwrite = 0;
@@ -1335,6 +1339,7 @@
 
 	case 'o': outputFile = optarg; break;
 	case 'S': scanScript = optarg; break;
+	case 128: scriptWait = 1; break;
 	case 's': startNum = atoi(optarg); break;
 	case 'e': endNum = atoi(optarg); break;
 	case 'r': raw = SANE_TRUE; break;
@@ -1348,6 +1353,9 @@
 	}
     }
 
+  if (scriptWait && !scanScript)
+    scriptWait = 0;
+
   if (help)
     printf (usage, prog_name);
 
@@ -1574,6 +1582,9 @@
   sane_cancel (device);
   sane_close (device);
 
+  if (scriptWait)
+    while (wait(NULL) != -1);
+
   return (status == SANE_STATUS_GOOD) ? 0 : 1;
 }
 

From henning at meier-geinitz.de  Wed Oct 13 16:29:36 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 13 Oct 2004 17:29:36 +0200
Subject: [sane-devel] Error at translation
In-Reply-To: <416D475B.9030303@austin.rr.com>
References: <416D3CD7.8020900@get2net.dk> <416D475B.9030303@austin.rr.com>
Message-ID: <20041013152936.GG8948@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 10:18:51AM -0500, Frank Zago wrote:
> It's a bug in the original string "...100% means". The "%" should be "%%". 
> The source code must be updated.

Are you sure? SANE titles and descriptions are not C format strings.
If you use "%%" you'll get "%%" in the output.

Bye,
  Henning



From karsten.pietsch at gmx.de  Wed Oct 13 20:52:25 2004
From: karsten.pietsch at gmx.de (Karsten Pietsch)
Date: Wed, 13 Oct 2004 21:52:25 +0200
Subject: [sane-devel] [Fwd: [Bug 3531] problems with my usb-scanner canon630u (sane)]
Message-ID: <416D8779.8090705@gmx.de>

hello!

in the attachment is my bug-report for the kernel-peoples....

i got a answer with  the tip to send thes bug to the x-sane-people....

hier is my problem:-)


-------------- next part --------------
An embedded message was scrubbed...
From: bugme-daemon at osdl.org
Subject: [Bug 3531] problems with my usb-scanner canon630u (sane)
Date: Wed, 13 Oct 2004 10:05:51 -0700
Size: 2050
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041013/f6082e29/attachment.eml>

From henning at meier-geinitz.de  Wed Oct 13 19:16:42 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 13 Oct 2004 20:16:42 +0200
Subject: [sane-devel] [Fwd: [Bug 3531] problems with my usb-scanner canon630u (sane)]
In-Reply-To: <416D8779.8090705@gmx.de>
References: <416D8779.8090705@gmx.de>
Message-ID: <20041013181642.GH8948@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 09:52:25PM +0200, Karsten Pietsch wrote:
> hello!
> 
> in the attachment is my bug-report for the kernel-peoples....
> 
> i got a answer with  the tip to send thes bug to the x-sane-people....
> 
> hier is my problem:-)

If the error message is really "device busy" it just means that.
Another program is blocking your scanner. Otherwise it's proabably a
kernel or hardware issue.

Could you please show us a debug log? E.g.:

SANE_DEBUG_CANON630U=255 scanimage -y 10 >/dev/null 2>dbg.log

Bye,
  Henning



From fbakan at gmx.net  Wed Oct 13 22:25:08 2004
From: fbakan at gmx.net (Franz Bakan)
Date: Wed, 13 Oct 2004 23:25:08 +0200 (CEST)
Subject: [sane-devel] compiling with gcc 3.3.4 on OS/2
Message-ID: <mailman.83.1670069770.26652.sane-devel@alioth-lists.debian.net>

Hi,

I'm trying to build with gcc 3.3.4 and besides other small problems

compiling fails with:

sanei_scsi.c: In function `sanei_scsi_find_devices':
sanei_scsi.c:3857: error: assignment of read-only member `str'
sanei_scsi.c:3858: error: assignment of read-only member `str'
sanei_scsi.c:3859: error: assignment of read-only member `str'
sanei_scsi.c:3860: error: assignment of read-only member `str'
sanei_scsi.c:3861: error: assignment of read-only member `i'
sanei_scsi.c:3862: error: assignment of read-only member `i'
sanei_scsi.c:3863: error: assignment of read-only member `i'
sanei_scsi.c:3864: error: assignment of read-only member `i'

I didn't have seen this problem with earlier versions of gcc.

Is there a solution or compiler-flag to solve the problem?

BTW Sane-CVS-code still compiles fine with earlier versions of gcc.

Franz





From mreuther at umich.edu  Thu Oct 14 03:48:53 2004
From: mreuther at umich.edu (Matt Reuther)
Date: Wed, 13 Oct 2004 22:48:53 -0400
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
Message-ID: <200410132249.08934.mreuther@umich.edu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi. I picked up an Epson Perfection 4180 scanner. I have it plugged into a 
USB 2.0 card. I have Slackware 10 on my computer, with linux-2.4.27 
installed on top of it. I am using xsane-0.93 compiled against GTK-2.4.1 
and with GIMP 2.0 support.

The scanner shows up in lsusb, and I set permissions and added the 
vendor/product ID to /etc/hotplug/usb.usermap, so it works with libusb. It 
shows up with scanimage -L and if I start xsane, I can pick it from the 
devices list. However, xsane crashes once I pick the scanner.

I set SANE_DEBUG_DLL=3 and captured the output. It's attached.

Any ideas?
- -- 
Matt Reuther
mreuther at umich.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD4DBQFBbekjFse4xrb7oagRAhAgAKCDy1eifHc2JzEmActdNn45JjIssACXcYhs
+0+OnCxEvvt2gCz4HOex3Q==
=ECYu
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sanelog-dll-epson4180.txt.bz2
Type: application/x-bzip2
Size: 1382 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041013/20ded007/attachment.bin>

From gerhard at gjaeger.de  Thu Oct 14 07:53:32 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Thu, 14 Oct 2004 08:53:32 +0200
Subject: [sane-devel] Re: [sane-commit] CVS update: sane-backends/backend
In-Reply-To: <4131C12D.4050107@freesurf.ch>
References: <4131C12D.4050107@freesurf.ch>
Message-ID: <200410140853.32953.gerhard@gjaeger.de>

Hi Ullrich,

could it be that you've missed to add your changes to the Changelog?
No worries ;) I've just added that, because I also needed to change it.
Hope it's okay.
  Gerhard




From gerhard at gjaeger.de  Thu Oct 14 07:58:42 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Thu, 14 Oct 2004 08:58:42 +0200
Subject: [sane-devel] memory problem
In-Reply-To: <200408261201.55683.oschirr@abm.de>
References: <200408251749.12668.oschirr@abm.de> <200408261012.09052.gerhard@gjaeger.de> <200408261201.55683.oschirr@abm.de>
Message-ID: <200410140858.42684.gerhard@gjaeger.de>

Hi Oliver, hi all,

On Thursday 26 August 2004 12:01, Oliver Schirrmeister wrote:
> Am Donnerstag 26 August 2004 10:12 schrieb Gerhard Jaeger:
> > [SNIPSNAP]
> >
> > > I've linked the sane backends statically with the 'frontend'. The
> > > problem is the same. The pthread lib is linked dynamically.
> > > I've tried valgrind. That revealed only two 'real' memory leaks in some
> > > init-routines of sanei_usb, the test backend and the pthread library,
> > > nothing severe.
> >
> > Is the sanei_usb memory-leak related to the patch you've sent me?
>
> Yes.
>
> > > Under control of valgrind the vm-size doesn't increase !?!
> >
> > Hmmm, strange...
> > anybody out there with some ideas?
>
> valgrind supplies its own libpthread.so, probably without that bug?
>
> > On what box are you working? Kernel-Version and glibc Version?
>
> Linux version 2.4.20-8 (bhcompile at porky.devel.redhat.com) (gcc version
> 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003
>
> RedHat 9.0 P4-2.8, libc-2.3.2

I remember this old issue with some memory problems, when using the pthread on
linux. In the meantime I checked the sanei_thread stuff again and I noticed,
that the call to pthread_detach() is missing after the pthread_join(). This
pthread_detach() is necessary to mark the pthread resources for further usage
by next threads. As long, as scanimage is used to scan only one picture this
does not make any problems, but when using scanadf (I think Oliver did this),
the thread resources won't be freed and will eat up the memory.

The applied fix should fix this problem. 
@Oliver: Could you please test with your scenario?

Ciao,
  Gerhard






From henning at meier-geinitz.de  Thu Oct 14 12:55:40 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 13:55:40 +0200
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <200410132249.08934.mreuther@umich.edu>
References: <200410132249.08934.mreuther@umich.edu>
Message-ID: <20041014115540.GA12141@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 10:48:53PM -0400, Matt Reuther wrote:
> Hi. I picked up an Epson Perfection 4180 scanner.

That scanner is not in our lists. But maybe it's supported under a
different name?

> I have it plugged into a USB 2.0 card. I have Slackware 10 on my
> computer, with linux-2.4.27 installed on top of it. I am using
> xsane-0.93 compiled against GTK-2.4.1 and with GIMP 2.0 support.
> 
> The scanner shows up in lsusb, and I set permissions and added the 
> vendor/product ID to /etc/hotplug/usb.usermap, so it works with libusb. It 
> shows up with scanimage -L and if I start xsane, I can pick it from the 
> devices list. However, xsane crashes once I pick the scanner.

Can you show us the "scanimage -L" output, please?

> I set SANE_DEBUG_DLL=3 and captured the output. It's attached.
> 
> Any ideas?

Looks like it crashes when handling option resolution. Please run
xsane again with SANE_DEBUG_EPSON=255. Does it also happen when
scanning with scanimage or other frontends?

Bye,
  Henning



From henning at meier-geinitz.de  Thu Oct 14 13:00:30 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 14:00:30 +0200
Subject: [sane-devel] compiling with gcc 3.3.4 on OS/2
In-Reply-To: <E1CHqpj-0001Z6-00@mxng18.kundenserver.de>
References: <E1CHqpj-0001Z6-00@mxng18.kundenserver.de>
Message-ID: <20041014120030.GB12141@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 11:25:08PM +0200, Franz Bakan wrote:
> I'm trying to build with gcc 3.3.4 and besides other small problems
> 
> compiling fails with:
> 
> sanei_scsi.c: In function `sanei_scsi_find_devices':
> sanei_scsi.c:3857: error: assignment of read-only member `str'
> sanei_scsi.c:3858: error: assignment of read-only member `str'
> sanei_scsi.c:3859: error: assignment of read-only member `str'
> sanei_scsi.c:3860: error: assignment of read-only member `str'
> sanei_scsi.c:3861: error: assignment of read-only member `i'
> sanei_scsi.c:3862: error: assignment of read-only member `i'
> sanei_scsi.c:3863: error: assignment of read-only member `i'
> sanei_scsi.c:3864: error: assignment of read-only member `i'

The struct itsself is const so I guess a warning would be ok. I'm not
sure if the error is correct.

If I remember correctly, that code was changed to avoid error messages
from gcc some time ago. The assigments to u and i were done in the
initializer before that.

> I didn't have seen this problem with earlier versions of gcc.
> 
> Is there a solution or compiler-flag to solve the problem?

Make the struct non-const? I haven't checked the consequences.

Bye,
  Henning



From kpeters at LHSolutions.com  Wed Oct 13 22:16:28 2004
From: kpeters at LHSolutions.com (Kenneth H. Peters)
Date: Wed, 13 Oct 2004 17:16:28 -0400
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <004001c4b0b5$b48b3e50$6400a8c0@kpdesktop>
Message-ID: <000901c4b169$e8829190$6601a8c0@khp5000elaptop>

Gerhard:

More info ... 
 
I download, compiled and installed the latest 1.0.14 CVS version (this
version also exhibited the imaging anomalies with plustek.) I wanted to try
another backend, so I purchased the Epson 2480 (need latest CVS to support
this) and used the "snapscan" backend. 

I was able to scan using this scanner which indicates to me that any
big-endian issues associated with running on a IXP425 in BE mode is not in
the frontend (i.e. scanimage) but maybe in the backend. 

Attached is a ZIP file that contains output using the "script" command. 

The "gentoo_xxx" (Works fine) are files generated on the following:

	- Gentoo 2.6 kernel
	- x86
	- libusb
	- Canon LiDE 30
	- plustek backend
	- scanimage frontend

The "ixp425_xxx: (demonstrates "color-bar" problem) are files generated on
the following:

	- MV 2.4.18
	- IXP425 in big endian mode
	- Canon LiDE 30
	- plustek backend
	- scanimage frontend

These all used the "scanimage -x 10 -y 10"

There is additional output in the function "scan_it" from scanimage.c. This
diag output is from "if ((output_format == OUTPUT_TIFF) || (parm.depth !=
16)) and dumps "buffer". 

Please let me know what additional information I can provide. 

Thanks,
K.P.

-----Original Message-----
From: sane-devel-admin at lists.alioth.debian.org
[mailto:sane-devel-admin at lists.alioth.debian.org] On Behalf Of Ken Peters
(NEW)
Sent: Tuesday, October 12, 2004 7:47 PM
To: 'Gerhard Jaeger'
Cc: sane-devel at lists.alioth.debian.org
Subject: RE: [sane-devel] Interesting image problem when scanning color ...

Gerhard:

I figure you are pretty busy! ... I appreciate any support you provide. 

I get the same results for both TIFF and PNG. 

I am currently going through the process of looking at the raw data from the
scanner. I'll keep plug-in away ... 

Thanks,
K.P.

-----Original Message-----
From: sane-devel-admin at lists.alioth.debian.org
[mailto:sane-devel-admin at lists.alioth.debian.org] On Behalf Of Gerhard
Jaeger
Sent: Tuesday, October 12, 2004 3:52 AM
To: Kenneth H. Peters
Cc: sane-devel at lists.alioth.debian.org
Subject: Re: [sane-devel] Interesting image problem when scanning color ...

Hi,

On Wednesday 06 October 2004 15:41, Kenneth H. Peters wrote:
> Gergard, thanks for the assist ... :) ...
>
> As you requested, below is output from two scan sessions:
>
> 	1.) scanimage -x 10 -y 10 --format=tiff --resolution 50
> 	2.) scanimage -x 10 -y 10 --format=tiff --resolution 300
>
> I am curious to know what specifically you are look for? An engineer here
> believes this is a Big-Endian issue, but I have not been able to nail it
> down.

sorry for ignoring your mail so far - I'm short of time (anyway who is not
;)
First I thought, that there's really something wrong with BE/LE on the
backend, but when comparing the register settings on my box and on your box
everything looks fine. The picture data are 8bit wide and therefore I guess
there's no problem.
Did you do all scans using TIFF? Can you please check PNM output too?

Ciao,
  Gerhard


-- 
sane-devel mailing list: sane-devel at lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request at lists.alioth.debian.org


-- 
sane-devel mailing list: sane-devel at lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request at lists.alioth.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gentoo_vs_ixp425_plustek.zip
Type: application/x-zip-compressed
Size: 44794 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041013/35e40c19/attachment.bin>

From cnorton at biosensorhawaii.com  Wed Oct 13 16:23:14 2004
From: cnorton at biosensorhawaii.com (Chris Norton)
Date: Wed, 13 Oct 2004 11:23:14 -0400
Subject: [sane-devel] XEROX 620S SCSI Scanner.
Message-ID: <1097680994.2078.7.camel@superman.biosensorhawaii.com>

Is there any support for a XEROX D620S SCSI Scanner through sane?

I'm using Mandrake linux and with a Adaptec 2940 card.  sane-scan-finder
finds the Xerox scanner on /dev/sg0.

Under windows 98 the Twain and ISIS drivers worked without any
additional software. The point is that it appeared to be Twain and ISIS
compliant.

I really would like to use this scanner with linux. It's the only reason
I still have windows around.

Any help is appreciated.

Chris




From Thetargos at tutopia.com  Thu Oct 14 01:45:27 2004
From: Thetargos at tutopia.com (Gian Paolo Mureddu)
Date: Wed, 13 Oct 2004 19:45:27 -0500
Subject: [sane-devel] UMAX 2000 (HP3200c) scanner problems
Message-ID: <416DCC27.7010303@tutopia.com>

I had my UMAX 2000 branded HP 3200c (Parallel port) scanner working with 
SANE just fine after I edited the /etc/sane.d/dll.conf file to also look 
for this scanner, however (I don't know if it was coincidence or not, or 
if it has to do with the problem or not) after I upgreded my 
distribution (FC2) especially the GIMP to version 2.0.5 from 2.0.4, I 
could scan an image just fine, however while working on the scanned 
image (not yet saved) GIMP crashed (while xsane was still running). I 
tried to re-open xsane through GIMP, but xsane could not find my scanner 
anymore. When I tried running xsane or scanimage from the command line I 
get this output:

[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3281)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3933)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3281)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3933)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3281)
[umax_pp_low] Blindly going on .....
[umax_pp_low] Unexpected reg19: 0xE8 instead of 0xC0 or 0xD0 
(umax_pp_low.c:3980)
[umax_pp_low] CmdSetDataBuffer(initbuf) failed ! (umax_pp_low.c:5950)
scanimage: no SANE devices found

What does this mean?

Just for reference, the way I have setup the scanner is as follows: The 
scanner is attached to my Zip drive (parallel port also) which is 
connected to the parallel port (lp0)  on the computer, no printer is 
setup in the parallel port (I use an USB one). The parallel port is set 
to ECP and at an auto configured port in BIOS. Could this configuration 
be the conflicting point, even though it *was* working right? What can I 
do to have it working again?

Thanks in advance for any input.



From henning at meier-geinitz.de  Thu Oct 14 13:23:32 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 14:23:32 +0200
Subject: [sane-devel] scanadf: waiting for child processes to finish
In-Reply-To: <20041013152329.GA28252@marge.cehill.co.uk>
References: <20041013152329.GA28252@marge.cehill.co.uk>
Message-ID: <20041014122332.GC12141@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 04:23:29PM +0100, Tristan Hill wrote:
> I use the --scan-script option with scanadf, however, if I want to do
> some work on all the files processed by the script is it difficult
> because scanadf may finish before one or more of the script processes
> do.  For example, I want to use it to combine the processed images into
> a single file.  As scanadf knows what processes it has forked I thought
> it easiest to use wait(), implemented as per attached patch.  However, I
> am open to other suggestions.

So you do something like:
"scanadf --scan-script script && some-other-script image*."?

Ok. The patch looks ok (untested). But I'll apply it after the
sane-frontends release as it's a new feature.

Thanks!

Bye,
  Henning



From henning at meier-geinitz.de  Thu Oct 14 13:29:28 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 14:29:28 +0200
Subject: [sane-devel] XEROX 620S SCSI Scanner.
In-Reply-To: <1097680994.2078.7.camel@superman.biosensorhawaii.com>
References: <1097680994.2078.7.camel@superman.biosensorhawaii.com>
Message-ID: <20041014122928.GD12141@meier-geinitz.de>

Hi,

On Wed, Oct 13, 2004 at 11:23:14AM -0400, Chris Norton wrote:
> Is there any support for a XEROX D620S SCSI Scanner through sane?

It's not mentioned in our lists so: probably no.

> I'm using Mandrake linux and with a Adaptec 2940 card.  sane-scan-finder
> finds the Xerox scanner on /dev/sg0.

Could you show us the output of "sane-find-scanner -v -v"?

> Under windows 98 the Twain and ISIS drivers worked without any
> additional software. The point is that it appeared to be Twain and ISIS
> compliant.

"TWAIN"-compliant doesn't mean anything. It's not a scanner standard
but a software interface standard. You still need a TWAIN driver for
each different scanner.

What is "ISIS"?

> I really would like to use this scanner with linux. It's the only reason
> I still have windows around.

Start writing a backend (=driver). This is not a joke. Drivers for
(older) SCSI scanners are usually easier than for the newer dumb USB
devices.

Bye,
  Henning



From gerhard at gjaeger.de  Thu Oct 14 14:16:38 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Thu, 14 Oct 2004 15:16:38 +0200
Subject: [sane-devel] Interesting image problem when scanning color ...
In-Reply-To: <000901c4b169$e8829190$6601a8c0@khp5000elaptop>
References: <000901c4b169$e8829190$6601a8c0@khp5000elaptop>
Message-ID: <200410141516.38277.gerhard@gjaeger.de>

Hi Kenneth,

On Wednesday 13 October 2004 23:16, Kenneth H. Peters wrote:
[SNIPSNAP]
> I download, compiled and installed the latest 1.0.14 CVS version (this
> version also exhibited the imaging anomalies with plustek.) I wanted to try
> another backend, so I purchased the Epson 2480 (need latest CVS to support
> this) and used the "snapscan" backend.
>
> I was able to scan using this scanner which indicates to me that any
> big-endian issues associated with running on a IXP425 in BE mode is not in
> the frontend (i.e. scanimage) but maybe in the backend.
>
> Attached is a ZIP file that contains output using the "script" command.
>
> The "gentoo_xxx" (Works fine) are files generated on the following:
>
> 	- Gentoo 2.6 kernel
> 	- x86
> 	- libusb
> 	- Canon LiDE 30
> 	- plustek backend
> 	- scanimage frontend
>
> The "ixp425_xxx: (demonstrates "color-bar" problem) are files generated on
> the following:
>
> 	- MV 2.4.18
> 	- IXP425 in big endian mode
> 	- Canon LiDE 30
> 	- plustek backend
> 	- scanimage frontend
>
> These all used the "scanimage -x 10 -y 10"
>
> There is additional output in the function "scan_it" from scanimage.c. This
> diag output is from "if ((output_format == OUTPUT_TIFF) || (parm.depth !=
> 16)) and dumps "buffer".
>
> Please let me know what additional information I can provide.

When scanning with the debug options enabled, there will be a file 
called plustek-pic.raw

Can you send me the files from your gentoo-box and from the IXP?
Please scan something which contains some colors and or stripes to
see the mismatch.
From the logs you've currently sent I can't see any problems. The register
settings seem to be okay, even the calibration steps seem to work on the
two boxes.
The only difference I see is, that on the gentoo box, scanimage seems to
get serveral lines in one transfer, while on the IPX each line is transferred.
The next odd thing is, that on the IXP you'll get some 0 data, but why?
You'll probably send me all the raw files you get from one scan...

Gerhard







From mreuther at umich.edu  Thu Oct 14 17:57:19 2004
From: mreuther at umich.edu (Matt Reuther)
Date: Thu, 14 Oct 2004 12:57:19 -0400
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <20041014115540.GA12141@meier-geinitz.de>
References: <200410132249.08934.mreuther@umich.edu> <20041014115540.GA12141@meier-geinitz.de>
Message-ID: <200410141257.21475.mreuther@umich.edu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 14 October 2004 07:55 am, Henning Meier-Geinitz wrote:
> Hi,
>
> On Wed, Oct 13, 2004 at 10:48:53PM -0400, Matt Reuther wrote:
> > Hi. I picked up an Epson Perfection 4180 scanner.
>
> That scanner is not in our lists. But maybe it's supported under a
> different name?

Vuescan docs also call it a GT-F500, although the Epson drivers call it a 
GT-F600.

[SNIP]

> > The scanner shows up in lsusb, and I set permissions and added the
> > vendor/product ID to /etc/hotplug/usb.usermap, so it works with
> > libusb. It shows up with scanimage -L and if I start xsane, I can pick
> > it from the devices list. However, xsane crashes once I pick the
> > scanner.

BTW, xsane segfaults when it crashes.

> Can you show us the "scanimage -L" output, please?

Here you go:

device `v4l:/dev/video0' is a Noname Kensington VideoCAM 67014 virtual 
device
device `epson:libusb:004:002' is a Epson  flatbed scanner

[SNIP]

> Looks like it crashes when handling option resolution. Please run
> xsane again with SANE_DEBUG_EPSON=255. Does it also happen when
> scanning with scanimage or other frontends?

I attached the output of 'xsane' and 'scanimage -vv'. The GIMP lets me pick 
it, but I see a brief flash of a dialog box, and then nothing. The GIMP 
doesn't crash, it just acts like nothing happened.

I also tried Vuescan, and it doesn't even see the scanner, even though it 
claims to support it. I am asking elsewhere about that.

> Bye,
>   Henning

Matt
- -- 
Matt Reuther
mreuther at umich.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBbq/vFse4xrb7oagRAtviAKCilXS4KT1oWk2Sl0sm2bsV0A9k2QCePygj
0JuslcB+L34rqSszF6c/tak=
=8iIt
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: scanimagelog-epson4180.txt.bz2
Type: application/x-bzip2
Size: 2315 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041014/b88763e8/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sanelog-dll+epson-epson4180.txt.bz2
Type: application/x-bzip2
Size: 2298 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041014/b88763e8/attachment-0001.bin>

From henning at meier-geinitz.de  Thu Oct 14 18:21:15 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 19:21:15 +0200
Subject: [sane-devel] saned array memory limit
Message-ID: <20041014172115.GE12141@meier-geinitz.de>

Hi everyone,

There was a long-standing bug in saned that allowed to alloc huge
amounts of memory on the server by simply sending big string (or
array) sizes. I've now limited the total size of malloced arrays (and
pointers) by sanei_wire to 1 MB in CVS.

This limit applies e.g. to usernames (in SANE_NET_INIT) and options
(e.g. gamma curves).

Please test if your backend still works over the net.

If you get the following error, you may have found a bug or a really
big option value:
[sanei_wire] sanei_w_array: DECODE: maximum amount of allocated memory exceeded (limit: 1048576, new allocation: 4294967295, total: 1048575 bytes)

Do "make clean" before "make" otherwise the changes caused by the
header file won't be picked up.

Bye,
  Henning



From henning at meier-geinitz.de  Thu Oct 14 18:32:05 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 19:32:05 +0200
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <200410141257.21475.mreuther@umich.edu>
References: <200410132249.08934.mreuther@umich.edu> <20041014115540.GA12141@meier-geinitz.de> <200410141257.21475.mreuther@umich.edu>
Message-ID: <20041014173205.GF12141@meier-geinitz.de>

Hi,

On Thu, Oct 14, 2004 at 12:57:19PM -0400, Matt Reuther wrote:
> > Can you show us the "scanimage -L" output, please?
> 
> Here you go:
> 
> device `v4l:/dev/video0' is a Noname Kensington VideoCAM 67014 virtual 
> device
> device `epson:libusb:004:002' is a Epson  flatbed scanner
> 
> [SNIP]

Ok. Just to be safe, comment out "v4l" in dll.conf.

> > Looks like it crashes when handling option resolution. Please run
> > xsane again with SANE_DEBUG_EPSON=255. Does it also happen when
> > scanning with scanimage or other frontends?
> 
> I attached the output of 'xsane' and 'scanimage -vv'. 

The latter one is from v4l not the epson backend. Try again with 
"-d epson" (or comment out v4l in dll.conf).

> The GIMP lets me pick 
> it, but I see a brief flash of a dialog box, and then nothing. The GIMP 
> doesn't crash, it just acts like nothing happened.

If you start gimp from a console window, I guess you would have seen
an error message or even a debug trace.

The log still points to reading the option descriptor but I'm not sure
if it's an xsane or epson backend problem. 

Checking if it happens with scanimage may help.

Try something like
export SANE_DEBUG_EPSON=255
scanimage -d epson -y 50 -x 50 >/tmp/image.pnm 2>log

If it's an xsane problem, setting XSANE_DEBUG=something may also help.
However, that can create "insane" amounts of logs.

Bye,
  Henning



From jb at jblache.org  Thu Oct 14 19:54:53 2004
From: jb at jblache.org (Julien BLACHE)
Date: Thu, 14 Oct 2004 20:54:53 +0200
Subject: [sane-devel] saned array memory limit
In-Reply-To: <20041014172115.GE12141@meier-geinitz.de> (Henning
 Meier-Geinitz's message of "Thu, 14 Oct 2004 19:21:15 +0200")
References: <20041014172115.GE12141@meier-geinitz.de>
Message-ID: <87oej5qgea.fsf@frigate.technologeek.org>

Henning Meier-Geinitz <henning at meier-geinitz.de> wrote:

Hi,

> Do "make clean" before "make" otherwise the changes caused by the
> header file won't be picked up.

Speaking of that, would it be possible to use .depend files to track
dependencies ? That would be very handy, given that the Makfiles
currently do not track dependencies, and sometimes can't do it
(#include <foo.c>).

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb at jblache.org>                                  GPG KeyID 0xF5D65169



From henning at meier-geinitz.de  Thu Oct 14 19:58:42 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 14 Oct 2004 20:58:42 +0200
Subject: [sane-devel] saned array memory limit
In-Reply-To: <87oej5qgea.fsf@frigate.technologeek.org>
References: <20041014172115.GE12141@meier-geinitz.de> <87oej5qgea.fsf@frigate.technologeek.org>
Message-ID: <20041014185842.GG12141@meier-geinitz.de>

Hi,

On Thu, Oct 14, 2004 at 08:54:53PM +0200, Julien BLACHE wrote:
> Speaking of that, would it be possible to use .depend files to track
> dependencies ? That would be very handy, given that the Makfiles
> currently do not track dependencies, and sometimes can't do it
> (#include <foo.c>).

Could you explain how that works or where I can read more about it?

I have already thought about using automake to generate the makefiles
but I guess we would need lots of special rules at least for backend/.

Bye,
  Henning



From svoltz at wanadoo.fr  Thu Oct 14 20:09:46 2004
From: svoltz at wanadoo.fr (svoltz at wanadoo.fr)
Date: Thu, 14 Oct 2004 21:09:46 +0200
Subject: [sane-devel] UMAX 2000 (HP3200c) scanner problems
In-Reply-To: <416DCC27.7010303@tutopia.com>
References: <416DCC27.7010303@tutopia.com>
Message-ID: <20041014190946.GA2675@wanadoo.fr>

On Wed, Oct 13, 2004 at 07:45:27PM -0500, Gian Paolo Mureddu wrote:
> I had my UMAX 2000 branded HP 3200c (Parallel port) scanner working with 
> SANE just fine after I edited the /etc/sane.d/dll.conf file to also look 
> for this scanner, however (I don't know if it was coincidence or not, or 
> if it has to do with the problem or not) after I upgreded my 
> distribution (FC2) especially the GIMP to version 2.0.5 from 2.0.4, I 
> could scan an image just fine, however while working on the scanned 
> image (not yet saved) GIMP crashed (while xsane was still running). I 
> tried to re-open xsane through GIMP, but xsane could not find my scanner 
> anymore. When I tried running xsane or scanimage from the command line I 
> get this output:
> 
> [umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3281)
> [umax_pp_low] Blindly going on .....
> [umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3933)
> [umax_pp_low] Blindly going on .....
> [umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3281)
> [umax_pp_low] Blindly going on .....
> [umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3933)
> [umax_pp_low] Blindly going on .....
> [umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3281)
> [umax_pp_low] Blindly going on .....
> [umax_pp_low] Unexpected reg19: 0xE8 instead of 0xC0 or 0xD0 
> (umax_pp_low.c:3980)
> [umax_pp_low] CmdSetDataBuffer(initbuf) failed ! (umax_pp_low.c:5950)
> scanimage: no SANE devices found
> 
> What does this mean?
> 
> Just for reference, the way I have setup the scanner is as follows: The 
> scanner is attached to my Zip drive (parallel port also) which is 
> connected to the parallel port (lp0)  on the computer, no printer is 
> setup in the parallel port (I use an USB one). The parallel port is set 
> to ECP and at an auto configured port in BIOS. Could this configuration 
> be the conflicting point, even though it *was* working right? What can I 
> do to have it working again?
> 
> Thanks in advance for any input.
> 

	When you get 0xE8 or 0xD8 values, the scanner's ASIC is confused
and needs resetting. It can be done by powering off the scanner, unplugging
the parallel port cable, plugging it back then powering on. 
	The ASIC gets confused each time a command in progress fails, in your
case it's certainly caused by the GIMP crash wich prevented the the backend
to finish cleanly the scan.

Regards,
	Stef




From jb at jblache.org  Thu Oct 14 21:40:21 2004
From: jb at jblache.org (Julien BLACHE)
Date: Thu, 14 Oct 2004 22:40:21 +0200
Subject: [sane-devel] saned array memory limit
In-Reply-To: <20041014185842.GG12141@meier-geinitz.de> (Henning
 Meier-Geinitz's message of "Thu, 14 Oct 2004 20:58:42 +0200")
References: <20041014172115.GE12141@meier-geinitz.de>
	<87oej5qgea.fsf@frigate.technologeek.org>
	<20041014185842.GG12141@meier-geinitz.de>
Message-ID: <87fz4hqbii.fsf@frigate.technologeek.org>

Henning Meier-Geinitz <henning at meier-geinitz.de> wrote:

>> Speaking of that, would it be possible to use .depend files to track
>> dependencies ? That would be very handy, given that the Makfiles
>> currently do not track dependencies, and sometimes can't do it
>> (#include <foo.c>).
>
> Could you explain how that works or where I can read more about it?

It basically boils down to : gcc -E -MM foo.c > .depend, and then
including the resulting file in the Makefile.

This depends on gcc, but there are a couple of standalone dependency
extractors lying around (a quick search on google indicates there's
one in X, called makedepend, but I haven't verified).

> I have already thought about using automake to generate the makefiles
> but I guess we would need lots of special rules at least for backend/.

Yes, it'd take some time to get it up & running...

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb at jblache.org>                                  GPG KeyID 0xF5D65169



From mreuther at umich.edu  Fri Oct 15 00:30:31 2004
From: mreuther at umich.edu (Matt Reuther)
Date: Thu, 14 Oct 2004 19:30:31 -0400
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <20041014173205.GF12141@meier-geinitz.de>
References: <200410132249.08934.mreuther@umich.edu> <200410141257.21475.mreuther@umich.edu> <20041014173205.GF12141@meier-geinitz.de>
Message-ID: <200410141930.32684.mreuther@umich.edu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 14 October 2004 01:32 pm, Henning Meier-Geinitz wrote:

[SNIP]

> Ok. Just to be safe, comment out "v4l" in dll.conf.

Done.

[SNIP]

> If you start gimp from a console window, I guess you would have seen
> an error message or even a debug trace.
>
> The log still points to reading the option descriptor but I'm not sure
> if it's an xsane or epson backend problem.

I ran gimp from the console and captured a log. It's attached. All I did in 
gimp was pick File -> Acquire -> Xsane: epson:libusb:004:002, and then 
quit.

> Checking if it happens with scanimage may help.
>
> Try something like
> export SANE_DEBUG_EPSON=255
> scanimage -d epson -y 50 -x 50 >/tmp/image.pnm 2>log

I did this and attached the output.

> If it's an xsane problem, setting XSANE_DEBUG=something may also help.
> However, that can create "insane" amounts of logs.

Let me know if you want me to try this.

> Bye,
>   Henning

Matt
- -- 
Matt Reuther
mreuther at umich.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBbwwXFse4xrb7oagRAnAYAKD6ONSmY12lFijcOxMYa0EgPX29XwCfReot
RNpjsAqHKVYzK3RfUukRTSY=
=UUEv
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: scanimagelog-epson4180.txt.bz2
Type: application/x-bzip2
Size: 1159 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041014/431b2f75/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gimplog-epson4180.txt.bz2
Type: application/x-bzip2
Size: 1013 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041014/431b2f75/attachment-0001.bin>

From khk at khk.net  Fri Oct 15 01:15:16 2004
From: khk at khk.net (Karl Heinz Kremer)
Date: Thu, 14 Oct 2004 20:15:16 -0400
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <200410141930.32684.mreuther@umich.edu>
References: <200410132249.08934.mreuther@umich.edu> <200410141257.21475.mreuther@umich.edu> <20041014173205.GF12141@meier-geinitz.de> <200410141930.32684.mreuther@umich.edu>
Message-ID: <4A35F8D0-1E3F-11D9-820C-000A957E40E8@khk.net>

It looks like this scanner does not "speak" the ESC/I protocol. At 
least not any flavor that the EPSON backend supports. Maybe Olaf can 
shed some light on this.

Karl Heinz


On Oct 14, 2004, at 7:30 PM, Matt Reuther wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thursday 14 October 2004 01:32 pm, Henning Meier-Geinitz wrote:
>
> [SNIP]
>
>> Ok. Just to be safe, comment out "v4l" in dll.conf.
>
> Done.
>
> [SNIP]
>
>> If you start gimp from a console window, I guess you would have seen
>> an error message or even a debug trace.
>>
>> The log still points to reading the option descriptor but I'm not sure
>> if it's an xsane or epson backend problem.
>
> I ran gimp from the console and captured a log. It's attached. All I 
> did in
> gimp was pick File -> Acquire -> Xsane: epson:libusb:004:002, and then
> quit.
>
>> Checking if it happens with scanimage may help.
>>
>> Try something like
>> export SANE_DEBUG_EPSON=255
>> scanimage -d epson -y 50 -x 50 >/tmp/image.pnm 2>log
>
> I did this and attached the output.
>
>> If it's an xsane problem, setting XSANE_DEBUG=something may also help.
>> However, that can create "insane" amounts of logs.
>
> Let me know if you want me to try this.
>
>> Bye,
>>   Henning
>
> Matt
> - --
> Matt Reuther
> mreuther at umich.edu
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFBbwwXFse4xrb7oagRAnAYAKD6ONSmY12lFijcOxMYa0EgPX29XwCfReot
> RNpjsAqHKVYzK3RfUukRTSY=
> =UUEv
> -----END PGP SIGNATURE-----
> <scanimagelog-epson4180.txt.bz2><gimplog-epson4180.txt.bz2>




From olaf at epkowa.co.jp  Fri Oct 15 02:37:39 2004
From: olaf at epkowa.co.jp (Olaf Meeuwissen)
Date: Fri, 15 Oct 2004 10:37:39 +0900
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <4A35F8D0-1E3F-11D9-820C-000A957E40E8@khk.net> (Karl Heinz
 Kremer's message of "Thu, 14 Oct 2004 20:15:16 -0400")
References: <200410132249.08934.mreuther@umich.edu>
	<200410141257.21475.mreuther@umich.edu>
	<20041014173205.GF12141@meier-geinitz.de>
	<200410141930.32684.mreuther@umich.edu>
	<4A35F8D0-1E3F-11D9-820C-000A957E40E8@khk.net>
Message-ID: <87u0sw3gnw.fsf@zen.epkowa.co.jp>

Karl Heinz Kremer <khk at khk.net> writes:

> It looks like this scanner does not "speak" the ESC/I protocol. At
> least not any flavor that the EPSON backend supports. Maybe Olaf can
> shed some light on this.

I guess I could ;-)

As the EPSON drivers say, this is a GT-F600.  It does not speak ESC/I.
It will be supported by iscan's epkowa backend in the near future (but
first we'll get a release for a bunch of all-in-ones).

FYI, it is closely related to the GT-9400 (Perfection 3170 PHOTO)
which is supported as of iscan-1.6.0.
 
> On Oct 14, 2004, at 7:30 PM, Matt Reuther wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On Thursday 14 October 2004 01:32 pm, Henning Meier-Geinitz wrote:
>>
>> [SNIP]
>>
>>> Ok. Just to be safe, comment out "v4l" in dll.conf.
>>
>> Done.
>>
>> [SNIP]
>>
>>> If you start gimp from a console window, I guess you would have seen
>>> an error message or even a debug trace.
>>>
>>> The log still points to reading the option descriptor but I'm not sure
>>> if it's an xsane or epson backend problem.
>>
>> I ran gimp from the console and captured a log. It's attached. All I
>> did in
>> gimp was pick File -> Acquire -> Xsane: epson:libusb:004:002, and then
>> quit.
>>
>>> Checking if it happens with scanimage may help.
>>>
>>> Try something like
>>> export SANE_DEBUG_EPSON=255
>>> scanimage -d epson -y 50 -x 50 >/tmp/image.pnm 2>log
>>
>> I did this and attached the output.
>>
>>> If it's an xsane problem, setting XSANE_DEBUG=something may also help.
>>> However, that can create "insane" amounts of logs.
>>
>> Let me know if you want me to try this.
>>
>>> Bye,
>>>   Henning
>>
>> Matt
>> - --
>> Matt Reuther
>> mreuther at umich.edu
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.4 (GNU/Linux)
>>
>> iD8DBQFBbwwXFse4xrb7oagRAnAYAKD6ONSmY12lFijcOxMYa0EgPX29XwCfReot
>> RNpjsAqHKVYzK3RfUukRTSY=
>> =UUEv
>> -----END PGP SIGNATURE-----
>> <scanimagelog-epson4180.txt.bz2><gimplog-epson4180.txt.bz2>
>

-- 
Olaf Meeuwissen                            EPSON KOWA Corporation, PF1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2



From olaf at epkowa.co.jp  Fri Oct 15 02:43:18 2004
From: olaf at epkowa.co.jp (Olaf Meeuwissen)
Date: Fri, 15 Oct 2004 10:43:18 +0900
Subject: [sane-devel] saned array memory limit
In-Reply-To: <87fz4hqbii.fsf@frigate.technologeek.org> (Julien BLACHE's
 message of "Thu, 14 Oct 2004 22:40:21 +0200")
References: <20041014172115.GE12141@meier-geinitz.de>
	<87oej5qgea.fsf@frigate.technologeek.org>
	<20041014185842.GG12141@meier-geinitz.de>
	<87fz4hqbii.fsf@frigate.technologeek.org>
Message-ID: <87pt3k3geh.fsf@zen.epkowa.co.jp>

Julien BLACHE <jb at jblache.org> writes:

> Henning Meier-Geinitz <henning at meier-geinitz.de> wrote:

>> I have already thought about using automake to generate the makefiles
>> but I guess we would need lots of special rules at least for backend/.
>
> Yes, it'd take some time to get it up & running...

Hmm, iscan still uses the build infra-structure (Makefile.in etc) from
sane-backends, but in my free time I've switched it over to use
automake (and I'm trying to get it included in our official releases).

Maybe, just maybe, I could see if generalising to multiple backends is
feasible.  Let me know if you're interested.

BTW, I'll also try to update epkowa.desc before sane-backends-1.0.15
comes out.
-- 
Olaf Meeuwissen                            EPSON KOWA Corporation, PF1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2



From thetargos at slackercentral.com  Fri Oct 15 04:09:44 2004
From: thetargos at slackercentral.com (Gian Paolo Mureddu)
Date: Thu, 14 Oct 2004 22:09:44 -0500
Subject: [sane-devel] UMAX 2000 (HP3200c) scanner problems
In-Reply-To: <20041014190946.GA2675@wanadoo.fr>
References: <416DCC27.7010303@tutopia.com> <20041014190946.GA2675@wanadoo.fr>
Message-ID: <416F3F78.90401@slackercentral.com>

svoltz at wanadoo.fr wrote:

>On Wed, Oct 13, 2004 at 07:45:27PM -0500, Gian Paolo Mureddu wrote:
>  
>
>>I had my UMAX 2000 branded HP 3200c (Parallel port) scanner working with 
>>SANE just fine after I edited the /etc/sane.d/dll.conf file to also look 
>>for this scanner, however (I don't know if it was coincidence or not, or 
>>if it has to do with the problem or not) after I upgreded my 
>>distribution (FC2) especially the GIMP to version 2.0.5 from 2.0.4, I 
>>could scan an image just fine, however while working on the scanned 
>>image (not yet saved) GIMP crashed (while xsane was still running). I 
>>tried to re-open xsane through GIMP, but xsane could not find my scanner 
>>anymore. When I tried running xsane or scanimage from the command line I 
>>get this output:
>>
>>[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3281)
>>[umax_pp_low] Blindly going on .....
>>[umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3933)
>>[umax_pp_low] Blindly going on .....
>>[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3281)
>>[umax_pp_low] Blindly going on .....
>>[umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3933)
>>[umax_pp_low] Blindly going on .....
>>[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3281)
>>[umax_pp_low] Blindly going on .....
>>[umax_pp_low] Unexpected reg19: 0xE8 instead of 0xC0 or 0xD0 
>>(umax_pp_low.c:3980)
>>[umax_pp_low] CmdSetDataBuffer(initbuf) failed ! (umax_pp_low.c:5950)
>>scanimage: no SANE devices found
>>
>>What does this mean?
>>
>>Just for reference, the way I have setup the scanner is as follows: The 
>>scanner is attached to my Zip drive (parallel port also) which is 
>>connected to the parallel port (lp0)  on the computer, no printer is 
>>setup in the parallel port (I use an USB one). The parallel port is set 
>>to ECP and at an auto configured port in BIOS. Could this configuration 
>>be the conflicting point, even though it *was* working right? What can I 
>>do to have it working again?
>>
>>Thanks in advance for any input.
>>
>>    
>>
>
>	When you get 0xE8 or 0xD8 values, the scanner's ASIC is confused
>and needs resetting. It can be done by powering off the scanner, unplugging
>the parallel port cable, plugging it back then powering on. 
>	The ASIC gets confused each time a command in progress fails, in your
>case it's certainly caused by the GIMP crash wich prevented the the backend
>to finish cleanly the scan.
>
>Regards,
>	Stef
>
>
>  
>
Thanks, I pretty much discovered this on my own when I went to the UMAX 
backend site... That was exactly what I did: unplug the scanner power 
supply, unplug the parallel cable and then replug everything in reversed 
order (parallel, power) and the scanner worked again. Thanks for the 
additional information, much appreciated!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041014/6ecc4648/attachment.htm>

From livhu.tshisikule at telkomsa.net  Fri Oct 15 11:44:58 2004
From: livhu.tshisikule at telkomsa.net (Livhu Tshisikule)
Date: Fri, 15 Oct 2004 12:44:58 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
Message-ID: <200410151244.58949.livhu.tshisikule@telkomsa.net>

Hi,

I am a newbie to SANE, I have an Olivetti Job_Jet M400 (MFP) connected to a 
machine running Fedora 2. (I am also new to Linux but have Unix experience), 
at the moment I can only print but not scan. (It is powered by HP, I think it 
must be compatible to an HP scanner).

I have been searching the net without any luck. Can somebody help? 

Regards 
Livhu Tshisikule




From cnorton at biosensorhawaii.com  Thu Oct 14 16:12:10 2004
From: cnorton at biosensorhawaii.com (Chris Norton)
Date: Thu, 14 Oct 2004 11:12:10 -0400
Subject: [sane-devel] XEROX 620S SCSI Scanner.
In-Reply-To: <20041014122928.GD12141@meier-geinitz.de>
References: <1097680994.2078.7.camel@superman.biosensorhawaii.com>
	 <20041014122928.GD12141@meier-geinitz.de>
Message-ID: <1097766730.2130.9.camel@superman.biosensorhawaii.com>

Thanks for reply.  The output is below.  With some direction I may be
able to make a back-end driver but right now I'm not sure where to
start.

Thanks for your help,

Chris
[nei at localhost nei]$ sane-find-scanner  -v -v 
 
searching for SCSI scanners: 
checking /dev/scanner... open ok 
  Inquiry for device: 
    000: 06 00 02 02 27 00 00 30 58 45 52 4f 58 20 20 
20    ....'..0XEROX 
    016: 44 6f 63 75 49 6d 61 67 65 36 32 30 53 20 20 20    
DocuImage620S 
    032: 30 30 30 31 01 27 00 56 20 00 00 0e                
0001.'.V ... 
found SCSI scanner "XEROX DocuImage620S 0001" 
at /dev/scanner 
checking /dev/sg0... open ok 
  Inquiry for device: 
    000: 06 00 02 02 27 00 00 30 58 45 52 4f 58 20 20 
20    ....'..0XEROX 
    016: 44 6f 63 75 49 6d 61 67 65 36 32 30 53 20 20 20    
DocuImage620S 
    032: 30 30 30 31 01 27 00 56 20 00 00 0e                
0001.'.V ... 
found SCSI scanner "XEROX DocuImage620S 0001" at /dev/sg0 
checking /dev/sg1... failed to open (Invalid argument) 
checking /dev/sg2... failed to open (Invalid argument) 
checking /dev/sg3... failed to open (Invalid argument) 
checking /dev/sg4... failed to open (Invalid argument) 
checking /dev/sg5... failed to open (Invalid argument) 
checking /dev/sg6... failed to open (Invalid argument) 
checking /dev/sg7... failed to open (Invalid argument) 
checking /dev/sg8... failed to open (Invalid argument) 
checking /dev/sg9... failed to open (Invalid argument) 
checking /dev/sga... failed to open (Invalid argument) 
checking /dev/sgb... failed to open (Invalid argument) 
checking /dev/sgc... failed to open (Invalid argument) 
checking /dev/sgd... failed to open (Invalid argument) 
checking /dev/sge... failed to open (Invalid argument) 
checking /dev/sgf... failed to open (Invalid argument) 
checking /dev/sgg... failed to open (Invalid argument) 
checking /dev/sgh... failed to open (Invalid argument) 
checking /dev/sgi... failed to open (Invalid argument) 
checking /dev/sgj... failed to open (Invalid argument) 
checking /dev/sgk... failed to open (Invalid argument) 
checking /dev/sgl... failed to open (Invalid argument) 
checking /dev/sgm... failed to open (Invalid argument) 
checking /dev/sgn... failed to open (Invalid argument) 
checking /dev/sgo... failed to open (Invalid argument) 
checking /dev/sgp... failed to open (Invalid argument) 
checking /dev/sgq... failed to open (Invalid argument) 
checking /dev/sgr... failed to open (Invalid argument) 
checking /dev/sgs... failed to open (Invalid argument) 
checking /dev/sgt... failed to open (Invalid argument) 
checking /dev/sgu... failed to open (Invalid argument) 
checking /dev/sgv... failed to open (Invalid argument) 
checking /dev/sgw... failed to open (Invalid argument) 
checking /dev/sgx... failed to open (Invalid argument) 
checking /dev/sgy... failed to open (Invalid argument) 
checking /dev/sgz... failed to open (Invalid argument) 
  # Your SCSI scanner was detected. It may or may not be 
supported by SANE. Try 
  # scanimage -L and read the backend's manpage. 
 
searching for USB scanners: 
checking /dev/usb/scanner... failed to open (Invalid 
argument) 
checking /dev/usb/scanner0... failed to open (Invalid 
argument) 
checking /dev/usb/scanner1... failed to open (Invalid 
argument) 
checking /dev/usb/scanner2... failed to open (Invalid 
argument) 
checking /dev/usb/scanner3... failed to open (Invalid 
argument) 
checking /dev/usb/scanner4... failed to open (Invalid 
argument) 
checking /dev/usb/scanner5... failed to open (Invalid 
argument) 
checking /dev/usb/scanner5... failed to open (Invalid 
argument) 
checking /dev/usb/scanner7... failed to open (Invalid 
argument) 
checking /dev/usb/scanner8... failed to open (Invalid 
argument) 
checking /dev/usb/scanner9... failed to open (Invalid 
argument) 
checking /dev/usb/scanner10... failed to open (Invalid 
argument) 
checking /dev/usb/scanner11... failed to open (Invalid 
argument) 
checking /dev/usb/scanner12... failed to open (Invalid 
argument) 
checking /dev/usb/scanner13... failed to open (Invalid 
argument) 
checking /dev/usb/scanner14... failed to open (Invalid 
argument) 
checking /dev/usb/scanner15... failed to open (Invalid 
argument) 
checking /dev/usbscanner... failed to open (Invalid 
argument) 
checking /dev/usbscanner0... failed to open (Invalid 
argument) 
checking /dev/usbscanner1... failed to open (Invalid 
argument) 
checking /dev/usbscanner2... failed to open (Invalid 
argument) 
checking /dev/usbscanner3... failed to open (Invalid 
argument) 
checking /dev/usbscanner4... failed to open (Invalid 
argument) 
checking /dev/usbscanner5... failed to open (Invalid 
argument) 
checking /dev/usbscanner6... failed to open (Invalid 
argument) 
checking /dev/usbscanner7... failed to open (Invalid 
argument) 
checking /dev/usbscanner8... failed to open (Invalid 
argument) 
checking /dev/usbscanner9... failed to open (Invalid 
argument) 
checking /dev/usbscanner10... failed to open (Invalid 
argument) 
checking /dev/usbscanner11... failed to open (Invalid 
argument) 
checking /dev/usbscanner12... failed to open (Invalid 
argument) 
checking /dev/usbscanner13... failed to open (Invalid 
argument) 
checking /dev/usbscanner14... failed to open (Invalid 
argument) 
checking /dev/usbscanner15... failed to open (Invalid 
argument) 
trying libusb: 
 
<device descriptor of 0x0000/0x0000 at 002:001 (Linux 
2.6.3-7mdk uhci_hcd UHCI H 
ost Controller)> 
bLength               18 
bDescriptorType       1 
bcdUSB                1.10 
bDeviceClass          9 
bDeviceSubClass       0 
bDeviceProtocol       0 
bMaxPacketSize0       8 
idVendor              0x0000 
idProduct             0x0000 
bcdDevice             2.06 
iManufacturer         3 (Linux 2.6.3-7mdk uhci_hcd) 
iProduct              2 (UHCI Host Controller) 
iSerialNumber         1 (0000:00:1f.4) 
bNumConfigurations    1 
 <configuration 0> 
 bLength              9 
 bDescriptorType      2 
 wTotalLength         25 
 bNumInterfaces       1 
 bConfigurationValue  1 
 iConfiguration       0 () 
 bmAttributes         64 (Self-powered) 
 MaxPower             0 mA 
  <interface 0> 
   <altsetting 0> 
   bLength            9 
   bDescriptorType    4 
   bInterfaceNumber   0 
   bAlternateSetting  0 
   bNumEndpoints      1 
   bInterfaceClass    9 
   bInterfaceSubClass 0 
   bInterfaceProtocol 0 
   iInterface         0 () 
    <endpoint 0> 
    bLength           7 
    bDescriptorType   5 
    bEndpointAddress  0x81 (in 0x01) 
    bmAttributes      3 (interrupt) 
    wMaxPacketSize    2 
    bInterval         255 ms 
    bRefresh          0 
    bSynchAddress     0 
 
<device descriptor of 0x0000/0x0000 at 001:001 (Linux 
2.6.3-7mdk uhci_hcd UHCI H 
ost Controller)> 
bLength               18 
bDescriptorType       1 
bcdUSB                1.10 
bDeviceClass          9 
bDeviceSubClass       0 
bDeviceProtocol       0 
bMaxPacketSize0       8 
idVendor              0x0000 
idProduct             0x0000 
bcdDevice             2.06 
iManufacturer         3 (Linux 2.6.3-7mdk uhci_hcd) 
iProduct              2 (UHCI Host Controller) 
iSerialNumber         1 (0000:00:1f.2) 
bNumConfigurations    1 
 <configuration 0> 
 bLength              9 
 bDescriptorType      2 
 wTotalLength         25 
 bNumInterfaces       1 
 bConfigurationValue  1 
 iConfiguration       0 () 
 bmAttributes         64 (Self-powered) 
 MaxPower             0 mA 
  <interface 0> 
   <altsetting 0> 
   bLength            9 
   bDescriptorType    4 
   bInterfaceNumber   0 
   bAlternateSetting  0 
   bNumEndpoints      1 
   bInterfaceClass    9 
   bInterfaceSubClass 0 
   bInterfaceProtocol 0 
   iInterface         0 () 
    <endpoint 0> 
    bLength           7 
    bDescriptorType   5 
    bEndpointAddress  0x81 (in 0x01) 
    bmAttributes      3 (interrupt) 
    wMaxPacketSize    2 
    bInterval         255 ms 
    bRefresh          0 
    bSynchAddress     0 
  # No USB scanners found. If you expected something 
different, make sure that 
  # you have loaded a driver for your USB host controller 
and have installed a 
  # kernel scanner module. 
 
  # Scanners connected to the parallel port or other 
proprietary ports can't be 
  # detected by this program. 
 
  # You may want to run this program as root to find all 
devices. Once you 
  # found the scanner devices, be sure to adjust access 
permissions as 
  # necessary. 
done 
[nei at localhost nei]$ 
 



On Thu, 2004-10-14 at 08:29, Henning Meier-Geinitz wrote:
> Hi,
> 
> On Wed, Oct 13, 2004 at 11:23:14AM -0400, Chris Norton wrote:
> > Is there any support for a XEROX D620S SCSI Scanner through sane?
> 
> It's not mentioned in our lists so: probably no.
> 
> > I'm using Mandrake linux and with a Adaptec 2940 card.  sane-scan-finder
> > finds the Xerox scanner on /dev/sg0.
> 
> Could you show us the output of "sane-find-scanner -v -v"?
> 
> > Under windows 98 the Twain and ISIS drivers worked without any
> > additional software. The point is that it appeared to be Twain and ISIS
> > compliant.
> 
> "TWAIN"-compliant doesn't mean anything. It's not a scanner standard
> but a software interface standard. You still need a TWAIN driver for
> each different scanner.
> 
> What is "ISIS"?
> 
> > I really would like to use this scanner with linux. It's the only reason
> > I still have windows around.
> 
> Start writing a backend (=driver). This is not a joke. Drivers for
> (older) SCSI scanners are usually easier than for the newer dumb USB
> devices.
> 
> Bye,
>   Henning




From henning at meier-geinitz.de  Fri Oct 15 12:57:57 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 15 Oct 2004 13:57:57 +0200
Subject: [sane-devel] XEROX 620S SCSI Scanner.
In-Reply-To: <1097766730.2130.9.camel@superman.biosensorhawaii.com>
References: <1097680994.2078.7.camel@superman.biosensorhawaii.com> <20041014122928.GD12141@meier-geinitz.de> <1097766730.2130.9.camel@superman.biosensorhawaii.com>
Message-ID: <20041015115757.GA3623@meier-geinitz.de>

Hi,

On Thu, Oct 14, 2004 at 11:12:10AM -0400, Chris Norton wrote:
> Thanks for reply.  The output is below. 

Thanks. I'll add your scanner to our lists as "unsupported".

> With some direction I may be
> able to make a back-end driver but right now I'm not sure where to
> start.

http://www.sane-project.org/contrib.html

Bye,
  Henning



From henning at meier-geinitz.de  Fri Oct 15 13:08:14 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 15 Oct 2004 14:08:14 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <200410151244.58949.livhu.tshisikule@telkomsa.net>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net>
Message-ID: <20041015120814.GB3623@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 12:44:58PM +0200, Livhu Tshisikule wrote:
> I am a newbie to SANE, I have an Olivetti Job_Jet M400 (MFP) connected to a 
> machine running Fedora 2. (I am also new to Linux but have Unix experience), 
> at the moment I can only print but not scan. (It is powered by HP, I think it 
> must be compatible to an HP scanner).

If it's really compatible to one of the HP multi function devices, it
may work with the hpoj SANE backend.

> I have been searching the net without any luck. Can somebody help? 

Please show us the output of "sane-find-scanner -v -v" when the
scanner is plugged in.

Bye,
  Henning



From livhu.tshisikule at telkomsa.net  Fri Oct 15 13:47:15 2004
From: livhu.tshisikule at telkomsa.net (Livhu Tshisikule)
Date: Fri, 15 Oct 2004 14:47:15 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <20041015120814.GB3623@meier-geinitz.de>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net> <20041015120814.GB3623@meier-geinitz.de>
Message-ID: <200410151447.15977.livhu.tshisikule@telkomsa.net>

Hi,

searching for SCSI scanners:
checking /dev/scanner... failed to open (Invalid argument)
checking /dev/sg0... failed to open (Invalid argument)
checking /dev/sg1... failed to open (Invalid argument)
checking /dev/sg2... failed to open (Invalid argument)
checking /dev/sg3... failed to open (Invalid argument)
checking /dev/sg4... failed to open (Invalid argument)
checking /dev/sg5... failed to open (Invalid argument)
checking /dev/sg6... failed to open (Invalid argument)
checking /dev/sg7... failed to open (Invalid argument)
checking /dev/sg8... failed to open (Invalid argument)
checking /dev/sg9... failed to open (Invalid argument)
checking /dev/sga... failed to open (Invalid argument)
checking /dev/sgb... failed to open (Invalid argument)
checking /dev/sgc... failed to open (Invalid argument)
checking /dev/sgd... failed to open (Invalid argument)
checking /dev/sge... failed to open (Invalid argument)
checking /dev/sgf... failed to open (Invalid argument)
checking /dev/sgg... failed to open (Invalid argument)
checking /dev/sgh... failed to open (Invalid argument)
checking /dev/sgi... failed to open (Invalid argument)
checking /dev/sgj... failed to open (Invalid argument)
checking /dev/sgk... failed to open (Invalid argument)
checking /dev/sgl... failed to open (Invalid argument)
checking /dev/sgm... failed to open (Invalid argument)
checking /dev/sgn... failed to open (Invalid argument)
checking /dev/sgo... failed to open (Invalid argument)
checking /dev/sgp... failed to open (Invalid argument)
checking /dev/sgq... failed to open (Invalid argument)
checking /dev/sgr... failed to open (Invalid argument)
checking /dev/sgs... failed to open (Invalid argument)
checking /dev/sgt... failed to open (Invalid argument)
checking /dev/sgu... failed to open (Invalid argument)
checking /dev/sgv... failed to open (Invalid argument)
checking /dev/sgw... failed to open (Invalid argument)
checking /dev/sgx... failed to open (Invalid argument)
checking /dev/sgy... failed to open (Invalid argument)
checking /dev/sgz... failed to open (Invalid argument)
  # No SCSI scanners found. If you expected something different, make sure 
that
  # you have loaded a SCSI driver for your SCSI adapter.

searching for USB scanners:
checking /dev/usb/scanner... failed to open (Invalid argument)
checking /dev/usb/scanner0... failed to open (Invalid argument)
checking /dev/usb/scanner1... failed to open (Invalid argument)
checking /dev/usb/scanner2... failed to open (Invalid argument)
checking /dev/usb/scanner3... failed to open (Invalid argument)
checking /dev/usb/scanner4... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner7... failed to open (Invalid argument)
checking /dev/usb/scanner8... failed to open (Invalid argument)
checking /dev/usb/scanner9... failed to open (Invalid argument)
checking /dev/usb/scanner10... failed to open (Invalid argument)
checking /dev/usb/scanner11... failed to open (Invalid argument)
checking /dev/usb/scanner12... failed to open (Invalid argument)
checking /dev/usb/scanner13... failed to open (Invalid argument)
checking /dev/usb/scanner14... failed to open (Invalid argument)
checking /dev/usb/scanner15... failed to open (Invalid argument)
checking /dev/usbscanner... failed to open (Invalid argument)
checking /dev/usbscanner0... failed to open (Invalid argument)
checking /dev/usbscanner1... failed to open (Invalid argument)
checking /dev/usbscanner2... failed to open (Invalid argument)
checking /dev/usbscanner3... failed to open (Invalid argument)
checking /dev/usbscanner4... failed to open (Invalid argument)
checking /dev/usbscanner5... failed to open (Invalid argument)
checking /dev/usbscanner6... failed to open (Invalid argument)
checking /dev/usbscanner7... failed to open (Invalid argument)
checking /dev/usbscanner8... failed to open (Invalid argument)
checking /dev/usbscanner9... failed to open (Invalid argument)
checking /dev/usbscanner10... failed to open (Invalid argument)
checking /dev/usbscanner11... failed to open (Invalid argument)
checking /dev/usbscanner12... failed to open (Invalid argument)
checking /dev/usbscanner13... failed to open (Invalid argument)
checking /dev/usbscanner14... failed to open (Invalid argument)
checking /dev/usbscanner15... failed to open (Invalid argument)
found USB scanner (vendor=0x0b3c [Olivetti], product=0xa880 [Job_Jet M400]) at 
l
ibusb:003:002
  # Your USB scanner was (probably) detected. It may or may not be supported 
by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Scanners connected to the parallel port or other proprietary ports can't 
be
  # detected by this program.
done

Regards
Livhu Tshisikule




From Oliver.Rauch at Rauch-Domain.DE  Fri Oct 15 15:44:42 2004
From: Oliver.Rauch at Rauch-Domain.DE (Oliver Rauch)
Date: 15 Oct 2004 16:44:42 +0200
Subject: [sane-devel] Timetable for the release of sane-backends-1.0.15
In-Reply-To: <20041005113202.GG7772@meier-geinitz.de>
References: <20041005113202.GG7772@meier-geinitz.de>
Message-ID: <1097851482.2134.8.camel@Babylon7>

Hello.

I am not able to get access to the CVS server (permission denied).
Please could someone who has acces to the server take a look at that?!

I suggest to delay the feature freeze for some days when this
is not solved soon.

Best regards
Oliver

Am Die, 2004-10-05 um 13.32 schrieb Henning Meier-Geinitz:
> Hi,
> 
> This is the timetable for the release of sane-backends 1.0.15
> 
> 2004-10-17 Feature freeze (snapshot)
> 2004-10-31 Code freeze (snapshot)
> 2004-11-07 Release
> 
> Feature freeze means that only bug fixes and documentation updates are
> allowed. After code freeze only fixes of grave bugs that render a
> backend completely unusable or break compilation and documentation
> updates are accepted.
> 
> If there are any new backends that should be included in that release
> please tell us NOW.
> 
> Please everyone have a look at out growing list of bugs and fix as
> many bugs as possible:
> http://alioth.debian.org/tracker/index.php?group_id=30186&atid=410366
> 
> Or, if the bug report is bogus, close it.
> You can view only bugs assigned to you to reduce the number of visible
> bugs. Having a look at bugs assigned to nobody is also worth a try as
> some bugs affect several backends/maintainers. You can also sort by
> topic ("Summary").
> 
> Bye,
>   Henning




From henning at meier-geinitz.de  Fri Oct 15 13:37:03 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 15 Oct 2004 14:37:03 +0200
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <87u0sw3gnw.fsf@zen.epkowa.co.jp>
References: <200410132249.08934.mreuther@umich.edu> <200410141257.21475.mreuther@umich.edu> <20041014173205.GF12141@meier-geinitz.de> <200410141930.32684.mreuther@umich.edu> <4A35F8D0-1E3F-11D9-820C-000A957E40E8@khk.net> <87u0sw3gnw.fsf@zen.epkowa.co.jp>
Message-ID: <20041015123703.GF3623@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 10:37:39AM +0900, Olaf Meeuwissen wrote:
> Karl Heinz Kremer <khk at khk.net> writes:
> 
> > It looks like this scanner does not "speak" the ESC/I protocol. At
> > least not any flavor that the EPSON backend supports. Maybe Olaf can
> > shed some light on this.
> 
> I guess I could ;-)
> 
> As the EPSON drivers say, this is a GT-F600.  It does not speak ESC/I.
> It will be supported by iscan's epkowa backend in the near future (but
> first we'll get a release for a bunch of all-in-ones).

I've added Perfection 4160 and GT-F600 as unsupported to our lists for
now (with some details from your mail).

Bye,
  Henning



From henning at meier-geinitz.de  Fri Oct 15 13:56:40 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 15 Oct 2004 14:56:40 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <200410151447.15977.livhu.tshisikule@telkomsa.net>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net> <20041015120814.GB3623@meier-geinitz.de> <200410151447.15977.livhu.tshisikule@telkomsa.net>
Message-ID: <20041015125640.GH3623@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 02:47:15PM +0200, Livhu Tshisikule wrote:
> found USB scanner (vendor=0x0b3c [Olivetti], product=0xa880 [Job_Jet M400]) at libusb:003:002

Thanks. 0x03bc is really Olivetti so they haven't just used a HP
device and printed a new logo on the case.

So I guess it won't work with hpoj without source code changes (if at
all).

Could you rerun sane-find-scanner and use "-v -v" (very verbose) this
time?

Bye,
  Henning




From johannes at sipsolutions.net  Fri Oct 15 14:47:40 2004
From: johannes at sipsolutions.net (Johannes Berg)
Date: Fri, 15 Oct 2004 15:47:40 +0200
Subject: [sane-devel] [BUG] saned: missing input sanitization
Message-ID: <1097848060.4219.2.camel@johannes>

SANE_NET_OPEN makes saned segfault if a NULL name is passed, because it
tries to strdup() the name without checking for != NULL.

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041015/705f8ac1/attachment.sig>

From johannes at sipsolutions.net  Fri Oct 15 14:47:06 2004
From: johannes at sipsolutions.net (Johannes Berg)
Date: Fri, 15 Oct 2004 15:47:06 +0200
Subject: [sane-devel] possible bin_w_string security issue (not)
Message-ID: <1097848026.4219.0.camel@johannes>

I was going to write a mail without the "(not)" but then discovered that
this issue is actually a non-issue, but this is totally non-obvious.

Would you know off-hand why?

bin_w_string contains the following code:

  if (w->direction == WIRE_DECODE)
    {
      if (len == 0)
        *s = 0;
      else if (w->status == 0)
        *(*s + len - 1) = '\0';
    }

If I interpret the code correctly, this could be used to bring the
server (running the binary protocol) into an invalid state:

1) send any kind of request that requires a string option at the end,
   for example SANE_NET_AUTHORIZE
2) tell the server that the length is 10 or so
3) send 9 bytes and close the connection

The server will react to this in the following way (if I interpret the
code correctly):
* during sanei_w_array it will notice that the status is
   bad and return
* bin_w_string will not(!) zero-terminate the string
   (because it is assuming that *s is not valid, while
   it actually is)
   sanei_w_array doesn't clear the array if anything
   item fails to read.
* now, the server has a password string that is not zero terminated,
   and strcpy()s that string accessing memory beyond the allocated size.


[Actually, I discovered this while I was documenting the wire protocol.
I think it is overly complex and the code badly structured, the wire's
direction thing is really strange!]





Ok, so here's the solution:

The server does
  signal (SIGPIPE, quit);

(which I think is actually another bug, why should sane_close,
sane_exit, sanei_w_exit and lots of other functions be async signal
safe?)

Still, this is that non-obvious that someone writing a server (or
client, which could then be attacked by a malevolent server) with the
sanei library functions could easily oversee this detail, ignore SIGPIPE
or use sockets that don't raise it.

Therefore I'm still sending this mail in hope that someone fixes the
sanei_w_array function to check for status != 0 and clean up after
itself.

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041015/5fc7b126/attachment.sig>

From johannes at sipsolutions.net  Fri Oct 15 15:03:04 2004
From: johannes at sipsolutions.net (Johannes Berg)
Date: Fri, 15 Oct 2004 16:03:04 +0200
Subject: [sane-devel] saned/sanei net bug
Message-ID: <1097848984.4219.3.camel@johannes>

somehow saned/the sanei network layer seem to get buffering wrong.

For example, I send the following:

SANE_NET_INIT
SANE_NET_GET_DEVICES
SANE_NET_EXIT

If I don't wait for the result from SANE_NET_GET_DEVICES before sending
the control code for SANE_NET_EXIT, then the SANE_NET_EXIT code is
discarded.
I would assume that somewhere there's a buffering problem and the old
buffer is simply dropped when the direction is changed or something.

The following works:
(echo  -n -e \\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00 ;
sleep .1 ; echo -n -e \\00\\00\\x00\\x01 ; sleep 1 ;
echo -en \\x00\\x00\\x00\\x0A ) | nc localhost 6566 -q 1 | hd

while this doesn't:
(echo  -n -e \\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00 ;
sleep .1 ; echo -n -e \\00\\00\\x00\\x01\\x00\\x00\\x00\\x0A
)| nc localhost 6566 -q 1 | hd

I think this is extremely counter-intuitive. TCP never guarantees
message boundaries, so one wouldn't think that data is explicitly read
by the application but then discarded.

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041015/c737ab28/attachment.sig>

From johannes at sipsolutions.net  Fri Oct 15 15:03:24 2004
From: johannes at sipsolutions.net (Johannes Berg)
Date: Fri, 15 Oct 2004 16:03:24 +0200
Subject: [sane-devel] weird message configuring sane-frontends
Message-ID: <1097849004.4219.4.camel@johannes>

[configure fails because it can't find sane-config]
"You may need to remove /dev/null before you run configure again."

Clearly, that is not something you want to do.

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041015/b728ea9f/attachment.sig>

From livhu.tshisikule at telkomsa.net  Sat Oct 16 07:04:34 2004
From: livhu.tshisikule at telkomsa.net (Livhu Tshisikule)
Date: Sat, 16 Oct 2004 08:04:34 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <20041015125640.GH3623@meier-geinitz.de>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net> <200410151447.15977.livhu.tshisikule@telkomsa.net> <20041015125640.GH3623@meier-geinitz.de>
Message-ID: <200410160804.34631.livhu.tshisikule@telkomsa.net>

Henning,

Thanks a lot, here are the results of sane-find-scanner -v -v

<device descriptor of 0x0b3c/0xa880 at 003:003 (Olivetti Job_Jet M400)>
bLength               18
bDescriptorType       1
bcdUSB                2.00
bDeviceClass          0
bDeviceSubClass       0
bDeviceProtocol       0
bMaxPacketSize0       8
idVendor              0x0B3C
idProduct             0xA880
bcdDevice             1.00
iManufacturer         1 (Olivetti)
iProduct              2 (Job_Jet M400)
iSerialNumber         3 (MY43FT62DF82)
bNumConfigurations    1
 <configuration 0>
 bLength              9
 bDescriptorType      2
 wTotalLength         99
 bNumInterfaces       3
 bConfigurationValue  1
 iConfiguration       0 ()
 bmAttributes         192 (Self-powered)
 MaxPower             2 mA
  <interface 0>
   <altsetting 0>
   bLength            9
   bDescriptorType    4
   bInterfaceNumber   0
   bAlternateSetting  0
   bNumEndpoints      3
   bInterfaceClass    255
   bInterfaceSubClass 204
   bInterfaceProtocol 0
   iInterface         0 ()
    <endpoint 0>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x01 (out 0x01)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 1>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x81 (in 0x01)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 2>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x82 (in 0x02)
    bmAttributes      3 (interrupt)
    wMaxPacketSize    8
    bInterval         10 ms
    bRefresh          0
    bSynchAddress     0
  <interface 1>
   <altsetting 0>
   bLength            9
   bDescriptorType    4
   bInterfaceNumber   1
   bAlternateSetting  0
   bNumEndpoints      3
   bInterfaceClass    7
   bInterfaceSubClass 1
   bInterfaceProtocol 2
   iInterface         0 ()
    <endpoint 0>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x03 (out 0x03)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 1>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x83 (in 0x03)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 2>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x84 (in 0x04)
    bmAttributes      3 (interrupt)
    wMaxPacketSize    8
    bInterval         10 ms
    bRefresh          0
    bSynchAddress     0
  <interface 2>
   <altsetting 0>
   bLength            9
   bDescriptorType    4
   bInterfaceNumber   2
   bAlternateSetting  0
   bNumEndpoints      3
   bInterfaceClass    255
   bInterfaceSubClass 255
   bInterfaceProtocol 255
   iInterface         0 ()
    <endpoint 0>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x05 (out 0x05)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 1>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x85 (in 0x05)
    bmAttributes      2 (bulk)
    wMaxPacketSize    64
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 2>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x86 (in 0x06)
    bmAttributes      3 (interrupt)
    bRefresh          0
<trying to find out which USB chip is used>
    checking for GT-6801 ...
    this is not a GT-6801 (bDeviceClass = 0)
    checking for GT-6816 ...
    this is not a GT-6816 (bcdUSB = 0x200)
    checking for MA-1017 ...
    this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 255)
    checking for MA-1015 ...
    this is not a MA-1015 (bDeviceClass = 0)
    checking for MA-1509 ...
    this is not a MA-1509 (bDeviceClass = 0)
    checking for LM983[1,2,3] ...
    this is not a LM983x (bcdUSB = 0x200)
    checking for GL646 ...
    this is not a GL646 (bDeviceClass = 0, bInterfaceClass = 255)
    checking for GL660+GL646 ...
    this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 255)
<Couldn't determine the type of the USB chip>

found USB scanner (vendor=0x0b3c [Olivetti], product=0xa880 [Job_Jet M400]) at 
libusb:003:003

Regards
Livhu




From Oliver.Rauch at Rauch-Domain.DE  Sat Oct 16 09:48:37 2004
From: Oliver.Rauch at Rauch-Domain.DE (Oliver Rauch)
Date: 16 Oct 2004 10:48:37 +0200
Subject: [sane-devel] Timetable for the release of sane-backends-1.0.15
In-Reply-To: <1097851482.2134.8.camel@Babylon7>
References: <20041005113202.GG7772@meier-geinitz.de>
	 <1097851482.2134.8.camel@Babylon7>
Message-ID: <1097916516.2128.1.camel@Babylon7>

Am Fre, 2004-10-15 um 16.44 schrieb Oliver Rauch:
> Hello.
> 
> I am not able to get access to the CVS server (permission denied).
> Please could someone who has acces to the server take a look at that?!
> 
> I suggest to delay the feature freeze for some days when this
> is not solved soon.

Today everything works right again, no need for a delay.

Oliver




From jb at jblache.org  Sat Oct 16 10:23:44 2004
From: jb at jblache.org (Julien BLACHE)
Date: Sat, 16 Oct 2004 11:23:44 +0200
Subject: [sane-devel] Timetable for the release of sane-backends-1.0.15
In-Reply-To: <1097851482.2134.8.camel@Babylon7> (Oliver Rauch's message of
 "15 Oct 2004 16:44:42 +0200")
References: <20041005113202.GG7772@meier-geinitz.de>
	<1097851482.2134.8.camel@Babylon7>
Message-ID: <87k6trt3rz.fsf@frigate.technologeek.org>

Oliver Rauch <Oliver.Rauch at Rauch-Domain.DE> wrote:

> I am not able to get access to the CVS server (permission denied).
> Please could someone who has acces to the server take a look at that?!

It should be working again, LDAP crashed again.

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb at jblache.org>                                  GPG KeyID 0xF5D65169



From jb at jblache.org  Sat Oct 16 12:03:45 2004
From: jb at jblache.org (Julien BLACHE)
Date: Sat, 16 Oct 2004 13:03:45 +0200
Subject: [sane-devel] Snapscan: Epson 2480 hangs on amd64
Message-ID: <87fz4eudpq.fsf@frigate.technologeek.org>

Hi,

My Epson 2480 hangs when doing a preview on an amd64 box, however it
works fine on both an i386 and a PowerPC boxes.

Here's the end of the log :

[snapscan] sane_snapscan_start: after measuring speed:
        3816 bytes per scan line
        0.000000 milliseconds per scan line.
        ==>inf bytes per millisecond
[snapscan] calibrate: reading calibration data (1 lines)
[snapscan] read_calibration_data
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0x647088,10,0x75fdb0,0xbfffe438 (61200))
[snapscan] atomic_usb_cmd(0,0x647088,10,0x75fdb0,0xbfffe438 (61200))
[snapscan] usb_cmd(0,0x647088,10,0x75fdb0,0xbfffe438 (61200))
[snapscan] usb_cmd: cmdlen=10, datalen=0
[snapscan] usb_write: writing:  0x28 0x00 0x82 0x00 0x00 0x01 0x00 0xef 0x10 0x00
[snapscan] Written 10 bytes
[snapscan] usb_read: reading:  0xf9 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Read 8 bytes
[snapscan] usb_read Only 0 bytes read
[snapscan] usb_read: reading:  0x5e 0x5d 0x63 0x60 0x60 0x5d 0x62 0x5e 0x60 0x64 ...
[snapscan] Read 0 bytes
[snapscan] read_calibration_data: snapscan_cmd command failed: Error during device I/O
[snapscan] calibrate: read_calibration_data command failed: Error during device I/O
[snapscan] sane_snapscan_start: calibration failed.
[snapscan] release_unit
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0xbfffe480,6,0x0,0x0 (0))
[snapscan] atomic_usb_cmd(0,0xbfffe480,6,0x0,0x0 (0))
[snapscan] usb_cmd(0,0xbfffe480,6,0x0,0x0 (0))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x17 0x00 0x00 0x00 0x00 0x00
[snapscan] usb_write Only 0 bytes written
[snapscan] Written 0 bytes
[snapscan] release_unit: scsi command error: Error during device I/O
[snapscan] sane_snapscan_cancel
[snapscan] release_unit
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0xbfffe3b0,6,0x0,0x0 (0))
[snapscan] atomic_usb_cmd(0,0xbfffe3b0,6,0x0,0x0 (0))
[snapscan] usb_cmd(0,0xbfffe3b0,6,0x0,0x0 (0))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x17 0x00 0x00 0x00 0x00 0x00
[snapscan] usb_write Only 0 bytes written
[snapscan] Written 0 bytes
[snapscan] release_unit: scsi command error: Error during device I/O
[snapscan] close_scanner
[snapscan] snapscani_usb_close(0)
[snapscan] 1st read 977 write 411
[snapscan] usb_cmd(0,0xbfffe3b0,6,0x0,0x0 (0))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] usb_write Only 0 bytes written
[snapscan] Written 0 bytes
[snapscan] 2nd read 977 write 411

dmesg indicates the usb operations time out (ret -110).

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb at jblache.org>                                  GPG KeyID 0xF5D65169



From henning at meier-geinitz.de  Sat Oct 16 12:17:50 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 13:17:50 +0200
Subject: [sane-devel] Timetable for the release of sane-backends-1.0.15
In-Reply-To: <1097851482.2134.8.camel@Babylon7>
References: <20041005113202.GG7772@meier-geinitz.de> <1097851482.2134.8.camel@Babylon7>
Message-ID: <20041016111750.GA10704@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 04:44:42PM +0200, Oliver Rauch wrote:
> I am not able to get access to the CVS server (permission denied).
> Please could someone who has acces to the server take a look at that?!

The reason was a 100% full / file system which stopped login and other
services like mail. As far as I can see it's fixed now.

As the mailinglists are hosted on the same server as CVS
(alioth.debian.org), they usually don't work when CVS is broken by
such failures. The IRC channel #sane is not affected as it's
independent from alioth. So better ask there when CVS or anything else
is broken.

Bye,
  Henning



From henning at meier-geinitz.de  Sat Oct 16 12:50:28 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 13:50:28 +0200
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <200410160804.34631.livhu.tshisikule@telkomsa.net>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net> <200410151447.15977.livhu.tshisikule@telkomsa.net> <20041015125640.GH3623@meier-geinitz.de> <200410160804.34631.livhu.tshisikule@telkomsa.net>
Message-ID: <20041016115028.GD10704@meier-geinitz.de>

Hi,

On Sat, Oct 16, 2004 at 08:04:34AM +0200, Livhu Tshisikule wrote:
> Henning,
> 
> Thanks a lot, here are the results of sane-find-scanner -v -v

Thanks. I'll add that scanner as unsupported to our lists.

Bye,
  Henning



From henning at meier-geinitz.de  Sat Oct 16 13:20:33 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 14:20:33 +0200
Subject: [sane-devel] possible bin_w_string security issue (not)
In-Reply-To: <1097848026.4219.0.camel@johannes>
References: <1097848026.4219.0.camel@johannes>
Message-ID: <20041016122033.GE10704@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 03:47:06PM +0200, Johannes Berg wrote:
> I was going to write a mail without the "(not)" but then discovered that
> this issue is actually a non-issue, but this is totally non-obvious.
> 
> Would you know off-hand why?

SIGPIPE (ok, I read your mail before answering) :-)

> bin_w_string contains the following code:
> 
>   if (w->direction == WIRE_DECODE)
>     {
>       if (len == 0)
>         *s = 0;
>       else if (w->status == 0)
>         *(*s + len - 1) = '\0';
>     }
> 
> If I interpret the code correctly, this could be used to bring the
> server (running the binary protocol) into an invalid state:

Nearly any protocol violation from server or client can have strange
results. That's one of the problems with the SANE net protocol.

Also there are still many tests missing for a bad wire status (see bug
#300105).

> * now, the server has a password string that is not zero terminated,
>    and strcpy()s that string accessing memory beyond the allocated size.

There may be other locations but at least here it tests for the wire
status:

(saned.c l. 356)

  sanei_w_authorization_req (&wire, &req);
  if (wire.status)
    {
      DBG(DBG_ERR, "auth_callback: bad status %d\n", wire.status);
      return;
    }

  if (req.username)
    strcpy (username, req.username);  
[...]

All the wire code expects the caller to test the wire status before he
does anything else. I think there should be tests in all functions of
sanei_net.c also to avoid calling sanei_wire again when the wire is
already bad.

> [Actually, I discovered this while I was documenting the wire protocol.
> I think it is overly complex and the code badly structured, the wire's
> direction thing is really strange!]

I'm still not sure if I have understood all the details of the wire
code. But I guess the idea was to have only one function for each kind
of data. So you don't need one for the server and one for the client
and one for ascii and one for bin and one for sending and one for
receiving...

> Ok, so here's the solution:
> 
> The server does
>   signal (SIGPIPE, quit);
> 
> (which I think is actually another bug, why should sane_close,
> sane_exit, sanei_w_exit and lots of other functions be async signal
> safe?)

They aren't. Only sane_cancel() must be async signal safe.

Yes, I guess that's a bug.

> Still, this is that non-obvious that someone writing a server (or
> client, which could then be attacked by a malevolent server) with the
> sanei library functions could easily oversee this detail, ignore SIGPIPE
> or use sockets that don't raise it.

Nobody should ever use sanei_wire/sanei_net/sanei_codec_* without
really knowing what he does :-)

> Therefore I'm still sending this mail in hope that someone fixes the
> sanei_w_array function to check for status != 0 and clean up after
> itself.

But what should sanei_w_array do? It already exits when the wire is in
bad state. I think that's really up to the caller.

Bye,
  Henning



From Oliver.Schwartz at gmx.de  Sat Oct 16 13:23:34 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Sat, 16 Oct 2004 14:23:34 +0200
Subject: [sane-devel] Snapscan: Epson 2480 hangs on amd64
In-Reply-To: <87fz4eudpq.fsf@frigate.technologeek.org>
References: <87fz4eudpq.fsf@frigate.technologeek.org>
Message-ID: <200410161423.37058.Oliver.Schwartz@gmx.de>

Hi,

> [snapscan] read_calibration_data: snapscan_cmd command failed:
> Error during device I/O [snapscan] calibrate: read_calibration_data
> command failed: Error during device I/O [snapscan]
> sane_snapscan_start: calibration failed.

the error occurs during quality calibration. It's a known issue that 
quality calibration as implemented in the snapscan backend doesn't 
work for epson scanners. For that reason the option is disabled for 
epson models (see snapscan-options.c, line 522ff). In this case the 
calibrate function should never be called (see snapscan.c, line 
1600).

Either you're using a wrong version of the backend or there's some 
issue with option handling on amd64.

/Oliver



From johannes at sipsolutions.net  Sat Oct 16 13:34:41 2004
From: johannes at sipsolutions.net (Johannes Berg)
Date: Sat, 16 Oct 2004 14:34:41 +0200
Subject: [sane-devel] possible bin_w_string security issue (not)
In-Reply-To: <20041016122033.GE10704@meier-geinitz.de>
References: <1097848026.4219.0.camel@johannes>
	<20041016122033.GE10704@meier-geinitz.de>
Message-ID: <1097930081.4439.13.camel@johannes>

Hi,

> SIGPIPE (ok, I read your mail before answering) :-)

:-)

> Nearly any protocol violation from server or client can have strange
> results. That's one of the problems with the SANE net protocol.
> 
> Also there are still many tests missing for a bad wire status (see bug
> #300105).

Will do.

> There may be other locations but at least here it tests for the wire
> status:

Hm. I guess you're right. Seems I missed it, or maybe I was writing this
when I looked at a different location? Sorry.

> I'm still not sure if I have understood all the details of the wire
> code. But I guess the idea was to have only one function for each kind
> of data. So you don't need one for the server and one for the client
> and one for ascii and one for bin and one for sending and one for
> receiving...

Yeah, and then it is also "overloaded" for freeing allocated data.

> They aren't. Only sane_cancel() must be async signal safe.
> 
> Yes, I guess that's a bug.

Ok.

> Nobody should ever use sanei_wire/sanei_net/sanei_codec_* without
> really knowing what he does :-)

:-)

> But what should sanei_w_array do? It already exits when the wire is in
> bad state. I think that's really up to the caller.

Yes, but before exiting it should free the result buffer and NULL the
pointer. When the wire is in an invalid state during reading, it cannot
be guaranteed that the buffer is in a valid state, so should be
discarded.

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041016/7215fca0/attachment.sig>

From jb at jblache.org  Sat Oct 16 14:15:31 2004
From: jb at jblache.org (Julien BLACHE)
Date: Sat, 16 Oct 2004 15:15:31 +0200
Subject: [sane-devel] Snapscan: Epson 2480 hangs on amd64
In-Reply-To: <200410161423.37058.Oliver.Schwartz@gmx.de> (Oliver Schwartz's
 message of "Sat, 16 Oct 2004 14:23:34 +0200")
References: <87fz4eudpq.fsf@frigate.technologeek.org>
	<200410161423.37058.Oliver.Schwartz@gmx.de>
Message-ID: <87zn2mst1o.fsf@frigate.technologeek.org>

Oliver Schwartz <Oliver.Schwartz at gmx.de> wrote:

Hi Oliver,

>> [snapscan] read_calibration_data: snapscan_cmd command failed:
>> Error during device I/O [snapscan] calibrate: read_calibration_data
>> command failed: Error during device I/O [snapscan]
>> sane_snapscan_start: calibration failed.
>
> the error occurs during quality calibration. It's a known issue that 
> quality calibration as implemented in the snapscan backend doesn't 
> work for epson scanners. For that reason the option is disabled for 
> epson models (see snapscan-options.c, line 522ff). In this case the 
> calibrate function should never be called (see snapscan.c, line 
> 1600).

This is fresh checkout, and the code seems OK. There is something
fishy going on... now it doesn't even find the scanner anymore. I'll
dig into it.

> Either you're using a wrong version of the backend or there's some 
> issue with option handling on amd64.

Looks like it :/

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb at jblache.org>                                  GPG KeyID 0xF5D65169



From henning at meier-geinitz.de  Sat Oct 16 14:17:05 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 15:17:05 +0200
Subject: [sane-devel] weird message configuring sane-frontends
In-Reply-To: <1097849004.4219.4.camel@johannes>
References: <1097849004.4219.4.camel@johannes>
Message-ID: <20041016131705.GF10704@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 04:03:24PM +0200, Johannes Berg wrote:
> [configure fails because it can't find sane-config]
> "You may need to remove /dev/null before you run configure again."
> 
> Clearly, that is not something you want to do.

That's the penalty for users who don't read the docs and install
sane-frontends before sane-backends :-)

Fixed in CVS now.

The idea was to print the name of the cache filr of autoconf (usually
./config.cache). Recent autoconf versions don't use it and set the
variable to /dev/null.

Bye,
  Henning



From henning at meier-geinitz.de  Sat Oct 16 14:32:11 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 15:32:11 +0200
Subject: [sane-devel] saned/sanei net bug
In-Reply-To: <1097848984.4219.3.camel@johannes>
References: <1097848984.4219.3.camel@johannes>
Message-ID: <20041016133211.GG10704@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 04:03:04PM +0200, Johannes Berg wrote:
> somehow saned/the sanei network layer seem to get buffering wrong.

I'm afraid that that's intentional. But that's only a guess.

> For example, I send the following:
> 
> SANE_NET_INIT
> SANE_NET_GET_DEVICES
> SANE_NET_EXIT
> 
> If I don't wait for the result from SANE_NET_GET_DEVICES before sending
> the control code for SANE_NET_EXIT, then the SANE_NET_EXIT code is
> discarded.

I think you must really read the result of any RPC before sending the
next one.

> I would assume that somewhere there's a buffering problem and the old
> buffer is simply dropped when the direction is changed or something.

That's done in sanei_w_set_direction().
Set SANE_DEBUG_SANEI_WIRE=255 and you'll even get a warning :-)

> The following works:
> (echo  -n -e \\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00 ;
> sleep .1 ; echo -n -e \\00\\00\\x00\\x01 ; sleep 1 ;
> echo -en \\x00\\x00\\x00\\x0A ) | nc localhost 6566 -q 1 | hd
> 
> while this doesn't:
> (echo  -n -e \\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00\\00 ;
> sleep .1 ; echo -n -e \\00\\00\\x00\\x01\\x00\\x00\\x00\\x0A
> )| nc localhost 6566 -q 1 | hd
> 
> I think this is extremely counter-intuitive. TCP never guarantees
> message boundaries, so one wouldn't think that data is explicitly read
> by the application but then discarded.
 
I guess you are right but I don't really know how to fix that with the
current code. One option would be to set the wire to error state (and
exit?) when data is discarded.

Bye,
  Henning



From henning at meier-geinitz.de  Sat Oct 16 14:48:19 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 15:48:19 +0200
Subject: [sane-devel] [BUG] saned: missing input sanitization
In-Reply-To: <1097848060.4219.2.camel@johannes>
References: <1097848060.4219.2.camel@johannes>
Message-ID: <20041016134819.GH10704@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 03:47:40PM +0200, Johannes Berg wrote:
> SANE_NET_OPEN makes saned segfault if a NULL name is passed, because it
> tries to strdup() the name without checking for != NULL.

I've added a check to CVS. It returns an error to the client because I
think that's a protocol violation. Zero-length strings are allowed for
sane_open but not NULL-pointers.

Could you check if that works and doesn't create any new bugs?

Bye,
  Henning



From johannes at sipsolutions.net  Sat Oct 16 15:01:20 2004
From: johannes at sipsolutions.net (Johannes Berg)
Date: Sat, 16 Oct 2004 16:01:20 +0200
Subject: [sane-devel] [BUG] saned: missing input sanitization
In-Reply-To: <20041016134819.GH10704@meier-geinitz.de>
References: <1097848060.4219.2.camel@johannes>
	<20041016134819.GH10704@meier-geinitz.de>
Message-ID: <1097935280.4439.17.camel@johannes>

On Sat, 2004-10-16 at 15:48 +0200, Henning Meier-Geinitz wrote:
> I've added a check to CVS. It returns an error to the client because I
> think that's a protocol violation. Zero-length strings are allowed for
> sane_open but not NULL-pointers.

I think the problem is that the network layer does not distinguish
between zero-length strings and NULL pointers -- as far as I can see it
interprets a zero-length string (which is only a byte-array after all)
as a NULL string.

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041016/3c4a1fbc/attachment.sig>

From henning at meier-geinitz.de  Sat Oct 16 15:10:52 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 16:10:52 +0200
Subject: [sane-devel] [BUG] saned: missing input sanitization
In-Reply-To: <1097935280.4439.17.camel@johannes>
References: <1097848060.4219.2.camel@johannes> <20041016134819.GH10704@meier-geinitz.de> <1097935280.4439.17.camel@johannes>
Message-ID: <20041016141052.GA11265@meier-geinitz.de>

Hi,

On Sat, Oct 16, 2004 at 04:01:20PM +0200, Johannes Berg wrote:
> I think the problem is that the network layer does not distinguish
> between zero-length strings and NULL pointers -- as far as I can see it
> interprets a zero-length string 

A zero length string is e.g. SANE_String hubba = "";

> (which is only a byte-array after all)

For sane_net a zero-lenth string is 0 0 0 1 0 (Array of length 1 which
only contains a 0 byte as end marker).

> as a NULL string.

I hope it doesn't. A NULL string is encoded as an array of length 0
(and has no data).

zero-length is ok in sane_open, NULL isn't.

Bye,
  Henning



From johannes at sipsolutions.net  Sat Oct 16 15:23:07 2004
From: johannes at sipsolutions.net (Johannes Berg)
Date: Sat, 16 Oct 2004 16:23:07 +0200
Subject: [sane-devel] [BUG] saned: missing input sanitization
In-Reply-To: <20041016141052.GA11265@meier-geinitz.de>
References: <1097848060.4219.2.camel@johannes>
	<20041016134819.GH10704@meier-geinitz.de>
	<1097935280.4439.17.camel@johannes>
	<20041016141052.GA11265@meier-geinitz.de>
Message-ID: <1097936587.4439.19.camel@johannes>

On Sat, 2004-10-16 at 16:10 +0200, Henning Meier-Geinitz wrote:

> For sane_net a zero-lenth string is 0 0 0 1 0 (Array of length 1 which
> only contains a 0 byte as end marker).

Reading through the code again -- looks like you're right. Somehow I got
the impression that it was the same, but don't remember where I read
that now.

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041016/7b7fb159/attachment.sig>

From lsumpter at dccnet.com  Sat Oct 16 16:35:28 2004
From: lsumpter at dccnet.com (Lloyd Sumpter)
Date: Sat, 16 Oct 2004 08:35:28 -0700
Subject: [sane-devel] Problems with libusb (WAS:Upgrading sane-backend
 on Mandrake 10.0)
In-Reply-To: <20041010133445.GG3144@meier-geinitz.de>
References: <3DDE554B.2030606@dccnet.com> <20041010133445.GG3144@meier-geinitz.de>
Message-ID: <41713FC0.6090006@dccnet.com>


Henning Meier-Geinitz wrote:
> Hi,
> 
> On Fri, Nov 22, 2002 at 08:03:23AM -0800, Lloyd Sumpter wrote:
> 
> Strange date.
> 
Sorry, had just rebooted (from the problems between harddrake and 
sane-find-scanner) and hadn't run rdate yet.

<snip>
> 
>>BTW: The reason I have to upgrade is that apparently the sane-backends 
>>included with Mandrake 10.0 do NOT support libusb (but since the kernel 
>>is 2.6.x, there's no scanner.o to use instead...)
> 
> 
> sane-backends supports libusb since quite some time. And it was needed
> before kernel 2.6 at least for some scanners. So I'd be surprised if
> the Mandrake version had no libusb support.
> 
> You can check by running "sane-find-scanner -v -v". It should print
> messages about using libusb.
> 

Thanks for your help! But on Sept 29, you wrote:

 > On Tue, Sep 28, 2004 at 01:22:01PM -0700, Lloyd Sumpter wrote:
 >
 > > [sanei_debug] Setting debug level of sanei_usb to 255.
 > > [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No 
such  > device
 > > [sanei_usb] sanei_usb_init: found 0 devices
 >
 >
 > Oh. That means that SANE isn't built with libusb support. It only
 > searches for /dev/usb/ but not for libusb devices.
 >
 > As your sane-find-scanner program finds libusb devices, maybe you have
 > an old installation of the SANE backends without libusb support that's
 > used by scanimage?

Note that sane-find-scanner DOES find the scanner (using libusb), but 
scanimage does not.

PLEASE, any help would be appreciated - I've been working on this for weeks!

Lloyd Sumpter




From henning at meier-geinitz.de  Sat Oct 16 17:51:03 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 16 Oct 2004 18:51:03 +0200
Subject: [sane-devel] Problems with libusb (WAS:Upgrading sane-backend on Mandrake 10.0)
In-Reply-To: <41713FC0.6090006@dccnet.com>
References: <3DDE554B.2030606@dccnet.com> <20041010133445.GG3144@meier-geinitz.de> <41713FC0.6090006@dccnet.com>
Message-ID: <20041016165103.GB11265@meier-geinitz.de>

Hi,

On Sat, Oct 16, 2004 at 08:35:28AM -0700, Lloyd Sumpter wrote:
> >You can check by running "sane-find-scanner -v -v". It should print
> >messages about using libusb.
> 
> Thanks for your help! But on Sept 29, you wrote:

Oh, different thread, same problem? I usually don't look at the
author's name :-)

> > Oh. That means that SANE isn't built with libusb support. It only
> > searches for /dev/usb/ but not for libusb devices.
> >
> > As your sane-find-scanner program finds libusb devices, maybe you have
> > an old installation of the SANE backends without libusb support that's
> > used by scanimage?
> 
> Note that sane-find-scanner DOES find the scanner (using libusb), but 
> scanimage does not.

Ok.

> PLEASE, any help would be appreciated - I've been working on this for weeks!

See above. Have you checked if you don't use two different
installations of SANE?

E.g. check sane-find-scanner:
ldd /usr/bin/sane-find-scanner
Check libsane:
ldd /usr/lib/libsane.so.1
And to be safe, check the plustek backend:
ldd /usr/lib/sane/libsane-plustek.so.1
Also check if scanimage is linked to the right sane-backend libs:
ldd /usr/bin/scanimage

You may need to adjust the paths. All should print something about
libusb.

If sane-find-scanner is linked to libusb and libsane isn't, better ask
your distributer what the heck they are doing.

Bye,
  Henning



From scottf at bigpond.net.au  Sat Oct 16 22:02:17 2004
From: scottf at bigpond.net.au (scott fagg)
Date: Sun, 17 Oct 2004 07:02:17 +1000
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <200410062029.50935.Oliver.Schwartz@gmx.de>
References: <415BD75B.1060103@bigpond.net.au> <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain>
 <Pine.LNX.4.53.0410061856300.13865@localhost.localdomain>
 <200410062029.50935.Oliver.Schwartz@gmx.de>
Message-ID: <Pine.LNX.4.53.0410170702070.1932@localhost.localdomain>

On Wed, 6 Oct 2004, Oliver Schwartz wrote:

> Date: Wed, 06 Oct 2004 20:29:47 +0200
> From: Oliver Schwartz <Oliver.Schwartz at gmx.de>
> To: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] epson 2580 problems
>
> Hi,
>
> > Using the latest drivers helps and i can now scan, however preview
> > doesn't work. At least i can get an image out of it now.
> >
> > It seems to only preview either the area of the most recent scan or
> > nothing, and then stretches that image vertically to fit the A4
> > scannable area and shows that as a preview.
>
> Please send me a debug log of a preview scan.

How do i get xsane to generate a debug log ?

>
> /Oliver
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org
>

--
scottf at bigpond.net.au




From scottf at bigpond.net.au  Sat Oct 16 22:08:14 2004
From: scottf at bigpond.net.au (scott fagg)
Date: Sun, 17 Oct 2004 07:08:14 +1000
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <200410062029.50935.Oliver.Schwartz@gmx.de>
References: <415BD75B.1060103@bigpond.net.au> <Pine.LNX.4.53.0410050625010.1814@localhost.localdomain>
 <Pine.LNX.4.53.0410061856300.13865@localhost.localdomain>
 <200410062029.50935.Oliver.Schwartz@gmx.de>
Message-ID: <Pine.LNX.4.53.0410170707470.1932@localhost.localdomain>

On Wed, 6 Oct 2004, Oliver Schwartz wrote:

> Date: Wed, 06 Oct 2004 20:29:47 +0200
> From: Oliver Schwartz <Oliver.Schwartz at gmx.de>
> To: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] epson 2580 problems
>
> Hi,
>
> > Using the latest drivers helps and i can now scan, however preview
> > doesn't work. At least i can get an image out of it now.
> >
> > It seems to only preview either the area of the most recent scan or
> > nothing, and then stretches that image vertically to fit the A4
> > scannable area and shows that as a preview.
>
> Please send me a debug log of a preview scan.

Ignore my earlier question.

Oliver : I've sent you a copy of the log and a screen shot of what occurs.

>
> /Oliver
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org
>

--
scottf at bigpond.net.au




From oliver.bonten at nexgo.de  Sun Oct 17 09:51:34 2004
From: oliver.bonten at nexgo.de (Oliver Bonten)
Date: Sun, 17 Oct 2004 10:51:34 +0200
Subject: [sane-devel] Canon 2700 slide scanner
Message-ID: <200410171051.34335.oliver.bonten@nexgo.de>

Hello,

in the sane-devel archives I found a discussion about 3 weeks old between 
Thomas L?scher and Mitsuru Okaniwa about a problem with the Canon 2700 slide 
scanner. The thread seems to be a bit open-ended to me, so I would like to 
know if there has been any resolution for the problem. It seems that I have 
the same problem with my 2700 and sane 1.0.13. 

I found a work-around which is only a hack and not a solution. I'm using Suse 
9.1, which includes sane 1.0.13-73. Before that, I used Suse 8.1, which 
included sane 1.0.8-47. I didn't have the problem with Suse 8.1. So I  
re-inserted the source-code from the 1.0.8 version of canon.c at the location 
where the error occured (function sense_handler()) to canon.c 1.0.13 at the 
corresponding location, with an if ( 1 ) { /* 1.0.8 source code */ } else 
{ /* 1.0.13 source code */ }. However, this seems to disable some error 
handling, and I have the feeling that my scanner doesn't execute the auto 
focus anymore. Either that or my current set of slides is unusually 
blurred. :-) Sorry, I don't have the source code anymore, because rpmbuild 
doesn't work the way I expected it to work. But I can re-create it if needed.

Would it be safe to re-insert the full 1.0.8 source code for the canon backend 
(i.e., all files matching backend/canon*.[ch]) into an otherwise 1.0.13 sane 
and recompile? I don't want to go back to an older version of sane because I 
also have a flatbed scanner (not canon) which works much better with the 
newer version of sane. 

Regards,

Oliver



From Oliver.Schwartz at gmx.de  Sun Oct 17 12:11:26 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Sun, 17 Oct 2004 13:11:26 +0200
Subject: [sane-devel] epson 2580 problems
In-Reply-To: <Pine.LNX.4.53.0410170707470.1932@localhost.localdomain>
References: <415BD75B.1060103@bigpond.net.au> <200410062029.50935.Oliver.Schwartz@gmx.de> <Pine.LNX.4.53.0410170707470.1932@localhost.localdomain>
Message-ID: <200410171311.28511.Oliver.Schwartz@gmx.de>

Hi,

> Oliver : I've sent you a copy of the log and a screen shot of what
> occurs.

it seems that the scanner somehow doesn't like the set_window command 
which is used to set the scanning area for previewing. 

Since normal scanning works I suspect that it's either the requested 
image size or the operation mode that causes problems. 

Please try to select a small scanning area in xsane and select 
"Preview" again, this should result in a preview of the selected 
area. If this works than it's most likely the default scan area that 
is not set correctly.

If selecting a smaller preview area still doesn't work you can try to 
play around with the operation_mode setting. It is set up in 
snapscan-scsi.c, around line 837, in the variable named "source". 
Bits 6 and 7 are the most likely suspects. The current value for 
preview is 0x80, you can try if any of the other three values gives 
better results.

/Oliver



From ukd at xenon.pc.Uni-Koeln.DE  Sun Oct 17 14:46:34 2004
From: ukd at xenon.pc.Uni-Koeln.DE (Ulrich Deiters)
Date: Sun, 17 Oct 2004 14:46:34 METDST
Subject: [sane-devel] Canon 2700 slide scanner
Message-ID: <200410171246.OAA05289@xenon.pc.Uni-Koeln.DE>

The trouble spot in the Canon SCSI backend has been located,
and we have an experimental backend that seems to support
both the 2700 and the 2710 now. But there is still some
testing and cleaning-up to be done, although that should
not take too long.

Regards,

Ulrich Deiters



From tim at boneko.de  Sun Oct 17 15:35:13 2004
From: tim at boneko.de (Tim Boneko)
Date: Sun, 17 Oct 2004 16:35:13 +0200
Subject: [sane-devel] snapscan: Identified scanner still doesn't work
Message-ID: <200410171635.22500.tim@brocken>

Hello from southern germany,

after lots of googling and searching i finally found this mailing list, 
thank goodness. snapscan.sourceforge.net doesn't mention this. 
I hope someone can help me here:

I bought an Epson Perfection 2480 Photo and tried to install it using 
the instructions on the mentioned sf-site. Software as follows: 

Debian system, kernel 2.6.8.1, sane 1.0.12 from unstable, libsane 
1.0.14-7 from unstable - building the cvs version failed, see below. 
libusb 0.1.5 from unstable, hotplug 20040329 ditto.
My /etc/sane.d/snapscan.conf is attached below. The firmware file to be 
uploaded is in /etc/sane.d. 

The scanner is detected correctly by sane-find-scanner:

>found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON           
>Scanner]) at libusb:003:004

Any access to the scanner (xsane and the like) end up in an error 
message:

>Couldn't start scanner - error during device i/o 

(translated from german)

...so i tried sane-troubleshoot without any result i didn't already 
know. The test-scan ended with the following in /var/log/syslog:

>ehci_hcd 0000:00:02.2: qh c1577780 (#17) state 1
>usb 3-3: usbfs: USBDEVFS_BULK failed ep 0x81 len 3856 >ret -75
>usb 3-3: bulk timeout on ep2out
>usb 3-3: usbfs: USBDEVFS_BULK failed ep 0x2 len 6 ret -110

To me this looks like a usb problem, right? After a failed access to the  
scanner the led of it keeps flashing for minutes. During this time a 
"cat /proc/bus/usb/devices" hangs for 30 seconds before giving out what 
i've attached below.

I tried to build the  snapscan-backend from cvs, but couldn't: 
"make" ended up with

>gcc -o gamma4scanimage gamma4scanimage.o  -lm
>gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations 
>-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes 
>-pedantic -ansi -DHAVE_CONFIG_H -I. -I. -I../include -I../include 
>-DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d          
>-DPATH_SANE_DATA_DIR=/usr/local/share           -DV_MAJOR=1 
>-DV_MINOR=0 sane-desc.c
>gcc -o sane-desc 
>sane-desc.o  ../sanei/libsanei.a ../lib/liblib.a /usr/lib/libusb.so 
>-lnsl -lm
>make[1]: Leaving directory 
>`/archiv/progs/snapscan-cvs/sane-backends/tools'
>making all in doc
>make[1]: Entering directory 
>`/archiv/progs/snapscan-cvs/sane-backends/doc'
>Generating sane.ps...
>make[1]: *** [sane.ps] Fehler 1
>make[1]: Leaving directory 
>`/archiv/progs/snapscan-cvs/sane-backends/doc'
>make: *** [all-recursive] Fehler 1

That's what i've achieved so far. Any hints are greatly appreciated.
TIA,

 tim

To complete the overkill, here's some output of /proc/bus/usb/devices 
after booting:

T:  Bus=03 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#=  7 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs=  1
P:  Vendor=04b8 ProdID=0121 Rev= 0.00
S:  Manufacturer=EPSON
S:  Product=EPSON Scanner
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=83(I) Atr=03(Int.) MxPS=   8 Ivl=4096ms

The output lacks the two "S" lines (Manuf. & Product) when i "cat" it 
while the scanner led is flashing.

Here's my snapscan.conf:

firmware /etc/sane.d/esfw41.bin
usb 0x04b8 0x0121

Adding a line "/dev/usb/scanner0 bus=usb" doesn't change anything. Same 
for an empty firmware file.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041017/61061ae2/attachment.sig>

From henning at meier-geinitz.de  Sun Oct 17 16:05:19 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 17:05:19 +0200
Subject: [sane-devel] snapscan: Identified scanner still doesn't work
In-Reply-To: <200410171635.22500.tim@brocken>
References: <200410171635.22500.tim@brocken>
Message-ID: <20041017150519.GA12072@meier-geinitz.de>

Hi,

On Sun, Oct 17, 2004 at 04:35:13PM +0200, Tim Boneko wrote:
> I tried to build the  snapscan-backend from cvs, but couldn't: 
> "make" ended up with
> 
> >gcc -o gamma4scanimage gamma4scanimage.o  -lm
> >gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations 
> >-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes 
> >-pedantic -ansi -DHAVE_CONFIG_H -I. -I. -I../include -I../include 
> >-DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d          
> >-DPATH_SANE_DATA_DIR=/usr/local/share           -DV_MAJOR=1 
> >-DV_MINOR=0 sane-desc.c
> >gcc -o sane-desc 
> >sane-desc.o  ../sanei/libsanei.a ../lib/liblib.a /usr/lib/libusb.so 
> >-lnsl -lm
> >make[1]: Leaving directory 
> >`/archiv/progs/snapscan-cvs/sane-backends/tools'
> >making all in doc
> >make[1]: Entering directory 
> >`/archiv/progs/snapscan-cvs/sane-backends/doc'
> >Generating sane.ps...
> >make[1]: *** [sane.ps] Fehler 1

latex or some other TeX tool didn't like the commands it got. 
configure checks if these commands are available but maybe you have a
rather strange TeX installation :-)

Anyway, just enter "make install". Make looks into the doc directory
after the backend directory so make install should still work. It may
complain about sane.ps but you can ignore it.

Ifyou like to debug the sane.ps issue, edit doc/Makefile, search for
the rule for sane.ps and delete the "@" in front of the commands and
all the ">/dev/null" and "2>/dev/null". That should print some more
reasonable error messages.

> T:  Bus=03 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#=  7 Spd=480 MxCh= 0
> D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs=  1
> P:  Vendor=04b8 ProdID=0121 Rev= 0.00
> S:  Manufacturer=EPSON
> S:  Product=EPSON Scanner
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
> I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad=83(I) Atr=03(Int.) MxPS=   8 Ivl=4096ms
> 
> The output lacks the two "S" lines (Manuf. & Product) when i "cat" it 
> while the scanner led is flashing.

I think when you cat the devices file the kernel tries to get the
strings by sending a USB control message to the scanner. If the
scanner is confused, it will not react to these messages and they time
out.

Bye,
  Henning



From henning at meier-geinitz.de  Sun Oct 17 16:53:38 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 17:53:38 +0200
Subject: [sane-devel] [ANNOUNCE] sane-frontends 1.0.13 released
Message-ID: <20041017155338.GD12072@meier-geinitz.de>

Hi everyone,

sane-frontends version 1.0.13 has just been released. Download it from
the usual locations as mentioned on http://www.sane-project.org/source.html

This is the md5sum:
2930626e627df49b45192a722cedc8a6  ./sane-frontends-1.0.13.tar.gz

Happy scanning!

Henning



From tim at boneko.de  Sun Oct 17 17:17:19 2004
From: tim at boneko.de (Tim Boneko)
Date: Sun, 17 Oct 2004 18:17:19 +0200
Subject: [sane-devel] snapscan: Identified scanner still doesn't work
In-Reply-To: <20041017150519.GA12072@meier-geinitz.de>
References: <200410171635.22500.tim@brocken> <20041017150519.GA12072@meier-geinitz.de>
Message-ID: <200410171817.27471.tim@brocken>

Something pleasant happened: right after sending tons of text to the 
list i had an idea how to avoid the build failure. After deleting the 
"doc" entry in the SUBDIRS entry of the Makefile the building succeded 
and the scanner seems to be working, apparently even without firmware 
upload.
Sorry for whacking you with text & keep up the good work!
Danke Henning!

 tim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041017/fa4fbe96/attachment.sig>

From henning at meier-geinitz.de  Sun Oct 17 19:10:30 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:10:30 +0200
Subject: [sane-devel] [ANNOUNCE] First pre-release of sane-backends 1.0.15 available
Message-ID: <20041017181030.GG12072@meier-geinitz.de>

Hi everyone,

The first pre-release of sane-backends 1.0.15 is available at
the usual locations as mentioned on http://www.sane-project.org/source.html

The md5sum is:
ff9ad4def17e6644e03d66f07c708b13  sane-backends-1.0.15-pre1.tar.gz

We are in feature freeze currently. In two weeks, code freeze will
start. Release is planned for 2004-11-07.

I'll append the NEWS file for 1.0.15.

Please test this prerelease and tell us about any bugs.

Happy scanning!

Henning

New with 1.0.15, released 2004-??-??:

* New backends: niash
* Updated backends: agfafocus, artec_eplus48u.c, avision, canon, canon_pp,
  coolscan, dll, epson, fujitsu, gt68xx, hp, hp5400, leo, microtek2, mustek,
  mustek_pp, net, pie, plustek, plustek_pp, snapscan, sp15c, tamarack, teco2,
  umax, umax_pp, u12, v4l
* Portability fixes (especially for MacOS X, NetBSD, OS/2, 64 bit platforms).
* sane-find-scanner detects more chipsets now.
* Added Finnish translation. Updated other translations.
* Several saned fixes.
* Build system updates.
* Documentation updates.
* Bugfixes.



From henning at meier-geinitz.de  Sun Oct 17 19:12:09 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:12:09 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
Message-ID: <20041017181209.GH12072@meier-geinitz.de>

Hi everyone,

Feature freeze for sane-backends 1.0.15 is now active. That means,
that now new backend or new features for existing backends should be
committed to CVS. Bug fixes, documentation and translation updates are
ok.

Timetable:
2004-10-31 Code freeze (snapshot)
2004-11-07 Release

Bye,
  Henning



From sirius-c at iname.com  Sun Oct 17 19:16:06 2004
From: sirius-c at iname.com (Jason Anderson)
Date: Sun, 17 Oct 2004 13:16:06 -0500
Subject: [sane-devel] Scanner problems
Message-ID: <20041017181606.58D504BDAB@ws1-1.us4.outblaze.com>

Hello everyone!

I've just got a CanoScan N650U.  When I use the current backends, however, the darn picture is upside down!  I don't know why, either.  Any ideas?

----------
Jason A.
ICQ# 148434286
-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm




From Oliver.Rauch at Rauch-Domain.DE  Sun Oct 17 19:12:29 2004
From: Oliver.Rauch at Rauch-Domain.DE (Oliver Rauch)
Date: 17 Oct 2004 20:12:29 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
In-Reply-To: <20041017181209.GH12072@meier-geinitz.de>
References: <20041017181209.GH12072@meier-geinitz.de>
Message-ID: <1098036749.2126.1.camel@Babylon7>

Am Son, 2004-10-17 um 20.12 schrieb Henning Meier-Geinitz:
> Hi everyone,
> 
> Feature freeze for sane-backends 1.0.15 is now active. That means,
> that now new backend or new features for existing backends should be
       ^^^ I think this should be a NO or there is missing a NO.
But it should be clear anyway that it is NOT allowed to add new features
after feature freeze.

Oliver

> committed to CVS. Bug fixes, documentation and translation updates are
> ok.





From henning at meier-geinitz.de  Sun Oct 17 19:25:28 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:25:28 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
In-Reply-To: <1098036749.2126.1.camel@Babylon7>
References: <20041017181209.GH12072@meier-geinitz.de> <1098036749.2126.1.camel@Babylon7>
Message-ID: <20041017182528.GI12072@meier-geinitz.de>

Hi,

On Sun, Oct 17, 2004 at 08:12:29PM +0200, Oliver Rauch wrote:
> Am Son, 2004-10-17 um 20.12 schrieb Henning Meier-Geinitz:
> > Hi everyone,
> > 
> > Feature freeze for sane-backends 1.0.15 is now active. That means,
> > that now new backend or new features for existing backends should be
>        ^^^ I think this should be a NO or there is missing a NO.
> But it should be clear anyway that it is NOT allowed to add new features
> after feature freeze.

Right. Copy- and paste error. I wanted to write something like this:

"Feature freeze means that no new backends or new features for existing
backends should be committed to CVS."

Bye,
  Henning



From henning at meier-geinitz.de  Sun Oct 17 19:30:00 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:30:00 +0200
Subject: [sane-devel] Scanner problems
In-Reply-To: <20041017181606.58D504BDAB@ws1-1.us4.outblaze.com>
References: <20041017181606.58D504BDAB@ws1-1.us4.outblaze.com>
Message-ID: <20041017183000.GJ12072@meier-geinitz.de>

Hi,

On Sun, Oct 17, 2004 at 01:16:06PM -0500, Jason Anderson wrote:
> I've just got a CanoScan N650U.  When I use the current backends,

With current backends you mean the version from CVS?

> however, the darn picture is upside down!  I don't know why, either.

What's the last version of sane-backends that worked?

"Upside down" means that if you turn around (180?) the image that is
to be scanned the result will be ok?

Bye,
  Henning



From henning at meier-geinitz.de  Sun Oct 17 19:42:28 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:42:28 +0200
Subject: [sane-devel] Translation status
Message-ID: <20041017184228.GK12072@meier-geinitz.de>

Hi everyone,

As sane-backends is in feature freeze now I don't expect any bigger
changes to the option strings until release. So it's the right time to
update translations now.

This is the current status (percentage of translation):

sane-backends.bg.po (96.2%)
sane-backends.cs.po (92.8%)
sane-backends.da.po (100.0%)
sane-backends.de.po (99.7%)
sane-backends.es.po (40.2%)
sane-backends.fi.po (94.7%)
sane-backends.fr.po (90.1%)
sane-backends.it.po (100.0%)
sane-backends.nl.po (96.4%)
sane-backends.no.po (36.5%)
sane-backends.pt.po (23.7%)
sane-backends.ru.po (66.1%)
sane-backends.sv.po (100.0%)

Even if the percentage is near 100%, it doesn't harm to have a look at
the translations to check if they are correct.

New translations are always appreciated.

Here is a translation question: What does "8x8 Coarse Fatting" mean
(from leo.c)? Well, I know what 8x8 and coarse is, but I can't really
interpret "fatting".

Bye,
  Henning



From henning at meier-geinitz.de  Sun Oct 17 19:55:55 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 17 Oct 2004 20:55:55 +0200
Subject: [sane-devel] Open bug reports
Message-ID: <20041017185555.GL12072@meier-geinitz.de>

Hi everyone,

There are currently 102 open bug reports for SANE. I'm quite sure that
some of them can be easily fixed.

If you are a SANE developer and have an account on alioth, please
logon on the alioth website. After login, you'll get a list with your
bug reports "My Assigned Items". These are the bug reports that have
been assigned to you. 

Please have a look at them. If you think they are bogus, write a short
comment and close them.

If you think it's a bug but not in your backend, write a short comment
and assign them to the "guilty" developer or "Nobody" if you don't
know which developer is the right one.

If it's a bug in your backend but it's not important decrease priority
and write a comment that you'll fix that later.

If there is not enough information, ask for more.

You'll get a mail once you have been assigned a bug and with every
change of that bug.

There are also quite some bugs that are not assigned to anyone because
they concern several backends or no backend at all. Please also have a
look at them.
Example: [ #300962 ] umax_pp & plustek: Harmonise option names

Also "normal" users are invited to add comments to the bug reports.
Maybe you have seen the same bug and can give more details? Or you
even know how to fix it? I recommend getting a login at alioth as
you'll be informed by mail when your bug is changed in this case. Also
you can attach files to bugs when you are logged in.

Happy bug-hunting!

Bye,
  Henning




From martin at mkcollins.org  Sun Oct 17 21:18:52 2004
From: martin at mkcollins.org (Martin Collins)
Date: Sun, 17 Oct 2004 21:18:52 +0100
Subject: [sane-devel] Translation status
In-Reply-To: <20041017184228.GK12072@meier-geinitz.de>
References: <20041017184228.GK12072@meier-geinitz.de>
Message-ID: <20041017211852.0bfeb848.martin@mkcollins.org>

On Sun, 17 Oct 2004 20:42:28 +0200
Henning Meier-Geinitz <henning at meier-geinitz.de> wrote:

> Here is a translation question: What does "8x8 Coarse Fatting" mean
> (from leo.c)? Well, I know what 8x8 and coarse is, but I can't
> really interpret "fatting".

Bizarre. Perhaps it should be "Fitting"? Doesn't make a great deal more
sense but at least it's an english word.

Martin



From johannes at sipsolutions.net  Sun Oct 17 21:58:24 2004
From: johannes at sipsolutions.net (Johannes Berg)
Date: Sun, 17 Oct 2004 22:58:24 +0200
Subject: [sane-devel] Translation status
In-Reply-To: <20041017184228.GK12072@meier-geinitz.de>
References: <20041017184228.GK12072@meier-geinitz.de>
Message-ID: <1098046704.5232.20.camel@johannes>

On Sun, 2004-10-17 at 20:42 +0200, Henning Meier-Geinitz wrote:
> Here is a translation question: What does "8x8 Coarse Fatting" mean
> (from leo.c)? Well, I know what 8x8 and coarse is, but I can't really
> interpret "fatting".

It is a type of "rastern". See
http://www.pl32.com/tutorial/sraster/sraster.htm
for an image.

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041017/d1e4d7e9/attachment.sig>

From martin at mkcollins.org  Sun Oct 17 22:54:44 2004
From: martin at mkcollins.org (Martin Collins)
Date: Sun, 17 Oct 2004 22:54:44 +0100
Subject: [sane-devel] Translation status
In-Reply-To: <1098046704.5232.20.camel@johannes>
References: <20041017184228.GK12072@meier-geinitz.de>
	<1098046704.5232.20.camel@johannes>
Message-ID: <20041017225444.2305af39.martin@mkcollins.org>

On Sun, 17 Oct 2004 22:58:24 +0200
Johannes Berg <johannes at sipsolutions.net> wrote:

> It is a type of "rastern". See
> http://www.pl32.com/tutorial/sraster/sraster.htm
> for an image.

So it seems Fatting is the name of the inventor of a dither pattern,
like Bayer or Floyd Steinberg. No translation necessary.

Martin



From mattias.ellert at tsl.uu.se  Sun Oct 17 23:23:41 2004
From: mattias.ellert at tsl.uu.se (Mattias Ellert)
Date: Mon, 18 Oct 2004 00:23:41 +0200
Subject: [sane-devel] Translation status
In-Reply-To: <20041017225444.2305af39.martin@mkcollins.org>
References: <20041017184228.GK12072@meier-geinitz.de> <1098046704.5232.20.camel@johannes> <20041017225444.2305af39.martin@mkcollins.org>
Message-ID: <33453883-208B-11D9-B39B-0003930D2AFC@tsl.uu.se>

2004-10-17 kl. 23.54 skrev Martin Collins:

> On Sun, 17 Oct 2004 22:58:24 +0200
> Johannes Berg <johannes at sipsolutions.net> wrote:
>
>> It is a type of "rastern". See
>> http://www.pl32.com/tutorial/sraster/sraster.htm
>> for an image.
>
> So it seems Fatting is the name of the inventor of a dither pattern,
> like Bayer or Floyd Steinberg. No translation necessary.
>
> Martin
>

This is what is in there now. S? most translators have tried to find a 
translation...

sane-backends-1.0.15-pre1/po/sane-backends.bg.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgstr "8x8 ???? 
Fatting"
--
sane-backends-1.0.15-pre1/po/sane-backends.bg.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgstr "8x8 ??? 
Fatting"
--
sane-backends-1.0.15-pre1/po/sane-backends.cs.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.cs.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.cs.po-msgstr "8x8 hrub? 
zv?razn?n? (fatting)"
--
sane-backends-1.0.15-pre1/po/sane-backends.cs.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.cs.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.cs.po-msgstr "8x8 jemn? 
zv?ran?n? (fatting)"
--
sane-backends-1.0.15-pre1/po/sane-backends.da.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.da.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.da.po-msgstr "8x8 grov 
fortykning"
--
sane-backends-1.0.15-pre1/po/sane-backends.da.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.da.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.da.po-msgstr "8x8 fin 
fortykning"
--
sane-backends-1.0.15-pre1/po/sane-backends.de.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.de.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.de.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.de.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.de.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.de.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.es.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.es.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.es.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.es.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.es.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.es.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.fi.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.fi.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.fi.po-msgstr "8x8 raaka 
lihavointi"
--
sane-backends-1.0.15-pre1/po/sane-backends.fi.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.fi.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.fi.po-msgstr "8x8 hieno 
lihavointi"
--
sane-backends-1.0.15-pre1/po/sane-backends.fr.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.fr.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.fr.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.fr.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.fr.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.fr.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.it.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.it.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.it.po-msgstr "8x8 grana 
grossa"
--
sane-backends-1.0.15-pre1/po/sane-backends.it.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.it.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.it.po-msgstr "8x8 grana fine"
--
sane-backends-1.0.15-pre1/po/sane-backends.nl.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.nl.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.nl.po-msgstr "8x8 Grof 
Aandikken"
--
sane-backends-1.0.15-pre1/po/sane-backends.nl.po-#, fuzzy
sane-backends-1.0.15-pre1/po/sane-backends.nl.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.nl.po-msgstr "8x8 Fijn 
Aandikken"
--
sane-backends-1.0.15-pre1/po/sane-backends.no.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.no.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.no.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.no.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.no.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.no.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.pt.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.pt.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.pt.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.pt.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.pt.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.pt.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.ru.po-#, fuzzy
sane-backends-1.0.15-pre1/po/sane-backends.ru.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.ru.po-msgstr "8x8 ??????"
--
sane-backends-1.0.15-pre1/po/sane-backends.ru.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.ru.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.ru.po-msgstr ""
--
sane-backends-1.0.15-pre1/po/sane-backends.sv.po-#: .tmp/leo.c:111
sane-backends-1.0.15-pre1/po/sane-backends.sv.po:msgid "8x8 Coarse 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.sv.po-msgstr "8x8 grov 
f?rtjockning"
--
sane-backends-1.0.15-pre1/po/sane-backends.sv.po-#: .tmp/leo.c:112
sane-backends-1.0.15-pre1/po/sane-backends.sv.po:msgid "8x8 Fine 
Fatting"
sane-backends-1.0.15-pre1/po/sane-backends.sv.po-msgstr "8x8 fin 
f?rtjockning"

	Mattias




From martin at mkcollins.org  Mon Oct 18 00:06:08 2004
From: martin at mkcollins.org (Martin Collins)
Date: Mon, 18 Oct 2004 00:06:08 +0100
Subject: [sane-devel] Translation status
In-Reply-To: <33453883-208B-11D9-B39B-0003930D2AFC@tsl.uu.se>
References: <20041017184228.GK12072@meier-geinitz.de>
	<1098046704.5232.20.camel@johannes>
	<20041017225444.2305af39.martin@mkcollins.org>
	<33453883-208B-11D9-B39B-0003930D2AFC@tsl.uu.se>
Message-ID: <20041018000608.3c4f4917.martin@mkcollins.org>

On Mon, 18 Oct 2004 00:23:41 +0200
Mattias Ellert <mattias.ellert at tsl.uu.se> wrote:

> This is what is in there now. S? most translators have tried to find
> a translation...

> sane-backends-1.0.15-pre1/po/sane-backends.cs.po-msgstr "8x8 hrub? 
> zv?razn__n? (fatting)"

> sane-backends-1.0.15-pre1/po/sane-backends.da.po-msgstr "8x8 grov 
> fortykning"

> sane-backends-1.0.15-pre1/po/sane-backends.fi.po-msgstr "8x8 raaka 
> lihavointi"

> sane-backends-1.0.15-pre1/po/sane-backends.it.po-msgstr "8x8 grana 
> grossa"

> sane-backends-1.0.15-pre1/po/sane-backends.nl.po-msgstr "8x8 Grof 
> Aandikken"

> sane-backends-1.0.15-pre1/po/sane-backends.sv.po-msgstr "8x8 grov 
> f?rtjockning"

I'm no linguist but it looks like mostly variations on "fat" or
"fattening". I bet the guy is as skinny as a rake.

Martin



From olaf at epkowa.co.jp  Mon Oct 18 02:48:16 2004
From: olaf at epkowa.co.jp (Olaf Meeuwissen)
Date: Mon, 18 Oct 2004 10:48:16 +0900
Subject: [sane-devel] Xsane Crashes with Epson 4180 Scanner
In-Reply-To: <20041015123703.GF3623@meier-geinitz.de> (Henning
 Meier-Geinitz's message of "Fri, 15 Oct 2004 14:37:03 +0200")
References: <200410132249.08934.mreuther@umich.edu>
	<200410141257.21475.mreuther@umich.edu>
	<20041014173205.GF12141@meier-geinitz.de>
	<200410141930.32684.mreuther@umich.edu>
	<4A35F8D0-1E3F-11D9-820C-000A957E40E8@khk.net>
	<87u0sw3gnw.fsf@zen.epkowa.co.jp>
	<20041015123703.GF3623@meier-geinitz.de>
Message-ID: <874qksn6e7.fsf@zen.epkowa.co.jp>

Henning Meier-Geinitz <henning at meier-geinitz.de> writes:

> Hi,
>
> On Fri, Oct 15, 2004 at 10:37:39AM +0900, Olaf Meeuwissen wrote:
>> Karl Heinz Kremer <khk at khk.net> writes:
>> 
>> > It looks like this scanner does not "speak" the ESC/I protocol. At
>> > least not any flavor that the EPSON backend supports. Maybe Olaf can
>> > shed some light on this.
>> 
>> I guess I could ;-)
>> 
>> As the EPSON drivers say, this is a GT-F600.  It does not speak ESC/I.
>> It will be supported by iscan's epkowa backend in the near future (but
>> first we'll get a release for a bunch of all-in-ones).
>
> I've added Perfection 4160 and GT-F600 as unsupported to our lists for
> now (with some details from your mail).

That's the Perfection 4180, but I see you've added it correctly in
unsupported.desc.

-- 
Olaf Meeuwissen                            EPSON KOWA Corporation, PF1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2



From sirius-c at iname.com  Mon Oct 18 04:59:09 2004
From: sirius-c at iname.com (Jason Anderson)
Date: Sun, 17 Oct 2004 22:59:09 -0500
Subject: [sane-devel] Re: Scanner Problems
Message-ID: <20041018035909.4D9636EEE9@ws1-5.us4.outblaze.com>

I'm talking about version 1.0.14, I think it's CVS, but I don't know.  And yep, I need to turn it 180 just to properly scan it.

>
> 
> Hi,
> 
> On Sun, Oct 17, 2004 at 01:16:06PM -0500, Jason Anderson wrote:
> > I've just got a CanoScan N650U.  When I use the current backends,
> 
> With current backends you mean the version from CVS?
> 
> > however, the darn picture is upside down!  I don't know why, either.
> 
> What's the last version of sane-backends that worked?
> 
> "Upside down" means that if you turn around (180?) the image that is
> to be scanned the result will be ok?
> 
> Bye,
>   Henning
> 
> 

-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm




From gerhard at gjaeger.de  Mon Oct 18 13:04:58 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Mon, 18 Oct 2004 14:04:58 +0200
Subject: [sane-devel] Re: Scanner Problems
In-Reply-To: <20041018035909.4D9636EEE9@ws1-5.us4.outblaze.com>
References: <20041018035909.4D9636EEE9@ws1-5.us4.outblaze.com>
Message-ID: <200410181404.58155.gerhard@gjaeger.de>

On Monday 18 October 2004 05:59, Jason Anderson wrote:
> I'm talking about version 1.0.14, I think it's CVS, but I don't know.  And
> yep, I need to turn it 180 just to properly scan it.

Which is the SANE version, that used to work? I'm pretty sure, that you won't
find any other version that did it the other way. When opening the scanner,
the sensor home position is on that side, where the button is located. 

Ciao,
  Gerhard

>
> > Hi,
> >
> > On Sun, Oct 17, 2004 at 01:16:06PM -0500, Jason Anderson wrote:
> > > I've just got a CanoScan N650U.  When I use the current backends,
> >
> > With current backends you mean the version from CVS?
> >
> > > however, the darn picture is upside down!  I don't know why, either.
> >
> > What's the last version of sane-backends that worked?
> >
> > "Upside down" means that if you turn around (180?) the image that is
> > to be scanned the result will be ok?
> >
> > Bye,
> >   Henning




From sushyad at yahoo.com  Mon Oct 18 17:03:55 2004
From: sushyad at yahoo.com (Susheel Yadav)
Date: Mon, 18 Oct 2004 09:03:55 -0700 (PDT)
Subject: [sane-devel] Need help analyzing USBSnoopy logs for Microtek Scanmaker 5600
In-Reply-To: <20040915221215.11604.qmail@web13903.mail.yahoo.com>
Message-ID: <20041018160355.27003.qmail@web13925.mail.yahoo.com>

Some good news on the Microtek Scanmaker 5600 front -
with Karsten's and Bertrik's help, I have been able to
decode the usb protocol for setting/reading status,
setting scan window and other scan parameters etc.
Using javax-usb, I have been able to read image data
through bulk transfer. I will start developing the
sane backend very soon. As a template, I plan to use
the sm3600 usb code.

I have a couple of questions regarding sane
integration:
1. Once I have the raw image data, what do I do with
it?
2. How do I process the raw image data to create
usable image?
3. Is there any common core sane code to handle the
raw image data like saving it in different formats?

Thanks!

Susheel

--- Susheel Yadav <sushyad at yahoo.com> wrote:

> Karsten,
> Please go ahead and send me the documents.
> 
> Bertrik,
> Your analysis is right on! So all that huge chunk of
> data in the beginning is just for calibration, and
> data the towards the end is the image data.
> 
> I will play around with those parameters and try to
> get some image. After that I will need to know how
> to
> use the calibration data.
> 
> Thanks a lot guys!
> 
> --- Karsten Festag <karsten.festag at gmx.de> wrote:
> 
> > Hi,
> > 
> > I just looked curiously on the data and I think
> > there are some similarities 
> > between the scsi based scanners driven by the
> > microtek2 backend and the 5600:
> > 
> > command 0x24 is used to setup the scan window,
> > probably first a fixed window 
> > for calibration and second the actual scan window.
> > 
> > command 0x28 0xnn 0x80 reads image information
> > (width, height, bytes)
> > command 0x28 0xnn 0x81 reads system status (Lamps
> > on/off, buttons,) and 0x2a 
> > 0xnn 0x81 should set the status.
> > command 0x28 0xnn 0x82 reads scanner attributes
> > (resolution, width, heigt of 
> > the scan area.......)
> > 
> > Maybe a look at the microtek2 sources helps you. I
> > also have some (quite old) 
> > documentation but it may help. Tell me if I shall
> > send it to you (its an ugly 
> > MS Word file :-()
> > 
> > Regards,
> > 
> > Karsten
> > 
> > 
> > On Wednesday 15 September 2004 21:57, Susheel
> Yadav
> > wrote:
> > > Thanks a lot Bertrik for your analysis. I have
> > figured
> > > out some things - I have written those down in
> the
> > > last  link on the web page.
> > >
> > > *request=0x24 value=0x00 data=0x45 bytes
> > > The data transferred in this request did not
> > change
> > > even if I moved the scan area horizontally
> keeping
> > the
> > > size constant. This makes me think that maybe it
> > scans
> > > the whole row and the software clips the image
> > later.
> > > What do you think?
> > >
> > > *request=0x26 value=0x00 data=0xef00 bytes
> > > This happens before bulk transfers, and the data
> > > returned in Nth step is sent to the scanner in
> the
> > > (N+1)th request.
> > >
> > > *The bulk transfer is followed by a small
> transfer
> > of
> > > 0x40 bytes. This returns 0x10 bytes. The last
> 0x30
> > > bytes sent always remain same, and the first
> 0x10
> > > bytes are the ones that were returned from the
> > > previous cycle. Could this signify the position
> of
> > the
> > > next chunk of data?
> > >
> > > *request=0x28, 0x40, 0x83, 0x12 repeat and I
> think
> > > they are status check. The windows driver has a
> > > scanner detector utility which when turned on,
> > keeps
> > > sending those packets.
> > >
> > > *request=0x28 value=0x83
> > > This request gets the data that is send back in
> > some
> > > 0x40 0x2a 0x81 requests.
> > >
> > > *request=0x29 seems to denote the end of
> transfer
> > > since there is no more bulk data after that.
> > >
> > > --- Bertrik Sikken <bertrik at zonnet.nl> wrote:
> > > > Susheel Yadav wrote:
> > > > > Hi,
> > > > > I am trying to write the linux driver for
> > Microtek
> > > > > Scanmaker 5600 scanner. I used USBSnoopy to
> > > >
> > > > generate
> > > >
> > > > > these logs from VMWare/Win2k. I have
> filtered
> > out
> > > >
> > > > the
> > > >
> > > > > big bulk transfers. The log files are still
> in
> > > >
> > > > ~200KB
> > > >
> > > > > range. I am providing a link below with the
> > log
> > > >
> > > > files.
> > > >
> > > > > I have made some progress in identifying the
> > > >
> > > > status
> > > >
> > > > > check packets, and some pattern in the bulk
> > > >
> > > > transfers,
> > > >
> > > > > but I have no idea what those medium sized
> > control
> > > > > packets mean. I would appreciate any help.
> > > > >
> > > > > http://blanca.homelinux.com/usblogs/
> > > > >
> > > > > Thank you very much!
> > > >
> > > > What medium sized control packets do you mean?
> > > >
> > > >
> > > > I looked a bit at the logs and noticed 10
> unique
> > > > patterns:
> > > >
> > > > * request=0x12, value=0x00: read version info?
> > > > The data returned by this transfer contains
> the
> > > > strings
> > > > "ScanMaker 5600  1.30"
> > > > "NowV0.10NewV0.10"
> > > >
> > > > * request=0x24, value=0x00: write 0x45 bytes
> of
> > scan
> > > > settings?
> > > > This transfer contains numbers like 1200, 600,
> > 300,
> > > > which are likely
> > > > DPI or LPI resolutions. I think that scan area
> > is
> > > > also coded in this
> > > > transfer. It noticed this transfer happens
> twice
> > > > (once for calibration,
> > > > then once for the actual scan?)
> > > >
> > > > * request=0x26, value=0x00: prepare bulk read
> > (index
> > > > = length)
> > > > This transfer always seems to happen just
> before
> > a
> > > > bulk read
> > > >
> > > > * request=0x28, value=0x80: get a bunch of
> bytes
> > > > (don't know what)
> > > >
> > > > * request=0x28, value=0x81: read some 9-byte
> > buffer
> > > >
> > > > * request=0x28, value=0x82: read scan
> > capabilities?
> > > > This transfer also has typical DPI numbers,
> but
> > > > always seem to be
> > > > the same (not always same length though)
> > > >
> > > > * request=0x28, value=0x83: read status byte?
> > > > (00 = ready, 08 = not ready?)
> > > >
> > > > * request=0x29, value=0x2101: prepare bulk
> write
> 
=== message truncated ===



		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com



From henning at meier-geinitz.de  Mon Oct 18 17:21:03 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 18 Oct 2004 18:21:03 +0200
Subject: [sane-devel] Need help analyzing USBSnoopy logs for Microtek Scanmaker 5600
In-Reply-To: <20041018160355.27003.qmail@web13925.mail.yahoo.com>
References: <20040915221215.11604.qmail@web13903.mail.yahoo.com> <20041018160355.27003.qmail@web13925.mail.yahoo.com>
Message-ID: <20041018162103.GA4761@meier-geinitz.de>

Hi,

On Mon, Oct 18, 2004 at 09:03:55AM -0700, Susheel Yadav wrote:
> Some good news on the Microtek Scanmaker 5600 front -
> with Karsten's and Bertrik's help, I have been able to
> decode the usb protocol for setting/reading status,
> setting scan window and other scan parameters etc.
> Using javax-usb, I have been able to read image data
> through bulk transfer. I will start developing the
> sane backend very soon. As a template, I plan to use
> the sm3600 usb code.

Good news. But please don't use direct calls to libusb as done in
sm3600. Instead use the sanei_usb_* functions that are provided by
sanei/sanei_usb.c. If backends use direct calls to libusb, they can't
be used with other USB access methods and every backend muste be
changed if e.g. a new USB access library is to be supported by SANE.

> I have a couple of questions regarding sane
> integration:
> 1. Once I have the raw image data, what do I do with
> it?

In the SANE backend, you implement the function sane_read() which is
called by the frontend to get the data from the backend. 

> 2. How do I process the raw image data to create
> usable image?

Depending on the scanner you may need to do line calibration
(correction of the brightness difference of every single CCD/CIS
pixel) and/or line distance correction (in color mode). More
intelligent scanners do that internally, however.

After that you process the image data to be compatible with the SANE
protocol (see SANE standard) and return it by sane_read().

> 3. Is there any common core sane code to handle the
> raw image data like saving it in different formats?

That's done by the frontend. As a backend author you don't need to
care about that.

Bye,
  Henning



From till.kamppeter at gmx.net  Mon Oct 18 19:29:19 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Mon, 18 Oct 2004 20:29:19 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Message-ID: <41740B7F.5040507@gmx.net>

Oi,

I got the above-mentioned scanners for some days for testing.
Unfortunately without the Windows CDs. Can someone send me the firmware
files for them (*.bin) files? The firmware file in Epson's IScan package
seems not to work, too old or so. XSane segfaults with it.

Thanks.

    Till




From drjones at vii.com  Mon Oct 18 18:48:08 2004
From: drjones at vii.com (Dr. Jones)
Date: Mon, 18 Oct 2004 11:48:08 -0600
Subject: [sane-devel] Scanjet 4C - newbie with linux and sane scanning
In-Reply-To: <41740B7F.5040507@gmx.net>
References: <41740B7F.5040507@gmx.net>
Message-ID: <417401D8.3020909@vii.com>

I am writing to get some help and pointers and to hopefully avoid the 
pitfalls.

I have been running debian 3.0 a while now, but have yet to hook up my 
scanner, which now resides on an older windows machine. It uses the SCSI 
card interface, and works well on my win 98se box; but I want to 
eliminate Windows completely from my network here.

Any suggestions other than to dive in and try it on my machine? I am 
thinking of just installing linux on my current 98se box...and then 
setting up SANE to handle the scanning, hoping that it's not too 
painful. I'd love to hear from others who use a ScanJet 4c device.

Scott

-- 
Dr. Scott S. Jones
Hands-On Chiropractic 
IRC: irc.freenode.net #utah
Yahoo: sanchiro12





From johannes at sipsolutions.net  Mon Oct 18 19:20:26 2004
From: johannes at sipsolutions.net (Johannes Berg)
Date: Mon, 18 Oct 2004 20:20:26 +0200
Subject: [sane-devel] update net.tex for sane1 documentation
Message-ID: <1098123627.5219.23.camel@johannes>

Here's a patch to add RPC codes and a short explanation of transferred
data to net.tex, with this the document is IMHO much more readable since
now you actually know what data is on the wire :)

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: net.tex.patch
Type: text/x-patch
Size: 2972 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041018/bc4a1a23/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041018/bc4a1a23/attachment.sig>

From martin at mkcollins.org  Mon Oct 18 22:31:27 2004
From: martin at mkcollins.org (Martin Collins)
Date: Mon, 18 Oct 2004 22:31:27 +0100
Subject: [sane-devel] Scanjet 4C - newbie with linux and sane scanning
In-Reply-To: <417401D8.3020909@vii.com>
References: <41740B7F.5040507@gmx.net>
	<417401D8.3020909@vii.com>
Message-ID: <20041018223127.374c47f5.martin@mkcollins.org>

On Mon, 18 Oct 2004 11:48:08 -0600
"Dr. Jones" <drjones at vii.com> wrote:

> I am writing to get some help and pointers and to hopefully avoid
> the pitfalls.
...
> Any suggestions other than to dive in and try it on my machine?

If the default kernel doesn't support your SCSI card you will need to
find or compile one that does. Knowing what chipset it uses will help
there. Once your card is recognised you have to set appropriate
permissions on the device files so non-root users can use the scanner.

Once you have got your SCSI configured properly it should be easy. Just
  apt-get install xsane
and you're good to go. If it doesn't go start by reading man sane-scsi
and sane-hp then post your logs and other details here.

Martin



From khk at khk.net  Mon Oct 18 22:52:10 2004
From: khk at khk.net (Karl Heinz Kremer)
Date: Mon, 18 Oct 2004 17:52:10 -0400
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41740B7F.5040507@gmx.net>
References: <41740B7F.5040507@gmx.net>
Message-ID: <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net>

You can download them from EPSON's web site:

http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? 
BV_UseBVCookie=yes&oid=41623&infoType=Overview
http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? 
BV_UseBVCookie=yes&oid=41624&infoType=Overview

On Oct 18, 2004, at 2:29 PM, Till Kamppeter wrote:

> Oi,
>
> I got the above-mentioned scanners for some days for testing.
> Unfortunately without the Windows CDs. Can someone send me the firmware
> files for them (*.bin) files? The firmware file in Epson's IScan  
> package
> seems not to work, too old or so. XSane segfaults with it.
>
> Thanks.
>
>    Till
>
>
> -- 
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to sane-devel-request at lists.alioth.debian.org




From janunez07 at hotmail.com  Tue Oct 19 14:29:51 2004
From: janunez07 at hotmail.com (José Alberto Nuñez Aranguren)
Date: Tue, 19 Oct 2004 09:29:51 -0400
Subject: [sane-devel] Compatibility with scanner HP 8290
Message-ID: <BAY24-F304Atg2c7qIA0000bd28@hotmail.com>

  Hi,  I'm looking for information to use scanner HP8290 with sanelib.

   Does SANE compatible with this scanner?

regards

JAN

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.com/




From till.kamppeter at gmx.net  Tue Oct 19 16:03:14 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Tue, 19 Oct 2004 17:03:14 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net>
References: <41740B7F.5040507@gmx.net> <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net>
Message-ID: <41752CB2.8000504@gmx.net>

Thank you for the links. The Windows driver packages and so the firmware 
files are absolutely the same for both the 2480 and the 2580 scanners. 
Unfortunately, both scanners do not work.

I have specified the firmware file in /etc/sane.d/snapscan.conf and 
"scanimage -L" confirms that "snapscan" is the driver in use for both 
models. I am using sane-backends 1.15-pre1.

To get a debug log I executed

SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm 2> eps2580debug.log

The log files are

http://www.linuxprinting.org/till/tmp/eps2480debug.log
http://www.linuxprinting.org/till/tmp/eps2580debug.log

    Till


Karl Heinz Kremer wrote:
> You can download them from EPSON's web site:
> 
> http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? 
> BV_UseBVCookie=yes&oid=41623&infoType=Overview
> http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? 
> BV_UseBVCookie=yes&oid=41624&infoType=Overview
> 
> On Oct 18, 2004, at 2:29 PM, Till Kamppeter wrote:
> 
>> Oi,
>>
>> I got the above-mentioned scanners for some days for testing.
>> Unfortunately without the Windows CDs. Can someone send me the firmware
>> files for them (*.bin) files? The firmware file in Epson's IScan  package
>> seems not to work, too old or so. XSane segfaults with it.
>>
>> Thanks.
>>
>>    Till
>>
>>
>> -- 
>> sane-devel mailing list: sane-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>             to sane-devel-request at lists.alioth.debian.org
> 
> 
> 




From gerard at gkall.hobby.nl  Tue Oct 19 16:55:05 2004
From: gerard at gkall.hobby.nl (gerard klaver)
Date: Tue, 19 Oct 2004 15:55:05 +0000
Subject: [sane-devel] Compatibility with scanner HP 8290
In-Reply-To: <BAY24-F304Atg2c7qIA0000bd28@hotmail.com>
References: <BAY24-F304Atg2c7qIA0000bd28@hotmail.com>
Message-ID: <1098201305.1604.3.camel@gk-lex3>

On Tue, 2004-10-19 at 13:29, Jos? Alberto Nu?ez Aranguren wrote:
>   Hi,  I'm looking for information to use scanner HP8290 with sanelib.
> 
>    Does SANE compatible with this scanner?
> 
> regards
> 
> JAN

See this link below for some information about your scanner (its not
supported).

A start is to fill the mentioned form on this page with the missing 
information.

 http://www.sane-project.org/unsupported/hp-scanjet-8290.html

-- 
----------
m.vr.gr.
Gerard Klaver




From hfiguiere at teaser.fr  Tue Oct 19 18:51:03 2004
From: hfiguiere at teaser.fr (Hubert Figuiere)
Date: Tue, 19 Oct 2004 13:51:03 -0400
Subject: [sane-devel] Problem with Olivetti Job_Jet M400
In-Reply-To: <20041015125640.GH3623@meier-geinitz.de>
References: <200410151244.58949.livhu.tshisikule@telkomsa.net>
	 <20041015120814.GB3623@meier-geinitz.de>
	 <200410151447.15977.livhu.tshisikule@telkomsa.net>
	 <20041015125640.GH3623@meier-geinitz.de>
Message-ID: <1098208264.27006.35.camel@atlan>

On Fri, 2004-10-15 at 14:56 +0200, Henning Meier-Geinitz wrote:
> > found USB scanner (vendor=0x0b3c [Olivetti], product=0xa880 [Job_Jet
> M400]) at libusb:003:002
> 
> Thanks. 0x03bc is really Olivetti so they haven't just used a HP
> device and printed a new logo on the case.
> 

They can still change the USB IDs in the firmware and still be
compatible. No ?

This is the case for rebadjed Lexmark 1150 (all-in-one) that are sold by
Dell as A920. They show up as Dell devices.

Hub
-- 
Crazy French - http://www.figuiere.net/hub/




From Oliver.Schwartz at gmx.de  Tue Oct 19 19:38:58 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Tue, 19 Oct 2004 20:38:58 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41752CB2.8000504@gmx.net>
References: <41740B7F.5040507@gmx.net> <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net> <41752CB2.8000504@gmx.net>
Message-ID: <200410192039.00356.Oliver.Schwartz@gmx.de>

Hi,

> http://www.linuxprinting.org/till/tmp/eps2480debug.log
> http://www.linuxprinting.org/till/tmp/eps2580debug.log

>[snapscan] sense_handler: Hardware error. (0x00, 0x04)

according to my docs this means "scan module locked". You probably 
didn't remove the transportation lock. For Benq scanners it's a small 
switch on the bottom side of the scanner.

/Oliver



From msampson at ic.sunysb.edu  Tue Oct 19 20:39:52 2004
From: msampson at ic.sunysb.edu (Mbosowo I Sampson)
Date: Tue, 19 Oct 2004 15:39:52 -0400 (EDT)
Subject: [sane-devel] clean up usbsnoop logs
Message-ID: <Pine.SOC.4.60.0410191537500.23235@sparky.ic.sunysb.edu>

I would like to post some usbsnoop logs to get some feedback, but the 
files are huge. I was wondering what scripts people used to strip the big 
bulk transfers from their logs. I have a web account that only gives me 
20mb of space, but my average log size is about 30Megs.


 							Mboso



From gerard at gkall.hobby.nl  Tue Oct 19 22:55:01 2004
From: gerard at gkall.hobby.nl (gerard klaver)
Date: Tue, 19 Oct 2004 21:55:01 +0000
Subject: [sane-devel] clean up usbsnoop logs
In-Reply-To: <Pine.SOC.4.60.0410191537500.23235@sparky.ic.sunysb.edu>
References: <Pine.SOC.4.60.0410191537500.23235@sparky.ic.sunysb.edu>
Message-ID: <1098222901.1604.18.camel@gk-lex3>

On Tue, 2004-10-19 at 19:39, Mbosowo I Sampson wrote:
> I would like to post some usbsnoop logs to get some feedback, but the 
> files are huge. I was wondering what scripts people used to strip the big 
> bulk transfers from their logs. I have a web account that only gives me 
> 20mb of space, but my average log size is about 30Megs.
> 
> 
>  							Mboso


See SANE CVS experimental/usbsnoop for a awk script

See the SANE mailing list archive for a spike4.pl (perl script) file

See http://spca50x.sourceforge.net/spca50x.php?page=tools for another
perl script usbfilter.pl

-- 
----------
m.vr.gr.
Gerard Klaver




From till.kamppeter at gmx.net  Tue Oct 19 22:42:47 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Tue, 19 Oct 2004 23:42:47 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410192039.00356.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net> <41752CB2.8000504@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de>
Message-ID: <41758A57.8010401@gmx.net>

Oliver Schwartz wrote:
> Hi,
> 
> 
>>http://www.linuxprinting.org/till/tmp/eps2480debug.log
>>http://www.linuxprinting.org/till/tmp/eps2580debug.log
> 
> 
>>[snapscan] sense_handler: Hardware error. (0x00, 0x04)
> 
> 
> according to my docs this means "scan module locked". You probably 
> didn't remove the transportation lock. For Benq scanners it's a small 
> switch on the bottom side of the scanner.
> 
> /Oliver
> 

Thanks, on the 2480 this was really the case. On the 2580 it was already 
open.

Now I have tried to scan with the 2480 and I was even successful 
sometimes. When it worked the problem was that there were long delays 
until the scan to start (command line) or the GUI to appear (xsane). 
There were console messages like

-----------------------------------------------------------------------
[snapscan] Scanner warming up - waiting 9 seconds.
[snapscan] Scanner warming up - waiting 33 seconds.
[snapscan] Scanner warming up - waiting 9 seconds.
[snapscan] Scanner warming up - waiting 33 seconds.
-----------------------------------------------------------------------

-----------------------------------------------------------------------
scanimage --test
-----------------------------------------------------------------------

worked with the long delays before actual scanning as described above.

-----------------------------------------------------------------------
SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm 2> eps2480_2debug.log
-----------------------------------------------------------------------

produced a correct output. 1.pnm was a scan of the full scanning area. 
Again the long delays.

-----------------------------------------------------------------------
SANE_DEBUG_SNAPSCAN=255 xsane > eps2480_3debug.log 2>&1 &
-----------------------------------------------------------------------

Successful run of xsane. Nothing than one pre-scan of the full scanning 
area was done. In another run of xsane the GUI opened but pre-scanning 
did not work, real scanning worked then and pre-scanning only bafter the 
first real scan.

On all later attempts I got a segmentation fault when the GUI started to 
open. The command line was the following:

-----------------------------------------------------------------------
SANE_DEBUG_SNAPSCAN=255 xsane > eps2480_4debug.log 2>&1 &
-----------------------------------------------------------------------

Here are the URLs of the debug log files:

http://www.linuxprinting.org/till/tmp/eps2480_2debug.log
http://www.linuxprinting.org/till/tmp/eps2480_3debug.log
http://www.linuxprinting.org/till/tmp/eps2480_4debug.log

    Till



From till.kamppeter at gmx.net  Tue Oct 19 22:47:10 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Tue, 19 Oct 2004 23:47:10 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41758A57.8010401@gmx.net>
References: <41740B7F.5040507@gmx.net> <F639C1F8-214F-11D9-9436-000A957E40E8@khk.net> <41752CB2.8000504@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net>
Message-ID: <41758B5E.9040609@gmx.net>

Till Kamppeter wrote:
> -----------------------------------------------------------------------
> SANE_DEBUG_SNAPSCAN=255 xsane > eps2480_3debug.log 2>&1 &
> -----------------------------------------------------------------------
> 
> Successful run of xsane. Nothing than one pre-scan of the full scanning 
> area was done. In another run of xsane the GUI opened but pre-scanning 
> did not work, real scanning worked then and pre-scanning only bafter the 
> first real scan.
>

When the pre-scan failed, it said "Invalid argument".

    Till



From Oliver.Schwartz at gmx.de  Tue Oct 19 23:21:34 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Wed, 20 Oct 2004 00:21:34 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41758A57.8010401@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net>
Message-ID: <200410200021.37386.Oliver.Schwartz@gmx.de>

Hi,

> Thanks, on the 2480 this was really the case. On the 2580 it was
> already open.

It seems the 2580 behaves somewhat different, although it uses the 
same USB ID. Up to now I have no idea what's going wrong.

The log you sent for the 2580 indicates an error in 
snapscani_usb_open() which is only a small wrapper for 
sanei_usb_open(). Can you provide logs with SANE_DEBUG_SANEI_USB=255 
as well?

> Now I have tried to scan with the 2480 and I was even successful
> sometimes. When it worked the problem was that there were long
> delays until the scan to start (command line) or the GUI to appear
> (xsane). 

The delays are annoying, but it seems that all delays are requested by 
the scanner. You can try to reduce the number of retries for the 
test_unit_ready in snapscan-scsi.c, line 1008 and see if that works 
any better.

> On all later attempts I got a segmentation fault when the GUI
> started to open. The command line was the following:

There's nothing obvious in the log. Can you run xsane in gdb and 
create a stacktrace (command "bt" IIRC) after the crash?

/Oliver



From till.kamppeter at gmx.net  Wed Oct 20 00:59:05 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 01:59:05 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410200021.37386.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de>
Message-ID: <4175AA49.9040105@gmx.net>

Oliver Schwartz wrote:
> It seems the 2580 behaves somewhat different, although it uses the 
> same USB ID. Up to now I have no idea what's going wrong.
> 
> The log you sent for the 2580 indicates an error in 
> snapscani_usb_open() which is only a small wrapper for 
> sanei_usb_open(). Can you provide logs with SANE_DEBUG_SANEI_USB=255 
> as well?
>

Here we go:

http://www.linuxprinting.org/till/tmp/eps2580debug2.log

Coomand line was:

SANE_DEBUG_SANEI_USB=255 SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm 2> 
eps2580debug2.log

1.pnm had 0 bytes after running this command.

    Till


> 
>>Now I have tried to scan with the 2480 and I was even successful
>>sometimes. When it worked the problem was that there were long
>>delays until the scan to start (command line) or the GUI to appear
>>(xsane). 
> 
> 
> The delays are annoying, but it seems that all delays are requested by 
> the scanner. You can try to reduce the number of retries for the 
> test_unit_ready in snapscan-scsi.c, line 1008 and see if that works 
> any better.
> 
> 
>>On all later attempts I got a segmentation fault when the GUI
>>started to open. The command line was the following:
> 
> 
> There's nothing obvious in the log. Can you run xsane in gdb and 
> create a stacktrace (command "bt" IIRC) after the crash?
> 
> /Oliver
> 




From till.kamppeter at gmx.net  Wed Oct 20 01:00:36 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 02:00:36 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410200021.37386.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de>
Message-ID: <4175AAA4.1040805@gmx.net>

Oliver Schwartz wrote:
> 
> The delays are annoying, but it seems that all delays are requested by 
> the scanner. You can try to reduce the number of retries for the 
> test_unit_ready in snapscan-scsi.c, line 1008 and see if that works 
> any better.
>

Would this really help? The scanners are USB scanners and not SCSI scanners.

    Till




From till.kamppeter at gmx.net  Wed Oct 20 01:14:34 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 02:14:34 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410200021.37386.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de>
Message-ID: <4175ADEA.6050500@gmx.net>

Oliver Schwartz wrote:
>>On all later attempts I got a segmentation fault when the GUI
>>started to open. The command line was the following:
> 
> 
> There's nothing obvious in the log. Can you run xsane in gdb and 
> create a stacktrace (command "bt" IIRC) after the crash?
> 
> /Oliver
> 

Here is a stacktrace of a failed "scanimage --test":

--------------------------------------------------------------
[root at majax s]# gdb -c core.21805 /usr/bin/scanimage
GNU gdb 6.0-2mdk (Mandrake Linux)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-mandrake-linux-gnu"...Using host 
libthread_db library "/lib/tls/libthread_db.so.1".

Core was generated by `scanimage --test'.
Program terminated with signal 11, Segmentation fault.

warning: current_sos: Can't read pathname for load map: Input/output error

Reading symbols from /usr/lib/libsane.so.1...done.
Loaded symbols for /usr/lib/libsane.so.1
Reading symbols from /usr/lib/libusb-0.1.so.4...done.
Loaded symbols for /usr/lib/libusb-0.1.so.4
Reading symbols from /lib/libnsl.so.1...
Reading symbols from /usr/lib/debug//lib/libnsl-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /usr/lib/libjpeg.so.62...done.
Loaded symbols for /usr/lib/libjpeg.so.62
Reading symbols from /usr/lib/libieee1284.so.3...done.
Loaded symbols for /usr/lib/libieee1284.so.3
Reading symbols from /usr/lib/libgphoto2.so.2...done.
Loaded symbols for /usr/lib/libgphoto2.so.2
Reading symbols from /usr/lib/libgphoto2_port.so.0...done.
Loaded symbols for /usr/lib/libgphoto2_port.so.0
Reading symbols from /lib/libdl.so.2...
Reading symbols from /usr/lib/debug//lib/libdl-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/lib/libexif.so.9...done.
Loaded symbols for /usr/lib/libexif.so.9
Reading symbols from /lib/tls/libm.so.6...
Reading symbols from /usr/lib/debug//lib/tls/libm-2.3.3.so.debug...done.
---Type <return> to continue, or q <return> to quit---
done.
Loaded symbols for /lib/tls/libm.so.6
Reading symbols from /lib/tls/libc.so.6...
Reading symbols from /usr/lib/debug//lib/tls/libc-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/sane/libsane-hpaio.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpaio.so.1
Reading symbols from /usr/lib/libhpip.so.0...done.
Loaded symbols for /usr/lib/libhpip.so.0
Reading symbols from /lib/libnss_files.so.2...
Reading symbols from /usr/lib/debug//lib/libnss_files-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /usr/lib/sane/libsane-hpoj.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpoj.so.1
Reading symbols from /usr/lib/libptal.so.0...done.
Loaded symbols for /usr/lib/libptal.so.0
Reading symbols from /usr/lib/libhpojip.so.0...done.
Loaded symbols for /usr/lib/libhpojip.so.0
Reading symbols from /usr/lib/libsnmp.so.5...done.
Loaded symbols for /usr/lib/libsnmp.so.5
Reading symbols from /usr/lib/libcrypto.so.0.9.7...done.
Loaded symbols for /usr/lib/libcrypto.so.0.9.7
Reading symbols from /usr/lib/sane/libsane-v4l.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-v4l.so.1
Reading symbols from /usr/lib/sane/libsane-umax1220u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-umax1220u.so.1
Reading symbols from /usr/lib/sane/libsane-umax.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-umax.so.1
Reading symbols from /usr/lib/sane/libsane-u12.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-u12.so.1
Reading symbols from /usr/lib/sane/libsane-teco3.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco3.so.1
Reading symbols from /usr/lib/sane/libsane-teco2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco2.so.1
Reading symbols from /usr/lib/sane/libsane-teco1.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco1.so.1
Reading symbols from /usr/lib/sane/libsane-tamarack.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-tamarack.so.1
Reading symbols from /usr/lib/sane/libsane-sp15c.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sp15c.so.1
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/sane/libsane-snapscan.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-snapscan.so.1
Reading symbols from /usr/lib/sane/libsane-sm3600.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sm3600.so.1
Reading symbols from /usr/lib/sane/libsane-sharp.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sharp.so.1
Reading symbols from /usr/lib/sane/libsane-sceptre.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sceptre.so.1
Reading symbols from /usr/lib/sane/libsane-s9036.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-s9036.so.1
Reading symbols from /usr/lib/sane/libsane-ricoh.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ricoh.so.1
Reading symbols from /usr/lib/sane/libsane-qcam.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-qcam.so.1
Reading symbols from /usr/lib/sane/libsane-plustek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-plustek.so.1
Reading symbols from /usr/lib/sane/libsane-pie.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-pie.so.1
Reading symbols from /usr/lib/sane/libsane-nec.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-nec.so.1
Reading symbols from /usr/lib/sane/libsane-mustek_usb.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-mustek_usb.so.1
Reading symbols from /usr/lib/sane/libsane-mustek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-mustek.so.1
Reading symbols from /usr/lib/sane/libsane-microtek2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-microtek2.so.1
Reading symbols from /usr/lib/sane/libsane-microtek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-microtek.so.1
Reading symbols from /usr/lib/sane/libsane-matsushita.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-matsushita.so.1
Reading symbols from /usr/lib/sane/libsane-ma1509.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ma1509.so.1
Reading symbols from /usr/lib/sane/libsane-leo.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-leo.so.1
Reading symbols from /usr/lib/sane/libsane-ibm.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ibm.so.1
Reading symbols from /usr/lib/sane/libsane-hp5400.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp5400.so.1
Reading symbols from /usr/lib/sane/libsane-hp4200.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp4200.so.1
Reading symbols from /usr/lib/sane/libsane-hpsj5s.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpsj5s.so.1
Reading symbols from /usr/lib/sane/libsane-hp.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp.so.1
Reading symbols from /usr/lib/sane/libsane-gt68xx.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-gt68xx.so.1
Reading symbols from /usr/lib/sane/libsane-fujitsu.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-fujitsu.so.1
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/sane/libsane-epson.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-epson.so.1
Reading symbols from /usr/lib/sane/libsane-dmc.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-dmc.so.1
Reading symbols from /usr/lib/sane/libsane-coolscan2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-coolscan2.so.1
Reading symbols from /usr/lib/sane/libsane-coolscan.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-coolscan.so.1
Reading symbols from /usr/lib/sane/libsane-canon630u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-canon630u.so.1
Reading symbols from /usr/lib/sane/libsane-canon.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-canon.so.1
Reading symbols from /usr/lib/sane/libsane-bh.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-bh.so.1
Reading symbols from /usr/lib/sane/libsane-as6e.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-as6e.so.1
Reading symbols from /usr/lib/sane/libsane-artec_eplus48u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-artec_eplus48u.so.1
Reading symbols from /usr/lib/sane/libsane-artec.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-artec.so.1
Reading symbols from /usr/lib/sane/libsane-avision.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-avision.so.1
Reading symbols from /usr/lib/sane/libsane-apple.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-apple.so.1
Reading symbols from /usr/lib/sane/libsane-agfafocus.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-agfafocus.so.1
Reading symbols from /usr/lib/sane/libsane-abaton.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-abaton.so.1
Reading symbols from /usr/lib/sane/libsane-net.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-net.so.1
#0  _IO_default_xsputn (f=0xbf800654, data=0x30, n=1) at genops.c:442
442     {
(gdb) bt
#0  _IO_default_xsputn (f=0xbf800654, data=0x30, n=1) at genops.c:442
#1  0x4017dac1 in _IO_padn (fp=0xbf800654, pad=1076125664, count=1)
     at iopadn.c:68
#2  0x40163e18 in _IO_vfprintf (s=0xbf800654, format=0x4052d929 " 0x%02x",
     ap=0xbf80072c "") at vfprintf.c:1516
#3  0x4017eafb in _IO_vsprintf (
     ng=0xbf800740 " 0x?\026@\200\a\200)?@h\a\200\a",
     format=0x40245fe0 "", args=0x40245fe0 "") at iovsprintf.c:46
#4  0x4016c5db in sprintf (s=0x40245fe0 "", format=0x40245fe0 "")
     at sprintf.c:34
#5  0x4052002d in usb_debug_data () from /usr/lib/sane/libsane-snapscan.so.1
(gdb)
--------------------------------------------------------------

    Till



From till.kamppeter at gmx.net  Wed Oct 20 01:27:38 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 02:27:38 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410200021.37386.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de>
Message-ID: <4175B0FA.6030705@gmx.net>

Oliver Schwartz wrote:
> Hi,
> 
> 
>>Thanks, on the 2480 this was really the case. On the 2580 it was
>>already open.
> 
> 
> It seems the 2580 behaves somewhat different, although it uses the 
> same USB ID. Up to now I have no idea what's going wrong.
> 
> The log you sent for the 2580 indicates an error in 
> snapscani_usb_open() which is only a small wrapper for 
> sanei_usb_open(). Can you provide logs with SANE_DEBUG_SANEI_USB=255 
> as well?
> 
> 
>>Now I have tried to scan with the 2480 and I was even successful
>>sometimes. When it worked the problem was that there were long
>>delays until the scan to start (command line) or the GUI to appear
>>(xsane). 
> 
> 
> The delays are annoying, but it seems that all delays are requested by 
> the scanner. You can try to reduce the number of retries for the 
> test_unit_ready in snapscan-scsi.c, line 1008 and see if that works 
> any better.
> 
> 
>>On all later attempts I got a segmentation fault when the GUI
>>started to open. The command line was the following:
> 
> 
> There's nothing obvious in the log. Can you run xsane in gdb and 
> create a stacktrace (command "bt" IIRC) after the crash?
> 
> /Oliver
> 

Here a backtrace fron xsane with the 2480:

---------------------------------------------------------------------
[root at majax s]# gdb -c ~/core.10148 /usr/bin/xsane
GNU gdb 6.0-2mdk (Mandrake Linux)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-mandrake-linux-gnu"...
(no debugging symbols found)...Using host libthread_db library 
"/lib/tls/libthread_db.so.1".

Core was generated by `xsane'.
Program terminated with signal 11, Segmentation fault.

warning: current_sos: Can't read pathname for load map: Input/output error

Reading symbols from /usr/lib/libsane.so.1...done.
Loaded symbols for /usr/lib/libsane.so.1
Reading symbols from /usr/lib/libusb-0.1.so.4...done.
Loaded symbols for /usr/lib/libusb-0.1.so.4
Reading symbols from /lib/libnsl.so.1...
Reading symbols from /usr/lib/debug//lib/libnsl-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/tls/libm.so.6...
Reading symbols from /usr/lib/debug//lib/tls/libm-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/tls/libm.so.6
Reading symbols from /usr/lib/libjpeg.so.62...done.
Loaded symbols for /usr/lib/libjpeg.so.62
Reading symbols from /usr/lib/libieee1284.so.3...done.
Loaded symbols for /usr/lib/libieee1284.so.3
Reading symbols from /usr/lib/libgphoto2.so.2...done.
Loaded symbols for /usr/lib/libgphoto2.so.2
Reading symbols from /lib/libdl.so.2...
Reading symbols from /usr/lib/debug//lib/libdl-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libdl.so.2
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...done.
Loaded symbols for /usr/lib/libgtk-x11-2.0.so.0
Reading symbols from /usr/lib/libgdk-x11-2.0.so.0...done.
Loaded symbols for /usr/lib/libgdk-x11-2.0.so.0
Reading symbols from /usr/lib/libatk-1.0.so.0...done.
Loaded symbols for /usr/lib/libatk-1.0.so.0
Reading symbols from /usr/lib/libgdk_pixbuf-2.0.so.0...done.
Loaded symbols for /usr/lib/libgdk_pixbuf-2.0.so.0
Reading symbols from /usr/lib/libpangoxft-1.0.so.0...done.
Loaded symbols for /usr/lib/libpangoxft-1.0.so.0
Reading symbols from /usr/lib/libpangox-1.0.so.0...done.
Loaded symbols for /usr/lib/libpangox-1.0.so.0
Reading symbols from /usr/lib/libpango-1.0.so.0...done.
Loaded symbols for /usr/lib/libpango-1.0.so.0
Reading symbols from /usr/lib/libgobject-2.0.so.0...done.
Loaded symbols for /usr/lib/libgobject-2.0.so.0
Reading symbols from /usr/lib/libgmodule-2.0.so.0...done.
Loaded symbols for /usr/lib/libgmodule-2.0.so.0
Reading symbols from /usr/lib/libglib-2.0.so.0...done.
Loaded symbols for /usr/lib/libglib-2.0.so.0
Reading symbols from /usr/lib/libpng.so.3...done.
Loaded symbols for /usr/lib/libpng.so.3
Reading symbols from /usr/lib/libtiff.so.3...done.
Loaded symbols for /usr/lib/libtiff.so.3
Reading symbols from /lib/libz.so.1...done.
Loaded symbols for /lib/libz.so.1
Reading symbols from /lib/tls/libc.so.6...
Reading symbols from /usr/lib/debug//lib/tls/libc-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/libgphoto2_port.so.0...done.
Loaded symbols for /usr/lib/libgphoto2_port.so.0
Reading symbols from /usr/lib/libexif.so.9...done.
Loaded symbols for /usr/lib/libexif.so.9
Reading symbols from /usr/X11R6/lib/libX11.so.6...done.
Loaded symbols for /usr/X11R6/lib/libX11.so.6
Reading symbols from /usr/X11R6/lib/libXrandr.so.2...done.
Loaded symbols for /usr/X11R6/lib/libXrandr.so.2
Reading symbols from /usr/X11R6/lib/libXi.so.6...done.
Loaded symbols for /usr/X11R6/lib/libXi.so.6
Reading symbols from /usr/X11R6/lib/libXinerama.so.1...done.
Loaded symbols for /usr/X11R6/lib/libXinerama.so.1
Reading symbols from /usr/X11R6/lib/libXext.so.6...done.
Loaded symbols for /usr/X11R6/lib/libXext.so.6
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/X11R6/lib/libXft.so.2...done.
Loaded symbols for /usr/X11R6/lib/libXft.so.2
Reading symbols from /usr/lib/libfreetype.so.6...done.
Loaded symbols for /usr/lib/libfreetype.so.6
Reading symbols from /usr/lib/libfontconfig.so.1...done.
Loaded symbols for /usr/lib/libfontconfig.so.1
Reading symbols from /usr/X11R6/lib/libXcursor.so.1...done.
Loaded symbols for /usr/X11R6/lib/libXcursor.so.1
Reading symbols from /usr/X11R6/lib/libXrender.so.1...done.
Loaded symbols for /usr/X11R6/lib/libXrender.so.1
Reading symbols from /usr/lib/libpangoft2-1.0.so.0...done.
Loaded symbols for /usr/lib/libpangoft2-1.0.so.0
Reading symbols from /usr/lib/libexpat.so.0...done.
Loaded symbols for /usr/lib/libexpat.so.0
Reading symbols from 
/usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2...done.
Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2
Reading symbols from /lib/libnss_files.so.2...
Reading symbols from /usr/lib/debug//lib/libnss_files-2.3.3.so.debug...done.
done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /usr/lib/gconv/ISO8859-1.so...
Reading symbols from 
/usr/lib/debug//usr/lib/gconv/ISO8859-1.so.debug...done.
done.
Loaded symbols for /usr/lib/gconv/ISO8859-1.so
Reading symbols from /usr/lib/gtk-2.0/2.4.0/engines/libgalaxy.so...done.
Loaded symbols for /usr/lib/gtk-2.0/2.4.0/engines/libgalaxy.so
Reading symbols from 
/usr/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-xpm.so...
done.
Loaded symbols for /usr/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-xpm.so
Reading symbols from /usr/lib/pango/1.4.0/modules/pango-basic-fc.so...done.
Loaded symbols for /usr/lib/pango/1.4.0/modules/pango-basic-fc.so
Reading symbols from /usr/lib/sane/libsane-hpaio.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpaio.so.1
Reading symbols from /usr/lib/libhpip.so.0...done.
Loaded symbols for /usr/lib/libhpip.so.0
Reading symbols from /usr/lib/sane/libsane-hpoj.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpoj.so.1
Reading symbols from /usr/lib/libptal.so.0...done.
Loaded symbols for /usr/lib/libptal.so.0
Reading symbols from /usr/lib/libhpojip.so.0...done.
Loaded symbols for /usr/lib/libhpojip.so.0
Reading symbols from /usr/lib/libsnmp.so.5...done.
Loaded symbols for /usr/lib/libsnmp.so.5
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/libcrypto.so.0.9.7...done.
Loaded symbols for /usr/lib/libcrypto.so.0.9.7
Reading symbols from /usr/lib/sane/libsane-v4l.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-v4l.so.1
Reading symbols from /usr/lib/sane/libsane-umax1220u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-umax1220u.so.1
Reading symbols from /usr/lib/sane/libsane-umax.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-umax.so.1
Reading symbols from /usr/lib/sane/libsane-u12.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-u12.so.1
Reading symbols from /usr/lib/sane/libsane-teco3.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco3.so.1
Reading symbols from /usr/lib/sane/libsane-teco2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco2.so.1
Reading symbols from /usr/lib/sane/libsane-teco1.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-teco1.so.1
Reading symbols from /usr/lib/sane/libsane-tamarack.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-tamarack.so.1
Reading symbols from /usr/lib/sane/libsane-sp15c.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sp15c.so.1
Reading symbols from /usr/lib/sane/libsane-snapscan.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-snapscan.so.1
Reading symbols from /usr/lib/sane/libsane-sm3600.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sm3600.so.1
Reading symbols from /usr/lib/sane/libsane-sharp.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sharp.so.1
Reading symbols from /usr/lib/sane/libsane-sceptre.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-sceptre.so.1
Reading symbols from /usr/lib/sane/libsane-s9036.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-s9036.so.1
Reading symbols from /usr/lib/sane/libsane-ricoh.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ricoh.so.1
Reading symbols from /usr/lib/sane/libsane-qcam.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-qcam.so.1
Reading symbols from /usr/lib/sane/libsane-plustek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-plustek.so.1
Reading symbols from /usr/lib/sane/libsane-pie.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-pie.so.1
Reading symbols from /usr/lib/sane/libsane-nec.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-nec.so.1
Reading symbols from /usr/lib/sane/libsane-mustek_usb.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-mustek_usb.so.1
Reading symbols from /usr/lib/sane/libsane-mustek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-mustek.so.1
Reading symbols from /usr/lib/sane/libsane-microtek2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-microtek2.so.1
Reading symbols from /usr/lib/sane/libsane-microtek.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-microtek.so.1
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/sane/libsane-matsushita.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-matsushita.so.1
Reading symbols from /usr/lib/sane/libsane-ma1509.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ma1509.so.1
Reading symbols from /usr/lib/sane/libsane-leo.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-leo.so.1
Reading symbols from /usr/lib/sane/libsane-ibm.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-ibm.so.1
Reading symbols from /usr/lib/sane/libsane-hp5400.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp5400.so.1
Reading symbols from /usr/lib/sane/libsane-hp4200.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp4200.so.1
Reading symbols from /usr/lib/sane/libsane-hpsj5s.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hpsj5s.so.1
Reading symbols from /usr/lib/sane/libsane-hp.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-hp.so.1
Reading symbols from /usr/lib/sane/libsane-gt68xx.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-gt68xx.so.1
Reading symbols from /usr/lib/sane/libsane-fujitsu.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-fujitsu.so.1
Reading symbols from /usr/lib/sane/libsane-epson.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-epson.so.1
Reading symbols from /usr/lib/sane/libsane-dmc.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-dmc.so.1
Reading symbols from /usr/lib/sane/libsane-coolscan2.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-coolscan2.so.1
Reading symbols from /usr/lib/sane/libsane-coolscan.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-coolscan.so.1
Reading symbols from /usr/lib/sane/libsane-canon630u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-canon630u.so.1
Reading symbols from /usr/lib/sane/libsane-canon.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-canon.so.1
Reading symbols from /usr/lib/sane/libsane-bh.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-bh.so.1
Reading symbols from /usr/lib/sane/libsane-as6e.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-as6e.so.1
Reading symbols from /usr/lib/sane/libsane-artec_eplus48u.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-artec_eplus48u.so.1
Reading symbols from /usr/lib/sane/libsane-artec.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-artec.so.1
Reading symbols from /usr/lib/sane/libsane-avision.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-avision.so.1
Reading symbols from /usr/lib/sane/libsane-apple.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-apple.so.1
Reading symbols from /usr/lib/sane/libsane-agfafocus.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-agfafocus.so.1
Reading symbols from /usr/lib/sane/libsane-abaton.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-abaton.so.1
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/sane/libsane-net.so.1...done.
Loaded symbols for /usr/lib/sane/libsane-net.so.1
#0  0x40c9ab67 in sanei_constrain_value ()
    from /usr/lib/sane/libsane-snapscan.so.1
(gdb) bt
#0  0x40c9ab67 in sanei_constrain_value ()
    from /usr/lib/sane/libsane-snapscan.so.1
#1  0x0823a6a8 in ?? ()
#2  0x0822bc10 in ?? ()
#3  0xbfffe01c in ?? ()
#4  0x40c909a1 in sanei_debug_snapscan_call ()
    from /usr/lib/sane/libsane-snapscan.so.1
#5  0x0000001e in ?? ()
(gdb)
---------------------------------------------------------------------

    Till



From rene at exactcode.de  Wed Oct 20 07:19:41 2004
From: rene at exactcode.de (=?ISO-8859-1?Q?Ren=E9_Rebe?=)
Date: Wed, 20 Oct 2004 08:19:41 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
In-Reply-To: <20041017181209.GH12072@meier-geinitz.de>
References: <20041017181209.GH12072@meier-geinitz.de>
Message-ID: <4176037D.3050307@exactcode.de>

Hi Henning,

Henning Meier-Geinitz wrote:

> Feature freeze for sane-backends 1.0.15 is now active. That means,
> that now new backend or new features for existing backends should be
> committed to CVS. Bug fixes, documentation and translation updates are
> ok.
> 
> Timetable:
> 2004-10-31 Code freeze (snapshot)
> 2004-11-07 Release

Sorry for always beeing late due to workload here ... :-(

I have some more avision updates in the queue, mostly fixes and cleanups 
- but also the button readout code, which would be a new feature ... 
Should I leave it out and seperate the rest of the code, or are those 
few button code lines tiny enought for a "just commit it"? ;-)

I guess committing the normal code changes today is ok?

Sincerely,

-- 
Ren? Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
             +49 (0)30  255 897 45



From Oliver.Schwartz at gmx.de  Wed Oct 20 18:46:06 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Wed, 20 Oct 2004 19:46:06 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <4175AAA4.1040805@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <4175AAA4.1040805@gmx.net>
Message-ID: <200410201946.07792.Oliver.Schwartz@gmx.de>

On Wednesday 20 October 2004 02.00, Till Kamppeter wrote:
> Oliver Schwartz wrote:
> > The delays are annoying, but it seems that all delays are
> > requested by the scanner. You can try to reduce the number of
> > retries for the test_unit_ready in snapscan-scsi.c, line 1008 and
> > see if that works any better.
>
> Would this really help? The scanners are USB scanners and not SCSI
> scanners.

Yes - some of routines in snapscan-scsi.c are used for usb as well. 

/Oliver



From henning at meier-geinitz.de  Wed Oct 20 18:44:22 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 20 Oct 2004 19:44:22 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
In-Reply-To: <4176037D.3050307@exactcode.de>
References: <20041017181209.GH12072@meier-geinitz.de> <4176037D.3050307@exactcode.de>
Message-ID: <20041020174422.GA7538@meier-geinitz.de>

Hi,

On Wed, Oct 20, 2004 at 08:19:41AM +0200, Ren? Rebe wrote:
> I have some more avision updates in the queue, mostly fixes and cleanups 
> - but also the button readout code, which would be a new feature ... 
> Should I leave it out and seperate the rest of the code, or are those 
> few button code lines tiny enought for a "just commit it"? ;-)

If it's really only a few lines and yiu are sure that these lines
don't break anything I guess it's ok.

Bye,
  Henning



From Oliver.Schwartz at gmx.de  Wed Oct 20 19:51:52 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Wed, 20 Oct 2004 20:51:52 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <4175AA49.9040105@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <4175AA49.9040105@gmx.net>
Message-ID: <200410202051.55687.Oliver.Schwartz@gmx.de>

Hi,

> http://www.linuxprinting.org/till/tmp/eps2580debug2.log
>
> Coomand line was:
>
> SANE_DEBUG_SANEI_USB=255 SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm
> 2> eps2580debug2.log

> [snapscan] snapscani_usb_open(libusb:001:037)
> [sanei_usb] sanei_usb_open: trying to open device `libusb:001:037'
> USB error: failed to open /proc/bus/usb/001/037: No such file or
> directory 
> [sanei_usb] sanei_usb_open: can't open device `libusb:001:037': No
> such file or directory 

hm - it seems the USB device disappeared during firmware upload. That 
certainly shouldn't happen, but there's little that the backend can 
do about it.

I'm not sure if esfw41.bin is the correct file for the 2580 at all. 
Maybe it needs a different firmware file. Is there another one 
installed with the windows driver?

/Oliver



From Oliver.Schwartz at gmx.de  Wed Oct 20 19:53:53 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Wed, 20 Oct 2004 20:53:53 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <4175ADEA.6050500@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <4175ADEA.6050500@gmx.net>
Message-ID: <200410202053.56532.Oliver.Schwartz@gmx.de>

Hi,

the backtraces are quite obscure. Is there any chance that you have 
two versions of SANE installed on your system (e.g. one 
in /usr/lib/sane, another one in /usr/local/lib/sane)?

/Oliver



From till.kamppeter at gmx.net  Wed Oct 20 21:01:24 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 22:01:24 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410202053.56532.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <4175ADEA.6050500@gmx.net> <200410202053.56532.Oliver.Schwartz@gmx.de>
Message-ID: <4176C414.10009@gmx.net>

Impossible, I have installed SANE always by RPM, for a new version I 
have rebuilt the RPM on the compiling machine and then updated the RPM 
on my testing machine.

    Till


Oliver Schwartz wrote:
> Hi,
> 
> the backtraces are quite obscure. Is there any chance that you have 
> two versions of SANE installed on your system (e.g. one 
> in /usr/lib/sane, another one in /usr/local/lib/sane)?
> 
> /Oliver
> 




From till.kamppeter at gmx.net  Wed Oct 20 21:04:09 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Wed, 20 Oct 2004 22:04:09 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410202051.55687.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <4175AA49.9040105@gmx.net> <200410202051.55687.Oliver.Schwartz@gmx.de>
Message-ID: <4176C4B9.40708@gmx.net>

There was only this one .bin file in the Windows driver package. The 
whole Windows driver package is exactly the same for both models.

When I llok at the scanners itself, the base parts are identical (only 
exception the "2480" and "2580" printed on them. Only the lids are 
different, the 2480 with only a transparency light and the 2580 with 
automatic film feeder (for 35-mm film).

    Till


Oliver Schwartz wrote:
> Hi,
> 
> 
>>http://www.linuxprinting.org/till/tmp/eps2580debug2.log
>>
>>Coomand line was:
>>
>>SANE_DEBUG_SANEI_USB=255 SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm
>>2> eps2580debug2.log
> 
> 
>>[snapscan] snapscani_usb_open(libusb:001:037)
>>[sanei_usb] sanei_usb_open: trying to open device `libusb:001:037'
>>USB error: failed to open /proc/bus/usb/001/037: No such file or
>>directory 
>>[sanei_usb] sanei_usb_open: can't open device `libusb:001:037': No
>>such file or directory 
> 
> 
> hm - it seems the USB device disappeared during firmware upload. That 
> certainly shouldn't happen, but there's little that the backend can 
> do about it.
> 
> I'm not sure if esfw41.bin is the correct file for the 2580 at all. 
> Maybe it needs a different firmware file. Is there another one 
> installed with the windows driver?
> 
> /Oliver
> 




From henning at meier-geinitz.de  Wed Oct 20 20:43:26 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 20 Oct 2004 21:43:26 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410200021.37386.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410192039.00356.Oliver.Schwartz@gmx.de> <41758A57.8010401@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de>
Message-ID: <20041020194326.GF7538@meier-geinitz.de>

Hi,

On Wed, Oct 20, 2004 at 12:21:34AM +0200, Oliver Schwartz wrote:
> There's nothing obvious in the log. Can you run xsane in gdb and 
> create a stacktrace (command "bt" IIRC) after the crash?

Why does the frontend want to set the gray gamma table to (nil)?

[snapscan] sane_snapscan_control_option (0x823a6b0, 24, 1, (nil), 0xbfffdffc)

Maybe I don't understand something here but that looks strange.

Bye,
  Henning



From boldra at tiscali.it  Thu Oct 21 08:32:31 2004
From: boldra at tiscali.it (Enrico Boldrini)
Date: Thu, 21 Oct 2004 09:32:31 +0200
Subject: [sane-devel] homepage for "artiscan 9600" scanner
Message-ID: <1098343951.968.10.camel@vicious>

>I the full name of that scanner "Tamarack Artiscan 9600" or "Tamarack
>Artiscan 9600 pro 36"?
>
>Bye,
>  Henning

Theese are two models of the scanner. The scanner we'll try to support
first will be Tamarack Artiscan 9600 pro 36.

I use this message also to inform that:
/!\ The project is moved to http://www.autistici.org/tamarhack /1\

Bye, Enrico




From Oliver.Schwartz at gmx.de  Thu Oct 21 23:59:47 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Fri, 22 Oct 2004 00:59:47 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <20041020194326.GF7538@meier-geinitz.de>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <20041020194326.GF7538@meier-geinitz.de>
Message-ID: <200410220059.49524.Oliver.Schwartz@gmx.de>

Hi,

> Why does the frontend want to set the gray gamma table to (nil)?
>
> [snapscan] sane_snapscan_control_option (0x823a6b0, 24, 1, (nil),
> 0xbfffdffc)
>
> Maybe I don't understand something here but that looks strange.

This seems to cause the crash (which is not that surprising). For some 
reason the frontend passes an invalid pointer.

Can you try another frontend (e.g. xscanimage)? It may also help to 
delete any xsane preferences (stored in ~/.sane/xsane IIRC).

/Oliver



From till.kamppeter at gmx.net  Fri Oct 22 17:03:34 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Fri, 22 Oct 2004 18:03:34 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <200410220059.49524.Oliver.Schwartz@gmx.de>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <20041020194326.GF7538@meier-geinitz.de> <200410220059.49524.Oliver.Schwartz@gmx.de>
Message-ID: <41792F56.6090307@gmx.net>

Oliver Schwartz wrote:
> Hi,
> 
> 
>>Why does the frontend want to set the gray gamma table to (nil)?
>>
>>[snapscan] sane_snapscan_control_option (0x823a6b0, 24, 1, (nil),
>>0xbfffdffc)
>>
>>Maybe I don't understand something here but that looks strange.
> 
> 
> This seems to cause the crash (which is not that surprising). For some 
> reason the frontend passes an invalid pointer.
> 

I have tried now with xscanimage and have interesting results:

The 2480 and 2580 consist of a lower part with the glass and scanning 
head and a lid with the transparency unit. The lower parts of both are 
absolutely identical, including the USB vendor/product IDs. The 
difference between the 2480 and 2580 is made up by the lids. The lid of 
the 2480 has a simple light which is turned on in transparency mode. You 
insert the film or slides in a special frame and put this on the glass, 
so film or slide are placed under the light and parallel to the 
scanner's borders. The 2580 has an automatic film feeder. You remove the 
white background from the inner side of the lid, close the lid and open 
a little door on the upper side of the lid. There you insert a piece of 
35-mm film and the scanner pulls it in automatically. For slides there 
is a frame for the scanner glass again, but a different one.

In principle the scanners work with SANE and the "snapscan" driver, but 
there are some problems:

- You need the scanner's firmware, as for all scanners used with the 
"snapscan" driver.

- There are long delays between starting the scanner software and the 
GUI opening or the scan beginning. Messages like

[snapscan] Scanner warming up - waiting 33 seconds

appear on the console from where the scanning frontend was started.

- The biggest problem is that the USB device address (like 
libusb:001:015) changes when the firmware is uploaded, it seems that 
after the upload the scanner is disconnected and then reconnected and so 
it gets a new ID.

This means that the very first start of a frontend (after 
connecting/turning on the scanner) lets the GUI open, but trying to 
preview of to scan gives "Invalid argument". Comparing the output of 
"lsusb" reveals that the USB device address changed at the moment where 
the firmware upload finished. On subsequent runs of scanning frontends 
the firmware is not uploaded again and so the address does not change. 
So one can scan when one closes the frontend and opens it again. Perhaps 
one should do modifications on the "snapscan" backend to take the 
reconnection/address change into account.

- The lid of the 2580 is not compatible with SANE. If the lid is in use 
with any of the two lower parts (2480 and 2580) the preview does not 
work. The head moves shortly and the preview is a stripy dirty white. 
Normal scanning does work at least in flatbed mode. Switching to the 
transparency unit makes the frontend freezing.

Both lower parts work without problems when the lid of the 2480 or no 
lid at all is connected. With the lid of the 2480 one can switch to the 
transparency unit and scan transparent documets correctly. Without lid 
the button for the transparency unit simply does not appear.

    Till


> Can you try another frontend (e.g. xscanimage)? It may also help to 
> delete any xsane preferences (stored in ~/.sane/xsane IIRC).
> 
> /Oliver
> 




From till.kamppeter at gmx.net  Fri Oct 22 19:41:29 2004
From: till.kamppeter at gmx.net (Till Kamppeter)
Date: Fri, 22 Oct 2004 20:41:29 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41792F56.6090307@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410200021.37386.Oliver.Schwartz@gmx.de> <20041020194326.GF7538@meier-geinitz.de> <200410220059.49524.Oliver.Schwartz@gmx.de> <41792F56.6090307@gmx.net>
Message-ID: <41795459.8090000@gmx.net>

Here are some more debug logs, all for the 2580 (lower part with film 
feeder lid):

http://www.linuxprinting.org/till/tmp/eps2580debug3.log
http://www.linuxprinting.org/till/tmp/eps2580debug4.log
http://www.linuxprinting.org/till/tmp/eps2580debug5.log

To get these logs the scanner was connected and turned on and then the 
following command lines executed:

------------------------------------------------------------------------
[root at majax g]# SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm 
2>eps2580debug3.log
[root at majax g]# ll 1.pnm
-rw-r--r--  1 root root 0 Oct 22 13:50 1.pnm
[root at majax g]# lsusb
Bus 001 Device 020: ID 04b8:0121 Seiko Epson Corp.
Bus 001 Device 003: ID 0451:2077 Texas Instruments, Inc. TUSB2077 Hub
Bus 001 Device 002: ID 04f9:0016 Brother Industries, Ltd
Bus 001 Device 001: ID 0000:0000
[root at majax g]# SANE_DEBUG_SNAPSCAN=255 scanimage > 1.pnm 
2>eps2580debug4.log
[root at majax g]# ll 1.pnm
-rw-r--r--  1 root root 26849629 Oct 22 13:58 1.pnm
[root at majax g]# SANE_DEBUG_SNAPSCAN=255 xscanimage >eps2580debug5.log 2>&1
------------------------------------------------------------------------

The scanimage commands are non-interactive and only on the second the 
scan succeeded (file contains the correct image). The first did not 
succeed because there the firmware was uploaded and the scanner 
reconnected with a new address as told already in the previous posting. 
The third command was an interactive xscanimage session. The following 
steps were done:

1. Normal preview, failed as described in the previous posting: fast 
sweep of scan head, no correct image.

2. Scan of a very small part of the image area. Succeeded, file contains 
expected image.

3. Preview with TPU, took VERY long until it started, head sweep sounded 
correct, but color components seem to be misaligned.

4. Scan with TPU, took long but seems correct.

5. Back to normal flatbed mode: Preview scan still broken.

6. Normal scan of full area at 100 dpi absolutely correct.]

    Till



Till Kamppeter wrote:
> Oliver Schwartz wrote:
> 
>> Hi,
>>
>>
>>> Why does the frontend want to set the gray gamma table to (nil)?
>>>
>>> [snapscan] sane_snapscan_control_option (0x823a6b0, 24, 1, (nil),
>>> 0xbfffdffc)
>>>
>>> Maybe I don't understand something here but that looks strange.
>>
>>
>>
>> This seems to cause the crash (which is not that surprising). For some 
>> reason the frontend passes an invalid pointer.
>>
> 
> I have tried now with xscanimage and have interesting results:
> 
> The 2480 and 2580 consist of a lower part with the glass and scanning 
> head and a lid with the transparency unit. The lower parts of both are 
> absolutely identical, including the USB vendor/product IDs. The 
> difference between the 2480 and 2580 is made up by the lids. The lid of 
> the 2480 has a simple light which is turned on in transparency mode. You 
> insert the film or slides in a special frame and put this on the glass, 
> so film or slide are placed under the light and parallel to the 
> scanner's borders. The 2580 has an automatic film feeder. You remove the 
> white background from the inner side of the lid, close the lid and open 
> a little door on the upper side of the lid. There you insert a piece of 
> 35-mm film and the scanner pulls it in automatically. For slides there 
> is a frame for the scanner glass again, but a different one.
> 
> In principle the scanners work with SANE and the "snapscan" driver, but 
> there are some problems:
> 
> - You need the scanner's firmware, as for all scanners used with the 
> "snapscan" driver.
> 
> - There are long delays between starting the scanner software and the 
> GUI opening or the scan beginning. Messages like
> 
> [snapscan] Scanner warming up - waiting 33 seconds
> 
> appear on the console from where the scanning frontend was started.
> 
> - The biggest problem is that the USB device address (like 
> libusb:001:015) changes when the firmware is uploaded, it seems that 
> after the upload the scanner is disconnected and then reconnected and so 
> it gets a new ID.
> 
> This means that the very first start of a frontend (after 
> connecting/turning on the scanner) lets the GUI open, but trying to 
> preview of to scan gives "Invalid argument". Comparing the output of 
> "lsusb" reveals that the USB device address changed at the moment where 
> the firmware upload finished. On subsequent runs of scanning frontends 
> the firmware is not uploaded again and so the address does not change. 
> So one can scan when one closes the frontend and opens it again. Perhaps 
> one should do modifications on the "snapscan" backend to take the 
> reconnection/address change into account.
> 
> - The lid of the 2580 is not compatible with SANE. If the lid is in use 
> with any of the two lower parts (2480 and 2580) the preview does not 
> work. The head moves shortly and the preview is a stripy dirty white. 
> Normal scanning does work at least in flatbed mode. Switching to the 
> transparency unit makes the frontend freezing.
> 
> Both lower parts work without problems when the lid of the 2480 or no 
> lid at all is connected. With the lid of the 2480 one can switch to the 
> transparency unit and scan transparent documets correctly. Without lid 
> the button for the transparency unit simply does not appear.
> 
>    Till
> 
> 
>> Can you try another frontend (e.g. xscanimage)? It may also help to 
>> delete any xsane preferences (stored in ~/.sane/xsane IIRC).
>>
>> /Oliver
>>
> 
> 




From haantc502 at sneakemail.com  Fri Oct 22 20:26:14 2004
From: haantc502 at sneakemail.com (Brad Johnson)
Date: 22 Oct 2004 19:26:14 -0000
Subject: [sane-devel] Vertical Comb effect on Epson 2580 scan at 2400 dpi
Message-ID: <11334-94068@sneakemail.com>

Hello,



I have an Epson Perfection 2580 Photo and when scanning at 50-1200 dpi I get good scans, but when scanning at 2400 dpi I get a vertical comb effect. Every other line is shifted 4 pixels down.



So when I'm expecting a set of pixels like this:

.....

.....

OOOOO

OOOOO

OOOOO

OOOOO



This is what I get:

.....

O.O.O

O.O.O

O.O.O

O.O.O

OOOOO



I am running sane built from today's CVS.



I know support for this scanner is still being worked on, but any ideas?



thanks,

Brad Johnson



From jb at jblache.org  Fri Oct 22 21:40:47 2004
From: jb at jblache.org (Julien BLACHE)
Date: Fri, 22 Oct 2004 22:40:47 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for
 testing
In-Reply-To: <41792F56.6090307@gmx.net> (Till Kamppeter's message of "Fri,
 22 Oct 2004 18:03:34 +0200")
References: <41740B7F.5040507@gmx.net>
	<200410200021.37386.Oliver.Schwartz@gmx.de>
	<20041020194326.GF7538@meier-geinitz.de>
	<200410220059.49524.Oliver.Schwartz@gmx.de> <41792F56.6090307@gmx.net>
Message-ID: <87vfd2jxkg.fsf@frigate.technologeek.org>

Till Kamppeter <till.kamppeter at gmx.net> wrote:

> - The biggest problem is that the USB device address (like
> libusb:001:015) changes when the firmware is uploaded, it seems that
> after the upload the scanner is disconnected and then reconnected and
> so it gets a new ID.

Doesn't happen here with a 2480.

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb at jblache.org>                                  GPG KeyID 0xF5D65169



From jb at jblache.org  Fri Oct 22 21:40:20 2004
From: jb at jblache.org (Julien BLACHE)
Date: Fri, 22 Oct 2004 22:40:20 +0200
Subject: [sane-devel] Vertical Comb effect on Epson 2580 scan at 2400
 dpi
In-Reply-To: <11334-94068@sneakemail.com> (Brad Johnson's message of "22 Oct
 2004 19:26:14 -0000")
References: <11334-94068@sneakemail.com>
Message-ID: <87zn2ejxl7.fsf@frigate.technologeek.org>

"Brad Johnson" <haantc502 at sneakemail.com> wrote:

Hi,

> I have an Epson Perfection 2580 Photo and when scanning at 50-1200 dpi
> I get good scans, but when scanning at 2400 dpi I get a vertical comb
> effect. Every other line is shifted 4 pixels down.

This is a known issue and is due to the scanner design.

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb at jblache.org>                                  GPG KeyID 0xF5D65169



From Oliver.Schwartz at gmx.de  Fri Oct 22 21:41:30 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Fri, 22 Oct 2004 22:41:30 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <41792F56.6090307@gmx.net>
References: <41740B7F.5040507@gmx.net> <200410220059.49524.Oliver.Schwartz@gmx.de> <41792F56.6090307@gmx.net>
Message-ID: <200410222241.32972.Oliver.Schwartz@gmx.de>

Hi,

> - There are long delays between starting the scanner software and
> the GUI opening or the scan beginning. Messages like
>
> [snapscan] Scanner warming up - waiting 33 seconds
>
> appear on the console from where the scanning frontend was started.

Did you try reducing the retry counter yet?

> - The biggest problem is that the USB device address (like
> libusb:001:015) changes when the firmware is uploaded, it seems
> that after the upload the scanner is disconnected and then
> reconnected and so it gets a new ID.
>
> This means that the very first start of a frontend (after
> connecting/turning on the scanner) lets the GUI open, but trying to
> preview of to scan gives "Invalid argument". Comparing the output
> of "lsusb" reveals that the USB device address changed at the
> moment where the firmware upload finished. On subsequent runs of
> scanning frontends the firmware is not uploaded again and so the
> address does not change. So one can scan when one closes the
> frontend and opens it again. Perhaps one should do modifications on
> the "snapscan" backend to take the reconnection/address change into
> account.

It's probably easier to set up a hotplug script that downloads the 
firmware once the scanner is connected. In principle this is possible 
using a modified "acerfirm" from the snapscan website. The biggest 
problem is that acerfirm doesn't work with libusb yet.

It would require a lot of tweakings and workarounds to handle changing 
device files within the SANE architecture framework.

> - The lid of the 2580 is not compatible with SANE. If the lid is in
> use with any of the two lower parts (2480 and 2580) the preview
> does not work. The head moves shortly and the preview is a stripy
> dirty white. Normal scanning does work at least in flatbed mode.
> Switching to the transparency unit makes the frontend freezing.
>
> Both lower parts work without problems when the lid of the 2480 or
> no lid at all is connected. With the lid of the 2480 one can switch
> to the transparency unit and scan transparent documets correctly.
> Without lid the button for the transparency unit simply does not
> appear.

If there are fundamental differences in the protocol it would help to 
get usb trace from the windows driver.

/Oliver



From Oliver.Schwartz at gmx.de  Fri Oct 22 21:50:18 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Fri, 22 Oct 2004 22:50:18 +0200
Subject: [sane-devel] Vertical Comb effect on Epson 2580 scan at 2400 dpi
In-Reply-To: <11334-94068@sneakemail.com>
References: <11334-94068@sneakemail.com>
Message-ID: <200410222250.19605.Oliver.Schwartz@gmx.de>

Hi,

> I have an Epson Perfection 2580 Photo and when scanning at 50-1200
> dpi I get good scans, but when scanning at 2400 dpi I get a
> vertical comb effect. Every other line is shifted 4 pixels down.
>
> I know support for this scanner is still being worked on, but any
> ideas?

It's a known issue for both the 2480 and the 2580. See 
https://alioth.debian.org/tracker/index.php?func=detail&aid=300756&group_id=30186&atid=410366 

To be honest I've no idea how to fix it. A trace of the USB 
communication in windows may be helpful.

/Oliver



From Oliver.Schwartz at gmx.de  Fri Oct 22 21:51:30 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Fri, 22 Oct 2004 22:51:30 +0200
Subject: [sane-devel] I have the Epson Perfection 2480 and 2580 for testing
In-Reply-To: <87vfd2jxkg.fsf@frigate.technologeek.org>
References: <41740B7F.5040507@gmx.net> <41792F56.6090307@gmx.net> <87vfd2jxkg.fsf@frigate.technologeek.org>
Message-ID: <200410222251.31537.Oliver.Schwartz@gmx.de>

Hi,

> > - The biggest problem is that the USB device address (like
> > libusb:001:015) changes when the firmware is uploaded, it seems
> > that after the upload the scanner is disconnected and then
> > reconnected and so it gets a new ID.
>
> Doesn't happen here with a 2480.

This may depend on the setup (kernel version, hotplug agent used).

/Oliver



From rene at exactcode.de  Thu Oct 21 11:45:37 2004
From: rene at exactcode.de (=?ISO-8859-1?Q?Ren=E9_Rebe?=)
Date: Thu, 21 Oct 2004 12:45:37 +0200
Subject: [sane-devel] Feature freeze for sane-backends 1.0.15
In-Reply-To: <20041020174422.GA7538@meier-geinitz.de>
References: <20041017181209.GH12072@meier-geinitz.de> <4176037D.3050307@exactcode.de> <20041020174422.GA7538@meier-geinitz.de>
Message-ID: <41779351.1070706@exactcode.de>

Hi,

Henning Meier-Geinitz wrote:
> Hi,
> 
> On Wed, Oct 20, 2004 at 08:19:41AM +0200, Ren? Rebe wrote:
> 
>>I have some more avision updates in the queue, mostly fixes and cleanups 
>>- but also the button readout code, which would be a new feature ... 
>>Should I leave it out and seperate the rest of the code, or are those 
>>few button code lines tiny enought for a "just commit it"? ;-)
> 
> 
> If it's really only a few lines and yiu are sure that these lines
> don't break anything I guess it's ok.

Hm. Ok, then I commit the remaining normal fixes that have queued up 
(those are already big enough) and post a diff with the button stuff 
here, for review (I do not urgently demand to get it into the next 
release, since it is not in wide use yet and I use my svn tree for my 
private stuf anyway).

Sincerely,

-- 
Ren? Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
             +49 (0)30  255 897 45



From eppesuig at users.sourceforge.net  Sat Oct 23 13:03:57 2004
From: eppesuig at users.sourceforge.net (Giuseppe Sacco)
Date: Sat, 23 Oct 2004 14:03:57 +0200
Subject: [sane-devel] some english words
Message-ID: <1098533036.2770.313.camel@localhost>

Hi all,
I am updating the italian translation for sane-backends and I have a
questiong about radiance and brightness: are these synonims in english?
If they are then I will translate both with "luminosit?", otherwise I
have to understand what is the difference between them.

The radiance word is used in saneopts.h microtek2 
The brightness word is used in saneopts.h epson.c gt68xx matsushita
mustek pnm

Thanks,
Giuseppe




From martin at mkcollins.org  Sat Oct 23 17:43:15 2004
From: martin at mkcollins.org (Martin Collins)
Date: Sat, 23 Oct 2004 17:43:15 +0100
Subject: [sane-devel] some english words
In-Reply-To: <1098533036.2770.313.camel@localhost>
References: <1098533036.2770.313.camel@localhost>
Message-ID: <20041023174315.45fbf2bb.martin@mkcollins.org>

On Sat, 23 Oct 2004 14:03:57 +0200
Giuseppe Sacco <eppesuig at users.sourceforge.net> wrote:

> I am updating the italian translation for sane-backends and I have a
> questiong about radiance and brightness: are these synonims in
> english? If they are then I will translate both with "luminosit?",
> otherwise I have to understand what is the difference between them.

Radiance implies the emission of light, brightness could also apply
to reflection.

Depending on context radiance might refer to absolute intensity (i.e
the number of photons emitted) and brightness to apparent intensity
(i.e. the number of photons detected).

Brightness is one coordinate of the HSB colourspace (black-white) or
the mean of R,G and B values.
Strictly speaking it is not a synonym of radiance which is a measure
of the intensity of a light beam.
Luminosity is the power output of a light emitter.

However, in this context I doubt we are dealing with the strict meaning
of radiance so it is fairly safe to assume that brightness, radiance
and luminosity are all referring to the same kind of thing.

Martin



From mattias.ellert at tsl.uu.se  Sat Oct 23 17:57:07 2004
From: mattias.ellert at tsl.uu.se (Mattias Ellert)
Date: Sat, 23 Oct 2004 18:57:07 +0200
Subject: [sane-devel] some english words
In-Reply-To: <20041023174315.45fbf2bb.martin@mkcollins.org>
References: <1098533036.2770.313.camel@localhost> <20041023174315.45fbf2bb.martin@mkcollins.org>
Message-ID: <92B82794-2514-11D9-95B1-0003930D2AFC@tsl.uu.se>

2004-10-23 kl. 18.43 skrev Martin Collins:

> However, in this context I doubt we are dealing with the strict meaning
> of radiance so it is fairly safe to assume that brightness, radiance
> and luminosity are all referring to the same kind of thing.
>
> Martin

If they really, within the sane-backends, mean the same thing, then I 
would strongly suggest to drop one of them and only use a singel term. 
That would be both less confusing for the users and easier to maintain 
for the developers.

	Mattias




From henning at meier-geinitz.de  Sat Oct 23 18:18:54 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 23 Oct 2004 19:18:54 +0200
Subject: [sane-devel] some english words
In-Reply-To: <92B82794-2514-11D9-95B1-0003930D2AFC@tsl.uu.se>
References: <1098533036.2770.313.camel@localhost> <20041023174315.45fbf2bb.martin@mkcollins.org> <92B82794-2514-11D9-95B1-0003930D2AFC@tsl.uu.se>
Message-ID: <20041023171854.GF13573@meier-geinitz.de>

Hi,

On Sat, Oct 23, 2004 at 06:57:07PM +0200, Mattias Ellert wrote:
> If they really, within the sane-backends, mean the same thing, then I 
> would strongly suggest to drop one of them and only use a singel term. 
> That would be both less confusing for the users and easier to maintain 
> for the developers.

saneopts.h already contains a brightness option so this should be used
if radiance is really the same:
#define SANE_NAME_BRIGHTNESS            "brightness"
#define SANE_TITLE_BRIGHTNESS           SANE_I18N("Brightness")
#define SANE_DESC_BRIGHTNESS \
SANE_I18N("Controls the brightness of the acquired image.")

Bye,
  Henning



From mattias.ellert at tsl.uu.se  Sat Oct 23 19:11:15 2004
From: mattias.ellert at tsl.uu.se (Mattias Ellert)
Date: Sat, 23 Oct 2004 20:11:15 +0200
Subject: [sane-devel] some english words
In-Reply-To: <20041023171854.GF13573@meier-geinitz.de>
References: <1098533036.2770.313.camel@localhost> <20041023174315.45fbf2bb.martin@mkcollins.org> <92B82794-2514-11D9-95B1-0003930D2AFC@tsl.uu.se> <20041023171854.GF13573@meier-geinitz.de>
Message-ID: <EDD84FE9-251E-11D9-95B1-0003930D2AFC@tsl.uu.se>

2004-10-23 kl. 19.18 skrev Henning Meier-Geinitz:

> saneopts.h already contains a brightness option so this should be used
> if radiance is really the same:
> #define SANE_NAME_BRIGHTNESS            "brightness"
> #define SANE_TITLE_BRIGHTNESS           SANE_I18N("Brightness")
> #define SANE_DESC_BRIGHTNESS \
> SANE_I18N("Controls the brightness of the acquired image.")

Yes, but it does not contain brightness per channel (as mustek.c):

   s->opt[OPT_BRIGHTNESS_R].name = "brightness-r";
   s->opt[OPT_BRIGHTNESS_R].title = SANE_I18N ("Red brightness");
   s->opt[OPT_BRIGHTNESS_R].desc = SANE_I18N ("Controls the brightness 
of "
                                              "the red channel of the "
                                              "acquired image.");

While we're at it...

What is the difference between blacklevel and shadow resp. whitelevel 
and highlight

For the "one setting for all channels" option the descriptions are the 
same:

#define SANE_DESC_BLACK_LEVEL \
SANE_I18N("Selects what radiance level should be considered \"black\".")

#define SANE_DESC_SHADOW \
SANE_I18N("Selects what radiance level should be considered \"black\".")

#define SANE_DESC_WHITE_LEVEL \
SANE_I18N("Selects what radiance level should be considered \"white\".")

#define SANE_DESC_HIGHLIGHT \
SANE_I18N("Selects what radiance level should be considered \"white\".")

When the channels are split the descriptions differ:

/* SANE_DESC_BLACK_LEVEL_R does not exist */

#define SANE_DESC_SHADOW_R \
SANE_I18N("Selects what red radiance level should be considered 
\"black\".")

#define SANE_DESC_WHITE_LEVEL_R \
SANE_I18N("Selects what red radiance level should be considered 
\"white\".")

#define SANE_DESC_HIGHLIGHT_R \
SANE_I18N("Selects what red radiance level should be considered \"full 
red\".")

The description for SANE_DESC_WHITE_LEVEL_R doesn't make sense to me, 
since 100% red would mean "full red" and not "white". But then it again 
would be the same as the SANE_DESC_HIGHLIGHT_R. But I might have the 
wrong conception here...

If there is some difference between the meanings of the options that 
difference should be made clear in the option description. If there is 
no difference, then one of the option titles should be dropped to avoid 
confusion and ease maintainance.

	Mattias




From martin at mkcollins.org  Sat Oct 23 22:36:35 2004
From: martin at mkcollins.org (Martin Collins)
Date: Sat, 23 Oct 2004 22:36:35 +0100
Subject: [sane-devel] some english words
In-Reply-To: <EDD84FE9-251E-11D9-95B1-0003930D2AFC@tsl.uu.se>
References: <1098533036.2770.313.camel@localhost>
	<20041023174315.45fbf2bb.martin@mkcollins.org>
	<92B82794-2514-11D9-95B1-0003930D2AFC@tsl.uu.se>
	<20041023171854.GF13573@meier-geinitz.de>
	<EDD84FE9-251E-11D9-95B1-0003930D2AFC@tsl.uu.se>
Message-ID: <20041023223635.696e4f27.martin@mkcollins.org>

On Sat, 23 Oct 2004 20:11:15 +0200
Mattias Ellert <mattias.ellert at tsl.uu.se> wrote:

> What is the difference between blacklevel and shadow resp.
> whitelevel and highlight

To me they are the same.
 
> #define SANE_DESC_BLACK_LEVEL \
> SANE_I18N("Selects what radiance level should be considered
> \"black\".")

Brightness would be much better than radiance here.

> The description for SANE_DESC_WHITE_LEVEL_R doesn't make sense to
> me, since 100% red would mean "full red" and not "white". But then
> it again would be the same as the SANE_DESC_HIGHLIGHT_R. But I might
> have the wrong conception here...

I agree. Maybe zero-red and full-red would be clearer.

Martin



From pmacv at telefonica.net  Sun Oct 24 22:05:49 2004
From: pmacv at telefonica.net (Pedro M (Morphix User))
Date: Sun, 24 Oct 2004 21:05:49 +0000
Subject: [sane-devel] Common multifunctional API
In-Reply-To: <200410171311.28511.Oliver.Schwartz@gmx.de>
References: <415BD75B.1060103@bigpond.net.au> <200410062029.50935.Oliver.Schwartz@gmx.de> <Pine.LNX.4.53.0410170707470.1932@localhost.localdomain> <200410171311.28511.Oliver.Schwartz@gmx.de>
Message-ID: <417C192D.6010106@telefonica.net>

I suggest create a common API for XFree86, that can use CUPS and SANE 
for multifunctional users.

It could be a Ncurses GUI that would execute Sane or CUPS .

Regards.



From henning at meier-geinitz.de  Sun Oct 24 20:17:17 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 24 Oct 2004 21:17:17 +0200
Subject: [sane-devel] Common multifunctional API
In-Reply-To: <417C192D.6010106@telefonica.net>
References: <415BD75B.1060103@bigpond.net.au> <200410062029.50935.Oliver.Schwartz@gmx.de> <Pine.LNX.4.53.0410170707470.1932@localhost.localdomain> <200410171311.28511.Oliver.Schwartz@gmx.de> <417C192D.6010106@telefonica.net>
Message-ID: <20041024191717.GH3901@meier-geinitz.de>

Hi,

On Sun, Oct 24, 2004 at 09:05:49PM +0000, Pedro M (Morphix User) wrote:
> I suggest create a common API for XFree86, that can use CUPS and SANE 
> for multifunctional users.
> 
> It could be a Ncurses GUI that would execute Sane or CUPS .

Could you explain in more detail about what you are talking?
Is it somehow related to the Epson 2580 (you are posting in the Epson
2580 thread)?

Why should an API for printers and scanners be created? There already
exist APIs for both kinds of devices. And why should it use X?

And how is a GUI related to that API?

What do you want to do exactly?

Bye,
  Henning



From john at netpurgatory.com  Sun Oct 24 22:53:39 2004
From: john at netpurgatory.com (John C. Vernaleo)
Date: Sun, 24 Oct 2004 17:53:39 -0400 (EDT)
Subject: [sane-devel] Epson Perfection 1640SU
Message-ID: <Pine.LNX.4.50.0410241150360.22494-100000@thales.astro.umd.edu>

I was wondering what the status of the Automatic Document Feeder on the 
Epson Perfection 1640SU.

There is a bug report (#300572) that says it doesn't work with the 
backends 1.0.13, but that is not the most recent version of the backends.

I know it worked with backends 1.0.12 on Fedora Core 1 and that it no 
longer works on Fedora Core 2 with backends 1.0.13 (like the bug report).  
Has anyone tried 1.0.14, or one of the 1.0.15 pre-releases?

I'm willing to compile and install from source if someone has seen it work 
(or if doing so could help us find out what the problem is).

Thanks.

John



From wberrier at myrealbox.com  Mon Oct 25 04:23:02 2004
From: wberrier at myrealbox.com (Wade Berrier)
Date: Sun, 24 Oct 2004 21:23:02 -0600
Subject: [sane-devel] Visioneer 8700
Message-ID: <1098674582.25452.3.camel@crusader>

I'm toying with the idea of attempting to write a backend for my
Visioneer Onetouch 8700 Scanner.  Anyone else out there interested in
this?

Sometimes I wonder if it would be worth writing the driver, compared to
going down to Costco and picking up a supported scanner for $100.

I don't have any usb experience, but I was planning on using a usb
sniffer on windows to try to get the protocol down.

Anyone have any info/suggestions for this task?

Wade
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041024/fae47097/attachment.sig>

From nteknikk at monet.no  Mon Oct 25 16:29:27 2004
From: nteknikk at monet.no (Terje J. Hanssen)
Date: Mon, 25 Oct 2004 17:29:27 +0200
Subject: [sane-devel] Epson Perfection 1640SU
Message-ID: <417D1BD7.4090906@monet.no>

John C. Vernaleo wrote:

> I was wondering what the status of the Automatic Document Feeder on the
> Epson Perfection 1640SU.
>
> There is a bug report (#300572) that says it doesn't work with the
> backends 1.0.13, but that is not the most recent version of the backends.
>
> I know it worked with backends 1.0.12 on Fedora Core 1 and that it no
> longer works on Fedora Core 2 with backends 1.0.13 (like the bug report).
> Has anyone tried 1.0.14, or one of the 1.0.15 pre-releases?
>
> I'm willing to compile and install from source if someone has seen it 
> work
> (or if doing so could help us find out what the problem is).


I got and posted this Epson 1640SU ADF problem with Sane 1.0.14 on Suse 
Linux 9.1 and on SJDS2/Linux.

Another user replied later that also Sane 1.013 on Suse Linux didn't 
work. However, stepping back to Sane 1.08 did work on Suse. I did the 
same and 1.08 worked for both Suse 9.1 and SJDS/Linux.

Karl Heinz should compare Sane 1.014 vs 1.08 to try to debug the 
problem. I haven't heard more about this ;-) maybe now as this is a 
problem for more of us?

http://lists.alioth.debian.org/pipermail/sane-devel/2004-August/011733.html
http://lists.alioth.debian.org/pipermail/sane-devel/2004-September/012094.html

Regards,
Terje J. Hanssen





From mailanryck at muenster.de  Sun Oct 24 20:48:16 2004
From: mailanryck at muenster.de (Ryck Purschke-Evers)
Date: Sun, 24 Oct 2004 21:48:16 +0200
Subject: [sane-devel] CanoScan D1250U2
Message-ID: <417C0700.4070908@muenster.de>

Hello!

Is there anybody working on a backend for a Canon CanoScan D1250U2?
When not, can someone help me to "build" (is that right, to "build" a 
backend?) the backend?

Greetings
    Ryck




From gerard at gkall.hobby.nl  Mon Oct 25 20:33:56 2004
From: gerard at gkall.hobby.nl (gerard klaver)
Date: Mon, 25 Oct 2004 19:33:56 +0000
Subject: [sane-devel] CanoScan D1250U2
In-Reply-To: <417C0700.4070908@muenster.de>
References: <417C0700.4070908@muenster.de>
Message-ID: <1098732835.2460.1.camel@gk-lex3>

On Sun, 2004-10-24 at 19:48, Ryck Purschke-Evers wrote:
> Hello!
> 
> Is there anybody working on a backend for a Canon CanoScan D1250U2?
> When not, can someone help me to "build" (is that right, to "build" a 
> backend?) the backend?
> 
> Greetings
>     Ryck

For status see the information on this page:

http://www.sane-project.org/unsupported/canon-d1250u2.html

-- 
----------
m.vr.gr.
Gerard Klaver




From the.beauty at adslhome.dk  Tue Oct 26 14:30:00 2004
From: the.beauty at adslhome.dk (Torben Andersen)
Date: Tue, 26 Oct 2004 15:30:00 +0200
Subject: [sane-devel] FC 2, hotplug and sane
Message-ID: <417E5158.2060606@adslhome.dk>

Hi,

I've installed a FC2 and updated. I can use sane, but only as root. I've 
been googling and reading and narrowed the problem to the USB interface 
to my Epson scanner. According to 
http://www.sane-project.org/README.linux, hotplug (which is compiled in 
the kernel) and /etc/hotplug/usb/libusbscanner (pasted in below 
signature) should  enable useracces to the scanner, if

"Usually you must just add the users that are allowed to access the scanner to group "scanner""

I don't know how to do that.

If I unplug and plug the scanner, user acces is allowed, but not on boot up !

Any help will bee appriciated :-)

Regards Torben

Contents af libusbscanner:

#!/bin/bash
# $Id: libusbscanner,v 1.1 2004/05/04 13:05:27 twaugh Exp $
#
# /etc/hotplug/usb/libusbscanner
#
# Sets up newly plugged in USB scanner so that the user who owns
# the console according to pam_console can access it from user space
#
# Note that for this script to work, you'll need all of the following:
# a) a line in the file /etc/hotplug/usermap that corresponds to the 
#    camera you are using.
# b) a setup using pam_console creates the respective lock files
#    containing the name of the respective user. You can check for that
#    by executing "echo `cat /var/{run,lock}/console.lock`" and 
#    verifying the appropriate user is mentioned somewhere there.
# c) a Linux kernel supporting hotplug and usbdevfs
# d) the hotplug package (http://linux-hotplug.sourceforge.net/)
#
# In the usermap file, the first field "usb module" should be named 
# "libusbscanner" like this script.
# 

if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
then
    # New code, using lock files instead of copying /dev/console permissions
    # This also works with non-gdm logins (e.g. on a virtual terminal)
    # Idea and code from Nalin Dahyabhai <nalin at redhat.com>
    if [ -f /var/run/console.lock ]
    then
        CONSOLEOWNER=`cat /var/run/console.lock`
    elif [ -f /var/lock/console.lock ]
    then
        CONSOLEOWNER=`cat /var/lock/console.lock`
    else
        CONSOLEOWNER=
    fi
    if [ -n "$CONSOLEOWNER" ]
    then
        chmod 0000 "${DEVICE}"
        chown "$CONSOLEOWNER" "${DEVICE}"
        chmod 0600 "${DEVICE}"
    fi
fi





-- 
"It's trivial to make fun of Microsoft products,
but it takes a real man to make them work,
and a god to make them do anything useful."




From henning at meier-geinitz.de  Tue Oct 26 17:34:16 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 26 Oct 2004 18:34:16 +0200
Subject: [sane-devel] FC 2, hotplug and sane
In-Reply-To: <417E5158.2060606@adslhome.dk>
References: <417E5158.2060606@adslhome.dk>
Message-ID: <20041026163416.GB19439@meier-geinitz.de>

Hi,

On Tue, Oct 26, 2004 at 03:30:00PM +0200, Torben Andersen wrote:
> I've installed a FC2 and updated. I can use sane, but only as root. I've 
> been googling and reading and narrowed the problem to the USB interface 
> to my Epson scanner. According to 
> http://www.sane-project.org/README.linux, hotplug (which is compiled in 
> the kernel) and /etc/hotplug/usb/libusbscanner (pasted in below 
> signature) should  enable useracces to the scanner, if
> 
> "Usually you must just add the users that are allowed to access the scanner 
> to group "scanner""
> 
> I don't know how to do that.

man gpasswd
man usermod
man groups
man group

> If I unplug and plug the scanner, user acces is allowed,

In this case hotplug is set up correctly.

>but not on boot up !

I have heard rumors about this problem and was told that "coldplug"
would help.

But:

> #!/bin/bash
> # $Id: libusbscanner,v 1.1 2004/05/04 13:05:27 twaugh Exp $

This is not the libusbscanner script from the sane-backends package.
It doesn't seem to work by using groups but by giving access to the
scanner to anyone who is logged-in locally. Quite strange.
Anyway, for details ask your distributor.

I haven't looked at the details but if the device is plugged-in while
nobody is logged in I guess only root can access it. Or do I
misunderstand the script?

Bye,
  Henning



From kpschrage at gmx.de  Tue Oct 26 18:54:11 2004
From: kpschrage at gmx.de (Klaus-Peter Schrage)
Date: Tue, 26 Oct 2004 19:54:11 +0200
Subject: [sane-devel] FC 2, hotplug and sane
In-Reply-To: <417E5158.2060606@adslhome.dk>
References: <417E5158.2060606@adslhome.dk>
Message-ID: <417E8F43.6090701@gmx.de>

Torben Andersen wrote:
> Hi,
> 
> I've installed a FC2 and updated. I can use sane, but only as root. I've 
> been googling and reading and narrowed the problem to the USB interface 
> to my Epson scanner. According to 
> http://www.sane-project.org/README.linux, hotplug (which is compiled in 
> the kernel) and /etc/hotplug/usb/libusbscanner (pasted in below 
> signature) should  enable useracces to the scanner, if

This is a known issue, see
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124053
Klaus



From wolframheider at web.de  Tue Oct 26 19:24:00 2004
From: wolframheider at web.de (Wolfram Heider)
Date: Tue, 26 Oct 2004 20:24:00 +0200
Subject: [sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S
Message-ID: <200410262024.00402.wolframheider@web.de>

Hello list,

when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with kernel 
2.6.5, my scanner, a UMAX Astra 1220 S which had worked well troughout all 
the kernel-versons of the last years, was gone without the slightest trace.  
scanimage -L, sane-find-scanner and the other little helpers remainend silent 
about it.
Maybe it's not a really sane-problem but a controller-problem.
The controller in use is a Dawicontrol DC-2975-C which connected till now over 
the sym53c8xx/ncr53c8xx-module.
The strange thing is that with the kernel 2.6.1 of the knoppix 
3.4-distribution everthing works as usual.
The Suse-Kernel still comes with the sym53c8xx-module, but something seems to 
be wrong with it.
I wasn't very close to the list in the last few months, so perhaps I missed 
some relevant stuff - sorry if I ask those damn old questions.
Is anybody out there who expierienced a similar kind of behaviour and has got 
a solution for it?

Thanks in advance

Wolfram Heider 



From adeuring at gmx.net  Tue Oct 26 21:11:44 2004
From: adeuring at gmx.net (abel deuring)
Date: Tue, 26 Oct 2004 22:11:44 +0200
Subject: [sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S
In-Reply-To: <200410262024.00402.wolframheider@web.de>
References: <200410262024.00402.wolframheider@web.de>
Message-ID: <417EAF80.7030005@gmx.net>

Wolfram Heider wrote:
> Hello list,
> 
> when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with kernel 
> 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well troughout all 
> the kernel-versons of the last years, was gone without the slightest trace.  
> scanimage -L, sane-find-scanner and the other little helpers remainend silent 
> about it.
> Maybe it's not a really sane-problem but a controller-problem.

yes, it's most likely a problem in the Linux SCSI system. To look for 
SCSI scanners, sane-find-scanner reads /proc/scsi/scsi, and the contents 
of this proc file is "managed" by the SCSI system of the kernel.

> The controller in use is a Dawicontrol DC-2975-C which connected till now over 
> the sym53c8xx/ncr53c8xx-module.
> The strange thing is that with the kernel 2.6.1 of the knoppix 
> 3.4-distribution everthing works as usual.
> The Suse-Kernel still comes with the sym53c8xx-module, but something seems to 
> be wrong with it.

Are you sure that the sym/ncr53c8xx module is indeed loaded? And if it 
loaded, do you get any error messages in /var/log/messages?

The sym/ncr53c8xx drivers offer many parameters; perhaps it helps to 
play with some of them. The file
<kernel source dir>/drivers/scsi/README.ncr53c8xx describes these 
parameters quite detailed.

Abel



From kpschrage at gmx.de  Tue Oct 26 21:48:13 2004
From: kpschrage at gmx.de (Klaus-Peter Schrage)
Date: Tue, 26 Oct 2004 22:48:13 +0200
Subject: [sane-devel] FC 2, hotplug and sane  - SOLVED
In-Reply-To: <417EA07C.4020705@adslhome.dk>
References: <417E5158.2060606@adslhome.dk> <417E8F43.6090701@gmx.de> <417EA07C.4020705@adslhome.dk>
Message-ID: <417EB80D.7050901@gmx.de>

Torben Andersen wrote:
> Thanks to Klaus-Peter. His link had a solution: Put
> 
> chmod 0666 "$DEVICE"
> 
> in the bottom of the libusbscanner. I don't know if its a perfect 
> solution, but it certainly worked.
> 

That's what I've done, and nobody ever gave me a good reason why this 
shouln't be done.
Klaus



From wolframheider at web.de  Tue Oct 26 21:59:26 2004
From: wolframheider at web.de (Wolfram Heider)
Date: Tue, 26 Oct 2004 22:59:26 +0200
Subject: [sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S
Message-ID: <200410262259.26185.wolframheider@web.de>

Am Dienstag, 26. Oktober 2004 22:11 schrieben Sie:
> Wolfram Heider wrote:
> > Hello list,
> >
> > when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with
> > kernel 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well
> > troughout all the kernel-versons of the last years, was gone without the
> > slightest trace. scanimage -L, sane-find-scanner and the other little
> > helpers remainend silent about it.
> > Maybe it's not a really sane-problem but a controller-problem.
>
> yes, it's most likely a problem in the Linux SCSI system. To look for
> SCSI scanners, sane-find-scanner reads /proc/scsi/scsi, and the contents
> of this proc file is "managed" by the SCSI system of the kernel.
>
> > The controller in use is a Dawicontrol DC-2975-C which connected till now
> > over the sym53c8xx/ncr53c8xx-module.
> > The strange thing is that with the kernel 2.6.1 of the knoppix
> > 3.4-distribution everthing works as usual.
> > The Suse-Kernel still comes with the sym53c8xx-module, but something
> > seems to be wrong with it.
>
> Are you sure that the sym/ncr53c8xx module is indeed loaded? And if it
> loaded, do you get any error messages in /var/log/messages?
>
> The sym/ncr53c8xx drivers offer many parameters; perhaps it helps to
> play with some of them. The file
> <kernel source dir>/drivers/scsi/README.ncr53c8xx describes these
> parameters quite detailed.
>
> Abel

Good evening; Abel

thanks for your quick reply.
The sym53c8xx modul isn't loadde at boottime. When loaded by hand via
 modprobe it takes suspiciously long time to come up - and finanally nothing
 has changed - everthing dead as the cemetry of Chicago. Only lspci gives a
 hint that there is something in the slot.
I'll take your advice and play around a little bit with the driver
 parameters. See you later.

Wolfram
( I first choosed the wrong reply address - sorry)



From herbr at pfinders.com  Tue Oct 26 22:05:40 2004
From: herbr at pfinders.com (herbr at pfinders.com)
Date: Tue, 26 Oct 2004 14:05:40 -0700 (PDT)
Subject: [sane-devel] feeder for scanner
Message-ID: <3079.144.91.44.131.1098824740.squirrel@144.91.44.131>

Hi,

I would like to buy a nice high end scanner that is supported
that has a document feeder. Any suggestions? Any experiences?

How do you handle a jam? What kind of speed. How many documents
can fit?

Herb
Pathfinders Software





From wolframheider at web.de  Tue Oct 26 22:25:03 2004
From: wolframheider at web.de (Wolfram Heider)
Date: Tue, 26 Oct 2004 23:25:03 +0200
Subject: [sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S
In-Reply-To: <417EAF80.7030005@gmx.net>
References: <200410262024.00402.wolframheider@web.de> <417EAF80.7030005@gmx.net>
Message-ID: <200410262325.03916.wolframheider@web.de>

Am Dienstag, 26. Oktober 2004 22:11 schrieb abel deuring:
> Wolfram Heider wrote:
> > Hello list,
> >
> > when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with
> > kernel 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well
> > troughout all the kernel-versons of the last years, was gone without the
> > slightest trace. scanimage -L, sane-find-scanner and the other little
> > helpers remainend silent about it.
> > Maybe it's not a really sane-problem but a controller-problem.
>
> yes, it's most likely a problem in the Linux SCSI system. To look for
> SCSI scanners, sane-find-scanner reads /proc/scsi/scsi, and the contents
> of this proc file is "managed" by the SCSI system of the kernel.
>
> > The controller in use is a Dawicontrol DC-2975-C which connected till now
> > over the sym53c8xx/ncr53c8xx-module.
> > The strange thing is that with the kernel 2.6.1 of the knoppix
> > 3.4-distribution everthing works as usual.
> > The Suse-Kernel still comes with the sym53c8xx-module, but something
> > seems to be wrong with it.
>
> Are you sure that the sym/ncr53c8xx module is indeed loaded? And if it
> loaded, do you get any error messages in /var/log/messages?
>
> The sym/ncr53c8xx drivers offer many parameters; perhaps it helps to
> play with some of them. The file
> <kernel source dir>/drivers/scsi/README.ncr53c8xx describes these
> parameters quite detailed.
>
> Abel

Hello Abel,

here is the output a "modprobe sym53c8xx" produces in /var/log/messages:

Oct 26 23:11:16 linux su: (to root) ich on /dev/pts/3
Oct 26 23:11:16 linux su: pam_unix2: session started for user root, service su 
Oct 26 23:11:32 linux kernel: sym0: <875> rev 0x26 at pci 0000:00:11.0 irq 12
Oct 26 23:11:32 linux kernel: sym0: No NVRAM, ID 7, Fast-20, SE, parity 
checking
Oct 26 23:11:32 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:11:32 linux kernel: scsi0 : sym-2.1.18i
Oct 26 23:11:38 linux kernel: sym0:0:0: ABORT operation started.
Oct 26 23:11:43 linux kernel: sym0:0:0: ABORT operation timed-out.
Oct 26 23:11:43 linux kernel: sym0:0:0: DEVICE RESET operation started.
Oct 26 23:11:48 linux kernel: sym0:0:0: DEVICE RESET operation timed-out.
Oct 26 23:11:48 linux kernel: sym0:0:0: BUS RESET operation started.
Oct 26 23:11:53 linux kernel: sym0:0:0: BUS RESET operation timed-out.
Oct 26 23:11:53 linux kernel: sym0:0:0: HOST RESET operation started.
Oct 26 23:11:53 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:11:58 linux kernel: sym0:0:0: HOST RESET operation timed-out.
Oct 26 23:11:58 linux kernel: scsi: Device offlined - not ready after error 
recovery: host 0 channel 0 id 0 lun 0
Oct 26 23:12:03 linux kernel: sym0:1:0: ABORT operation started.
Oct 26 23:12:08 linux kernel: sym0:1:0: ABORT operation timed-out.
Oct 26 23:12:08 linux kernel: sym0:1:0: DEVICE RESET operation started.
Oct 26 23:12:13 linux kernel: sym0:1:0: DEVICE RESET operation timed-out.
Oct 26 23:12:13 linux kernel: sym0:1:0: BUS RESET operation started.
Oct 26 23:12:18 linux kernel: sym0:1:0: BUS RESET operation timed-out.
Oct 26 23:12:18 linux kernel: sym0:1:0: HOST RESET operation started.
Oct 26 23:12:18 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:12:23 linux kernel: sym0:1:0: HOST RESET operation timed-out.
Oct 26 23:12:23 linux kernel: scsi: Device offlined - not ready after error 
recovery: host 0 channel 0 id 1 lun 0
Oct 26 23:12:29 linux kernel: sym0:2:0: ABORT operation started.
Oct 26 23:12:34 linux kernel: sym0:2:0: ABORT operation timed-out.
Oct 26 23:12:34 linux kernel: sym0:2:0: DEVICE RESET operation started.
Oct 26 23:12:38 linux su: (to root) ich on /dev/pts/7
Oct 26 23:12:38 linux su: pam_unix2: session started for user root, service su 
Oct 26 23:12:39 linux kernel: sym0:2:0: DEVICE RESET operation timed-out.
Oct 26 23:12:39 linux kernel: sym0:2:0: BUS RESET operation started.
Oct 26 23:12:42 linux su: pam_unix2: session finished for user root, service 
su 
Oct 26 23:12:42 linux su: (to root) ich on /dev/pts/7
Oct 26 23:12:42 linux su: pam_unix2: session started for user root, service su 
Oct 26 23:12:44 linux kernel: sym0:2:0: BUS RESET operation timed-out.
Oct 26 23:12:44 linux kernel: sym0:2:0: HOST RESET operation started.
Oct 26 23:12:44 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:12:49 linux kernel: sym0:2:0: HOST RESET operation timed-out.
Oct 26 23:12:49 linux kernel: scsi: Device offlined - not ready after error 
recovery: host 0 channel 0 id 2 lun 0
Oct 26 23:12:54 linux kernel: sym0:3:0: ABORT operation started.
Oct 26 23:12:59 linux kernel: sym0:3:0: ABORT operation timed-out.
Oct 26 23:12:59 linux kernel: sym0:3:0: DEVICE RESET operation started.
Oct 26 23:13:04 linux kernel: sym0:3:0: DEVICE RESET operation timed-out.
Oct 26 23:13:04 linux kernel: sym0:3:0: BUS RESET operation started.
Oct 26 23:13:09 linux kernel: sym0:3:0: BUS RESET operation timed-out.
Oct 26 23:13:09 linux kernel: sym0:3:0: HOST RESET operation started.
Oct 26 23:13:09 linux kernel: sym0: SCSI BUS has been reset.

Sounds as there is something fundamental going wrong. Can you make it out?

Greetings

Wolfram



From thetargos at slackercentral.com  Wed Oct 27 05:58:49 2004
From: thetargos at slackercentral.com (Gian Paolo Mureddu)
Date: Tue, 26 Oct 2004 23:58:49 -0500
Subject: [sane-devel] feeder for scanner
In-Reply-To: <3079.144.91.44.131.1098824740.squirrel@144.91.44.131>
References: <3079.144.91.44.131.1098824740.squirrel@144.91.44.131>
Message-ID: <417F2B09.9040100@slackercentral.com>

herbr at pfinders.com wrote:

>Hi,
>
>I would like to buy a nice high end scanner that is supported
>that has a document feeder. Any suggestions? Any experiences?
>
>How do you handle a jam? What kind of speed. How many documents
>can fit?
>
>Herb
>Pathfinders Software
>
>
>
>  
>
Interesting question, a friend of mine is also interested on a 
professional scanner for his Linux box, I'm eager to see the suggestions.



From gerard at gkall.hobby.nl  Wed Oct 27 13:36:26 2004
From: gerard at gkall.hobby.nl (gerard klaver)
Date: Wed, 27 Oct 2004 12:36:26 +0000
Subject: [sane-devel] Re: [Lcms-user] monitor profile questions -- adding vcgt to a
 profile?
In-Reply-To: <200410191019.i9JAJu1W025691@web218.megawebservers.com>
References: <200410191019.i9JAJu1W025691@web218.megawebservers.com>
Message-ID: <1098880586.2799.16.camel@gk-lex3>

On Tue, 2004-10-19 at 10:19, marti at littlecms.com wrote:
> Hi,
> 
> > >Are the reasons known? Just curious..
> 
> 
> As Gerhard already noted, I am not allowed to support or maintain 
> the lprof package anymore. The reasons are the company I work 
> for (HP) acquired the sources for its internal use. 
> 
> Moreover, the technology I was using in the latest profilers (not 
> lprof, but what intended to sell as professional package) is 
> "sensible" in terms my non-disclosure agreement. So, I 
> sacrificed this package in order to keep lcms (the CMM) alive 
> and well. 
> 
> HP kindly allow me to continue the development of lcms as 
> open source and even more, they does SUPPORT this development. 
> In such way I have contact with ICC members, access to restricted 
> documents, proposed extensions, etc.
> 
> So, I'm very sorry for that, but lprof is now effectively dead. 
> At least as open source. It would be nice, however, if anybody 
> would take the sources and continue with the development. But as said, 
> I am not allowed to do that anymore.
> 
> King regards,
> Marti.
> 
Hello,

To keep the lprof package available i have placed the lprof files and
other information from Marti old profilers page on my homepage.
See http://gkall.hobby.nl/sane-lprof/sane-lprof.html

Goal is to maintain the package as good as possible but time and/or
knowledge can be a problem. Also if more people are interested in
maintaining this package, let me know.
Then maintenance depends not on a single person and placing it in the
SANE CVS tree (sane-lprof or first sane/experimental/sane-lprof) is a
good option. See als SANE Bugreport 30181.
 
In this way more people are be able to use the package on more platforms
and there is a tracking system for the patches and changes.

And if you have any remarks/comments/updates on/for this page, please
let me know.


-- 
----------
m.vr.gr.
Gerard Klaver




From anoah at pfeiffer.edu  Wed Oct 27 14:04:24 2004
From: anoah at pfeiffer.edu (m. allan noah)
Date: Wed, 27 Oct 2004 09:04:24 -0400 (EDT)
Subject: [sane-devel] feeder for scanner
In-Reply-To: <417F2B09.9040100@slackercentral.com>
References: <3079.144.91.44.131.1098824740.squirrel@144.91.44.131>
 <417F2B09.9040100@slackercentral.com>
Message-ID: <Pine.LNX.4.61.0410270904030.7940@limos.pfeiffer.edu>

try searching the archives of this mailing list. this comes up every few 
months.

allan

On Tue, 26 Oct 2004, Gian Paolo Mureddu wrote:

> herbr at pfinders.com wrote:
>
>> Hi,
>> 
>> I would like to buy a nice high end scanner that is supported
>> that has a document feeder. Any suggestions? Any experiences?
>> 
>> How do you handle a jam? What kind of speed. How many documents
>> can fit?
>> 
>> Herb
>> Pathfinders Software
>> 
>> 
>> 
>> 
> Interesting question, a friend of mine is also interested on a professional 
> scanner for his Linux box, I'm eager to see the suggestions.
>
>

-- 
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera



From artpi at ptic.pl  Wed Oct 27 15:01:43 2004
From: artpi at ptic.pl (Artur Pierscinski)
Date: Wed, 27 Oct 2004 16:01:43 +0200
Subject: [sane-devel] genesys backend - warming up procedure
Message-ID: <417FAA47.2010903@ptic.pl>

Hi!

I have question about warming up procedure in genesys backend (scaner: 
Plustek ST24).

How is proper range of readed values from scaner sensor during warming 
up the lamp procedure?
It seems for me like a 12-bits (sensor), with set other (higher) bit set.
So, calculated average values are about 9600, which in my case
newer pass warming loop exit:

      if (second_average > (110 * 256) && (((double) difference) / 
second_average) < 0.002)
        {
          DBG (DBG_info, "genesys_warmup_lamp: warmup succeeded after %d 
seconds\n",
               seconds);
          break;
         }

Multiply  second_average by 3 in above condition will satisfied it,
and warming up lamp ends with success.
Is those belongs only to  my scanner or happed on others to?

Artur Pierscinski

e-mail: artpi at ptic.pl



From gerhard at gjaeger.de  Wed Oct 27 16:46:29 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Wed, 27 Oct 2004 17:46:29 +0200
Subject: [sane-devel] genesys backend - warming up procedure
In-Reply-To: <417FAA47.2010903@ptic.pl>
References: <417FAA47.2010903@ptic.pl>
Message-ID: <200410271746.29865.gerhard@gjaeger.de>

On Mittwoch 27 Oktober 2004 16:01, Artur Pierscinski wrote:
> Hi!
>
> I have question about warming up procedure in genesys backend (scaner:
> Plustek ST24).
>
> How is proper range of readed values from scaner sensor during warming
> up the lamp procedure?
> It seems for me like a 12-bits (sensor), with set other (higher) bit set.
> So, calculated average values are about 9600, which in my case
> newer pass warming loop exit:
>
>       if (second_average > (110 * 256) && (((double) difference) /
> second_average) < 0.002)
>         {
>           DBG (DBG_info, "genesys_warmup_lamp: warmup succeeded after %d
> seconds\n",
>                seconds);
>           break;
>          }
>
> Multiply  second_average by 3 in above condition will satisfied it,
> and warming up lamp ends with success.
> Is those belongs only to  my scanner or happed on others to?
>

Hi,

I've done some tests here with the ST24 and rewrote some parts of
the code, that the warmup and calibration stuff gets passed on it.
The major problem of the current genesys code is, that it is tied to
a UMAX device. All the settings specific to CCD and DAC (and motor)
are only valid for this scanner. This needs to be tweaked. I did this
here, but the code is not available so far ....

Gerhard





From henning at meier-geinitz.de  Wed Oct 27 17:19:52 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 27 Oct 2004 18:19:52 +0200
Subject: [sane-devel] FC 2, hotplug and sane  - SOLVED
In-Reply-To: <417EB80D.7050901@gmx.de>
References: <417E5158.2060606@adslhome.dk> <417E8F43.6090701@gmx.de> <417EA07C.4020705@adslhome.dk> <417EB80D.7050901@gmx.de>
Message-ID: <20041027161952.GA14330@meier-geinitz.de>

Hi,

On Tue, Oct 26, 2004 at 10:48:13PM +0200, Klaus-Peter Schrage wrote:
> Torben Andersen wrote:
> >Thanks to Klaus-Peter. His link had a solution: Put
> >
> >chmod 0666 "$DEVICE"
> >
> >in the bottom of the libusbscanner. I don't know if its a perfect 
> >solution, but it certainly worked.
> >
> 
> That's what I've done, and nobody ever gave me a good reason why this 
> shouln't be done.

If you are the only user on your system, that's ok.

Bye,
  Henning



From mmotovsk at gnome.sk  Wed Oct 27 21:20:28 2004
From: mmotovsk at gnome.sk (Martin Motovsky)
Date: Wed, 27 Oct 2004 20:20:28 +0000 (GMT)
Subject: [sane-devel] Epson 1250 scanner does not return back after scanning
Message-ID: <1098908428026_29625227@aladarko.gnome.sk>

Dear sirs,

we have a problem with our Epson 1250 scanner. It scans an image correctly,
but after scanning, a lamp remains be switched on and a scanner's header
remains at the "end of the image" position. I.e. it does not return back to
the original home position. Can somebody help us?

We have 
- FreeBSD system
- sane-backends-1.0.14
- only unmarked driver in the dll.conf if a plustek driver

Martin Motovsky



From wolframheider at web.de  Thu Oct 28 03:27:54 2004
From: wolframheider at web.de (Wolfram Heider)
Date: Thu, 28 Oct 2004 04:27:54 +0200
Subject: [sane-devel] Suse9.1, sym53c8xx and umaxscanner, help from Abel
Message-ID: <200410280427.54100.wolframheider@web.de>

Hello list,

with updating to Suse 9.1 I got a lot of trouble with my scanner, a vernerable 
umax 1220 S, connected via the sym53c8xx module, which had worked absolutely 
flawlessly till then. The module wasn't loaded ast boottime, the scanner 
because of this not regonized. Module loading by hand lasted extremely long 
and unloading wasn't just impossible. The same procedure with additional 
parameters brought but little relief - the scanner remained dead.
I talked about this problem and the problems I faced during the initial setup 
of Suse 9.1, when automatic installation didn't work, because Yast searched 
for a scsi-harddrive that didn't exist (the only client of the controller was 
the scanner), with Abel Deuring. He proposed to focus on the coldplug script 
and to switch it off for tresting. And that was it. There must be something 
considerably wrong in the realm of this script. So I would recommend to 
everyone who also faces the Suse9.1/sym53c8xx-problem and can afford to get 
on without USB-support to deactivate the 
startupscript /etc/init.d/rc5./S02coldplug till the folks at Suse have done 
it better.

Greetings

Wolfram Heider
 



From olaf at epkowa.co.jp  Thu Oct 28 04:42:37 2004
From: olaf at epkowa.co.jp (Olaf Meeuwissen)
Date: Thu, 28 Oct 2004 12:42:37 +0900
Subject: [sane-devel] Epson 1250 scanner does not return back after
 scanning
In-Reply-To: <1098908428026_29625227@aladarko.gnome.sk> (Martin Motovsky's
 message of "Wed, 27 Oct 2004 20:20:28 +0000 (GMT)")
References: <1098908428026_29625227@aladarko.gnome.sk>
Message-ID: <87mzy75x02.fsf@zen.epkowa.co.jp>

Martin Motovsky <mmotovsk at gnome.sk> writes:

> Dear sirs,
>
> we have a problem with our Epson 1250 scanner. It scans an image correctly,
> but after scanning, a lamp remains be switched on and a scanner's header
> remains at the "end of the image" position. I.e. it does not return back to
> the original home position. Can somebody help us?

The lamp has to be switched off by the software.  I don't know if the
plustek backend does that.

> We have 
> - FreeBSD system
> - sane-backends-1.0.14
> - only unmarked driver in the dll.conf if a plustek driver

You may want to try the epkowa backend that comes as part of "Image
Scan! for Linux" which is downloadable via:

  http://www.epkowa.co.jp/english/linux_e/dl_scan.html

Hope this helps,
-- 
Olaf Meeuwissen                            EPSON KOWA Corporation, PF1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2



From gerhard at gjaeger.de  Thu Oct 28 08:19:56 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Thu, 28 Oct 2004 09:19:56 +0200
Subject: [sane-devel] Epson 1250 scanner does not return back after scanning
In-Reply-To: <1098908428026_29625227@aladarko.gnome.sk>
References: <1098908428026_29625227@aladarko.gnome.sk>
Message-ID: <200410280919.56899.gerhard@gjaeger.de>

On Mittwoch 27 Oktober 2004 22:20, Martin Motovsky wrote:
> Dear sirs,
>
> we have a problem with our Epson 1250 scanner. It scans an image correctly,
> but after scanning, a lamp remains be switched on and a scanner's header
> remains at the "end of the image" position. I.e. it does not return back to
> the original home position. Can somebody help us?
>
> We have
> - FreeBSD system
> - sane-backends-1.0.14
> - only unmarked driver in the dll.conf if a plustek driver
>
The lamp is switched off by the software and the behaviour can be setup
in the configuration file. Why the sensor gets stucked, I don't know.
Can you please retry and enabling the debug message before, i.e.
export SANE_DEBUG_PLUSTEK=20 ; scanimage [what-ever-parameter-you-need]

--
 Gerhard




From mmotovsk at gnome.sk  Thu Oct 28 10:16:09 2004
From: mmotovsk at gnome.sk (Martin Motovsky)
Date: Thu, 28 Oct 2004 11:16:09 +0200
Subject: [sane-devel] Epson 1250 scanner does not return back after scanning
In-Reply-To: <200410280919.56899.gerhard@gjaeger.de>
References: <1098908428026_29625227@aladarko.gnome.sk> <200410280919.56899.gerhard@gjaeger.de>
Message-ID: <013E3129-28C2-11D9-9806-000393775A6A@gnome.sk>

Thank you for previous advices.

While testing scanimage in the debug mode, I mentioned, that sometimes 
it finished scanning correctly and sometime not. Below is a debug 
output, when lamp remained on and scanner's header did not return back 
to original position.

Martin

---------------------------------------------------
I used this script:
export SANE_DEBUG_PLUSTEK=20 ; scanimage -d plustek:/dev/uscanner0 
--format tiff -l10 -t10 -x100 -y100 --resolution 150dpi --mode Color > 
test.tiff 2>log.txt

---------------------------------------------------
Here is a debug output:

[sanei_debug] Setting debug level of plustek to 20.
[plustek] Plustek backend V0.47-11, part of sane-backends 1.0.14
[plustek] ># Plustek-SANE Backend configuration file<
[plustek] ># For use with LM9831/2/3 based USB scanners<
[plustek] >#<
[plustek] ><
[plustek] ># each device needs at least two lines:<
[plustek] ># - [usb] vendor-ID and product-ID<
[plustek] ># - device devicename<
[plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)<
[plustek] ># [usb] 0x07B3 0x0017<
[plustek] ># device /dev/usbscanner<
[plustek] ># or<
[plustek] ># device libusb:bbb:ddd<
[plustek] ># where bbb is the busnumber and ddd the device number<
[plustek] ># make sure that your user has access to 
/proc/bus/usb/bbb/ddd<
[plustek] >#<
[plustek] ># additionally you can specify some options<
[plustek] ># warmup, lOffOnEnd, lampOff<
[plustek] >#<
[plustek] ># For autodetection use<
[plustek] ># [usb]<
[plustek] ># device /dev/usbscanner<
[plustek] >#<
[plustek] ># or simply<
[plustek] ># [usb]<
[plustek] >#<
[plustek] ># or if you want a specific device but you have no idea 
about the<
[plustek] ># device node or you use libusb, simply set vendor- and 
product-ID<
[plustek] ># [usb] 0x07B3 0x0017<
[plustek] ># device auto<
[plustek] >#<
[plustek] ># NOTE: autodetection is safe, as it uses the info it got<
[plustek] >#       from the USB subsystem. If you're not using the<
[plustek] >#       autodetection, you MUST have attached that device<
[plustek] >#       at your USB-port, that you have specified...<
[plustek] >#<
[plustek] ><
[plustek] >[usb]<
[plustek] next device uses autodetection
[plustek] ... next device
[plustek] ><
[plustek] >#<
[plustek] ># options for the previous USB entry<
[plustek] >#<
[plustek] ># switch lamp off after xxx secs, 0 disables the feature<
[plustek] >option lampOff 309<
[plustek] Decoding option >lampOff<
[plustek] ><
[plustek] ># warmup period in seconds, 0 means no warmup<
[plustek] >option warmup 15<
[plustek] Decoding option >warmup<
[plustek] ><
[plustek] ># 0 means leave lamp-status untouched, not 0 means switch 
off<
[plustek] ># on sane_close<
[plustek] >option lOffOnEnd 1<
[plustek] Decoding option >lOffOnEnd<
[plustek] ><
[plustek] >#<
[plustek] ># options to tweak the image start-position<
[plustek] ># (WARNING: there's no internal range check!!!)<
[plustek] >#<
[plustek] ># for the normal scan area<
[plustek] >#<
[plustek] >option posOffX 0<
[plustek] Decoding option >posOffX<
[plustek] >option posOffY 0<
[plustek] Decoding option >posOffY<
[plustek] ><
[plustek] ># for transparencies<
[plustek] >option tpaOffX 0<
[plustek] Decoding option >tpaOffX<
[plustek] >option tpaOffY 0<
[plustek] Decoding option >tpaOffY<
[plustek] ><
[plustek] ># for negatives<
[plustek] >option negOffX 0<
[plustek] Decoding option >negOffX<
[plustek] >option negOffY 0<
[plustek] Decoding option >negOffY<
[plustek] ><
[plustek] >#<
[plustek] ># for setting the calibration strip position<
[plustek] ># (WARNING: there's no internal range check!!!)<
[plustek] ># -1 means use built in<
[plustek] >#<
[plustek] >option posShadingY -1<
[plustek] Decoding option >posShadingY<
[plustek] >option tpaShadingY -1<
[plustek] Decoding option >tpaShadingY<
[plustek] >option negShadingY -1<
[plustek] Decoding option >negShadingY<
[plustek] ><
[plustek] >#<
[plustek] ># to invert the negatives, 0 disables the feature<
[plustek] >#<
[plustek] >option invertNegatives 0<
[plustek] Decoding option >invertNegatives<
[plustek] ><
[plustek] >#<
[plustek] ># to save/restore coarse calibration data<
[plustek] >#<
[plustek] >option cacheCalData 0<
[plustek] Decoding option >cacheCalData<
[plustek] ><
[plustek] >#<
[plustek] ># use alternate calibration routines<
[plustek] >#<
[plustek] >option altCalibration 0<
[plustek] Decoding option >altCalibration<
[plustek] ><
[plustek] >#<
[plustek] ># for skipping whole calibration step<
[plustek] >#<
[plustek] >option skipCalibration 0<
[plustek] Decoding option >skipCalibration<
[plustek] ><
[plustek] >#<
[plustek] ># for skipping entire fine calibration step<
[plustek] ># coarse calibration is done<
[plustek] >#<
[plustek] >option skipFine 0<
[plustek] Decoding option >skipFine<
[plustek] ><
[plustek] >#<
[plustek] ># discard the result of the fine white calibration<
[plustek] >#<
[plustek] >option skipFineWhite 0<
[plustek] Decoding option >skipFineWhite<
[plustek] ><
[plustek] ># for replacing the gain values found during<
[plustek] ># calibration<
[plustek] >option red_gain   -1<
[plustek] Decoding option >red_gain<
[plustek] >option green_gain -1<
[plustek] Decoding option >green_gain<
[plustek] >option blue_gain  -1<
[plustek] Decoding option >blue_gain<
[plustek] ><
[plustek] >#<
[plustek] >#<
[plustek] >option red_lampoff   -1<
[plustek] Decoding option >red_lampoff<
[plustek] >option green_lampoff -1<
[plustek] Decoding option >green_lampoff<
[plustek] >option blue_lampoff  -1<
[plustek] Decoding option >blue_lampoff<
[plustek] ><
[plustek] >#<
[plustek] ># for adjusting the default gamma values<
[plustek] >#<
[plustek] >option redGamma         1.0<
[plustek] Decoding option >redGamma<
[plustek] >option greenGamma       1.0<
[plustek] Decoding option >greenGamma<
[plustek] >option blueGamma        1.0<
[plustek] Decoding option >blueGamma<
[plustek] >option grayGamma        1.0<
[plustek] Decoding option >grayGamma<
[plustek] ><
[plustek] >#<
[plustek] ># to enable TPA (non Plustek devices only)<
[plustek] ># 0 means default behaviour as specified in the internal 
tables<
[plustek] ># 1 means enable<
[plustek] >#<
[plustek] >option enableTPA 0<
[plustek] Decoding option >enableTPA<
[plustek] ><
[plustek] >#<
[plustek] ># model override functionality, currently only available for<
[plustek] ># Mustek devices, using NSCs' vendor ID: 0x0400 and<
[plustek] ># also their product ID: 0x1000 (LM9831) 0x1001 (LM9832)<
[plustek] >#<
[plustek] ># mov/PID    |    0x1000   |   0x1001<
[plustek] ># ---------------------------------------<
[plustek] ># 0 (default)| BearPaw1200 | BearPaw 2400<
[plustek] ># 1          |   ignored   | BearPaw 1200<
[plustek] >#<
[plustek] >option mov 0<
[plustek] Decoding option >mov<
[plustek] ><
[plustek] >#<
[plustek] ># and of course the device-name<
[plustek] >#<
[plustek] ># device /dev/usbscanner<
[plustek] >device auto<
[plustek] Decoding device name >auto<
[plustek] ><
[plustek] >#<
[plustek] ># to define a new device, start with a new section:<
[plustek] ># [usb]<
[plustek] >#<
[plustek] attach (auto, 0xbfbfed24, 0x0)
[plustek] Device configuration:
[plustek] device name  : >auto<
[plustek] USB-ID       : ><
[plustek] model ovr.   : 0
[plustek] warmup       : 15s
[plustek] lampOff      : 309
[plustek] lampOffOnEnd : yes
[plustek] cacheCalData : no
[plustek] altCalibrate : no
[plustek] skipCalibr.  : no
[plustek] skipFine     : no
[plustek] skipFineWhite: no
[plustek] invertNegs.  : no
[plustek] pos_x        : 0
[plustek] pos_y        : 0
[plustek] pos_shading_y: -1
[plustek] neg_x        : 0
[plustek] neg_y        : 0
[plustek] neg_shading_y: -1
[plustek] tpa_x        : 0
[plustek] tpa_y        : 0
[plustek] tpa_shading_y: -1
[plustek] red gain     : -1
[plustek] green gain   : -1
[plustek] blue gain    : -1
[plustek] red lampoff  : -1
[plustek] green lampoff: -1
[plustek] blue lampoff : -1
[plustek] red Gamma    : 1.00
[plustek] green Gamma  : 1.00
[plustek] blue Gamma   : 1.00
[plustek] gray Gamma   : 1.00
[plustek] ---------------------
[plustek] usbDev_open(auto,)
[plustek] Autodetection...
[plustek] Checking for 0x07b3-0x0010
[plustek] Checking for 0x07b3-0x0011
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0015
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0013
[plustek] Checking for 0x07b3-0x0013
[plustek] Checking for 0x07b3-0x0011
[plustek] Checking for 0x07b3-0x0010
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0015
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0016
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0007
[plustek] Checking for 0x07b3-0x000f
[plustek] Checking for 0x07b3-0x000f
[plustek] Checking for 0x07b3-0x0005
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0012
[plustek] Checking for 0x0400-0x1000
[plustek] Checking for 0x0400-0x1001
[plustek] Checking for 0x0400-0x1001
[plustek] Checking for 0x0458-0x2007
[plustek] Checking for 0x0458-0x2008
[plustek] Checking for 0x0458-0x2009
[plustek] Checking for 0x0458-0x2013
[plustek] Checking for 0x0458-0x2015
[plustek] Checking for 0x0458-0x2016
[plustek] Checking for 0x03f0-0x0505
[plustek] Checking for 0x03f0-0x0605
[plustek] Checking for 0x04b8-0x010f
[plustek] Found device at >/dev/uscanner0<
[plustek] Vendor ID=0x04B8, Product ID=0x010F
[plustek] usbio_DetectLM983x
[plustek] usbio_DetectLM983x: found LM9832/3
[plustek] Detected vendor & product ID: 0x04B8-0x010F
[plustek] Device description for >0x04B8-0x010F< found.
[plustek] usb_initDev(32,0x04b8,-1)
[plustek] Device WAF: 0x00000002
[plustek] usb_switchLampX(ON=0,TPA=1)
[plustek] Switch Lamp: 0, regs[0x59] = 0x00
[plustek] REG[0x02] = 0x81
[plustek] TPA NOT detected
[plustek] Vendor adjusted to: >Epson<
[plustek] REG[0x5b] = 0x14 (msk=0x80)
[plustek] LAMP-STATUS: 0x00000000
[plustek] RESETTING REGISTERS(-1)
[plustek] SETTING THE MISC I/Os
[plustek] MISC I/O after RESET: 0x41, 0x44, 0x14
[plustek] Calibration file-name set to:
[plustek] >/root/.sane/Epson-Perfection_1250_Photo.cal<
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 8.000
[plustek] * XDPI=150, HDPI=8.000
[plustek] * YDPI=150, MinDPIY=150
[plustek] * DataPixelStart=69, LineEnd=69
[plustek] * DataPixelStart=70, LineEnd=70 (ADJ)
[plustek] >> End-Start=0, HDPI=8.00
[plustek] * Full Steps to Skip at Start = 0x0000
[plustek] * StepSize(Preset) = 231 (0x00e7)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 675, 0x46=0x02 0x47=0xa3
[plustek] * DPD =5568 (0x15c0)
[plustek] * DPD =5208 (0x1458), step size=675, steps2rev=30
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 0 (HDPI=8.000,MCLKD=4.000)
[plustek] * Setting GreenPWMDutyCycleLow
[plustek] * Current MCLK Divider = 4.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 260, [0x48] = 0x01, [0x49] = 0x04
[plustek] * PhyBytes   = 2
[plustek] * PhyLines   = 1296834662
[plustek] * TotalBytes = 2593669324
[plustek] * PL=295, coeffsize=216, scaler=1
[plustek] * PauseLimit = 295, [0x4e] = 0x91, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] usbDev_getCaps()
[plustek] Scanner information:
[plustek] Vendor : Epson
[plustek] Model  : Perfection 1250/Photo
[plustek] Flags  : 0x00000000
[plustek] drvclose()
[plustek] usbDev_stopScan()
[plustek] usbDev_ScanEnd(), start=0, park=0
[plustek] usbDev_close()
[plustek] attach: model = >Perfection 1250/Photo<
[plustek] sane_open - /dev/uscanner0
[plustek] Presetting Gamma tables (len=4096)
[plustek] * Channel[0], gamma 1.000
[plustek] * Channel[1], gamma 1.000
[plustek] * Channel[2], gamma 1.000
[plustek] * Channel[3], gamma 1.000
[plustek] ----------------------------------
[plustek] sane_start
[plustek] usbDev_open(/dev/uscanner0,)
[plustek] Vendor ID=0x04B8, Product ID=0x010F
[plustek] usbio_DetectLM983x
[plustek] usbio_DetectLM983x: found LM9832/3
[plustek] Detected vendor & product ID: 0x04B8-0x010F
[plustek] Device description for >0x04B8-0x010F< found.
[plustek] usb_initDev(32,0x04b8,32)
[plustek] Device WAF: 0x00000002
[plustek] Vendor adjusted to: >Epson<
[plustek] REG[0x5b] = 0x14 (msk=0x80)
[plustek] REG[0x59] = 0x41 (msk=0x08)
[plustek] LAMP-STATUS: 0x00000000
[plustek] RESETTING REGISTERS(32)
[plustek] USING MISC I/O settings
[plustek] MISC I/O after RESET: 0x41, 0x44, 0x14
[plustek] usbDev_getCaps()
[plustek] scanmode = 3
[plustek] usbDev_getCropInfo()
[plustek] usb_GetImageInfo()
[plustek] PPL = 590
[plustek] LPA = 590
[plustek] BPL = 1770
[plustek] brightness 0, contrast 0
[plustek] usbDev_setScanEnv()
[plustek] usb_SaveImageInfo()
[plustek] dwFlag = 0x00000400
[plustek] usb_GetImageInfo()
[plustek] * Preview Mode NOT set!
[plustek] Setting map[0] at 0x08061094
[plustek] Setting map[1] at 0x08065094
[plustek] Setting map[2] at 0x08069094
[plustek] usbDev_startScan()
[plustek] * HDPI: 8.000
[plustek] * XDPI=150, HDPI=8.000
[plustek] * YDPI=150, MinDPIY=150
[plustek] REG[0x5b] = 0x14 (msk=0x80)
[plustek] REG[0x59] = 0x41 (msk=0x08)
[plustek] LAMP-STATUS: 0x00000000
[plustek] Switching Lamp on
[plustek] usb_switchLampX(ON=0,TPA=1)
[plustek] Switch Lamp: 0, regs[0x59] = 0x41
[plustek] usb_switchLampX(ON=1,TPA=0)
[plustek] Switch Lamp: 1, regs[0x5b] = 0x94
[plustek] Warmup-Timer started
[plustek] REG[0x5b] = 0x94 (msk=0x80)
[plustek] REG[0x59] = 0x41 (msk=0x08)
[plustek] LAMP-STATUS: 0x00000001
[plustek] Lamp-Timer stopped
[plustek] dwflag = 0x40000400 dwBytesPerLine = 1770
[plustek] TIME START
[plustek] sane_start done
[plustek] reader_process started (forked)
[plustek] reader_process:starting to READ data (1044300 bytes)
[plustek] buf = 0x0886e000
[plustek] usbDev_PrepareScan()
[plustek] usb_DoCalibration()
[plustek] goto shading position
[plustek] ShadingOriginY=10
[plustek] MotorDPI=600, MaxMoveSpeed=0.800, FFStepSize=520, Steps=20
[plustek] MOTOR: PWM=0x02, PWM_DUTY=0x01 0x45=0x13 0x48=0x02, 0x49=0x08
[plustek] MCLK_FFW = 6 --> 0x0a
[plustek] shading position reached
[plustek] kEPSON adjustments
[plustek] SETMCLK[3/2], using entry 8: 6.000000, 1200
[plustek] No Plustek model: 150dpi
[plustek] SETMCLK[3/2], using entry 2: 2.000000, 150
[plustek] Settings done, so start...
[plustek] ###### ADJUST GAIN (COARSE)#######
[plustek] usb_AdjustGain()
[plustek] Coarse Calibration Strip:
[plustek] Lines    = 1
[plustek] Pixels   = 10200
[plustek] Bytes    = 61200
[plustek] Origin.X = 17
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 1.000
[plustek] * XDPI=1200, HDPI=1.000
[plustek] * YDPI=1200, MinDPIY=150
[plustek] * DataPixelStart=68, LineEnd=10268
[plustek] >> End-Start=10200, HDPI=1.00
[plustek] * Full Steps to Skip at Start = 0x0000
[plustek] * StepSize(Preset) = 462 (0x01ce)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 5406, 0x46=0x15 0x47=0x1e
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=5406, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 3 (HDPI=1.000,MCLKD=2.000)
[plustek] * Stepsize = 7208, 0x46=0x1c 0x47=0x28
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=7208, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] * Setting GreenPWMDutyCycleHigh
[plustek] * Current MCLK Divider = 2.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 173, [0x48] = 0x00, [0x49] = 0xad
[plustek] * PhyBytes   = 61202
[plustek] * PhyLines   = 1
[plustek] * TotalBytes = 61202
[plustek] * PL=260, coeffsize=192, scaler=1
[plustek] * PauseLimit = 60, [0x4e] = 0x1c, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] Warmup: Waiting 15 seconds
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(1)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 20 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 44 28 1c 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  00 00 00 01 01 01 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 1c 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 00 65 18 e1 02 06 a8 48  00 04 00 00 50 00 00 02
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] PhyBytes  = 61202
[plustek] PhyPixels = 10200
[plustek] Creating file 'coarse-gain-0.raw'
[plustek] > X=10200, Y=1, depth=16
[plustek] MAX(R,G,B)= 0x2935(10549), 0x23a5(9125), 0x268e(9870)
[plustek] MIN(R,G,B)= 0x000e(14), 0x0015(21), 0x030e(782)
[plustek] CUR(R,G,B)= 0x2935(10549), 0x23a5(9125), 0x268e(9870)
[plustek] REG[0x3b] = 47
[plustek] REG[0x3c] = 51
[plustek] REG[0x3d] = 48
[plustek] after tweaking:
[plustek] REG[0x3b] = 47
[plustek] REG[0x3c] = 51
[plustek] REG[0x3d] = 48
[plustek] red_lamp_on    = 16383
[plustek] red_lamp_off   = 0
[plustek] green_lamp_on  = 16383
[plustek] green_lamp_off = 0
[plustek] blue_lamp_on   = 16383
[plustek] blue_lamp_off  = 0
[plustek] usb_AdjustGain() done.
[plustek] ###### ADJUST OFFSET (COARSE) ####
[plustek] usb_AdjustOffset()
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 1.000
[plustek] * XDPI=1200, HDPI=1.000
[plustek] * YDPI=1200, MinDPIY=150
[plustek] * DataPixelStart=0, LineEnd=2550
[plustek] >> End-Start=2550, HDPI=1.00
[plustek] * Full Steps to Skip at Start = 0x0000
[plustek] * StepSize(Preset) = 462 (0x01ce)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 5406, 0x46=0x15 0x47=0x1e
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=5406, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 3 (HDPI=1.000,MCLKD=2.000)
[plustek] * Stepsize = 7208, 0x46=0x1c 0x47=0x28
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=7208, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] * Setting GreenPWMDutyCycleHigh
[plustek] * Current MCLK Divider = 2.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 173, [0x48] = 0x00, [0x49] = 0xad
[plustek] * PhyBytes   = 15302
[plustek] * PhyLines   = 1
[plustek] * TotalBytes = 15302
[plustek] * PL=305, coeffsize=192, scaler=1
[plustek] * PauseLimit = 15, [0x4e] = 0x05, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] S.dwPixels  = 2550
[plustek] dwPixels    = 66
[plustek] dwPhyBytes  = 15302
[plustek] dwPhyPixels = 2550
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(4)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 00 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 00 09 f6 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  00 00 00 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 05 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 50 60 28 5c 02 04 a8 48  00 04 00 00 50 00 00 02
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Creating file 'coarse-off-0.raw'
[plustek] > X=2550, Y=1, depth=16
[plustek] RedSum   = 327621, ave = 4963
[plustek] GreenSum = 430626, ave = 6524
[plustek] BlueSum  = 528886, ave = 8013
[plustek] RedExpect   = 0
[plustek] GreenExpect = 0
[plustek] BlueExpect  = 0
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(4)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 10 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 00 09 f6 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  30 30 30 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 05 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 60 60 18 60 32 46 a4 48  00 04 00 00 50 00 00 02
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Creating file 'coarse-off-1.raw'
[plustek] > X=2550, Y=1, depth=16
[plustek] RedSum   = 0, ave = 0
[plustek] GreenSum = 0, ave = 0
[plustek] BlueSum  = 0, ave = 0
[plustek] RedExpect   = 0
[plustek] GreenExpect = 0
[plustek] BlueExpect  = 0
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(4)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 10 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 00 09 f6 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  28 28 28 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 05 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 60 62 18 48 6e 06 00 48  00 04 00 00 70 00 00 06
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Creating file 'coarse-off-2.raw'
[plustek] > X=2550, Y=1, depth=16
[plustek] RedSum   = 15116, ave = 229
[plustek] GreenSum = 67860, ave = 1028
[plustek] BlueSum  = 201515, ave = 3053
[plustek] RedExpect   = 0
[plustek] GreenExpect = 0
[plustek] BlueExpect  = 40
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(4)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 00 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 00 09 f6 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  24 24 24 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 05 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 50 22 2a 30 68 04 00 80  00 04 00 00 90 00 00 08
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Creating file 'coarse-off-3.raw'
[plustek] > X=2550, Y=1, depth=16
[plustek] RedSum   = 162770, ave = 2466
[plustek] GreenSum = 247130, ave = 3744
[plustek] BlueSum  = 365514, ave = 5538
[plustek] RedExpect   = 0
[plustek] GreenExpect = 36
[plustek] BlueExpect  = 40
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(4)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 10 00 XX XX 03  02 20 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 03 00 01 00 00 00 00
[plustek] 0x20: 2a 06 00 00 09 f6 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  22 22 26 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 1c 28  00 ad 00 00 00 00 05 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 60 65 18 87 62 06 40 48  00 04 00 00 10 00 00 04
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Creating file 'coarse-off-4.raw'
[plustek] > X=2550, Y=1, depth=16
[plustek] RedSum   = 245858, ave = 3725
[plustek] GreenSum = 329596, ave = 4993
[plustek] BlueSum  = 284178, ave = 4305
[plustek] RedExpect   = 34
[plustek] GreenExpect = 36
[plustek] BlueExpect  = 38
[plustek] REG[0x38] = 34
[plustek] REG[0x39] = 36
[plustek] REG[0x3a] = 38
[plustek] usb_AdjustOffset() done.
[plustek] ###### ADJUST DARK (FINE) ########
[plustek] usb_AdjustDarkShading()
[plustek] MCLK = 2.000000 (scanparam-MCLK=2.000000)
[plustek] usb_switchLampX(ON=0,TPA=0)
[plustek] Switch Lamp: 0, regs[0x5b] = 0x14
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 8.000
[plustek] * XDPI=150, HDPI=8.000
[plustek] * YDPI=1200, MinDPIY=150
[plustek] * DataPixelStart=641, LineEnd=5361
[plustek] * DataPixelStart=642, LineEnd=5362 (ADJ)
[plustek] >> End-Start=4720, HDPI=8.00
[plustek] * Full Steps to Skip at Start = 0x0000
[plustek] * StepSize(Preset) = 462 (0x01ce)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 5406, 0x46=0x15 0x47=0x1e
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=5406, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 0 (HDPI=8.000,MCLKD=2.000)
[plustek] * Setting GreenPWMDutyCycleHigh
[plustek] * Current MCLK Divider = 2.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 520, [0x48] = 0x02, [0x49] = 0x08
[plustek] * PhyBytes   = 3542
[plustek] * PhyLines   = 1
[plustek] * TotalBytes = 3542
[plustek] * PL=316, coeffsize=192, scaler=1
[plustek] * PauseLimit = 4, [0x4e] = 0x01, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(2)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 87 00 01 XX XX 03  02 26 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 00 00 01 00 00 00 00
[plustek] 0x20: 2a 06 02 82 14 f2 00 40  03 00 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  22 24 26 2f 33 30 00 00
[plustek] 0x40: 40 00 20 00 00 03 15 1e  02 08 00 00 00 00 01 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 14 00 00 00 00
[plustek] 0x60: 60 25 18 eb 32 46 28 80  00 04 00 00 d0 00 00 0e
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] usb_switchLampX(ON=1,TPA=0)
[plustek] Switch Lamp: 1, regs[0x5b] = 0x94
[plustek] Creating file 'fine-black.raw'
[plustek] > X=590, Y=1, depth=16
[plustek] Color[0] (Dark) : min=56352(0) max=56352(0) ave=56352
[plustek] 5%: 53534 (0), 59169 (0)
[plustek] Color[1] (Dark) : min=8994(0) max=8994(0) ave=8994
[plustek] 5%: 8544 (0), 9443 (0)
[plustek] Color[2] (Dark) : min=38436(0) max=38436(0) ave=38436
[plustek] 5%: 36514 (0), 40357 (0)
[plustek] ###### ADJUST WHITE (FINE) #######
[plustek] FINE WHITE Calibration Strip: fine-white.raw
[plustek] Shad.-Lines = 64
[plustek] Lines       = 64
[plustek] Pixels      = 590
[plustek] Bytes       = 3540
[plustek] Origin.X    = 143
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 8.000
[plustek] * XDPI=150, HDPI=8.000
[plustek] * YDPI=1200, MinDPIY=150
[plustek] * DataPixelStart=641, LineEnd=5361
[plustek] * DataPixelStart=642, LineEnd=5362 (ADJ)
[plustek] >> End-Start=4720, HDPI=8.00
[plustek] * Full Steps to Skip at Start = 0x0000
[plustek] * StepSize(Preset) = 462 (0x01ce)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 5406, 0x46=0x15 0x47=0x1e
[plustek] * DPD =0 (0x0000)
[plustek] * DPD =10776 (0x2a18), step size=5406, steps2rev=0
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 0 (HDPI=8.000,MCLKD=2.000)
[plustek] * Setting GreenPWMDutyCycleHigh
[plustek] * Current MCLK Divider = 2.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 520, [0x48] = 0x02, [0x49] = 0x08
[plustek] * PhyBytes   = 3542
[plustek] * PhyLines   = 64
[plustek] * TotalBytes = 226688
[plustek] * PL=316, coeffsize=192, scaler=1
[plustek] * PauseLimit = 222, [0x4e] = 0x6d, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] usb_ScanBegin()
[plustek] usb_DownloadShadingData(3)
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 07 08 00 XX XX 03  02 26 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 00 00 01 00 00 00 00
[plustek] 0x20: 2a 06 02 82 14 f2 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  22 24 26 2f 33 30 00 00
[plustek] 0x40: 40 00 24 00 00 13 15 1e  02 08 00 00 00 00 6d 01
[plustek] 0x50: 00 0c 2a 18 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 50 20 2b f3 32 44 a8 80  00 04 00 00 d0 00 00 00
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] TotalBytes = 226688
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] Creating file 'fine-white.raw'
[plustek] > X=590, Y=64, depth=16
[plustek] usbDev_ScanEnd(), start=1, park=0
[plustek] Color[0] (White) : min=81(155) max=65360(163) ave=35351
[plustek] 5%: 33583 (264), 37118 (299)
[plustek] Color[1] (White) : min=85(193) max=65107(84) ave=31459
[plustek] 5%: 29886 (291), 33031 (263)
[plustek] Color[2] (White) : min=82(500) max=65369(327) ave=32522
[plustek] 5%: 30895 (278), 34148 (278)
[plustek] MotorDPI=600, MaxMoveSpeed=0.800, FFStepSize=520, Steps=2
[plustek] MOTOR: PWM=0x02, PWM_DUTY=0x01 0x45=0x13 0x48=0x02, 0x49=0x08
[plustek] MCLK_FFW = 6 --> 0x0a
[plustek] MotorDPI=600, MaxMotorSpeed=0.900, FFStepSize=462
[plustek] MOTOR: PWM=0x02, PWM_DUTY=0x01 0x45=0x13 0x48=0x01, 0x49=0xce
[plustek] MCLK_FFW = 6 --> 0x0a
[plustek] Calibration done
[plustek] -----------------------
[plustek] Static Gain:
[plustek] REG[0x3b] = 47
[plustek] REG[0x3c] = 51
[plustek] REG[0x3d] = 48
[plustek] Static Offset:
[plustek] REG[0x38] = 34
[plustek] REG[0x39] = 36
[plustek] REG[0x3a] = 38
[plustek] -----------------------
[plustek] calibration done.
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 8.000
[plustek] * XDPI=150, HDPI=8.000
[plustek] * YDPI=150, MinDPIY=150
[plustek] * DataPixelStart=641, LineEnd=5361
[plustek] * DataPixelStart=642, LineEnd=5362 (ADJ)
[plustek] >> End-Start=4720, HDPI=8.00
[plustek] * Full Steps to Skip at Start = 0x0196
[plustek] * StepSize(Preset) = 462 (0x01ce)
[plustek] * Scan calculations...
[plustek] * LineLength=10776, LineRateColor=1
[plustek] * Stepsize = 675, 0x46=0x02 0x47=0xa3
[plustek] * DPD =5568 (0x15c0)
[plustek] * DPD =5208 (0x1458), step size=675, steps2rev=30
[plustek] * llen=10776, lineRateColor=1, qtcnt=0, hfcnt=0
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 0 (HDPI=8.000,MCLKD=2.000)
[plustek] * Setting GreenPWMDutyCycleHigh
[plustek] * Current MCLK Divider = 2.000000
[plustek] * MOTOR-Settings: PWM=0x02, PWM_DUTY=0x01
[plustek] * FFStepSize = 520, [0x48] = 0x02, [0x49] = 0x08
[plustek] * PhyBytes   = 1772
[plustek] * PhyLines   = 592
[plustek] * TotalBytes = 1049024
[plustek] * PL=294, coeffsize=216, scaler=1
[plustek] * PauseLimit = 294, [0x4e] = 0x91, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] ImageProc is: ColorDuplicate8
[plustek] usb_ScanBegin()
[plustek] usb_MapDownload()
[plustek] * brightness = 0 -> 0
[plustek] * contrast   = 0 -> 1.000
[plustek] * downloading map 0...
[plustek] * downloading map 1...
[plustek] * downloading map 2...
[plustek] usb_MapDownload() done.
[plustek] usb_DownloadShadingData(0)
[plustek] Downloading 590 pixels
[plustek] Register Dump before reading data:
[plustek] 0x00: XX 00 06 09 00 XX XX 03  02 1e 00 02 04 7d 37 06
[plustek] 0x10: 16 00 05 0c 17 00 00 0a  17 00 00 01 00 00 00 00
[plustek] 0x20: 2a 06 02 82 14 f2 00 40  03 03 00 01 3f ff 00 00
[plustek] 0x30: 3f ff 00 00 3f ff 00 00  22 24 26 2f 33 30 00 00
[plustek] 0x40: 40 00 26 00 00 13 02 a3  02 08 01 96 00 00 91 01
[plustek] 0x50: 1e 0c 14 58 00 0f 02 01  00 41 44 94 00 00 00 00
[plustek] 0x60: 40 20 0c c7 32 44 26 48  00 04 00 00 b0 00 00 00
[plustek] 0x70: 00 00 00 00 30 00 00 00  00 00 00 00 00 00 00 00
[plustek] Creating file 'plustek-pic.raw'
[plustek] > X=590, Y=590, depth=8
[plustek] Reading the data now!
[plustek] PhyDpi.x         = 150
[plustek] PhyDpi.y         = 150
[plustek] UserDpi.x        = 150
[plustek] UserDpi.y        = 150
[plustek] NumberOfScanBufs = 2366
[plustek] LinesPerScanBufs = 4732
[plustek] dwPhyBytes       = 1772
[plustek] dwPhyPixels      = 590
[plustek] dwTotalBytes     = 1049024
[plustek] dwPixels         = 590
[plustek] dwBytes          = 1770
[plustek] dwValidPixels    = 590
[plustek] dwBytesScanBuf   = 3544
[plustek] dwLinesDiscard   = 2
[plustek] dwLinesToSkip    = 3
[plustek] dwLinesUser      = 590
[plustek] dwBytesLine      = 1770
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available
[plustek] drvclose()
[plustek] TIME END 1: 31s
[plustek] usbDev_stopScan()
[plustek] usbDev_ScanEnd(), start=1, park=1
[plustek] reader_process: finished reading data
[plustek] (SIG) Child is down (signal=20)
scanimage: received signal 2
scanimage: trying to stop scanner
[plustek] sane_cancel
[plustek] do_cancel
[plustek] >>>>>>>> killing reader_process <<<<<<<<
[plustek] reader_process killed
[plustek] drvclose()
[plustek] TIME END 1: 260s
[plustek] usbDev_stopScan()
[plustek] usbDev_ScanEnd(), start=1, park=1
[plustek] UIO error
[plustek] UIO error
[plustek] UIO error
[plustek] Lamp-Timer started (using ITIMER)
[plustek] usbDev_close()
[plustek] TIME END 2: 268s
scanimage: received signal 2
scanimage: aborting




From artpi at ptic.pl  Thu Oct 28 11:43:08 2004
From: artpi at ptic.pl (Artur Pierscinski)
Date: Thu, 28 Oct 2004 12:43:08 +0200
Subject: [sane-devel] genesys backend - warming up procedure
In-Reply-To: <200410271746.29865.gerhard@gjaeger.de>
References: <417FAA47.2010903@ptic.pl> <200410271746.29865.gerhard@gjaeger.de>
Message-ID: <4180CD3C.5090705@ptic.pl>

Gerhard Jaeger wrote:

>On Mittwoch 27 Oktober 2004 16:01, Artur Pierscinski wrote:
>  
>
>> <>
>> Hi,
>>
>> I've done some tests here with the ST24 and rewrote some parts of
>> the code, that the warmup and calibration stuff gets passed on it.
>> The major problem of the current genesys code is, that it is tied to
>> a UMAX device. All the settings specific to CCD and DAC (and motor)
>> are only valid for this scanner. This needs to be tweaked. I did this
>> here, but the code is not available so far ....
>>
>> Gerhard
>>
Thats is fine. May I help in something?
So there is almost no traffic in experimental cvs, so its like as no any 
progress.

So, the matter is I as expected---code is device (UMAX) expected; Your 
answer
clears my assumptions.

Artur Pierscinski



From whitemanor at netzero.net  Thu Oct 28 14:26:12 2004
From: whitemanor at netzero.net (Bensel)
Date: Thu, 28 Oct 2004 09:26:12 -0400
Subject: [sane-devel] Help with compiler error
Message-ID: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>

We are trying to get a Memorex MEM 48u scanner working with Linspire 4.5.393.  It is suppose to work with the artec_eplus48u backend so we downloaded sane-backends-1.0.14.  When we run ./configure, we get the error: no acceptable C compiler found in $PATH.  We understand the ANSI C Compiler: GNU C (gcc) is recommended.  Could someone advise how we should proceed from here.  Thanks for your advice and help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041028/b92ee600/attachment.htm>

From anoah at pfeiffer.edu  Thu Oct 28 14:40:27 2004
From: anoah at pfeiffer.edu (m. allan noah)
Date: Thu, 28 Oct 2004 09:40:27 -0400 (EDT)
Subject: [sane-devel] Help with compiler error
In-Reply-To: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>
References: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>
Message-ID: <Pine.LNX.4.61.0410280938500.17000@limos.pfeiffer.edu>

umm, install a compiler package for your os? if you have one, and 
comfigure could not find it, then you either need to change your path. you 
might also need to see the CC= environment var if your compiler has a 
funny name.

allan

On Thu, 28 Oct 2004, Bensel wrote:

> We are trying to get a Memorex MEM 48u scanner working with Linspire 4.5.393.  It is suppose to work with the artec_eplus48u backend so we downloaded sane-backends-1.0.14.  When we run ./configure, we get the error: no acceptable C compiler found in $PATH.  We understand the ANSI C Compiler: GNU C (gcc) is recommended.  Could someone advise how we should proceed from here.  Thanks for your advice and help.
>

-- 
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera



From gerhard at gjaeger.de  Thu Oct 28 13:54:09 2004
From: gerhard at gjaeger.de (Gerhard Jaeger)
Date: Thu, 28 Oct 2004 14:54:09 +0200
Subject: [sane-devel] genesys backend - warming up procedure
In-Reply-To: <4180CD3C.5090705@ptic.pl>
References: <417FAA47.2010903@ptic.pl> <200410271746.29865.gerhard@gjaeger.de> <4180CD3C.5090705@ptic.pl>
Message-ID: <200410281454.09348.gerhard@gjaeger.de>

On Donnerstag 28 Oktober 2004 12:43, Artur Pierscinski wrote:
> Gerhard Jaeger wrote:
> >On Mittwoch 27 Oktober 2004 16:01, Artur Pierscinski wrote:
> >> <>
> >> Hi,
> >>
> >> I've done some tests here with the ST24 and rewrote some parts of
> >> the code, that the warmup and calibration stuff gets passed on it.
> >> The major problem of the current genesys code is, that it is tied to
> >> a UMAX device. All the settings specific to CCD and DAC (and motor)
> >> are only valid for this scanner. This needs to be tweaked. I did this
> >> here, but the code is not available so far ....
> >>
> >> Gerhard
>
> Thats is fine. May I help in something?
> So there is almost no traffic in experimental cvs, so its like as no any
> progress.

That's probably not true, I think Henning is still working on that.
I didn't want to check in my code, as there are too much changes, that
have not been discussed with Henning. Maybe I add a new directory

> So, the matter is I as expected---code is device (UMAX) expected; Your
> answer clears my assumptions.
--
  Gerhard




From gerard at gkall.hobby.nl  Thu Oct 28 17:02:45 2004
From: gerard at gkall.hobby.nl (gerard klaver)
Date: Thu, 28 Oct 2004 16:02:45 +0000
Subject: [sane-devel] Help with compiler error
In-Reply-To: <Pine.LNX.4.61.0410280938500.17000@limos.pfeiffer.edu>
References: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>
	 <Pine.LNX.4.61.0410280938500.17000@limos.pfeiffer.edu>
Message-ID: <1098979365.4560.8.camel@gk-lex3>

check the linspire website and search for gcc

which version you should install?

their sane-backends (libsane) version is 1.0.12 ..... a bit old, don't
know if the support for your scanner is included.


On Thu, 2004-10-28 at 13:40, m. allan noah wrote:
> umm, install a compiler package for your os? if you have one, and 
> comfigure could not find it, then you either need to change your path. you 
> might also need to see the CC= environment var if your compiler has a 
> funny name.
> 
> allan
> 
> On Thu, 28 Oct 2004, Bensel wrote:
> 
> > We are trying to get a Memorex MEM 48u scanner working with Linspire 4.5.393.  It is suppose to work with the artec_eplus48u backend so we downloaded sane-backends-1.0.14.  When we run ./configure, we get the error: no acceptable C compiler found in $PATH.  We understand the ANSI C Compiler: GNU C (gcc) is recommended.  Could someone advise how we should proceed from here.  Thanks for your advice and help.
> >
> 


-- 
----------
m.vr.gr.
Gerard Klaver




From marc at electronics-design.nl  Thu Oct 28 16:24:24 2004
From: marc at electronics-design.nl (Marc Dirix)
Date: Thu, 28 Oct 2004 17:24:24 +0200
Subject: [sane-devel] Parallel Scanning and Printing
Message-ID: <20041028152424.GB26359@angus.electronics-design.nl>

I have an Canoscan N640P, which works fine with sane/xsane.
The interface is parallel, and on the scanner there is printer
throughput which also is working fine.

However, and I don't know if this should be solved in the backend
or in sane, when I use the copy mode of Xsane, or even if Xsane
is opened the printer doesn't work anymore. I need to close xsane 
and then te printjob starts. Probably xsane opens the backend and keeps 
the connecting live with the scanner while open.

I can think of 2 sollutions for this problem, either xsane let's go of the 
scanner when it isn't using the device, or the backend should detect 
a printjob is waiting and disconnect from the scanner.

Is there anyone else experiencing this problem? Is there already a sollution
for this? If not, which sollution is best, and where should I start looking?

versions:
sane  1.0.13-1 (Debian unstable)
xsane 0.96-1 (Debian unstable)

Kind regards,

Marc



From alej82 at yahoo.es  Thu Oct 28 17:32:06 2004
From: alej82 at yahoo.es (=?iso-8859-1?q?Alejandro=20Reche=20P=E9rez?=)
Date: Thu, 28 Oct 2004 18:32:06 +0200 (CEST)
Subject: [sane-devel] HP ScanJet 3670
Message-ID: <20041028163206.82423.qmail@web20925.mail.yahoo.com>

Hi,

we would like to make a driver for the Hewlett Packard
 ScanJet 3670 which is currently unsuported by sane.

So we would like to know where to find more
information than the one that can be found in the sane
site. Also if we can find the scanner especifications
somewhere or we have to ask them to HP.
Finally if there is anybdoy else also trying to do
this driver, please tell us.

Thanks in advance and sorry for our bad english.
Greetings.




		
______________________________________________
Renovamos el Correo Yahoo!: ?100 MB GRATIS!
Nuevos servicios, m?s seguridad
http://correo.yahoo.es



From gerard at gkall.hobby.nl  Thu Oct 28 20:07:02 2004
From: gerard at gkall.hobby.nl (gerard klaver)
Date: Thu, 28 Oct 2004 19:07:02 +0000
Subject: [sane-devel] HP ScanJet 3670
In-Reply-To: <20041028163206.82423.qmail@web20925.mail.yahoo.com>
References: <20041028163206.82423.qmail@web20925.mail.yahoo.com>
Message-ID: <1098990422.4560.17.camel@gk-lex3>

On Thu, 2004-10-28 at 16:32, Alejandro Reche P?rez wrote:
> Hi,
> 
> we would like to make a driver for the Hewlett Packard
>  ScanJet 3670 which is currently unsuported by sane.
> 
> So we would like to know where to find more
> information than the one that can be found in the sane
> site. Also if we can find the scanner especifications
> somewhere or we have to ask them to HP.
> Finally if there is anybdoy else also trying to do
> this driver, please tell us.
> 
You mist some pages i think?

Did you check this page (with link to datasheet scanner chip):
http://www.meier-geinitz.de/sane/genesys-backend/

and links on this page?

http://www.sane-project.org/unsupported/hp-scanjet-3670c.html

and the files on

http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/experimental/genesys/?cvsroot=sane

But i could be wrong.

-- 
----------
m.vr.gr.
Gerard Klaver




From hvengel at astound.net  Wed Oct 27 21:04:00 2004
From: hvengel at astound.net (Hal V. Engel)
Date: Wed, 27 Oct 2004 13:04:00 -0700
Subject: [sane-devel] lprof and sane, was [Lcms-user] monitor profile questions -- adding vcgt to a profile?
In-Reply-To: <1098880586.2799.16.camel@gk-lex3>
References: <200410191019.i9JAJu1W025691@web218.megawebservers.com> <1098880586.2799.16.camel@gk-lex3>
Message-ID: <200410271304.08843.hvengel@astound.net>

In the sane-devel mailing list on 27 Jul, 2003 Gerard Klaver wrote (see 
http://www.mostang.com/pipermail/sane-devel/2003-July/008334.html):

?I think it (meaning lprof) should be nice if this package could be 
used as a short of plugin package in the sane frontends. But maybe i 
am wrong??

I think this is right on the money.  The lprof scanner profiler would 
likely need some modification to make it a plugin but most of the 
functionality would be usable as is.  In addition the front end(s) 
would need to be enhanced to embed profiles and do conversions between 
profiles.  

I have two scanner packages that are ICC aware.  On Windows I have 
SilverFast AI.  SilverFast AI will use the device profile to convert 
the image to your selected working profile as part of the scanning 
process.  It also has an optional feature that will let you create 
custom profiles using an IT8 target.  I also have Vuescan Professional 
on both Windows and Linux.  Vuescan Pro has the ability to use ICC 
profiles and functions like SilverFast where you specify both a device 
and working profile and your images are output having been converted 
to the working profile.  Vuescan Pro can also create scanner profiles 
using an IT8 target.  I believe that Vuescan uses the SANE back end on 
linux.  So this functionality belongs in the front end.

Also scanners and cameras are almost trivial to profile.  All you need 
is a good target, the targets data file and some software and almost 
any user can get a good profile.  With a properly designed front end 
it should be easy for almost any user to use this functionality.

Hal


On Wednesday 27 October 2004 05:36, gerard klaver wrote:
> On Tue, 2004-10-19 at 10:19, marti at littlecms.com wrote:
> > Hi,
> > 
> > > >Are the reasons known? Just curious..
> > 
> > 
> > As Gerhard already noted, I am not allowed to support or maintain 
> > the lprof package anymore. The reasons are the company I work 
> > for (HP) acquired the sources for its internal use. 
> > 
> > Moreover, the technology I was using in the latest profilers (not 
> > lprof, but what intended to sell as professional package) is 
> > "sensible" in terms my non-disclosure agreement. So, I 
> > sacrificed this package in order to keep lcms (the CMM) alive 
> > and well. 
> > 
> > HP kindly allow me to continue the development of lcms as 
> > open source and even more, they does SUPPORT this development. 
> > In such way I have contact with ICC members, access to restricted 
> > documents, proposed extensions, etc.
> > 
> > So, I'm very sorry for that, but lprof is now effectively dead. 
> > At least as open source. It would be nice, however, if anybody 
> > would take the sources and continue with the development. But as 
said, 
> > I am not allowed to do that anymore.
> > 
> > King regards,
> > Marti.
> > 
> Hello,
> 
> To keep the lprof package available i have placed the lprof files and
> other information from Marti old profilers page on my homepage.
> See http://gkall.hobby.nl/sane-lprof/sane-lprof.html
> 
> Goal is to maintain the package as good as possible but time and/or
> knowledge can be a problem. Also if more people are interested in
> maintaining this package, let me know.
> Then maintenance depends not on a single person and placing it in the
> SANE CVS tree (sane-lprof or first sane/experimental/sane-lprof) is a
> good option. See als SANE Bugreport 30181.
>  
> In this way more people are be able to use the package on more 
platforms
> and there is a tracking system for the patches and changes.
> 
> And if you have any remarks/comments/updates on/for this page, please
> let me know.
> 
> 
> -- 
> ----------
> m.vr.gr.
> Gerard Klaver
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Lcms-user mailing list
> Lcms-user at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lcms-user
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041027/3a3b2e98/attachment.sig>

From prcormier at adelphia.net  Thu Oct 28 15:15:34 2004
From: prcormier at adelphia.net (Paul R. Cormier)
Date: Thu, 28 Oct 2004 10:15:34 -0400
Subject: [sane-devel] Help with compiler error
In-Reply-To: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>
References: <001501c4bcf1$b29891e0$1c88ee04@NetZeroUser>
Message-ID: <20041028101534.3abb0e8d.prcormier@adelphia.net>

On Thu, 28 Oct 2004 09:26:12 -0400
"Bensel" <whitemanor at netzero.net> wrote:

> We are trying to get a Memorex MEM 48u scanner working with Linspire 4.5.393.  It is suppose to work with the artec_eplus48u backend so we downloaded sane-backends-1.0.14.  When we run ./configure, we get the error: no acceptable C compiler found in $PATH.  We understand the ANSI C Compiler: GNU C (gcc) is recommended.  Could someone advise how we should proceed from here.  Thanks for your advice and help.
> 

If you have access to Linspire's Click-N-Run library, you can get the compilers and other tools there.
If not, you might try using the Debian Package tools (Linspire is based on the Debian distribution).

-- 
Best regards,

Paul R. Cormier
prcormier at adelphia.net




From henning at meier-geinitz.de  Thu Oct 28 19:48:16 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 28 Oct 2004 20:48:16 +0200
Subject: [sane-devel] genesys backend - warming up procedure
In-Reply-To: <200410281454.09348.gerhard@gjaeger.de>
References: <417FAA47.2010903@ptic.pl> <200410271746.29865.gerhard@gjaeger.de> <4180CD3C.5090705@ptic.pl> <200410281454.09348.gerhard@gjaeger.de>
Message-ID: <20041028184816.GA4740@meier-geinitz.de>

Hi,

On Thu, Oct 28, 2004 at 02:54:09PM +0200, Gerhard Jaeger wrote:
> That's probably not true, I think Henning is still working on that.
> I didn't want to check in my code, as there are too much changes, that
> have not been discussed with Henning. Maybe I add a new directory

At the moment I don't have enough time to work on that code. All my
local changes are in CVS. The last thing I did was to start a debug
print of all the registers so it's easier to find out what's actually
wrong. It's not complete yet, however. That debug printout is based on
the GL646 docu, so it should fit all scanners based on that chip.

So I don't mind if someone goes ahead and works on that code. It needs
generalization anyway. Most chipset settings are at least somewhat
commented so it should be possible to put the device specific values
in the device settings of each device.

If by a commit snathingy breaks for the UMAX 4500 (breaks more than it
already is :-) I'll try to fix it.

Status for the UMAX 4500: Works upto the start of fine claibration,
fine calibration times out (waits for too much data, maybe?). Coarse
calibration goes wrong, also. It actually scans data but the setting
gets worse with each calibration step.

Bye,
  Henning



From ulrick2 at faith4miracle.org  Fri Oct 29 06:39:16 2004
From: ulrick2 at faith4miracle.org (Steven P. Ulrick)
Date: Fri, 29 Oct 2004 00:39:16 -0500
Subject: [sane-devel] Problem scanning with Kooka/Epson Perfection 2400
Message-ID: <200410290039.16664.ulrick2@faith4miracle.org>

Hello, Everyone
I am having a problem scanning with our Epson Perfection 2400 scanner. ?I 
don't know for sure if this is a KDE issue or not.  But I figured that since 
the Scanner Guru's are here, that at the very least you could tell me if this 
is a problem with SANE or not.

This problem only occurs when I use Kooka (doesn't matter whether it's the 
version that ships with Fedora Core 2, or the one on CVS HEAD.) ?I tried 
scanning an image earlier using xsane, and it worked just fine.
Here is a link to an image that I Just scanned (using "xsane", to show that 
the scanner works just fine:
http://www.faith4miracle.org/kooka/JoeyRamone.jpg

When I start any version of Kooka (for this experiment, I will start Kooka 
while su'd into root. ?This is what the GUI looks like:
http://www.faith4miracle.org/kooka/kooka-1.jpg

Then I proceed to do a "Preview Scan" ?This is what the GUI looks like then:
http://www.faith4miracle.org/kooka/kooka-2.jpg

If I try to do a "Final Scan", this is what the GUI looks like:
http://www.faith4miracle.org/kooka/kooka-3.jpg

You will notice that these are identical screen shots. ?This is because 
whether I choose "Preview Scan" or "Final Scan", nothing appears to be 
scanned.

The only configuration file I could find was in "~/.kde/share/config" ?I tried 
deleting that and retrying what I described above, to no avail.

At the following location, you will find a tarball of the terminal window 
outputs that I got when I tried a Preview and a Final scan. ?In the same 
tarball, you will find straces of attempts at Preview and Final scans.
http://www.faith4miracle.org/kooka/kooka-logs.tar.bz2

Root is the group and user of /proc/bus/usb/001/013
Also, root does have read, write and execute permissions on this device.
One thing I just thought of: I can't remember for sure, but should I have 
a /dev/scanner? ?I can't remember if I had one in the past, or if that is 
relevant with a USB scanner. ?All I know is that I don't have one now.

Operating System: Fedora Core 2, All Packages installed, All official Updates 
installed (Except the kernel)
QT: 3.3.3 from TrollTech source tarball
KDE: CVS HEAD

QT and KDE paths are both exported in my ~/.bash_profile. ?I did not overwrite 
the FC2 default KDE.

In closing, this same scanner, using Kooka from the CVS HEAD version of KDE, 
used to work perfectly, never giving me a moment of trouble. ?Like I stated 
earlier, and proved with an example for your viewing, this same scanner that 
does not work with kooka, does work just fine with xsane.

I will be glad to answer any questions that this problem might require.

Have a Great Day
Steven P. Ulrick
-- 
 00:36:39 up 16 days, 10:06, 45 users,  load average: 0.34, 0.33, 0.67



From olaf at epkowa.co.jp  Fri Oct 29 09:29:23 2004
From: olaf at epkowa.co.jp (Olaf Meeuwissen)
Date: Fri, 29 Oct 2004 17:29:23 +0900
Subject: [sane-devel] Problem scanning with Kooka/Epson Perfection 2400
In-Reply-To: <200410290039.16664.ulrick2@faith4miracle.org> (Steven P.
 Ulrick's message of "Fri, 29 Oct 2004 00:39:16 -0500")
References: <200410290039.16664.ulrick2@faith4miracle.org>
Message-ID: <87is8uhqqk.fsf@zen.epkowa.co.jp>

"Steven P. Ulrick" <ulrick2 at faith4miracle.org> writes:

> Hello, Everyone
> I am having a problem scanning with our Epson Perfection 2400 scanner. ?I 
> don't know for sure if this is a KDE issue or not.  But I figured that since 
> the Scanner Guru's are here, that at the very least you could tell me if this 
> is a problem with SANE or not.
> [...]
> In closing, this same scanner, using Kooka from the CVS HEAD version of KDE, 
> used to work perfectly, never giving me a moment of trouble. ?Like I stated 
> earlier, and proved with an example for your viewing, this same scanner that 
> does not work with kooka, does work just fine with xsane.

It's not a SANE problem if everything works just fine with xsane.
Both xsane and kooka communicate with your scanner with the same
mechanism.  Something in kooka is screwing around with the scanner
data.

Check what has changed in CVS since your last working version of
kooka.
-- 
Olaf Meeuwissen                            EPSON KOWA Corporation, PF1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2



From artpi at ptic.pl  Fri Oct 29 11:43:39 2004
From: artpi at ptic.pl (Artur Pierscinski)
Date: Fri, 29 Oct 2004 12:43:39 +0200
Subject: [sane-devel] genesys backend - warming up procedure
In-Reply-To: <200410281454.09348.gerhard@gjaeger.de>
References: <417FAA47.2010903@ptic.pl> <200410271746.29865.gerhard@gjaeger.de> <4180CD3C.5090705@ptic.pl> <200410281454.09348.gerhard@gjaeger.de>
Message-ID: <41821EDB.60204@ptic.pl>

Gerhard Jaeger wrote:

>On Donnerstag 28 Oktober 2004 12:43, Artur Pierscinski wrote:
>  
>
>>Gerhard Jaeger wrote:
>>    
>>
>>>On Mittwoch 27 Oktober 2004 16:01, Artur Pierscinski wrote:
>>>      
>>>
>>>><>
>>>>Hi,
>>>>
>>>>I've done some tests here with the ST24 and rewrote some parts of
>>>>the code, that the warmup and calibration stuff gets passed on it.
>>>>The major problem of the current genesys code is, that it is tied to
>>>>a UMAX device. All the settings specific to CCD and DAC (and motor)
>>>>are only valid for this scanner. This needs to be tweaked. I did this
>>>>here, but the code is not available so far ....
>>>>
>>>>Gerhard
>>>>        
>>>>
>>Thats is fine. May I help in something?
>>So there is almost no traffic in experimental cvs, so its like as no any
>>progress.
>>    
>>
>
>That's probably not true, I think Henning is still working on that.
>I didn't want to check in my code, as there are too much changes, that
>have not been discussed with Henning. Maybe I add a new directory
>  
>
Henning, as he wrote in other post, have not enough time to work on that 
code.

That seems, as exists some independent from each other code, which try 
to solve genesys devices to work.

Artur Pierscinski
e-mail: artpi at ptic.pl




From john at jcoppens.com  Fri Oct 29 15:52:50 2004
From: john at jcoppens.com (John Coppens)
Date: Fri, 29 Oct 2004 11:52:50 -0300
Subject: [sane-devel] Strange file save problem
Message-ID: <20041029115250.5c5cf8cf.john@jcoppens.com>

Hi all.

At a friendly non-profit foundation, I installed Xsane/Sane quite a while
ago. I installed it as saned, so that I can access it from another (WinXP)
machine too, but the problems below are on the local (linux) machine.

Just to be sure I installed the latest versions of sane-backends
(1.0.14?) and Xsane (.96).

1) I still get erratic 'argument error' messages when trying to change
from, eg., binary to gray or to color modes. After a while, for some
reason, the command gets accepted... I reported this problem a long time
ago, but never really got it solved.

2) When saving a file from the viewer in some directories, I get a message
like:

Could not create secure file (may be a link does exist):

In other directories, there is no problem. I checked the priviledges of
the directories and the owners - they're the same. I found a few
references in the mailing list, but no real solution... In the failing
directory no file is present of the same name. It's not part of a project
either - just saving a scanned document.

Thanks in advance.
John



From henning at meier-geinitz.de  Fri Oct 29 16:38:53 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 29 Oct 2004 17:38:53 +0200
Subject: [sane-devel] Strange file save problem
In-Reply-To: <20041029115250.5c5cf8cf.john@jcoppens.com>
References: <20041029115250.5c5cf8cf.john@jcoppens.com>
Message-ID: <20041029153853.GA11940@meier-geinitz.de>

Hi,

On Fri, Oct 29, 2004 at 11:52:50AM -0300, John Coppens wrote:
> At a friendly non-profit foundation, I installed Xsane/Sane quite a while
> ago. I installed it as saned, so that I can access it from another (WinXP)
> machine too, but the problems below are on the local (linux) machine.
> 
> Just to be sure I installed the latest versions of sane-backends
> (1.0.14?) and Xsane (.96).
> 
> 1) I still get erratic 'argument error' messages when trying to change
> from, eg., binary to gray or to color modes. After a while, for some
> reason, the command gets accepted... I reported this problem a long time
> ago, but never really got it solved.

I rember that problem but unfortunately nobody could really reproduce
it as far as I know and such kind of network problems are quite
impossible to debug without reproducing them.

But the problem only happens over the (localhost) network?

Bye,
  Henning



From john at jcoppens.com  Sat Oct 30 05:19:22 2004
From: john at jcoppens.com (John Coppens)
Date: Sat, 30 Oct 2004 01:19:22 -0300
Subject: [sane-devel] Strange file save problem
In-Reply-To: <20041029153853.GA11940@meier-geinitz.de>
References: <20041029115250.5c5cf8cf.john@jcoppens.com>
	<20041029153853.GA11940@meier-geinitz.de>
Message-ID: <20041030011922.67769fe0.john@jcoppens.com>

On Fri, 29 Oct 2004 17:38:53 +0200
Henning Meier-Geinitz <henning at meier-geinitz.de> wrote:

> Hi,
> 
> On Fri, Oct 29, 2004 at 11:52:50AM -0300, John Coppens wrote:
> > At a friendly non-profit foundation, I installed Xsane/Sane quite a
> > while ago. I installed it as saned, so that I can access it from
> > another (WinXP) machine too, but the problems below are on the local
> > (linux) machine.
> > 
> > Just to be sure I installed the latest versions of sane-backends
> > (1.0.14?) and Xsane (.96).
> > 
> > 1) I still get erratic 'argument error' messages when trying to change
> > from, eg., binary to gray or to color modes. After a while, for some
> > reason, the command gets accepted... I reported this problem a long
> > time ago, but never really got it solved.
> 
> I rember that problem but unfortunately nobody could really reproduce
> it as far as I know and such kind of network problems are quite
> impossible to debug without reproducing them.
> 
> But the problem only happens over the (localhost) network?

  I didn't try this time around, after updating. I'll do so tomorrow. I
seem to recall the problem also exists from the XP end.

  Any suggestions on the 'secure' file problem?

  Thanks,

  John

> 
> Bye,
>   Henning
> 
> -- 
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org



From Oliver.Rauch at Rauch-Domain.DE  Sat Oct 30 08:37:26 2004
From: Oliver.Rauch at Rauch-Domain.DE (Oliver Rauch)
Date: 30 Oct 2004 09:37:26 +0200
Subject: [sane-devel] Strange file save problem
In-Reply-To: <20041030011922.67769fe0.john@jcoppens.com>
References: <20041029115250.5c5cf8cf.john@jcoppens.com>
	 <20041029153853.GA11940@meier-geinitz.de>
	 <20041030011922.67769fe0.john@jcoppens.com>
Message-ID: <1099121846.2131.2.camel@Babylon7>

Am Sam, 2004-10-30 um 06.19 schrieb John Coppens:

>   Any suggestions on the 'secure' file problem?

When this happens on the linux machine then please do:

export XSANE_DEBUG=12
xsane 2>debug.txt

and make taht the problem occurs, then close xsane

gzip debug.txt

and send debug.txt.gz to me.
Oliver




From henning at meier-geinitz.de  Sat Oct 30 12:23:51 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 30 Oct 2004 13:23:51 +0200
Subject: [sane-devel] Strange file save problem
In-Reply-To: <20041030011922.67769fe0.john@jcoppens.com>
References: <20041029115250.5c5cf8cf.john@jcoppens.com> <20041029153853.GA11940@meier-geinitz.de> <20041030011922.67769fe0.john@jcoppens.com>
Message-ID: <20041030112351.GA9541@meier-geinitz.de>

Hi,

On Sat, Oct 30, 2004 at 01:19:22AM -0300, John Coppens wrote:
>   I didn't try this time around, after updating. I'll do so tomorrow. I
> seem to recall the problem also exists from the XP end.

What I meant to ask was if it only happens over saned, i.e. does scanning
without saned always work?

Bye,
  Henning



From henning at meier-geinitz.de  Sat Oct 30 17:17:58 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 30 Oct 2004 18:17:58 +0200
Subject: [sane-devel] update net.tex for sane1 documentation
In-Reply-To: <1098123627.5219.23.camel@johannes>
References: <1098123627.5219.23.camel@johannes>
Message-ID: <20041030161758.GG9541@meier-geinitz.de>

Hi,

On Mon, Oct 18, 2004 at 08:20:26PM +0200, Johannes Berg wrote:
> +The data transferred from the client to the server is compromised of

I guess you mean "comprised"?

> +the RPC code (as a \code{SANE\_WORD}), followed by the arguments in the
> +order listed. The server reply consists only of the data given below.

I'd also mention that the data sent to the server is the "request".

I guess we can add that to the sane 1 standard after the release.

Bye,
  Henning



From henning at meier-geinitz.de  Sat Oct 30 17:07:31 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 30 Oct 2004 18:07:31 +0200
Subject: [sane-devel] saned array memory limit
In-Reply-To: <87pt3k3geh.fsf@zen.epkowa.co.jp>
References: <20041014172115.GE12141@meier-geinitz.de> <87oej5qgea.fsf@frigate.technologeek.org> <20041014185842.GG12141@meier-geinitz.de> <87fz4hqbii.fsf@frigate.technologeek.org> <87pt3k3geh.fsf@zen.epkowa.co.jp>
Message-ID: <20041030160731.GF9541@meier-geinitz.de>

Hi,

On Fri, Oct 15, 2004 at 10:43:18AM +0900, Olaf Meeuwissen wrote:
> Hmm, iscan still uses the build infra-structure (Makefile.in etc) from
> sane-backends, but in my free time I've switched it over to use
> automake (and I'm trying to get it included in our official releases).
> 
> Maybe, just maybe, I could see if generalising to multiple backends is
> feasible.  Let me know if you're interested.

Yes, I am. If that's feasable, it would really make development of
multi-file backends easier. I really hate to always do "touch
backend/gt68xx.c" after a change in one of those other gt68xx files.

I'm rather clueless about automake and/or depend files so if anyone
has more experience with this topic please go ahead and tell us what
the easiest solution is.

> BTW, I'll also try to update epkowa.desc before sane-backends-1.0.15
> comes out.

That would be good. On the other hand that file can be changed at any
time as the external backends list is updated immediately and not only
at releases.

Bye,
  henning



From herbr at pfinders.com  Sat Oct 30 17:24:36 2004
From: herbr at pfinders.com (Herb Rubin)
Date: Sat, 30 Oct 2004 09:24:36 -0700
Subject: [sane-devel] Visionshape support?
Message-ID: <1099153476.20930.4.camel@fred.sf.pfinders.com>

Is this supported at all? Visionshape Millenium DS-50/75 that can
scan over 60 pages per minute?

http://www.visionshape.com/millennium.html

It says it has USB and SCSI interface.

Herb





From johannes at sipsolutions.net  Sat Oct 30 18:17:45 2004
From: johannes at sipsolutions.net (Johannes Berg)
Date: Sat, 30 Oct 2004 19:17:45 +0200
Subject: [sane-devel] update net.tex for sane1 documentation
In-Reply-To: <20041030161758.GG9541@meier-geinitz.de>
References: <1098123627.5219.23.camel@johannes>
	<20041030161758.GG9541@meier-geinitz.de>
Message-ID: <1099156665.4294.4.camel@johannes.sipsolutions.net>

On Sat, 2004-10-30 at 18:17 +0200, Henning Meier-Geinitz wrote:
> > +The data transferred from the client to the server is compromised of
> 
> I guess you mean "comprised"?

Um, yes :)

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041030/a84dcb9a/attachment.sig>

From henning at meier-geinitz.de  Sat Oct 30 17:32:08 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 30 Oct 2004 18:32:08 +0200
Subject: [sane-devel] Epson 1250 scanner does not return back after scanning
In-Reply-To: <013E3129-28C2-11D9-9806-000393775A6A@gnome.sk>
References: <1098908428026_29625227@aladarko.gnome.sk> <200410280919.56899.gerhard@gjaeger.de> <013E3129-28C2-11D9-9806-000393775A6A@gnome.sk>
Message-ID: <20041030163207.GI9541@meier-geinitz.de>

Hi,

On Thu, Oct 28, 2004 at 11:16:09AM +0200, Martin Motovsky wrote:
> [plustek] drvclose()
> [plustek] TIME END 1: 31s
> [plustek] usbDev_stopScan()
> [plustek] usbDev_ScanEnd(), start=1, park=1
> [plustek] reader_process: finished reading data
> [plustek] (SIG) Child is down (signal=20)
> scanimage: received signal 2
> scanimage: trying to stop scanner
> [plustek] sane_cancel

Looks like SIGCHILD called the plustek signal handler. However, also
the scanimage signal handler was called. What is sig 2 and sig 20 on
FreeBSD?

scanimage calls sane_cancel() in its own signal handler.

Bye,
  Henning



From henning at meier-geinitz.de  Sat Oct 30 17:22:18 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 30 Oct 2004 18:22:18 +0200
Subject: [sane-devel] homepage for "artiscan 9600" scanner
In-Reply-To: <1098343951.968.10.camel@vicious>
References: <1098343951.968.10.camel@vicious>
Message-ID: <20041030162218.GH9541@meier-geinitz.de>

Hi,

On Thu, Oct 21, 2004 at 09:32:31AM +0200, Enrico Boldrini wrote:
> Theese are two models of the scanner. The scanner we'll try to support
> first will be Tamarack Artiscan 9600 pro 36.
> 
> I use this message also to inform that:
> /!\ The project is moved to http://www.autistici.org/tamarhack /1\

Thanks. I'll update the links.

Bye,
  Henning



From jb at jblache.org  Sun Oct 31 10:42:46 2004
From: jb at jblache.org (Julien BLACHE)
Date: Sun, 31 Oct 2004 11:42:46 +0100
Subject: [sane-devel] Makefile.in : libsane.la should use $(libdir) instead of
 $(libsanedir)
Message-ID: <87fz3v4195.fsf@frigate.technologeek.org>

Hi,


From jb at jblache.org  Sun Oct 31 16:52:03 2004
From: jb at jblache.org (Julien BLACHE)
Date: Sun, 31 Oct 2004 17:52:03 +0100
Subject: [sane-devel] Makefile.in : libsane.la should use $(libdir)
 instead of $(libsanedir)
In-Reply-To: <87fz3v4195.fsf@frigate.technologeek.org> (Julien BLACHE's
 message of "Sun, 31 Oct 2004 11:42:46 +0100")
References: <87fz3v4195.fsf@frigate.technologeek.org>
Message-ID: <87brei4yq4.fsf@frigate.technologeek.org>

Julien BLACHE <jb at jblache.org> wrote:

> libsane.la: dll.lo dll-s.lo $(EXTRA) $(addsuffix .lo,$(DLL_PRELOAD)) $(LIBOBJS) 
>         @$(LIBTOOL) $(MLINK) $(CC) -o $@ $(LDFLAGS) $(BACKENDLIBS)  $^ \ 
>                 $(addsuffix .lo,$(DLL_PRELOAD_EXTRAS)) @LIBTOOL_LINK_EXTRA@ \ 
>                 -rpath $(libsanedir) -version-info $(V_MAJOR):$(V_REV):$(V_MINOR) 
>                        ^^^^^^^^^^^^^

Actually, this comes from one of my patches, and isn't in the vanilla
sane-backends sources.

Looks like a copy&paste error, as I can't remember doing any changes
to that part of the Makefile.

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb at jblache.org>                                  GPG KeyID 0xF5D65169



From jb at jblache.org  Sun Oct 31 18:00:35 2004
From: jb at jblache.org (Julien BLACHE)
Date: Sun, 31 Oct 2004 19:00:35 +0100
Subject: Source dependency tracking (was: Re: [sane-devel] saned array
 memory limit)
In-Reply-To: <20041030160731.GF9541@meier-geinitz.de> (Henning
 Meier-Geinitz's message of "Sat, 30 Oct 2004 18:07:31 +0200")
References: <20041014172115.GE12141@meier-geinitz.de>
	<87oej5qgea.fsf@frigate.technologeek.org>
	<20041014185842.GG12141@meier-geinitz.de>
	<87fz4hqbii.fsf@frigate.technologeek.org>
	<87pt3k3geh.fsf@zen.epkowa.co.jp>
	<20041030160731.GF9541@meier-geinitz.de>
Message-ID: <877jp64vjw.fsf_-_@frigate.technologeek.org>

Henning Meier-Geinitz <henning at meier-geinitz.de> wrote:

Hi,

> I'm rather clueless about automake and/or depend files so if anyone
> has more experience with this topic please go ahead and tell us what
> the easiest solution is.

Here's a proposed solution... It uses makedepend (from XFree86, in the
xutils package for Debian users) to generate backend/.depend.

The depend rule could be made a noop if makedepend isn't found or by a
configure switch (could be disabled in releases by default, and
reenabled by a configure switch).

The makedepend run takes less than a second on my workstation.

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb at jblache.org>                                  GPG KeyID 0xF5D65169

-------------- next part --------------
A non-text attachment was scrubbed...
Name: sane-backends_makedepend.patch
Type: text/x-patch
Size: 997 bytes
Desc: Add a working depend rule to backend/Makefile.in and use it
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20041031/275f7d14/attachment.bin>

From henning at meier-geinitz.de  Sun Oct 31 19:17:37 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 31 Oct 2004 20:17:37 +0100
Subject: [sane-devel] Code freeze for sane-backends 1.0.15
Message-ID: <20041031191737.GB5937@meier-geinitz.de>

Hi everyone,

Code freeze for sane-backends 1.0.15 is now active. This means,
that no changes to the code should be committed. The only exceptions
are bugs that may render a backend completely useless, that may
destroy hardware, or that break compilation on at least one platform.
If in doubt, ask sane-devel.
Documentation and translation updates are still allowed.

Timetable:
2004-11-07 Release

Bye,
  Henning



From prcormier at adelphia.net  Sun Oct 31 17:36:19 2004
From: prcormier at adelphia.net (Paul R. Cormier)
Date: Sun, 31 Oct 2004 12:36:19 -0500
Subject: [sane-devel] Re: Debian confusion
In-Reply-To: <000001c4bf5c$4895f4a0$ca88ee04@NetZeroUser>
References: <000001c4bf5c$4895f4a0$ca88ee04@NetZeroUser>
Message-ID: <20041031123619.0c2bf24f.prcormier@adelphia.net>

You're welcome.
I checked the Readme file that comes with the sane package in question.  I was surprised that it did not specify a version requirement for GCC.
Versions 2.95.4 and 3.0.4 have worked with Lindows/Linspire, and versions 3.2 and 3.3 may work.
You will also want to check the Readme file for other requirements.
The debian web site will also have instructions on how to use their package tools.  Using those will help to check for other dependencies that need to be addressed.  One note of caution:  Linspire is not yet working at the same release level as debian, so avoid updating things that are not necessary to your goals (or join Linspire's Click-n-Run library program - works fairly well, but up to date releases are not always available).

-- 
Best regards,

Paul R. Cormier
prcormier at adelphia.net


On Sun, 31 Oct 2004 10:08:36 -0500
"Bensel" <whitemanor at netzero.net> wrote:

> Thanks for your help.
> We went to debian.org and are confused with all the gcc packages.  Can you give us any guidelines to help sort out which package we should download to get a working compiler on our system?
> Thank you very much.
> Howard
> 
> On Thu, 28 Oct 2004 09:26:12 -0400
> "Bensel" <whitemanor at netzero.net> wrote:
> 
> > We are trying to get a Memorex MEM 48u scanner working with Linspire 4.5.393.  It is suppose to work with the artec_eplus48u backend so we downloaded sane-backends-1.0.14.  When we run ./configure, we get the error: no acceptable C compiler found in $PATH.  We understand the ANSI C Compiler: GNU C (gcc) is recommended.  Could someone advise how we should proceed from here.  Thanks for your advice and help.
> > 
> 
> If you have access to Linspire's Click-N-Run library, you can get the compilers and other tools there.
> If not, you might try using the Debian Package tools (Linspire is based on the Debian distribution).
> 
> -- 
> Best regards,
> 
> Paul R. Cormier
> prcormier at adelphia.net
> 
> 
> 



From henning at meier-geinitz.de  Sun Oct 31 19:14:55 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 31 Oct 2004 20:14:55 +0100
Subject: [sane-devel] [ANNOUNCE] Second pre-release of sane-backends 1.0.15 available
Message-ID: <20041031191455.GA5937@meier-geinitz.de>

Hi everyone,

The second pre-release of sane-backends 1.0.15 is available at
the usual locations as mentioned on
http://www.sane-project.org/source.html

The md5sum is:
be835c68cb6a387d50ca250755031983  sane-backends-1.0.15-pre2.tar.gz

We are in code freeze currently. Release is planned for 2004-11-07.

I'll append the NEWS file for 1.0.15.

Please test this prerelease and tell us about any bugs.

Happy scanning!

Henning

New with 1.0.15, released 2004-11-07:

* New backends: niash.
* Updated backends: agfafocus, artec_eplus48u.c, avision, canon, canon_pp,
  coolscan, dll, epson, fujitsu, gt68xx, hp, hp5400, leo, microtek2, mustek,
  mustek_pp, net, pie, plustek, plustek_pp, snapscan, sp15c, tamarack, teco2,
  umax, umax_pp, u12, v4l.
* Portability fixes (especially for MacOS X, NetBSD, OS/2, 64 bit platforms).
* sane-find-scanner detects more chipsets now.
* Added Finnish translation. Updated other translations.
* Several saned fixes.
* Build system updates.
* Documentation updates.
* Bugfixes.