Epson V200 SOLVED -
THE SHORT ANSWER
The two available iscan SlackBuilds will not get the job done for an Epson V200 on a 2.6.x system.
You must use the Epson Avasys Iscan Utility WITH the Epson Avasys Iscan plugin for the V200 (GT-F670 model plugin which is the Non-US version of the V200).
SlackBuild.org has a script for the Iscan Utility but nothing for the complete plugin.
Here is my SlackBuild (it's slackbuild.README explains the plugin): iscan+plugin_2.25.0-1.tgz
EDIT: Buildscript updated Sept 11 2010 for Iscan v2.25-1
NOTE: parts of this post have become obsolete!!
If you want the details keep reading.
THE LONG ANSWER
PITFALLS OF A NOOB
I made some bad assumptions, some bad choices, and even hosed my OS at one point, but I finally got the V200 working.
So, Epson Avasys makes available four files to download regarding the V200 scanner; 2 RPM's, Source Code, User Guide:
iscan.SlackBuild compiles from the source code and says:
"Image Scan! for Linux" is a scanner utility that makes
it easy to obtain high quality images on Linux with your
EPSON scanner or all-in-one.
Cool, so this is all I need right? (Mistake number one. I should have read the source code README)
Installing the package from that build resulted in no scanner operation.
So, I must need the iscan-firmware.SlackBuild right? (I must have taken a stupid pill that morning)
The iscan-firmware.SlackBuild tells me that my scanner will work with the FOSS Snapscan backend that comes with Sane; all I need is the firmware for my scanner. It even lists specific instruction to configure Snapscan for the V200 scanner. Great, open source is a beautiful thang, lets just use that.
The iscan-firmware.SlackBuild just repacks an OpenSUSE Package which contains Epson Avasys iscan plugins for all of the available scanner models. I only need one so I'll just drop the firmware into the proper directory, tell Snapscan to use it, all done right?
Trying to make the Snapscan backend work with my V200 is where I really started getting my butt kicked. Essentially, Sane was telling me it did not recognize the scanners USB chip. I was running down one dark alley and dead end after another. Finally I decide, maybe this scanner is just broken. So I hook it up to a friends Vista box and it runs like a pickle seeder.
So, maybe this Snapscan backend just won't work. I go the Snapscan site and the last update listed is 11/27/05. Hummm.
Then I find this tidbit on the Snapscan site:
You can also upload the firmware to your scanner manually.
You need to launch one of agfafirm or acerfirm perl scripts:
acerfirm /dev/usbscanner u34v101.bin
Note: acerfirm and agfafirm will only work if you use the
scanner module to access your USB scanner. It does not work
Perhaps this is why Snapscan would not work with my 2.6.x
kernel as there is no scanner module for it. 2.6.x kernels
only use libusb. The Snapscan site does not elaborate as to
whether their backend also requires the module to upload the
firmware. I didn't bother looking at the code so this is all just speculation on my part. All I can say for sure is the Snapscan backend for Sane would not work for the V200 on my system.
The Sane backend database also does NOT list the V200 for use with the Snapscan backend. For the V200 it lists only iscan and it's required plugin.
Drop back and punt. I explode the Avasys and OpenSUSE packages to see what goes where and compare it to my install.
Everything looks good, except for one little problem. The OpenSUSE package used by the iscan-firmware.SlackBuild only has half of the plugin. What!?! Yup, OpenSUSE gathers all of the Epson Avasys plugins for the different model scanners and SPLITS THEM INTO TWO SEPARATE PACKAGES:
To put an end to this long sad story. As far as I can tell the Snapscan backend will not work with V200 Scanner (at least with a 2.6 kernel). Thus the iscan-firmware.SlackBuild is of no use for the V200.
You must use the Epson Avasys Iscan Utility with the GT-F670 iscan plugin.
Technically, you don't need all of the Iscan package. You need the epkowa Sane backend from the Iscan package and the plugin (both are binary only). But the Iscan package has a nice frontend and I would recommend it. Besides, the frontend is open source anyway.
You could use the iscan.SlackBuild but there is nothing available to make a slackpackage for the complete GT-F670 iscan plugin. So, that really doesn't help.
Using rpm2tgz on the Epson Avasys Packages doesn't get the job done. It's close, but there are some rpm scripts that do not get run, so it still needs some manual labor. Mostly udev rules and gimp plug. If you know how to write udev rules and make links you can go that route if you'd like.
I ended up writing a new SlackBuild that will repack iscan and the plugin RPM's into one Slackpackage. It should repack as many plugins as you include (but that is untested). It generates an iscan udev rules file and The Gimp plugin.
There is a link to my SlackBuild at the top of this post.
In my n00b opinion, template.SlackBuild at Line 63 needs:
-o -perm 700
When repacking RPM's cpio seems to use 0700 a lot and it will really foobar a persons system if it is missed. Yeah, like I said I'm a n00b. It really pisses off X when you tell it not to play in /etc or /usr. X has no sense of humor at all. CLI just gets stupid. You can login (as a user) but that's about it. It was a great learning experience at least.
You're welcome to use my SlackBuild if you think it's worthy of SlackBuild.org