Device Driver Entries, PART 3--Mouse/Keyboard Driver

This article was previously published under Q102990
This article has been archived. It is offered "as is" and will no longer be updated.
SUMMARY
The article contains REGISTRY entries for Mouse and Keyboard Drivers. Thereis a second half of this topic, found in the article Device Driver EntriesPart 3.

These subgroups are included:

  • Microsoft Serial Mouse Port Driver
  • Mouse Class Driver
  • Keyboard Class Driver
  • Device Map Entries for the Keyboard and Mouse
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

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 choosingthe Devices button in WinMSD.

Microsoft Serial Mouse Port Driver Entries

The value entries for the Microsoft serial mouse are found in this subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sermouse\ParametersMouseDataQueueSize     REG_DWORD     >= 0x1				
Specifies the number of mouse events to be buffered internally by thedriver, in nonpaged pool. The allocated size, in bytes, of the internalbuffer is this value times the size of the MOUSE_INPUT_DATA structure(defined in NTDDMOU.H). Consider increasing the size if the System log inEvent Viewer contains the following message from the Sermouse source: "Thering buffer that stores incoming mouse data has overflowed (buffer size isconfigurable via the Registry)."Default: 0x64 (100)
NumberOfButtons     REG_DWORD     >= 0x1				
Specifies the number of buttons on the serial mouse. If the number ofbuttons detected at startup time and placed in the Registry is incorrect,this value can be used to override it.Default: 0x2
OverrideHardwareBitstring     REG_DWORD     0x1 or 0x2				
This entry is not usually present. When present, it specifies thatregardless of whether it was actually detected, a serial mouse is presenton the system. Add this value to tell the driver to assume the serial mouseis on COM1 (specified by the value 0x1) or COM2 (specified by the value0x2). This entry is useful if the serial mouse has not been automaticallydetected.
PointerDeviceBaseName     REG_SZ     Base port device name				
Specifies the base name for the device object(s) created by the serialmouse device driver. The device driver also writes information about thedevice objects into HKEY_LOCAL_MACHINE\HARDWARE\DeviceMap so that thepointer class driver can locate the pointer port device objects.Default: PointerPort
SampleRate     REG_DWORD     Mouse sample rate in Hz				
Specifies the sample rate for the serial mouse. Intended for future use.This value might have no effect in the first release of Windows NT.Default: 0x28 (1200 baud)

Mouse Class Driver Entries

The value entries for the mouse class driver are found in this subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mouclass\ParametersConnectMultiplePorts     REG_DWORD     0x0 or 0x1				
Specifies the type of connection between class and port device objects.This parameter is mainly of interest to device driver writers.

The value 0x0 specifies a 1:1 relationship between class device objects andport device objects. (That is, one class device object is created by thedriver and connected to one port device object; the maximum number ofobjects created and connected to an associated port object is determined bythe value of MaximumPortsServiced.) The value 0x1 specifies a 1:manyrelationship between a single class device object and multiple port deviceobjects. (That is, one class device object is created by the driver andthen connected to multiple port device objects, up to a maximum specifiedby MaximumPortsServiced.)Default: 0x1 (The events generated by up to the MaximumPortsServiced numberof pointing devices on the system will all be fed to the Windows subsystemin a single input stream.)
MaximumPortsServiced     REG_DWORD     >= 0x1				
Specifies the number of port devices the mouse class device driver willconnect to and service. The class device driver handles hardware-independent operations on a specific class of devices (in this case, themouse and other pointing devices). The port drivers manage the hardware-specific operations.Default: 0x3 (The class driver will service up to three pointing devices.)
MouseDataQueueSize     REG_DWORD     >= 0x1				
Specifies the number of mouse events to be buffered internally by thedriver, in nonpaged pool. The allocated size, in bytes, of the internalbuffer is this value times the size of the MOUSE_INPUT_DATA structure(defined in NTDDMOU.H). Consider increasing the size if the System log inEvent Viewer frequently contains the following message from the Mouclasssource: "The ring buffer that stores incoming mouse data has overflowed(buffer size is configurable via the Registry)."Default: 0x64 (100)
PointerDeviceBaseName     REG_SZ     Base class device name				
Specifies the base name for the device object(s) created by the mouse classdevice driver. The device driver also writes information about the deviceobject into HKEY_LOCAL_MACHINE\HARDWARE\DeviceMap so that the pointer classdevice object(s) can be easily located.Default: PointerClass

Keyboard Class Driver Entries

The value entries for the keyboard class driver are found in the followingsubkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Kbdclass\ParametersConnectMultiplePorts     REG_DWORD     0x0 or 0x1				
Specifies the type of connection between class and port device objects.This parameter is mainly of interest to device driver writers.

