[sane-devel] 3 minor problems with current (20061202) CVS code on OS/2

2006-12-02 Thread Franz Bakan
Hi,

two minor problems on OS/2 with current CVS (since 1. 12. 2006)

1. configure  (generated by Autoconf 2.59e) fails and claims
   not to find grep (which is bogus)

 Running autoconf (2.59) locally solves the problem.

2 I have to add
 #include sys/socket.h
 to 
 .sanei\sanei_tcp.c
because otherwise AF_INET is not defined.

3. : *** No rule to make target `libsane-epson2.la', needed by `all'.  Stop.

probably a temporary problem until epson2 - code  is added..

Thanks for listening
Franz




[sane-devel] Re: Plustec OpticSlim 12M - calibration

2006-12-02 Thread Maciej Piechotka
On Fri, 01 Dec 2006 07:11:35 +0100, Gerhard Jaeger wrote:

 On Friday 01 December 2006 00:21, Maciej Piechotka wrote:
 I have probably not calibrated scanner (If I scan something it returns
 blue sheet). How can I do it?
 
 
 RTFM - SCNR ;)
 The status of this device says: Scans, but no calibration is performed and 
 the area selection is limited.
 
 There's no way for you to do the calibration, as the backend itself is not
 able to handle this - sorry
 
 Gerhard
 


Sorry I asked in such way - is it possible to make it working (after give
some values from hand)?

If I understand you it's also[1] impossible by operating in such values as
R/G/B Brightness and so on in xsane or any other front-end) - am I correct?

Regards

[1] As I said I thought I could give some values to make it working and
it's just automatized process.

-- 
I've probably left my head... somewhere. Please wait untill I find it.
Homepage (pl_PL): http://uzytkownik.jogger.pl/
(GNU/)Linux User: #425935 (see http://counter.li.org/)



[sane-devel] Re: Plustec OpticSlim 12M - calibration

2006-12-02 Thread Gerard Klaver
On Sat, 2006-12-02 at 00:41 +0100, Maciej Piechotka wrote:
 On Fri, 01 Dec 2006 07:11:35 +0100, Gerhard Jaeger wrote:
 
  On Friday 01 December 2006 00:21, Maciej Piechotka wrote:
  I have probably not calibrated scanner (If I scan something it returns
  blue sheet). How can I do it?
  
  
  RTFM - SCNR ;)
  The status of this device says: Scans, but no calibration is performed and 
  the area selection is limited.
  
  There's no way for you to do the calibration, as the backend itself is not
  able to handle this - sorry
  
  Gerhard
  
 
 
 Sorry I asked in such way - is it possible to make it working (after give
 some values from hand)?
 
 If I understand you it's also[1] impossible by operating in such values as
 R/G/B Brightness and so on in xsane or any other front-end) - am I correct?
 
 Regards
 
 [1] As I said I thought I could give some values to make it working and
 it's just automatized process.
 
 -- 
 I've probably left my head... somewhere. Please wait untill I find it.
 Homepage (pl_PL): http://uzytkownik.jogger.pl/
 (GNU/)Linux User: #425935 (see http://counter.li.org/)
 
 
If you see the frontend menu for this scanner (xscanimage or xsane) the
only fields for some color correction are maybe the gamma value and/or
selecting the red, green or blue (gray mode color).

To get the calibration into the backend some usb sniff or usb log is
needed using the calibration sheet and then writing program code for it.
I don't know if somebody already made some usb sniff/log file?

I have placed on my page some info and a sample of the calibration card
for this scanner see http://gkall.hobby.nl/gt6816-07b3-0412.html

-- 

m.vr.gr.
Gerard Klaver




[sane-devel] 3 minor problems with current (20061202) CVS code on OS/2

2006-12-02 Thread Jon Chambers

Hi Alessandro,

On Sat, 2 Dec 2006, Alessandro Zummo wrote:
 1. configure  (generated by Autoconf 2.59e) fails and claims
not to find grep (which is bogus)
  Running autoconf (2.59) locally solves the problem.
 [...]
 dunno how to resolve the autoconf problem though... maybe only
 configure.in should be shipped.

I have also fallen for this and been the Bad Man to break the OS/2 build 
by simply using the default autoconf installed on my debian box!  The 
solution is just to install autoconf 2.59 (eg: from tarball), use that to 
generate ./configure, test and check in the result.

There used to be a note about correct autoconf versions on the SANE 
website although a quick search just now failed to find it.

cheers,
Jon

== Jon Chambers =
  http://www.jon.demon.co.uk, 020 8575 7097, 07931 961669
=



[sane-devel] Re: Plustec OpticSlim 12M - calibration

