Any news in getting support for radioddity gs5b?
From: chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of chirp_users-request@intrepid.danplanet.com <chirp_users-request@intrepid.danplanet.com>
Sent: Wednesday, June 24, 2020 12:00:02 PM
To: chirp_users@intrepid.danplanet.com <chirp_users@intrepid.danplanet.com>
Subject: chirp_users Digest, Vol 138, Issue 20
 
Send chirp_users mailing list submissions to
        chirp_users@intrepid.danplanet.com

To subscribe or unsubscribe via the World Wide Web, visit
        http://intrepid.danplanet.com/mailman/listinfo/chirp_users
or, via email, send a message with subject or body 'help' to
        chirp_users-request@intrepid.danplanet.com

You can reach the person managing the list at
        chirp_users-owner@intrepid.danplanet.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of chirp_users digest..."


Today's Topics:

   1. Re: Baofeng GT-1 can read radio but cannot write (wtforme)
   2. Chirp program (George Piek)
   3. Re: Chirp program (Jim Unroe)
   4. Re: Chirp program (George Piek)
   5. Re: Chirp program (Jim Unroe)
   6. Re: Radioddity QB25 (Byron Boggs)
   7. Re: Chirp program (George Piek)
   8. Re: Chirp program (George Piek)
   9. Re: Chirp program (Jim Unroe)
  10. Re: Radioddity QB25 (Jim Unroe)
  11. Re: Radioddity QB25 (Byron Boggs)
  12. Re: Radioddity QB25 (Jim Unroe)
  13. unable to install (Donald Jacob)


----------------------------------------------------------------------

Message: 1
Date: Tue, 23 Jun 2020 15:10:22 -0400
From: wtforme <wtforme@hotmail.com>
Subject: Re: [chirp_users] Baofeng GT-1 can read radio but cannot
        write
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <DM5PR2001MB1722C010C05DC6D42606A8A4BF940@DM5PR2001MB1722.namprd20.prod.outlook.com>
       
Content-Type: text/plain; charset="utf-8"

Thank you. I finally got the factory software to work. I had to turn off
the U ART FIFO BUFFERS.

On Tue, Jun 23, 2020, 1:54 PM W Paul Mills <ac0hy@wpmills.com> wrote:

> Make absolutely sure that the cable is fully plugged into the radio. It is
> not unusual for them to not mate up well.
>
> On 6/20/20 11:37 PM, wtforme wrote:
>
>   I have the latest version of chirp installed. I am showing the Prolific
> driver on com 5 and have retrograded it to version 3.2.00. I know it is a
> cheap ass cable but what is baffling me is why I can read but not write.
>
> I am running Windows 10.
>
> I get the following error: Failed to send block to radio at 0000.
>
> Thanks for any hep
>
> _______________________________________________
> chirp_users mailing listchirp_users@intrepid.danplanet.comhttp://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Paul AC0HY at ac0hy@wpmills.com
> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
>
>
> --
> /**************************************************
> * Amateur Radio Station AC0HY                     *
> * W. Paul Mills         SN807                     *
> * Assistant EC Alpha-1 ARES Shawnee/Wabaunsee, KS *
> * President Kaw Valley Amateur Radio Club         *
> **************************************************/
>
> _______________________________________________
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Bob at wtforme@hotmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe@intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200623/e409ddf9/attachment-0001.html

------------------------------

Message: 2
Date: Wed, 24 Jun 2020 10:21:39 +0200
From: George Piek <georgepiek7@gmail.com>
Subject: [chirp_users] Chirp program
To: chirp_users@intrepid.danplanet.com
Message-ID:
        <CALfNQNupsbOz3HyFkAa0h9Tnn0_HVCxgAAKTq9-6H=h9LqJgPQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Good day to you, I am using Chirp for programming my UV 5 R Baofeng Radio.
Suddenly when I request to "Download from Radio" I receive the message "
Not enough data" Why would that be please. I have used it before and had no
problems.

Regards
George
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/37d27225/attachment-0001.html

------------------------------

