Advanced SCSI Programming Interface
An editor has nominated this article for deletion. You are welcome to participate in the deletion discussion, which will decide whether or not to retain it. |
This article includes a list of general references, but it lacks sufficient corresponding inline citations. (June 2009) |
In computing, ASPI (Advanced SCSI Programming Interface) is an Adaptec-developed programming interface which standardizes communication on a computer bus between a SCSI driver module on the one hand and SCSI (and ATAPI) peripherals on the other.[1]
ASPI structure
[edit]The ASPI manager software provides an interface between ASPI modules (device drivers or applications with direct SCSI support), a SCSI host adapter, and SCSI devices connected to the host adapter. The ASPI manager is specific to the host adapter and operating system; its primary role is to abstract the host adapter specifics and provide a generic software interface to SCSI devices.
On Windows 9x and Windows NT, the ASPI manager is generic and relies on the services of SCSI miniport drivers. On those systems, the ASPI interface is designed for applications which require SCSI pass-through functionality (such as CD-ROM burning software).
The primary operations supported by ASPI are discovery of host adapters and attached devices, and submitting SCSI commands to devices via SRBs (SCSI Request Blocks). ASPI supports concurrent execution of SCSI commands.
History
[edit]Originally inspired by a driver architecture developed by Douglas W. Goodall for Ampro Computers in 1983,[2] ASPI was developed by Adaptec around 1990. It was initially designed to support MS-DOS, OS/2, Windows 3.x, and Novell NetWare. It was originally written to support SCSI devices; support for ATAPI devices was added later. Most other SCSI host adapter vendors (for example BusLogic, DPT, AMI, Future Domain, DTC) shipped their own ASPI managers with their hardware.[3]
Adaptec also developed generic SCSI disk and CD-ROM drivers for DOS (ASPICD.SYS and ASPIDISK.SYS).
Microsoft licensed the interface for use with Windows 9x series. At the same time Microsoft developed SCSI Pass Through Interface (SPTI), an in-house substitute that worked on the NT platform. Microsoft did not include ASPI in Windows 2000/XP, in favor of its own SPTI. Users may still download ASPI from Adaptec. A number of CD/DVD applications also continue to offer their own implementations of ASPI layer.
To support USB drives under DOS, Panasonic developed a universal ASPI driver (USBASPI.SYS) that bypasses the lack of native USB support by DOS.
Driver
[edit]ASPI was provided by the following drivers.
Operating System | Driver Filename | Bundled |
---|---|---|
MS-DOS | ASPI4DOS.SYS or USBASPI.SYS (USB drives only) | No |
Windows 3.1x | WINASPI.DLL | No |
Windows 95, 98 and ME | WNASPI32.DLL, WINASPI.DLL, APIX.VXD and ASPIENUM.VXD | Yes |
Windows NT, 2000, XP | WNASPI32.DLL, ASPI32.SYS | No |
See also
[edit]- SCSI Pass-Through Direct (SPTD)
- SCSI Pass Through Interface (SPTI)
References
[edit]- ^ Sawert, Brian (March 1994). "The Advanced SCSI Programming Interface". Dr. Dobb's Journal.
- ^ "Douglas W. Goodall - Ampro Computers". Retrieved 2017-01-28.
I worked briefly at Ampro in order to modify the CP/M-80 BIOS for the Little Board Z80 to support SCSI hard disk operations. […] I suggested my skills would be better used working with a 16-bit card such as an 80186. […] I wrote the SCSI support for that board as well. […] I taught a staff employee the principles of my driver architecture. He then left Ampro and went to work for Adaptec, where he reproduced my driver architecture and it ended up being called ASPI.
- ^ Myers, Ben. "More on ASPI".