<div dir="ltr"><div class="gmail_default" style="font-size:large">I bought the same PC03 cable from Amazon and that is the cable that worked for me. That cable while not made by Baofeng is stamped with the Baofeng name and sold by Baofeng Tech. I started my install on Windows 7 (64 bit) with one of my cheap cables for which Windows tried to find a driver but it did not work. That was when I went to FTDI's driver site and installed the current driver. As I said before, Windows was reporting the cable and driver as being the right driver but did not work. When I switched to the PC03 cable then it worked. Some of the FTDI clone cables I have, I also bought from Baofeng tech but this was before FTDI produced drivers that broke non FTDI chip cables.<br><br></div><div class="gmail_default" style="font-size:large">Thank you.<br></div><div class="gmail_default" style="font-size:large">Jim Pruitt<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 27, 2016 at 8:57 AM, Jim Unroe <span dir="ltr"><<a href="mailto:rock.unroe@gmail.com" target="_blank">rock.unroe@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Jul 27, 2016 at 9:53 AM, Dennis Yocom, President & CEO<br>
<<a href="mailto:dennis@basiclifetraining.com">dennis@basiclifetraining.com</a>> wrote:<br>
> John et. al.: I'm completely confused now. I bought one PC03 FTDI Authentic<br>
> Genuine USB Programming Cable for BaoFeng, Kenwood, etc from Amazon,<br>
> which said, Sold by: BaoFeng Tech for $20.46<br>
<br>
No need to be confused. The BaoFeng Tech programming cable is not made<br>
by Baofeng. It is highly recommended over a Baofeng programming cable.<br>
<br>
><br>
><br>
><br>
> The cable, which doesn't have any ID on it anywhere (except for a USB symbol<br>
> and something else near it which I don't recognize) was supposed to be the<br>
> correct cable to use in programming a pair of new Baofeng F8HPs. With my<br>
> Windows 7 machine, I got the "Radio did not respond" message about a dozen<br>
> times. I've pushed that cable in so hard I surprised it didn't come out the<br>
> other side.<br>
<br>
I don't know why, but in my tests, it can take up to 8 minutes for the<br>
FTDI driver to be fully installed. If you try to use it prior to that<br>
it will not work and it may interrupt the installation.<br>
<br>
><br>
><br>
><br>
> I realize I'm not the brightest crayon in the box, but does this sound like<br>
> a cable issue, HT, user or a driver issue ( I've tried several times to<br>
> manually install a driver with no luck)? The BaofengTech instructions with<br>
> the cable indicate the cable was supposed to initiate the proper downloads,<br>
> and it was supposed to be a snap. Can someone lighten this poor fool?<br>
<br>
Normally it is plug-and-play. I would recommend that you go to<br>
<a href="http://ftdichips.com" rel="noreferrer" target="_blank">ftdichips.com</a> and download the latest driver and install it. This is<br>
typically the "fix" for when Windows doesn't get it done<br>
automatically.<br>
<br>
><br>
><br>
><br>
><br>
> DR Yocom<br>
<br>
<br>
Jim KC9HI<br>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Jim at <a href="mailto:jpruitt67@gmail.com">jpruitt67@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
</blockquote></div><br></div>