Sponsored Content
Full Discussion: Epson Scanner
Special Forums Hardware Epson Scanner Post 302992529 by 1in10 on Monday 27th of February 2017 05:14:19 AM
Old 02-27-2017
May I just add this. It was my first adventure with just the same OEM to install the scanner, by the way one of the real hurdles for Linux or Unix. Look for the vendor ID, this is the crucial point, because it comes along the reverse way.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Epson Driver

hi i'm new here and my first problem ( and not the last) that i acquired a network laser printer epson epl 6200n and i can't print on it with unix sco5. is there a driver that allow this? thanx (1 Reply)
Discussion started by: zapping
1 Replies

2. AIX

Epson lq2080 Aix 4.3.3

I'm trying to set up a print queue that connects to an Epson printer via a jetdirect. There are no Epson printer drivers so I set it up as "other". The problem is nothing will print to the printer. It goes in and out of the AIX queue. When you do an lpstat is looks like it's printing... (3 Replies)
Discussion started by: seanaix43
3 Replies

3. UNIX for Dummies Questions & Answers

epson driver

:confused: I want to install epson LQ1150 printer on a unix system ,epson doesnt have a unixdriver provided with it,which comptible driver would support the printer with unix (0 Replies)
Discussion started by: athais
0 Replies

4. HP-UX

HP-UNIX, EPSON FX80+ and TVS 250 Champion

Does anyone knows if HP-UNIX supports Epson FX80+ and TVS 250 Champion? These are all dot matrix printers. I have been trying to look for the driver but no avail. Thanks (1 Reply)
Discussion started by: wyattwang
1 Replies

5. Solaris

Epson ESC/P2 on solaris prints LD

I am hoping someone can help me with this little riddle. I have an oldish Epson ESC/P2 which I connected to a solaris10 box, with 2 queues, 1 with the solaris print filter so I can print from Solaris (works fine), and a second raw queue so that windows machines can print to it. The raw queue... (0 Replies)
Discussion started by: gdommett
0 Replies

6. Shell Programming and Scripting

Need some help with shell content scanner

Just started to create my own small content scanner that searches all the visible files on my server, but now I got stuck. It should be used to scan the files for phrases like in the following example. What I tried is the following code: #!/bin/bash find /home/userid*/public_html/ -size... (18 Replies)
Discussion started by: medic
18 Replies

7. Linux

micro film scanner

epson microfilm 500 scsi: Is there any way to make this work under linux ? I'm using pclinuxos, it shows the machine in the device panel as sg2 and lists the machine , so Im guessing the kernel knows what it is, but I can't view it as a scanner or capture or input device . What catagory does... (4 Replies)
Discussion started by: tom1200
4 Replies

8. Red Hat

IP Scanner tool

Hey guys.. What is the best tool that can be used on Linux for IP scanning tool that can bring ping status, hostname, and any other open service. I wish I can find a tool like "The Dude" from Mikrotik, but that works only under Windows. Thanks (4 Replies)
Discussion started by: leo_ultra_leo
4 Replies

9. Ubuntu

Can Scanner be Initialized from the Terminal

Hi, somewhat of a newbie with Linux, although I have been at it for about three weeks now. Is there a way to wake up or initialize my scanner with a command in the terminal? (6 Replies)
Discussion started by: klrman
6 Replies
sane-avision(5) 					   SANE Scanner Access Now Easy 					   sane-avision(5)

NAME
sane-avision - SANE backend for original Avision and Avision OEM scanners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed and film scanners. ABOUT THIS FILE
This file is a short descripton for the avision-backend shipped with SANE. DESCRIPTION
The sane-avision library implements a SANE (Scanner Access Now Easy) backend that provides access to various Avision scanners and the Avi- sion OEM scanners labelled by HP, Minolta, Mitsubishi or Fujitsu. It is fully big-endian aware and in every-day use on PowerPC and SPARC systems. I suggest you hold one hand on the power-button of the scanner while you try the first scans - especially with film-scanners! CONFIGURATION
The configuration file for this backend resides in /etc/sane.d/avision.conf. Its contents is a list of device names that correspond to Avision and Avision compatible scanners and backend-options. Empty lines and lines starting with a hash mark (#) are ignored. A sample configuration file is shown below: # this is a comment option force-a4 option force-a3 option disable-gamma-table option disable-calibration #scsi Vendor Model Type Bus Channel ID LUN scsi AVISION scsi HP scsi /dev/scanner usb 0x03f0 0x0701 force-a4: Forces the backend to overwrite the scanable area returned by the scanner to ISO A4. Scanner that are known to return bogus data are marked in the backend so if you need this option please report this to the backend maintainer. USE WITH CARE! force-a3: Forces the backend to overwrite the scanable area returned by the scanner to ISO A3. Scanner that are known to return bogus data are marked in the backend so if you need this option please report this to the backend maintainer. USE WITH CARE! disable-gamma-table: Disables the usage of the scanner's gamma-table. You might try this if your scans hang or only produces random garbage. disable-calibration: Disables the scanner's color calibration. You might try this if your scans hang or only produces random garbage. Note: Any option above modifies the default code-flow for your scanner. The options should only be used when you encounter problems with the default be- haviour of the backend. Please report the need of options to the backend-author so the backend can be fixed as soon as possible. DEVICE NAMES
This backend expects device names of the form: scsi scsi-spec usb usb-spec Where scsi-spec is the path-name to a special device or a device ID for the device that corresponds to a SCSI scanner. The special device name must be a generic SCSI device or a symlink to such a device, for example on Linux "/dev/sga" or "/dev/sg0". The device ID is the ID returned by the scanner, for example "HP" or "AVISION". See sane-scsi(5) for details. Note: Since the backend now includes native USB access, it is no longer needed - even considered obsolete - to access USB scanner via the SCSI emulation (named hpusbscsi on Linux) for Avision USB devices such as the HP 53xx, HP 74xx or Minolta film-scanners. usb-spec is the USB device name, the vendor/product ID pair or the name used by libusb corresponding to the USB scanner. For example "0x03f0 0x0701" or "libusb:002:003". See sane-usb(5) for details. The program sane-find-scanner helps to find out the correct scsi or usb device name. A list with supported devices is built into the avision backend so normally specifying an ID should not be necessary. FILES
/etc/sane.d/avision.conf The backend configuration file (see also description of SANE_CONFIG_DIR below). /usr/lib64/sane/libsane-avision.a The static library implementing this backend. /usr/lib64/sane/libsane-avision.so The shared library implementing this backend (present on systems that support dynamic loading). ENVIRONMENT
SANE_CONFIG_DIR 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 configura- tion 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 explic- itly 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). SANE_DEBUG_AVISION If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. Higher debug levels increase the verbosity of the output. The debug level 7 is the author's prefered value to debug backend problems. Example: export SANE_DEBUG_AVISION=7 SEE ALSO
sane(7), sane-scsi(5), sane-usb(5) http://www.exactcode.de/oss/avision/ AUTHOR
Rene Rebe and Meino Christian Cramer 11 Jul 2008 sane-avision(5)
All times are GMT -4. The time now is 10:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy