Date   

locked Re: Almost no QRZ-XML lookups succeed since 2.15.8

HamApps Support (VK3AMA)
 

On 4/02/2020 8:43 am, WA2NDV via Groups.Io wrote:
I have noticed he same issue with NAME not being populated in HRD logbook.

As Laurie stated the only entry with a NAME are from previous log entries.

After the NAME failure I open the HRD log entry and hit the "lookup" button next to the callsign and the NAME will be populated showing that the lookup is working from within the HRD logbook.




73
Frank
WA2NDV

Frank,

Do a PC restart and all should start working (assuming it is the same error as the original report).

de Laurie VK3AMA



locked Re: Almost no QRZ-XML lookups succeed since 2.15.8

WA2NDV <frankatcvc@...>
 

I have noticed he same issue with NAME not being populated in HRD logbook.

As Laurie stated the only entry with a NAME are from previous log entries.

After the NAME failure I open the HRD log entry and hit the "lookup" button next to the callsign and the NAME will be populated showing that the lookup is working from within the HRD logbook.




73
Frank
WA2NDV


locked Re: False alert for P29ZL

HamApps Support (VK3AMA)
 

On 3/02/2020 9:15 pm, Uwe wrote:
Hi Laurie,
I don't know if this has already been reported. This morning I got a false alert for P29ZL. OL725PLZ was calling that station. Looks like that two special callsigns were trying to call each other. Maybe a hash code collision? Anyway, JTAlert shouldn't have alerted me because P29ZL was not calling but getting called. (And likely due to this I've falsly posted P29ZL to Hamspots.net.)
73 de Uwe, DG2YCB
Uwe,

Thanks for the report. Yours is the first.
I can confirm the defect which is already corrected for the next public release (towards the end of this week).

The problem is caused by recent changes in decode message processing. To improve performance and allow many of the now common special event callsigns to be alerted, the strict callsign and message structure validation was altered. This change caused this defect, previously fixed in version 2.12.10, to occur.

The trigger for the defect is that the calling station, "OL725PLZ", in a two word only decode, "<P29ZL> OL725PLZ", is being interpreted as a grid, "OL72", causing JTAlert to consider the first word, "<P29ZL>", as the transmitting callsign.

This defect affects other current special event callsigns like "HF90IARU" since "HF90" is a valid grid. Other "IARU" callsigns like "SN75IARU" & "SO15IARU" are not affected since the first 4 characters of their callsign is not a valid grid.

It took me longer to write this email than it did to correct the defect, Hi.

de Laurie VK3AMA


locked Re: Jtalert for windows xp

HamApps Support (VK3AMA)
 

On 4/02/2020 1:43 am, lozere15@... wrote:
I got a laptop with windows xp
i want to install JTaler and wsjt x
what should i do to make it work
Hope to read you 73 qro
amites
The last version of JTAlert that worked with XP was 2.11.5
This is available from https://hamapps.com/JTAlert/ near the bottom of the page.

2.11.5 is no longer officially supported and will likely fail in many of its functions especially if you try to use any of the online services or recent versions of WSJT-X.
Performance is likely to be a problem on an aging XP laptop especially with the high CPU demands of WSJT-X.

I personally would not recommend using Win XP.

de Laurie VK3AMA


locked Re: Error with JTAlert

Michael Black
 

You need to install the latest 32-bit X86 VC runtime....


It's the vc_redist.x86.exe

de Mike W9MDB


On Monday, February 3, 2020, 09:17:20 AM CST, David Rounds <groups@...> wrote:


Dave,
This issue has been answered several times in this group.
Laurie posted the following on 1/25/20 (and again on 1/30):

On 26/01/2020 3:35 am, edward bishop via Groups.Io wrote:

jt-alert 2.15.8 i get error when start WSJT-X or WSJT-Z when start JTDX it open . now when i hit setting on jt-alert  i get mysql start Failure program now exit . i rollback to jt-alert 2.15.6 everything works.


The problem is that something is preventing the MySQL client dll from loading (during the Settings startup). The difference between 2.15.6 and 2.15.8 is that the later has had additional code added to report on this failure, in previous versions it was failing quietly which caused problems for anyone using a Logger with MySQL logs, HRD & Log4OM.

At this time, I don't know the cause.

I suggest you stay with the older version, I strongly suggest at 2.15.7 rather than 2.15.6


On 2/2/2020 5:25 PM, davebacon1377 wrote:

Sri I sent a screen shot but I guess it didn’t work. The error is as follows:

 

MySQL start Failure, Program will not exit

 

73

 

Sam

KD2T

 

From: HamApps Support (VK3AMA)
Sent: Sunday, February 2, 2020 5:58 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Error with JTAlert

 

What is the error? Your message referred to an error but nothing was

provided.

 

de Laurie VK3AMA

 

 

 

 



locked Re: Error with JTAlert

David Rounds
 

Dave,
This issue has been answered several times in this group.
Laurie posted the following on 1/25/20 (and again on 1/30):

On 26/01/2020 3:35 am, edward bishop via Groups.Io wrote:

jt-alert 2.15.8 i get error when start WSJT-X or WSJT-Z when start JTDX it open . now when i hit setting on jt-alert  i get mysql start Failure program now exit . i rollback to jt-alert 2.15.6 everything works.


The problem is that something is preventing the MySQL client dll from loading (during the Settings startup). The difference between 2.15.6 and 2.15.8 is that the later has had additional code added to report on this failure, in previous versions it was failing quietly which caused problems for anyone using a Logger with MySQL logs, HRD & Log4OM.

At this time, I don't know the cause.

I suggest you stay with the older version, I strongly suggest at 2.15.7 rather than 2.15.6


On 2/2/2020 5:25 PM, davebacon1377 wrote:

Sri I sent a screen shot but I guess it didn’t work. The error is as follows:

 

MySQL start Failure, Program will not exit

 

73

 

Sam

KD2T

 

From: HamApps Support (VK3AMA)
Sent: Sunday, February 2, 2020 5:58 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Error with JTAlert

 

What is the error? Your message referred to an error but nothing was

provided.

 

de Laurie VK3AMA

 

 

 

 



locked Jtalert for windows xp

lozere15@...
 

I got a laptop with windows xp
i want to install JTaler and wsjt x
what should i do to make it work
Hope to read you 73 qro
amites

 


locked Re: False alert for P29ZL

Phil Cooper
 

Hi Laurie and Uwe,

 

I have seen exactly the same. T6AA was on 80m (which I need!) and he was showing up in the RX box (as per the picture from Uwe with P29ZL) but he was being called, not calling in that period.

The result was that folk were calling him on the wrong period.

 

I also noticed it with a few other calls, and all seemed to be from stations with a non-standard callsign, and in the case of T6AA, it was some of the 3Z*IARU calls that were calling him.

 

73 de Phil GU0SUP

 

 

-----Original Message-----
From: "Uwe" <DG2YCB@...>
Sent: Monday, 3 February, 2020 10:15
To: Support@HamApps.groups.io
Subject: [HamApps] False alert for P29ZL

Hi Laurie,
I don't know if this has already been reported. This morning I got a false alert for P29ZL. OL725PLZ was calling that station. Looks like that two special callsigns were trying to call each other. Maybe a hash code collision? Anyway, JTAlert shouldn't have alerted me because P29ZL was not calling but getting called. (And likely due to this I've falsly posted P29ZL to Hamspots.net.)
73 de Uwe, DG2YCB


locked False alert for P29ZL

Uwe, DG2YCB
 

Hi Laurie,
I don't know if this has already been reported. This morning I got a false alert for P29ZL. OL725PLZ was calling that station. Looks like that two special callsigns were trying to call each other. Maybe a hash code collision? Anyway, JTAlert shouldn't have alerted me because P29ZL was not calling but getting called. (And likely due to this I've falsly posted P29ZL to Hamspots.net.)
73 de Uwe, DG2YCB


locked Re: Double entries on JTAlert Decodes window with instances

asobel@...
 

Laurie

 

Which JTAlert files do you want me to send?

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: יום ב 03 פברואר 2020 06:57
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Double entries on JTAlert Decodes window with instances

 

On 3/02/2020 3:20 pm, asobel@... wrote:

Laurie

 

I did turn my station off for the night and on this moerning.

 

The duplication phenomenon of one instance did repeat the same as yesterday.

 

Amos 4X4MF

 

OK,

I will need to see your JTAlert files for when this is happening.

Use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis. Include a note of the utc date/time when this was observed and the instance # and Decodes "src" column value (ie the WSJT-X rig-name parameter)

de Laurie VK3AMA


locked Re: Spots from JTDX > JTAlert > Hamspots

HamApps Support (VK3AMA)
 

On 3/02/2020 4:03 pm, HamApps Support (VK3AMA) via Groups.Io wrote:

  first to go are PSKReporter Spots, then all PSKReporter Spots
That should read "first to go are PSKReporter FT8 only Spots, then all PSKReporter Spots (the feed is turned off)"

de Laurie VK3AMA


locked Re: Spots from JTDX > JTAlert > Hamspots

HamApps Support (VK3AMA)
 

On 3/02/2020 12:54 pm, neil_zampella wrote:

I suspect more a problem with JTDX, as it has been known to deviate from the WSJT-X standard in the past.

 

Neil, KN3ILZ


Not a JTDX or JTAlert problem. A HamSpots problem as it had to shed a significant amount of incoming spot data as it was experiencing unacceptable levels of load due to some badly coded (I assume) bots trying to harvest spots data by screen-scraping the html pages.

When HamSpots discards spots, first to go are PSKReporter Spots, then all PSKReporter Spots, then JTAlert JTDX spots ("T" spots) and finally JTAlert WSJT-X spots ("X" spots). Yesterday I had to drop all but WSJT-X spots in order to get the load down.

de Laurie VK3AMA




locked Re: Double entries on JTAlert Decodes window with instances

HamApps Support (VK3AMA)
 

On 3/02/2020 3:20 pm, asobel@... wrote:

Laurie

 

I did turn my station off for the night and on this moerning.

 

The duplication phenomenon of one instance did repeat the same as yesterday.

 

Amos 4X4MF

 

OK,

I will need to see your JTAlert files for when this is happening.

Use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis. Include a note of the utc date/time when this was observed and the instance # and Decodes "src" column value (ie the WSJT-X rig-name parameter)

de Laurie VK3AMA


locked Re: Double entries on JTAlert Decodes window with instances

HamApps Support (VK3AMA)
 

On 3/02/2020 3:20 pm, asobel@... wrote:

I did turn my station off for the night and on this moerning.

 

The duplication phenomenon of one instance did repeat the same as yesterday.

 

Amos 4X4MF

OK,

Please use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: Double entries on JTAlert Decodes window with instances

asobel@...
 

Laurie

 

I did turn my station off for the night and on this moerning.

 

The duplication phenomenon of one instance did repeat the same as yesterday.

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: יום ב 03 פברואר 2020 01:00
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Double entries on JTAlert Decodes window with instances

 

On 3/02/2020 8:27 am, asobel@... wrote:

For your attention:

See below a snip of my Decodes window. Instance alcBB is always double while instance slc is always single. In addition, not shown here, sometimes entries are missing.

 

Amos 4X4MF

Please restart JTAlert. Does the duplicate entries still occur?
If so, perform a PC restart and let me know if the duplication continues.

de Laurie VK3AMA


locked Re: Spots from JTDX > JTAlert > Hamspots

davebacon1377
 

Tnx for getting back. Thanks to the help people it's fixed.

Sam 
KD2T 



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: neil_zampella <neilz@...>
Date: 2/2/20 8:54 PM (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Spots from JTDX > JTAlert > Hamspots

I suspect more a problem with JTDX, as it has been known to deviate from the WSJT-X standard in the past.

 

Neil, KN3ILZ


locked Re: Spots from JTDX > JTAlert > Hamspots

neil_zampella
 

I suspect more a problem with JTDX, as it has been known to deviate from the WSJT-X standard in the past.

 

Neil, KN3ILZ


locked Re: Error with JTAlert

davebacon1377
 

Sri I sent a screen shot but I guess it didn’t work. The error is as follows:

 

MySQL start Failure, Program will not exit

 

73

 

Sam

KD2T

 

From: HamApps Support (VK3AMA)
Sent: Sunday, February 2, 2020 5:58 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Error with JTAlert

 

What is the error? Your message referred to an error but nothing was

provided.

 

de Laurie VK3AMA

 

 

 

 


locked Re: Double entries on JTAlert Decodes window with instances

HamApps Support (VK3AMA)
 

On 3/02/2020 8:27 am, asobel@... wrote:

For your attention:

See below a snip of my Decodes window. Instance alcBB is always double while instance slc is always single. In addition, not shown here, sometimes entries are missing.

 

Amos 4X4MF

Please restart JTAlert. Does the duplicate entries still occur?
If so, perform a PC restart and let me know if the duplication continues.

de Laurie VK3AMA


locked Re: Error with JTAlert

HamApps Support (VK3AMA)
 

What is the error? Your message referred to an error but nothing was provided.

de Laurie VK3AMA