Serial Mouse Port
Jul 31, 2011 is the serial port configured for the device in question? Something like baud 9600 8,n,1 which would translate to 9600 bits per second,8 bit word,no parity bit,and 1 stop bit. May also have settings for flow control. Hardware,software, or no flow control. Also check that com1 is associated with serial port. 9-Pin Serial Port for PS/2 Mouse. Serial Optical 3 Button Mouse + FREE Mouse Pad w/ 9 Pin Serial Connector for Windows + DOS Computers - Legacy Vintage.
Jul 09, 2004 It's a Logitech trackball mouse with a PS/2 connecter into an adapter connected to a serial port in my computer. I have installed the proper XP driver for the mouse from Logitech. I have only a serial port and no PS/2 port. The mouse is not being detected at the serial port but I do get the message that it's detected 'at an unknown port'. The computer (Old notebook) I want to plug the mouse, into only has a serial port. The mouse came with an USB to PS/2 adapter and worked with my desktop computer. Maybe it would be better to ask for a PS/2 to serial port converter. I would like to see a schematic that would accomplish this if possible. To check whether or not an RS-232 serial port is working, perform an RS-232 loopback test by doing the following: If your serial port is not female, convert it by taking a female/female cable or gender changer and plugging it into the serial port. Take a metal paperclip or wire and cross pins 2 and 3.
Vintage Microsoft Serial Port Mouse - Tested - Working - Fast Ship!
It's in great shape and has been tested and working. It would be great to use or for a collector.Customs services and international tracking provided$22.21 shippingNew! Serial Port/RS232 Genius Mouse for Retro Computers
Mouse for Retro Computers (Serial Port). Rare three button 9 pin D Type serial mouse. Suitable for many retro computers including most Acorn computers. Provided you can get the module on to a disc in the computer the driver can initially be loaded from the command line.From United Kingdom$6.08 shipping31 soldVintage Microsoft Serial Mouse/Port Compatible Mouse
<p>Mouse is in great shape, adaptor attached. Serial/port config.</p>Customs services and international tracking provided$17.99 shippingRS-232 9pin Serial mouse Com Port Trackball Industrial Mechanical wired Bal mice
Interface:Serial ports/COM/RS/Side port. we thought communication is more important than anything.so how do you think about?. Color: as picture shown(White ).From ChinaFree shippingVintage Genuine Microsoft Serial Mouse Port Compatible 2.0 Trackball 'MEXICO'
From Australia$19.76 shippingAnir Ergonomic Vertical Gaming Mouse Model AE2SRSUN w/ Serial Port NOS anir2
Requires a serial port to USB adapter.Customs services and international tracking provided$26.95 shippingKiddy Mouse Combi Version, PS/2 & Serial Port Convertible (Multiple Colours)
Model Combi Version.From United Kingdom$31.01 shippingLOGITECH T-CH11 TrackMan Marble PS/2 Corded Mouse w/ Serial Port Adapter
It features a three button design and a long cord for ease of use. • This item is in pre-owned, good working condition.Customs services and international tracking provided$23.36 shippingMouse RS232 (Serial Port) Black Color With Scroll
From Israel$15.00 shippingPort Adapter Mouse 501215-0004 HC SH Serial USB
Customs services and international tracking provided$16.76 shippingEarly Mouse Systems Corp. PC Mouse Older Serial Port Model no 403917-001 c4
Our sales team Works diligently to price everything competitive. Early Mouse Systems Corp. PC Mouse older serial port Model no 403917-001. Or if you buy a part and it doesn't fit your needs. APPLICATION FOR A PART NUMBER IS YOUR RESPONSIBILITY.Customs services and international tracking provided$17.30 shipping
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.
Instead I'd like to avoid the problem by changing our protocol to not send any data which may get us misidentified as a mouse. The only problem is that I'm not quite certain what patterns to avoid.Apparently Microsoft's Mouse protocol consists of packets of four bytes where the MSB of the first is set and that of the last three is clear.
Would sending only 7-bit ASCII suffice? Are there any other devices I need to worry about being detected as?
doynaxdoynax8 Answers
I just encountered this problem myself on Windows 7 Professional x64, and a solution that worked for me was to go into the registry and edit the following value:
Change Value to 4 and it will stop this problem occurring.
Here is a list of all valid Start values:
A reg edit command would be as follows:
You then need to restart the computer, which should now start correctly and not attempt to discover a serial mouse.
good luck.
SerdalisSerdalisIt 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.
During detection the ports switches to 1200-7-N-1 mode while asserting DTR+RTS to which a response is expected within 200 ms, with a couple of retries in case of failure. Unfortunately for a legacy mouse a single M or B character suffices as identification.
In our case the protocol was reworked to avoid these characters and now appears not to be misidentified anymore.
However we were using a virtual USB serial port and for a traditional serial port this approach may be somewhat difficult as anything sent at a different baud rate is liable to look like line noise. In this case I suppose the easiest workaround is probably, as has already been suggested, to avoid making any unsolicited transmissions.
Alternatively with the serial control signals actually hooked up, or intercepted by a USB CDC device, processing the DTR or RTS signals and holding off on output. Actually implementing the plug-and-play protocol would be an even niftier option. Supposedly there are cheap RS232 cables around without a full complement of control signals though so this approach might still fail.
I also encountered this problem, fixed it by disabling 'serial enumerator' in the advanced properties of the FTDI driver (properties of COM ports in Device Manager). This is described in http://www.ftdichip.com/Support/Documents/AppNotes/AN_107_AdvancedDriverOptions_AN_000073.pdf.
Reed HedgesReed HedgesI have encountered this Windows bug myself. Here is my own research on the topic:
Microsoft acknowledges this bug: http://support.microsoft.com/kb/819036Start with downloading their tool and see if it solves the issue.
- Download & install their program.
- Run it from the command prompt from C:programMicrosoft comdisable
- Write
comdisable /listwhen executing the program. - All ports on the computer will be shown.
- Write
comdisable /disable COMxwhere x is the port number. - Do this for all ports on the computer.
- Reboot.
This should hopefully work as an universal solution.
Alternatively, you can hack in boot.ini but I don't believe this works in Vista/Win 7. I have some app note from Cisco systems describing how to do this. If the above doesn't solve your problem, please let me know.
LundinLundinMaybe this helps:We had the same problem with FTDI FT232RL.We found out, that it was a hardware issue of our PCB.
Rational Acoustics Smaart.v7.4 CrackHere on our site you will discover the arrangement. This is motivation behind why me make this site. Smaart 8 keygen download. We have a great deal of full broke virtual products and applications checked and tried just to enhance your product encounter. We confirm the virtual products on all stages to guarantee that no bugs showed up.Our group know the issues around the web identified with all the split programming projects accessible on the web and we are certain that you finded harmed content, break not working, inaccessible serials or keys lapsed.We was there in your place and know how disappointing is the point at which you don’t have a split or key accessible for your product.
FTDI-Datasheet says about #RESET-Pin: Active low reset pin. This can be used by an external device to reset the FT232R. If not required can be left unconnected, or pulled up to VCC.
RESET-Pin was not required in our application, so we connected it to Vcc via 1k Pull-Up.It seemed that the pull-up of #RESET-Pin caused an undefined start-up of the FT232RL, at least every second converter, we connected to a USB-socket caused a serial-ball-point in the devive manager. We removed the pull-up-resistor at #RESET-Pin, therewith the #RESET-Pin is unconnected. Since then every interface worked proberly and didn't any longer create serial-ball-points in the Windows device manager.
If you have a 'true' serial port, or an USB dongle (RS-232, RS-485, it does not matter) this problem can be worked around by first opening the serial port in question with a terminal, or whatever application you want to monitor it with, and only then plugging the device in. For your own sake, you should also pay attention to remove the device before terminating the connection.
Serial Mouse Port Orange
With FTDI chips soldered on the device itself, you are busted. It took a few rounds for me to explain the management that a device communicating on it's own paired with an FTDI chip soldered on the PCB meeting Windows computers won't likely pass for user-friendliness, no matter how slick an USB socket may look like on the cabinet.. (Thankfully, all these conditions coming together are quite rare and unusual)
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
In my development environment, I've simply disabled Microsoft Serial Mouse from the Device Manager.
This seems to solve the culprit of my problem. Before doing so, the CH340G chip I've used in my design used to lower the DTR five times before initiating the connection, effectively rebooting my Arduino-based board and render it useless.
protected by Samuel Liew♦Jan 3 '17 at 4:13
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?