Kodak Digital Science Scanner Problem

  • Thread starter Thread starter gkamieneski
  • Start date Start date
G

gkamieneski

I inherited a Kodak Digital Science 3500D scanner. This is a 2001
vintage and uses a Kofax Adrenaline SCSI board in the PC running XP.

I downloaded the TWAIN driver and diagnostics from the Kodak website
but the diagnostics cannot recognize the scanner. What is really
strange about this is that I have some demo Kofax applications that
actually cause the paper to feed and be scanned. Other software from
Kodak and Presto Pagemanager do not recognize the scanner at all.

I'm having trouble reconciling how some applications are actually
working with the scanner while the diagnostics and other demo software
from Kodak do not recognize the scanner at all.
 
I inherited a Kodak Digital Science 3500D scanner. This is a 2001
vintage and uses a Kofax Adrenaline SCSI board in the PC running XP.

I downloaded the TWAIN driver and diagnostics from the Kodak website
but the diagnostics cannot recognize the scanner. What is really
strange about this is that I have some demo Kofax applications that
actually cause the paper to feed and be scanned. Other software from
Kodak and Presto Pagemanager do not recognize the scanner at all.

I'm having trouble reconciling how some applications are actually
working with the scanner while the diagnostics and other demo software
from Kodak do not recognize the scanner at all.
Click to expand...

Hi...

Don't have one; don't have any Kodak, but for whatever little
it may be worth...

If you have a scsi drive attached to the same card as the
scanner try removing that drive and see if it works. May be
that you'll have to use a second separate card.

And check with adaptec, see if they have a better driver
available.

Take care.

Ken
 
I inherited a Kodak Digital Science 3500D scanner. This is a 2001
vintage and uses a Kofax Adrenaline SCSI board in the PC running XP.

I downloaded the TWAIN driver and diagnostics from the Kodak website
but the diagnostics cannot recognize the scanner. What is really
strange about this is that I have some demo Kofax applications that
actually cause the paper to feed and be scanned. Other software from
Kodak and Presto Pagemanager do not recognize the scanner at all.

I'm having trouble reconciling how some applications are actually
working with the scanner while the diagnostics and other demo software
from Kodak do not recognize the scanner at all.
Click to expand...

Is there an updated driver for the SCSI card - the drivers may only
support up to ME.

And thinking back something to do with ATAPI interface?? drivers.


Have you checked in your device manager for problems?
 
Ken said:
Hi...

Don't have one; don't have any Kodak, but for whatever little
it may be worth...

If you have a scsi drive attached to the same card as the
scanner try removing that drive and see if it works. May be
that you'll have to use a second separate card.
Click to expand...

I think what you are saying is that the cable needs to be terminated at
the last device in the daisy chain.

If you only have the scanner connected them this still has to be terminated.

Make sure that each device has its own ID 1-7 or they will conflict.
 
I think what you are saying is that the cable needs to be terminated at
the last device in the daisy chain.

If you only have the scanner connected them this still has to be terminated.

Make sure that each device has its own ID 1-7 or they will conflict.
Click to expand...

Thanks, everyone.

I am terminating the device and in fact it is the only SCSI device (I
think this is all SCSI II by the way) that I am using. I went and got
the latest drivers. Next step may be to try a different PC/card
combination. Usually diagnostics will work but not the application.
This time vice versa. The SCSI card's demo scan program feeds 20
sheets in like nothing. It is a very fast mid-production scanner and
worth holding onto.
 
Thanks, everyone.

I am terminating the device and in fact it is the only SCSI device (I
think this is all SCSI II by the way) that I am using. I went and got
the latest drivers. Next step may be to try a different PC/card
combination. Usually diagnostics will work but not the application.
This time vice versa. The SCSI card's demo scan program feeds 20
sheets in like nothing. It is a very fast mid-production scanner and
worth holding onto.
Click to expand...

And I would assume that you are turning the device on before you start
the computer? or your doing a refresh in the device manager so the PB OS
does know the scanner is there?

Random thoughts.

rm
 
Check to see if it required an "active termination" or passive
termination. Two different animals

Adaptec 2940 card was pretty universal.
 
You may also have to clear out the twain32 directory with the scanner
files - look for a name that matches the scanner and delete the files in
the directory. and TWUNK as well.

