Scanners and Windows 2000

What drivers are you talking about?

The latest from BenQ are v2.01 and the ones on the CD are v1.1.
I also tried v2.0 which I happened to have somewhere.
All three of them fail in the same way.

Are you confusing the ScanWit 2720S with another model?

Regards,

Tony

Mr. Chuck wrote:
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

"Mac McDougald" wrote in message
. ..
In article , see_reply-
says...

Neither does any other Windows.

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

Sure it will. Scanner drivers are imaging miniports, or WDM drivers that use
SCSI pass-through. Neither use APSI nor implement TWAIN.

Of course if you have an ancient scanner it may not have Win 2K/XP drivers.

In article ,
says...
"Mac McDougald" wrote in message
. ..
In article , see_reply-
says...

Neither does any other Windows.

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

Sure it will. Scanner drivers are imaging miniports, or WDM drivers that use
SCSI pass-through. Neither use APSI nor implement TWAIN.

Of course if you have an ancient scanner it may not have Win 2K/XP drivers.

Well, so you say.
Drivers allow OS to see the scanner, but it just won't work without ASPI
(which was included in Win9x)
Can assure you that "ancient" scanner like Nikon 2000 will not work
without ASPI in W2K or XP, even though there is W2K/XP compatible
versions of NikonScan. Since there are few (if any) SCSI scanners still
being produced, I'd like to hear from anyone who is running one withOUT
ASPI on system (I'd wager that ASPI is included in the installation CD
for them).

Mac

"Mac McDougald" wrote in message
In article , 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

Well that is your problem.
So you are saying that no SCSI scanner will support TWAIN?

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

Windows does not "run" scanners.
Windows itself does not use ASPI (nor TWAIN).
ASPI (and TWAIN) are programming interfaces used by programs.


Mac

Sorry, wrong model...

MrC.

"Tony" wrote in message
...
What drivers are you talking about?

The latest from BenQ are v2.01 and the ones on the CD are v1.1.
I also tried v2.0 which I happened to have somewhere.
All three of them fail in the same way.

Are you confusing the ScanWit 2720S with another model?

Regards,

Tony

Mr. Chuck wrote:
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

In article , see_reply-
says...
"Mac McDougald" wrote in message
In article , 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

Well that is your problem.
So you are saying that no SCSI scanner will support TWAIN?

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

Windows does not "run" scanners.
Windows itself does not use ASPI (nor TWAIN).
ASPI (and TWAIN) are programming interfaces used by programs.

Thanks for the precise definition, but point is still that SCSI scanner
won't work without ASPI in the Windows environment.

Mac

No, your unsupported scanner does not have Win 2K/XP drivers.

"Mac McDougald" wrote in message
.. .

Well that is your problem.
So you are saying that no SCSI scanner will support TWAIN?

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

Windows does not "run" scanners.
Windows itself does not use ASPI (nor TWAIN).
ASPI (and TWAIN) are programming interfaces used by programs.

Thanks for the precise definition, but point is still that SCSI scanner
won't work without ASPI in the Windows environment.

Mac

In article ,
says...


No, your unsupported scanner does not have Win 2K/XP drivers.

If we are speaking of any actual SCSI consumer scanners (and this thread
was), then of course anyone with a SCSI scanner knows that Mac is correct.
SCSI consumer scanners absolutely do require ASPI in XP to work.

It is true that W2K/XP does provide an alternate Microsoft SCSI API, and
SCSI hard disk drivers and SCSI CD drivers do use it instead of ASPI. The
idea is then they can no longer bypass Windows security to access system
protected disk files, which is why Microsoft discouraged ASPI.

I suppose your point was that the scanner driver **could** have been
rewritten that way too. My point is that it wasnt. Consumer scanners
simply didnt do it, and they do still require ASPI if you want them to
work in XP. Actually consumer scanners instead abandoned SCSI and
converted to Firewire, etc.

The commerical 10-20 ppm class of office document scanners largely stayed
with SCSI so far, and generally use ISIS instead of TWAIN, and I'd guess
ISIS probably no longer uses ASPI, to keep Microsoft happy.

But SCSI consumer scanners still require ASPI, and this is the first thing
to know to make a SCSI scanner work in XP.

--
Wayne
http://www.scantips.com "A few scanning tips"

In article ,
says...
No, your unsupported scanner does not have Win 2K/XP drivers.

Please name one SCSI scanner (film/flatbed/combo) that runs on 2K/XP
without ASPI.

I'm sure if you ran aspichk.exe on that puter, you would find ASPI
installed, however it got there (apparantly from the installation CD that
came with the scanner if user didn't do it separately).

Mac
==================

"Mac McDougald" wrote in message
.. .

Well that is your problem.
So you are saying that no SCSI scanner will support TWAIN?

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

Windows does not "run" scanners.
Windows itself does not use ASPI (nor TWAIN).
ASPI (and TWAIN) are programming interfaces used by programs.

Thanks for the precise definition, but point is still that SCSI scanner
won't work without ASPI in the Windows environment.

Mac

The
idea is then they can no longer bypass Windows security to access system
protected disk files, which is why Microsoft discouraged ASPI.

Thought it was a licensing thing between MS and Adaptac that left it out
of W2K and XP? Or fact that Adaptec didn't have an updated version ready,
or combo of both?

Mac