[sane-devel] Epson perfection 660 usb - problem with lineart scanning - snapscan backend

2006-09-09 Thread Frédéric Leroy
Le mardi 05 septembre 2006 ? 20:29 +0200, Oliver Schwartz a ?crit :
> Hi,
> 
> > > When I try to scan in lineart mode, it makes garbage on output.
> > > The scan seems "misaligned".
> > > But if I first make a scan in gray or color mode, and then switch
> > > to lineart, it works !
> >
> > It works ... sometimes :(
> >
> > I acquire a scan in Lineart mode and make a log :
> > http://www.starox.org/pub/sane/snapscan/lineart.log
> > It makes dirty squares in the image :
> > http://www.starox.org/pub/sane/snapscan/lineart.pnm
> [...]
> Maybe you can provide an USB trace of a lineart scan on windows. 
> You need to install an USB sniffer first. I prefer USBSnoop which is 
> available from http://benoit.papillault.free.fr/usbsnoop/ . The page 
> also gives basic instructions on how to use it.
> 
> To produce the log you should
> - unplug and replug the scanner
> - Start the scanning software
> - Do a preview scan
> - Do a very small scan with lowest resolution
I forgot to set the lowest resolution :(

So here is the tarball:
http://www.starox.org/pub/sane/snapscan/epson%20perfection%20660%20-%
20lieart%20mode%20-%20usbsnoop.tar.bz2

Or go simply here if the link above don't work:
http://www.starox.org/pub/sane/snapscan/

I made 2 scans, one with a small images (scanner tool says it's 765byte)
and another one with full width.

==
Offsets : 
0   Plug the scanner in
...
2819458 Scanner preview ended

* Click on acquire button
3790xxx Calibration stuff (it pause but I hadn't time to read the
number)
3827264 scan of image 1 finished

* Change the surface of acqusition (no activity on usb) and click on
acquire button
480 Calibration stuff 
5322638 scan of image 2 finished
==

You can ask me any other log, even if I'm busy, I'll answer !
Don't hesitate :)



[sane-devel] Epson perfection 660 usb - problem with lineart scanning - snapscan backend

2006-09-05 Thread Frédéric Leroy
Le mardi 05 septembre 2006 ? 20:29 +0200, Oliver Schwartz a ?crit :
> Hi,
> 
> > > When I try to scan in lineart mode, it makes garbage on output.
> > > The scan seems "misaligned".
> > > But if I first make a scan in gray or color mode, and then switch
> > > to lineart, it works !
> >
> > It works ... sometimes :(
> >
> > I acquire a scan in Lineart mode and make a log :
> > http://www.starox.org/pub/sane/snapscan/lineart.log
> > It makes dirty squares in the image :
> > http://www.starox.org/pub/sane/snapscan/lineart.pnm
> 
> So... is this the best result you can get or does it work ok (without 
> the dirty squares) if you scan in grayscale first?
It is the best result I can get with scanimage.
It always fails.
Whereas with xsane, sometimes it works after a real scan (not a preview,
but after a preview). Maybe a problem with preview ?

> Unfortunately it seems that lineart mode is less and less supported in 
> newer scanners. These scanners always scan in grayscale mode, the 
> conversion to lineart has to be done in the backend. I don't know if 
> this is the case for the Perfection 660, but on the other hand 
> there's not much that can fail on lineart mode.
So, it's possible to fallback to software conversion.
It seem's there is many scanner with this problem, maybe we can add a new 
option for this ?

> Maybe you can provide an USB trace of a lineart scan on windows. 
> You need to install an USB sniffer first. I prefer USBSnoop which is 
> available from http://benoit.papillault.free.fr/usbsnoop/ . The page 
> also gives basic instructions on how to use it.
> [...]
I'll do this tomorrow.



[sane-devel] Epson perfection 660 usb - problem with lineart scanning - snapscan backend

2006-09-05 Thread Oliver Schwartz
Hi,

> > When I try to scan in lineart mode, it makes garbage on output.
> > The scan seems "misaligned".
> > But if I first make a scan in gray or color mode, and then switch
> > to lineart, it works !
>
> It works ... sometimes :(
>
> I acquire a scan in Lineart mode and make a log :
> http://www.starox.org/pub/sane/snapscan/lineart.log
> It makes dirty squares in the image :
> http://www.starox.org/pub/sane/snapscan/lineart.pnm

So... is this the best result you can get or does it work ok (without 
the dirty squares) if you scan in grayscale first?

Unfortunately it seems that lineart mode is less and less supported in 
newer scanners. These scanners always scan in grayscale mode, the 
conversion to lineart has to be done in the backend. I don't know if 
this is the case for the Perfection 660, but on the other hand 
there's not much that can fail on lineart mode. 

Maybe you can provide an USB trace of a lineart scan on windows. 
You need to install an USB sniffer first. I prefer USBSnoop which is 
available from http://benoit.papillault.free.fr/usbsnoop/ . The page 
also gives basic instructions on how to use it.

To produce the log you should
- unplug and replug the scanner
- Start the scanning software
- Do a preview scan
- Do a very small scan with lowest resolution

You can send the (compressed) log to me in private mail

/Oliver


[sane-devel] Epson perfection 660 usb - problem with lineart scanning - snapscan backend

2006-09-04 Thread Frédéric Leroy
Le jeudi 30 mars 2006 ? 00:12 +0200, Fr?d?ric Leroy a ?crit :
> Hello,
> 
> When I try to scan in lineart mode, it makes garbage on output. The scan
> seems "misaligned".
> But if I first make a scan in gray or color mode, and then switch to
> lineart, it works !
It works ... sometimes :(

I acquire a scan in Lineart mode and make a log :
http://www.starox.org/pub/sane/snapscan/lineart.log
It makes dirty squares in the image :
http://www.starox.org/pub/sane/snapscan/lineart.pnm

And the same thing in grey :
http://www.starox.org/pub/sane/snapscan/grey.log
http://www.starox.org/pub/sane/snapscan/grey.pnm

I obtain the same results with sane-backend cvs and firmwares
tail_0{58,60,61}.bin on little/big endian system :(.

I tried to look at sane source but I'm lost in the snapscan backend.
If a snapscan guru can guide me, it would be wonderfull. I really want
my scanner work in lineart mode.



[sane-devel] Epson perfection 660 usb - problem with lineart scanning - snapscan backend

2006-03-29 Thread Frédéric Leroy
Hello,

When I try to scan in lineart mode, it makes garbage on output. The scan
seems "misaligned".
But if I first make a scan in gray or color mode, and then switch to
lineart, it works !
It seems the snapscan backend forget to initialize something in lineart
mode.



[sane-devel] Epson Perfection 660

2004-07-02 Thread Oliver Schwartz
=2DBEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

> libusb is there, actual output was:
>
>libusb-0.1.so.4 =3D> /usr/lib/libusb-0.1.so.4 (0x40032000)

try another debug log then, this time with SANE_DEBUG_SANEI_USB=3D255=20
and SANE_DEBUG_SNAPSCAN=3D255. Comment out everything in dll.conf=20
except for "net" and "snapscan" in dll.conf to reduce log size.

/Oliver
=2DBEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFA5diB/V6sbrmfIuMRAi1fAJ9Tg5L4dZfiRcyNsPMrl8crrwo9WACePgVr
z++oOfx72oofRVzxd/g5g6U=3D
=3D9PvP
=2DEND PGP SIGNATURE-



[sane-devel] Epson Perfection 660

2004-07-02 Thread Eelke Klein
> try another debug log then, this time with
> SANE_DEBUG_SANEI_USB=255 
> and SANE_DEBUG_SNAPSCAN=255. Comment out everything in
> dll.conf 
> except for "net" and "snapscan" in dll.conf to reduce log
> size.
Thanks but I have solved the problem. I do not know the real
cause but I think the portage system of gentoo is to blame. The
first time I installed I had forgotten to set the usb USE flag.
I set it afterwards and reinstalled and I think this is where
something went wrong. Because a complete cleanup and reinstall
solved the problem.

Eelke





__
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 



[sane-devel] Epson Perfection 660

2004-07-01 Thread Eelke Klein
--- Oliver Schwartz  wrote:
> it seems the backend is not even attempting to open the
> scanner 
> device. Maybe the version of SANE you're using was compiled
> without 
> libusb support? To find out, run
> 
> ldd /usr/bin/scanimage | grep libusb
> 
libusb is there, actual output was:

   libusb-0.1.so.4 => /usr/lib/libusb-0.1.so.4 (0x40032000)

Eelke



__
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail



[sane-devel] Epson Perfection 660

2004-07-01 Thread Oliver Schwartz
=2DBEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

> [sanei_debug] Setting debug level of snapscan to 255.
> [snapscan] sane_snapscan_init
> [snapscan] sane_snapscan_init: Snapscan backend version 1.4.37
> [snapscan] sane_snapscan_get_devices (0xbfffe2f8, 0)

it seems the backend is not even attempting to open the scanner=20
device. Maybe the version of SANE you're using was compiled without=20
libusb support? To find out, run

ldd /usr/bin/scanimage | grep libusb

If you don't get any output libusb isn't used at all and you won't be=20
able to access your scanner with kernel 2.6. You'll have to compile a=20
version with libusb in that case.

/Oliver
=2DBEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFA5Eqr/V6sbrmfIuMRAqhZAKCDTOQuiC9vob7R/xjqfrXkw1mghgCbBmmO
5W3oF8MNKiuwTpirZNql/ps=3D
=3DUpZu
=2DEND PGP SIGNATURE-



[sane-devel] Epson Perfection 660

2004-06-30 Thread Eelke Klein
> Try enabling debug messages:
> SANE_DEBUG_SNAPSCAN=255 scanimage -L
> 
> If you don't get any output, the snapscan backend isn't loaded
> for
> some reason.
Ok I got this. So it seems to be loaded.

[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.37
[snapscan] sane_snapscan_get_devices (0xbfffe2f8, 0)

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).
[snapscan] sane_snapscan_exit 

Eelke



__
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail 



[sane-devel] Epson Perfection 660

2004-06-30 Thread Henning Meier-Geinitz
Hi,

On Wed, Jun 30, 2004 at 09:38:24AM -0700, Eelke Klein wrote:
> I'm trying to get my epson perfection 660 scanner to work. I
> have had it working on SuSE 8.2 but I have switched to gentoo
> and can't get it to work anymore.
> 
> sane-find-scanner can find it but scanimage -L doesn't. I have
> the permissions in /proc/bus/usb automatically set by a hotplug
> script and have checked that the rights are actually set. I also
> tried it as root so the rights shouldn't be a problem anyway.

Try enabling debug messages:
SANE_DEBUG_SNAPSCAN=255 scanimage -L

If you don't get any output, the snapscan backend isn't loaded for
some reason.

Bye,
  Henning



[sane-devel] Epson Perfection 660

2004-06-30 Thread Eelke Klein
Hello,

I'm trying to get my epson perfection 660 scanner to work. I
have had it working on SuSE 8.2 but I have switched to gentoo
and can't get it to work anymore.

sane-find-scanner can find it but scanimage -L doesn't. I have
the permissions in /proc/bus/usb automatically set by a hotplug
script and have checked that the rights are actually set. I also
tried it as root so the rights shouldn't be a problem anyway.

I have copied the firmware of my windows drivers and configured
the location of it in the scapscan.conf. I have also checked
that the id's of my scanner actually matched the id's in the
snapscan.conf.

snapscan is also enabled in the dll.conf.

Here some version:
Kernel 2.6.7
sane-backends 1.0.14-r3
libusb 0.1.7-r1

Eelke




__
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 



[sane-devel] Epson perfection 660 ->Problem building on OSX

2003-09-16 Thread hironori kohno
 $B$N!"(B
   "Re: [sane-devel] Epson perfection 660 ->Problem building on 
OSX" 
   "Dino Tang "wrote:

Hi,

i read your mail and was consulted very much.
Can't the patch file to libusb be obtained by the attached file
of mail?


--
kouno.hiron...@pfu.fujitsu.com


[sane-devel] Epson perfection 660 ->Problem building on OSX

2003-06-22 Thread Oliver Schwartz
=2DBEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

> After getting the latest tools (dec2002) and getting the CVS
> versions of everything (sane, snapscan, libusb) it compiles. But it
> looks like I am stuck where everyone else has been getting stuck.
> Sane-find-scanner sees the scanner but I can't get scanimage to
> find it. I think that this is becoming not worth the effort. Has
> anyone gotten the epson perfection 660  and sane to work with os x?

Please send me the output of "SANE_DEBUG_SNAPSCAN=3D255 scanimage -L".=20
Btw, the snapscan version in the SANE CVS archive is the most recent=20
version. There's no need to upgrade the snapscan backend from=20
Sourceforge anymore.

=2D -Oliver
=2DBEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+9hj2/V6sbrmfIuMRAtKaAJ9T6SSaR7ESgOT+9pwvEKtU1241VQCeKtUc
2lqzYdNhNaACZvI1appYWKU=3D
=3Dz0WI
=2DEND PGP SIGNATURE-



[sane-devel] Epson perfection 660 ->Problem building on OSX

2003-06-22 Thread Peter Howard
On Sat, 2003-06-21 at 22:57, Henning Meier-Geinitz wrote: 
 
> Yeah, that's the already known multiple definition error. Some MacOS X
> users don't seem to get that error, some see it. No idea why.
> And, by the way, I have no idea why libm should define _getopt.
> 
As covered earlier in this thread, updating to the December 02 Developer
Tools fixed the problem for me.  Note, the interim update (IIRC October)
still had the problem. 

PJH



[sane-devel] Epson perfection 660 ->Problem building on OSX

2003-06-22 Thread Brian D. Williams
After getting the latest tools (dec2002) and getting the CVS versions of
everything (sane, snapscan, libusb) it compiles. But it looks like I am stuck
where everyone else has been getting stuck. Sane-find-scanner sees the scanner
but I can't get scanimage to find it. I think that this is becoming not worth
the effort. Has anyone gotten the epson perfection 660  and sane to work with
os x?

Thanks for the help everyone.

Brian

--- Peter Howard  wrote:
> On Sat, 2003-06-21 at 22:57, Henning Meier-Geinitz wrote: 
>  
> > Yeah, that's the already known multiple definition error. Some MacOS X
> > users don't seem to get that error, some see it. No idea why.
> > And, by the way, I have no idea why libm should define _getopt.
> > 
> As covered earlier in this thread, updating to the December 02 Developer
> Tools fixed the problem for me.  Note, the interim update (IIRC October)
> still had the problem. 
> 
> PJH
> 
> ___
> Sane-devel mailing list
> sane-de...@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel

=
Brian Williams
homepage == 


[sane-devel] Epson perfection 660 ->Problem building on OSX

2003-06-22 Thread Henning Meier-Geinitz
Hi,

On Sat, Jun 21, 2003 at 09:04:34AM -0700, Brian D. Williams wrote:
> Thanks for having a look at that. Could I remove the offending define(s)?

It's not a problem of an offending define. liblib.a uses _getopt
internally. libm (?) also uses _getopt. Usually that's not a problem
but your system tools (linker) don't seem too like it for some reason.

Bye,
  Henning


[sane-devel] Epson perfection 660 ->Problem building on OSX

2003-06-21 Thread Henning Meier-Geinitz
Hi,

On Sat, Jun 21, 2003 at 05:13:08AM -0700, Brian D. Williams wrote:
> gcc -o .libs/scanimage scanimage.o stiff.o  ../lib/liblib.a 
> ../backend/.libs/libsane.dylib /usr/local/lib/libusb.dylib -lIOKit -lm 
> -framework CoreFoundation -framework IOKit
> ld: multiple definitions of symbol _getopt
> /usr/lib/libm.dylib(getopt.So) definition of _getopt
> ../lib/liblib.a(getopt.o) definition of _getopt in section (__TEXT,__text)
> ld: multiple definitions of symbol _opterr
> /usr/lib/libm.dylib(getopt.So) definition of _opterr
> ../lib/liblib.a(getopt.o) definition of _opterr in section (__DATA,__data)
> ld: multiple definitions of symbol _optind
> /usr/lib/libm.dylib(getopt.So) definition of _optind
> ../lib/liblib.a(getopt.o) definition of _optind in section (__DATA,__data)
> ld: multiple definitions of symbol _optopt
> /usr/lib/libm.dylib(getopt.So) definition of _optopt
> ../lib/liblib.a(getopt.o) definition of _optopt in section (__DATA,__data)

Yeah, that's the already known multiple definition error. Some MacOS X
users don't seem to get that error, some see it. No idea why.
And, by the way, I have no idea why libm should define _getopt.

Bye,
  Henning


[sane-devel] Epson perfection 660 ->Problem building on OSX

2003-06-21 Thread Dino Tang
Hi Brian,

You have the latest system, but you might not have the latest tool set. 
  You can open the Project Builder and use the "About Project Builder" 
to find out what version you have.  If it doesn't say "Version 2.1 
(December 2002 Developer Tools)", you don't have the latest tool set.  
You can download the latest tools from the ADC ( Apple Developer 
Connection ) site.

The "multiple symbol defined" problem has to do with the way you 
compile libusb.  Mattias Ellert  has sent me 
the following explanation and patch awhile back.

Cheers!

--Dino

--- beginning Mattias's message ---
If you get that error even when linking against libusb, I guess you 
didn't patch the libusb before compiling it. The attached patch should 
be applied to libusb before compiling. It does build without the patch, 
but the configure script cheats a bit and links frameworks as 
libraries, so the dependencies don't get recorded correctly in the 
libraries. This means that when you compile something that depends on 
libusb you might get into trouble -- as you did.

Since the libusb patch changes some autoconf/automake files you need to 
rerun those. My build instructions for libusb are as follows. (The 
--disable-static is optional of course.) In this way you get a library 
with the correct dependencies recorded.

tar -z -x -f libusb-0.1.7.tar.gz
patch -p0 < frameworks.patch
cd libusb-0.1.7
#  Remove 'missing' in order to avoid warning about it being old during 
configure.
#  A newer version will be installed by automake.
rm missing
aclocal
automake --add-missing
autoconf
./configure --disable-static
make

Mattias

PS. I have sent the patch to the maintainer of libusb, so it might be 
included in the next official release if it is accepted. The SANE 
prerelease already has the corresponding patch included.

diff -ur libusb-0.1.7.orig/Makefile.am libusb-0.1.7/Makefile.am
--- libusb-0.1.7.orig/Makefile.am   Mon Nov 11 19:04:15 2002
+++ libusb-0.1.7/Makefile.amSun Mar  2 15:59:42 2003
@@ -28,7 +28,7 @@
  if DARWIN_API
  OS_SUPPORT = darwin.c
  CFLAGS_EXT = -no-cpp-precomp
-LDADDS = -lIOKit -framework "CoreFoundation"
+LDADDS = -framework IOKit -framework CoreFoundation
  else
  OS_SUPPORT =
  endif
diff -ur libusb-0.1.7.orig/configure.in libusb-0.1.7/configure.in
--- libusb-0.1.7.orig/configure.in  Sun Nov 17 19:45:15 2002
+++ libusb-0.1.7/configure.in   Sun Mar  2 15:59:42 2003
@@ -11,7 +11,8 @@

  dnl we need to AC_DIVERT_PUSH/AC_DIVERT_POP these variable definitions 
so they
  dnl are available for $ac_help expansion (don't we all *love* 
autoconf?)
-AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)dnl
+ifdef([AC_DIVERSION_NOTICE], [AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)],
+[AC_DIVERT_PUSH(NOTICE)])

  #
  # The following version number definitions apply to libusb
@@ -76,7 +77,8 @@
  dnl Initialize maintainer mode
  AM_MAINTAINER_MODE

-AC_CANONICAL_HOST
+dnl This has already been dragged in by AM_PROG_LIBTOOL
+dnl AC_CANONICAL_HOST

  AC_MSG_CHECKING(for what USB OS support)
  case $host in
@@ -99,7 +101,7 @@
  AC_SUBST(DARWIN_API)
  os_support=darwin
  AC_MSG_RESULT(Darwin and/or MacOS 10)
-OSLIBS="-lIOKit"
+OSLIBS="-framework IOKit"
  ;;
  esac

@@ -111,7 +113,8 @@

  dnl figure debugging default, prior to $ac_help setup
  dnl
-AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)dnl
+ifdef([AC_DIVERSION_NOTICE], [AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)],
+[AC_DIVERT_PUSH(NOTICE)])
  if test `expr $LIBUSB_MINOR_VERSION \% 2` = 1 ; then
debug_default=yes
  else
diff -ur libusb-0.1.7.orig/ltmain.sh libusb-0.1.7/ltmain.sh
--- libusb-0.1.7.orig/ltmain.sh Wed Mar 27 20:10:10 2002
+++ libusb-0.1.7/ltmain.sh  Sun Mar  2 15:59:42 2003
@@ -887,6 +887,11 @@
  prev=
  continue
  ;;
+   framework)
+ deplibs="$deplibs -framework $arg"
+ prev=
+ continue
+ ;;
release)
  release="-$arg"
  prev=
@@ -988,6 +993,11 @@
continue
;;

+  -framework)
+   prev=framework
+   continue
+   ;;
+
# The native IRIX linker understands -LANG:*, -LIST:* and -LNO:*
# so, if we see these flags be careful not to treat them like -L
-L[A-Z][A-Z]*:*)
@@ -1378,10 +1388,37 @@
link) libs="$deplibs %DEPLIBS% $dependency_libs" ;;
esac
fi
+  prev=
for deplib in $libs; do
+   case $prev in
+   "") ;;
+   framework)
+ prev=
+ if test $linkmode = oldlib && test $linkmode = obj; then
+   $echo "$modename: warning: \`-framework' is ignored for 
archives/objects: $deplib" 1>&2
+   continue
+ fi
+ if test $pass = conv; then
+   deplibs="-framework $deplib $deplibs"
+   continue
+ fi
+ if test "$linkmode,$pass" = "prog,link"; then
+   compile_deplibs="-framework $deplib $compile_deplibs"
+   finalize_deplibs="-framework $deplib

