>> Sorry, I was confused by the private message system! Your PM to me (thank you for it) appeared to come from 'John'. Looking at it again, I see now that they all come from John Murga's id!

Quote:

Yes, I am using the epkowa-2.26.0.pet. I tried editing /etc/sane.d/epkowa.conf as you suggest. (I also edited /etc/sane.d/dll.conf and added "epkowa" at the end of the file, as advised up-thread.)

I'm confused. If you are actually using the epkowa-2.26.0.pet, it would have automatically updated the dll.conf file. Are you sure you got the right package?

>> Yes, it was 2.26.0. I noticed afterwards that it updates dll.conf and that my own edit wasn't needed.

Quote:

With the change to epkowa.conf, xsane no longer reports 'no scanners found' but unfortunately it crashes after about 20 seconds.

I will post a new package.

Thank you for doing this so quickly. I have installed 2.26.2 but sadly it produces the same result. At the first time of trying, xsane reported 'no devices found'. Then I spotted that the entry for 0x0142 was missing from epkowa.conf so I added that; now I get the same result as with 2.26.0, namely that xsane closes after 20 secs, and iscan hangs. (Puppy Package Manager does confirm that iscan_epkowa-2.26.2 is installed!) Would you mind taking another look at it, please?Last edited by simes on Mon 28 Mar 2011, 07:06; edited 2 times in total

Unfortunately, there is nothing else I can do. This package is built from the official Epson sources recommended for your model. It runs correctly on my Workforce 320 printer/scanner, so I know that the driver is basically good.

[Edit] See below for the fix.

As a general rule, xsane will run even if the file /etc/sane.d/epkowa.conf is missing because it detects the scanner other ways. If you need to add your unit to epkowa.conf, that suggests that the driver really isn't designed for your V330, in spite of what Epson says.Last edited by rcrsn51 on Mon 28 Mar 2011, 18:50; edited 2 times in total

Thanks for the reply. Maybe there is something strange about my Lucid installation. I will build a virgin 5.2 system and try installing the software there. I know the hardware works (from testing on W*nd*ws).

Edit: Tested your 2.26.2 package on an unmodified Lucid 5.2 system with the same results. It's starting to look as if the Epson driver is faulty, as you suggest. Oh, b*gg*r! Back to booting my emergency W*nd*ws system for this one.