Message: 3
Date: Wed, 24 Jun 2020 08:11:31 -0400
From: Jim Unroe <rock.unroe@gmail.com>
Subject: Re: [chirp_users] Chirp program
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <CADnO8U6ai82_+PqD-AJGZx7wwBRhhp_hntyiudRVX4-8g9-=Ug@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

On Wed, Jun 24, 2020 at 4:10 AM George Piek <georgepiek7@gmail.com> wrote:
>
> Good day to you, I am using Chirp for programming my UV 5 R Baofeng Radio. Suddenly when I request to "Download from Radio" I receive the message " Not enough data" Why would that be please. I have used it before and had no problems.
>
> Regards
> George

Hi George,

>From the information you have provided, I am going to guess that you
may be selecting the wrong model. Here's why.

There is no CHIRP driver for any radio model that provides a " Not
enough data" message to the user. The word "enough" doesn't even show
up in any message for any radio driver module. So looking through all
of the Baofeng radio driver modules for messages that contain both
"not" and "data" I find "baofeng_common.py". It contains the following
message: "Error reading data from radio: not the amount of data we
want." Assuming this message is the actual message that you are
seeing, this allows me to get a list of all radio driver modules that
use "baofeng_common.py". They are as follows.

baofeng_wp970i.py
gmrsuv1.py
mursv1.py
uv6r.py
uv5x3.py

>From the above list only "baofeng_wp970i.py" and "uv6r.py" use the
Vendor: Baofeng selection. Assuming that "UV 5 R" means "UV-5R", if I
hook up a UV-5R and choose Vendor: Baofeng and Model: UV-6R, I get the
"Error reading data from radio: not the amount of data we want."
message (screen capture attached).

Since the "UV-5R" and "UV-6R" selections are visually similar, I think
you may accidentally be choosing "UV-6R" instead of choosing "UV-5R".

Jim KC9HI
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2020-06-24 07_49_42-.png
Type: image/png
Size: 6267 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/aa3e2b99/attachment-0001.png

------------------------------

Message: 4
Date: Wed, 24 Jun 2020 15:23:01 +0200
From: George Piek <georgepiek7@gmail.com>
Subject: Re: [chirp_users] Chirp program
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <CALfNQNtp_E8335EJP3gLf8_pCrAXfh_Bim4Uy=2Gims5A079hQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi, yes you are correct on the actual msg. No I have made double sure in
selecting the correct radio i.e. UV 5 R. As I said, cannot understand why
because I had downloaded from same radio previously.

Regards
George

On Wed, 24 Jun 2020, 14:14 Jim Unroe, <rock.unroe@gmail.com> wrote:

> On Wed, Jun 24, 2020 at 4:10 AM George Piek <georgepiek7@gmail.com> wrote:
> >
> > Good day to you, I am using Chirp for programming my UV 5 R Baofeng
> Radio. Suddenly when I request to "Download from Radio" I receive the
> message " Not enough data" Why would that be please. I have used it before
> and had no problems.
> >
> > Regards
> > George
>
> Hi George,
>
> >From the information you have provided, I am going to guess that you
> may be selecting the wrong model. Here's why.
>
> There is no CHIRP driver for any radio model that provides a " Not
> enough data" message to the user. The word "enough" doesn't even show
> up in any message for any radio driver module. So looking through all
> of the Baofeng radio driver modules for messages that contain both
> "not" and "data" I find "baofeng_common.py". It contains the following
> message: "Error reading data from radio: not the amount of data we
> want." Assuming this message is the actual message that you are
> seeing, this allows me to get a list of all radio driver modules that
> use "baofeng_common.py". They are as follows.
>
> baofeng_wp970i.py
> gmrsuv1.py
> mursv1.py
> uv6r.py
> uv5x3.py
>
> >From the above list only "baofeng_wp970i.py" and "uv6r.py" use the
> Vendor: Baofeng selection. Assuming that "UV 5 R" means "UV-5R", if I
> hook up a UV-5R and choose Vendor: Baofeng and Model: UV-6R, I get the
> "Error reading data from radio: not the amount of data we want."
> message (screen capture attached).
>
> Since the "UV-5R" and "UV-6R" selections are visually similar, I think
> you may accidentally be choosing "UV-6R" instead of choosing "UV-5R".
>
> Jim KC9HI
> _______________________________________________
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to George Piek at georgepiek7@gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe@intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/bedb802a/attachment-0001.html

