Re: [chirp_users] Chirp no work - on Windows, try Linux if possible

If you download the source, and have Python (2) installed, you could update that file and test it. You don't need an executable. Joe Pizzi KI5LST On 1/6/2021 6:20 AM, John wrote: This is the third post I have read in the last couple of weeks that mentions a bug in COM port handling where the

Re: [chirp_users] Chirp no work - on Windows, try Linux if possible

Hi. In Windows, after connecting the cable (no radio needed on the other end, nor Chirp running.) Go into the Device Manager, and look for the COM/Serial port device lists. If there are no Yellow Triangle signs, and you only see one COM port, that is the one you tell Chirp about. If you see mor

Re: [chirp_users] (None) Entries in Chirp

Tnx Pat, 73, Billy Original Message Subject: Re: [chirp_users] (None) Entries in Chirp From: Pat Anderson Date: Wed, January 06, 2021 9:02 am To: Discussion of CHIRP Billy,+2 on what Nigel says. Fire up CHIRP. Read t

Re: [chirp_users] Which version do I really have?

On Wed, Jan 6, 2021 at 11:43 AM Don Brett wrote: > > I re-downloaded and installed the flatpak file (just in case); flatpak > installer said the latest version was already installed, as expected. Does > anyone know which version I actually have? > > Don The flatpak version of CHIRP is somethin

Re: [chirp_users] Which version do I really have?

Assuming you have the latest version, is help/about correct on your's? Virus-free. www.avast.com

Re: [chirp_users] Which version do I really have?

Yes, it says "CHIRP daily-20201121, GTK 2.24.32, PyGTK 2.24.0, Python 2.7.17", but I just installed "chirp-daily-20201221.flatpak". Don Virus-free. www.avast.com

Re: [chirp_users] Which version do I really have?

Doesn't it say under help and about? - Original Message - From: Don Brett To: Discussion of CHIRP Sent: Wednesday, January 06, 2021 10:40 AM Subject: Re: [chirp_users] Which version do I really have? I re-downloaded and installed the flatpak file (just in case); flatpak installer sai

Re: [chirp_users] Which version do I really have?

I re-downloaded and installed the flatpak file (just in case); flatpak installer said the latest version was already installed, as expected. Does anyone know which version I actually have? Don

Re: [chirp_users] (None) Entries in Chirp

On Wed, Jan 6, 2021 at 8:34 AM wrote: > > Yes, I am a wet-behind-the-ears Chirp user. I have read and studied the FAQ, > WIKI, and documentation. I am running the latest version. I am working with > on Baofeng UV-82. I have three minor questions to clarify my Chirp > understanding. > > 1. On pa

Re: [chirp_users] Chirp no work - on Windows, try Linux if possible

Billy, +2 on what Mark says about using LInux instead of Windows with CHIRP. I use a Chromebook with Ubuntu Linux installed as my daily driver, but you can run Linux on any system.. Linux has a bit of a learning curve but getting CHIRP installed and using it in Linux is as simple as following som

Re: [chirp_users] (None) Entries in Chirp

Billy, +2 on what Nigel says. Fire up CHIRP. Read the image from your radio, edit the image in CHIRP, and write it back to your radio. Pat Anderson KD7OAC On Wed, Jan 6, 2021 at 6:22 AM Nigel A. Gunn G8IFF/W8IFF wrote: > Please forget about .csv files and just work with .img files in ther Chir

Re: [chirp_users] (None) Entries in Chirp

Please forget about .csv files and just work with .img files in ther Chirp editor screen. Saves all manner of problems. > On 06/01/2021 08:31 bwmo...@slidesnmoore.com wrote: > > > Yes, I am a wet-behind-the-ears Chirp user. I have read and studied the > FAQ, WIKI, and documentation.

[chirp_users] (None) Entries in Chirp

Yes, I am a wet-behind-the-ears Chirp user. I have read and studied the FAQ, WIKI, and documentation. I am running the latest version. I am working with on Baofeng UV-82. I have three minor questions to clarify my Chirp understanding.1. On page https://chirp.danplanet.com/projects/chirp/wiki/Memory

Re: [chirp_users] Chirp no work - on Windows, try Linux if possible

This is the third post I have read in the last couple of weeks that mentions a bug in COM port handling where the COM port number is above 10. I believe this is an straightforward fix. The problem appear to be in platform.py which generates a list of available COM ports. It correctly starts by