On Wed, Mar 5, 2025 at 8:42 AM Brian Morrison via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> On Wed, 5 Mar 2025 04:29:24 -0700
> Jim Reisert AD1C via wsjt-devel
> wrote:
>
> > I just tried to update the data files in WSJT-X 2.7.0 in this order:
> >
>
I just tried to update the data files in WSJT-X 2.7.0 in this order:
1. CTY.DAT
2. LoTW
3. HamLib
Both #1 and #2 updated without any problems. But when I tried to update
Hamlib, I received the following error. What does CTY.DAT have to do with
updating Hamlib?
[image: wsjtx_2025-03-05_04-25-
On Fri, Dec 27, 2024 at 12:55 PM ATKINSON NOEL W9FR wrote:
Hi, During F/H QSO with TO0J, my first TX was moved to 674 his highest of 3
> streams, but he didn’t decode it, the next time, my TX was moved to 374
> Down 300 Hz. Is this a new feature with F/H. Will it also do Up 300 Hz and
> Down 300
On Sun, Aug 25, 2024 at 3:21 PM Hasan N0AN wrote:
Anyone in the continental USA that did not copy N5J at any time during
> their stay when they operated on SuperFox, was obviously not there when
> propagation peaked in their area. Bad timing. It had nothing to do with
> SuperFox vs. standard F/H.
It's a callsign hash collision. DP1POL has not been operating on those
frequencies.
On Mon, Jan 29, 2024 at 4:07 PM V. Scott Moore via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> I saw similar decodes. I attributed it to two stations on the same
> frequency. The PJ5 was very stron
On Thu, Dec 7, 2023 at 2:46 AM Reino Talarmo wrote:
> From: Jim Reisert AD1C via wsjt-devel [mailto:
> wsjt-devel@lists.sourceforge.net]
> > Sent: Thursday, December 7, 2023 3:51 AM
>
> > 3. 4U is listed as a prefix for Italy.
> Regarding #3, this was done so that "