------------------------------

Message: 5
Date: Wed, 24 Jun 2020 09:51:58 -0400
From: Jim Unroe <rock.unroe@gmail.com>
Subject: Re: [chirp_users] Chirp program
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <CADnO8U4aGZwJwaGAoGSW6Q1sEOk+3SuPk-q4ojSZBWWwXJtPEw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

On Wed, Jun 24, 2020 at 9:26 AM George Piek <georgepiek7@gmail.com> wrote:
>
> Hi, yes you are correct on the actual msg. No I have made double sure in selecting the correct radio i.e. UV 5 R. As I said, cannot understand why because I had downloaded from same radio previously.
>
> Regards
> George
>

Then please supply some additional information. You've supplied very
little. Such as...

CHIRP version:
Operating system and version (Windows, Linux, macOS):
Programming cable type (which USB-to-Serial chip is inside):
Attach clean debug.log file:

The "How To Report Issues" page shows how to find the debug.log file
for all 3 supported operating systems.
https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues

A "clean" debug.log file is one where you close CHIRP, open CHIRP,
cause the error and finally close CHIRP.

Jim KC9HI


------------------------------

Message: 6
Date: Wed, 24 Jun 2020 14:01:34 +0000
From: Byron Boggs <kc8ue@hotmail.com>
Subject: Re: [chirp_users] Radioddity QB25
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <DM6PR07MB6427263109439DE673818BD3EF950@DM6PR07MB6427.namprd07.prod.outlook.com>
       
Content-Type: text/plain; charset="us-ascii"

I once again contacted Radioddity Support.  He installed the factory software, set it up for me and then set up Chirp for me.  I have my radio programmed.
He said to open the factory software first, then open Chirp as the Administrator and it works.  I does work.

Sent from Byron Boggs
kc8ue@hotmail.com

________________________________
From: chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of Jim Unroe <rock.unroe@gmail.com>
Sent: Monday, June 22, 2020 10:53:22 AM
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Subject: Re: [chirp_users] Radioddity QB25

On Fri, Jun 19, 2020 at 2:00 PM Jim Unroe <rock.unroe@gmail.com> wrote:
>
> On Fri, Jun 19, 2020 at 1:23 PM Byron Boggs <kc8ue@hotmail.com> wrote:
> >
> > I purchased the QB25 with hopes of installing it in my pickup truck.  I have two programming cables for it, the one that came with the radio and an FTDI cable that I purchased recently.
> > My problem us error messages.  Depending on the port configuration, I get an error message that states it failed to identify the radio, OR the it failed to enter the clone mode.  I have tried other variants of this radio like the QTY7900.  I have tried Windows 10 and an old laptop with Windows XP.  Same error message on either operating system.  Searching through requests I see others have experienced the same issue.  I have clicked on the post for that issue but it doesn't do anything and I am at a loss as to what I need to do.  I have used Chirp to program the little UV5R units without issue.
> > Suggestions will be greatly appreciated
> >
> > Byron
> > Kc8ue
>
> Hi Byron,
>
> Your QB25 most likely has an MCU-Version that is not recognized by
> CHIRP. I recently submitted a patch to add one in May (VC4114) and
> another one in June (VC4104) but the most recent one hasn't been
> accepted yet. There are quite a few patches in the queue to be
> accepted but the process has been slowed down by the Covid-19
> pandemic. Unless it has an even different MCU-Version than the one I
> just added, it will be supported in the next CHIRP daily build. You
> can determine the MCU-Version using the factory programming software.
> It will be shown in the bottom status display area.
>
> Jim KC9HI

Assuming that your radio's MCU-version is VC4114, today's CHIRP daily
build should allow it to be recognized.

Jim KC9HI
_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Byron at kc8ue@hotmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/697c248f/attachment-0001.html

------------------------------

