<html><head>
<style id="css_styles"><![CDATA[
blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; }
a img { border: 0px; }
li[style='text-align: center;'], li[style='text-align: right;'] { list-style-position: inside;}
body { font-family: Segoe UI; font-size: 12pt; }
]]></style>
</head>
<body>I have not had to do anything with my Baofeng and Yaesu radios for quite a while but our group has added some new frequencies so it time to update.<div><br /></div><div>Neither my Yaesu VX-6Rs nor my Baofeng UV-5Rs will communicate with either my Linux Netbook or my WIndows 10 computers. In the case of the Linux box, I have added my user name to the Dialout group then rebooted. In the case of the Windows machines I have changed the Baofeng cable to the Prolific 3.2.0.0 driver that I downloaded today from the Miklor site. The Yaesu cable is an FTDI cable and was always recognized previously. The cables are fully inserted in each case and the volume is maxed out. Device Manager shows both cables as working. The Baofeng cable reports as COM7 and the Yaesu cable as COM6</div><div><br /></div><div>I'm never surprised with the Windows machines need some tinkering to work but CHIRP and Linux have always worked will in the past.</div><div><br /></div><div>What am I missing. I suspect it's something simple.</div><div><br /></div><div>Many thanks for reading.</div><div><br /></div><div>Tom</div></body></html>