Hello all! I'd like some advice on whether this scanner is usable under
Linux.
My sister brought the Heidelberg AG Linoscan 1200 back when her work
chucked it out, and I thought I'd try and get it running under Linux
(Ubuntu 7.10). It connects via USB, and lsusb gives:
Bus 001 Device 002: ID 0
On 1/2/08, Nick Urbanik wrote:
> Dear Folks,
>
> I am having problems setting up saned on Fedora 8:
> $ grep sane /var/log/rpmpkgs
> libsane-hpaio-2.7.7-6.fc8.i386.rpm
> sane-backends-1.0.18-17.fc8.i386.rpm
> sane-backends-devel-1.0.18-17.fc8.i386.rpm
> sane-backends-libs-1.0.18-17.fc8.i386.rpm
>
On 1/10/08, jazz_johnson at verizon.net wrote:
> I decided to do some testing on the avision backend with the Fujitsu SP15C.
>
> The first major difference I've noticed, is that the avision backend
> monopolizes the scanner so that only one program can use the scanner while
> that program is runn
if you can put a small pnm up on the web somewhere demonstrating the
problem you might get more help, but it sounds like a calibration
issue, which can be fairly specific to the chip involved, and without
docs can be difficult to get right.
allan
On 1/9/08, Philip Aston wrote:
> Listed as minima
if you put these usb ids into our search engine at:
http://www.sane-project.org/cgi-bin/driver.pl
you will see that canon has recently released a closed-source driver
for this scanner, but it is untested.
If you would rather an open-source driver, you might have to 'scratch
your own itch' by writ
easiest thing to do is to open the scanner and get logos and numbers
off the larger chips. second easiest is to take a trace under windows
using benoit's usbsnoop, put it on the web, and post a link on this
list. if you are lucky, someone here might recognize the protocol.
allan
On 1/10/08, Ben F
===
== Neuer Eintrag
===
---
-- Formular: 'adddev'
---
1. Your email address:
'slashbeast at jid.pl'
2. Manufacturer (e.g. "M
I decided to do some testing on the avision backend with the Fujitsu SP15C.
The first major difference I've noticed, is that the avision backend
monopolizes the scanner so that only one program can use the scanner while
that program is running, i.e. the first user who runs xsane will see the
a
