#ES-300C & A4000/040
11 messages in this thread
I saw your problem, and just wanted to let you know that you are NOT
alone! I have exactly the same problem, and ASDG gives me the same
answer! I purchased the ES-300C when I owned my A500, and then
upgraded to my A4000. I even got a new motherboard on my A4000,
thinking that would solve all of my problems. The new motherboard
solved some problems I was having with Deluxe Paint, but the Epson
scanner problem remains.
ASDG even supposedly sent me an upgrade which was supposed to "fix"
this non-existant problem, and they even talked me through the
installation over the telephone. When I still had the same problem,
the tech at the other end basically threw up his hands and said he
had no idea why I was still having the problem. They claim not to
have the problem at their end, but then why are we out here having
the problem? I know it's not the motherboard this time, so it has to
be a glitch in the program. I'm just hoping that the ADPro 2.5 will
fix it.
PMFBI If you are referring to to having to do "cpu nodatacache"
before using your Epson300C with ADPro & 4000/40, you'll still have
to do that with the 2.5 upgrade. Gracia, on AutoPilot from
Cooleemee, NC
I am sorry all you Epson Scan/ 040 users are having this cache problem
but the fact still remains is that we have not been able to reproduce
this problem. I would like nothing more than to have this problem
resolved but any fixes we attempt would basically be guesswork since
we dont have this problem.
If it is a glitch in our scanner driver, we would happily update it
but until we can get this to happen on our end, there is no ready
solution.
Please believe me when I say we want this to be resolved every bit as
much as the rest of you do.
Chris Edgin ASDG tech,
Chris,
I just had a thought… What if it's your scanner? Mabye you have a
newer revision that has some improved firmware… Something that doesn't
produce our suspect errors…
Drop me EMail or post a list of what you have (As far as CXchange
software and other packages you have in your startup-sequence and user-
startup… I will duplicate your configuration EXACTLY and try out this
hypothesis… I have a feeling it might be the answer.
Thanks,
Don Suhr 73117.1337@compuserve.com
I will check the scanner firmware revision and see if it matches yours. As far
as add-ons are concerned, we run clean machines with exeception of debugging
tools (enforcer, mungwall, etc.).
Chris Edgin ASDG tech.
Chris,
Sounds good. I will restore my machine to a clean slate and try v2.3
again… If I can convince my friend to bring his A4000/040 over, I will also
be able to report on v2.5.
I will also get the firmware/version of my Epson ES-300C… Would be a
wonderous thing if we were able to solve this one…
Don Suhr 73117.1337@compuserve.com
Chris,
Ok… I couldn't come up with a Firmware # for the scanner, but there
were two numbers on it… The first was the serial # 0Y90006173. The second was
unmarked on a small label and was B01608001UA168059. My DIP switch settings
are:
Switch 1: ON/OFF/OFF/ON/OFF/OFF/OFF/OFF
Switch 2: ON/OFF/OFF/OFF/OFF/ON/ON/OFF
I setup my Amiga 4000/040/25 with only the original software,
aside from ADPro. I WAS able to get the scanner to respond ONCE if I
turned off the cache then turned it back on, although only for the
Preview mode. The fine mode would only cause the scanner to go
immediatly into the E-1 alert, unless the data caches were disabled
first.
For the validity of cross-testing, I just want to be sure that
the system you are testing the scanner with is an A4000/040 25mhz
with OS3.0… Also, the Copyback data cache needs to be turned on to
show this problem. The version of the 68040.library in my system is
37.30… I can't think of anything else to add at this point.
Chris: I've been following this thread about the Epson scanner problems
with 040 users but wanted to do some testing on my own before I posted the
results, and ask a few questions. First off, it seems to happen only when
the scanner module is trying to initialize the scanner. As soon as you hit
the PREVIEW button, or ACCEPT for the final scan, the scanner immediately
displays the E-I Interface error. When the copyback mode is off and you
start the scan, you can then go and turn on copyback without any problems
from the scanner. In fact, this usually speeds up the scan considerably.
So copyback doesn't seem to affect a scan already in progress where the
computer is receiving data. I imagine that during the scan, the scanner
module is sending some kind of acknowledge for handshaking, or is the
scanner the only device sending data?
From what I have been able to gather from the operation of the scanner,
this is how I guess a scan is done:
1. An initialize command is sent to the scanner to home the carriage and
set a default state.
2. Commands are then sent to set resolution, scanning area, brightness,
and other modes the user has selected for the preview or final scan.
3. The scan is then performed using some kind of handshaking between the
computer and scanner.
Mind you, I'm taking a wild guess on the operation considering I haven't
used a scope to actually check the sequence, nor do I have a technical
manual for the scanner. One thing I tried was to force the EPSON_SCAN
loader to load into Chip memory. When the loader is in chip memory, it
functions normally although rather slow. So it seems to follow the pattern
that the loader is having some kind of problem with data caching since it
is disabled for chip memory. So maybe trying a CacheClearE() command
before the initialization commands are sent to the scanner? Mind you, I'm
not an expert Amiga programmer by any means, but I like to do a little
digging before I get on and say "It doesn't work!!" 8^)
// John – (Who enjoys harrasing the vendors)
\X/ Mercury@ins.infonet.net
Jeannie,
I just tried a friend's copy of ADPro v2.5 with my scanner & HIS
A4000/040
.. Guess what… Same problem… It still puts the scanner into an error
mode… Sigh… I guess I'll wait for v2.6… (or 2.7/8/9/3.0…)
Thanks for the support… Sorry to say it's for a problem…
Don Suhr 73117.1337@compuserve.com
Thanks for the message. Now, I'm not as anxious to get the new 2.5
version as I had been. Hopefully there'll be a time when ASDG can
finally realize that there IS a problem, even though they can't
"duplicate it there." I see too many messages from Amiga users who
have had this problem for it to be our error.
It would be nice if ASDG tried to do some field work…asked the users
who had the problem what their startup sequence was, or let us see
what their startup sequence was. Maybe there's a small glitch in the
order of the sequence or something ASDG is overlooking that could
solve this problem. I wish I had the money to fly one of their techs
to my house so that they wouldn't think we're all halucinating!
The more I work with ADPro, the more I want to buy PhotoShop (and I've
worked with ADPro for over 3 years!).
We KNOW that there is a problem AND we want to fix it! I am absoultely sure
that you are not dreaming and I am sure that it is not user error.
Every time we look into this, we come up with the same results (different
people here have tried this and have come up blank – very frustrating).
We HAVE asked what people's user startups & WB startups are like, what boards
they have, waht OS, what add-ons (as well as temperature of the room, checks
for RF interference, scanner revisions, cables, motherboards, etc.)
The bottom line is that we have and are trying to get this thing fixed but
until we can make it happen aand we would flying blind if tried to make a fix
without know what was causing the problem.
We look into this problem every time someone brings it up. Hopefully we will
find out what it is.
Chris Edgin ASDG tech.