<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Arial">Hi Dan,<br>
See attached. There may be a few changes between the two, I think
I changed the power settings and maybe a name or two.<br>
<br>
I hear what you say about turning the radio into a brick. I used
to have this argument with the PE's at my former employer. It went
something like, "you were outside the maintenance package, you
shouldn't have done that" to which I replied "don't let me do
things that are bad." You can't win that argument.....<br>
<br>
-Scott<br>
<br>
</font>
<div class="moz-cite-prefix">On 7/3/2012 7:44 PM, Dan Smith wrote:<br>
</div>
<blockquote cite="mid:4FF3AE01.5070003@danplanet.com" type="cite">
<blockquote type="cite">
<pre wrap="">So, did I run into both a CHIRP bug and a Yaesu firmware bug, or is this
known behavior?
</pre>
</blockquote>
<pre wrap="">
Sounds like an honest-to-goodness bug to me.
Can you send me the original CHIRP image, and then an image captured
after "fixing" it with commander? There's probably just some stray bit
that isn't getting cleared. I should be able to find it from the diff of
the two images.
I'll go on to say, once again, that Yaesu radios are really bad about
this. They let you program basically anything into the memory you want,
regardless of whether it will crash the radio's microcontroller or not.
It's really rather unfortunate that they didn't design the radio a
little better than that...
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
chirp_users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a>
<a class="moz-txt-link-freetext" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>