Canon FS2710 and Windows XP

  • Thread starter Thread starter Peter
  • Start date Start date
P

Peter

There's at least 4 years worth of archive on this subject and I must have
ploughed through most of it.

The scanner, SCSI card and cable work fine in a Pentium II W2000 machine.

I'm attempting to move the equipment to a new PC running XP Pro SP2. The
CPU
is an AMD Athlon 64.

I've installed the updated Adaptec Windows ASPI drivers version 4.71.2 (both
XP32 and XP64 tried). Device manager reports the SCSI controller as working
properly.

I've also downloaded the latest 3.6 version of the Canon Scancraft software.

When the PC is started with the scanner connected and powered on, there is a
few seconds fidgeting from the scanner and the 'Found New Hardware' wizard
pops up, identifying the device as "Canon IX-27025E SCSI Scanner
Device". However the wizard is unable to find the required software, either
automatically or when directed to the downloaded Canon software or the
original Canon CDROM.

Running SETUP.EXE in the downloaded software runs the installation, but
right at the end a window pops up "Configuration Manager - Error Reading
SCSI Devices". On pressing OK another window announces "Configuration
Manager - Automatic Configuration was successfully completed" and the
installation completes.

The scanner cannot be seen by the installed Canon software or by VueScan.
Device Manager is aware of the scanner when it is switched on, showing a "?"
next to the entry. No driver details are shown.

Where am I going wrong?

Peter
 
Ah, the world of SCSI.
Makes one appreciate USB and firewire.
If your card is recognized in WinXP as being installed properly with the
correct driver then the card is not the problem.
The most common cause of these types of issues is: the SCSI cable! Unless
your scanner has died.
Make sure none of the pins are bent and that the cable sits properly. If
there are no problems then something internal in the cable may have come
apart and you can try replacing the cable or replacing the scanner with a
newer non-SCSI model. Sad to say the latter may be a better choice in the
long run.
 
It's also possible that the Cannon scanner may not even have an .inf
file with the installation software which would cause the scanner to be
seen in device manager with a ? icon and put it under the
"other devices" category. This is quite common with scsi technology
because the device/ technology is not dependent on windows.

I would say that there may be a connectivity problem only if the
scanner model was not listed properly in device menager.. (
hyroglyphics or mispelling of the model) otherwise, it's probably
ready to scan already.

otherwise if the scanner is listed properly, try to scan with your
software.

if it fails, try:
1. verify aspi (even though you ran the update- trust me, more people
miss this than you'd imagine)
running the aspichk.exe should show the following: version 4.71.2 for
both the aspi32.sys AND the wnaspi.dll
the other 2 files should say v4.60 (1021) 0
run the aspiinst.exe file if this is not the case... reboot is required
after

2. if aspi is okay, verify by installing the twain and testing with
another application: something like word would even work

if this still doesn't work , what model adaptec scsi card do you have?
what's the scsi ID of the scanner? is it properly terminated? etc...

hope it helps....

hope it helps...
 
Danny said:
if it fails, try:
1. verify aspi (even though you ran the update- trust me, more people
miss this than you'd imagine)
running the aspichk.exe should show the following: version 4.71.2 for
both the aspi32.sys AND the wnaspi.dll
the other 2 files should say v4.60 (1021) 0
run the aspiinst.exe file if this is not the case... reboot is
required after
Click to expand...

Spot on! Aspichk.exe showed the other two files 'not installed'. After
running aspiinst.exe and rebooting I am happily scanning.
hope it helps....
Click to expand...

It sure did! Very many thanks.

Peter
 
Back
Top