Re: [wsjt-devel] Custom frequencies lost after upgrade from 2.5.4 to 2.6.1

2023-03-05 Thread false via wsjt-devel
Thanks, that worked! On Saturday, March 4, 2023 at 11:30:04 PM PST, Reino Talarmo via wsjt-devel wrote: >From: false via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] >Before the upgrade, I renamed the old version (2.5.4) and when I open it, the >custom frequencies are present

Re: [wsjt-devel] FT-736 fails with 2.6.1

2023-03-05 Thread alawler mudhawk.com via wsjt-devel
Thank you, Chris and Michael - that worked perfectly! I'm back in business! —al WB1BQE From: Black Michael Sent: Sunday, March 5, 2023 6:38 PM To: wsjt-devel@lists.sourceforge.net Cc: alawler mudhawk.com Subject: Re: [wsjt-devel] FT-736 fails with 2.6.1 dif

Re: [wsjt-devel] FT-736 fails with 2.6.1

2023-03-05 Thread Black Michael via wsjt-devel
diff --git a/Transceiver/HamlibTransceiver.cpp b/Transceiver/HamlibTransceiver.cpp index 32ea283ea..12d420e32 100644 --- a/Transceiver/HamlibTransceiver.cpp +++ b/Transceiver/HamlibTransceiver.cpp @@ -659,7 +659,7 @@ int HamlibTransceiver::do_start ()        rmode_t mb;        pbwidth_t w {RIG_PAS

Re: [wsjt-devel] FT-736 fails with 2.6.1

2023-03-05 Thread alawler mudhawk.com via wsjt-devel
Morning Everybody, I recently upgraded to 2.6.1 (Built form source on Linux Mint) and am also seeing this problem. Is there a fix, or a pull request I can reference? (I'm building from source, so it's pretty easy to poke something in if the fix is known.) Thanks! --al WB1BQE _

Re: [wsjt-devel] FT-736 fails with 2.6.1

2023-03-05 Thread Black Michael via wsjt-devel
Here's the patch that fixes it. diff --git a/Transceiver/HamlibTransceiver.cpp b/Transceiver/HamlibTransceiver.cppindex 32ea283ea..12d420e32 100644--- a/Transceiver/HamlibTransceiver.cpp+++ b/Transceiver/HamlibTransceiver.cpp@@ -659,7 +659,7 @@ int HamlibTransceiver::do_start ()       rmode_t mb

Re: [wsjt-devel] FT-736 fails with 2.6.1

2023-03-05 Thread Chris Elmquist via wsjt-devel
Hi Al, Michael Black sent me a couple (Windows) versions to try and the final one seemed to fix it. He wrote (off list, on 27 Jan 2023), >The "dirty" is due to having a patch against it. > >That patch is already incorporated for the next release... > >Mike So perhaps you need to pull the source