Did you load the proper ASPI layers ? you can get the latest from
adaptec. Also run ASPIchk after to verify no errors. XP does not have
native ASPI support.
 
You may also have to clear out the twain32 directory with the scanner
files - look for a name that matches the scanner and delete the files in
the directory. and TWUNK as well.

Did you load the proper ASPI layers ? you can get the latest from
adaptec. Also run ASPIchk after to verify no errors. XP does not have
native ASPI support.
Click to expand...

Lots of Adaptec references. Though I'm familiar with their SCSI
offerings, this card is a Kofax accelerator card if that makes any
difference.
 
Lots of Adaptec references. Though I'm familiar with their SCSI
offerings, this card is a Kofax accelerator card if that makes any
difference.
Click to expand...

What has been suggested needs to be followed irrespective of the brand
of SCSI card.

Also you have to check and get the ASPI driver for XP which can be
downloaded from Adaptec site. This has been mentioned twice now.

Make sure when you boot the PC have the device switched on. Then check
in the device manager that the PC is seeing the device - not just the
SCSI card.

Lets know if you can see the device as its becoming obvious that its not
being seen. This requires all the drivers(3)for XP to be installed.

http://www.adaptec.com/en-US/support/scsi_soft/

http://www.kofax.com/support/downloads.asp

Plus the XP Scanner drivers Kodak Digital Science 3500D.
 
What has been suggested needs to be followed irrespective of the brand
of SCSI card.

Also you have to check and get the ASPI driver for XP which can be
downloaded from Adaptec site. This has been mentioned twice now.

Make sure when you boot the PC have the device switched on. Then check
in the device manager that the PC is seeing the device - not just the
SCSI card.

Lets know if you can see the device as its becoming obvious that its not
being seen. This requires all the drivers(3)for XP to be installed.

http://www.adaptec.com/en-US/support/scsi_soft/

http://www.kofax.com/support/downloads.asp

Plus the XP Scanner drivers Kodak Digital Science 3500D.- Hide quoted text -

- Show quoted text -
Click to expand...

I installed the Adaptec ASPI layer and ran aspichk.exe. It reported
that Wowpost.exe and WNASPI.DLL were not installed as it should as I
installed for Win XP. I reinstalled the Kofax Adrenaline and Kodak
3500D drivers. The latter is a combination driver/ diagnostic called
kds_bitonal_080400.exe. You are correct the Adrenaline board is being
seen however the Kodak 3500D is not. Doesn't seem to be a way to pick
it up pNp or by forcing it.
 
I installed the Adaptec ASPI layer and ran aspichk.exe. It reported
that Wowpost.exe and WNASPI.DLL were not installed as it should as I
installed for Win XP. I reinstalled the Kofax Adrenaline and Kodak
3500D drivers. The latter is a combination driver/ diagnostic called
kds_bitonal_080400.exe. You are correct the Adrenaline board is being
seen however the Kodak 3500D is not. Doesn't seem to be a way to pick
it up pNp or by forcing it.
Click to expand...

Then make sure your using the XP (32bit)drivers for your scanner. If you
can't find the Xp specific ones then you should find and load the
Windows 2000 drivers - these should work. Then do a install new hardware
(forced) install to find the scanner and match the drivers.


Just as an after thought have you looked at Vuescan site to see if your
scanner is supported (as its SCSI) and tried using that as a test
software?? Ed Hamrick wrote quite a bit of code to support SCSI stuff.

http://www.hamrick.com/
 
I installed the Adaptec ASPI layer and ran aspichk.exe. It reported
that Wowpost.exe and WNASPI.DLL were not installed as it should as I
installed for Win XP. I reinstalled the Kofax Adrenaline and Kodak
3500D drivers. The latter is a combination driver/ diagnostic called
kds_bitonal_080400.exe. You are correct the Adrenaline board is being
seen however the Kodak 3500D is not. Doesn't seem to be a way to pick
it up pNp or by forcing it.
Click to expand...

Adaptec's ASPI package often fails on XP and sometimes on Win98SE also.
But it MUST be installed for SCSI scanners to work.
Try ForceASPI 1.7. It will work, does version 4.6 of the files, which is
fine.
You should have installed:
aspi32.sys
wowpost.exe
winaspi.dll
snaspi32.dll
These can be confirmed by aspichk.exe

Just google for forceaspi or force aspi to find it.

MM
 
