I'm working on a device which communicates with a PC through a (virtual) serial port. The problem is that the data we are sending occasionally gets incorrectly identified by Windows as a bus mouse, after which the "Microsoft Serial Ballpoint" driver is loaded and the mouse pointer starts jumping around on the screen and randomly clicking on things.
A bit of Googling reveals that is an old and well-known problem with serial devices where the usual work-around is a bit of registry hacking to disable the offending driver. That it is a lot to demand from our users however and I'd rather not have our application messing around with the user's registry. Especially not when the fix is dependent on the Windows version and the user may well be using a bus mouse.
Microsoft Serial Mouse Disable
DOWNLOAD: https://tinurll.com/2vzZAs
It turns out that mouse detection in Windows is normally handled by the serenum.sys filter driver. This driver implements support for legacy serial mice along with serial plug-and-play. Microsoft has even provided the sourcecode as a WDK sample.
I had this problem since 2010 with serial scale heads connected to the pc. Usb to serial converter or not.. I use onkly SILABS device's CP2102 or the like.. I worked around it by simply allowing the driver to install and then in device manager look for the ballpoint driver under mouse/HIDA and then simply DISABLE the driver, DO NOT UNINSTALL IT simply disable it. Then when you reboot even with the driver instaled it seems windows ignores the comport as serial mouse and uses the data from the input. You will also find that if the ballpoint driver is active then that COMport is in use and sometimes returns a COM PORT not accessible... hope this helps some one out there :) Tx Ben
Below is the code for a subroutine in C#.net. It checks if the registry key is set to 4 and if not it issues the configuration command to disable sermouse.Embed this subroutine in a program which runs at startup and it will correct the setting after a windows update.
/fastdetect:comnumberThis switch turns off serial and bus mouse detection in the Ntdetect.com file for the specified port. Use this switch if you have a component other than a mouse that is attached to a serial port during the startup process. For example, type /fastdetect:comnumber, where number is the number of the serial port. Ports may be separated with commas to turn off more than one port. If you use /fastdetect, and you do not specify a communications port, serial mouse detection is turned off on all communications ports.
If you have installed any third-party mouse drivers, go into Control Panel - Devices and disable their Serial Mouse drivers as well. For example, if you installed the Logitech Mouseware V8.0 for a Trackman Marble, you must also disable the "Logitech Serial Mouse" device, called "lsermous" (note that the Arial lower-case l looks like a capitol i).
So we purchased a SABRENT USB to serial cable for the testing phase. I installed the driver of the cable and everything was ok. But each time we unplug/replug the cable OR each time the computer is restarted, the GPS is detected as a serial mouse. When the GPS is detected as a serial mouse, the mouse start to move everywhere, clicking and double-clicking randomly causing a major problem.
I was hoping to find out how to stop windows 2008 server R2 64 bit from detecting a serial mouse on the com port. i know the boot.ini version with /noserialmouse....etc for earlier versions also i have edited the registry/services/sermouse start parameter (change from 4 to 3) to no avail.windows 2008 server has BCDedit to manage the boot options but i have not seen a reference anywhere to stop the detection of a serial mouse needless to say this server is specific to our PABX and i DO NOT HAVE a serial mouse on that port but i do have a data stream from the PABX. there is some data but it is being garbled and the application will not work.
I did manage to get it working for a few days by uninstalling the serial mouse in Dev manager, disabling and enabling the com port, but after a reboot the problem came back and now no matter what i do it will not work. i am using tools like hyperterminal and putty to view the data stream on the server and no luck. however if i connect my laptop (an XP machine) using hyperterminal the data stream is valid.assistance is greatly appreciated.
By default, DOSBox-X emulates a PS/2 mouse.But some early DOS applications or Windows versions come with their own mouse driver that only works with serial mice.For this purpose, DOSBox-X can be set to emulate a Microsoft serial mouse.If serial mouse emulation is enabled, the PS/2 mouse emulation is automatically disabled.
Another option is VBMOUSE.EXE, which provides seamless support, and also supports the scroll wheel on modern mice.It is however limited to PS/2 mice, so will not work with the optional serial mouse emulation that DOSBox-X provides.
This behavior occurs because you cannot use a USB keyboard or mouse in MS-DOS mode without BIOS USB legacy support because the operating system uses the BIOS for device input; without USB legacy support, USB input devices do not work.The operating system disables USB legacy support for 32-bit USB drivers to work. Windows typically re-enables USB legacy support when you restart your computer in MS-DOS mode unless the USB Host Controller resources have changed from the values that were assigned during Startup.The operating system cannot restore BIOS-designated resource settings. If the current input/output (I/O) port settings are different from the BIOS settings, the device may be inaccessible and your computer may stop responding (hang).
If you use Scream on a Windows PC which receives digitiser data over aserial (RS232 or USB) link, you may find that your mouse pointer starts movingerratically around the screen and making random clicks. This is not a faultwith Scream: it is a Windows bug and it can happen when a Windows PC receivesany serial data. This article provides some methods to fix theproblem.
Many popular brands of RS232-USB converter use the FTDI chip-set and driver.FTDI provide a switch ("serial enumerator") in their driver to enable ordisable this behaviour: seewww.ftdichip.com/Support/Documents/AppNotes/AN_107_AdvancedDriverOptions_AN_000073.pdffor details.
DRIVERS DOS SERIAL MOUSE FOR WINDOWS 10 DOWNLOAD. Index of /downloads, rufus. Ms mousedriver v8, business support home support, windows win new. Alexandre bartel added, universal serial bus, myharmony support ultimate ears.
I worked around it by simply allowing the driver to install and then in device manager look for the ballpoint driver under mouse/HIDA and then simply DISABLE the driver, DO NOT UNINSTALL IT simply disable it. Then when you reboot even with the driver instaled it seems windows ignores the comport as serial mouse and uses the data from the input.
It uses a facility called "Serial Enumeration" to test if there is a mouse attached to the COM port, and it will send characters and expect a response. If the right combination of modem control signals and characters come back, it will automatically add a Serial Mouse. You can find this in the Device Manager and disable the serial mouse.
CurrentControlSet\Services\. The Services subkeys contain parametersfor the device drivers, file system drivers, and Win32 service drivers. The name of each Services subkey is the name of the service, whichis also the root of the name of the file from which the service is loaded. For example, for the serial mouse, the service name and Services subkeyname is Sermouse.
The Microsoft BallPoint serial mouse is a type of input device that allows the computer user to navigate the various menu options of the installed software applications. It also delivers the interface that will provide the interaction between the host operating system environment and the computer user. By using this hardware component the computer user can perform various actions like launching, closing, minimizing, and restoring various elements of the operating system environment.
Open the Windows Device manager. Look for the Mice and other pointing devices section. If you find a Mircosoft Serial BallPoint it needs to be disabled. Right mouse click the Microsoft Serial BallPoint and choose to Disable. When disabled Windows will free up the COM Port and show a small arrow in the Mouse icon.
Code tot stop GPS from being detected as serial mouse. Below is the code for a subroutine in C#.net. It checks if the registry key is set to 4 and if not it issues the configuration command to disable sermouse. Embed this subroutine in a program which runs at startup and it will correct the setting after a windows update.
The problem lied in Windows, who incorrectly think anything coming from a serial port at boot time is automatically from a mouse or a pointing device. What we need is a way to disable the detection of pointing device (mouse or anything else) on any serial port when Windows 7 boot.
You can specify a single COM port by naming it after the colon, as in: /fastdetect:com1. which will disable detection of serial mice on COM1. If you want to disable serial mice detection on several ports, put their names in a comma-separated list after the colon, as in: /fastdetect:com1,com2.
Problem: Plugging in a USB GPS, or a serial GPS connected via a Serial->USB adapter causes Windows 7 to improperly recognize the device as a serial mouse, and since the data stream is rapid, the mounse pointer begins to jump all over the screen. In XP, disconnecting the GPS temporarily left behind the serial mouse in Device Manager, and disabling it there would then allow the system to be used again.
Many GPS users have experienced the nuisance of having a GPS receiver falsely identified as a mouse on Windows PCs. This occurs if an active GPS device (already outputting data) is already connected to a serial port while Windows is booting. The result is an uncontrollable mouse cursor randomly jumping around the screen. Normally, the only way to stop this is to unplug the GPS serial connection, and then reconnect it. 2ff7e9595c
Comments