Date   

locked Re: Decode not clearing

John Holmes W9ILY
 
Edited

Laurie,

i rolled back to RC155 and there was no change. I think you are correct in that the call clear instruction is not being received. When I double click on the number of QSOs, it sometimes clears but other times a "waiting" circular image is shown like the CPU is maxed out. I have included several screen shots including one where of Task Manager where JTAlert is not running. JTAlert is using a lot of processing. I had completely rebooted and reloaded the JTAlert program after all this started and there was no difference.
John W9ILY


locked Re: Convert free-floating "Callsigns No1" window to being part of single window ... as before

Peter Laws
 

You will eventually have a one window when the old JTAlert main window code is fully migrated to the new .NET 5 code base and the old window is removed. But that change is not imminent, there is still a considerable amount of work to undertake to complete the code migration.
"Transitional" is all I needed to hear - I will be patient. :-)

As I noted, the new callsigns window seems better and more functional
and this has been borne out by fiddling around on 50 MHz today ... but
it's superfluous because there is already a window. Seriously, I'll
try to be patient!

I did note that JTAlert will now look for updates by itself, which is
a BIG help - thanks for that.




--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


locked Re: Convert free-floating "Callsigns No1" window to being part of single window ... as before

HamApps Support (VK3AMA)
 

On 22/05/2021 4:16 am, Peter Laws wrote:
Subject: line says it all.  I have looked all through settings ... and the "other" settings under the superflous window's "gear" ("Follow JTAlert window" ain't it).  I would just like *one* JTAlert Windows ... as it was before.

Lest anyone think I just want things to go back to where they were "in the day", the new callsign window looks much more useful ... if it was docked at the bottom of WSJT-X 2.3.1 ...

You will eventually have a one window when the old JTAlert main window code is fully migrated to the new .NET 5 code base and the old window is removed. But that change is not imminent, there is still a considerable amount of work to undertake to complete the code migration.

If you want docking like behavior with the new Callsigns window, set the old JTAlert window to dock with WSJT-X and then set the Callsigns window to "Follow JTAlert window", use the Gear icon or F2 to bring up the Options popup. The Callsigns window will minimize & restore following the old JTAlert window as it follows WSJT-X. I do this, but with the Callsigns window positioned to the right of the WSJT-X window, something that cannot be done with the old docking method which supported docking to the Top or Bottom only.

Not sure what you mean when you refer to the Gear icon as superflous (the correct spelling is superfluous). I use it all the time, it is more convenient than the F2 hotkey. It also hosts a right-click context menu. It definitely is not superfluous, IMO.

If none of the above is suitable, you're best to roll back to JTAlert 2.16.17 which still has the callsigns (limited to a max of 36) in the main window.

de Laurie VK3AMA



locked Re: Decode not clearing

HamApps Support (VK3AMA)
 

On 22/05/2021 4:44 am, John Holmes W9ILY wrote:
Today the JTAlert decodes are not deleted after each JTDX decode sequence as has happened in the past. I probably changed something but do not know what has caused this issue. After 4 or 5 decode sequences on JTDX the JTAlert screen will clear and decodes begin again. Some of the previous decodes are redisplayed along with some new decodes. Any ideas?
John W9ILY

Have you recently upgraded JTDX to RC 2.2.156? I have seen some forums commentary of delays/lag with 156 that are not present with 155. I wonder if these delays are contributing to the JTAlert misbehavior. In your case it appears that the Callsigns window is not receiving the callsigns clear instruction from the background Manager process.

Rather than letting the callsigns accumulate, you can force a clear of the display and its underlying data structure by making the window active and hitting the Esc key or via a double-click on the callsign count (96 in your image) in the statusbar.

If you're on JTDX 156 try rolling back to 155.
If you do roll back JTDX to 155, please report back if that corrected the anomalous behavior.

Sorry, at this time I don't have a fix as it is still unclear what is the root cause.

de Laurie VK3AMA


locked Decode not clearing

John Holmes W9ILY
 

Today the JTAlert decodes are not deleted after each JTDX decode sequence as has happened in the past. I probably changed something but do not know what has caused this issue. After 4 or 5 decode sequences on JTDX the JTAlert screen will clear and decodes begin again. Some of the previous decodes are redisplayed along with some new decodes. Any ideas?
John W9ILY


locked Convert free-floating "Callsigns No1" window to being part of single window ... as before

Peter Laws
 

Subject: line says it all. I have looked all through settings ... and the "other" settings under the superflous window's "gear" ("Follow JTAlert window" ain't it). I would just like *one* JTAlert Windows ... as it was before.

