Perfection V39 Driver

0 views
Skip to first unread message

Otilia Mojarro

unread,
Aug 3, 2024, 6:01:44 PM8/3/24
to terichatog

I have downloaded Epson's iscan-bundle-1.0.0-x64.deb and run sudo ./install.sh. The script runs without errors. However, the device driver does not get installed. As a test I ran Simple Scan and it says to install the device driver. Iscan says it cannot send commands to the scanner.

I have an Epson ME Office 620F. Imagescan is what I have been using so far. But the following steps will help in installing any package that depends on libsane instead of libsane1(included in Ubuntu 17.10)

The drivers depend on libsane. However, in Ubuntu 23.10, the package libsane is missing. A workaround is to download and install the libsane package from another Ubuntu release. In the example below, I am using libsane from Ubuntu 23.04 (Lunar Lobster) for amd64 architecture. You also have to install libsane1 package, because libsane depends on it.

On the german epson support page there is also an update for the driver "EPSON Scan Updater 1.0 13-Jul-2018 0.72MBs". I also installed this afterwards with success.Probably the english version "Scanner Driver and EPSON Scan Utility v3.04A" has this update already included.

2) Install the old drivers under Windows XP as a virtual machine in VMware Workstation Player, which is free for non-commercial purposes.If you have (or find) a working key then the ISO file of Windows XP Pro can be downloaded from here.

I also installed an old registered Windows XP version of VueScan Professional in this VM to scan the images. This works fine and scans faster than the trial version of the most recent VueScan Standard/Pro which supports Windows 10.

Note: Once you have the drivers installed, remember that the scanner should be turned on prior to starting/booting your computer. Otherwise, the computer may fail to recognize the scanner is attached to the computer via USB. Powering on the scanner while the computer is running, while common for many USB devices these days, often will result in a failure to recognize the presence of this scanner in my experience.

It looks like the Epson website now has updated drivers to support Perfection Series through Windows 10.
I have not verified that they are actually there or that they actually work.
If interested, check it out and please post here the results.

Hi AppleTreasures! Unforunately, that does not appear to be the case. There are some miscellaneous utility downloads available for older scanners (for example Epson Event Manager), but not typically drivers for the hardware. Scanners on that list that were released since Windows 10 has been available will tend to have Windows 10 drivers, for example the Epson Perfection V850 Pro.

I have an old Epson Perfection 1300Pro scanner. Do you know if I can use it with my current Mac system, High Sierra OS? If not, can you recommend a scanner for printed photographs as well as transparencies?

Thanks for your detailed information, now I do not have to scrap my scanner. My main use was to scan films and slides on my iMac. I had put the unit aside since it was no longer supported. Going thru the Epson support did not help.

If you manage to get it running again, note I have seen Windows 10 drop the driver (likely after a Windows update). In those cases it still showed the device as listed in Printers and Scanners and the Device Manager, but was marked as not having a driver.

Thank you for pointing me in the right direction. I do however wonder why you suggest installing the scanner as a 4990 though. The download driver file 12180 is specifically listed by Epson for the 2400 which lucky for us apparently uses the same drivers as the 1200. I Installed as a 2400 and my 1200 scanner works perfectly in Windows 10.
Cheers

Yes I had same issue as you and had to do a search in Google for the epson12181.exe since I did not find it on the Epson page. I also selected 32 bit version. I did get things to work years ago with selecting Epson 2400 from Device Manager on my other Windows 8.1 laptop but every few weeks when I went to scan (infrequent use) the driver was gone and I had to reinstall it through Device Manager. Hopefully this will not occur on my Win 10 machine using the 1200 USB scanner and the 4990 driver. I also am not sure why Vance preferred the 4990 driver and if I should have used 64 bit and if the driver will also disappear after a while on Win 10 machine. Time will tell. But not worth me buying Vuescan for 2 machines at $60 each or buying a new scanner since I scan so infrequently.

The same text for a better translation
Thanks for the advice.
I was able to keep my Perfection 1200 for transparent backs.
It worked fine until win 8.updated win 10.
But for win 11, the scanner was well reinstalled but not possible to make the adapter work for transparent backs. This adapter can light up on the scanner, but an error message (Windows has stopped this device because it has problems. (Code 43)) does not allow the adapter to be used.
If there is a solution to this problem, many thanks in advance.

