Carbide v.1.3.1, (N95 1-gig, firmware v.20.0.0.015)
After repeated failures trying to connect to TRK via USB, I installed some up-to-date Bluetooth software (Toshiba) and tried it that way. After that failed, I moved to another machine with a clean install of Carbide and was able to connect there via USB, thus keeping my job.

HOWEVER: now, as soon as I start Carbide on the original machine, it floods the COM ports with messages. Here, from the portmon log, are the opening salvos, pretty normal:
4 0.24370779 Carbide.c++.1.3 IRP_MJ_CREATE Winachsf0 SUCCESS Options: Open
5 0.00000307 Carbide.c++.1.3 IOCTL_SERIAL_SET_QUEUE_SIZE Winachsf0 SUCCESS InSize: 8192 OutSize: 8192
6 0.00000223 Carbide.c++.1.3 IOCTL_SERIAL_GET_BAUD_RATE Winachsf0 SUCCESS
7 0.00000168 Carbide.c++.1.3 IOCTL_SERIAL_GET_LINE_CONTROL Winachsf0 SUCCESS
8 0.00000196 Carbide.c++.1.3 IOCTL_SERIAL_GET_CHARS Winachsf0 SUCCESS
9 0.00000168 Carbide.c++.1.3 IOCTL_SERIAL_GET_HANDFLOW Winachsf0 SUCCESS
10 0.00000223 Carbide.c++.1.3 IOCTL_SERIAL_GET_BAUD_RATE Winachsf0 SUCCESS
11 0.00000168 Carbide.c++.1.3 IOCTL_SERIAL_GET_LINE_CONTROL Winachsf0 SUCCESS
12 0.00000196 Carbide.c++.1.3 IOCTL_SERIAL_GET_CHARS Winachsf0 SUCCESS
13 0.00000196 Carbide.c++.1.3 IOCTL_SERIAL_GET_HANDFLOW Winachsf0 SUCCESS
14 0.00000251 Carbide.c++.1.3 IOCTL_SERIAL_SET_BAUD_RATE Winachsf0 SUCCESS Rate: 9600
.
.
--------------------
then after these openers, Carbide produces a steady stream of the following until I close it:

313 0.00000559 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS BtPort0 SUCCESS
314 0.00000251 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS Winachsf0 SUCCESS
315 0.00000251 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS USBSER001 SUCCESS
316 0.00000251 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS USBSER000 SUCCESS
317 0.00000335 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS BtPort0 SUCCESS
318 0.00000223 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS Winachsf0 SUCCESS
319 0.00000223 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS USBSER001 SUCCESS
320 0.00000168 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS USBSER000 SUCCESS
321 0.00000391 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS BtPort0 SUCCESS
322 0.00000251 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS Winachsf0 SUCCESS
323 0.00000223 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS USBSER001 SUCCESS
324 0.00000251 Carbide.c++.1.3 IOCTL_SERIAL_GET_COMMSTATUS USBSER000 SUCCESS

iterating over the 4 assigned COM ports again and again and blocking any communication with them.

At shutdown, Carbide produces a sensible stream of shutdown messages, once, and quits appropriately.

Uninstalling the bluetooth software did not change this behavior, nor did any variation of connection or device settings I was able to come up with. Since the affected machine is my laptop, I would like to find a solution and be portable again.

Has anyone else seen this behavior? Any cure? Thanks!!