2006-12-02 Thread Maciej Piechotka
On Sat, 02 Dec 2006 16:11:34 +0100, Gerard Klaver wrote:

 On Sat, 2006-12-02 at 00:41 +0100, Maciej Piechotka wrote:
 On Fri, 01 Dec 2006 07:11:35 +0100, Gerhard Jaeger wrote:
 
  On Friday 01 December 2006 00:21, Maciej Piechotka wrote:
  I have probably not calibrated scanner (If I scan something it returns
  blue sheet). How can I do it?
  
  
  RTFM - SCNR ;)
  The status of this device says: Scans, but no calibration is performed and 
  the area selection is limited.
  
  There's no way for you to do the calibration, as the backend itself is not
  able to handle this - sorry
  
  Gerhard
  
 
 
 Sorry I asked in such way - is it possible to make it working (after give
 some values from hand)?
 
 If I understand you it's also[1] impossible by operating in such values as
 R/G/B Brightness and so on in xsane or any other front-end) - am I correct?
 
 Regards
 
 [1] As I said I thought I could give some values to make it working and
 it's just automatized process.
 
 -- 
 I've probably left my head... somewhere. Please wait untill I find it.
 Homepage (pl_PL): http://uzytkownik.jogger.pl/
 (GNU/)Linux User: #425935 (see http://counter.li.org/)
 
 
 If you see the frontend menu for this scanner (xscanimage or xsane) the
 only fields for some color correction are maybe the gamma value and/or
 selecting the red, green or blue (gray mode color).
 

Ok. I'll try to use it.

 To get the calibration into the backend some usb sniff or usb log is
 needed using the calibration sheet and then writing program code for it.
 I don't know if somebody already made some usb sniff/log file?
 

What's a name of open usb sniffer?
Should I send a sniff from GNU/Linux or from Windows?

 I have placed on my page some info and a sample of the calibration card
 for this scanner see http://gkall.hobby.nl/gt6816-07b3-0412.html
 

I've been there searching informations.
I have the same calibration sheet.

Regards
-- 
I've probably left my head... somewhere. Please wait untill I find it.
Homepage (pl_PL): http://uzytkownik.jogger.pl/
(GNU/)Linux User: #425935 (see http://counter.li.org/)



[sane-devel] trying to get a Benq4300U USB scanner working .....

2006-12-02 Thread Michael Fothergill

Dear sane people,


I have tried to get my scanner to work a number of times under
Fedora Core 6 on my machine (1200 MHz Athlon) but have not
succeeded.

I am now trying with Debian on the same machine on a second drive.

It is pretty recalcitrant and it may still not work but I will post
some of my efforts here and if you would make suggestions I would be
grateful.

What is REALLY sad is that if I can't succeed I will have to wipe
Fedora off and reinstall Windows 98 just so I can scan images.

Yikes

The other alternative is to go to the library and use the scanner
there.  I would still be using Windows but at least not on my own
machine.

OK.  Here goes.

As you can see I have edited the snapscan.conf file that lives in
/etc/sane.d and bunged in the driver for the scanner I use and the
device directory /dev/usb/scanner0.

more snapscan.conf
#-- General
#---

# Change to the fully qualified filename of your firmware file, if
# firmware upload is needed by the scanner
firmware /home/mikef/benq4300/u222v067.bin

# If not automatically found you may manuaully specify a device
name.

# For USB scanners also specify bus=usb, e.g.
# /dev/usb/scanner0 bus=usb

# For SCSI scanners specify the generic device, e.g. /dev/sg0 on
Linux.
# /dev/sg0

#---
# No changes should be necessary below this line
#---

#-- SCSI scanners
--
# These SCSI devices will be probed automatically
scsi AGFA * Scanner
scsi COLOR * Scanner
scsi Color * Scanner
scsi ACERPERI * Scanner

#--- USB scanners
---
# These USB devices will be probed automatically
# (This will currently work only on Linux)

# Benq/Acer/Vuego 310U
usb 0x04a5 0x1a20
usb 0x04a5 0x1a26

# Benq/Acer/Vuego 320U
usb 0x04a5 0x2022

# Benq/Acer/Vuego 620U / 620UT
usb 0x04a5 0x1a2a
usb 0x04a5 0x2040

# Benq/Acer/Vuego 640U
usb 0x04a5 0x2060

# Benq/Acer/Vuego 640BU
usb 0x04a5 0x207e

# Benq/Acer/Vuego 640BT
usb 0x04a5 0x20be

# Benq/Acer/Vuego 1240U
usb 0x04a5 0x20c0

# Benq/Acer/Vuego 3300 / 4300
usb 0x04a5 0x20b0

# Benq/Acer/Vuego 4300
usb 0x04a5 0x20de