Lest anyone think I just want things to go back to where they were "in the day", the new callsign window looks much more useful ... if it was docked at the bottom of WSJT-X 2.3.1 ...


locked Re: JTAlert Boot issue

Jim Denneny
 

I should add that a total reboot sometimes allows JTAlert to run.  Once it is running, all is OK.  Again, if there was any interaction with protection software, I would know it.  I have examined TotalAV and Win Defender and see nothing.

Jim K7EG


locked Re: JTAlert Boot issue

Jim Denneny
 

Logan

I am having same issue with latest JTAlert. OS is latest updated Win 10x64.  I have double-checked all protection software and find no trace of any action.  I am trying to figure out how to rollback JTAlert.  I am not sure whether I must also rollback NET framework as well.

Laurie.  You now have at least two incidents of this issue.  HELP.

73, Jim K7EG


locked Re: JTAlert Boot issue

KE7AZ
 

Here is the failure data from the Event Viewer

Faulting application name: JTAlert.exe, version: 2.50.1.0, time stamp: 0x608a69d2
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x05517f78
Faulting process id: 0x449c
Faulting application start time: 0x01d74dd21a05ee03
Faulting application path: C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe
Faulting module path: unknown

Report Id: 46f2f19c-65db-4304-928b-567514d3caca
Faulting package full name:
Faulting package-relative application ID:

I also found events in the Windows log for Applications that identified an application error for JTAlert.  There were links to dump files but I didn't have permission to access. 

Logan


locked Re: JTAlert Boot issue

KE7AZ
 

I'm running MS Defender, however, i'm not getting any notifications or warnings about a virus being detected.  I went through and shut down all virus and firewall protections and still no success.

Any other ideas?

Logan


locked Re: JTAlert Boot issue

Jim Denneny
 

Thanks Laurie.  Don't think it is protection hardware.  I am always warned if action is needed.  I use TotalAV.  I also ran Restoro with no malware noted.  Fingers crossed.

I reinstalled Net 5 and 2.50.1.  So far JTAlert has not crashed. - Jim K7EG


locked Re: JTAlert Boot issue

HamApps Support (VK3AMA)
 

On 21/05/2021 6:58 am, KE7AZ wrote:
Me, too.....

Two weeks ago, JTAlert was running fine.  Today, not so much.  It goes into the start up process, I get the loading settings message, then it disappears.  No sign of JTAlert in the Task Manager.  I tried upgrading wsjt-x to 2.3.1 and JTAlert to 2.50.1 and have the same problem.  Windows 10.

Logan, KE7AZ

Very likely your PC protection software has decided to take a dislike to JTAlert and is inappropriately interfering with JTAlert operation. You will need to set your software to consider JTAlert safe.

What protection software do you use?

If you're uneasy about setting your protection software with an override for JTAlert, than submit JTAlert to the protection software vendor for analysis, once they give JTAlert the "all clear", which I am sure they will, than you will need to configure their software appropriately.

de Laurie VK3AMA


locked Re: JTAlert Boot issue

KE7AZ
 

Me, too.....

Two weeks ago, JTAlert was running fine.  Today, not so much.  It goes into the start up process, I get the loading settings message, then it disappears.  No sign of JTAlert in the Task Manager.  I tried upgrading wsjt-x to 2.3.1 and JTAlert to 2.50.1 and have the same problem.  Windows 10.

Logan, KE7AZ


locked Re: JTAlert Boot issue

HamApps Support (VK3AMA)
 

On 21/05/2021 3:17 am, Jim Denneny wrote:
Running latest JTAlert released version 2.50.1.  Net 5 also installed The past few days JTAlert hangs during boot sequence.  Don't know if it is a pc or app issue.  I cannot kill the loading message with Task manager.  Task Manager shows  JTAlert as not responding.  Reboot fixes it usually.

I have run several diagnostic programs without issue.  PC is Win10 64bit with latest MS updates. No evidence of malware etc.  Am I the only one experiencing this?

73, Jim K7EG

Jim,

I have not seen any other reports of this. Sounds like possible PC Protection interference"

When JTAlert hangs, has it completed its loading or is there a specific window that appears to be hanging or not loading.

If a PC restart corrects the problem, that indicates that it is unlikely a config file issue.

When you view a hung JTAlert in taskmanager, are you seeing the JTAlertV2.Manager.exe process? You should as it is core to proper functioning. It is the component that requires the .NET 5 runtime.

