INFO: SCSI Pass Through Functionality and Limitations

This article was previously published under Q251369
This article has been archived. It is offered "as is" and will no longer be updated.
On Windows NT and Windows 2000, the interface used in an application to send SCSI commands to a SCSI device is called SCSI Pass Through (SPT). A Win32 program uses DeviceIoControl with the IoControlCode of IOCTL_SCSI_PASS_THROUGH or IOCTL_SCSI_PASS_THROUGH_DIRECT. This article explains some of the functionality and limitations of the SCSI Pass Through interface.

Synchronous Requests

The SPT requests are always synchronous. Even if the caller has specified overlapped I/O (FILE_FLAG_OVERLAPPED) and passed the overlapped structure to the DeviceIoControl call, the ScsiPort driver will block the SPT request until the SCSI device completes it.

When completed by the SCSI device (success or error), ScsiPort will complete the SPT request and the calling thread will be unblocked.

Untagged Queuing

A SCSI command can be send to the SCSI device as either untagged or tagged. Untagged queuing permits a device to accept commands from an initiator while executing commands from another. Tagged queuing gives the device the ability to accept a series of commands from the same or different initiators. The SPT always uses untagged queuing while sending commands to the device.
The SPT interface is documented in the Windows NT/Windows 2000 DDK documentation.

For additional information on the SPT interface, click the article numbers below to view the articles in the Microsoft Knowledge Base:
241374 INFO: Read and Write Access Required for SCSI Pass Through Request

There is sample program (SPTI) available in the DDK that demonstrates the SPT interface. It can be found in the \Ddk\Src\Storage\Class\Spti folder.

Article ID: 251369 - Last Review: 12/05/2015 18:19:06 - Revision: 2.2

Microsoft Windows NT 4.0 Driver Development Kit, Microsoft Win32 Device Driver Kit for Windows 2000

  • kbnosurvey kbarchive kbfaq kbinfo kbstoragedev KB251369