This article is from the CD-Recordable FAQ, by Andy McFadden (firstname.lastname@example.org) with numerous contributions by others.
See http://www.mrichter.com/cdr/primer/aspi.htm for an introduction to ASPI.
Win2K and WinXP software can use an alternate set of interfaces (SPTI).
This avoids the whole issue of having ASPI drivers installed. Use of
SPTI is becoming more common.
Many people have solved problems by updating their ASPI layer. In the
past, it has been the first thing that customer service would ask you
to check. Adaptec makes it easy with a program called ASPICHK, available
(If it has moved yet again, do a google search for it.)
At any rate, according to Roxio, as of version 4.02 of Easy CD Creator
(ECDC), the ASPI layer is no longer used by their product. The necessary
bits are included in the application, so there's no need to check or
update the layer.
For non-Adaptec owners, there is a program (of questionable legality)
called "ForceASPI" that forces the Adaptec ASPI layer to install. Usually
Adaptec will ask sites to remove it, so it's a bit of a moving target.
http://www.mindspring.com/~tburke1/aspi.htm had a list of active sites,
and it can occasionally be found with a Google search. You can also try
Some other software uses and/or modifies ASPI -- poorly. Known examples
are some USB SmartMedia readers and the Creative Labs Infra system.
Updating the ASPI layer when one of these devices is present may be unwise.
It's unclear what interactions Windows ME has with ASPI.
As of September 2001, the Adaptec ASPI layer causes problems on Win2K and
should not be used. The LSI "w2kaspi" layer may work better; it can be
found at http://www.lsilogic.com/support/support+drivers/scsi/w2kaspi.html.
[At last check, the links in the page were broken.] WinXP may have