The band was really up and down here, with some rapid QSB also. A few times I
saw signals with gaping holes in them, other times somone would disappear
entirely only to come back a couple minutes later. Propagation is a harsh
misteress!
73
-Jim
NU0c
On Wed, 14 Nov 2018 00:30:13 -0600, Stan Ga
Well, it did but obviously I missed it probably because I was looking for a
check box instead of an entry box. And it was late. In my defense I also did a
text search of the QSG and the online manual.
Thanks for your answer.
73
-Jim
NU0C
On Wed, 14 Nov 2018 08:46:22 -0500, Joe Taylor wrote:
>
>> On Nov 13, 2018, at 14:23, Marco Calistri via wsjt-devel
>> wrote:
>>
>> Despite my great interest of testing RC4, I'm a bit worry about the
>> possibility to meet other stations in my area using the new FT8
>> protocol, may be this being easy in the USA but I guess will be more
>> difficu
> On Nov 13, 2018, at 14:23, Marco Calistri via wsjt-devel
> wrote:
>
> Despite my great interest of testing RC4, I'm a bit worry about the
> possibility to meet other stations in my area using the new FT8
> protocol, may be this being easy in the USA but I guess will be more
> difficult in o
Hi Jim,
On 11/14/2018 12:54 AM, Jim Shorney NU0C wrote:
The only little nit I have os Operator call isn't sticky in the logging box.
Not that big a deal since I rarely do mutli-op, but I like to fill it in for
completeness if it is there and having to enter if for each QSO gets old. Am I
missin
Same here. I too compiled from source on Kubuntu 18.04. Good to work
you Jim.
Could have been band conditions, but it seem like I had a few decode
problems with stations that the exchanged signal levels should have
decoded on both ends.
Colors were all gray at first, so I missed a few that
On Tue, 13 Nov 2018 09:17:06 -0500, Joe Taylor wrote:
>A fourth candidate release ("RC4") of WSJT-X 2.0 is now available for
>download and use by beta testers.
So far, so good. Compiled from source in Kubuntu 18.04. Madea handful of
contacts on 40M late this evening. No flashes, crashes, waili
Don AA5AU
From: Marco Calistri via wsjt-devel
To: wsjt-devel@lists.sourceforge.net
Cc: Marco Calistri
Sent: Tuesday, November 13, 2018 3:26 PM
Subject: Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc4
Hi Joe,
Thanks for the new WSJT-X release, I think I'm going to test it right tod
nt
Sent: Tuesday, November 13, 2018 8:22 AM
Subject: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc4
A fourth candidate release ("RC4") of WSJT-X 2.0 is now available for
download and use by beta testers.
Changes in RC4 relative to RC3 include the following:
- Fix the "cann
Hi Joe,
Thanks for the new WSJT-X release, I think I'm going to test it right today.
Despite my great interest of testing RC4, I'm a bit worry about the
possibility to meet other stations in my area using the new FT8
protocol, may be this being easy in the USA but I guess will be more
difficult i
Thanks to all who have installed RC4, read the new Quick-Start Guide,
and proceeded to make QSOs using the new FT8 protocol.
Transition to the v2.0 protocol seems to be going smoothly. Most people
with RC4 are using the standard FT8 dial frequencies and remembering to
transmit above Tx Freq 2
Maybe it would be okay if the 5-min no-mouse watchdog was active only for HF
FT8? And it superseded any WD timer settings?
George J Molnar
KF2T - Virginia, USA
> On Nov 13, 2018, at 12:58 PM, Hasan al-Basri
> wrote:
>
> The five minute mouse timer business is going too far. Long MSK144 qsos o
The five minute mouse timer business is going too far. Long MSK144 qsos
over difficult paths, should not require the OP to be chained to the desk.
Several ops are running (on a clear freq), for hours to complete. They
aren't sitting in front of the mouse. The developers may not approve of
this ope
On Tue, Nov 13, 2018 at 10:35 AM Bill Somerville
wrote:
> On 13/11/2018 15:16, Richard Shaw wrote:
> > BUILDSTDERR: In file included from
> > /builddir/build/BUILD/wsjtx-2.0.0-rc4/wsjtx/models/FoxLog.cpp:13:0:
> > BUILDSTDERR:
> > /builddir/build/BUILD/wsjtx-2.0.0-rc4/wsjtx/qt_db_helpers.hpp: In
Two thumbs up from the west coast.
73 John W7CD
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Tuesday, November 13, 2018 6:17 AM
To: WSJT software development
Subject: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc4
A fourth candidate release ("RC4")
Congrats, dev team. Running smoothly so far (Mac OS 10.14).
Not sure I understand the intent of the five minute no-mouse timer. Isn’t this
essentially competing with the watchdog? Not sure of a use case that requires
this second timer.
Can you elaborate?
Thanks
George J Molnar
KF2T, Arlingt
On 13/11/2018 15:16, Richard Shaw wrote:
BUILDSTDERR: In file included from
/builddir/build/BUILD/wsjtx-2.0.0-rc4/wsjtx/models/FoxLog.cpp:13:0:
BUILDSTDERR:
/builddir/build/BUILD/wsjtx-2.0.0-rc4/wsjtx/qt_db_helpers.hpp: In
constructor
'ConditionalTransaction::ConditionalTransaction(QSqlTableMo
I'm seeing the following error when building for EPEL 7 (CentOS/SL/Etc)
/usr/bin/c++ -DBIGSYM=1 -DCMAKE_BUILD -DQT5 -DQT_CORE_LIB -DQT_GUI_LIB
-DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_DEBUG_OUTPUT -DQT_NO_WARNING_OUTPUT
-DQT_PRINTSUPPORT_LIB -DQT_SQL_LIB -DQT_WIDGETS_LIB -DUDP_STATIC_DEFINE
-DUNIX
A fourth candidate release ("RC4") of WSJT-X 2.0 is now available for
download and use by beta testers.
Changes in RC4 relative to RC3 include the following:
- Fix the "cannot open file fort.81" bug
- Avoid too many redirect loops related to openSSL support
- Fix the auto-generated messag
19 matches
Mail list logo
