<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p>Where are you?</p><p><br></p><blockquote type="cite">On 13 May 2018 at 16:00 Tom Balaban <mototom800@gmail.com> wrote: <br> <br>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></blockquote><p class="default-style"><br> </p><blockquote type="cite">_______________________________________________ <br>chirp_users mailing list <br>chirp_users@intrepid.danplanet.com <br>http://intrepid.danplanet.com/mailman/listinfo/chirp_users <br>This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net <br>To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com</blockquote><p class="default-style"><br> </p><p><br></p><p class="io-ox-signature">Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385-1115, USA. tel +1 937 825 5032<br>Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), e-mail nigel@ngunn.net www http://www.ngunn.net <br>Member of ARRL, QRPARCI #11644, SOC #548, Flying Pigs QRP Club International #385,<br> Dayton ARA #2128, AMSAT-NA LM-1691, GCARES, EAA382.</p></body></html>