Thanks for the quick response Jim. Yes Chirp was closed before I executed the install file. The installation confirms install location, and then proceeds to "churn & burn" for several minutes before giving me a successful message. I just repeated the process again to double check .. and this time I noticed that the default install location was not where my 20151126 version had been installed (go figure). Going to the default location I found the 2016 version. So, 1 issue has been resolved. I still have the other 2 issues that I reported last night (message 3 below) with the 2016 version (i.e. changing DTCS elements and the radio going into transmit after uploading to the radio). -- John 73's de K9RSQ On 3/15/2016 3:00 PM, chirp_users-request@intrepid.danplanet.com wrote:

Today's Topics:

1. Chirp Update not replacing old version (John Randle)
2. Re: Chirp Update not replacing old version (Jim Unroe)
3. BAOFENG UV-5Rs acting strange when programming with	Chirp
   (John Randle)

---

Message: 1 Date: Mon, 14 Mar 2016 23:30:18 -0400 From: John Randle john.randle@tds.net Subject: [chirp_users] Chirp Update not replacing old version To: chirp_users@intrepid.danplanet.com Message-ID: 56E781CA.1080207@tds.net Content-Type: text/plain; charset=utf-8; format=flowed

I have downloaded the daily build for Windows 10 (20160309), but when I execute the install file my previous version of Chirp (20151126) is not replaced. Is it necessary to uninstall the previous version before executing the new version's install file? -- John 73's de K9RSQ

---

Message: 2 Date: Mon, 14 Mar 2016 23:34:16 -0400 From: Jim Unroe rock.unroe@gmail.com Subject: Re: [chirp_users] Chirp Update not replacing old version To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Message-ID: CADnO8U6wd233F7S4VY5Aom70RsTLT-XTqfe2v4rJniGtL1L1AA@mail.gmail.com Content-Type: text/plain; charset=UTF-8

On Mon, Mar 14, 2016 at 11:30 PM, John Randle john.randle@tds.net wrote:

...

I have downloaded the daily build for Windows 10 (20160309), but when I execute the install file my previous version of Chirp (20151126) is not replaced. Is it necessary to uninstall the previous version before executing the new version's install file? -- John 73's de K9RSQ

No need to delete it. CHIRP removes it as part of the install. Did you have CHIRP closed?

Jim KC9HI

---

Message: 3 Date: Mon, 14 Mar 2016 23:50:17 -0400 From: John Randle john.randle@tds.net Subject: [chirp_users] BAOFENG UV-5Rs acting strange when programming with Chirp To: chirp_users@intrepid.danplanet.com Message-ID: 56E78679.201@tds.net Content-Type: text/plain; charset=utf-8; format=flowed

I have been maintaining several UV5R's with Chirp for a couple of years without any issues. I am currently running Chirp Daily Build 20151126 on W10 to program several UV5R's. I have recently experienced two strange programming operation issues, with all the UV5R's, that I have not previously encountered. First problem: After downloading the current configuration of the UV5R's, I then proceeded to add some new memory channels that use Digital Coded Squelch settings. When programming the DCS settings, I first set "DTCS", then I set the individual T-DCS and R-DCS codes and then I set Cross to "Tone -> Tone" (as this is what the existing DCS memory channels reflect), but as soon as I set the offset direction, Chirp changes "DTCS" to "Cross" and changes "Tone -> Tone" to "DTCS->". As these settings are not what is required (or at least what is currently reflected in the older DCS memory channels), I then have to go back and reset "DTCS->" to "Tone -> Tone" and "Cross" to "DTCS". Is there any reason why my initial inputs are being over-ridden? Second problem: After successfully uploading a new configuration to the UV5-R's, the UV5R's automatically go into transmit mode about 5 seconds after they restart if the programming cable is left connected to the radio. This seems to be a new issue that I had not previously experienced. Any suggestions on either problem will be greatly appreciated. -- John 73's de K9RSQ