You can check if it is a .NET runtime issue by executing the "NET Framework Check" shortcut located in the Windows "HamApps JTAlert" start menu group. Does it run successfully?

de Laurie VK3AMA


locked Re: Alert sound not working

Paul F6EXV
 

Hi again
I found it.... I forgot to put a sound file in each individual alertt needed (states, countries, etc)
Now all OK, so sorry for bandwidth !
73
Paul F6EXV

Le 20/05/2021 à 18:59, Paul F6EXV a écrit :
Hi all
I have a sound in the "own call" box, and the test does work.
I have "sound on" in the main window, and the test does work.
I have seletected the proper sound card, and the test does work.
BUT, when it should buzz on a new (country for example) thing, I do read the red color, I do see a vertical little bar in the decode line, but no sound played....
Where am I forgetting another setting please ?

Thanks + 73
Paul F6EXV
--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked JTAlert Boot issue

Jim Denneny
 

Laurie

Running latest JTAlert released version 2.50.1.  Net 5 also installed The past few days JTAlert hangs during boot sequence.  Don't know if it is a pc or app issue.  I cannot kill the loading message with Task manager.  Task Manager shows  JTAlert as not responding.  Reboot fixes it usually.

I have run several diagnostic programs without issue.  PC is Win10 64bit with latest MS updates. No evidence of malware etc.  Am I the only one experiencing this?

73, Jim K7EG


locked Alert sound not working

Paul F6EXV
 

Hi all
I have a sound in the "own call" box, and the test does work.
I have "sound on" in the main window, and the test does work.
I have seletected the proper sound card, and the test does work.
BUT, when it should buzz on a new (country for example) thing, I do read the red color, I do see a vertical little bar in the decode line, but no sound played....
Where am I forgetting another setting please ?

Thanks + 73
Paul F6EXV

--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked Re: Potential For Lost JTAlert Functionality By Directly Updating HRD Logbook Via WSJTX ? #HRD

HamApps Support (VK3AMA)
 

On 20/05/2021 11:12 am, n3ps via groups.io wrote:
I find that ~ 5% of my logbook updates via JTAlert aren't 100% (missing parts of name and/or address or contain some weird characters).  They are correctable after entry by initiating a Lookup within HRD Logbook (as HRD pulls the info from a multiple sources), so I thought about just using UDP broadcast which would result in HRD doing the lookup as part of the logbook update.

I do rely heavily on the Worked B4 and Alert function within JT Alert, so I will continue doing the logbook updates via JT Alert . . .

--
Paul / N3PS

Paul,

If there is data missing from the QSOs logged by JTAlert that is something I would like to investigate. When you note a newly logged QSO with incomplete or inaccurate values send me a support request via the "Help" -> "Contact Support" menu, on the main JTAlert window. Include a note of the Callsign affected and the data problem.

de Laurie VK3AMA



locked Re: Potential For Lost JTAlert Functionality By Directly Updating HRD Logbook Via WSJTX ? #HRD

n3ps@...
 

Thanks for the explanation Laurie.

I find that ~ 5% of my logbook updates via JTAlert aren't 100% (missing parts of name and/or address or contain some weird characters).  They are correctable after entry by initiating a Lookup within HRD Logbook (as HRD pulls the info from a multiple sources), so I thought about just using UDP broadcast which would result in HRD doing the lookup as part of the logbook update.

I do rely heavily on the Worked B4 and Alert function within JT Alert, so I will continue doing the logbook updates via JT Alert . . .

--
Paul / N3PS


locked Re: JTAlert talking to WSJT and JTDX

HamApps Support (VK3AMA)
 

On 20/05/2021 2:19 am, Dave Garber wrote:
Aclog uses the api on port 1100.   And jtalert should be set to that port and correct log file..   I did try it using the multicast.    Cant remember if it worked
FYI, JTAlert does use the port 1100 API for interaction with ACLog.

The original poster was having issues where the UDP server in WSJT-X was setup for unicast and ACLog was taking ownership of the UDP port preventing JTAlert from interacting with WSJT-X.

In the situation where 2 or more applications need to interact with WSJT-X concurrently, WSJT-X needs to be set to use multicast UDP and all applications wanting to work with WSJT-X will similarly need to changed over to using multicast. For JTAlert, that changeover is simple, a simple tick of a menu entry, all other settings like the correct multicast address and port are automatically determined by JTAlert. I don't know how or if ACLog can use multicast in their newly released ACLog 7.

de Laurie VK3AMA

2061 - 2080 of 36956