Jim, just disconnect and reconnect each USB cable while watching the COM
ports in Device Mangler. You'll see the port disappear and then reappear.
FWIW: I never had any problems with Prolific USB-Serial chipsets until
Win10 graciously installed itself in the middle of the night without
asking. Turns out, there are several generations of Prolific chipsets,
and there are no Win10 drivers for a couple of the oldest ones. I found
an adapter with one of the more recent chipsets and it works fine.
73,
Fred ("Skip") K6DGW
Sparks NV USA
Washoe County DM09dn
On 8/14/2017 10:27 AM, Jim Reisert AD1C wrote:
On my Win 10 machine I can tell by going to Device Manager, Ports, selecting
the specific port in question, then right clicking and going to Properties.
There, on all of my USB connections, it says "Manufacturer: FTDI". Hope
that will help.
Thanks, Bill, but I don't know which interface cable he has - it could
be Prolific or FTDI, depending on how old it is. Because there are
two COM ports not associated with the microHAM device (the generic
"USB" and the one that has a Silicon Labs driver), I guess I have to
assume that the generic USB COM port is the one that the K3 needs.
I'll see what type of device it is, and if I can find the right driver
for it.
- Jim
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com