# Benq/Acer/Vuego 5000
usb 0x04a5 0x20fc

# Benq/Acer/Vuego 5300
usb 0x04a5 0x20fe

# Agfa 1236U
usb 0x06bd 0x0002

# Agfa 1212U
usb 0x06bd 0x0001
usb 0x06bd 0x2061

# Agfa Snapscan e10
usb 0x06bd 0x2093

# Agfa Snapscan e20
usb 0x06bd 0x2091

# Agfa Snapscan e25
usb 0x06bd 0x2095

# Agfa Snapscan e26
usb 0x06bd 0x2097

# Agfa Snapscan e40
usb 0x06bd 0x208d

# Agfa Snapscan e42
usb 0x06bd 0x20ff

# Agfa Snapscan e50
usb 0x06bd 0x208f

# Agfa Snapscan e52
usb 0x06bd 0x20fd

# Epson Perfection 660
usb 0x04b8 0x0114

# Epson Perfection 1670
usb 0x04b8 0x011f

# Epson Perfection 2480
usb 0x04b8 0x0121
mikef@spc2-burn3-0-0-cust329:/etc/sane.d$

OK, now let's try to detect it.  I have changed my user group to include 
the scanner group.

Apparently you are supposed to do this.

But I am logged in as root at the terminal I am showing now to help ease 
things.



spc2-burn3-0-0-cust329:/proc/bus/usb/002# sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If
the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # 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.

found USB scanner (vendor=0x04a5, product=0x20b0) at libusb:002: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.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other
proprietary ports
  # can't be detected by this program.


It looks like it has found it.  But don't get too excited.

Let's try something else;

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).

Hmmm..  It can't find it now. I think if it is a USB device I once read 
somewhere that scanimage -L might not work so easily c.f. SCSI in this 
situation.

Comments please.

OK, let's rock the joint and run cat /proc/bus/usb/devices:

spc2-burn3-0-0-cust329:/proc/bus/usb/002# cat /proc/bus/usb/devices


T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 3
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor= ProdID= Rev= 0.00
S:  

[sane-devel] 3 minor problems with current (20061202) CVS code on OS/2

2006-12-02 Thread Franz Bakan
On Sat, 2 Dec 2006 14:23:05 +0100, Alessandro Zummo wrote:

  probably a temporary problem until epson2 - code  is added..
 
  ach! :( 
  will commit a patch soon, thanks!

Thanks, this leads to other problems ;-)

epson2.c:53:27: asm/byteorder.h: No such file or directory
epson2.c:841: warning: implicit declaration of function `__le16_to_cpup'
epson2.c:841: error: `__u16' undeclared (first use in this function)
epson2.c:1256: warning: implicit declaration of function `__le32_to_cpup'
epson2.c:1256: error: `__u32' undeclared (first use in this function)
epson2.c:4336: error: `__le32' undeclared (first use in this function)
epson2.c:4338: warning: implicit declaration of function `__cpu_to_le32'

(the warnings will change to errors about unresolved symbols,
if I expand '__u16' to 'unsingned short' and so on.

Franz




[sane-devel] 3 minor problems with current (20061202) CVS code on OS/2

2006-12-02 Thread Alessandro Zummo
On Sat, 02 Dec 2006 20:04:37 +0100 (CET)
Franz Bakan fba...@gmx.net wrote:

 On Sat, 2 Dec 2006 14:23:05 +0100, Alessandro Zummo wrote:
 
   probably a temporary problem until epson2 - code  is added..
  
   ach! :( 
   will commit a patch soon, thanks!
 
 Thanks, this leads to other problems ;-)
 
 epson2.c:53:27: asm/byteorder.h: No such file or directory
 epson2.c:841: warning: implicit declaration of function `__le16_to_cpup'
 epson2.c:841: error: `__u16' undeclared (first use in this function)
 epson2.c:1256: warning: implicit declaration of function `__le32_to_cpup'
 epson2.c:1256: error: `__u32' undeclared (first use in this function)
 epson2.c:4336: error: `__le32' undeclared (first use in this function)
 epson2.c:4338: warning: implicit declaration of function `__cpu_to_le32'
 
 (the warnings will change to errors about unresolved symbols,
 if I expand '__u16' to 'unsingned short' and so on.


 well, you need to check where are those functions/types
 defined on os/2 :)

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Turin, Italy

  http://www.towertech.it



[sane-devel] 3 minor problems with current (20061202) CVS code on OS/2

2006-12-02 Thread Franz Bakan
On Sat, 2 Dec 2006 20:31:06 +0100, Alessandro Zummo wrote:

  well, you need to check where are those functions/types
  defined on os/2 :)

