Scanners and Windows 2000

There are problems with bus mastering ISA and certain chipsets that show up
under Win 2K but not Win NT. I got myself PCI SCSI 4 years ago.

"Tony" wrote in message
...

HW setup:
PC + Adaptec 1542CF + Adaptec 2904
Acer (now BenQ) ScanWit 2720S Filmscanner
Microtek Phantom 336 Flatbed
Both scanners connected to the 1542CF, film scanner first, then flatbed.
then terminator.

Both working flawlessly when I run with WinNT 4.0 (SP6a).
Apparently there is no HW problem (?).

However...
running W2k SP4 I can't get them to work properly.
Both devices are detected properly and I installed the latest
drivers.

Hi,

I'm having some troubles with my scanners...

HW setup:
PC + Adaptec 1542CF + Adaptec 2904
Acer (now BenQ) ScanWit 2720S Filmscanner
Microtek Phantom 336 Flatbed
Both scanners connected to the 1542CF, film scanner first, then flatbed.
then terminator.

Both working flawlessly when I run with WinNT 4.0 (SP6a).
Apparently there is no HW problem (?).

However...
running W2k SP4 I can't get them to work properly.
Both devices are detected properly and I installed the latest
drivers.

But when I try to scan anything (no matter which scanner) they
start doing so, e.g. the film scanner is focussing, but after a while
the procedure stops and some time later I get a timeout and the scnner
isn't recognised anymore. After a power cycle the scanner regains
consciousness and I can again start scanning but it hangs at the same
step as before.

What I've tried so far:

*) Removed all TWAIN drivers
*) Removed all SW that uses ASPI (surprisingly many)
*) Tried about a half dozen different ASPI layers
*) Tried TWAIN dll's from twain.org
*) Removed one scanner (tried each) from SCSI chain

And of course I have installed/uninstalled the drivers at all stages
and rebooted every time. Also I made sure that when uninstalling the
files really disappear (quite often there are leftovers) and that the
registry is clean (?).

The SCSI drivers in my system are aha154x.sys and aic78xx.sys (both from
the W2k CD)I have re-installed these from the CD as well, but the files
were identical and - of course - it didn't help any.

And yes, I've tried Vuescan. Same story...

I'm runnig out of ideas.

Suggestions anyone?

sigh

Tony

First, I'm no expert in this area; the following is my PERSONAL experience
with ASPI and Win2K (Folkert take note):

I had similar problems writing to my CD writer using programs that require
ASPI under Win2K...

Win2k does not use the ASPI layer and does not (officially) support its'
use, and installing it (ASPI) gives hit-or-miss results. I found that I can
use the aspi driver under *certain* circumstances... under other
circumstances it hangs my bus. Apparently there is some conflict with the
aspi layer whatever newer protocol/transport/whatever Win2K uses...

Here's some unverified info I found in another post that seemed relevant:

Adaptec developed software drivers for their SCSI cards, the ASPI
drivers. CD burners were initially SCSI-only devices, so other
hardware and software makers could reasonably expect the ASPI drivers
to be installed on any computers using their product. So rather than
develop their own solutions, they took advantage of Adaptec's existing
drivers.

Fast forward to 2001. Microsoft produces two operating systems,
Windows ME and Windows 2000, that don't support ASPI in some fashion
or another. Rather than rewrite ASPI to ensure that it is stable,
Adaptec made a business decision to drop ASPI and use the new built-in
capabilities of Windows to instead. So they changed their SCSI card
drivers and their software (ECDC) so that it doesn't need ASPI. (ECDC
4.02e runs fine on my Win2k machine without ASPI.)

Now all of the software makers that hooked on to ASPI are hosed
because Adaptec doesn't support it anymore under Win2k and Win ME.
How is that Adaptec's fault? I've never seen Adaptec incourage other
software makers to use the ASPI layer. I've never seen them push that
as a standard. In fact, as we all know, they have tried to prevent
anyone else from distributing it.


"Tony" wrote in message
...
Hi,

I'm having some troubles with my scanners...

