Debian Codegraph @

upstream/debian-unstable/man5/sane-microtek.5

raw
1 .TH sane\-microtek 5 "13 Jul 2008" "" "SANE Scanner Access Now Easy"
2 .IX sane\-microtek
3 .SH NAME
4 sane\-microtek \- SANE backend for Microtek scanners
5 .SH DESCRIPTION
6 The
7 .B sane\-microtek
8 library implements a SANE (Scanner Access Now Easy) backend that
9 provides access to the "second generation" Microtek scanners. At present,
10 the following hardware is known to work with this backend:
11 .PP
12 .RS
13 Microtek ScanMaker E2, E3, E6
14 .br
15 Microtek ScanMaker II, IIG, IIHR, IISP, III
16 .br
17 Microtek ScanMaker 35t, 35t+, 45t
18 .br
19 Microtek ScanMaker 600GS, 600ZS (see bug notes)
20 .br
21 Agfa StudioScan
22 .br
23 Agfa StudioScan II, StudioScan IIsi
24 .br
25 Agfa Arcus II (but not the "Arcus")
26 .br
27 Agfa DuoScan (preliminary)
28 .br
29 Vobis "Highscreen Realscan"
30 .br
31 Microtek Color PageWiz (preliminary)
32 .br
33 .PP
34 Transparent Media Adapter
35 .br
36 Document AutoFeeder
37 .br
38 .RE
39 .PP
40 The driver supports line art, halftone, 8bpp gray, and 24bpp color scans
41 at normal and "expanded" resolutions (i.e. 1200x1200 on an E6), fast scans
42 for color previews, and downloadable gamma tables.
43 .PP
44 The supported scanners are all SCSI scanners. However, some parallel
45 port models may work (under Linux), if they use a parport->scsi chip,
46 and if you can find a scsi->parport driver. This is known to be the
47 case for the Color PageWiz.
48 .PP
49 The driver does
50 .B not
51 support the newest Microtek scanners, such as the V330 and V660, which use
52 a new and very different SCSI-II command set. For those, try the alternate
53 .BR microtek2 (5)
54 backend. Most non-SCSI scanners would use the new command set. Most
55 scanners newer than the Scanmaker E6 would use the new command set.
56 .PP
57 If you own a Microtek scanner other than the ones listed above, tell us
58 what happens --- see the
59 .BR BUGS
60 section at the end of this document.
61 .PP
62 Although this manual page is generally updated with each release,
63 up-to-date information on new releases and extraneous helpful hints
64 are available from the backend homepage:
65 .br
66 .PP
67 .RS
68 .I http://www.mir.com/mtek/
69 .RE
70
71 .SH "DEVICE NAMES"
72 This backend expects device names of the form:
73 .PP
74 .RS
75 .I special
76 .RE
77 .PP
78 Where
79 .I special
80 is the UNIX path-name for the special device that corresponds to the
81 scanner. The special device name must be a generic SCSI device or a
82 symlink to such a device. Under Linux, such a device name could be
83 .I /dev/sga
84 or
85 .IR /dev/sge ,
86 for example.
87 .PP
88
89 .SH CONFIGURATION
90 The contents of the
91 .I microtek.conf
92 file is a list of device names that correspond to Microtek
93 scanners. Empty lines and lines starting with a hash mark (#) are
94 ignored. A sample configuration file is shown below:
95 .PP
96 .RS
97 /dev/scanner
98 .br
99 # this is a comment
100 .br
101 /dev/sge
102 .RE
103 .PP
104 The configuration file may also contain the special tokens
105 .I norealcal
106 or
107 .IR noprecal .
108 .I norealcal
109 will disable the use of magic, undocumented scanner calibration commands
110 which are known to work on the E6, but may not work with other models.
111 .I noprecal
112 will disable logic which tries to avoid scanner precalibration. This logic
113 would only have been activated if the magic calibration code was turned off.
114
115 .PP
116 .SH FILES
117 .TP
118 .I /etc/sane.d/microtek.conf
119 The backend configuration file (see also description of
120 .B SANE_CONFIG_DIR
121 below).
122 .TP
123 .I /usr/lib/x86_64-linux-gnu/sane/libsane\-microtek.a
124 The static library implementing this backend.
125 .TP
126 .I /usr/lib/x86_64-linux-gnu/sane/libsane\-microtek.so
127 The shared library implementing this backend (present on systems that
128 support dynamic loading).
129
130 .SH ENVIRONMENT
131 .TP
132 .B SANE_CONFIG_DIR
133 This environment variable specifies the list of directories that may
134 contain the configuration file. On *NIX systems, the directories are
135 separated by a colon (`:'), under OS/2, they are separated by a
136 semi-colon (`;'). If this variable is not set, the configuration file
137 is searched in two default directories: first, the current working
138 directory (".") and then in
139 .IR /etc/sane.d .
140 If the value of the
141 environment variable ends with the directory separator character, then
142 the default directories are searched after the explicitly specified
143 directories. For example, setting
144 .B SANE_CONFIG_DIR
145 to "/tmp/config:" would result in directories
146 .IR "tmp/config" ,
147 .IR "." ,
148 and
149 .I "/etc/sane.d"
150 being searched (in this order).
151 .TP
152 .B SANE_DEBUG_MICROTEK
153 If the library was compiled with debugging support enabled, this
154 environment variable controls the debug level for this backend.
155 A value of 128 requests maximally copious debug output; smaller
156 levels reduce verbosity.
157
158 .SH "SEE ALSO"
159 .BR sane (7),
160 .BR sane\-scsi (5),
161 .BR sane\-microtek2 (5)
162
163 .SH AUTHOR
164 Matt Marjanovic
165
166 .SH BUGS
167 Known bugs/limitations are:
168 .PP
169 .RS
170 Brightness and contrast broken.
171 .br
172 The 600GS is grayscale only, and will lock up if you select color.
173 (Unfortunately, the 600GS and 600ZS are indistinguishable by software.)
174 .br
175 .RE
176 .PP
177 i.e. don't complain about these --- but if brightness and/or contrast
178 .B do
179 work for you, please tell me.
180 .PP
181 If your scanner locks up, try setting the
182 .I norealcal
183 or
184 .I noprecal
185 option in the configuration file (first one, then both), and see if it helps.
186 (If it does, report it.)
187 .PP
188 Send lengthy bug reports and new scanner information to
189 .IR mtek\[email protected] .
190 All bug reports and new scanner inquiries should include an error log file.
191 You can generate copious
192 stderr output by setting the
193 .B SANE_DEBUG_MICROTEK
194 environment variable described above. For example:
195 .PP
196 .RS
197 setenv SANE_DEBUG_MICROTEK 128
198 .RE
199 .PP
200 More general comments, suggestions, and inquiries about frontends
201 or SANE should go to
202 .IR sane\[email protected] ,
203 the SANE Developers mailing list. Have a look at
204 .I http://www.sane\-project.org/mailing\-lists.html
205 concerning subscription to sane\-devel.