Actually IDE/EIDE family members are the poor relatives of SCSI2 devices. I have no experience in dealing with IDE/EIDE devices. There should be very good sites around the web talking about this subject.

The HA_num variable in the outermost "for" cycle in the provided sample code:

for ( BYTE HA_num = 0; HA_num < HA_Count; HA_num++ )

starts from zero and goes up to HA_Count, scanning each host adapter found, IDE/EIDE controller included. Please note that the value of HA_num is the host adapter card number, an unique identifier assigned by the ASPI manager. I don't know how does the ASPI manager assign these numbers to the installed host adapters, but as soon as your SCSI2 host adapter card gets one assigned, it should be always passed in the SRB_HaId member of the SRB for the commands to reach the desired host adapter. A wrong number would make the application program appear to do nothing.

The SRB_ExecSCSICmd structure accomodates the SCSI2 command description in its members. Furthermore accomodates a "sense area", see below.

The good new with the Exec SCSI2 command ASPI command is that, in case the SCSI2 command fails, a RequestSense SCSI2 command is automatically sent to the target device to retrieve the sense data. So if the returned ASPI status byte is not SS_COMP the programmer automatically finds the sense data into the sense area of SRB_ExecSCSICmd.

Any other SCSI2 command can be sent to any SCSI2 device in a similar fashion.

Thanks Tony for pointing out that the proposed code does reset an individual target and not the whole bus.

Working with SCSI ? This is the book to buy: