<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">No, nothing bad happened. It was years ago, and you might be right. Maybe it was an earlier version of CHIRP that just wasn’t going to work no matter what. In any case, I have the ADMS and it works great for me.<div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 17, 2020, at 8:41 PM, John Kemker <<a href="mailto:kemkerj3@gmail.com" class="">kemkerj3@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Mark, I can certainly understand why you're sticking with what you have. Makes lots of sense. However, your description doesn't sound like your radio was bricked. That version of CHIRP just didn't want to talk to it. It may work, now, but there's no reason for you to switch, since you already have working software. Am I right?</div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 17, 2020 at 11:13 PM Mark Lassman via chirp_users <<a href="mailto:chirp_users@intrepid.danplanet.com" class="">chirp_users@intrepid.danplanet.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class="">I tried Chirp and some other program I think it was called FT60 Commander? Anyway, could never get it to work, the Chirp software and the radio could not “speak” to each other. I’ve been using the ADMS software for the last ten years with both the FT60 and the FT-7900 with absolutely NO problems. Sure, it’s $50 as opposed to “free” (Chirp), but it works, I’m familiar with it, and it does what I want it to do.<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Mar 17, 2020, at 7:04 PM, <a href="mailto:benton@siletzbay.com" target="_blank" class="">benton@siletzbay.com</a> wrote:</div><br class=""><div class=""><div style="font-size:10pt;font-family:Verdana,Geneva,sans-serif" class=""><p class="">On 2020-03-17 08:52, Dennis Wage wrote:</p>
<blockquote type="cite" style="padding:0px 0.4em;border-left:2px solid rgb(16,16,255);margin:0px" class="">
<div dir="ltr" class="">
<div class="gmail_default" style="font-family:monospace,monospace"> </div>
<div class="gmail_default" style="font-family:monospace,monospace">Is there any documented cases of Chirp bricking a radio so badly it had to be sent back for a factory restore.</div>
<div class="gmail_default" style="font-family:monospace,monospace"> </div>
<div class="gmail_default" style="font-family:monospace,monospace">I see so many Yaesu users bring this up that they're afraid to use Chirp because it will break a radio bad enough to void warranty etc. etc...</div>
<div class="gmail_default" style="font-family:monospace,monospace"> </div>
</div>
</blockquote><p class="">I've used Chirp many times with my FT-60 w/o so much as a sneeze.</p><p class="">Back in the day, speculation was these stories were circulated by Yaesu due to their partnership with RTS. I know HRO sold bare 'Kenwood' cables but for my FT-60 I had to buy a cable with the RTS software for $40 - $50. SW was useless to me, me being a Linux guy (and back then w/o a Win VM.)</p><p class="">And at that, I later found the cable wouldn't work with one of the wx-resistant Yaesu models -- the overmolding wouldn't fit down into the programming socket.</p><p class="">Benton 17mar2020<br class="">--<br class="">NX7O<br class=""><a href="mailto:benton@siletzbay.com" target="_blank" class="">benton@siletzbay.com</a><br class=""><br class=""></p>
</div>
_______________________________________________<br class="">chirp_users mailing list<br class=""><a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank" class="">chirp_users@intrepid.danplanet.com</a><br class=""><a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank" class="">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br class="">This message was sent to Mark at <a href="mailto:kb6kgx@mac.com" target="_blank" class="">kb6kgx@mac.com</a><br class="">To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank" class="">chirp_users-unsubscribe@intrepid.danplanet.com</a></div></blockquote></div><br class=""></div>_______________________________________________<br class="">
chirp_users mailing list<br class="">
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank" class="">chirp_users@intrepid.danplanet.com</a><br class="">
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank" class="">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br class="">
This message was sent to W5NNH at <a href="mailto:kemkerj3@gmail.com" target="_blank" class="">kemkerj3@gmail.com</a><br class="">
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank" class="">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div dir="ltr" class="gmail_signature"><div dir="ltr" class="">--John E Kemker III</div></div>
</div></blockquote></div><br class=""></div></body></html>