However my Help/About looks different: Something I'm missing ?

Something is seriously wrong if your not showing UDP ports  & Manager modules status, that info comes directly from 2 status files that are always created at JTAlert startup.

I got your support request it doesn't show any of the files that are always created when the JTAlertV2.Manager.exe process is run. There are many older session files with the latest being created 23-Dec-2019, nothing since.

It looks to me like the JTAlertV2.Manager.exe process is not running.

I suggest you do the following...

• perform a PC restart.
• uninstall JTAlert using Windows Control Panel.
• Using Windows File Explorer delete the old JTAlert installation directory and remaining files and sub-directories it contains.
• Install JTAlert again.

Let me know how you get on.

de Laurie VK3AMA

I ran the program I selected the alt (2) check boxes.
And I still get misplaced buttons also I cannot find the decodes history display window it seem to be gone.

I running windows 10 Intel R core i7-7700K CPU @ 4.20GHz   64 bit  16 GB ram

Any suggestions?

Thanks for any help

Fred KB4QZH

If your getting misplaced menus then your NOT running JTAlert in Alt Layout mode. You need to start JTAlert with the correct shortcut. "Alt Layout" builds of JTAlert use unique colored icons for the shortcuts and the JTAlert window titlebar.

• Red => JTAlert for WSJT-X.
• Blue => JTAlert for JTDX.
• Green => JTAlert (Alt Layout) for WSJT-X.
• Purple => JTAlert (Alt Layout) for JTDX.

de Laurie VK3AMA

I have downloaded the alt layout.
I ran the program I selected the alt (2) check boxes.
And I still get misplaced buttons also I cannot find the decodes history display window it seem to be gone.

I running windows 10 Intel R core i7-7700K CPU @ 4.20GHz   64 bit  16 GB ram

Any suggestions?

Thanks for any help

Fred KB4QZH

Hi Laurie,

"Help about" is a handy feature.  Thanks :)

It does show my Audio issue of no sound, also in the latest version.



Remains the same even after a couple minutes after starting.

Restarting JTAlert shows all modules initialized and sound works.

73,
Rick VK6RK

Rick,

FYI, waiting for a non-initiialised module to initialise is wasted time. The initialization command is only sent once at JTAlert startup. Initialising failed modules automatically is on the todo-list (likely with the next release).

I am curious why this happened to you, Please use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis. Thanks.

de Laurie VK3AMA

Hi Laurie,

"Help about" is a handy feature.  Thanks :)

It does show my Audio issue of no sound, also in the latest version.



Remains the same even after a couple minutes after starting.

Restarting JTAlert shows all modules initialized and sound works.

73,
Rick VK6RK

Great news! the 2.5.17 update fixed my log problems with QRZ and my Hamspots are working again too. Thanks!

The Latest JTAlert version 2.15.7 is now available @ https://hamapps.com/JTAlert/

de Laurie VK3AMA

The Release Notes...

Thanks Laurie,

As it turned out they released it last night and I am running it now.

I will make some changes until you get that worked out.

Thanks for your efforts.

Rich

Laurie,

That you will be looking to add Log4ON v2 support in due course is excellent news.  We all appreciate the time and effort expended in advancing the hobby with all the great software available.

I just setup a Shortcut, great idea, put on Desktop of Windows10

Named:  Find WSJT-X Contacts

C:\Windows\notepad.exe   C:\Users\INSETUSERNAMEHERE\AppData\Local\WSJT-X\ALL.TXT

 

Mine is:   C:\Windows\notepad.exe C:\Users\bobwilley\AppData\Local\WSJT-X\ALL.TXT
Start in:  C:\Windows

Run: Normal Window

will be installing Log4OM v2 as soon as it comes out so need to come up with a game plan for what I am going to do with WSJT.

Thanks and 73,

Rich

If your installing Log4OMV2 as soon as it is available, then you will be running without JTAlert as it currently does not support V2.

• The next release of JTAlert, 2.15.7, due tomorrow, also DOES NOT support V2.
  
  
• There are enough differences between V1 and V2, incompatible config files and log schemas, that JTAlert will be treating V2 as a separate logger.
  
  
• Initially JTAlert will only support the sqlite log of V2.
  
  
• There is an issue with V2 MySQL log schema that impose a significant performance hit with real-time access to the log records. MySQL logs may never be supported.

de Laurie VK3AMA

Log4OM v2 installed and working well though not yet with JTAlert.  I will stick to Log4OM V1.4 as JTAlert is vital for me.  Hope the two can be made compatible.

Thanks
Mike G0KAD

On Wed, Jan 15, 2020 at 11:22 AM, WB8ASI Herb wrote:

Hey Gary....thanks for the tip.  Wish I would have known you can do that.  Sure will save scrolling thru the miles of log. Herb WB8ASI.

The all.txt file is such a valuable resource, I have a shortcut to it on my desktop.  If you have never deleted it,  you may find your all.txt file contains thousands of decoded entries going back to when you first started using WSJT-X.   I was concerned about the size of this file affecting performance and have made it my practice to limit it to one year.  I rename and save old files as 2014_All.txt,  2015_All.txt, etc.  Never know when you might want to dig through an old file for some reason.   The Notepad "Find" tool is very flexible and can be used to search for almost anything.

73 de Gary - AC6EG 

Running 2.15.0 when opening the decodes window the continents are blank. Can you think why nothing is populating in that window.

Also in 2.15.6 the decodes window does not open/display at all on my Win7 Pro PC. Ideas?

Thanks once again.

Bill W2PKY 

Are you sure you mean "continents" are blank or is that a typo and should read as "contents"? If the later, you need to enable Decodes collection under the "Window -> Decodes" section of the Settings window.

On the Win7 PC is the "JTAlertV2.Decodes.exe" process running, check using taskmanager? If it is there should be a corresponding taskbar entry for the Decodes window. If there isn't then likely your PC protection software is interfering and preventing its execution. Another possibility is that your Win7 PC doesn't meet the minimum requirements. The Decodes window is based on new .NET code and as such requires at least the 4.7.2 .NET framework to be installed and for Win7 it needs to be at a minimum SP1. The JTAlert installer should warn if either of those requirements are not met, but the installer code is not 100% when trying to determine the state of your Windows environment especially with old Windows installations.

de Laurie VK3AMA

Thanks everyone.

I cannot locate any QSO for the one Incoming Confirmation Request.
Interesting....

Request ReceivedQSO DateCallsignActions
1  2020-01-14  07:42:02  2019-11-20   K3RLW de K6JMQ  

 

I did send an e-mail (got from QRZ page thankfully it was there), to ask for any details on what they saw as a contact.
Incase I missed something.
It is possible it was a SSB contact, but most of those I do an immediate "Log a NEW contact with K6JMQ"

Have not heard anything back from him.