In the TAC32 documentation, you will read about Mouse data and GPS data !

Theres a command line switch to run that should resolve it (NoSerialMice 
or something to that efect)....


Brian N4FMN


[EMAIL PROTECTED] wrote:
> ); SAEximRunCond expanded to false
> Errors-To: [EMAIL PROTECTED]
> X-Spam: [F=0.0149253731; S=0.010(2007071801); MH=0.500(2007071904); 
> R=0.600(s0/n0)]
> X-MAIL-FROM: <[EMAIL PROTECTED]>
> X-SOURCE-IP: [(unknown)]
> X-MxL-Spam-Verdict: No
> 
>  
> 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.

Reply via email to