Nigel, The bouncing mouse is always a fun problem. If you go up to the Synergy at:
http://www.synergy-gps.com/images/stories/ShopTalk/disabling detection of microsoft ballpoint mouse.pdf there is an old paper I wrote about this problem. Disabling the mouse in the Windows system folder works pretty well, but on more than one occasion I have seen it mysteriously reappear. As you noted, this only happens when the receiver is plugged in during a boot. If the receiver is plugged in during a boot, unplugging it and plugging it back in will not help. Apparently this is a system variable that is set during boot. The second half of the paper is the registry fix that Rick Hambly showed me several years ago. I think this method is included in his TAC32 user manuals. This is the way to REALLY shut the serial mouse down for good. Note that this problem is not limited to VP receivers. If you have anything plugged into a serial port outputting data during boot that your computer thinks is valid mouse data the same thing will happen. Best regards, Randy Warner Senior Applications Engineer Geodetics, Inc. 858.729.0872 ____________________________________________________________________ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, July 19, 2007 3:13 AM To: time-nuts@febo.com Subject: Re: [time-nuts] Oncore VP problem ); SAEximRunCond expanded to false Errors-To: [EMAIL PROTECTED] In a message dated 19/07/2007 02:44:42 GMT Daylight Time, [EMAIL PROTECTED] writes: My suggestion is that you pick up a free evaluation copy of Rick Hambly's TAC32 software at http://cnssys.com/cnsclock/Tac32Software.html . TAC32 knows all the quirks & options that ever existed in a Motorola receiver, going all the way back to the Rev.3 PVT6. Then if you find it useful, a legal copy can be purchased from Rick, or at members discount from TAPR (http://www.tapr.org/gps_tac32.html). ------------------- Hi Tom Many thanks for the suggestion. You may have seen my subsequent post in which I commented that I had tried TAC32 without solving my problem, only to find the kit was working ok but with an incorrectly labelled connector. TAC32 does look useful though so I'll check it over more thoroughly later. One "interesting" side effect...... Some time after shutting down TAC32 last night, but with the Oncore still connected to the serial port and outputting data, my PS2 connected mouse started misbehaving, with the pointer jumping all over the place then settling down for a while before repeating the performance. It didn't occur to me at first that the incoming serial data might have anything to do with it until it started again this morning and I eventually stopped it by disconnecting the serial lead from the receiver. Whilst I can't say for sure that running TAC32 was what caused it, it's not something I've ever seen in the past nor previously this past few days after running WinOncore. I'll check later to see if the port shut down properly and also take a look at the Oncore message stream, perhaps TAC32 may have changed something there as part of its auto setup routine? regards Nigel GM8PZR _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
