<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=US-ASCII" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16446"></HEAD>
<BODY style="FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=role_body
bottomMargin=7 leftMargin=7 rightMargin=7 topMargin=7><FONT id=role_document
color=#000000 size=2 face=Arial>
<DIV>Did not get your first problem in a message but if you hold down the left
three buttons and turn on then do the same thing again you will get a good
reset. </DIV>
<DIV>Robby N6MNL</DIV>
<DIV> </DIV>
<DIV>
<DIV>In a message dated 7/3/2012 7:44:33 P.M. Pacific Daylight Time,
dsmith@danplanet.com writes:</DIV>
<BLOCKQUOTE
style="BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"><FONT
style="BACKGROUND-COLOR: transparent" color=#000000 size=2 face=Arial>> So,
did I run into both a CHIRP bug and a Yaesu firmware bug, or is this <BR>>
known behavior?<BR><BR>Sounds like an honest-to-goodness bug to me.<BR><BR>Can
you send me the original CHIRP image, and then an image captured<BR>after
"fixing" it with commander? There's probably just some stray bit<BR>that isn't
getting cleared. I should be able to find it from the diff of<BR>the two
images.<BR><BR>I'll go on to say, once again, that Yaesu radios are really bad
about<BR>this. They let you program basically anything into the memory you
want,<BR>regardless of whether it will crash the radio's microcontroller or
not.<BR>It's really rather unfortunate that they didn't design the radio
a<BR>little better than that...<BR><BR>-- <BR>Dan
Smith<BR>www.danplanet.com<BR>KK7DS<BR><BR><BR><BR><BR>_______________________________________________<BR>chirp_users
mailing
list<BR>chirp_users@intrepid.danplanet.com<BR>http://intrepid.danplanet.com/mailman/listinfo/chirp_users<BR></FONT></BLOCKQUOTE></DIV></FONT></BODY></HTML>