Thanks for the idea - I have a (rarely used) Ubuntu 10.04 install so have tried installing there. After several attempts this worked. I had to install SANE 1.0.14 (I stupidly assumed at first that SANE was a pre-req to XSANE, but it isn't), and the Epson driver installation requires that SANE is installed before the driver without explicitly making it a dependency. Then I got similar errors to my Lucid Puppy install - couldn't communicate with scanner, etc. I then realised that the third file on the Epson drivers page (esci-interpreter-perfection-v330_0.0.1-1_i386.deb) is a plug-in specifically for this printer. With the plug-in installed, ImageScan talks to the printer, but not without. Would you advise trying to install the plug-in on Lucid Puppy?

EDIT: Just seen your Update! We have been working on this in parallel, I think. Thanks for your help. Will try the plug-in on Puppy.

2nd EDIT: Tested the esci-interpreter-... PET on Lucid Puppy 5.2 and it works, thank you. The V330 now works on ISCAN and also on XSANE (though startup on both is very slow - as it is on Ubuntu). And ISCAN can be started as a plug-in from GIMP. Many thanks to rcrsn51.

One footnote however for anyone else who is considering this scanner. The Linux drivers (or possibly the Linux interface apps) are lower function than the W*nd*ws ones, much as I hate to say this. In particular the clever manipulation of transparencies and negatives that can be done in the Epson W*nd*ws app (e.g. scan a strip of 6 negatives, separate them into 6 images automatically, adjust the contrast and brightness of each individually during the scan) isn't available. The W*nd*ws drivers don't work under WINE, unsurprisingly, so some functions are just going to mean booting that emergency W*nd*ws system.

That's good news! I should have trusted Epson to have a working driver.

Quote:

The Linux drivers (or possibly the Linux interface apps) are lower function than the W*nd*ws ones,

Unfortunately, that's true with many printer/scanner units. But it's a far cry from a few years ago when it was a real crap-shoot to find a printer supported by Puppy. Now you can go into any computer store and find lots of models that will give you at least basic functionality.

BTW, here's a trick for making your scanner start faster. Open the file /etc/sane.d/dll.conf and delete all the entries except for your model.

I first edited the /etc/sane.d/dll.cong file and uncommented the "epson" entry. (Note: I am running Wary 5.)
I then installed epkowa-2.26.0.pet which is supposed to work well in Peasyscan.
It kind of works in Peasyscan. It will scan the image, but the images do not save to the file I specify, and when I close file manager and go back to take another look at the image, it's gone! It didn't save to the specified location. It did--at first try--save to /root/. I closed file manager and took another look at /root/ for the image and it had also disappeared!
I then tried Xsane, and it works for me beautifully. Scans the image, saves to the specified location and prints it out too (through mtPaint image editor but not through Viewnior image viewer).
Thank you so much for the person who wrote this file (epkowa-2.26.0.pet). I really appreciate having an all-in-one that does all it's supposed to. As yet I don't know if 'Print Photo' or 'Index Sheet' works since I don't yet have an SD card to test with.
Maybe I got the instructions backwards? Anyhow, it's scanning and I'm happy. Thank you.

If you go back to the Avasys site, you will see the second scanner package named iscan-2.26.3-1_i386.deb. If you install it, you can run your scanner using Epson's Iscan program.

Quote:

/root/.

If you are using a "dot" in the filename, you are declaring it to be a hidden file. Maybe that's why you can't find it. Just type a name like "scan.png" in the file box without specifying a path, and see what happens. The file should be saved to /root by default.

Against Xsane Iscan seems to work also more than one scan with the usblp and the usb-storage module loaded . On Xsane I got an IOerror the second scan and the dmesg commad told Xsane wanted to use the port but it had been claimed by usblp and after `rmmod usblp` the same happened with 'usb-storage' . After I rmmoded that kernel module also , Xsane could work several scans in a row .

Iscan is more simple , but offers me
+ a much larger amounts of dpi to choose from .

Disadvantages are
- 'Xdialog -filesect' , that does not offer to create diirectories .
- it seems not to have a gray scan possibility
- it has no picture GUI to work with the scanned image after the real scan had been done .

It really needs the epkowa entry in the dll.conf file with the entry
usb 0x04b8 0x0851

That's true with all the Epsons I have tested, despite what the epkowa.conf file says. The epkowa-2.26.4.pet posted above contains an epkowa.conf with the full set of vendor/product IDs.

Quote:

Against Xsane Iscan seems to work also more than one scan with the usblp and the usb-storage module loaded . On Xsane I got an IOerror the second scan and the dmesg commad told Xsane wanted to use the port but it had been claimed by usblp and after `rmmod usblp` the same happened with 'usb-storage' . After I rmmoded that kernel module also , Xsane could work several scans in a row .

I have tested iscan/xsane/epkowa with numerous Puppies, including Macpup-525 and cannot duplicate this problem. I suspect that it has something to do with USB handling in Macpup Foxy. Be aware that some units need to be rebooted when switching between scanning and printing mode.

You are right I guess , because I think so , too .
Kernel is 2.6.30.5-01SEPT09-TICKLESS-SMP .

On one installation after adding many many pkgs for compiling , xsane does not work with the sanner : does not detect it at all . This made me trying to compile newer sane and xsane , which succeeded more or less . At the end it did not work also - I suspect libusb somehow , which I may once have recompiled or installed again from debian , perhaps because of the dev-pkg .
I also tried to compile the gimp-plugin for xsane , because Mpup_F3 has got gimp-2.6.3 pre-installed and the xsane from debian also comes without the gimp-plug-in , as far as I can see , but i did not succeed with that either . Compiling gimp additionally turned out to be a huge task .

rcrsn51 , your both dotPETS do work on Macpup_F3 frugal also , after I installed libieee1284 : http://packages.debian.org/lenny/libieee1284-3 .

As far as I can see , the Iscan-User-Interface-GUI and its tools had not changed (much?) .

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum