Hunteromg344

• Drivers Comat Input Devices Download
• Output Devices
• Drivers Comat Input Devices Input

The function driver uses the class service callback to transfer input data from a device to the class data queue for the device. The function driver's ISR dispatch completion routine for a device calls the class service callback. Jul 05, 2017 Unknown devices show up in the Windows Device Manager when Windows can’t identify a piece of hardware and provide a driver for it. An unknown device isn’t just unknown — it’s not functioning until you install the right driver. Windows can identify most devices and download drivers for them automatically. When I click 'update driver' it says that Windows could not find drivers for my device. Under 'Sound, video, and game', it says that my Intel (R) Display Audio is working properly. Under 'System devices' it says this: Other forums said that if I uninstalled the driver and then restarted my computer that the audio would be fixed when it rebooted.

Popular Manufacturers

If the device-specific driver is distributed through Windows Update, you can manually update the driver by using Device Manager. For more information about how to do this, see update drivers in Windows 10. If the device is not yet connected, first install the device-specific driver, such as by using the appropriate installer. Manually install the drivers on Windows. If the drivers came in a.zip file, you'll need to install them manually. You can do this from the Device Manager: Select the hardware item you want to update in Device Manager. Click Update driver. Click Browse my computer for driver software when prompted.

Latest Drivers in Input Devices

• Intel Wireless Bluetooth is recommended for end users, including home users and business customers with Intel Wireless Bluetooth technology.

  • January 13, 2021
  • Windows 7/8/10
  • 13 MB
• The latest Realtek Card Reader Controller Driver for the RTS5101, RTS5111, RTS5116, and RTS5169 chips.

  • August 12, 2020
  • Windows (all)
  • 17.3 MB
• GoPro has now made it easier than ever to repurpose its latest action camera as a high-definition webcam.

  • July 9, 2020
  • Mac OS X
  • 70.3 MB
• The Xbox 360 console software is updated periodically with new features, download the latest firmware to take advantage of them.

  • May 17, 2020
  • Mac OS X
  • 1.3 MB
• Official Realtek Card Reader Driver for RTS5101/RTS5111/RTS5116/RTS5169.

  • March 20, 2019
  • Windows (all)
  • 12.6 MB
• SteelSeries Engine 3 gives you everything you need in one single app. A unified platform that supports nearly all your SteelSeries gear.

  • March 11, 2019
  • Windows (all)
  • 125 MB
• The Synaptics Gesture Suite device driver is now equipped with Scrybe Gesture Workflow Technology – the next generation in TouchPad-based PC interfaces.

  • March 1, 2011
  • Windows XP/Vista/7
  • 50.9 MB
• Logitech SetPoint Software lets you customize your mouse buttons, keyboard F-keys and hot-keys, control tracking speed, and configure other device-specific settings.

  • September 14, 2018
  • Windows (all)
  • 82.6 MB
• • March 6, 2012
  • Windows 7 64-bit
  • 87.7 MB
• ASRock XFast USB instantly accelerates the performance of USB devices on ASRock branded motherboards.

  • September 4, 2017
  • Windows (all)
  • 4.6 MB
• You can download the Intel USB 3.0 driver for Windows 7 right here. If you need this driver for Windows XP, Vista or Windows 8 please read the notes below.

  • May 6, 2017
  • Windows 7 / 8
  • 5.4 MB
• Logitech webcam software is an upgrade from the QuickCam software and drivers that came with your webcam.

  • January 16, 2017
  • Windows (all)
  • 71.1 MB
• Every peripheral. Every macro. Every preference, profile and Razer add-on. All ready to go, all the time, from anywhere.

  • December 15, 2016
  • Windows (all)
  • 12.3 MB
• With a wave of a hand or lift of a finger, you’re about to use your computer in a whole new way. The Leap Motion Controller senses how you move your hands the way you naturally move them.

  • December 13, 2016
  • Windows (all)
  • 114 MB
