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
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
Hi,
It seems a Microsoft fixation that anything that puts streams on the
serial port is a Microsoft Serial Ballpoint (I bet you've never seen
one) since any version I remember. I don't think that the application
version makes any difference. If the application has open the port
before the