The value 0x0 specifies a 1:1 relationship between class device objects andport device objects. (That is, one class device object is created by thedriver and connected to one port device object; the maximum number ofobjects created and connected to an associated port object is determined bythe value of MaximumPortsServiced.) The value 0x1 specifies a 1:manyrelationship between a single class device object and multiple port deviceobjects (That is, one class device object is created by the driver and thenconnected to multiple port device objects, up to a maximum specified byMaximumPortsServiced.)Default: 0x0 (The events generated by up to the MaximumPortsServiced numberof keyboard devices on the system will feed separate input streams. In thefirst release of Windows NT, the Windows subsystem only reads from a singlekeyboard input stream.)
KeyboardDataQueueSize     REG_DWORD     >= 0x1				
Specifies the number of keyboard events to be buffered internally by thedriver, in nonpaged pool. The allocated size, in bytes, of the internalbuffer is this value times the size of the KEYBOARD_INPUT_DATA structure(defined in NTDDKBD.H). Consider increasing the size if the System log inEvent Viewer contains the following message from the Kbdclass source: "Thering buffer that stores incoming keyboard data has overflowed (buffer sizeis configurable via the Registry)."Default: 0x64 (100)
KeyboardDeviceBaseName     REG_SZ     Base class device name				
Specifies the base name for the keyboard device object(s) created by thekeyboard class device driver. The device driver also writes informationabout the device objects into HKEY_LOCAL_MACHINE\HARDWARE\DeviceMap so thatthe keyboard class device objects are easily located.Default: KeyboardClass
MaximumPortsServiced     REG_DWORD     >= 0x1				
Specifies the number of port devices the keyboard class device driver willconnect to and service. The class device driver handles hardware-independent operations on a specific class of devices (in this case,keyboard devices). The port drivers manage the hardware-specificoperations.Default: 0x3 (The class driver will service up to three keyboard devices.)

DeviceMap Entries for the Keyboard and Mouse The following DeviceMapdescriptions are for informational purposes only, since the DeviceMapsubkeys are volatile and are recreated each time you start Windows NT.Administrators cannot modify DeviceMap entries.

These DeviceMap entries are used by the Windows subsystem to locate thepointer and keyboard class devices, and by the pointer and keyboard classdrivers to locate the associated pointer and keyboard port devices.Information is placed in the DeviceMap subkey by the keyboard and pointerclass and port drivers.

The format for each of these entries is:

Name of class device object : REG_SZ : Registry path to driver's Services

The keyboard class information appears in the Registry path:
HKEY_LOCAL_MACHINE\HARDWARE\DeviceMap\KeyboardClass				
There can be one or more of these entries. Each entry specifies the name ofa device object created by the keyboard class driver to represent the classdevice, followed by the Registry path to the driver's Services subkey.Default:
\Device\KeyboardClass0 : REG_SZ :\Registry\Machine\System\ControlSet001\Services\Kbdclass				
The keyboard port information appears in the Registry path:
HKEY_LOCAL_MACHINE\HARDWARE\DeviceMap\KeyboardPort				
There can be one or more of these entries. Each entry specifies the name ofa device object created by the keyboard port driver(s) to represent thephysical keyboard (port) device, followed by the Registry path to thedriver's Services subkey.Default:
\Device\KeyboardPort0 : REG_SZ :\Registry\Machine\System\ControlSet001\Services\i8042prt				
The mouse class information appears in the Registry path:
HKEY_LOCAL_MACHINE\HARDWARE\DeviceMap\PointerClass				
There can be one or more of these entries. Each entry specifies the name ofa device object created by the pointer (mouse) class driver to representthe class device, followed by the Registry path to the driver's Servicessubkey.Default:
\Device\PointerClass0 : REG_SZ :\Registry\Machine\System\ControlSet001\Services\Mouclass				
The mouse port information appears in the Registry path:
HKEY_LOCAL_MACHINE\HARDWARE\DeviceMap\PointerPort				
There can be one or more of these entries. Each entry specifies the name ofa device object created by the pointer port driver(s) to represent thephysical pointing (port) device, followed by the Registry path to thedriver's Services subkey.Default (assumes mouse port, Microsoft InPort, and serial pointing devicesare connected):

\Device\PointerPort0 : REG_SZ :
     \Registry\Machine\System\ControlSet001\Services\i804				
2prt\Device\PointerPort1 : REG_SZ :
     \Registry\Machine\System\ControlSet001\Services\Inport				
\Device\PointerPort2 : REG_SZ :
     \Registry\Machine\System\ControlSet001\Services\Sermouse				
REFERENCES
Reference: "The Windows NT Resource Kit for Operating System Version 3.1".
prodnt
Properties

Article ID: 102990 - Last Review: 12/04/2015 09:39:01 - Revision: 2.1

Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1

  • kbnosurvey kbarchive kbinfo kbprint KB102990
Feedback