Hello ,
I have a specific question with null.sys and storport driver.
We have a emulex FC card which connects to a FC based MSL tape library. The
tape library has HP’s NSE1200-160 FC router which converts the FC
packets to SCSI and passes to library and drives.
The .inf file provided by HP for this FC router states that no driver
is required for this device but still to avoid the detection of the
driver everytime windows boots up null.sys will be the driver for this
device and this device is installed as a system device.
OS : windows 2003 enterprise sp1
HBA : emulex FC HBA with storport compatible drivers
When our software send a TUR (or any SCSI command) to this FC router using
DeviceIOControl
and SCSI pass through, the response does not come back at all.
When I modified the .inf file and removed the association between the
device and null.sys so that the device manager shows that “No driver is
needed or installed for this device”.
With this configuration the Test Unit Ready command sent to the FC router
succeeds
and DeviceIOControl returns.
The SCSIport driver worked well even with null.sys
I would like to know
-
When I remove the association between null.sys and the device why
does TUR succeed and why it fails with the null.sys and why does it
succeed with scsiport driver. -
Is this expected behaviour with storport?
Thanks.
Regards,
Mandar Nanivadekar,
HP Storage Labs