I went a different route - I bought a multiport serial card (PCIE RS232C) and have a dedicated, unique, serial port for the Tbolt. I put it on COM 15, which did not even exist prior to the addition and have had no conflicts since. Just added /15 to the .exe command line.
PC: Home made I7-875 CPU OC to 4GHZ, 12GB RAM, dual 250GB SSD in Raid 0, Fidelity Titanium audio card, HD-5970 graphics card all operating on WIN 7 64B Ultimate edition. Michael / K7HIL On Sun, May 15, 2011 at 12:18 PM, Chuck Forsberg WA7KGX N2469R <[email protected] > wrote: > I replaced a 2.22 version Thunderbolt with a 3.0 version > and Windows 7 Pro 64 bit went nuts. After some Googling > it became apparent that some bagbiter MS software was > interrogating the serial ports looking for a serial ballpoint > pointer. Windows started hallucinating as it tried to parse > GPS data as cursor movements and mouse clicks. > > After reinstalling Windows twice I saw a message suggesting > disabling the ballpoint driver. That works so far. Don't remove > it, it will just come back. Disable it. > > The 3.0 version seems to do a much better job keeping things > steady than 2.22 dis. > > > -- > Chuck Forsberg WA7KGX N2469R [email protected] www.omen.com > Developer of Industrial ZMODEM(Tm) for Embedded Applications > Omen Technology Inc "The High Reliability Software" > 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 > > > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
