<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:large">Are you sure that is an FTDI and not a prolific chip.?</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><p style="color:rgb(0,0,0);margin-bottom:0pt;margin-top:0pt"><font size="4" face="verdana, sans-serif">Todd Bloomingdale-KC9LOX</font></p><p style="margin-bottom:0pt;margin-top:0pt"><font color="#cc0000" size="4" face="verdana, sans-serif">Tomah, WI</font></p></div></div><div style="color:rgb(0,0,0)"><div><font face="arial, helvetica, sans-serif" size="4"></font></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Sat, Feb 20, 2016 at 12:47 PM, Lreiher <span dir="ltr"><<a href="mailto:lreiher@comcast.net" target="_blank">lreiher@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">folks, thank you all for your efforts to help me out. the reality is<br>
that BENTON seems to have it correct. the cable i purchased was directly<br>
from baofeng. i believe that the source was china b/c when i wrote them<br>
they told me i bought it 14 mo.s ago and that it was listed as 'works w/<br>
win vista, win7, win 8' and was never listed as for win 10. i pointed<br>
out that win 10 did not exist when i bought the cable! clearly, they<br>
have used a CLONE of the ftdi chip and, as benton noted, the drivers<br>
which FTDI loaded into my PC w/o my knowledge or permission was designed<br>
to send TRASH to my cable and render it inoperable! i proved that by<br>
using a friend's cable and it worked fine w/ my UV-5RTP; but, my cable<br>
on HIS pc is useless. the device mgr sees the cable but does NOT get<br>
thru it to see the radio. i asked baofeng if tthey would write code to<br>
FIX the cable since it is their shared fault for using a clone in the<br>
first place. they didnt respond to that message. now, i have reviewed<br>
about 15 programming cables; all - EXCEPT one - are less than $6; oNE is<br>
$20 and it is marked 'genuine FTDI cable'. so, i kknow that i could<br>
resolve this for 20 bucks. but i am pissed that FTDI trashed something i<br>
purchasedd in good faith FROM the manufacturer!!<br>
so, i was hoping someone had the expertise to write code to send to my<br>
cable to make it functional again.<br>
<br>
thanks again to you all for your input; however, i'm afraid that i'm<br>
still out in left field.............<br>
peace,<br>
larry<br>
KD9AVZ<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 <a href="mailto:tbloomingdale@gmail.com">tbloomingdale@gmail.com</a> at <a href="mailto:tbloomingdale@gmail.com">tbloomingdale@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>