• This driver supports SD, SD High Capacity (HC), MMC, MS and MS pro serial cards for the VIA VX800, VX855, VX900, and VX11 chipsets built in MSP PCI card reader.

  • September 19, 2016
  • Windows Vista / 7 / 8
  • 14.0 MB
• Download Mouse and Keyboard Center to get the most out of Windows.

  • August 19, 2016
  • Windows 8 64-bit
  • 42.0 MB
• Download Mouse and Keyboard Center to get the most out of Windows.

  • August 19, 2016
  • Windows (all)
  • 40.3 MB
• • August 15, 2016
  • Windows 2000/XP
  • 6.2 MB
• The Realtek camera controllers are designed for notebook and desktop PCs. This driver offer support for Windows 10 64-bit and 32-bit.

  • August 8, 2016
  • Windows 10
  • 5.1 MB
• Operating system support: Windows (all).

  • June 29, 2016
  • Windows (all)
  • 19.6 MB
• • June 28, 2016
  • Windows 10
  • 795 KB
• Capture photos and videos, upload to Facebook with one-click, adjust camera settings, and more.

  • June 16, 2016
  • Windows (all)
  • 71.1 MB
• SteelSeries Engine 2 gives you everything you need in one single app. This version works with older SteelSeries products.

  • May 2, 2016
  • Mac OS X
  • 117 MB
• SteelSeries Engine 2 gives you everything you need in one single app. This version works with older SteelSeries products.

  • May 2, 2016
  • Windows (all)
  • 50.5 MB
• Killer Wireless-AC high-performance networking adapters combine intelligence, control and superior wireless networking speed for online games, HD video, and high quality audio.

  • November 30, 2015
  • Windows 10
  • 53.9 MB
• WHQL Driver for VL800/801 & 805/806 USB 3.0 Host Controller. Compatible with Windows XP/Vista/7/8 32-bit and 64-bit.

  • February 4, 2013
  • Windows Vista / 7 / 8
  • 66.6 MB
• VIA USB 3.

  • September 28, 2015
  • Windows Vista / 7 / 8
  • 11.6 MB
• This update improves FaceTime camera compatibility with Windows, and is recommended for all Boot Camp users.

  • August 4, 2015
  • Windows (all)
  • 1.4 MB
• Download here the latest Windows 10 to Windows 2000 Realtek RTS5101/RTS5111/RTS5116/RTS5169 Card Reader Driver.

  • July 23, 2015
  • Windows (all)
  • 13.6 MB
• Find all the latest ElanTech touchpad drivers here, from the generic driver to Asus and Lenovo versions.

  • July 13, 2015
  • Windows XP/Vista/7
  • 10.3 MB
• This package installs the software (Elan Touchpad driver) to enable the Elan pointing device on Lenovo notebooks.

  • April 1, 2015
  • Windows 8 64-bit
  • 150 MB
• This file updates the firmware for the Thunderbolt Display to version 1.2.

  • November 14, 2014
  • Mac OS X
  • 1.7 MB
• The Synaptics Gesture Suite device driver is now equipped with Scrybe gesture workflow technology – the next generation in TouchPad-based PC interfaces.

  • November 11, 2014
  • Windows (all)
  • 120 MB
• This new firmware for the TRENDnet TV-IP743SIC 1.0R Baby Cam improves WPS compatibility and updates the Active X plug-in for Windows.

  • October 14, 2014
  • Windows (all)
  • 14.1 MB
• Operating system support: Windows 2000/XP.

  • September 17, 2014
  • Windows 2000/XP
  • 2.5 MB
• This driver works on any computer with either a Broadcom-enabled embedded or USB plug-in Bluetooth wireless adapter.

  • September 16, 2014
  • Windows XP/Vista/7
  • 4.0 MB
• • June 5, 2014
  • Windows 7 / 8 64-bit
  • 2.7 MB
• • June 5, 2014
  • Windows 7 / 8
  • 2.3 MB
• • April 28, 2014
  • Mac OS X
  • 40.8 MB
