Scanwise 1212u

[David Perrault]

Hi

I have the above scanner and have installed the latest drivers from Agfa's
web site but it does not work. What happens is I get an error as follows " A
communication problem occurred Open the log file to find out more" so I did
and it says

++++ PROBLEM DESCRIPTION +++++
++++ SAT ERROR ID: A communication problem occurred.
Open the log file to find out more.
++++++++ERROR STRING: General SCSI error, <<detail>>
++++++++++++++++++++++++++++++


Any ideas ?

Thanks for looking

 

[RSD99]

We need to know more information. As an absolute minimum ...

(1) What operating system?
(For instance, if Windows XP ... did you install the
ASPI
software from Adaptek?

(2) What hardware? Specifically, what SCSI adapter, and what
devices are connected to the adapter.

(3) Does the SCSI "chain" work with anything ... has it ever
worked with anything?

 

[David Perrault]

Win XP pro - this is a UBS device not SCSI.
Latest drivers installed after an uninstall of previous software.
Worked fine before on XP as well but rebuilt my machine and does not work anymore.

 

[RSD99]

If it is a USB device, why is the error string you are
quoting

"ERROR STRING: General SCSI error"

 

[David Perrault]

Very good question for which I don't have a response- this is
definitely a USB scanner and I downloaded the right drivers from the
Agfa website.

 

[CSM1]

Did you try to re-install the USB drivers on your motherboard?

Open Device Manager, select the USB controller properties, update driver.
Maybe check your motherboard manufacturer's support web site for new
drivers.

 

[RSD99]

Good idea ... I would probably also try (just on "General
Principles") installing the Adaptec "ASPI Layer" software.
Some portion of a poorly written driver (one that some
hack-programmer 'converted' from a SCSI-based application)
might be mistakenly trying to find or use one of those
subroutines ... and Windows XP no longer includes them "by
default."

 

[news.ntl.com]

Hi David,

Came across your post - any luck with this problem? I'm having the same
problem with my scanner since trying to upgrade the Scanware software to the
2.009 version - now can't get the scanner to respond - have tried going back
to the previous version, still the same error as below.

Peter

 

[Sanktwo]

I had the same "SCSI" error today on Windows 2000 with an Agfa
Snapscan E-40. Now it is fixed after much pain.
The short answer: As far as I can tell, Scanwise does NOT install
correctly if there are ANY other USB devices plugged in and possibly
not if there is history in the registry. I uninstalled Scanwise,
cleaned the registry, unplugged all devices, re-installed on Windows
2000 and bingo, it sprang to life.
The long answer:
I do not like Scanwise very much, so I sort-of hoped that the latest
version would be better than the "old" one (3 versions previously).
On a working scanner system (E-40) I uninstalled Scanwise. Downloaded
the latest from Agfa site and installed without changing ANYTHING in
the hardware. Promptly a complaint "+++++++ERROR STRING: General SCSI
error, <<detail>>" was in the log file and the application
would not run.
I used a USB monitor (Compuware WDMSniff) and a registry monitor
(www.sysinternals.com regmon) to discover the behaviour of Scanwise.
The application always tries the USB route first, and if that fails
it then looks up registry entries for the SCSI system. It tries scsi
units 0 and 1 and then times out with the complaint that you
referenced. What was interesting is that, even when it failed, it
actually managed to talk to the scanner via USB (about 6
bi-directional interactions). Obviously Scanwise did not like the
response from the scanner and for some reason decided that it did not
wish to continue to discuss with the scanner via USB. I then
uninstalled Scanwise. I unplugged ALL USB devices. I deleted anything
in the registry that I could find which mentioned Agfa, scanwise or
snapscan. I then plugged in ONLY the scanner. I received a message
saying that I should install the software from Agfa. That I did and,
without rebooting Windows the scanner sprang to life. Using the
monitor the first 12 messages down the USB device were the same as in
the failing case, but then it carried on with the normal business.
Thus the message about SCSI is a GIANT RED HERRING for USB based
scanners. The Scanwise (Scanstupid?) software writer failed to give
an error message saying why the USB interaction was unsuccessful. So,
my problem is solved and was not a hardware related problem - just
incompetent software.