1sane-snapscan(5) SANE Scanner Access Now Easy sane-snapscan(5)
2
6 sane-snapscan - SANE backend for AGFA SnapScan flatbed scanners
7
9 The sane-snapscan library implements a SANE (Scanner Access Now Easy)
10 backend that provides access to AGFA SnapScan flatbed scanners. At
11 present, the following scanners are supported from this backend: AGFA
12 SnapScan 300, 310, 600, and 1236s, 1236u, 1212u, e20, e25, e40, e50,
13 e60, Vuego 310s, Acer 300f, 310s, 610s, 610plus, Prisa 620s, Prisa
14 620u, Prisa 620ut, Prisa 640u, Prisa 640bu, Prisa 1240, Prisa 3300,
15 Prisa 4300, Prisa 5300 and Guillemot Maxi Scan A4 Deluxe (SCSI) (with
16 varying success).
17
19 This backend expects device names of the form:
20 special
22 Where special is the path-name for the special device that corresponds
24 to a SCSI scanner. For SCSI scanners, the special device name must be a
25 generic SCSI device or a symlink to such a device. Under Linux, such a
26 device name could be /dev/sga or /dev/sge, for example. See sane-
27 scsi(5) for details.
28 For USB scanners the devicename must contain the keyword "usb", as in
30 /dev/usbscanner or /dev/usb/scanner0. For scanners that need a
31 firmware upload before scanning add a line starting with "firmware"
32 followed by the fully qualified path to your firmware file, e.g.
33 firmware /usr/share/sane/snapscan/firmware.bin
35 For further details read http://snapscan.sourceforge.net.
37
40 The contents of the snapscan.conf file is a list of device names that
41 correspond to SnapScan scanners. Empty lines and lines starting with a
42 hash mark (#) are ignored. See sane-scsi(5) on details of what consti‐
43 tutes a valid device name.
44
47 /etc/sane.d/snapscan.conf
48 The backend configuration file (see also description of
49 SANE_CONFIG_DIR below).
50 /usr/lib*/sane/libsane-snapscan.a
52 The static library implementing this backend.
53 /usr/lib*/sane/libsane-snapscan.so
55 The shared library implementing this backend (present on systems
56 that support dynamic loading).
57
59 SANE_CONFIG_DIR
60 This environment variable specifies the list of directories that
61 may contain the configuration file. Under UNIX, the directories
62 are separated by a colon (`:'), under OS/2, they are separated
63 by a semi-colon (`;'). If this variable is not set, the config‐
64 uration file is searched in two default directories: first, the
65 current working directory (".") and then in /etc/sane.d. If the
66 value of the environment variable ends with the directory sepa‐
67 rator character, then the default directories are searched after
68 the explicitly specified directories. For example, setting
69 SANE_CONFIG_DIR to "/tmp/config:" would result in directories
70 "tmp/config", ".", and "/etc/sane.d" being searched (in this
71 order).
72 SANE_DEBUG_SNAPSCAN
74 If the library was compiled with debug support enabled, this
75 environment variable controls the debug level for this backend.
76 E.g., a value of 255 requests all debug output to be printed.
77 Smaller levels reduce verbosity.
78
82 Man page doesn't provide much information yet.
83
86 sane(7), sane-scsi(5)
87 http://www.cs.ualberta.ca/~charter/SnapScan/snapscan.html
88 http://sourceforge.net/projects/snapscan/ (new development website)
89
92 Kevin Charter, Franck Schneider, Michel Roelofs, Emmanuel Blot, Mikko
93 Tyolajarvi, David Mosberger-Tang, Wolfgang Goeller, Petter Reinholdt‐
94 sen, Gary Plewa, Sebastien Sable, Oliver Schwartz and Mikael Magnusson.
95 Man page by Henning Meier-Geinitz (mostly based on the web pages and
96 source code).
97sane-backends 1.0.18 26 May 2001 sane-snapscan(5)