Oliver Rauch | 1 Dec 2007 01:01
Picon

Re: unable to specify sane default save-directory

Hello Julien,

the manual is not up to date. The saving directory handling has been
changed. The desired way is to give a complete path/filename in the
filename box. This is what automtically happens when you use the
filechooser dialog. When you enter only a filename without path then
the CWD (current working directory) is used.

The problem is that CWD is only updated to the last used directory when
xsane is closed. Looks like I have to change something here.

Best regards
Oliver

Am Freitag, den 30.11.2007, 23:06 +0100 schrieb Julien Michielsen:
> According to the official manual I should be able to specify the
> directory where sane saves its scans under preferences. However, when I
> go to preferences (in my xsane 0.994), I only see the options "save
> device settings"and "load device settings". In addition there is an
> option "setup" (under preferences) which allows to specify the tempo-
> rary directory. That is not what I want either. Does another possibility
> exist to specify the default save-directory?
> 
> Thanks
> -- 
> Julien Michielsen
> julien_at_michkloo.xs4all.nl
> 

--

-- 
(Continue reading)

Oliver Rauch | 1 Dec 2007 01:03
Picon

Re: ghostscript so much better with pdf files than xsane

Did you enable "save PDF zlib compressed" in preferences/setup/file
type ?

Best regards
Oliver

Am Freitag, den 30.11.2007, 23:05 +0100 schrieb Julien Michielsen:
> The filesize of as pdf saved scans is enourmous: one page scans often
> take more than 14 Mb of filespace. However, when reading a couple of
> them with ghostscript, in order to make a multipage pdf-file of it, the
> result shrinks to less than 15% of the original file:
> -rw-r--r-- 1 julien users  1817720 Nov 27 23:31 07brbtot.pdf
> -rw------- 1 julien users 14808071 Nov 27 17:48 07brb1.pdf
> -rw------- 1 julien users 16691483 Nov 27 17:50 07brb2.pdf
> -rw------- 1 julien users 13640821 Nov 27 23:30 07brb3.pdf
> 
> The first line (of 07brbtot.pdf) is the combination of the three pages
> 07brb1-3.
> 
> The command to create the combined file:
> 
> gs -q -sPAPERSIZE=a4 -dNOPAUSE -dBATCH -sDEVICE=pdfwrite
> -sOutputFile=07brbtot.pdf 07brb1.pdf 07brb2.pdf 07brb3.pdf
> 
> Especially when sending pdf's bij mail it is usefull to have small scan-
> files. Couldn't xsane incorporate a call to gs to reduce it's output?
> 
> Thanks
> 
> -- 
(Continue reading)

jazz_johnson | 1 Dec 2007 01:33
Picon

Re: ghostscript so much better with pdf files than xsane

> The filesize of as pdf saved scans is enourmous: one 
page scans often
> take more than 14 Mb of filespace.

I routinely routinely use Xsane to scan documents 
directly to pnm
(Portable aNy Map) format, which I then convert to 
muli-page pdf
files using netpbm tools. If the ink on a document is 
faded or non-uniform,
I ususally will scan  <at> 256 shades [1byte/pixel] of gray 
and then convert
to black & white [2bits/pixel]. A typical scan would 
be ~40-60K/page.
I wrote a shell script "scans2pdf" to filter the pnm 
to pdf.

http://www.acjlaw.net:8080/~jeremy/Ricoh/scripts/scans2pdf

If I have a series of grayscale scans in pnm format 
named out.%04d.pnm
I would convert the pnm images to a single multi-page 
pdf thus:
#scans2pdf -bw 0.6 out
which would create out.pdf and then remove the 
out.*.pnm files

There is also a program "tic98" which will compress 
pnm text documents
using a dictionary of the scanned characters. It 
(Continue reading)

cgi-mailer | 2 Dec 2007 18:34
Picon

Formulardaten


===========================================
== Neuer Eintrag
===========================================

      
-------------------------------------------
-- Formular: 'adddev'
-------------------------------------------

1. Your email address:
   'benjamin.kensche <at> web.de'
2. Manufacturer (e.g. "Mustek"):
   'Canon'
3. Model name (e.g. ScanExpress 1200UB):
   'CanoScan LiDE 600F'
4. Bus type:
   'USB'
5. Vendor id (e.g. 0x001):
   '0x04A9'
6. Product id (e.g. 0x0002):
   '0x2224'
7. Chipset (e.g. lm9831):
   ''
8. Comments (e.g. similar to Mustek 1234):
   ''
9. Data (e.g. sane-find-scanner -v -v):
   '<device descriptor of 0x04a9/0x2224 at 001:006 (Canon CanoScan)>
bLength               18
bDescriptorType       1
(Continue reading)

cgi-mailer | 2 Dec 2007 21:03
Picon

Formulardaten


===========================================
== Neuer Eintrag
===========================================

      
-------------------------------------------
-- Formular: 'adddev'
-------------------------------------------

1. Your email address:
   'philip.aston <at> ntlworld.com'
2. Manufacturer (e.g. "Mustek"):
   'artec'
3. Model name (e.g. ScanExpress 1200UB):
   'E+pro'
4. Bus type:
   'USB'
5. Vendor id (e.g. 0x001):
   '0x05d8'
6. Product id (e.g. 0x0002):
   '0x4004'
7. Chipset (e.g. lm9831):
   'GT -6816'
8. Comments (e.g. similar to Mustek 1234):
   'Support is listed as minimal, but I now have it working.
