On 05/27/2015 04:38 AM, Rick Moen wrote:
Quoting Andrew Greig ([email protected]):
Thanks for that tip. The dll.conf file had everything commented
out, so all I had to do was lose the hash in front of the epson2
entry.
Yeah, that would do it. ;->
Glad you got to the bottom of that, though one wonders _what_ disabled
all SANE back-ends.
By the way I downloaded a trial version of Vuescan, a proprietary
scanning front end which runs on Linux. It must be small as it took
around 20 seconds to download, and the whole thing was self
contained. I stuck it in my Downloads folder. Last night, before I
had done the dll.conf thing, running of the binary, it found the
scanner and was ready to go with a very slick, clean interface in
seconds. Scan quality was very good but trial scans are heavily
watermarked, and issue the invitation to buy the full versions. A
very nice piece of work.
Yes, Vuescan has an excellent reputation, and I've often recommended it
for users of scanners unsupported (or poorly supported) by SANE. As
with other categories of proprietary drivers, Vuescan has the advantage
that its maintainer (Hamrick Software) can sign NDAs to get access to
secret manufacturer-confidential chipset information, instead of needing
to reverse-engineer that information or glean it from public
information, as open source coders are obliged to do. So, inherently,
they have an information advantage in coding for the problem cases.
Additionally, they have a financial incentive to develop support even
for obscure hardware that open source coders would try _not_ to own and
have no compelling personal interest in supporting.
Personally, on the rare occasions when I end up with hardware with
really poor or nonexistent open source driver support, I interpret that
as an indicator of undesirable hardware, sell it, and get something
better. Your Mileage May Differ.[tm]
I really appreciate this conversation, as it answers a question which I
planned to ask. So for the sake of completeness, here was my unasked
question. Which I preface with this comment that up until OpenSuse 13.2
every Linux system I have loaded has "just worked" out of the box with
the GT7000S. I was told that this was because SCSI and Linux fit like
hand in glove.
My question was how can a proprietary product, completely stand-alone in
my ~/ , load in seconds, and discover the SCSI card in seconds, and be
ready to work? Xsane, when installed into a running machine has always
needed a reboot to start working. In fact if I cancel a scan (I have
learned not to do this) Xsane will not even find the scanner until I
reboot. This provokes another question, how do I avoid the reboot to get
a SCSI scanner working again? Is there such a thing as stopping and
starting a SCSI process?
Thanks again
Andrew Greig
_______________________________________________
luv-main mailing list
[email protected]
http://lists.luv.asn.au/listinfo/luv-main
