<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>On 2020-03-17 08:52, Dennis Wage wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div dir="ltr">
<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>I've used Chirp many times with my FT-60 w/o so much as a sneeze.</p>
<p>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>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>Benton 17mar2020<br />--<br />NX7O<br /><a href="mailto:benton@siletzbay.com">benton@siletzbay.com</a><br /><br /></p>
</body></html>