Date   

locked New hiccup after windows flagged as virus again

Chuck Kraly K0XM
 

I set the exception and it has been ok, then all of a sudden it killed JTAlert. I reset the eception, then I started getting this, and I cannot close with the X
Any ideas what got corrupted? It seems all the title bar has shifted left. And no access to settings


locked Re: JtAlert - Inability To Filter Already Worked Prefixes

Jim N6VH
 

Greg,

Probably the only way to do this is under the "Scan Log and Rebuild" area in Settings. With "Enable this Scan" checked (which it probably already is), check "No QSL Confirmation (Any Worked Station)". This should keep JTAlert from alerting for a prefix you have already worked, even if it isn't confirmed. However, if you are interested in the prefix award, you need confirmations, and this solution won't help. If you aren't interested in the prefix award, go to "Wanted Prefix" under Settings, and uncheck "Enable Wanted Prefix Alert".

If you are interested in the prefix award, you want to let JTAlert scan for confirmations. In that case, you will get alerts for prefixes worked but not confirmed. That's the only way it can work,

73,

Jim N6VH

On 2/15/2020 11:30 AM, Gregory Speyrer wrote:
Hello,

When running Jtalsert with WSJT-X, i'm unable to successfully configure Jtalert to ignore already worked call sign prefixes.

When mousing over a contact in jtalert, the bubble clearly shows that contact was worked - shows month and year (LoTW).

Any assistance in resolving this issue would be appreciated.

Thx,

Greg
_._,_._,_



locked JtAlert - Inability To Filter Already Worked Prefixes

Gregory Speyrer <gspeyrer@...>
 

Hello,

When running Jtalsert with WSJT-X, i'm unable to successfully configure Jtalert to ignore already worked call sign prefixes.

When mousing over a contact in jtalert, the bubble clearly shows that contact was worked - shows month and year (LoTW).

Any assistance in resolving this issue would be appreciated.

Thx,

Greg


locked Re: Rescanning log for prefixes

Stuart, K2YYY
 

I confirmed that it is not an issue with the version of JTAlert.  I reinstalled 2.15.8 and it does the same thing.  

How do I get it to scan the HRD logbook and find the prefixes?  Every QSO in the database has a value for prefix.


locked Rescanning log for prefixes

Stuart, K2YYY
 

I'm using 2.15.10 (and HRD v6.7.0.254) and after upgrading from 2.15.8 the scanning for prefixes identifies fewer prefixes confirmed than previously. 

Doesn't the prefix scan use the HRD database to search for prefixes?  The Standard ADIF file is unselected.

Thanks,

Stu, K2YYY


locked Re: MYSQL Connection Error: Client does not support authentication protocol requested by server; consider upgrading MySQL client

HamApps Support (VK3AMA)
 

On 15/02/2020 12:27 am, Michael Black via Groups.Io wrote:
You may need the SSL libraries.  Install the Win32 Lite package from here (not the Win64 which is for 64-bit executables).


de MIke W9MDB

Mike,

Thanks, but no cigar.

The problem is not with SSL libraries.
The problem is with the new Client authentication method introduced with MySQL 8.0.