[sane-devel] Epson perfection 660 ->Problem building on OSX

2003-06-21 Thread Henning Meier-Geinitz
Hi,

On Sat, Jun 21, 2003 at 02:14:56AM -0700, Brian D. Williams wrote:
> I have been trying to get sane to work with the epson perfection 660. I could
> build sane with 1.0.11 but not with the snapscan addition. I could not build
> 1.0.12 at all. It would stop building at when trying to make scanimage but I
> didn't see any error messages that made sense to me. I am running the latest 
> os
> x (10.2.6). Sadly I don't have a scanner available (other than the epson) to
> test against. Any suggestions would be greatly appreciated.

Please show us the error messages (e.g. the last 100 lines of the
output).

Bye,
  Henning


[sane-devel] Epson perfection 660 ->Problem building on OSX

2003-06-21 Thread Brian D. Williams
Hi,

Thanks for having a look at that. Could I remove the offending define(s)?

Brian

--- Henning Meier-Geinitz  wrote:
> Hi,
> 
> On Sat, Jun 21, 2003 at 05:13:08AM -0700, Brian D. Williams wrote:
> > gcc -o .libs/scanimage scanimage.o stiff.o  ../lib/liblib.a
> ../backend/.libs/libsane.dylib /usr/local/lib/libusb.dylib -lIOKit -lm
> -framework CoreFoundation -framework IOKit
> > ld: multiple definitions of symbol _getopt
> > /usr/lib/libm.dylib(getopt.So) definition of _getopt
> > ../lib/liblib.a(getopt.o) definition of _getopt in section (__TEXT,__text)
> > ld: multiple definitions of symbol _opterr
> > /usr/lib/libm.dylib(getopt.So) definition of _opterr
> > ../lib/liblib.a(getopt.o) definition of _opterr in section (__DATA,__data)
> > ld: multiple definitions of symbol _optind
> > /usr/lib/libm.dylib(getopt.So) definition of _optind
> > ../lib/liblib.a(getopt.o) definition of _optind in section (__DATA,__data)
> > ld: multiple definitions of symbol _optopt
> > /usr/lib/libm.dylib(getopt.So) definition of _optopt
> > ../lib/liblib.a(getopt.o) definition of _optopt in section (__DATA,__data)
> 
> Yeah, that's the already known multiple definition error. Some MacOS X
> users don't seem to get that error, some see it. No idea why.
> And, by the way, I have no idea why libm should define _getopt.
> 
> Bye,
>   Henning
> ___
> Sane-devel mailing list
> sane-de...@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel

=
Brian Williams
homepage == 


[sane-devel] Epson perfection 660 ->Problem building on OSX

2003-06-21 Thread Brian D. Williams
--0-1698544750-1056197588=:12806
Content-Type: text/plain; charset=us-ascii
Content-Id: 
Content-Disposition: inline

Hi Henning (and others),

I have attached the last 100+ lines from from make. 

Thanks
Brian


--- Henning Meier-Geinitz  wrote:
> Hi,
> 
> On Sat, Jun 21, 2003 at 02:14:56AM -0700, Brian D. Williams wrote:
> > I have been trying to get sane to work with the epson perfection 660. I
> could
> > build sane with 1.0.11 but not with the snapscan addition. I could not
> build
> > 1.0.12 at all. It would stop building at when trying to make scanimage but
> I
> > didn't see any error messages that made sense to me. I am running the
> latest os
> > x (10.2.6). Sadly I don't have a scanner available (other than the epson)
> to
> > test against. Any suggestions would be greatly appreciated.
> 
> Please show us the error messages (e.g. the last 100 lines of the
> output).
> 
> Bye,
>   Henning
> ___
> Sane-devel mailing list
> sane-de...@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel

=
Brian Williams
homepage == 
--0-1698544750-1056197588=:12806
Content-Type: text/plain; name="make_sane.txt"
Content-Description: make_sane.txt
Content-Disposition: inline; filename="make_sane.txt"

