<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Sep 29, 2013 at 5:10 PM, Milton Hywatt <span dir="ltr"><<a href="mailto:mhywattt@yahoo.com" target="_blank">mhywattt@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="font-size:12pt;font-family:times new roman,new york,times,serif"><div><span>John, you won't necessarily get the yellow triangle of death</span></div>
<div style="font-style:normal;font-size:16px;background-color:transparent;font-family:'times new roman','new york',times,serif"><span>as the driver may be compatible with the cable but not with Chirp. </span></div>
<br></div></div></blockquote></div><br></div><div class="gmail_extra">I would agree with this if you were talking out the Baofeng software. But not when talking about CHIRP.<br><br></div><div class="gmail_extra">I have tried nearly every Prolific driver I could get my hands on to
determine the latest driver that would work with the unauthorized
USB-to-Serial chip copies that are normally used in low cost programming cables. The latest driver that you can use is v3.3.2.105. CHIRP works fine with this driver. The older Baofeng software from a year ago (I haven't tried the latest Baofeng software) won't work with it. I had to downgrade to v3.2.0.0 before the Baofeng software would work. This is the sole reason that I recommend this driver for cables with unauthorized chips.<br>
<br>I have no doubt that CHIRP will work on any programming cable (Prolific, FTDI, CP2102, etc.) that provides a working virtual COM port.<br><br></div><div class="gmail_extra">Jim KC9HI<br>
</div></div>