If it came with a CH341 driver, it is likely a WCH CH340/CH341 chip. You can usually determine which chip is in the programming cable by using the Windows Device Manager app. However I have seen Windows incorrectly load and try to use the Prolific driver when a WCH chip is present. This can be avoided by manually installing the WCH driver. Except for RT Systems, I don't recommend using the driver CD that comes with a programming cable. Many times it comes on a homemade CD with a bunch file for which the source is unknown (and a high probability of malware being found if it is scanned using an anti-virus program). What I recommend is to download any drivers that are needed from the chip vendor's website. The Miklor radio information website has links to all of the major USB-to-Serial chip vendors (FTDI, Silicon Labs, Prolific and WCH).
Now that I know that Windows can get it wrong, I am in the habit of manually installing the latest drivers (except for Prolific I install the v4.3.0.0 driver) from each chip vendor before I plug in the first USB chip based programming cable.
If you have already installed the WCH CH340/CH341 driver and verified with Device Manager it is loading, then you most likely have an incomplete connection between the? 2-pin plug of the programming cable and the speaker/mic connector of the radio. To understand why I am saying this, leave the 2-pin plug unconnected with the radio and attempt a download. The same "Radio did not respond" error will be encountered. Double-double check that you are getting the plug fully inserted in the socket. I can remember when I would swear that my programming cable was fully inserted into my UV-82 and it wouldn't work. I eventually wiggled and pressed the plug and was dumbfounded when it finally snapped in the rest of the way. Some have been known to have to put pressure on the plug during the cloning process.
Jim