• • April 28, 2014
  • Windows (all)
  • 30.4 MB
• • July 17, 2013
  • Mac OS X
  • 120.1 MB
• • April 17, 2014
  • Windows Vista / 7 / 8
  • 30.4 MB
• Operating system support: Windows Vista / 7 / 8.

  • April 17, 2014
  • Windows Vista / 7 / 8
  • 29.2 MB
• Operating system support: Windows Vista / 7 / 8.

  • April 4, 2014
  • Windows Vista / 7 / 8
  • 51.6 MB
• • August 23, 2011
  • Windows XP/Vista/7
  • 18.9 MB
• Developed for World of Warcraft players by SteelSeries and Blizzard Entertainment, the World of Warcraft: Cataclysm MMO Gaming Mouse invokes the iconic imagery of Deathwing the Destroyer, leader of the black dragonflight and instigator of the Cataclysm.

  • August 19, 2014
  • Mac OS X
  • 9.5 MB
• • August 23, 2011
  • Windows XP/Vista/7
  • 28.1 MB
• • October 3, 2011
  • Windows XP/Vista/7
  • 27.7 MB
• • August 19, 2011
  • Mac OS X
  • 10.4 MB
• Operating system support: Windows Vista / 7 64-bit.

  • February 22, 2011
  • Windows Vista / 7 64-bit
  • 54.6 MB

Note

This topic is for developers who are creating drivers for keyboard and mouse HID clients. If you are looking to fix a mouse or keyboard, see:

This topic discusses keyboard and mouse HID client drivers. Keyboards and mice represent the first set of HID clients that were standardized in the HID Usage tables and implemented in Windows operating systems.

Keyboard and mouse HID client drivers are implemented in the form of HID Mapper Drivers. A HID mapper driver is a kernel-mode WDM filter driver that provides a bidirectional interface for I/O requests between a non-HID Class driver and the HID class driver. The mapper driver maps the I/O requests and data protocols of one to the other.

Windows provides system-supplied HID mapper drivers for HID keyboard, and HID mice devices.

Architecture and overview

The following figure illustrates the system-supplied driver stacks for USB keyboard and mouse/touchpad devices.

The figure above includes the following components:

• KBDHID.sys – HID client mapper driver for keyboards. Converts HID usages into scancodes to interface with the existing keyboard class driver.
• MOUHID.sys – HID client mapper driver for mice/touchpads. Converts HID usages into mouse commands (X/Y, buttons, wheel) to interface with the existing keyboard class driver.
• KBDCLASS.sys – The keyboard class driver maintains functionality for all keyboards and keypads on the system in a secure manner.
• MOUCLASS.sys – The mouse class driver maintains functionality for all mice / touchpads on the system. The driver does support both absolute and relative pointing devices. This is not the driver for touchscreens as that is managed by a different driver in Windows.
• HIDCLASS.sys - The HID class driver. The HID Class driver is the glue between KBDHID.sys and MOUHID.sys HID clients and various transports (USB, Bluetooth, etc).

The system builds the driver stack as follows:

• The transport stack creates a physical device object (PDO) for each HID device attached and loads the appropriate HID transport driver which in turn loads the HID Class Driver.
• The HID class driver creates a PDO for each keyboard or mouse TLC. Complex HID devices (more than 1 TLC) are exposed as multiple PDOs created by HID class driver. For example, a keyboard with an integrated mouse might have one collection for the standard keyboard controls and a different collection for the mouse.
• The keyboard or mouse hid client mapper drivers are loaded on the appropriate FDO.
• The HID mapper drivers create FDOs for keyboard and mouse, and load the class drivers.

Important notes:

• Vendor drivers are not required for keyboards and mice that are compliant with the supported HID Usages and top level collections.
• Vendors may optionally provide filter drivers in the HID stack to alter/enhance the functionality of these specific TLC.
• Vendors should create separate TLCs, that are vendor specific, to exchange vendor proprietary data between their hid client and the device. Avoid using filter drivers unless critical.
• The system opens all keyboard and mouse collections for its exclusive use.
• The system prevents disable/enabling a keyboard.
• The system provides support for horizontal/vertical wheels with smooth scrolling capabilities.

