Epson Perfection 3170 with VueScan 7.6.78

  • Thread starter Thread starter Pierre
  • Start date Start date
P

Pierre

Hello,

I just installed the new release of VueScan 7.6.78 so that I can use
it with my also new Epson 3170 scanner. Unfortunatly, when the scanner
is ON, VueScan hangs when I start it. If the Epson 3170 scanner is
OFF, VueScan starts OK, and detects my other scanner a Canon Lide 30.

What am I doing wrong ??

I have Windows 2000 SP3.

Thanks,
Pierre
 
Try disconnecting the Canon. Sometimes multiple twain apps fight with each
other. Delete the vuescan.ini file in the vuescan folder first though.
That is standard procedure to reset vuescan.
 
I disconnected the Canon, deleted the vuescan.ini file, and now after
waiting about 1 minute after I started Vuescan, I could see that the
Epson 3170 was detected. Good.

But now, if I try anything like preview or calibrate in Vuescan, I
just get the "busy x%" forever... Nothing else happens.

Any other suggestions ?

Thanks,
Pierre
 
Hi

I have got exactly the same problem. Vuescan starts up (very slowly, the
banner takes 5 min to give way to the main program) and then it simulates
being busy but the scanner remains completely silent.

What could be wrong?

Henk
 
Same problem here. I finally got the program to start even though it
takes ages, but then the busy sign is on when I press either the
preview or the scan button. I left it like that when we went out to
lunch and when I got back 3 hours later still nothing. I have also
tried Silverfast and it works and I think I will purchase it because
Vuescan is not working with the 3170.

S
 
Henk said:
I have got exactly the same problem. Vuescan starts up (very slowly, the
banner takes 5 min to give way to the main program) and then it simulates
being busy but the scanner remains completely silent.

The problem with reporting problems here is that I usually
don't get enough information to figure out what the problem
is. It's possible that the problem only occurs on Mac OS X 10.?,
or maybe it only happens on Windows 2000, etc. That's why
if someone really wants a problem solved, they need to report
it with all the supporting configuration information at:

http://www.hamrick.com/sup.html

Regards,
Ed Hamrick
 
Ed Hamrick said:
The problem with reporting problems here is that I usually
don't get enough information to figure out what the problem
is. It's possible that the problem only occurs on Mac OS X 10.?,
or maybe it only happens on Windows 2000, etc. That's why
if someone really wants a problem solved, they need to report
it with all the supporting configuration information at:

http://www.hamrick.com/sup.html

Regards,
Ed Hamrick

In my case I am using Windows XP Home Edition and the latest version
of Vuescan. The program locks on start-up and sometimes only
sometimes, recognizes the 3170 Epson scanner. When it does open, it
never actually scans anything it just says busy all the time. Computer
is P4 at 2.6Ghz with 512 ram. And sorry Ed. I would love to go through
all the steps in your web page if 1.- I had the time 2.- I thought I
should do it for a software I am trying out to consider puerchase and
it does not work.

S
 
I disconnected the Canon, deleted the vuescan.ini file, and now after
waiting about 1 minute after I started Vuescan, I could see that the
Epson 3170 was detected. Good.

But now, if I try anything like preview or calibrate in Vuescan, I
just get the "busy x%" forever... Nothing else happens.

Any other suggestions ?

Thanks,
Pierre

Hi Pierre!

Well, I had the same problem with Vuescan and my Epson 3170!

The solution is simple: Vuescan needs a command translation library
(esint32.dll) because this Epson scanner doesn't speak native
ESC/I-language (most Epson scanners do this, I think). This .dll can be
found in the location where you have installed the original Epson driver.

Unfortunately Ed Hamrick made the "mistake" to look for this dll in a
hardcoded place which defaults to an english Windows version, namely
"C:\Program Files\EPSON\ESCNDV\esint32.dll". My Windows XP is german, it
isn't installed on drive C:\, in the scope of Vuescan I'm lost.

