Unix/Linux Go Back    

RedHat 9 (Linux i386) - man page for sane-snapscan (redhat section 5)

Linux & Unix Commands - Search Man Pages
Man Page or Keyword Search:   man
Select Man Page Set:       apropos Keyword Search (sections above)

sane-snapscan(5)								 sane-snapscan(5)

       sane-snapscan - SANE backend for AGFA SnapScan flatbed scanners

       The  sane-snapscan  library  implements a SANE (Scanner Access Now Easy) backend that pro-
       vides access to AGFA SnapScan flatbed scanners. At present,  the  following  scanners  are
       supported  from	this  backend: AGFA SnapScan 300, 310, 600, and 1236s, 1236u, 1212u, e20,
       e25, e40, e50, e60, Vuego 310s, Acer 300f, 310s, 610s, 610plus, Prisa  620s,  Prisa  620u,
       Prisa  620ut,  Prisa 640u, Prisa 640bu, Prisa 1240, Prisa 3300, Prisa 4300, Prisa 5300 and
       Guillemot Maxi Scan A4 Deluxe (SCSI) (with varying success).

       This backend expects device names of the form:


       Where special is the path-name for the special device that corresponds to a SCSI  scanner.
       For  SCSI  scanners, 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 or /dev/sge,  for  exam-
       ple.  See sane-scsi(5) for details.

       For  USB  scanners the devicename must contain the keyword "usb", as in /dev/usbscanner or
       /dev/usb/scanner0.  For scanners that need a firmware upload before scanning  add  a  line
       starting with "firmware" followed by the fully qualified path to your firmware file, e.g.

	      firmware /path/to/my/firmware.bin

       For further details read http://snapscan.sourceforge.net.

       The  contents of the snapscan.conf file is a list of device names that correspond to Snap-
       Scan scanners.  Empty lines and lines starting with a hash  mark  (#)  are  ignored.   See
       sane-scsi(5) on details of what constitutes a valid device name.

	      The backend configuration file (see also description of SANE_CONFIG_DIR below).

	      The static library implementing this backend.

	      The  shared  library  implementing  this	backend  (present on systems that support
	      dynamic loading).

	      This environment variable specifies the list of directories that	may  contain  the
	      configuration  file.   Under  UNIX, the directories are separated by a colon (`:'),
	      under OS/2, they are separated by a semi-colon (`;').  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.	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  to  "/tmp/config:"  would result in directories "tmp/config", ".",
	      and "/etc/sane.d" being searched (in this order).

	      If the library was compiled with debug support enabled, this  environment  variable
	      controls the debug level for this backend.  E.g., a value of 255 requests all debug
	      output to be printed.  Smaller levels reduce verbosity.

       Man page doesn't provide much information yet.

       sane(7), sane-scsi(5)
       http://sourceforge.net/projects/snapscan/ (new development website)

       Kevin Charter, Franck Schneider, Michel Roelofs, Emmanuel Blot,	Mikko  Tyolajarvi,  David
       Mosberger-Tang, Wolfgang Goeller, Petter Reinholdtsen, Gary Plewa, Sebastien Sable, Oliver
       Schwartz and Mikael Magnusson.
       Man page by Henning Meier-Geinitz (mostly based on the web pages and source code).

					   26 May 2001				 sane-snapscan(5)
Unix & Linux Commands & Man Pages : ©2000 - 2018 Unix and Linux Forums

All times are GMT -4. The time now is 05:20 AM.