Microsoft Serial Ballpoint Driver Installed

[InvaderZim]

This might be a fluke, but it was weird enough to post. I'm running Win Vista64 and editor v5.3.1. I was debugging while running the editor (with the 8MHz option). My code wasn't using the serial port, just sampling an ADC, averaging, and then debugging. I'm using the RevEd USB serial thingy.

All of sudden I get a driver installation for Microsoft Serial Ballpoint Driver, and on completion my windows pointer goes nuts. I turned off the 'Axe and it settled down. Turning it back on started the weirdness again. Damndest thing!

Unplugging and re-plugging the serial port seemed to help.

Looks like I'm not the only one with this issue: http://www.eggheadcafe.com/software/aspnet/29648873/com-port-problem-serial-ballpoint.aspx

 

[lazzymonk]

I have experienced a similar thing with my home made FT232RL board. I thought it was just something i didnt have quite right.

It works fine, but from time to time my mouse (logitech laser) goes nuts until i unplug it.

 

[hippy]

Had the same problem myself with XP and I recall that was with some other device than an AXE027. Windows 'just decides' for some reason you've got a Ballpoint Device. Uninstallling the device in Device Manager was the solution I believe I took, re-booted, and everything seems to have been fine since.

 

[MPep]

This is a relatively common problem especially noticed by people using GPSs.
It seems the NMEA string, at the constant data that it sends out at, is recognised by the computer as a MS Ballpoint mouse. Usually associated with baudrate 4800,8,N,1.

Check here: http://support.microsoft.com/kb/833721/en-us Look for the title fastdetect

Another is http://support.microsoft.com/default.aspx?scid=kb;[LN];Q131976.

Searching for "Crazy Mouse Problem GPS" in Google brings forth enough potential solutions.

Hope this helps,
MPep.