@Ed Hamrick:
Please recode Vuescan, so that it can find the "Program Files"-Folder for
any version and installation location. There are appropriate registry
keys, where these informations are stored. The Epson 3170 is detected
without the esint32.dll, but it takes some minutes. Vuescan should
complain if it can't find the esint32.dll when a scanner is detected which
needs this library. Why not also search for this library in Vuescan's
folder?

Hope this helps...

BTW, I checked Vuescan 7.6.78 and 7.6.79.


\relax\bye % Viktor 8-)
 
Hi Viktor !

You are right !

Windows 2000 is installed on the E: drive on my computer while Windows
98 is on the C: drive (I don't use it anymore). I just copied the
whole E:/program files/Epson to C:/program files/ and now VueScan
works !

Thanks a lot,
Pierre
 
Viktor,

Great job. My problem is gone as well. Thanks a lot. How did you find out?
To me it seems not that easy.

Henk
 
Viktor,

Great job. My problem is gone as well. Thanks a lot. How did you find
out?
To me it seems not that easy.

Henk

Henk,

I remembered a posting of Ed where he wrote something about the Epson 3170
not using the standard ESC/I-protocol, normally used by Epson scanners.
The Epson driver has some kind of protocol conversion module which he
thought could be used by him to make the 3170 understand Vuescan or vice
versa.

I was a bit disappointed that Vuescan didn't work, it's kind of a
challange. After more than 20 years of more or less intense contact to
computers, I simply have a feeling what could help me in my/our situation.
I grabbed my favourite editor, loaded vuescan.exe and did a search for the
string "EPSON" ... easy!

That's what makes playing around with computers so funny...

But, it's still Ed's "mistake" to hardcode the needed protocol conversion
module.


\relax\bye % Viktor 8-)
 
That's what makes playing around with computers so funny...

But, it's still Ed's "mistake" to hardcode the needed protocol conversion
module.

Does this mean that Vuescan does NOT work with MacOSX and Linux and the
Epson 3170?
 
Viktor said:
Unfortunately Ed Hamrick made the "mistake" to look for this dll in a
hardcoded place which defaults to an english Windows version, namely
"C:\Program Files\EPSON\ESCNDV\esint32.dll". My Windows XP is german, it
isn't installed on drive C:\, in the scope of Vuescan I'm lost.

Yes, it was a quick hack, and I forgot to use the registry
to look this up. I'll add it to my list of things to fix.

Regards,
Ed Hamrick
 
Digitalis said:
Does this mean that Vuescan does NOT work with MacOSX and Linux and the
Epson 3170?

The protocol translation library is availble on Windows, Mac OS X
and Linux, so VueScan works with the 3170 on all three.

Regards,
Ed Hamrick
 
Ed Hamrick said:
Yes, it was a quick hack, and I forgot to use the registry
to look this up. I'll add it to my list of things to fix.

I re-released VueScan 7.6.79 with a fix for this problem. It was
only a problem on Windows (obviously). It can be downloaded from:

http://www.hamrick.com/vsm.html

Regards,
Ed Hamrick
 
Anyway, an excellent detective job!

Henk


Viktor said:
Henk,

I remembered a posting of Ed where he wrote something about the Epson 3170
not using the standard ESC/I-protocol, normally used by Epson scanners.
The Epson driver has some kind of protocol conversion module which he
thought could be used by him to make the 3170 understand Vuescan or vice
versa.

I was a bit disappointed that Vuescan didn't work, it's kind of a
challange. After more than 20 years of more or less intense contact to
computers, I simply have a feeling what could help me in my/our situation.
I grabbed my favourite editor, loaded vuescan.exe and did a search for the
string "EPSON" ... easy!

That's what makes playing around with computers so funny...

But, it's still Ed's "mistake" to hardcode the needed protocol conversion
module.


\relax\bye % Viktor 8-)
 
Ed Hamrick said:
I re-released VueScan 7.6.79 with a fix for this problem. It was
only a problem on Windows (obviously). It can be downloaded from:

http://www.hamrick.com/vsm.html

Regards,
Ed Hamrick


What I did was to create the path mentioned earlier and managed to get
a scan out of a slide. Now will take some time learning gthe software.
 
Back
Top