gcc -c -g -O2 -W -Wall -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 -DSTUBS 
-DBACKEND_NAME=artec_eplus48u artec_eplus48u-s.c  -fno-common -DPIC -o 
.libs/artec_eplus48u-s.o
gcc -bundle -flat_namespace -undefined suppress -o 
.libs/libsane-artec_eplus48u.1.0.12.so  .libs/artec_eplus48u.o 
.libs/artec_eplus48u-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_constrain_value.o ../sanei/.libs/sanei_usb.o  
/usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit
(cd .libs && rm -f libsane-artec_eplus48u.1.so && ln -s 
libsane-artec_eplus48u.1.0.12.so libsane-artec_eplus48u.1.so)
(cd .libs && rm -f libsane-artec_eplus48u.so && ln -s 
libsane-artec_eplus48u.1.0.12.so libsane-artec_eplus48u.so)
creating libsane-artec_eplus48u.la
(cd .libs && rm -f libsane-artec_eplus48u.la && ln -s 
../libsane-artec_eplus48u.la libsane-artec_eplus48u.la)
 gcc -c -g -O2 -W -Wall -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 
-DBACKEND_NAME=ma1509 -DLIBDIR=/usr/local/lib/sane ma1509.c  -fno-common -DPIC 
-o .libs/ma1509.o
ma1509.c: In function `calibration':
ma1509.c:826: warning: int format, long unsigned int arg (arg 3)
ma1509.c: In function `send_gamma':
ma1509.c:919: warning: int format, size_t arg (arg 3)
rm -f ma1509-s.c
ln -s ./stubs.c ma1509-s.c
 gcc -c -g -O2 -W -Wall -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 -DSTUBS 