Yes, I know and already checked, but unfortunattely there is not place where

__le16_to_cpup(), __u16,, __le32_to_cpup(),
__u32,  __le32 or __cpu_to_le32()

are defined on OS/2. What do you suggest?

Franz




[sane-devel] Does Epson Expression 10000XL support auto cropping

2006-12-02 Thread Karl Heinz Kremer
That depends on the scanner. Some scanners do allow image processing in the
scanner, others just deliver the raw image data.


On 12/1/06, Sam sas...@yahoo.com wrote:

 I have a general question as to the inner workings of
 a scanner.

 Do scanners (or Epson) generally capture a Raw image
 and pass it on to a front end program? or does the
 scanner do some image processing.

 I guess if a scanner can do some image processing,
 then the same or better can be done at the front-end
 side.

 Does anyone have a favorite front-end to hook up to
 SANE?

 thanks
 sam








 --- Karl Heinz Kremer k...@khk.net wrote:

  The scanner does not support auto cropping. This
  feature would have to be
  implemented in a frontend.
 
  You can see all features offered by a
  scanner/backend by using the scanimage
  application with the --help parameter (see the man
  page
  http://www.sane-project.org/man/scanimage.1.html for
  more information).
 
 
  On 12/1/06, Chittananda Kulatilake
  chittana...@gmail.com wrote:
  
   Hi All,
  
   I want to do auto cropping using Epson Expression
  1XL scanner. Does
   this
   scanner support for that? If so can pl send me C++
  code snippets?
  
   Is there any software aviable to see the list
  fucntions supported by a
   printer?
  
   Thank you in advance.
  
   Chitta
   --
   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-requ...@lists.alioth.debian.org
  
  
   --
  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-requ...@lists.alioth.debian.org





 
 Yahoo! Music Unlimited
 Access over 1 million songs.
 http://music.yahoo.com/unlimited

 --
 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-requ...@lists.alioth.debian.org

-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061202/150c9ad4/attachment.html
From azummo-li...@towertech.it  Sat Dec  2 22:11:01 2006
From: azummo-li...@towertech.it (Alessandro Zummo)
Date: Sat Dec  2 22:11:09 2006
Subject: [sane-devel] 3 minor problems with current (20061202) CVS code
on OS/2
References: 20061202203106.48b3d8f4@inspiron
Message-ID: 20061202221101.4e8f168b@inspiron

On Sat, 02 Dec 2006 21:26:25 +0100 (CET)
Franz Bakan fba...@gmx.net wrote:

 On Sat, 2 Dec 2006 20:31:06 +0100, Alessandro Zummo wrote:
 
   well, you need to check where are those functions/types
   defined on os/2 :)
 
 Yes, I know and already checked, but unfortunattely there is not place where
 
 __le16_to_cpup(), __u16,, __le32_to_cpup(),
 __u32,  __le32 or __cpu_to_le32()
 
 are defined on OS/2. What do you suggest?

 mmm.. you should try to find similar macros we
 can use/adapt in some OS/2 include file... I guess
 endianness conversion is performed even on OS/2 ;)


-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Turin, Italy

  http://www.towertech.it



[sane-devel] [solved?] Re: Plustec OpticSlim 12M - calibration

2006-12-02 Thread Maciej Piechotka
On Fri, 01 Dec 2006 00:21:08 +0100, Maciej Piechotka wrote:

 I have probably not calibrated scanner (If I scan something it returns
 blue sheet). How can I do it?
 
 Regards

I do 2 calibration on windows and it works ok.
I think I do not update nothing. Anyway thanks...

Regards
-- 
I've probably left my head... somewhere. Please wait untill I find it.
Homepage (pl_PL): http://uzytkownik.jogger.pl/
(GNU/)Linux User: #425935 (see http://counter.li.org/)



[sane-devel] Missing greys

2006-12-02 Thread Pierre Willenbrock
Hi Henrik

Henrik Uggla schrieb:
 I've got a Canoscan Lide 50. I have discovered that when I scan at 150
 dpi or more the greys are missing in depth (in the black end). But when
 I scan at only 75 dpi the result looks much better since darker and
 lighter pixels are mixed to show the right grey nuance. Is it possible
 to have this behaviour at higher resolutions as well and in that way
 creating those missing greys?

I can't explain why there is a difference between calibration for 75dpi
compared to 150dpi(You didn't scan them at different bit depth, i
guess). But anyways, dark shades were incorrect since the beginning of
Canon LiDE 50 support.

I had some improvements to the calibration process sitting in my local
copy since about 3 months, so i just committed them. You can get them
from the cvs repository. Test results for the current method are welcome.

Regards,
  Pierre