Hello all
Using JTAlert v2.50.1 and Log4OM version 2.13.0.0
I have configured L4OM default LoTW snet to "requested", and LoTW received to "no".
I have configured JTAlert logging as shown on the attachment.
BUT when I log a QSO, the LoTW received in L4OM shows as requested, while it should show No... unless I missed something !

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

Doing a search for (logging start time End Time) I get 2014 2015 results . I'm using WSJT-X , Jtalerts V2.50.1 and AClog ... When I click on a call I'd like to work in JTalerts and after sending RR73 the logging window pops up but the start time is the End time of last QSO logged ! This can very from 1 minute to Hours . I've found what I have to do to set the Start time is double click the call in WSJT-X . I know I've missed a setting somewhere ?  The 2 J-pegs below, The left is clicking JTAlerts and right is clicking WSJT . Please not the Start time ..Thanks Ed N5DG
  

Hi Laurie, what I call the "alerts window" is wthe window that shows all the calls which I can click on etc. I upgraded from 2.5.0. which was working fine up until the the.net and 2.5.1. installations.

Thanks for replying.

de Jeff M1BCM

Jeff,

There was no requirement for a .NET install with 2.50.1, the .NET install required for the 2.50.0 install is all that was needed. What prompted you to install a new NET 5 runtime?

Are you able to open the JTAlert Help->About window?

Are you able to open any of the new 2.50.x windows? See the "Yellow star" entries under the View menu of the main JTAlert window.
   

If none of these windows will open, that suggests a problem with the JTAlertV2.Manager process, likely it is not running or is continually stopping and starting. What does TaskManager show for this process?

The Manager process is dependent on the .NET 5 runtime. When you installed/upgraded the runtime for your 2.50.1 install did your install the correct architecture version matching that of JTAlert? The runtime needs to match JTAlert, either x86 or x64. If you're using Windows 64 bit, I suggests using the x64 version of the runtime and JTAlert. While the 32 bit (x86) runtime and JTAlert will work under 64bit Windows, IMO, it is best to keep it x64 across the board, Windows, NET runtime and JTAlert all being x64.

de Laurie VK3AMA

Hi Laurie, what I call the "alerts window" is wthe window that shows all the calls which I can click on etc. I upgraded from 2.5.0. which was working fine up until the the.net and 2.5.1. installations.

Thanks for replying.

de Jeff M1BCM

Before installing the new JTAlert version, I first installed the new .net software. Both went with no problems but the Alerts window is a no-show and the QSO history window won't populate. I'm sure it's fixable in settings but I sure as hell can't find it hihi. Report sent.

Jeff M1BCM

There is no "Alerts" window in JTAlert 2.50.1

What version did you upgrade from, was it a pre 2.50.x version? If so, is it the missing Callsign display grid of the main JTAlert window that is your problem? If yes, see the 2.50.0 release notes.

de Laurie VK3AMA

Notice from NET here this AM that NET 5.0 has problem.  Recommends upgrade to 5.0.6.  That seems to be my fix

Do you have a link to the source of this .NET problem?

de Laurie VK3AMA

Hi guys, could'nt find a fix for this ...
Before installing the new JTAlert version, I first installed the new .net software. Both went with no problems but the Alerts window is a no-show and the QSO history window won't populate. I'm sure it's fixable in settings but I sure as hell can't find it hihi. Report sent.

Jeff M1BCM

Known issue. I updated NET to later version.  It works

Jim K7EG

Laurie: Definitely not protection software.  Notice from NET here this AM that NET 5.0 has problem.  Recommends upgrade to 5.0.6.  That seems to be my fix..  It has been two days now.

73, Jim K7EG

That was it, Michael, thanks !
73
Paul

Hi Paul

You'll find it as shown on the picture.

73 de Michael 5p1kzx

Den 24-05-2021 kl. 10:55 skrev Paul F6EXV:

Hi all
The answer is probably obvious, but I just could not find it...
The JTAlert windows is hidden when I bring another screen on top of it.
But the callsign windows is always on top. Can I change this ? Where please ?
73
Paul F6EXV

Hi Paul

You'll find it as shown on the picture.

73 de Michael 5p1kzx

Hi all
The answer is probably obvious, but I just could not find it...
The JTAlert windows is hidden when I bring another screen on top of it.
But the callsign windows is always on top. Can I change this ? Where please ?
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

I only have two applications using the UDP port - WSJT-X and JTAlert.  I also tried the multicast set up and it didn't work. 

So I went back to find previous versions to see if I could get something to work.  Here is what I found...
WSJT-X Version     JTAlert version    Result
2.1.2                            2.12.9               OK
2.3.1                            2.15.0               OK
2.3.1                            2.16.17            UDP Error
2.3.1                            2.16.1              AutoIT Crash
2.3.1                            2.16.3              OK
2.3.1                            2.16.6              OK but crashes after settings change
2.3.1                            2.16.11             UDP Error

There was a Windows 10 update just before this appeared.  I tried backing out the update out but one of the updates did not give me the option to undo it.  I did not have a system restore that I could use because of subsequent Windows 10  updates.I suspect that this problem is an unintended consequence of a Windows 10 update.  Entropy is winning!

73
Logan

Laurie thank you very much
that was my problem
everything is ok
73s

Javi - LU5FF
-----------------------

HI all...

how to make my window look maximized?

view photo

tnx 

 

Javi - LU5FF

If you can't drag the edges of the Callsigns window to increase its size, make the window active, then press the F2 key which will open the Options, then untick the "Size locked" checkbox which will allow you to resize the window.

   

de Laurie VK3AMA

On 24/05/2021 4:09 am, Jim Denneny wrote:

Rolled back to 2.16.6 and 2.16.7.  Only the settings window opened. No main window starts. NET is 5.0

Next, upgraded NET to 5.0.6 and reinstalled JTAlert 2.50.1 again. It loads now and runs OK.  I have slim confidence that this will remain OK. All exceptions are in place.

Jim K7EG

JTAlert 2.16.17 & .16 do not use the .NET 5 runtime.

.NET 5.0.0 or 5.0.6 will make no difference, both will work with the JTAlert 2.50.x series.

My only thoughts on your troubles are that your Protection software was interfering, or you had an incompatible .NET installed. Perhaps the x86 runtime was installed while trying to use the x64 build of JTAlert. The two need to match. While the x86 versions will work under Windows x64, It is best to keep all architecture types the same, X64 across the board.

de Laurie VK3AMA