I got an interesting email from David, (SV0SGS) this morning. Long story short, after programming using the supplied software, his TH-8600 began doing strange things in weird and unexpected ways. That brought me back to reality and the fact I have been sorely remiss in updating this thread. Ergo, see below.
What to do if your TYT TH-8600 starts doing bizarre things after a programming session
Sorry! Re-programming from your existing programming file isn’t going to fix it nor help. The problem is your programming file has become corrupted, and no matter how many sweet nothings you whisper into its ear, it ain’t gonna change.
How to fix it.
Sadly, this is going to involve some unpleasant aspects. But here we go.
1) Delete your programming file from the computer. It’s seriously busted and is going to stay that way. You cannot save it.
2) Do a complete factory reset on the radio. Yes. You will and must lose all your programmed channels and settings. This is necessary and cannot be avoided.
3) THIS STEP IS CRITICAL! After the radio has been reset, and is as dumb as a newly minted rock, redo the unlock procedure (for U.S. radios) listed above in the first post in this subject, then plug it into the computer, and then read the radio back into the program.
4) This will become the un-corrupted basis for your new programming file. (You might want to save it now for later use.)
5) Rebuild your programmed channels, and all of the rest of the applicable parameters available in the programming windows. Including the VFO parameters. That means ALL programming options. (When you write the file back into the radio, it will overwrite everything in the radio.)
6) SAVE THIS DEFAULT FILE NOW — MARKED AS RESCUE! It will become your default backup, so you don’t have to do this all over again.
7) RTFM, and then function check and test ALL controls on the face of the radio and the microphone. If you wish to avoid unnecessary redos, frustrations and FUBARS, don’t forget nor neglect the Read The Fine Manual before testing. What you think is a recurrent problem may just be no more than a misunderstood feature or function. PEBCAKs and Operator Headspace issues are self generated. If any button performs unexpected functions … (Sigh!) … go back to step one, and do it all over again.
Okey dokey. That’s it for now. More solutions later as I stumble across the problems.