-->
Support and resources for Inseego’s products and services including documentation, manuals, user guides, firmware, software, and other files can be found here. Contact Inseego support for questions. Go to the official site of the manufacturer Type the name and model of your device in the search box. Select your device and click the Support tab/button. You will get the download link for the specific USB Drivers for your device.
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:
Download actiontec motherboards driver win 7. 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:
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
- Filter drivers are allowed in the following scenarios:
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
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.
Driver developers should leverage driver Frameworks (KMDF or UMDF) and not rely on WDM for their filter drivers.
Driver developers should reduce the number of kernel-user transitions between their service and the driver stack.
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.
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.
| Feature | Windows XP | Windows Vista | Windows 7 | Windows 8 and later |
|---|---|---|---|---|
| Buttons 1-5 | Supported (P/2 & HID) | Supported (PS/2 & HID) | Supported (PS/2 & HID) | Supported (PS/2 & HID) |
| Vertical Scroll Wheel | Supported (PS/2 & HID) | Supported (PS/2 & HID) | Supported (PS/2 & HID) | Supported (PS/2 & HID) |
| Horizontal Scroll Wheel | Not Supported | Supported(HID only) | Supported(HID only) | Supported(HID only) |
| Smooth Scroll Wheel Support (Horizontal and Vertical) | Not Supported | Partly Supported | Supported (HID only) | Supported (HID only) |
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)
| Byte | D7 | D6 | D5 | D4 | D3 | D2 | D1 | D0 | Comment |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Yover | Xover | Ysign | Xsign | Tag | M | R | L | X/Y overvlows and signs, buttons |
| 2 | X7 | X6 | X5 | X4 | X3 | X2 | X1 | X0 | X data byte |
| 3 | Y7 | Y6 | Y5 | Y4 | Y3 | Y2 | Y1 | Y0 | Y data bytes |
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)
| Byte | D7 | D6 | D5 | D4 | D3 | D2 | D1 | D0 | Comment |
|---|---|---|---|---|---|---|---|---|---|
| 1 | 0 | 0 | Ysign | Xsign | 1 | M | R | L | X/Y signs and R/L/M buttons |
| 2 | X7 | X6 | X5 | X4 | X3 | X2 | X1 | X0 | X data byte |
| 3 | Y7 | Y6 | Y5 | Y4 | Y3 | Y2 | Y1 | Y0 | Y data bytes |
| 4 | Z7 | Z6 | Z5 | Z4 | Z3 | Z2 | Z1 | Z0 | Z/wheel data byte |
Standard PS/2-compatible mouse data packet format (5 Buttons + VerticalWheel)
| Byte | D7 | D6 | D5 | D4 | D3 | D2 | D1 | D0 | Comment |
|---|---|---|---|---|---|---|---|---|---|
| 1 | 0 | 0 | Ysign | Xsign | 1 | M | R | L | X/Y signs and R/L/M buttons |
| 2 | X7 | X6 | X5 | X4 | X3 | X2 | X1 | X0 | X data byte |
| 3 | Y7 | Y6 | Y5 | Y4 | Y3 | Y2 | Y1 | Y0 | Y data bytes |
| 4 | 0 | 0 | B5 | B4 | Z3 | Z2 | Z1 | Z0 | Z/wheel data and buttons 4 and 5 |
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.
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: Drivers anydata port devices.
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.
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:
4g Systems Gmbh Port Devices Driver Downloads
- 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
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.
Dec 21, 2020 • Filed to: USB Recovery • Proven solutions
Have you ever had difficulty connecting your devices to your computer using a Prolific USB to Serial adapter? If yes you are lucky to find this page, it will give you all the information need to fix an unresponsive Serial driver adapter. You may have noticed a yellow exclamation mark hovering over or beside the USB to Serial Driver when searching your Device Manager and if you have we can all agree that it signifies a prevailing problem.
Overview of the Error
If you are not able to connect your device to your PC using a USB to Serial adapter it may be that
- The USB driver is outdated
- The USB Driver is missing
- Or even a corrupted driver
While you can't be so sure what the exact problem is there are solutions you can adopt to fix the issue once and for all. Read on to find quick fixes to resolve the problem.
1# Fix Prolific USB to Serial Driver not Working
Solution: Roll your Prolific USB to Serial Driver back to an older version
Updating your drivers often work wonders for your system because it makes sure that it runs on the latest features that guarantee maximum functionality. Unfortunately updating your drivers can cause this kind of error especially if your latest update does not work too well with your hardware. Once you upgrade your PC to the latest Windows version your Prolific USB to Serial Driver also updates to the latest driver software and if the driver is not compatible with your Hardware issues may arise. To correct the error, you will have to download the driver again by following these steps.
- Right-click on your PC Start button and open Device Manager
- Double click LPT and COM ports then locate the Prolific USB to Serial Driver and right-click it so you can select Update Driver
- For driver software click My computer
- From My computer select 'Let me pick from a list of drivers available'
- Choose an older version from the list then click Next
- The driver you selected will be installed automatically
- Once it has been downloaded reconnect the driver to see if it works.
2# Fix Prolific USB to Serial Driver 'Coder 10'
Driver issues reveal themselves in so many ways or through messages such as
- This device will not start (Code 10)
- There is no driver installed in this device
- The driver was not successfully installed
A code 10 error may arise because the chip you are using is not an original one. If you are using a fake, the manufacturer has a way of disabling it due to copy write infringement and the copy write takes effect once you download a recent update. To protect your PC from getting this code, you will have to make sure that your Windows 10 never updates a driver without approval. Updates come in the form of 64 bit and 32-bit drivers. Below we will show you how to work your way around the problem.
Window 64 bit Fix
To fix Windows 64 bit OS including Prolific USB to Serial Adapter, follow through these steps.
- Download 'PL2303_64bit_Installer.exe and Save
- Remove every USB to Serial adapter from your PC and double click the 'PL2303_64bit_installer.exe
- Follow the prompt by plugging in one USB to Serial adapter the click on Continue
- Reboot your PC to get Windows up and running
If you have followed these process through and you still see the same error go to your device manager
- Open the control panel and navigate to Device Manager
- From your control panel navigate to the System category and click the Hardware tab
- Scroll to the LPT/COM port and double click Prolific USB to Serial Comm Port
- Click Drivers in the Properties section
- The Driver you choose should read '3.3.2.102 with an appropriate date attached
- If the date is wrong then it means the wrong driver was installed
- Unplug the Serial adapter and run the steps again to install the correct driver
4g Systems Gmbh Port Devices Driver Download Windows 7
Window 32-bit
For Windows 32-bit OS systems follow these steps
- You will have to download the 'PL-2303_Driver_Installer.exe and save from Microsoft download link
- Run the program and eradicate the driver if you can
- Run the installer once more to install a correct driver
To Troubleshoot for error if your device still does not work
4g Systems Gmbh Port Devices Driver Download
- Go to Control panel, enter System to access your Device Manager
- Scroll down to the LPT/ COM port then double click Prolific USB to Serial Comm Port
- Click Driver in the Windows Properties section
- The driver must be numbered as '2.0.2.8' and dates accordingly
If the driver was not installed, remove the Serial adapter then run 'PL2303_Driver_Installer.exe' again. Follow directions in Device Manager to download the correct driver
The three solutions listed in this article have proven to be quite helpful in fixing a Prolific USB to Serial driver not working on Windows 10. They may appear confusing at first but if you follow each step in detail you can resolve the issue.
Video Tutorial on How to Fix USB Device Not Recognized
USB Solution
4g Systems Gmbh Port Devices Driver Download Windows 10
- Recover USB Drive
- Format USB Drive
- Fix/Repair USB Drive
- Know USB Drive