Message: 7
Date: Wed, 24 Jun 2020 16:15:59 +0200
From: George Piek <georgepiek7@gmail.com>
Subject: Re: [chirp_users] Chirp program
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <CALfNQNuaDCR3BqJT1v1t8AKcyHWBNGN4ODKdxfttd=1-w1ukxg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

My operating system is Windows 10. Version of Chirp is latest , 20200622


On Wed, 24 Jun 2020, 15:54 Jim Unroe, <rock.unroe@gmail.com> wrote:

> On Wed, Jun 24, 2020 at 9:26 AM George Piek <georgepiek7@gmail.com> wrote:
> >
> > Hi, yes you are correct on the actual msg. No I have made double sure in
> selecting the correct radio i.e. UV 5 R. As I said, cannot understand why
> because I had downloaded from same radio previously.
> >
> > Regards
> > George
> >
>
> Then please supply some additional information. You've supplied very
> little. Such as...
>
> CHIRP version:
> Operating system and version (Windows, Linux, macOS):
> Programming cable type (which USB-to-Serial chip is inside):
> Attach clean debug.log file:
>
> The "How To Report Issues" page shows how to find the debug.log file
> for all 3 supported operating systems.
> https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
>
> A "clean" debug.log file is one where you close CHIRP, open CHIRP,
> cause the error and finally close CHIRP.
>
> Jim KC9HI
> _______________________________________________
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to George Piek at georgepiek7@gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe@intrepid.danplanet.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/83fec9a8/attachment-0001.html

------------------------------

Message: 8
Date: Wed, 24 Jun 2020 16:19:38 +0200
From: George Piek <georgepiek7@gmail.com>
Subject: Re: [chirp_users] Chirp program
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <CALfNQNsnJxqq=T3ZCYVvqiRiJZA=CCONHFfkBJPa0bDkT-Qh8A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

And my cable is a Boafeng cable purchased from China shop. As I said, cable
worked before.


On Wed, 24 Jun 2020, 16:15 George Piek, <georgepiek7@gmail.com> wrote:

> My operating system is Windows 10. Version of Chirp is latest , 20200622
>
>
> On Wed, 24 Jun 2020, 15:54 Jim Unroe, <rock.unroe@gmail.com> wrote:
>
>> On Wed, Jun 24, 2020 at 9:26 AM George Piek <georgepiek7@gmail.com>
>> wrote:
>> >
>> > Hi, yes you are correct on the actual msg. No I have made double sure
>> in selecting the correct radio i.e. UV 5 R. As I said, cannot understand
>> why because I had downloaded from same radio previously.
>> >
>> > Regards
>> > George
>> >
>>
>> Then please supply some additional information. You've supplied very
>> little. Such as...
>>
>> CHIRP version:
>> Operating system and version (Windows, Linux, macOS):
>> Programming cable type (which USB-to-Serial chip is inside):
>> Attach clean debug.log file:
>>
>> The "How To Report Issues" page shows how to find the debug.log file
>> for all 3 supported operating systems.
>> https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
>>
>> A "clean" debug.log file is one where you close CHIRP, open CHIRP,
>> cause the error and finally close CHIRP.
>>
>> Jim KC9HI
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users@intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to George Piek at georgepiek7@gmail.com
>> To unsubscribe, send an email to
>> chirp_users-unsubscribe@intrepid.danplanet.com
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/0212ab69/attachment-0001.html

------------------------------

Message: 9
Date: Wed, 24 Jun 2020 10:38:57 -0400
From: Jim Unroe <rock.unroe@gmail.com>
Subject: Re: [chirp_users] Chirp program
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <CADnO8U5Y78+JV6qJRGEU_v7NsG7yidtGy_P8-7ov9E2X5XN9-A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

On Wed, Jun 24, 2020 at 10:28 AM George Piek <georgepiek7@gmail.com> wrote:
>
> And my cable is a Boafeng cable purchased from China shop. As I said, cable worked before.
>
debug.log?

Jim KC9HI


------------------------------

Message: 10
Date: Wed, 24 Jun 2020 10:47:24 -0400
From: Jim Unroe <rock.unroe@gmail.com>
Subject: Re: [chirp_users] Radioddity QB25
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <CADnO8U7o7T3nAPr-gHH+wcggbH3H5-ZAR+2T1w85HpBB7YYiDw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

