locked Re: JTAlert 2.50.0 Not Working


Harry Hall
 

Well perhaps I am using the wrong wording I download the new version 2.50 etc

 

Sent from Mail for Windows

 

From: Tom Melvin
Sent: Friday, August 20, 2021 3:12 AM
To: Support@hamapps.groups.io
Subject: Re: [HamApps] JTAlert 2.50.0 Not Working

 

Harry

 

What ‘Crashes’ - first time seen the word crash mentioned in your posts.

 

Is it the install of Net 5.0.8 ? If so that is a Microsoft issue.

 

If it installed and JTAlert crashes pretty sure there will be an error message somewhere on the screen with crash details.

 

If you are seeing ????m in the main window   it is definitely an issue with JTAlert not getting any info from WSJT-X. The port is being blocked by OS, Anti-Malware, Anti Virus, incorrect settings WSJT-X.  Is there any heading in the box with ???? in it - may be worth posting a screen shot showing that box - not the whole desktop - cut/snip the window.

 

To rule out the Net issue can you confirm that it installs ok, no errors and PC is OK BEFORE you start to play with HRD, JTAlert, WSJT-X etc.

 

Regards

TOM

GM8MJV

 



On 20 Aug 2021, at 06:17, Harry Hall via groups.io <hhallcosd@...> wrote:

 

Yes twice and each time its crashes and JT Alert will not see anything???

 

Sent from Mail for Windows

 

From: Joe Subich, W4TV
Sent: Friday, August 13, 2021 7:53 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.50.0 Not Working

 

 

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.

 

73,

 

    ... Joe, W4TV

 

 

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} 

> (Updates)

> 

> 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

> 

> Installed RAM    8.00 GB

> 

> 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

> 

> Edition  Windows 10 Pro

> 

> Version 20H2

> 

> Installed on        ‎6/‎19/‎2020

> 

> OS build               19042.1165

> 

> Experience          Windows Feature Experience Pack 120.2212.3530.0

> 

> Thanks for your time I am good on QRZ K5HLH 73’s

> 

> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

> 

> *From: *HamApps Support (VK3AMA) <mailto:vk3ama.ham.apps@...>

> *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

> 

>     Installed RAM 8.00 GB

> 

>     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

> 

>     Edition Windows 10 Pro

> 

>     Version 20H2

> 

>     Installed on ‎6/‎19/‎2020

> 

>     OS build 19042.1165

> 

>     Experience Windows Feature Experience Pack 120.2212.3530.0

> 

> 

> OM,

> 

> "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 

> window.

> 

> de Laurie VK3AMA

> 

 

 

 

 

 

 

 

 

Join Support@HamApps.groups.io to automatically receive all group messages.