The following registry entries allow you to configure the behavior of the port driver/SCSI miniport driver pair. For information about the PnpInterface registry entry required for all Plug and Play (PnP) devices, see Registry Entries for Plug and Play SCSI Miniport Drivers.
Nov 13, 2008 ScsiPort Miniport Driver is the default LSI Logic SCSI Controller included when Windows Server 2003 SP2 is installed as the Guest OS in ESX Server. The LSI Logic SCSI Controller must be updated with the Storport Miniport Driver for proper SnapDrive operations. Xvdd Scsi Miniport Driver for Windows 7 32 bit, Windows 7 64 bit, Windows 10, 8, XP. Uploaded on 2/21/2019, downloaded 413 times, receiving a 89/100 rating by 150 users.
- TimeoutValue
Location: HKLMSystemCurrentControlSetServicesDiskTimeoutValue
Values: 1 - 255 seconds
Meaning: Time in units of seconds before an SRB request initiated by the disk class driver will time out. If this registry value is not set, a default value of 10 seconds is used. Time-out values for requests that are initiated by class drivers vary according to the class driver.
Note If the miniport sets a value, that timeout will be honored preferentially. The timeout selection logic is as follows:
- Starting in Windows 8, if the miniport sets a timeout value (in HKLM … Services<miniport>ParametersIoTimeoutValue), this value is honored by the storage class driver.
- Otherwise, if the disk global timeout registry (this key) is set, this value is honored by the storage class driver.
- Otherwise, a default value of 10 seconds is used by the storage class driver.
Operating system version: This feature is available in all versions of the Windows operating systems.
- TotalSenseDataBytes
- Location: HKLMSystemCurrentControlSetEnum<Bus>< DeviceID><Device>DeviceParametersScsiPortTotalSenseDataBytes
- Values: Between 18 and 255 for SCSI Port. Storport always uses 255.
- Meaning: If set, this value designates the size in bytes of the buffer that the SCSI Port driver allocates for request sense data. If the value is not set, SCSI port uses a default size of 18. The Storport driver always allows 255. Warning: filter drivers that insert between the class driver and the port driver must respect this value and not attempt to manage the size of the sense data buffer.
- Operating system version: This feature is available in Windows 2000 Server and later operating systems.
- MaximumSGList
- Location: HKLMSystemCurrentControlSetServices<ServiceName>ParametersDeviceMaximumSGList, where <ServiceName> = the miniport driver name specified with the AddServices directive in the INF file.
- Values: Between 16 and 255.
- Meaning: Indicates the number of scatter/gather list elements supported by the adapter.
- Operating system version: This feature is available in Windows NT 4.0 SP4 and later operating systems.
- BusType
- Location: HKLMSystemCurrentControlSetServices<ServiceName>ParametersBusType, where <ServiceName> = the miniport driver name specified with the AddServices directive in the INF file.
- Values: The same as STORAGE_BUS_TYPE enumerator:
- Meaning: Indicates the type of bus that the adapter is connected to.
- Operating system version: This feature is available in Windows 2000 and later operating systems.
- CreateInitiatorLU
- Location: <ServiceName>ParametersDeviceCreateInitiatorLU, where <ServiceName> = the miniport driver name specified with the AddServices directive in the INF file.
- Values: Either 0 or 1.
- Meaning: A value of 1 indicates that the port driver will create an 'initiator logical unit,' so that higher-level drivers can send certain requests to the port driver even though there is no actual hardware device connected to the adapter or the connected device is not visible to the system. Sometimes it is necessary to configure a device's operating parameters or update its firmware before it will be visible to the system. Prior to Windows Server 2003, it was not possible to instruct the port driver to update firmware for a device unless the port driver had at least one logical unit in its device stack. Some vendors attempted to remedy this deficiency by adding so-called 'pseudo-LUNs' to the adapter's stack, but this created problems for setup and disk management, and occasionally such solutions would cause the configuration manager to prompt the user for a driver for a non-existent device. With the new 'initiator logical unit' feature, it is no longer necessary to use these work-around techniques. By setting CreateInitiatorLU to 1 in the registry, you can send IOCTLs and WMI requests to the port driver whether it has devices attached that are visible to the operating system. Another use of the 'initiator logical unit' feature is to allow communication with fibre channel adapters that have a purely administrative function and no attached devices.
- Operating system version: This feature is available in Windows Server 2003 and later operating systems. The value of this registry value only affects the functionality of the SCSI Port miniport drivers. Storport miniport driver always permit access to adapter objects, even when no device is attached to the adapter.
-->Scsi Miniport Driver Windows 7
This section contains the following information:
SCSI miniport drivers for NT-based operating systems are HBA-specific but operating system-independent. That is, each miniport driver links itself with the system-supplied SCSI port driver, which is a dynamic-link library (DLL), and calls only the port driver's ScsiPortXxx routines to communicate with the system and its HBA. Such SCSI miniport drivers run on other Microsoft operating systems that support Microsoft Win32 applications and also export the ScsiPortXxx routines. For more information about the ScsiPortXxx routines, see SCSI Port Library Routines.
Note that any SCSI miniport driver that calls routines other than the ScsiPortXxx cannot run in both Microsoft operating system environments. To remain portable across Microsoft Windows systems, including NT-based operating systems, SCSI miniport drivers must call only the system-supplied ScsiPortXxx.
Wan Miniport Driver Update
A SCSI miniport driver can be a Plug and Play driver, or it can run as a legacy driver that does not participate in Plug and Play operations such as resource redistribution or power management. The primary differences between a Plug and Play and a legacy miniport driver are the order in which initialization routines are called and enforcement of certain restrictions that were applied to miniport drivers in Microsoft Windows NT 4.0, but not enforced.