Driver Guidance

Microsoft provides the following guidance for IHVs writing drivers:

1. Driver developers are allowed to add additional drivers in the form of a filter driver or a new HID Client driver. The criteria are described below:

   1. Filters Drivers: Driver developers should ensure that their value-add driver is a filter driver and does not replace (or be used in place of) existing Windows HID drivers in the input stack.

      • Filter drivers are allowed in the following scenarios:
        • As an upper filter to kbdhid/mouhid
        • As an upper filter to kbdclass/mouclass
      • Filter drivers are not recommended as a filter between HIDCLASS and HID Transport minidriver

   2. Function Drivers: Alternatively vendors can create a function driver (instead of a filter driver) but only for vendor specific HID PDOs (with a user mode service if necessary).

      Function drivers are allowed in the following scenarios:

      • Only load on the specific vendor’s hardware

   3. Transport Drivers: Windows team does not recommend creating additional HID Transport minidriver as they are complex drivers to write/maintain. If a partner is creating a new HID Transport minidriver, especially on SoC systems, we recommend a detailed architectural review to understand the reasoning and ensure that the driver is developed correctly.

2. Driver developers should leverage driver Frameworks (KMDF or UMDF) and not rely on WDM for their filter drivers.

3. Driver developers should reduce the number of kernel-user transitions between their service and the driver stack.

4. Driver developers should ensure ability to wake the system via both keyboard and touchpad functionality (adjustable by the end user (device manager) or the PC manufacturer). In addition on SoC systems, these devices must be able to wake themselves from a lower powered state while the system is in a working S0 state.

5. Driver developers should ensure that their hardware is power managed efficiently.

   • Device can go into its lowest power state when the device is idle.
   • Device is in the lowest power state when the system is in a low power state (for example, standby (S3) or connected standby).

Keyboard layout

A keyboard layout fully describes a keyboard's input characteristics for Microsoft Windows 2000 and later versions. For example, a keyboard layout specifies the language, keyboard type and version, modifiers, scan codes, and so on.

See the following for information about keyboard layouts:

• Keyboard header file, kdb.h, in the Windows Driver Development Kit (DDK), which documents general information about keyboard layouts.

• Sample keyboard layouts.

To visualize the layout of a specific keyboard, see Windows Keyboard Layouts.

For additional details around the keyboard layout, visit Control PanelClock, Language, and RegionLanguage.

Supported buttons and wheels on mice

The following table identifies the features supported across different client versions of the Windows operating system.

Activating buttons 4-5 and wheel on PS/2 mice

The method used by Windows to activate the new 4&5-button + wheel mode is an extension of the method used to activate the third button and the wheel in IntelliMouse-compatible mice:

• First, the mouse is set to the 3-button wheel mode, which is accomplished by setting the report rate consecutively to 200 reports/second, then to 100 reports/second, then to 80 reports/second, and then reading the ID from the mouse. The mouse should report an ID of 3 when this sequence is completed.
• Next, the mouse is set to the 5-button wheel mode, which is accomplished by setting the report rate consecutively to 200 reports/second, then to 200 reports/second again, then to 80 reports/second, and then reading the ID from the mouse. Once this sequence is completed, a 5-button wheel mouse should report an ID of 4 (whereas an IntelliMouse-compatible 3-button wheel mouse would still report an ID of 3).

Note that this is applicable to PS/2 mice only and is not applicable to HID mice (HID mice must report accurate usages in their report descriptor).

Standard PS/2-compatible mouse data packet format (2 Buttons)

Note

Windows mouse drivers do not check the overflow bits. In case of overflow, the mouse should simply send the maximal signed displacement value.

Standard PS/2-compatible mouse data packet format (3 Buttons + VerticalWheel)

Standard PS/2-compatible mouse data packet format (5 Buttons + VerticalWheel)

Important

Notice that the Z/wheel data for a 5-button wheel mouse has been reduced to four bits instead of the 8 bits used in the IntelliMouse-compatible 3-button wheel mode. This reduction is made possible by the fact that the wheel typically cannot generate values beyond the range +7/-8 during any given interrupt period. Windows mouse drivers will sign extend the four Z/wheel data bits when the mouse is in the 5-button wheel mode, and the full Z/wheel data byte when the mouse operates in the 3-button wheel mode.

Buttons 4 & 5 on are mapped to WM_APPCOMMAND messages and correspond to App_Back and App_Forward.

Drivers Comat Input Devices Download

Devices not requiring vendor drivers

Vendor drivers are not required for the following devices:

• Devices that comply with the HID Standard.
• Keyboard, mouse, or game port devices operated by the system-supplied non-HIDClass drivers.

Kbfiltr sample

Kbfiltr is designed to be used with Kbdclass, the system class driver for keyboard devices and I8042prt, the function driver for a PS/2-style keyboard. Kbfiltr demonstrates how to filter I/O requests and how to add callback routines that modify the operation of Kbdclass and I8042prt.

For more information about Kbfiltr operation, see the following:

• The ntddkbd.h WDK header file.

• The sample Kbfiltr source code.

Kbfiltr IOCTLs

IOCTL_INTERNAL_I8042_HOOK_KEYBOARD

The IOCTL_INTERNAL_I8042_HOOK_KEYBOARD request does the following:

• Adds an initialization callback routine to the I8042prt keyboard initialization routine.
• Adds an ISR callback routine to the I8042prt keyboard ISR.

The initialization and ISR callbacks are optional and are provided by an upper-level filter driver for a PS/2-style keyboard device.

After I8042prt receives an IOCTL_INTERNAL_KEYBOARD_CONNECT request, it sends a synchronous IOCTL_INTERNAL_I8042_HOOK_KEYBOARD request to the top of the keyboard device stack.

After Kbfiltr receives the hook keyboard request, Kbfiltr filters the request in the following way:

• Saves the upper-level information passed to Kbfiltr, which includes the context of an upper-level device object, a pointer to an initialization callback, and a pointer to an ISR callback.
• Replaces the upper-level information with its own.
• Saves the context of I8042prt and pointers to callbacks that the Kbfiltr ISR callback can use.

IOCTL_INTERNAL_KEYBOARD_CONNECT

The IOCTL_INTERNAL_KEYBOARD_CONNECT request connects the Kbdclass service to the keyboard device. Kbdclass sends this request down the keyboard device stack before it opens the keyboard device.

After Kbfiltr received the keyboard connect request, Kbfiltr filters the connect request in the following way:

• Saves a copy of Kbdclass's CONNECT_DATA (Kbdclass) structure that is passed to the filter driver by Kbdclass.
• Substitutes its own connect information for the class driver connect information.
• Sends the IOCTL_INTERNAL_KEYBOARD_CONNECT request down the device stack.

If the request is not successful, Kbfiltr completes the request with an appropriate error status.

Kbfiltr provides a template for a filter service callback routine that can supplement the operation of KeyboardClassServiceCallback, the Kbdclass class service callback routine. The filter service callback can filter the input data that is transferred from the device input buffer to the class data queue.

IOCTL_INTERNAL_KEYBOARD_DISCONNECT

The IOCTL_INTERNAL_KEYBOARD_DISCONNECT request is completed with a status of STATUS_NOT_IMPLEMENTED. Note that a Plug and Play keyboard can be added or removed by the Plug and Play manager.

For all other device control requests, Kbfiltr skips the current IRP stack and sends the request down the device stack without further processing.

Callback routines implemented by Kbfiltr

KbFilter_InitializationRoutine

See PI8042_KEYBOARD_INITIALIZATION_ROUTINE

The KbFilter_InitializationRoutine is not needed if the I8042prt default initialization of a keyboard is sufficient.

I8042prt calls KbFilter_InitializationRoutine when it initializes the keyboard. Default keyboard initialization includes the following operations:

• reset the keyboard
• set the typematic rate and delay
• set the light-emitting diodes (LED)

KbFilter_IsrHook

See PI8042_KEYBOARD_ISR. This callback is not needed if the default operation of I8042prt is sufficient.

The I8042prt keyboard ISR calls KbFilter_IsrHook after it validates the interrupt and reads the scan code.

KbFilter_IsrHook runs in kernel mode at the IRQL of the I8042prt keyboard.

KbFilter_ServiceCallback

See PSERVICE_CALLBACK_ROUTINE.

Output Devices

The ISR dispatch completion routine of the function driver calls KbFilter_ServiceCallback, which then calls the keyboard class driver's implementation of PSERVICE_CALLBACK_ROUTINE. A vendor can implement a filter service callback to modify the input data that is transferred from the device's input buffer to the class data queue. For example, the callback can delete, transform, or insert data.

Moufiltr sample

Moufiltr is designed to be used with Mouclass, the system class driver for mouse devices used with Windows 2000 and later versions, and I8042prt, the function driver for a PS/2-style mouse used with Windows 2000 and later. Moufiltr demonstrates how to filter I/O requests and add callback routines that modify the operation of Mouclass and I8042prt.

For more information about Moufiltr operation, see the following:

• The ntddmou.h WDK header file.

• The sample Moufiltr source code.

Moufiltr control codes

IOCTL_INTERNAL_I8042_HOOK_MOUSE

The IOCTL_INTERNAL_I8042_HOOK_MOUSE request adds an ISR callback routine to the I8042prt mouse ISR. The ISR callback is optional and is provided by an upper-level mouse filter driver.

I8042prt sends this request after it receives an IOCTL_INTERNAL_MOUSE_CONNECT request. I8042prt sends a synchronous IOCTL_INTERNAL_I8042_HOOK_MOUSE request to the top of the mouse device stack.

After Moufiltr receives the hook mouse request, it filters the request in the following way:

• Saves the upper-level information passed to Moufiltr, which includes the context of an upper-level device object and a pointer to an ISR callback.
• Replaces the upper-level information with its own.
• Saves the context of I8042prt and pointers to callbacks that the Moufiltr ISR callbacks can use.

Moufiltr Callback Routines

IOCTL_INTERNAL_MOUSE_CONNECT

The IOCTL_INTERNAL_MOUSE_CONNECT request connects Mouclass service to a mouse device.

IOCTL_INTERNAL_MOUSE_DISCONNECT

The IOCTL_INTERNAL_MOUSE_DISCONNECT request is completed by Moufiltr with an error status of STATUS_NOT_IMPLEMENTED.

For all other requests, Moufiltr skips the current IRP stack and sends the request down the device stack without further processing.

Callback routines

MouFilter_IsrHook

See PI8042_MOUSE_ISR.

A MouFilter_IsrHook callback is not needed if the default operation of I8042prt is sufficient.

The I8042prt mouse ISR calls MouFilter_IsrHook after it validates the interrupt.

To reset a mouse, I8042prt goes through a sequence of operational substates, each one of which is identified by an MOUSE_RESET_SUBSTATE enumeration value. For more information about how I8042prt resets a mouse and the corresponding mouse reset substates, see the documentation of MOUSE_RESET_SUBSTATE in ntdd8042.h.

MouFilter_IsrHook runs in kernel mode at the IRQL of the I8042prt mouse ISR.

MouFilter_ServiceCallback

See PSERVICE_CALLBACK_ROUTINE

Drivers Comat Input Devices Input

The ISR DPC of I8042prt calls MouFilter_ServiceCallback, which then calls MouseClassServiceCallback. A filter service callback can be configured to modify the input data that is transferred from the device's input buffer to the class data queue. For example, the callback can delete, transform, or insert data.