On Wed, Jun 24, 2020 at 10:05 AM Byron Boggs <kc8ue@hotmail.com> wrote:
>
> I once again contacted Radioddity Support.  He installed the factory software, set it up for me and then set up Chirp for me.  I have my radio programmed.
> He said to open the factory software first, then open Chirp as the Administrator and it works.  I does work.
>
> Sent from Byron Boggs
> kc8ue@hotmail.com

You don't need the factory software. The reason it works now is
because the CHIRP daily build that was issued a couple of days ago
added an additional MCU-Version (which is probably the one your radio
has - VC4114). Prior to that, your radio couldn't be identified. You
can verify this by looking at the following CHIRP setting...

Settings -> Other Settings -> Fingerprint: {MCU-version}

The MCU-Version is also displayed in the bottom status display area of
the factory programming software.

Jim KC9HI


------------------------------

Message: 11
Date: Wed, 24 Jun 2020 15:06:57 +0000
From: Byron Boggs <kc8ue@hotmail.com>
Subject: Re: [chirp_users] Radioddity QB25
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <DM6PR07MB6427D1062893AAB3F0BE0539EF950@DM6PR07MB6427.namprd07.prod.outlook.com>
       
Content-Type: text/plain; charset="us-ascii"

Someone asked what the MCU version of my radio was.  It is VC4104.

Sent from Byron Boggs
kc8ue@hotmail.com
________________________________
From: chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of Jim Unroe <rock.unroe@gmail.com>
Sent: Wednesday, June 24, 2020 10:47:24 AM
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Subject: Re: [chirp_users] Radioddity QB25

On Wed, Jun 24, 2020 at 10:05 AM Byron Boggs <kc8ue@hotmail.com> wrote:
>
> I once again contacted Radioddity Support.  He installed the factory software, set it up for me and then set up Chirp for me.  I have my radio programmed.
> He said to open the factory software first, then open Chirp as the Administrator and it works.  I does work.
>
> Sent from Byron Boggs
> kc8ue@hotmail.com

You don't need the factory software. The reason it works now is
because the CHIRP daily build that was issued a couple of days ago
added an additional MCU-Version (which is probably the one your radio
has - VC4114). Prior to that, your radio couldn't be identified. You
can verify this by looking at the following CHIRP setting...

Settings -> Other Settings -> Fingerprint: {MCU-version}

The MCU-Version is also displayed in the bottom status display area of
the factory programming software.

Jim KC9HI
_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Byron at kc8ue@hotmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/5eaa24e1/attachment-0001.html

------------------------------

Message: 12
Date: Wed, 24 Jun 2020 12:36:18 -0400
From: Jim Unroe <rock.unroe@gmail.com>
Subject: Re: [chirp_users] Radioddity QB25
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <CADnO8U4BD-2cCbD2bLmsUfos_Wj=cfP77p6Z-E+NpmuJv0XQVw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

On Wed, Jun 24, 2020 at 11:18 AM Byron Boggs <kc8ue@hotmail.com> wrote:
>
> Someone asked what the MCU version of my radio was.  It is VC4104.
>
> Sent from Byron Boggs
> kc8ue@hotmail.com

The VC4014 MCU version was added late last month. You need a CHIRP
daily-200603 or later to support your radio.

Jim KC9HI


------------------------------

Message: 13
Date: Wed, 24 Jun 2020 11:20:46 -0700
From: Donald Jacob <wb5eku@gmail.com>
Subject: [chirp_users] unable to install
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
        <CABCjCMCuD1k32yyncnmYn23O-9xdpAzcC2ai1EHhVyX5rv-B3A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

On Windows 10 system,
I tried to install daily 20200622-installer.exe
and received this message. I tried running as Administrator with same
results.
Can't write: C:\Program Files (x86)\CHIRP\_hashlib.pyd

I do have an earlier version installed, should I remove that one?
If so, what will happen to my data for the older version?

Thanks

Don
WB5EKU
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/2c05b4e0/attachment-0001.html

------------------------------

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

End of chirp_users Digest, Vol 138, Issue 20
********************************************