NAME<\/a> sane\u2212microtek \u2212 SANE backend for Microtek scanners<\/p>\n The sane\u2212microtek<\/b> library implements a SANE (Scanner Access Now Easy) backend that provides access to the “second generation” Microtek scanners. At present, the following hardware is known to work with this backend:<\/p>\n Microtek ScanMaker E2, E3, E6 Transparent Media Adapter The driver supports line art, halftone, 8bpp gray, and 24bpp color scans at normal and “expanded” resolutions (i.e. 1200×1200 on an E6), fast scans for color previews, and downloadable gamma tables.<\/p>\n The supported scanners are all SCSI scanners. However, some parallel port models may work (under Linux), if they use a parport->scsi chip, and if you can find a scsi->parport driver. This is known to be the case for the Color PageWiz.<\/p>\n The driver does not<\/b> support the newest Microtek scanners, such as the V330 and V660, which use a new and very different SCSI-II command set. For those, try the alternate microtek2<\/b>(5) backend. Most non-SCSI scanners would use the new command set. Most scanners newer than the Scanmaker E6 would use the new command set.<\/p>\n If you own a Microtek scanner other than the ones listed above, tell us what happens — see the BUGS<\/b> section at the end of this document.<\/p>\n Although this manual page is generally updated with each release, up-to-date information on new releases and extraneous helpful hints are available from the backend homepage:<\/p>\n http:\/\/www.mir.com\/mtek\/<\/i><\/p>\n This backend expects device names of the form:<\/p>\n special<\/i><\/p>\n Where special<\/i> is the UNIX path-name for the special device that corresponds to the scanner. The special device name must be a generic SCSI device or a symlink to such a device. Under Linux, such a device name could be \/dev\/sga<\/i> or \/dev\/sge<\/i>, for example.<\/p>\n The contents of the microtek.conf<\/i> file is a list of device names that correspond to Microtek scanners. Empty lines and lines starting with a hash mark (#) are ignored. A sample configuration file is shown below:<\/p>\n \/dev\/scanner The configuration file may also contain the special tokens norealcal<\/i> or noprecal. norealcal<\/i> will disable the use of magic, undocumented scanner calibration commands which are known to work on the E6, but may not work with other models. noprecal<\/i> will disable logic which tries to avoid scanner precalibration. This logic would only have been activated if the magic calibration code was turned off.<\/p>\n \/etc\/sane.d\/microtek.conf<\/i><\/p>\n The backend configuration file (see also description of SANE_CONFIG_DIR<\/b> below).<\/p>\n \/usr\/lib64\/sane\/libsane\u2212microtek.a<\/i><\/p>\n The static library implementing this backend.<\/p>\n \/usr\/lib64\/sane\/libsane\u2212microtek.so<\/i><\/p>\n The shared library implementing this backend (present on systems that support dynamic loading).<\/p>\n SANE_CONFIG_DIR<\/b><\/p>\n This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (\u2018:\u2019), under OS\/2, they are separated by a semi-colon (\u2018;\u2019). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (“.”) and then in \/etc\/sane.d<\/i>. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR<\/b> to “\/tmp\/config:” would result in directories tmp\/config<\/i>, .<\/i>, and \/etc\/sane.d<\/i> being searched (in this order).<\/p>\n SANE_DEBUG_MICROTEK<\/b><\/p>\n If the library was compiled with debugging support enabled, this environment variable controls the debug level for this backend. A value of 128 requests maximally copious debug output; smaller levels reduce verbosity.<\/p>\n sane<\/b>(7), sane\u2212scsi<\/b>(5), sane\u2212microtek2<\/b>(5)<\/p>\n Matt Marjanovic<\/p>\n Known bugs\/limitations are:<\/p>\n Brightness and contrast broken. i.e. don\u2019t complain about these — but if brightness and\/or contrast do<\/b> work for you, please tell me.<\/p>\n If your scanner locks up, try setting the norealcal<\/i> or noprecal<\/i> option in the configuration file (first one, then both), and see if it helps. (If it does, report it.)<\/p>\n Send lengthy bug reports and new scanner information to mtek\u2212bugs@mir.com<\/i>. All bug reports and new scanner inquiries should include an error log file. You can generate copious stderr output by setting the SANE_DEBUG_MICROTEK<\/b> environment variable described above. For example:<\/p>\n setenv SANE_DEBUG_MICROTEK 128<\/p>\n More general comments, suggestions, and inquiries about frontends or SANE should go to sane\u2212devel@alioth-lists.debian.net<\/i>, the SANE Developers mailing list. Have a look at http:\/\/www.sane\u2212project.org\/mailing\u2212lists.html<\/i> concerning subscription to sane\u2212devel.<\/p>\n sane\u2212microtek \u2212 SANE backend for Microtek scanners <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[959],"tags":[961,1291,1641],"class_list":["post-4718","post","type-post","status-publish","format-standard","hentry","category-5-formatos-de-ficheros","tag-961","tag-man5","tag-sane-microtek"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4718","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=4718"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4718\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=4718"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=4718"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=4718"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
DESCRIPTION<\/a>
DEVICE NAMES<\/a>
CONFIGURATION<\/a>
FILES<\/a>
ENVIRONMENT<\/a>
SEE ALSO<\/a>
AUTHOR<\/a>
BUGS<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
Microtek ScanMaker II, IIG, IIHR, IISP, III
Microtek ScanMaker 35t, 35t+, 45t
Microtek ScanMaker 600GS, 600ZS (see bug notes)
Agfa StudioScan
Agfa StudioScan II, StudioScan IIsi
Agfa Arcus II (but not the “Arcus”)
Agfa DuoScan (preliminary)
Vobis “Highscreen Realscan”
Microtek Color PageWiz (preliminary)<\/p>\n
Document AutoFeeder<\/p>\nDEVICE NAMES <\/a> <\/h2>\n
CONFIGURATION <\/a> <\/h2>\n
# this is a comment
\/dev\/sge<\/p>\nFILES <\/a> <\/h2>\n
ENVIRONMENT <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n
AUTHOR <\/a> <\/h2>\n
BUGS <\/a> <\/h2>\n
The 600GS is grayscale only, and will lock up if you select color. (Unfortunately, the 600GS and 600ZS are indistinguishable by software.)<\/p>\n
\n","protected":false},"excerpt":{"rendered":"