Drivers Contex A/s SCSI & RAID Devices



Belcarra network login. If the per-target scsi-options property is defined, the HBA driver uses that value rather than the per-HBA driver instance scsi-options property. This approach can provide more precise control if, for example, synchronous data transfer needs to be disabled for just one particular target device.

-->

The ScsiPortWmiSetInstanceCount specifies the number of instances for which data buffers must be set aside within the WNODE_ALL_DATA structure in the request context.

Note The SCSI port driver and SCSI miniport driver models may be altered or unavailable in the future. Instead, we recommend using the Storport driver and Storport miniport driver models.

Syntax

Drivers/scsi/scsi.c¶ Main file for the SCSI midlayer. Int scsichangequeuedepth (struct scsidevice.sdev, int depth) ¶ change a device’s queue depth. Struct scsidevice.sdev SCSI Device in question int depth number of commands allowed to be queued to the driver. Sets the device queue depth and returns the new value. Find Contex technical support for your Contex scanners and software here or contact your reseller for direct help. Use the drop down box to reach your products support page and access relevant downloads, drivers. Insert the USB flash drive which contains the driver setup files for your hard disk. On the main window of PCUnlocker, click the Options button and select Load IDE/SCSI/SATA/RAID Driver from the drop-down menu. When the file open dialog appears, select the Driver.

Parameters

RequestContext

[in]Pointer to a structure of type SCSIWMI_REQUEST_CONTEXT that contains the request context for a WMI SRB.

InstanceCount

[in]Contains the number of instances for which the minidriver will provide data.

BufferAvail

[out]Contains, on return, the number of bytes of buffer space available for describing instance names and data. The value that is returned in this member can be passed to routines ScsiPortWmiSetData and ScsiPortWmiSetInstanceName in the BufferAvail parameter of those routines.

The ScsiPortWmiSetInstanceCount routine initializes an array of pointers to data buffers, with one array element for each instance. If there is not enough memory available in the WNODE to initialize an array of size InstanceCount, a zero will be returned in this member.

SizeNeeded

[out]Indicates, on input, the number of bytes needed to describe the entire WNODE before configuring the internal arrays in the WNODE. On return, this member will contain the size of the entire WNODE, including the newly initialized arrays within the WNODE.

Scsi Device Driver

Return value

The ScsiPortWmiSetInstanceCount routine returns TRUE if the operation succeeds and FALSE if the WNODE contained within the request context is not of type WNODE_ALL_DATA.

Drivers Contex A/s SCSI & RAID Devices

Remarks

The minidriver must call ScsiPortWmiSetInstanceCount before calling either ScsiPortWmiSetData or ScsiPortWmiSetInstanceName. The minidriver should only call ScsiPortWmiSetInstanceCount once.

Scsi

The parameter RequestContext points to a request context structure, SCSIWMI_REQUEST_CONTEXT, that contains information associated with a Windows Management Instrumentation (WMI) SCSI request block (SRB). The request context structure, in turn, contains one of the WMI WNODE_XXX Structures used by the WMI system to pass data between user-mode data consumers and kernel-mode data providers such as drivers.

The ScsiPortWmiSetInstanceCount routine requires the WNODE structure that is defined within the request context to be of type WNODE_ALL_DATA. This is because ScsiPortWmiSetInstanceCount sets aside a data area that will hold information for multiple instances associated with a WMI data block. Unlike the WNODE_SINGLE_INSTANCE structure which contains information about a single instance, the WNODE_ALL_DATA structure contains an array of pointers to buffer areas for different instances, and ScsiPortWmiSetInstanceCount initializes this array, so that each buffer of instance data can be accessed individually using an instance index.

The memory allocated for the request context must remain valid until after the miniport driver calls ScsiPortWmiPostProcess, and ScsiPortWmiPostProcess returns the final SRB status and buffer size. If the SRB can pend, the memory for the request context should be allocated from the SRB extension. If the SRB cannot pend, the memory can be allocated from a stack frame that does not go out of scope.

Microsoft Scsi Driver

Requirements

Drivers Contex A/s SCSI & RAID Devices

What Is Scsi Scanner Device

Target PlatformDesktop
Headerscsiwmi.h (include Miniport.h, Scsi.h)

Drivers Contex A/s Scsi & Raid Devices -

See also