Laurie, This occurs both using the shortcut created by the setup, or by executing the  still present JTAlert.exe file.(1,748 KB)
I do use Spy Hunter and it will prevent setup from working but I have it locked out and rebooted, as I always do when doing an upgrade.
The first time I setup the new version it asked about paths. It does not do that now even though I removed all traces of JTAlert and
rebooted before trying to install again using the same setup app and a newly downloaded one.

de Dave KR4LU
image attached

Jon,

That message indicates that JTAlert was unable to confirm that the QSO got logged (by JTAlert) successfully to ACLog. JTAlert confirms the QSO was logged by directly querying the ACLog log database. A couple of possibilities...

1. The QSO didn't get logged because ACLog is not running or the TCP API is not enabled in ACLog (both conditions need to be satisfied).
2. The log file JTAlert tried to read was not found.

In a default installation, JTAlert automatically determines the correct log file by reading the ACLog settings file, so number 1. is the most likely problem.

Let us know how you get on with this.

If you still can't get this to work, use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis.

I neglected in the above response to ask the question "Does the QSO get logged to ACLog despite the error message?"

If the answer is yes, than look under the "Miscellaneous -> Performance" section of the JTAlert Settings window and increase the "Check QSO Log Record" time.

de Laurie VK3AMA

Hello.  I have just installed JTAlert and the N3FJP Amateur Contact Log program (ver. 6.5).  I use WSJT-X in the FT-8 mode. When the WSJT-X pops up its own log window and I click to save the QSO info in the WSJT-X log I get the following message in a pop-up box:

FAILURE: QSO to N3FJP Amateur Contact Log

ERROR Message: : AC LOG File : Unable to confirm QSO logged

NOTE: The QSO is still saved to the WSJT-X Log File.

I looked in the FAQ area but did not find useful information.  What does this error message mean, what is the solution to get the log info into the ACL log?  Any help greatly appreciated.  Thank you.

Jon Titus, KZ1G

Jon,

That message indicates that JTAlert was unable to confirm that the QSO got logged (by JTAlert) successfully to ACLog. JTAlert confirms the QSO was logged by directly querying the ACLog log database. A couple of possibilities...

1. The QSO didn't get logged because ACLog is not running or the TCP API is not enabled in ACLog (both conditions need to be satisfied).
2. The log file JTAlert tried to read was not found.

In a default installation, JTAlert automatically determines the correct log file by reading the ACLog settings file, so number 1. is the most likely problem.

Let us know how you get on with this.

If you still can't get this to work, use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis.

de Laurie VK3AMA

Hello.  I have just installed JTAlert and the N3FJP Amateur Contact Log program (ver. 6.5).  I use WSJT-X in the FT-8 mode. When the WSJT-X pops up its own log window and I click to save the QSO info in the WSJT-X log I get the following message in a pop-up box:

FAILURE: QSO to N3FJP Amateur Contact Log

ERROR Message: : AC LOG File : Unable to confirm QSO logged

NOTE: The QSO is still saved to the WSJT-X Log File.

I looked in the FAQ area but did not find useful information.  What does this error message mean, what is the solution to get the log info into the ACL log?  Any help greatly appreciated.  Thank you.

Jon Titus, KZ1G
Herriman, Utah

Not red, absolutely not red. For those of us who are chromatically challenged.

Tony, don't worry. I endeavour to have all colors in JTAlert user-settable.

In this case, coloring the updates indicator, it is very unlikely to be implemented. But if it is, the color will be user-settable.

A little know fact, I am personally color challenged in one eye only.

de Laurie VK3AMA

Not red, absolutely not red. For those of us who are chromatically challenged.
T

I've been shrinking the band activity columns that I don't use, thus it's about half the size for just FT4&8. Would also like to cancel out the bands I can't use.

I don't know what your achieving by altering the column widths. The overall window size doesn't change so you end up with a lot of empty  window space without any net gain in available screen space, plus the widths are not remembered so you have to do that every time you start JTAlert.

Hiding user-selectable bands is already on the todo list.

de Laurie VK3AMA

I've been shrinking the band activity columns that I don't use, thus it's about half the size for just FT4&8. Would also like to cancel out the bands I can't use.


Sent from Xfinity Connect Application

On 25/08/2019 6:05 am, wbr via Groups.Io wrote:

Hello, I'm a beginner and would like to know where the hamapps callsign database is installed on my computer.
I've searched but am not able find.  I've also tried to catch the path while program was installing but little window
goes by too fast.
Is it important to know where the call sign database is installed? probably not, but I'd still like to know.  Thanks
73, WF4R

"C:\ProgramData\HamApps\Databases\fcc_lotw_eqsl.sqlite"

I advise against trying to modify the data in the file.
If there is an error in the data report it here so it can be corrected for all users.

de Laurie VK3AMA