HW setup:
PC + Adaptec 1542CF + Adaptec 2904
Acer (now BenQ) ScanWit 2720S Filmscanner
Microtek Phantom 336 Flatbed
Both scanners connected to the 1542CF, film scanner first, then flatbed.
then terminator.

Both working flawlessly when I run with WinNT 4.0 (SP6a).
Apparently there is no HW problem (?).

However...
running W2k SP4 I can't get them to work properly.
Both devices are detected properly and I installed the latest
drivers.

But when I try to scan anything (no matter which scanner) they
start doing so, e.g. the film scanner is focussing, but after a while
the procedure stops and some time later I get a timeout and the scnner
isn't recognised anymore. After a power cycle the scanner regains
consciousness and I can again start scanning but it hangs at the same
step as before.

What I've tried so far:

*) Removed all TWAIN drivers
*) Removed all SW that uses ASPI (surprisingly many)
*) Tried about a half dozen different ASPI layers
*) Tried TWAIN dll's from twain.org
*) Removed one scanner (tried each) from SCSI chain

And of course I have installed/uninstalled the drivers at all stages
and rebooted every time. Also I made sure that when uninstalling the
files really disappear (quite often there are leftovers) and that the
registry is clean (?).

The SCSI drivers in my system are aha154x.sys and aic78xx.sys (both from
the W2k CD)I have re-installed these from the CD as well, but the files
were identical and - of course - it didn't help any.

And yes, I've tried Vuescan. Same story...

I'm runnig out of ideas.

Suggestions anyone?

sigh

Tony

In article 30gic.2$en3.0@edtnps89, says...
First, I'm no expert in this area; the following is my PERSONAL experience
with ASPI and Win2K (Folkert take note):

I had similar problems writing to my CD writer using programs that require
ASPI under Win2K...

Note that ASPI for Win2K has been updated at least twice in last few
years. When W2K came out, you had to use the version that still worked on
Win95 also.

Now there have been 2 or 3 versions that are specifically for XP/W2K.
They also work on 98/98SE/Me also, if one needs an update.

If you are already using latest, 4.7something, disregard.


Mac

As you can see I have a PCI card in my system as well which serves
6 devices (disks, CD/DVD/ZIP drives). I have already swapped the
two cables. That causes some reconfiguration to make all the
disks work again (drive letters...) but the gain is zero, i.e.the
scanners behave on the PCI card the same as on the ISA.

Regards,

Tony

Eric Gisin wrote:
There are problems with bus mastering ISA and certain chipsets that show up
under Win 2K but not Win NT. I got myself PCI SCSI 4 years ago.

"Tony" wrote in message
...

HW setup:
PC + Adaptec 1542CF + Adaptec 2904
Acer (now BenQ) ScanWit 2720S Filmscanner
Microtek Phantom 336 Flatbed
Both scanners connected to the 1542CF, film scanner first, then flatbed.
then terminator.

Both working flawlessly when I run with WinNT 4.0 (SP6a).
Apparently there is no HW problem (?).

However...
running W2k SP4 I can't get them to work properly.
Both devices are detected properly and I installed the latest
drivers.

Maybe I should give a list of my ASPI trials...

1) The one that came with W2k
I've checked the service packs. There is no update for these.
2) Adaptec v4.6
3) Adaptec v4.7 alpha 2 (anybody has any newer?)
4) Nero v2.0.1.45
5) LSI v1.7.1
6) ACARD (came with film scanner driver)

They do not all behave the same way.
Some do not generate the pop-up error message (timeout) but rather
cause the program to hang.
The error code also seems to vary with different ASPI layers.
Nero is definitely the "best" because it doesn't even detect any scanners...

BTW: scsi configurations are detected nicely with a tool called
"aspi_you" I found somewhere on the internjet.

Regards,

Tony


Mac McDougald wrote:

In article 30gic.2$en3.0@edtnps89, says...

First, I'm no expert in this area; the following is my PERSONAL experience
with ASPI and Win2K (Folkert take note):

I had similar problems writing to my CD writer using programs that require
ASPI under Win2K...