Adaptec's ASPI package often fails on XP and sometimes on Win98SE also.
But it MUST be installed for SCSI scanners to work.
Try ForceASPI 1.7. It will work, does version 4.6 of the files, which is
fine.
You should have installed:
aspi32.sys
wowpost.exe
winaspi.dll
snaspi32.dll
These can be confirmed by aspichk.exe

Just google for forceaspi or force aspi to find it.

MM
Click to expand...

I will look into this, but Adaptec seemed to indicate that wowpost.exe
and winaspi.dll are not installed under XP as they are for 16-bit.
 
Then make sure your using the XP (32bit)drivers for your scanner. If you
can't find the Xp specific ones then you should find and load the
Windows 2000 drivers - these should work. Then do a install new hardware
(forced) install to find the scanner and match the drivers.

Just as an after thought have you looked at Vuescan site to see if your
scanner is supported (as its SCSI) and tried using that as a test
software?? Ed Hamrick wrote quite a bit of code to support SCSI stuff.

http://www.hamrick.com/
Click to expand...

Vuescan doesn't see the scanner either. Thing is, I can't find these
drivers anywhere, XP or W2000. All I can find is the combination
driver/ diagnostic called kds_bitonal_080400.exe and that doesn't seem
to allow me to manually install the scanner.
 
I will look into this, but Adaptec seemed to indicate that wowpost.exe
and winaspi.dll are not installed under XP as they are for 16-bit.
Click to expand...

I'm using XP Home, and two SCSI scanners (old HP and LS-2000).
I assure you that all four files are installed in the ASPI layer.
Whether all four are necessary I don't know, but everything works fine,
but with HP and Nikon scanning utils, and with VueScan.

MM
 
I'm using XP Home, and two SCSI scanners (old HP and LS-2000).
I assure you that all four files are installed in the ASPI layer.
Whether all four are necessary I don't know, but everything works fine,
but with HP and Nikon scanning utils, and with VueScan.

MM
Click to expand...

I'll take another look at it, but the Adaptec doc said that only the
32-bit versions were necessary. Seems the Kofax board is a little
more than a SCSI board. I wonder if that's why Device Manager doesn't
report the scanner, just the board?
Click to expand...
Click to expand...
 
I'll take another look at it, but the Adaptec doc said that only the
32-bit versions were necessary. Seems the Kofax board is a little
more than a SCSI board. I wonder if that's why Device Manager doesn't
report the scanner, just the board?
Click to expand...


There would seem a couple of possibilities. SCSI devices do not have to use
ASPI today. SCSI hard disks for example have not used ASPI for years, but
instead use the SCSI API and disk drivers provided by Windows. Others can
use the Windows SCSI API too, but very few scanner drivers were rewritten to
do so. CD drives installed by Windows setup doesnt use ASPI either.

When used, ASPI was the classic interface between the Adaptec SCSI driver
and the other applications (for example the manufacturers device driver).
Other SCSI board manufacturers also provided the ASPI interface. Had to,
since scanner stuff was written to see ASPI. Without ASPI (which Win2000
and WinXP and Vista no longer provide), the scanner is not visible by the
scanner driver or Windows or anyone else, that middle link is missing. A
few scanner companies license and install ASPI with their drivers, but you
can install it from Adaptec for those that dont. The latest ASPI version
will install without an Adaptec board being present (earlier would not,
hence the "Force" stuff).

I am totally ignorant of the Kofax board, but if it worked without ASPI,
then clearly it uses the Windows SCSI API instead of ASPI. Which is the
more modern way today, but it has not been conventional for scanners. I
think Kofax must have written their version of the Kodak scanner driver too,
to work with their board and driver for their application. Like VueScan
writes the device driver too, however VueScan uses ASPI. So the
Kodak-provided scanner drivers probably do use ASPI (guessing), since most
scanners do, almost no one bothered to rewrite.

So the question seems to be if the Kofax SCSI board and driver is spec'd to
also provide an ASPI interface to third party applications needing it, like
probably the Kodak-provided scanner application. They would not need that
for their own application (since you say it works without ASPI), but may do
it as a courtesy to allow other programs to use their SCSI board. Did they,
or didnt they? It would have been an extra step for them to take. A
very superficial look did not see the word ASPI jumping out there. The
Kofax support people could quickly tell you if it is supposed to work or not
with ASPI.
 
Back
Top