Jim,
comments in line below.
On 22/12/2018 22:32, Jim Kennedy wrote:
So, as I read it, 32 MB is OK functionally, although 14 MB is the new
“normal” for shared memory as far as WSJT X is concerned.
The amount of shared memory required depends on how many instances of
WSJT-X you have running
Did you notice that it said the WIN32 versoin, and specifically said to
use the Win32 version even if you're on a 65 bit version of Windows.
It also points out you want the 1.02 version, NOT the 1.1.0.
The correct version is here:
https://slproweb.com/download/Win32OpenSSL_Light-1_0_2q.exe
Thank you John and Steve:
So, as I read it, 32 MB is OK functionally, although 14 MB is the new “normal”
for shared memory as far as WSJT X is concerned.
One of the other things I also noticed, just after going to Mojave, was that
the boot-up and log-in times are VERY slow, and opening apps is
Thanks Bill - you have given me a new term!
73,
Mark - KS4W
On Sat, Dec 22, 2018 at 3:24 PM Bill Somerville
wrote:
> you have gone off piste
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
>
With regard to the change in shmmax that has been commented on, I reduced the
size of the shared memory segment from 32 MB to a value (14MB) more in keeping
with the size of the arrays which are shared between wsjtx and the decoders.
This reduction will have no effect whatever on the
On 22/12/2018 18:10, Bill Mullin wrote:
I located the package, the current version is
_*Win64OpenSSL_Light-1_1_0j*_, which I'm sure makes no difference.
FWIW, there is a 1.0.2j lite also available.
Hi Bill,
you have gone off piste, v1.1.0 is the wrong package, please use the one
linked
Merry Christmas Joe
de AE5SB
From: Joe Taylor
Sent: Saturday, December 22, 2018 12:45 PM
To: Игорь Ч; WSJT software development
Subject: Re: [wsjt-devel] bug in 77-bit message packing
Hi Igor,
On 12/22/2018 05:10, Игорь Ч UA3DJY via wsjt-devel wrote:
> Hello
Hi Igor,
On 12/22/2018 05:10, Игорь Ч UA3DJY via wsjt-devel wrote:
Hello Joe,
.
There is a bug in packjt77 module observed when first character of the
base call is 'P' in the compound callsign.
It can be seen in ft8apset.f90 code, where message with user's callsign
DU6/VA3AAA is packed as
The following information is from the 2.0.0 FT8 User's guide:
*
You can download a suitable /OpenSSL/ package from _Windows OpenSSL
Packages_, you need the latest *Win32 v1.0.2 Lite* version (Note it
is the Win32 package even if you are using a 64-bit Windows
operating system)
Hi Jim,
I have the same model Mini, and the same OS upgrade caused issues. I
also noticed that the values from the sysctl.conf were different than
what is recommended; the shmall value was 8192 as in yours, and the
shmmax 33554432 even though the recommended is lower than that (and
the default
Hello Joe,
.
This behaviour is triggered by this code in the subroutine pack77_1:
.
if(index(w(1),'/P').ge.4 .or. index(w(2),'/P').ge.4) i3=2 !Type 2, with "/P"
...
if(index(w(1),'/P').ge.4 .or. index(w(1),'/R').ge.4) ipa=1
if(index(w(2),'/P').ge.4 .or. index(w(2),'/R').ge.4) ipb=1
.
Compоund
For MacOS, this is taken care by JT-Bridge.
Robert Rearden
AE5UV
_
On Dec 22, 2018, at 8:41 AM, Tom Ramberg via wsjt-devel
wrote:
May I suggest using JTAlert which has already taken care of this?
73 de Tom OH6VDA
> 22. des. 2018 kl. 00:17 skrev I Z :
>
> Suggestion
May I suggest using JTAlert which has already taken care of this?
73 de Tom OH6VDA
> 22. des. 2018 kl. 00:17 skrev I Z :
>
> Suggestion regarding colors.
> I really love what was done in 2.0. Finally a great logger, many thanks!
> I miss one enhancement though. When I see a message from one
Running v2.0.0 r78f75 on a PC with 32-bit Win 7 Pro.
I haven't managed to find any reference to the following two minor issues in
any of the
documentation or previous discussions via this group, so here goes...!
1. If I modify the standard Tx 6 message of 'CQ G0HDB IO82' by adding a
Hello Joe,
.
There is a bug in packjt77 module observed when first character of the base
call is 'P' in the compound callsign.
It can be seen in ft8apset.f90 code, where message with user's callsign
DU6/VA3AAA is packed as
'VA3AAA K9ABC RRR' and i3 equal to 1, while message with user's callsign
15 matches
Mail list logo
