Epson-WF-2860 multifunction inkjet - scanner not found

[davids45]

G'day,

Running a life-threatened Acer-Aspire E1-531 via a 64GB USB drive with a Frugal Bookworm Pup. The Aspire's hard-drive may be dying (and/or the CPU?) as there is are frequent mini-freezes if the original hard-drive is used as the OS - Bookworm on USB is barely affected and runs very quickly so the Aspire's RAM looks good. The 64GB usb seems to take a long time to load installed programs off the Aspire's hard drive via desktop links, maybe another pointer to the hard-drive.
A few months ago, I ran czkawka on this laptop and the hard-drive result was a likely failure in months, so maybe Niels Bohr was wrong - "Prediction is difficult, particularly about the future."

My Epson printer-scanner is on our local network with a dynamic IP address (not static).

Printing is now works in Bookworm with rcrsn51's EPPI script and a .deb driver package.

The included 'Simple Scanner' app. opens but cannot locate the scanner part of the Epson.

Is there a fix for 'Simple Scanner' to get my networked scanner located, or is there an alternative scanner package (like xsane?)?

Thanks for any advice.

David S.

[mikewalsh]

@davids45 :-

Hallo, David. Long time no see...

Um.....okay. Right. Now; you say you've installed the printer via Eppi and a .deb package, yes?

Silly question, perhaps, but you DO realise that Epsons require a separate scanner driver package, yes? They've always been like this, even on the "all-in-ones".....and not everybody is aware of this.

Go here:-

https://download.ebz.epson.net/dsc/sear ... archModule

.....enter "WF-2860" in the top box, select Linux from the lower drop-down, and click on the wee magnifying glass. You'll want the bottom item; the "Epson Scan 2" scanner driver. Install this via Eppi, too; as I observed here, it's all down to the way the official .deb package's post-install script works (which sets up a whole bunch of sym-links and other stuff). Puppy won't run the post-install script if you install the .deb in the normal way, because it expects the script to have a different name.....so it doesn't 'see' it. Therefore, the sym-links don't get set-up, and thus the scanner won't work.

Eppi runs it correctly, making sure the included Debian post-install script IS run. Ergo, stuff should happen, if everything does what it's supposed to.

If you haven't done the above, please do so.....then try things again.

=======================

As for a scanner application, Epson's own included "Image Scan!" usually works pretty well. Or, you could try this:-

viewtopic.php?p=56636#p56636

.....which I've always found to work without a hitch, even surpassing Epson's own app. See what ya think, anyroad. I know Skanlite is a big one, but it's been built correctly, and whoever put this particular AppImage together really knew what they were doing, 'cos it works flawlessly.

========================

Question:- I assume this is a wireless Epson, yes? Any particular reason why you use a dynamic IP rather than a static one? I'm curious as to how machines on your network are able to find the thing from one session to another.....

Mike.