Conflicting Mouse Drivers in Windows NT
This article explains how to diagnose and resolve touchscreen communication issues caused by conflicting extended-function mouse drivers in legacy Windows NT environments using the v3.1c driver from Elo — Now part of Zebra Technologies.
Important Support Notice: Windows NT is an obsolete operating system and is no longer supported by Microsoft or Elo Touch Solutions. This information is provided solely for legacy maintenance and historical reference.
How to Resolve Mouse Driver Conflicts
Extended-function mouse utility packages (such as Logitech MouseWare) often conflict with legacy touchscreen drivers. If you are experiencing touch failures, follow this troubleshooting progression:
- Apply the Registry Patch: Many mouse utilities search the touchscreen's assigned serial port. To disable this behavior, check the registry path and remove the touchscreen's COM port by following the instructions in our Logitech Mouseware Patch Guide.
-
Uninstall Conflicting Software: If MouseWare or global port search options are not present in the registry:
- Open Control Panel and select Add/Remove Programs.
- If any specialized or brand-name mouse drivers (other than the native MonitorMouse driver) are listed, uninstall them.
- Reboot the system and check touch operation.
-
Perform Hardware and Driver Diagnostics: If removing mouse drivers does not restore functionality:
- For serial touchmonitors connected to a physical COM port, use the comdump utility to verify that raw touch coordinate data is reaching the COM port.
- If you have verified that the hardware is functioning correctly and raw data is present, proceed to verify your startup driver states with our Windows NT Driver Checks Guide.
```
Please report any broken links by emailing support@elotouch.com and include a link to the knowledge article