-DBACKEND_NAME=ma1509 ma1509-s.c  -fno-common -DPIC -o .libs/ma1509-s.o
gcc -bundle -flat_namespace -undefined suppress -o 
.libs/libsane-ma1509.1.0.12.so  .libs/ma1509.o .libs/ma1509-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_constrain_value.o ../sanei/.libs/sanei_usb.o  
/usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit
(cd .libs && rm -f libsane-ma1509.1.so && ln -s libsane-ma1509.1.0.12.so 
libsane-ma1509.1.so)
(cd .libs && rm -f libsane-ma1509.so && ln -s libsane-ma1509.1.0.12.so 
libsane-ma1509.so)
creating libsane-ma1509.la
(cd .libs && rm -f libsane-ma1509.la && ln -s ../libsane-ma1509.la 
libsane-ma1509.la)
 gcc -c -g -O2 -W -Wall -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 
-DBACKEND_NAME=ibm -DLIBDIR=/usr/local/lib/sane ibm.c  -fno-common -DPIC -o 
.libs/ibm.o
rm -f ibm-s.c
ln -s ./stubs.c ibm-s.c
 gcc -c -g -O2 -W -Wall -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 -DSTUBS 
-DBACKEND_NAME=ibm ibm-s.c  -fno-common -DPIC -o .libs/ibm-s.o
gcc -bundle -flat_namespace -undefined suppress -o .libs/libsane-ibm.1.0.12.so  
.libs/ibm.o .libs/ibm-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_scsi.o 
../sanei/.libs/sanei_config2.o ../sanei/.libs/sanei_constrain_value.o  
/usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit
(cd .libs && rm -f libsane-ibm.1.so && ln -s libsane-ibm.1.0.12.so 
libsane-ibm.1.so)
(cd .libs && rm -f libsane-ibm.so && ln -s libsane-ibm.1.0.1

[sane-devel] Epson perfection 660 ->Problem building on OSX

2003-06-21 Thread Brian D. Williams
I have been trying to get sane to work with the epson perfection 660. I could
build sane with 1.0.11 but not with the snapscan addition. I could not build
1.0.12 at all. It would stop building at when trying to make scanimage but I
didn't see any error messages that made sense to me. I am running the latest os
x (10.2.6). Sadly I don't have a scanner available (other than the epson) to
test against. Any suggestions would be greatly appreciated.

Brian

--- Dino Tang  wrote:
> > But that's only with USB, isn't it? Or even only with this scanner? As
> > far as I know, SCSI scanners work with the epson backend on MacOS X.
> > At least I have one report about the Epson Perfection 1640SU working.
> >
> > More reports on which scanners work or don't work on MacOS X are
> > welcome.
> >
> 
> As long as the usblib was installed properly using the recent toolset ( 
> Dec 2002 ), quite a few of USB and SCSI devices should work.  I have 
> tested and got images back from the following devices:
> 
> - UMax Astra 1220U in USB mode
> * Reasonable image quality, still need color correction.
> - UMax Astra 2000U in USB mode
> * Serious image quality problem.
> - Epson Perfection 1640SU in both USB and SCSI modes
> * Good image quality.  Support a lot of options.  Good performance in 
> SCSI mode.
> - Epson Perfection 2450 PHOTO in USB mode
> * Good image quality.  Support a lot of options. Still has problems in 
> FireWire mode.
> - CANON IX-06015C ( similar to CanoScan 600 ) in SCSI mode
> * Does not support tiff format! ( --format=tiff ).  I can only get 
> image back in pnm format.  --format=tiff returned bad argument error.  
> This seems like a problem of the canon backend.  Please correct me if 
> I'm wrong.
> 
> I too would like to see reports on which scanners work or don't work on 
> MacOS X.
> 
> --Dino
> 
> ___
> Sane-devel mailing list
> sane-de...@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel

=
Brian Williams
homepage == 


[sane-devel] Epson Perfection 660 supported by SnapScan backend

2003-02-08 Thread Oliver Schwartz
Hi,

the Epson Perfection 660 is now supported by the SnapScan backend,=20
with a lot of testing effort from Bernard Cafarelli and others. The=20
reports I've received so far are encouraging but further tests are=20
welcome.

You can get the latest version of the backend from=20
http://sourceforge.net/project/showfiles.php?group_id=3D12742
If you own a Perfection 660 please test this versions and inform me of=20
any problems.

More information on the SnapScan backend is available from=20
http://snapscan.sourceforge.net

If you already have a self-compiled version of SANE installed make=20
sure to update your snapscan.conf file to include the new IDs for the=20
Perfection 660.=20

-Oliver



[sane-devel] epson perfection 660

2003-01-10 Thread Oliver Schwartz
Hi,

> in the end we got it so far:
> The Epson 660 seems to be a rebadged AGFA scnapscan e26

I received an USB log of a windows scan and the protocol looks indeed=20
similar. I'll change the snapscan backend to make it recognize the=20
scanner, maybe we're lucky.

Regards,

Oliver


[sane-devel] epson perfection 660

2003-01-10 Thread Jaeger, Gerhard
Hi there,

in the end we got it so far:
The Epson 660 seems to be a rebadged AGFA scnapscan e26
--> see below.

As scanimage currently does not work you might ask
the AGFA specialists on the sane mailing list...

Gerhard

BTW: No need to cc the mail to me!

On Friday, 10. January 2003 00:06, tcp-isim tcp-isim wrote:
> Hi
>
> I saw in a window directory this file called
> "scanner.dat":
>
> [SupportScannerNo]
> Number=2
>
> [ScannerModel]
> ;   Model Name,Length,NeedCheckOem
>
> 0Scanner=AGFASNAPSCAN e26,24,0
> 1Scanner=EPSON   Perfection 660  ,24,0
>
> ;A4 color CCD model firefly,Push Button
> ;0=CCD,1=CIS
> ;0=SCSI,1=Parallel,2=USB, 3=USBCIS
>
> [0Scanner]
> Name=Perfection 660
> SensorType=0
> Interface=2
> RefSize=8.426,11.6
> TPOSize=5,7
> Limit=TRUE
>
> [1Scanner]
> Name=Perfection 660
> SensorType=0
> Interface=2
> RefSize=8.426,11.6
> TPOSize=5,7
> Limit=TRUE
>
> [Other]
> Name=%s
> SensorType=0
> Interface=0,2
> RefSize=8.5,11.693
> TPOSize=5,7
> Limit=TRUE
>
> [DS]
> OPEN=0
> EVENT=0
> EXIT=0
> CLR=245
> CLG=215
> CLB=52
>
> Interresting, isn't it ?
>
> So, like snapscan scanners, I tried to load a
> firmware. I found the firmware taill_05.bin. So I
> tested agfafirm tail_058.bin
> the light scanner switch on, and move !
>
> But, scanimage doesn't work !
>
>  --- "Jaeger, Gerhard"  a écrit :
> > Hi,
> >
> > this doesn't look too good, I think that the 660
> > does
> > not contain a LM983x chipset. Ain't it possible that
> > you open the scanner?
> > Or does anybody else know what chipset it uses?
> >
> > Cheers
> >Gerhard
> >
> > On Monday, 6. January 2003 22:29, you wrote:
> > > On Debian testing I did :
> > > #insmod scanner vendor=0x4b8 product=0x114
> > >
> > > #sane-find-scanner
> > > found USB scanner (vendor = 0x04b8, product =
> >
> > 0x0114)
> >
> > > at device /dev/usbscanner
> > >
> > > #./checkm
> > > Checking /dev/usbscanner for MERLIN chipset...
> > > sanei_usb_read_bulk: read failed: Input/output
> >
> > error
> >
> > > UIO error
> > >
> > > #scanimage -d plustek:/dev/usbscanner -h return
> > > segmentation fault !!
> > >
> > > I'll try with the latest release (Debian unstable
> > > package)
> > >
> > >
> > > --- "Jaeger, Gerhard"  a écrit
> > >
> > > On Sunday, 5. January 2003 13:58, Karl Heinz
> >
> > Kremer
> >
> > > > wrote:
> > > > > It may work with the Plustek backend.
> > > >
> > > > Or may not! I suggest to check for the chip
> >
> > inside!
> >
> > > > There's a LM983x check on the download site for
> >
> > the
> >
> > > > Plustek backend, called "merlin testprogram":
>
> http://www.gjaeger.de/scanner/test/checkmerlin.tar.gz
>
> > > > You should have loaded the scanner kernel
> >
> > module...
> >
> > > > Gerhard
> > > >
> > > > > On Sun, Jan 05, 2003 at 01:31:54PM +0100,
> >
> > tcp-isim
> >
> > > > tcp-isim wrote:
> > > > > > Is is possible to use the EPSON PERFECTION
> >
> > 660
> >
> > > > under
> > > >
> > > > > > linux? I didn't see an article witch
> >
> > explains
> >
> > > > it's
> > > >
> > > > > > possible to use it.
> > > > > > Who hnows how to use the EPSON PERFECTION
> >
> > 660
> >
> > > > with
> > > >
> > > > > > SANE ?
> > > > > > David
> >