Note that ASPI for Win2K has been updated at least twice in last few
years. When W2K came out, you had to use the version that still worked on
Win95 also.

Now there have been 2 or 3 versions that are specifically for XP/W2K.
They also work on 98/98SE/Me also, if one needs an update.

If you are already using latest, 4.7something, disregard.


Mac

The latest drivers for the Benq do not work, I opened a ticket with Benq and
they told me to revert to the original drivers ver. 3.40 and the scanner
works fine.

MrC


"Tony" wrote in message
...
Hi,

I'm having some troubles with my scanners...

HW setup:
PC + Adaptec 1542CF + Adaptec 2904
Acer (now BenQ) ScanWit 2720S Filmscanner
Microtek Phantom 336 Flatbed
Both scanners connected to the 1542CF, film scanner first, then flatbed.
then terminator.

Both working flawlessly when I run with WinNT 4.0 (SP6a).
Apparently there is no HW problem (?).

However...
running W2k SP4 I can't get them to work properly.
Both devices are detected properly and I installed the latest
drivers.

But when I try to scan anything (no matter which scanner) they
start doing so, e.g. the film scanner is focussing, but after a while
the procedure stops and some time later I get a timeout and the scnner
isn't recognised anymore. After a power cycle the scanner regains
consciousness and I can again start scanning but it hangs at the same
step as before.

What I've tried so far:

*) Removed all TWAIN drivers
*) Removed all SW that uses ASPI (surprisingly many)
*) Tried about a half dozen different ASPI layers
*) Tried TWAIN dll's from twain.org
*) Removed one scanner (tried each) from SCSI chain

And of course I have installed/uninstalled the drivers at all stages
and rebooted every time. Also I made sure that when uninstalling the
files really disappear (quite often there are leftovers) and that the
registry is clean (?).

The SCSI drivers in my system are aha154x.sys and aic78xx.sys (both from
the W2k CD)I have re-installed these from the CD as well, but the files
were identical and - of course - it didn't help any.

And yes, I've tried Vuescan. Same story...

I'm runnig out of ideas.

Suggestions anyone?

sigh

Tony

"Dave" wrote in message news:30gic.2$en3.0@edtnps89...
First, I'm no expert in this area; the following is my PERSONAL experience
with ASPI and Win2K (Folkert take note):

I had similar problems writing to my CD writer using programs that require
ASPI under Win2K...

Win2k does not use the ASPI layer

Neither does any other Windows.

[snip]

Dave wrote:

(snip)

Win2k does not use the ASPI layer and does not (officially) support its'
use, and installing it (ASPI) gives hit-or-miss results. I found that I can
use the aspi driver under *certain* circumstances... under other
circumstances it hangs my bus. Apparently there is some conflict with the
aspi layer whatever newer protocol/transport/whatever Win2K uses...


I really don´t know what to say upon that,
because my scanner runs perfectly under
Win2k with ASPI. Anyway here goes my
system configuration, if it can help:

Win2K SP4
Adaptec ASPI 4.60 (1021)

HP ScanJet 4c scanner connected to
Adaptec 1542CF ISA SCSI controller

Asus P3C-LS motherboard (with embedded Adaptec AIC-7892 Ultra160 SCSI controler)

2 Plextor SCSI CD-RW drives
2 Seagate SCSI Cheetah HDs

Just two notes:

1- Adaptec´s "ASPI Check" utility reports
my OS as WinNT instead of Win2K.

2- The scanner does not works properly if
connected to the SE segment of motherboard´s
SCSI controller bus.

Good luck,

Rubens

-------------------------------------------------------------------------------

(snip)

In article , see_reply-
says...

"Dave" wrote in message news:30gic.2$en3.0@edtnps89...
First, I'm no expert in this area; the following is my PERSONAL experience
with ASPI and Win2K (Folkert take note):

I had similar problems writing to my CD writer using programs that require
ASPI under Win2K...

Win2k does not use the ASPI layer

Neither does any other Windows.

I assure you than no version of Windows will run a SCSI scanner withOUT
ASPI.

Mac