REG: Device Driver Entries, PART 4

Last reviewed: May 8, 1997
Article ID: Q102991
The information in this article applies to:
  • Windows NT operating system version 3.1
  • Windows NT Advanced Server version 3.1

The article contains REGISTRY entries for SCSI Miniport Drivers.

There are 5 parts to the Device Driver Entries article series:

Part 1: Device Driver Entries, containing:

  • File System Drivers and Recognizers
  • Disk, Serial and Parallel Ports

Part 2: Mouse and Keyboard Entries, containing:
  • Microsoft Bus Mouse Port Driver
  • Intel 8042 Port Driver
  • Microsoft InPort Bus Mouse Port Driver

Part 3: Mouse and Keyboard Entries, cont'd, containing:
  • Microsoft Serial Mouse Port Driver
  • Mouse Class Driver
  • Keyboard Class Driver
  • Device Map Entries for the Keyboard and Mouse

Part 4: SCSI Miniport Entries

Part 5: Sound Card and Video Device Driver Entries

NOTE: You can view current settings for these device drivers by choosing the Devices button in WinMSD.

SCSI Miniport Driver Entries

The basic SCSI miniport driver entries in the Registry are found under subkeys in the following path:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services

Each subkey’s name is the same as the driver’s filename minus the .SYS filename extension; for example, FD8XX, which is the entry for all Future Domain 800-series SCSI adapter. The Registry includes entries for at least the following SCSI miniport device drivers:

Driver      Description
name

Ahaxxx      Adaptec 154x and 174x SCSI adapters
DptScsi     DPT SCSI adapter
Fd16_700,   Future Domain MCS 600/MCS 700, TMC-
 Fd7000ex,  7000ex, and 800-series SCSI adapters
 Fd8xx
Ncr53c9x,   NCR SCSI controller and adapters
 Ncrc700,
 Ncrc710
Oliscsi     Olivetti SCSI adapter
Sparrow     SCSI adapter
Spock       SCSI adapter
T128        Trantor SCSI adapters
 and T13B
Ultraxxx    UltraStor 124, 14f, and 24f  SCSI adapter
Wd33c93     Maynard SCSI adapter

The contents of a SCSI miniport subkey are standard for all SCSI miniport drivers, with these basic value entries:

Value entry    Value

ErrorControl   0x01-which is the preferred value for
               ErrorControl. With a value of 0x01,
               the startup process continues if the
               SCSI miniport driver fails to initialize.
Group          SCSI Miniport.
Start          0x00 (Auto Start).
Tag            Optional (determines the load order of
               SCSI miniport drivers).
Type           0x01 (device driver).


For each SCSI miniport key, there can be one or more subkeys named Parameters\Device or Parameters\DeviceN, where N = 0, 1, 2, and so on. The value of N corresponds to the SCSI host adapter number. If the subkey name is Device, the value is globally defined. If the subkey name is DeviceN, the value only pertains to the particular SCSI host adapter.

The SCSI miniport driver recognizes several optional value entries that can be defined under these subkeys, as described in this section.

InitiatorTargetId     REG_DWORD     Number
Sets the SCSI bus host adapter ID. It is used by host adapters that can set the initiator ID from software. Default: Uninitialized

MaximumLogicalUnit     REG_DWORD     Number
Controls the number of logical units per target controller that are scanned for by the SCSI miniport driver. Most devices only support one logical unit, and some devices may fail if more than one logical unit is scanned for. Default: 8

ScsiDebug     REG_DWORD     Number
This value is used to set the value of the ScsiDebug variable, which controls the verbosity of DebugPrint, with 0 being the least verbose. This is used for debugging. Default: 0

The following value entries are used to fix problems such as device time- outs or controller detection errors but will reduce I/O performance. These value entries can be abbreviated. For example, a value entry of Disable will cause DisableSynchronousTransfers, DisableTaggedQueuing, DisableDisconnects, and DisableMultipleRequests to be set.

NOTE: The system must be restarted before these options take effect.

BreakPointOnEntry     REG_DWORD     0 or 1
A DbgBreakPoint() call is immediately made inside of SpParseDevice. This is used for debugging. Default: 0 (disabled)

DisableDisconnects     REG_DWORD     0 or 1
Disables disconnects on the SCSI bus. It causes all requests to be executed sequentially. Default: 1 (enabled)

DisableMultipleRequests     REG_DWORD     0 or 1
Prevents the SCSI miniport driver from sending more than one request at a time per SCSI device. Default: 1 (enabled)

DisableSynchronousTransfers     REG_DWORD     0 or 1
Disables synchronous data transfers on the SCSI bus. Default: 1 (enabled)

DisableTaggedQueuing     REG_DWORD     0 or 1
Disables SCSI-II tagged command queuing on the host adapter. Default: 1 (enabled)

DriverParameter     Data type is specific to driver     A
string

A pointer to this data is passed to the SCSI miniport driver in a miniportFindAdapter routine. It is the fourth parameter, ArgumentString. A miniport driver uses this data to define the IRQ number for the SCSI host adapter, but other applications for the data are possible.

The data type for this value is defined by the specific SCSI miniport driver developer. If the data type is REG_SZ, the Unicode string is converted to an ANSI string before transferring it to the SCSI miniport driver.

These drivers currently use the DriverParameter value entry:

Driver    Values    Meaning

Wd33c93   IRQ=xx;    xx is the IRQ the card should use.
          DMA=yy     Valid values are: 3, 4, 5, 10, 11,
                     12, and 15. The default is 10. yy is
                     the DMA channel the card should use.
                     Valid values are: 5, 6, and 7. The
                     default is 6.
Aha154x BusOnTime=xx xx is the bus on time in microseconds
                     for the card. Valid values are 2-15.
                     The default is 7. The value is usually
                     adjusted downward when DMA transfers
                     from the Adaptec card are interfering
                     with other DMA transfers.
FD8XX      IRQ=xx    xx is the IRQ the card should use.
                     Valid values are 0, 3, 4, 5, 10, 11,
                     12, 14, 15. This value should match
                     the jumper settings on the card.
                     Numbers 0, 3, and 5 are for the short
                     cards (850, 845); the rest are for the
                     885 card only. A value of 0 indicates
                     the card should not use any interrupts
                     and will poll. The default is 5.
T128       IRQ=xx    xx is the IRQ the card should use.
                     Valid values are: 0, 3, 5, 7 , 10,
                     12, 14, and 15. This value should
                     match the jumper settings on the card.
                     Numbers greater than 7 are for the
                     T128F card only. A value of 0 indicates
                     the card should not use any interrupts
                     and will poll. The default is 5.
T13B       IRQ=xx    xx is the IRQ the card should use.
                     Valid values are 0, 3, 5, and 7. This
                     value should match the jumper settings
                     on the card. A value of 0 indicates
                     the card should not use any interrupts
                     and will poll. The default is 5.
TMV1       IRQ=xx    xx is the IRQ the card should use.
                     Valid values are: 2, 3, 4, 5, 6, 7,
                     10, 11, 12, and 15. The default is 10.


Resource List     REG_FULL_DESOURCE_DESCRIPTOR
This parameter is passed to the miniport in the PORT_CONFIGURATION_INFORMATION data structure. This parameter may be used to initialize memory, ports, interrupts, and the DMA channel.

Reference: "The Windows NT Resource Kit for Operating System Version 3.1".


Additional query words: prodnt
Keywords : kbother ntregistry
Version : 3.1
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.