[sane-devel] epson perfection 660

2003-01-09 Thread Jaeger, Gerhard
Hi,

this doesn't look too good, I think that the 660 does
not contain a LM983x chipset. Ain't it possible that
you open the scanner?
Or does anybody else know what chipset it uses?

Cheers
   Gerhard

On Monday, 6. January 2003 22:29, you wrote:
> On Debian testing I did :
> #insmod scanner vendor=0x4b8 product=0x114
>
> #sane-find-scanner
> found USB scanner (vendor = 0x04b8, product = 0x0114)
> at device /dev/usbscanner
>
> #./checkm
> Checking /dev/usbscanner for MERLIN chipset...
> sanei_usb_read_bulk: read failed: Input/output error
> UIO error
>
> #scanimage -d plustek:/dev/usbscanner -h return
> segmentation fault !!
>
> I'll try with the latest release (Debian unstable
> package)
>
>
> --- "Jaeger, Gerhard"  a écrit : >
> On Sunday, 5. January 2003 13:58, Karl Heinz Kremer
>
> > wrote:
> > > It may work with the Plustek backend.
> >
> > Or may not! I suggest to check for the chip inside!
> > There's a LM983x check on the download site for the
> > Plustek backend, called "merlin testprogram":
>
> http://www.gjaeger.de/scanner/test/checkmerlin.tar.gz
>
> > You should have loaded the scanner kernel module...
> > Gerhard
> >
> > > On Sun, Jan 05, 2003 at 01:31:54PM +0100, tcp-isim
> >
> > tcp-isim wrote:
> > > > Is is possible to use the EPSON PERFECTION 660
> >
> > under
> >
> > > > linux? I didn't see an article witch explains
> >
> > it's
> >
> > > > possible to use it.
> > > > Who hnows how to use the EPSON PERFECTION 660
> >
> > with
> >
> > > > SANE ?
> > > > David
>