Its my 1st time i write here, i watched a lot of thread about setting windows 7 in new hardware - i gave up and stick to 8.1 that seems pretty good to me
i have an Epson Perfection1640SU scanner since i was in XP , when i move to windows 7 and i found driver solution for them, ( as new member cant write the link )
but unfortunately this trick dindt work on 8.1, i will appreciate any help guys
With respect to the great work that you do here!

* my English not the best/sorry if something looks strange

I am trying to scan my art into Photoshop using an Epson Perfection V600 Photo scanner. I have had the scanner for several years and it works fine just scanning files into the computer. Just recently, I installed photoshop on my Macbook Pro. When I try to scan directly into photoshop I get a message that says "Failed to open connection to the device (-21345). See photo. I did upload the latest driver from Epson. It still says the dame thing. Does anyone know a fix for this? Thank you in advance.

If you're using Windows and you've installed a Epson driver, VueScan's built-in drivers won't conflict with this. If you haven't installed a Windows driver for this scanner, VueScan will automatically install a driver.

According to my cursory analysis (which uses a Poisson distribution and assumes the accuracy of the national crash and mileage estimates), Google's cars would need to drive themselves (by themselves) more than 725,000 representative miles without incident for us to say with 99 percent confidence that they crash less frequently than conventional cars. If we look only at fatal crashes, this minimum skyrockets to 300 million miles. To my knowledge, Google has yet to reach these milestones.

(By the way, can we draw meaningful conclusions about safety from total crash data rather than from injury- and fatal-crash data alone? This issue merits discussion for at least half a million more miles.)

Engineering is about trade-offs: We replace one set of problems with another set of problems and hope that, in the aggregate, our new problems are smaller than our old ones. (Take just one example: Although antilock brake systems without electronic stability control decrease the risk of fatal collision for those outside the vehicle, they may increase that risk for those on the inside.) Careful design therefore requires selection of system boundaries, assessment of risks and opportunities, and analysis of costs and benefits. None of these decisions are value-free; indeed, cost-benefit analyses performed by administrative agencies may even involve explicit assumptions about the value of a human life.

The real benefit to safety would be if all vehicles were computer controlled. I'm willing to bet a large number of accidents are caused by either driver distraction (including falling asleep) or high risk behaviors such as super speeding and dangerous maneuvers.

So, the question I have after this all too long preamble is, how do I go about extracting the deb file from this deb.tar.gz file? I would normally ask the gentleman who made the original posting, unfortunately, the original Manjaro forum has been archived and I have no means to contact him.

I have in fact attempted that, but it does not work. It appears that Epson has updated its drivers since that AUR entry, and consequently, when you attempt to install it, the installation routine fails, claiming the MD5/SH256 checksums do not match. I then downloaded the snapshot from AUR, manually updated the checksums contained within the PKGBUILD script to reflect the correct ones, and ran it locally, but still, I cannot get the scanner to work. I contacted the AUR maintainer and asked if he could correct the issue, but so far have not heard a word back. Interestingly, when I run $lsusb, I see the V600 listed, but none of the scanning software I have tried (VueScan professional, Image Scan! for Linux, etc.) can see the scanner.

I have spent the better part of the last week searching high and low for an answer, and unsuccessfully attempting to implement the ones I have found, and this includes information found in the archived version of the Manjaro Forum and elsewhere. Using a spare SSD, I installed Linux Mint 20 and later Kubuntu, and the Epson drivers for this scanner installed without a hitch on both, after which the scanner was recognized and became fully operational.

I already flagged it and contacted the maintainer a week ago, with zero acknowledgments. In addition, I downloaded the latest Epson rpm package, calculated the checksums, and updated the pkgbuild posted in AUR, and ran the script locally. While it appeared to complete successfully, the various scanning applications I have run in Manjaro fail to recognize the V600 scanner. As I stated, I have tried almost everything under the sun, and so far far nothing works, whereas in other, Debian based distributions (Mint and Kubuntu) there are zero issues. This is extremely frustrating.

After having read your exchanges, the package provided by Epson (imagescan-bundle-debian-10-3.65.0.x64.deb.tar.gz) creates a folder. The README.rst file tells you not to use the .deb package, but to use their installation script: install.sh

c80f0f1006
Reply all
Reply to author
Forward
0 new messages