Dan,
More background:
The driver disks that came with all 3 usb cables were identical and the three driver fileson them appear to be identical (Prolific 2.0.0.26) so I just installed one.
I individually plugged in and out all 3 usb cables and each reported using COM3
Im guessing now that I may have a defective FT2800 USB cable?? Where do you
suggest I buy another, this one came from Kawa.
I read some scuttlebutt on another forum that the Prolific drivers are troublesome
on Yaesu transceivers. Know any options?
Thanks again for taking time to help.
73, Mike
> CHIRP uses COM3, which works well when cloning my Icom 2200H and UV-3A
> Yes, the driver only appears when the USB cable is plugged in, remove it and
> the driver goes away. Ideas?
CHIRP needs to be pointed at whatever COM port your cable is showing up
as. I would not expect all three of the above-mentioned cables to show
up on the same COM port every time. I'm always confused by Windows'
seemingly-random behavior, so maybe there's something I'm missing.
However, I would make sure that you're using what Device Manager shows
_each_time_ you try a clone.
Another thing you may try is unplugging your cable and then trying to
use CHIRP on COM3 again. You should get a different error, and
immediately. If not, then something other than your FT-2800 cable is
actually COM3.