[sane-devel] epson perfection 660

2003-01-06 Thread Jaeger, Gerhard
On Sunday, 5. January 2003 13:58, Karl Heinz Kremer wrote:
> It may work with the Plustek backend.

Or may not! I suggest to check for the chip inside!
There's a LM983x check on the download site for the
Plustek backend, called "merlin testprogram":
http://www.gjaeger.de/scanner/test/checkmerlin.tar.gz

You should have loaded the scanner kernel module...
Gerhard

>
> On Sun, Jan 05, 2003 at 01:31:54PM +0100, tcp-isim tcp-isim wrote:
> > Is is possible to use the EPSON PERFECTION 660 under
> > linux? I didn't see an article witch explains it's
> > possible to use it.
> > Who hnows how to use the EPSON PERFECTION 660 with
> > SANE ?
> > David
> >
> > ___
> > Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
> > Yahoo! Mail : http://fr.mail.yahoo.com
> > ___
> > Sane-devel mailing list
> > sane-de...@www.mostang.com
> > http://www.mostang.com/mailman/listinfo/sane-devel


[sane-devel] epson perfection 660

2003-01-05 Thread tcp-isim tcp-isim
Is is possible to use the EPSON PERFECTION 660 under
linux? I didn't see an article witch explains it's
possible to use it.
Who hnows how to use the EPSON PERFECTION 660 with
SANE ? 
David

___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com


[sane-devel] epson perfection 660

2003-01-05 Thread Karl Heinz Kremer
It may work with the Plustek backend.

On Sun, Jan 05, 2003 at 01:31:54PM +0100, tcp-isim tcp-isim wrote:
> Is is possible to use the EPSON PERFECTION 660 under
> linux? I didn't see an article witch explains it's
> possible to use it.
> Who hnows how to use the EPSON PERFECTION 660 with
> SANE ?=20
> David
>=20
> ___
> Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran=E7ais !
> Yahoo! Mail : http://fr.mail.yahoo.com
> ___
> Sane-devel mailing list
> sane-de...@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel

--=20
Karl Heinz Kremer  k...@khk.net
PGP Key at http://www.khk.net/download/khk.asc
EPSON Sane Backend: http://www.khk.net