Scanners and Windows 2000

Absolutely clueless. Win 2K uses STI drivers, and XP uses a variation called
WIA. Neither use APSI.

http://www.fdg.fujitsu.com/home/faqs...&CID=9&xid=155

"Mac McDougald" wrote in message
. ..
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).

Win 98/2K uses STI drivers, and XP/ME uses a variation called WIA. Both use
the WDM still image driver for SCSI, not ASPI or SPTI. See figure 15.6 in Win
2K Pro Res Kit.

TWAIN and ISIS are APIs that sit on top of drivers. APIs and drivers are very
different.

If you have a TWAIN/ASPI driver, it predates Win 98.

http://www.microsoft.com/whdc/device...g-connect.mspx

"Wayne Fulton" wrote in message
...
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.

In article ,
says...


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?


It was a mess, political, not technical. One early factor was that ASPI
disks could bypass Microsoft security - ASPI could access the disk directly
anyplace it was told to, didnt bother with passwords, so Microsoft stopped
distributing Adaptec ASPI. But SCSI scanners simply couldnt work without
ASPI (however most of us still used Win98 that included ASPI). There were
other methods possible, and scanner drivers could have been rewritten, but
were not. Some did adopt STI for the buttons, but they largely werent SCSI
anymore. Adaptec sold ASPI with their EZ-SCSI package for their own SCSI
cards. A few scanners licensed and installed ASPI for W2K/XP (this didnt
conflict with Adaptec products). CD software was rewritten to be non-ASPI,
since Adaptec was marketing the EZCD software then, and wouldnt provide ASPI
for competitor CD software or other SCSI cards. Illegal patches were popular
to allow it to be installed in a non-Adaptec environment. A mess, conflicts
of proprietary standards.

This seemed tolerated during NT and W2K, which wasnt a mass market, but when
XP came out, then Joe User was affected. So about 4 months after XP
appeared, and after Adaptec disposed of EZCD, then ASPI 4.71 appeared, free
for all comers, officially blessed for XP by the powers that be. Earlier
versions worked, but were not blessed g

Microsoft publishes Knowledge Base Q300674 that says if you want your SCSI
scanner to work with XP, then install ASPI. But there were few SCSI
scanners left.

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

In article ,
says...
In article ,
says...


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?


It was a mess, political, not technical. One early factor was that ASPI
disks could bypass Microsoft security - ASPI could access the disk directly
anyplace it was told to, didnt bother with passwords, so Microsoft stopped
distributing Adaptec ASPI. But SCSI scanners simply couldnt work without
ASPI (however most of us still used Win98 that included ASPI). There were
other methods possible, and scanner drivers could have been rewritten, but
were not. Some did adopt STI for the buttons, but they largely werent SCSI
anymore. Adaptec sold ASPI with their EZ-SCSI package for their own SCSI
cards. A few scanners licensed and installed ASPI for W2K/XP (this didnt
conflict with Adaptec products). CD software was rewritten to be non-ASPI,
since Adaptec was marketing the EZCD software then, and wouldnt provide ASPI
for competitor CD software or other SCSI cards. Illegal patches were popular
to allow it to be installed in a non-Adaptec environment. A mess, conflicts
of proprietary standards.

This seemed tolerated during NT and W2K, which wasnt a mass market, but when
XP came out, then Joe User was affected. So about 4 months after XP
appeared, and after Adaptec disposed of EZCD, then ASPI 4.71 appeared, free
for all comers, officially blessed for XP by the powers that be. Earlier
versions worked, but were not blessed g

Microsoft publishes Knowledge Base Q300674 that says if you want your SCSI
scanner to work with XP, then install ASPI. But there were few SCSI
scanners left.

Ah, thanks Wayne...I'm stashing this one in my UseNet gems section. I
never really understood the whole nuanced saga!

Mac