The JTAlertV2 MySQL support uses a library that wraps the libmysql.dll client file.
Both the library and the dll are old and do not support the new authentication method of MySQL 8.0.
At this time, I have been unable to locate a new library (I don't expect I will).

I was able to workaround this by enabling Legacy Authentication on the server.

   

I understand this may not be an option for some MySQL Server users, but it is the only fix at this time.

BTW, this change broke many MySQL client applications when first released, including at one time, the official MySQL workbench app.

FWIW, JTAlertV3 will not have this problem as it uses the official Oracle .NET MySQL connector.

de Laurie VK3AMA


locked Re: Unable to start-up

Jim Sharp
 

wow....thanks for your quick response.
Ok I got it started from the command line using jtalert_al.exe/wsjtx
What bat file might you suggest (I haven't constructed a bat file in a long time..ha) that would also not start the sound option as this bombs out the program as well
tnx, Jim

On Fri, Feb 14, 2020 at 10:08 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
Jim,

To avoid the JTMode selection window, which I am assuming is what is causing your crash, you need to start JTAlert using the correct command-line parameter, either "/wsjtx" or "/jtdx". This is why the JTAlert installer creates shortcuts which have those parameters already set. Starting the JTAlert.exe file directly will always present that window as the command-line parameter is missing.

de Laurie VK3AMA

On 15/02/2020 8:54 am, Jim Sharp wrote:
Not sure how to get JTAlert working  since when I start up (have installed the latest version today (2.15.10) and with prior versions, I get an box requesting the sound card.
I select speakers/headphones (Realtek) and the box crashes with the only option to close out as it goes into "not responding" /close the program.

Please see attached 


locked Re: FT4 Support #HRD

WarrenG KC0GU
 

Oh and I doe have HRD set as the logging program in JT-Alert.

Warren
KC0GU


locked Re: FT4 Support #HRD

WarrenG KC0GU
 

I can see by the responses I should have been more explicit.  I do manually update HRD Logbook from LOTW.  HRD is logging the mode as FT4. The entries are marked as confirmed in the log but the scan and rebuild does not update the Wanted US State check boxes.

I manually updated everything today (what a pain) so let's see what happens from here.

Thanks for the replies,

Warren
KC0GU


locked Re: JTAlert New error message

HamApps Support (VK3AMA)
 

On 11/02/2020 9:50 pm, Paul-N5DUP wrote:
I think maybe the ACLog .mdb log file got corrupted somehow because I overwrote the backup to it and no more problems confirming the QSO. Thank you and sorry for the trouble.

Paul
N5DUP
Paul,

No problems. Glad you have it sorted. From your description is sounds very much like a broken or missing index in the .mdb database since apart from the slowness it was working.

de Laurie VK3AMA


locked Re: odbcji32.dll

HamApps Support (VK3AMA)
 

On 14/02/2020 10:55 am, jmajka@... wrote:
Deleted then reinstalled ACCESS. That did it. Thank you. 73 John

John,

Thanks for the update. Good to hear your now working.

de Laurie VK3AMA


locked Re: Scan Log and Rebuild

HamApps Support (VK3AMA)
 

On 15/02/2020 6:47 am, Monty Wilson wrote:

I do not see a way to download from QRZ….only upload.

Cheers

Monty Wilson, NR0A


FYI, even if HRDLogbook was able to download QRZ confirmed QSOs, JTAlert would not use them as it doesn't support QRZ confirmed QSOs for the Scan Log function.

de Laurie VK3AMA



locked Re: Scan Log and Rebuild

HamApps Support (VK3AMA)
 

On 15/02/2020 2:33 am, Charlie Hoffman wrote:
Since I'm not getting answers, let me restate the question.

When I run a "Scan Log and Rebuild", what log is the source of the confirmed QSL information?

The Scan Log uses the Log you have enabled in JTAlert. If your using HRD logbook, whatever HRDLogbook database you have set in JTAlert (Logging -> HRD V5/V5 section) is used for the Scan.

JTAlert does not automatically set your logbook. You need to do that, especially since HRD supports multiple logs. JTAlert doesn't know which log you have active in HRDLogbook

de Laurie VK3AMA


locked Re: FT4 Support #HRD

HamApps Support (VK3AMA)
 

On 15/02/2020 3:27 am, kcZEROgu@... wrote:
I have been able to use the work around to get HRD to log FT contacts but it looks like JT-Alert Scan log and Rebuild does not support FT4.  It works fine on FT8 but is not removing the check marks from wanted States for WAS.  Is that by choice or an error?

Laurie thank you so much for this great resource to work Digital modes, I love it!!!!

Warren
KC0GU

The JTAlert Scan Log does support FT4 and has for many months since FT4 was first released.

HRD is the program that doesn't support FT4. If HRD is still recording FT4 QSOs in its log as Mode = MSFK with no submode defined (it should be FT4) than the scan will not find your incorrectly recorded FT4 QSOs.

If the HRD Log has FT4 QSOs recorded as Mode=FT4 than JTAlert will find them. QSOs with Mode recorded as MSFK without a submode will not be found.

My 2cents... The ball has been in the HRD court for many months with respect to correct FT4 logging. All other Loggers were updated within days of the FT4 release. HRD chose to sit on their hands and offer incorrect support advise on how to workaround their non-updated log.

de Laurie VK3AMA


locked Re: Unable to start-up

HamApps Support (VK3AMA)
 

Jim,

To avoid the JTMode selection window, which I am assuming is what is causing your crash, you need to start JTAlert using the correct command-line parameter, either "/wsjtx" or "/jtdx". This is why the JTAlert installer creates shortcuts which have those parameters already set. Starting the JTAlert.exe file directly will always present that window as the command-line parameter is missing.

de Laurie VK3AMA

On 15/02/2020 8:54 am, Jim Sharp wrote:
Not sure how to get JTAlert working  since when I start up (have installed the latest version today (2.15.10) and with prior versions, I get an box requesting the sound card.
I select speakers/headphones (Realtek) and the box crashes with the only option to close out as it goes into "not responding" /close the program.

Please see attached 
_._,_._,_



locked Unable to start-up

Jim Sharp
 

Help please
 
Not sure how to get JTAlert working  since when I start up (have installed the latest version today (2.15.10) and with prior versions, I get an box requesting the sound card.
I select speakers/headphones (Realtek) and the box crashes with the only option to close out as it goes into "not responding" /close the program.

Please see attached 


locked Re: Scan Log and Rebuild

Monty Wilson, NR0A
 

You can do a manual download from eQSL also to HRD.  On the HRD log window goto Logbook > File > eQSL.cc > download.  I do not see a way to download from QRZ….only upload.

 

Cheers

 

Monty Wilson, NR0A

jwilson16@...

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Charlie Hoffman
Sent: Friday, February 14, 2020 1:34 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Scan Log and Rebuild

 

Thanks Tom.

With your info, I was able to find out that my local HRD log does not automatically get confirmation updates from
any on-line logs.   I have to perform that task manually.   After downloading new updated info from LOTW, I now
have agreement with the Scan Log Results and what is shown on LOTW awards page  for DXCC and WAS.

I still have a number of confirmed QSOs on both eQSL and QRZ that are not LOTW users so there is nothing I
can do about that problem.


locked Re: Scan Log and Rebuild

n4qwf .
 

If you have designated a log program for JTAlert to log to then it will scan that log based on the filters you have set. I have my system logging to DXKeeper. Once I log a stations using WSJT-X it is in DXKeeper. The JTAlert scan (when run) then updates my log display in JTAlert. 

73<<John

On Fri, Feb 14, 2020 at 10:33 AM Charlie Hoffman <hoffmanc@...> wrote:
Since I'm not getting answers, let me restate the question.

When I run a "Scan Log and Rebuild", what log is the source of the confirmed QSL information?


locked Re: Scan Log and Rebuild

Barry <boat.anchor@...>
 

On Fri, Feb 14, 2020 at 11:34 AM, Charlie Hoffman wrote:
Thanks Tom.

With your info, I was able to find out that my local HRD log does not automatically get confirmation updates from
any on-line logs.   I have to perform that task manually.   After downloading new updated info from LOTW, I now
have agreement with the Scan Log Results and what is shown on LOTW awards page  for DXCC and WAS.

I still have a number of confirmed QSOs on both eQSL and QRZ that are not LOTW users so there is nothing I
can do about that problem.
Charlie
Download your eQSL confirmations also.
Barry


locked Re: Hamapp

John Profita
 

Thank you, it is working now. Much appreciated

Tnx, John
ND1X


On Fri, Feb 14, 2020 at 10:43 AM Michael Black via Groups.Io <mdblack98=yahoo.com@groups.io> wrote:
Log4OM has nothing to do with JTAlert starting.

It's just the JTDX has to be running before JTAlert will start.

So make sure JTDX is started first.




On Friday, February 14, 2020, 09:26:54 AM CST, John Profita <jwpjjj@...> wrote:


Laurie, that is exactly what I am seeing on the screen. So if I run LOG4OM do I need to install into it?  Or does log4om pick it up automatically?  Which IMHO it doesn't'

On Thu, Feb 13, 2020 at 9:17 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 14/02/2020 12:38 pm, John Profita wrote:
the message says trying to download because Jtdx is not loaded? I’m guessing, being I have Log4OM, the jtdx and jtalert etc. gets loaded onto Log4OM? Please give if it looks like I am lost here. 

That is not any message JTAlert displays. I assume what your seeing is the same as this image, no mention of downloading.

   

This message is shown because JTDX needs to be running before JTAlert can continue its startup process.
You just need to start JTDX and JTAlert will then continue.

If this is not the window your seeing, please post a screen-capture of the window (please, no images of your entire desktop, just the window, and no cell phone images)

de Laurie VK3AMA

10801 - 10820 of 38532