/etc/sane.d/artec_eplus48u.conf  was used, all options except the E+pro commented out. However this
section required "option artecFirmwareFile /usr/share/sane/artec_eplus48u/1200.usb" which was
not present. I made this directory and added the file 1200.usb from my Windows cd supplied with the scanner
and with necesssary permissions change xsane operated as expected, with one exception: 1200 dpi is not
(Continue reading)

Mich Linux | 3 Dec 2007 03:46
Picon
Favicon

Problems with HP 6200C


I'm having problems getting my scanner working

HP scanjet 6200c
Fedora 8
Kernel: 2.6.23
Sane: 1.0.18
It Currently works 100% in windows.
It worked with Linux/sane in the past (6months or more.. don't use it that often so hard to say)
Sane has no problem detecting the scanner.
Other USB devices working fine.

Outputs:
[root <at> tbred ~]# sane-find-scanner
~
found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0201 [HP ScanJet 6200C]) at libusb:004:004
~

[root <at> tbred ~]# scanimage -L
device `hp:libusb:004:004' is a Hewlett-Packard ScanJet 62x0C flatbed scanner

[root <at> tbred ~]# scanimage -T 
scanimage: unable to determine option count (xsane returns the same error)

dmesg:
usb 4-2: reset full speed USB device using uhci_hcd and address 4
usb 4-2: failed to restore interface 0 altsetting 0 (error=-110)
usb 4-2: USB disconnect, address 4
usb 4-2: new full speed USB device using uhci_hcd and address 5
usb 4-2: configuration #1 chosen from 1 choice
(Continue reading)

Johannes Ranke | 3 Dec 2007 11:08
Picon
Picon
Favicon

CanoScan LiDE30 problem

Hi,

My Canoscan LiDE30 used to work nicely under Debian unstable for more
than a year. Since about half a year it makes problems: If I scan from a
frontend like quiteinsane, I can select the device  (I am using libusb),
and the frontend pretends to scan, but the scanner does nothing, so I
end up with a black image. The scanner works under Windows. Last week,
after I tested under Windows, it worked under Linux, too.

  $ scanimage -L
  device `v4l:/dev/video0' is a Noname BT878 video (AVerMedia AVerTV D
  virtual device
  device `plustek:libusb:003:003' is a Canon CanoScan N1240U/LiDE30
  flatbed scanner

I discovered that I can scan from the command line as normal user:

  $ SANE_DEBUG_PLUSTEK=128 scanimage -d 'plustek:libusb:003:003' \
      > image.pnm \
      2> canoscanLiDE30.err

I am attaching the output of this. Graphical frontends still don't work,
even when specifying the device on the command line for xscanimage, or 
selecting it in quiteinsane.

I also noticed the following dmesg output after trying to scan with
xscanimage: 

  usb 3-2: usbfs: interface 0 claimed by usbfs while 'xscanimage' sets
  config #1
(Continue reading)

Gerard Klaver | 3 Dec 2007 18:20
Picon

Re: CanoScan LiDE30 problem

On Mon, 2007-12-03 at 11:08 +0100, Johannes Ranke wrote:
> Hi,
> 
> My Canoscan LiDE30 used to work nicely under Debian unstable for more
> than a year. Since about half a year it makes problems: If I scan from a
> frontend like quiteinsane, I can select the device  (I am using libusb),
> and the frontend pretends to scan, but the scanner does nothing, so I
> end up with a black image. The scanner works under Windows. Last week,
> after I tested under Windows, it worked under Linux, too.
> 
>   $ scanimage -L
>   device `v4l:/dev/video0' is a Noname BT878 video (AVerMedia AVerTV D
>   virtual device
>   device `plustek:libusb:003:003' is a Canon CanoScan N1240U/LiDE30
>   flatbed scanner
> 
> I discovered that I can scan from the command line as normal user:
> 
>   $ SANE_DEBUG_PLUSTEK=128 scanimage -d 'plustek:libusb:003:003' \
>       > image.pnm \
>       2> canoscanLiDE30.err
> 
> I am attaching the output of this. Graphical frontends still don't work,
> even when specifying the device on the command line for xscanimage, or 
> selecting it in quiteinsane.
> 
> I also noticed the following dmesg output after trying to scan with
> xscanimage: 
> 
>   usb 3-2: usbfs: interface 0 claimed by usbfs while 'xscanimage' sets
(Continue reading)

Gerhard Jaeger | 3 Dec 2007 22:20
Picon

Re: CanoScan LiDE30 problem

Am Montag, 3. Dezember 2007 11:08:15 schrieb Johannes Ranke:
> Hi,
>
> My Canoscan LiDE30 used to work nicely under Debian unstable for more
> than a year. Since about half a year it makes problems: If I scan from a
> frontend like quiteinsane, I can select the device  (I am using libusb),
> and the frontend pretends to scan, but the scanner does nothing, so I
> end up with a black image. The scanner works under Windows. Last week,
> after I tested under Windows, it worked under Linux, too.

This is a know issue and relatet to the suspend feature on the kernel
you are using, disable the CONFIG_USB_SUSPEND kernel config option and
recompile the kernel. 

Thought this has been fixed in more recent versions. Maybe there
are some motr better ideas around - or check this list for USB_SUSPEND...

HTH
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

Adam Sulmicki | 3 Dec 2007 22:26
Picon

Microtek ScanMaker 4900 (USB2400) and Qemu

Ok, so I got the Microtek ScanMaker 4900 (USB2400) to work under Linux
as follows:

Linux Fedora 8 -> Qemu 0.9.0 -> Windows 98 SE -> Microtek ScanWizard 5

What would be the next step? Any idea?

-- 
Adam Sulmicki
http://www.eax.com      The Supreme Headquarters of the 32 bit registers

--

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


Gmane