I've noticed just recently (probably since installing SP1) that my Canon
Lide 60 has stopped working right. To be specific, the only way I can
reach the scanner interface for advanced scanning is to launch it from
the canon toolbox utility. Then, once the image is delivered to
photoshop, I have to start the re-launch the scanner interface again; I
can't get it to stay open for more pages to be scanned. It used to open
just fine directly from Photoshop and wouldn't close until I
deliberately dismissed it.
I've checked MS knowledge base and Canon support but I see no newer
drivers and no other reports of my specific issue. The error I get when
trying to open the twain interface from photoshop is: "Could not open
the twain source".
Other apps, such as Microsoft Doc imaging, don't see teh scanner at
all. I also tried downloading VueScan but that couldn't see the scanner
either.
I only scan infrequently so I'm not gonna run out and buy a new
scanner, but when I do scan it's usually more than one page, so this is
a pain.
Thanks, Bob Graham

Signature
rvgraham
rvgrahamsevatenein@sbcglobal.net - 14 May 2008 05:27 GMT
I guess this is not a very active newsgroup. Anyway, I found the
problem in my case. Probably not SP1 related...
I have alot of software installed and it aparently keeps adding more
and more onto the Path variable in System Properties. On the advice of
another user in another forum, I added C:\Windows\twain_32\ (and the
name of the particular folder in there my scanner uses, not the same
for other scanners). Problem solved, without so much as a reboot!
Bob
> I've noticed just recently (probably since installing SP1) that my Canon
> Lide 60 has stopped working right. To be specific, the only way I can
[quoted text clipped - 22 lines]
> --
> rvgraham
Simon - 22 May 2008 11:42 GMT
Hi
I have a Canoscan 3200F scanner and it couldn't find the Twain driver.
Adding the path you suggested fixed the problem. I reckon it was something to
do with adding Sp1 as it worked fine before that!
> I guess this is not a very active newsgroup. Anyway, I found the
> problem in my case. Probably not SP1 related...
[quoted text clipped - 33 lines]
> > --
> > rvgraham