On 24/08/2019 11:07 pm, Vladimir Doroshenko wrote:

Hello!

Please help, not work scan Wanted Continent and Wanted Prefix. In scan
results I see Continents Needed : 7 and Prefix Not Needed : 0 in all
bands and modes:

[Prefixes : FT8 Modes Only]
Band : ANY - Prefix Not Needed : 0 (Previous : 0)
Band : 160 - Prefix Not Needed : 0 (Previous : 0)
Band : 80 - Prefix Not Needed : 0 (Previous : 0)
Band : 60 - Prefix Not Needed : 0 (Previous : 0)
Band : 40 - Prefix Not Needed : 0 (Previous : 0)
Band : 30 - Prefix Not Needed : 0 (Previous : 0)
Band : 20 - Prefix Not Needed : 0 (Previous : 0)
Band : 17 - Prefix Not Needed : 0 (Previous : 0)
Band : 15 - Prefix Not Needed : 0 (Previous : 0)
Band : 12 - Prefix Not Needed : 0 (Previous : 0)
Band : 10 - Prefix Not Needed : 0 (Previous : 0)
Band : 6 - Prefix Not Needed : 0 (Previous : 0)
Band : 2 - Prefix Not Needed : 0 (Previous : 0)


Other scans work correctly. For example:

[Grids : FT8 Modes Only]
Band : ANY - Grids Not Needed : 893 (Previous : 893)
Band : 160 - Grids Not Needed : 157 (Previous : 157)
Band : 80 - Grids Not Needed : 534 (Previous : 534)
Band : 60 - Grids Not Needed : 0 (Previous : 0)
Band : 40 - Grids Not Needed : 387 (Previous : 387)
Band : 30 - Grids Not Needed : 545 (Previous : 545)
Band : 20 - Grids Not Needed : 421 (Previous : 421)
Band : 17 - Grids Not Needed : 223 (Previous : 223)
Band : 15 - Grids Not Needed : 142 (Previous : 142)
Band : 12 - Grids Not Needed : 58 (Previous : 58)
Band : 10 - Grids Not Needed : 71 (Previous : 71)
Band : 6 - Grids Not Needed : 0 (Previous : 0)
Band : 2 - Grids Not Needed : 5 (Previous : 5)

ADIF file from AAlog 3.9

Thank you!

73!
UW5EKD
Vladimir

Vladimir,

Very likely that for the scans affected your adif log file doesn't contain the required information. Does it contain the <CONT> and <PFX> fields?

Please send me direct (not via this group) a copy of your adif file.

de Laurie VK3AMA

Was working fine, but after a freeze and reinstall of both WSJT-X and JTALERT 2.14.3, WSJT-X starts and runs fine. When I start Jtalert, I get the message: Windows cannot access the specified device, path or file. You may not have appropriate permissions to access them. I suspect a path problem, but don't know how to correct it. BTW the Windows is 10 64bit.
Dave KR4LU

Dave,

Sounds like the shortcut your using to start JTAlert is referencing an incorrect path or file. Is this a user-created shortcut or one automatically created during the JTAlert install? If the later, than very likely you virus protection may have removed the JTAlert.exe file.

Please post an image of the offending error window (pse don't post your entire desktop, just the error window is needed).

de Laurie VK3AMA

Speaking of the "!", it might be nice if it were in red to make it more noticeable.

Ed, K0KC

Ed,

While possible, coloring is unlikely to be implemented. An alternative is to use the Alternate Build of JTAlert which does away with this abbreviation,  instead using plain text, "(Updates)".

de Laurie VK3AMA

Hi Laurie,

Russian JT9 activity w/e.

73
Bill
G4WJS.

RR73

Is there a way to not show modes in which I am not interested? For example, if I'm running FT8, I have no real interest in say JT65. With the recent addition of the FT4 columns, the display is now using up a lot screen real estate - a very valuable commodity in my shack hihi.
Kind Regards,
Dennis W7DRW

Dennis,

It is on the todo list, added by myself when I first coded the F4 support as I knew the user request would be coming ;-)

Until it is implemented, I suggest you don't have the Band Activity window open and rely on a periodic mouse-hover over the Band Activity status to temporarily show the popup window.

de Laurie VK3AMA

Does anyone know the reason for the sudden increase?

de Laurie VK3AMA

Hi Laurie,

Russian JT9 activity w/e.

73
Bill
G4WJS.

--
73
Bill
G4WJS.

I have noticed over the last 2 days, a significant increase in JT9 activity as shown in the JTAlert Band Activity popup and on HamSpots and PSKReporter. Is there a JT9 specific contest on at the moment?

As I type this message 19:30 utc, the daily peak in PSKReporter activity, the top 3 reported modes (last 2 hours) on PSKReporter are FT8, FT4, JT9.
   

Does anyone know the reason for the sudden increase?

de Laurie VK3AMA