1sane-microtek(5) SANE Scanner Access Now Easy sane-microtek(5)
2
6 sane-microtek - SANE backend for Microtek scanners
7
9 The sane-microtek library implements a SANE (Scanner Access Now Easy)
10 backend that provides access to the "second generation" Microtek scan‐
11 ners. At present, the following hardware is known to work with this
12 backend:
13 Microtek ScanMaker E2, E3, E6
15 Microtek ScanMaker II, IIG, IIHR, IISP, III
16 Microtek ScanMaker 35t, 35t+, 45t
17 Microtek ScanMaker 600GS, 600ZS (see bug notes)
18 Agfa StudioScan
19 Agfa StudioScan II, StudioScan IIsi
20 Agfa Arcus II (but not the "Arcus")
21 Agfa DuoScan (preliminary)
22 Vobis "Highscreen Realscan"
23 Microtek Color PageWiz (preliminary)
24 Transparent Media Adapter
26 Document AutoFeeder
27 The driver supports line art, halftone, 8bpp gray, and 24bpp color
29 scans at normal and "expanded" resolutions (i.e. 1200x1200 on an E6),
30 fast scans for color previews, and downloadable gamma tables.
31 The supported scanners are all SCSI scanners. However, some parallel
33 port models may work (under Linux), if they use a parport->scsi chip,
34 and if you can find a scsi->parport driver. This is known to be the
35 case for the Color PageWiz.
36 The driver does not support the newest Microtek scanners, such as the
38 V330 and V660, which use a new and very different SCSI-II command set.
39 For those, try the alternate microtek2 backend. Most non-SCSI scanners
40 would use the new command set. Most scanners newer than the Scanmaker
41 E6 would use the new command set.
42 If you own a Microtek scanner other than the ones listed above, tell us
44 what happens --- see the BUGS section at the end of this document.
45 Although this manual page is generally updated with each release, up-
47 to-date information on new releases and extraneous helpful hints are
48 available from the backend homepage:
49 http://www.mir.com/mtek/
50
53 This backend expects device names of the form:
54 special
56 Where special is the UNIX path-name for the special device that corre‐
58 sponds to the scanner. The special device name must be a generic SCSI
59 device or a symlink to such a device. Under Linux, such a device name
60 could be /dev/sga or /dev/sge, for example.
61
63 The contents of the microtek.conf file is a list of device names that
64 correspond to Microtek scanners. Empty lines and lines starting with a
65 hash mark (#) are ignored. A sample configuration file is shown below:
66 /dev/scanner
68 # this is a comment
69 /dev/sge
70 The configuration file may also contain the special tokens norealcal or
72 noprecal. norealcal will disable the use of magic, undocumented scan‐
73 ner calibration commands which are known to work on the E6, but may not
74 work with other models. noprecal will disable logic which tries to
75 avoid scanner precalibration. This logic would only have been acti‐
76 vated if the magic calibration code was turned off.
77
80 /etc/sane.d/microtek.conf
81 The backend configuration file (see also description of
82 SANE_CONFIG_DIR below).
83 /usr/lib*/sane/libsane-microtek.a
85 The static library implementing this backend.
86 /usr/lib*/sane/libsane-microtek.so
88 The shared library implementing this backend (present on systems
89 that support dynamic loading).
90
93 SANE_CONFIG_DIR
94 This environment variable specifies the list of directories that
95 may contain the configuration file. Under UNIX, the directories
96 are separated by a colon (`:'), under OS/2, they are separated
97 by a semi-colon (`;'). If this variable is not set, the config‐
98 uration file is searched in two default directories: first, the
99 current working directory (".") and then in /etc/sane.d. If the
100 value of the environment variable ends with the directory sepa‐
101 rator character, then the default directories are searched after
102 the explicitly specified directories. For example, setting
103 SANE_CONFIG_DIR to "/tmp/config:" would result in directories
104 "tmp/config", ".", and "/etc/sane.d" being searched (in this
105 order).
106 SANE_DEBUG_MICROTEK
108 If the library was compiled with debugging support enabled, this
109 environment variable controls the debug level for this backend.
110 A value of 128 requests maximally copious debug output; smaller
111 levels reduce verbosity.
112
115 sane(7), sane-scsi(5)
116
119 Matt Marjanovic
120
123 Known bugs/limitations are:
124 Brightness and contrast broken.
126 The 600GS is grayscale only, and will lock up if you select
127 color. (Unfortunately, the 600GS and 600ZS are indistinguish‐
128 able by software.)
129 i.e. don't complain about these --- but if brightness and/or contrast
131 do work for you, please tell me.
132 If your scanner locks up, try setting the norealcal or noprecal option
134 in the configuration file (first one, then both), and see if it helps.
135 (If it does, report it.)
136 Send lengthy bug reports and new scanner information to mtek-
138 bugs@mir.com. All bug reports and new scanner inquiries should include
139 an error log file. You can generate copious stderr output by setting
140 the SANE_DEBUG_MICROTEK environment variable described above. For
141 example:
142 setenv SANE_DEBUG_MICROTEK 128
144 More general comments, suggestions, and inquiries about frontends or
146 SANE should go to sane-devel@lists.alioth.debian.org, the SANE Develop‐
147 ers mailing list. Have a look at http://www.sane-project.org/mailing-
148 lists.html concerning subscription to sane-devel.
149sane-backends 1.0.18 February 8, 2000 sane-microtek(5)