When a Colibri is connected to a PC and the PC is communicating with
the flight data transfer of the Colibri ( ie when LXe or CU 'connection
wizard' is running ) the Colibri will beep at about 1Hz. This
'heartbeat' tells the user that the mode is working. This beep becomes
intermittent as data is downloaded from the device. When connected
'normally' ie in transmit only NMEA mode as in the glider, the Colibri
does not make any sounds unless a TP or zone is entered.

If your Colibri is connected to your PC and is not making any noise and
your PC's mouse is 'locked up' or doing wierd things ( like wandering
about of its own will ) then the PC has identified and is using the
data stream from the Colibi as a mouse. Depending on your particular
setup on your PC and what programs you are running or have installed
etc this can either be simple to fix ie: by disabling the 'phantom'
mouse driver, or a right pain in the behind.

The Interrupt request used for this will not help much BTW, I suspect
that tinkering with the Windows registry to make the Device Manager
load the serial port driver before the mouse driver might be the right
way to fix the problem once and for all but this is beyond most average
PC users. I wont discuss it here because playing with the registry can
be *fatal* to your PC.

The best solution would be to get a savy PC bloke to sort out your
driver setups. Personally I run ConnectMe on the cockpit iPaq, download
the flights to the iPaq at the end of the day and then transfer the
data using activesync when I'm at the PC. The Colibri doesn't get
removed from the aircraft.

Ian