Yes twice and each time its crashes and JT Alert will not see anything???
Sent from
Mail for Windows
Have you installed the *CORRECT VERSION* of NET 5.0.8?
You must install the *DESKTOP* version and match 64 or 32 bit
to the version of JTAlert you have installed.
THIS IS ALL IN THE DOCUMENTATION.
On 2021-08-13 9:32 PM, Harry Hall via
groups.io wrote:
> Outstanding done logging back on track. A friend ham down the road has
> an old win7 computer of mine he says he uploaded to 2.50.0 with no
> problems I am going to hold off trying it again because nothing works on
> jtalert after install, no sound, no logging, no way to open any of the
> windows to show the call signs decoding. You just get one box full of
> ????? near the top on 2.50.0.
> Hers what we are using JTAlert 2.16.17 K5HLH {17M, ft8,hrd6+,Filter, #1}
> WSJT-X v2.40 by K1JT, G4WJS, K9AN, and IV3NWV
> Device name HarryHall-PC
> Processor AMD Phenom(tm) II X4 945 Processor 3.00 GHz
> Device ID C2DB017D-2A54-403B-B1A4-84D693AD8A5B
> Product ID 00330-50000-00000-AAOEM
> System type 64-bit operating system, x64-based processor
> Pen and touch No pen or touch input is available for this display
> Installed on 6/19/2020
> Experience Windows Feature Experience Pack 120.2212.3530.0
> Thanks for your time I am good on QRZ K5HLH 73’s
> *Sent: *Friday, August 13, 2021 4:20 PM
> *Subject: *Re: [HamApps] JTAlert 2.50.0 Not Working
> On 14/08/2021 8:08 am wrote:
> Up graded from 2.16.17 to 2.50.0 nothing worked. Reloaded back down
> to 2.16.17 took several days to start working again now it doubles
> the log entry back to HRD.
> Device name HarryHall-PC
> Processor AMD Phenom(tm) II X4 945 Processor 3.00 GHz
> Device ID C2DB017D-2A54-403B-B1A4-84D693AD8A5B
> Product ID 00330-50000-00000-AAOEM
> System type 64-bit operating system, x64-based processor
> Pen and touch No pen or touch input is available for this display
> Installed on 6/19/2020
> Experience Windows Feature Experience Pack 120.2212.3530.0
> "Nothing Works" is a very broad statement. You will need to be more
> specific about what is not working.
> As for Double-logging in HRD, that will be due to HRD listening for
> logging events from WSJT-X and also the logging instruction sent by
> JTAlert. You will need to turn off the "Enable logged contact ADIF
> broadcast" setting in WSJTX, under the "Secondary UDP Server
> (depreciated)" area of Reporting Tab of its Settings.
> If that was not enabled, the extra logging will be coming via the
> JTAlert "UDP Resend" option being enabled, you need to turn that off
> under the "Applications -> WSJT-X/JTDX" section of the JTAlert Settings
