Ian Jackson wrote:
In message , Lil' Dave
writes
"pg" wrote in message
...
On Feb 11, 3:11 am, Martin Trautmann wrote:
On Tue, 10 Feb 2009 22:39:28 -0800 (PST), pg wrote:
"The scanner is not ready! Please check the scanner connection."
Did I do anything wrong??
Microteks software here is most annoying.
I don't know which is the right order, but the scanner has to be plugged
in properly before/after installing the software (I'd guess after).
Otherwise it might be ignored.
Mine can't be used via an USB hub.
- Martin
I have plugged and unplugged the scanner, rebooted the PC several
times, and even un-installed and re-installed the software, and still
I got the error !!!
I checked the scanner as well, no problem.
Oh well ... This is getting very very weird !!
----------
Forgot to mention both my previous MicroTek scanners were scsi connected
using scsi ID 6 with active termination. I started out early with
flatbed
scanners using the old printer port connection. Scsi seems to work best
both for connection, and, actual throughput without worry of
interruption.
Maybe it's just a coincidence, but my nine year old Epson 1260 has also
just stopped working. [XP Home, BTW.] However, it's still OK on a laptop
using XP Professional.
I've uninstalled and reinstalled the original software, and also used
the latest TWAIN driver, run a registry repair, re-done the un- and re-
installations etc, but I always get a report saying that there is no
TWAIN driver.
Yes, the computer knows the scanner is there, and says it's working -
but unless it can recognise the TWAIN driver, it isn't going to work.
Fortunately, it WILL work (although with far fewer options) with two of
my little-used imaging programs - Photshop 7 and Microsoft Paint. These
can use the WIA driver, and that hasn't been affected.
http://www.scanhelp.com/ScanEdu/wiascanners.html#List
http://en.wikipedia.org/wiki/Windows_Image_Acquisition
I've done a bit of digging in the newsgroup and forum archives, and it
seems that this sudden failure of various scanners to work may be linked
to one of the Windows updates. There are countless helpful suggestions
but, unfortunately, I've only found one person who positively said "I
did this, and it fixed it". I think that alt.comp.periphs.scanner (which
I have just found) might provide the best leads, but I have only started
to peruse the old posts. I think this was one of them.
http://thedailyreviewer.com/xphelp/v...02500249#10189
7202
I'm in two minds as whether to accept the fact that I still can use the
scanner (but not like I used to) and get on with my life, or to pursue a
fix, and possibly screw up my PC in the process!
If you sort the contents of C:\WINDOWS by date, then look for things
like $NtUninstallKB2641690$ , the contents of those may contain things
like .dll files that got replaced by recent Windows update. That may
give a hint as to what has changed. Since you have a rough idea when
the problem arose, you won't have to go back too far.
You can also find some hints in Event viewer. Too bad the interface
on that thing is so bad, as if it had a decent interface, it would be
easier to find the offender.
I scanned back through my updates, and don't see anything TWAIN related,
but I also don't have a scanner connected. So maybe if something changed,
it's an actual scanner driver that changed ?
I've had one change in the behavior of my system recently, which
was getting Explorer killed by DEP (data execution prevention). That's
happened twice now. It may be related in some way, to a piece of software
that's been installed for years, but I only started using it again a
few weeks ago. And time wise, there is no relation to the Explorer problem,
and usage of that program. That's the only strange thing of note on my
WinXP Pro SP3 32 bit system here.
http://en.wikipedia.org/wiki/Data_execution_prevention
Paul