Date   

locked Re: False alert for P29ZL

Phil Cooper
 

Uwe and Laurie,

 

I’ve just had a look at the data from this, and it looks like I saw the 3Z90IARU calling T6AA, as T6AA had been shown in the JTAlert box. As it happened, HF90IARU had indeed called him and because there were so many calls, I only noticed 3Z90IARU.

 

Anyway, I am pleased you have identified the problem, and it is now fixed.

 

73 de Phil GU0SUP

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Uwe
Sent: 03 February 2020 10:16
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 Re: Double entries on JTAlert Decodes window with instances / Clue

HamApps Support (VK3AMA)
 

On 4/02/2020 4:52 pm, asobel@... wrote:

Here is your clue. See the attached files. It's just the filter.

Amos 4X4MF


Amos,

Please post an image of your Decodes Filter status when your getting the doubled decodes display. Use the "Filter -> View detailed Filter status" menu.

de Laurie VK3AMA


locked Re: Double entries on JTAlert Decodes window with instances / Clue

HamApps Support (VK3AMA)
 

On 4/02/2020 4:52 pm, asobel@... wrote:

Dear Laurie

Here is your clue. See the attached files. It's just the filter.

Amos 4X4MF


Amos,

Thanks for that.
This will help greatly in tracking down the defect.

Applying a filter producing a double listing is unexpected and it is not immediately obvious to me how that is happening.
Once I can reproduce the defect in testing a fix should be easy. Once corrected I will send you a link to a new build.

de Laurie VK3AMA


locked Re: unable to start up JTAlert for WSJT-X

HamApps Support (VK3AMA)
 

On 4/02/2020 11:16 am, Jim Sharp wrote:
When i launch 2.15.8     it starts up ok but then displays "Select Sound Output Device" with a blank drop down.
Closing this window bombs out JT Alert
Help please
_
This is the first report of JTAlert not detecting your Windows Sound devices.

Did previous versions of JTAlert work?

If your running Windows 10, it is always good practice to perform a PC restart whenever you encounter unusual or broken application behaviour (not just with JTAlert, any application).

de Laurie VK3AMA


locked Re: JT-Alert al for WSJT-X

HamApps Support (VK3AMA)
 

On 5/02/2020 5:42 am, jgmags2000 via Groups.Io wrote:
Is it a problem with the Windows 10 or is something wrong with JT-Alert?

Thanks for a reply.
73, John
KJ1J
Most likely a problem with your WSJT-X installation if JTAlert is working with JTDX.
What version of WSJT-X? Make sure you using the latest v2.1.2
Is it the official release or one you compiled your self?
Do you have WSJT-X set to run as Administrator? If so turn that off (check both the wsjtx.exe file and the shortcut you used to start WSJT-X)

If JTAlert is showing an Instance number in the waiting message it means that JTAlert is already running but not visible, a PC restart will fix that.

de Laurie VK3AMA



locked JT-Alert al for WSJT-X

jgmags2000
 

I have JT-Alert 2.15.8 and Windows 10 1909..
"waiting or WSJT-X to start"
WSJT-X starts..BUT "WSJT-x is starting but JT-Alert is still running to "wait for WSJT-X to start" If i clip the x in the top right corner all will unload.
Either the standard or the AL jt-alert will not work properly.
JT-Alert works fine for JTDX.

I uninstalled 2,15.8 and re-installed 2.15.5. but still the same.
Is it a problem with the Windows 10 or is something wrong with JT-Alert?

Thanks for a reply.
73, John
KJ1J


locked Re: Computer monitors go black

davebacon1377
 

Tnx you agn.

 

73

Sam

 

From: John
Sent: Tuesday, February 4, 2020 8:41 AM
To: support
Subject: Re: [HamApps] Computer monitors go black

 

Clean the dust out of the computer fans, dust filters, heatsinks etc.

 

I blow the dust out of my machine twice a year.

 

PC's are great air filtration systems.

 

John

VE3KKQ

 

> ---------- Original Message ----------

> From: chas cartmel <chas@...>

> Date: February 4, 2020 at 7:32 AM

>

>

> That sounds like a PC failure somewhere, power supply or  memory perhaps.

> Could even be a graphics card issue. It may be overheating due to a clogged

> fan intake or even the case fan has died. I assume you have already checked

> your drivers are up to date.

> Run a memory check and check cooling.

>

>

>

>

> Charlie

>

> G4EST

>

> www.g4est.me.uk

>

>

>

>

>

>

>

>

> From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf

> Of davebacon1377

> Sent: 04 February 2020 13:22

> To: Support@HamApps.groups.io

> Subject: [HamApps] Computer monitors go black

>

>

> This is a shot in the dark but has anyone reported that while running JTAlert

> and WSJT-X their computer monitors go black?

>

> The computer also locks up and must be unplugged to reboot.

>

>

> Sam

>

> KD2T

>

>

>

>

> Sent from my Verizon, Samsung Galaxy smartphone

>

>

>

>

>

> This email has been scanned by BullGuard antivirus protection.

> For more info visit www.bullguard.com

> <http://www.bullguard.com/tracking.aspx?affiliate=bullguard&buyaffiliate=smtp&url=/>

>

>

>

 

 

 


locked Re: Computer monitors go black

K9MK
 

Mine went dark a couple months back. But just the left one. 

One of the two Video card fans stopped.  

Replaced fan and it has been working since.

Also vacuumed the dust out and then air sprayed it to be sure.

 

MK

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of davebacon1377
Sent: Tuesday, February 04, 2020 9:03 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Computer monitors go black

 

Tnx you Charlie.

 

73 Sam

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 

 

-------- Original message --------

From: chas cartmel <chas@...>

Date: 2/4/20 8:32 AM (GMT-05:00)

To: Support@HamApps.groups.io

Subject: Re: [HamApps] Computer monitors go black

 

That sounds like a PC failure somewhere, power supply or  memory perhaps. Could even be a graphics card issue. It may be overheating due to a clogged fan intake or even the case fan has died. I assume you have already checked your drivers are up to date.
Run a memory check and check cooling.



Charlie

G4EST

www.g4est.me.uk

 





 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of davebacon1377
Sent: 04 February 2020 13:22
To: Support@HamApps.groups.io
Subject: [HamApps] Computer monitors go black

 

This is a shot in the dark but has anyone reported that while running JTAlert and WSJT-X their computer monitors go black?

The computer also locks up and must be unplugged to reboot.

 

Sam

KD2T 

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 


locked Re: Computer monitors go black

davebacon1377
 

Tnx you Charlie.

73 Sam



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: chas cartmel <chas@...>
Date: 2/4/20 8:32 AM (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Computer monitors go black

That sounds like a PC failure somewhere, power supply or  memory perhaps. Could even be a graphics card issue. It may be overheating due to a clogged fan intake or even the case fan has died. I assume you have already checked your drivers are up to date.
Run a memory check and check cooling.


Charlie

G4EST

www.g4est.me.uk

 




 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of davebacon1377
Sent: 04 February 2020 13:22
To: Support@HamApps.groups.io
Subject: [HamApps] Computer monitors go black

 

This is a shot in the dark but has anyone reported that while running JTAlert and WSJT-X their computer monitors go black?

The computer also locks up and must be unplugged to reboot.

 

Sam

KD2T 

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 


locked Re: Computer monitors go black

John
 

Clean the dust out of the computer fans, dust filters, heatsinks etc.

I blow the dust out of my machine twice a year.

PC's are great air filtration systems.

John
VE3KKQ

---------- Original Message ----------
From: chas cartmel <chas@...>
Date: February 4, 2020 at 7:32 AM


That sounds like a PC failure somewhere, power supply or memory perhaps.
Could even be a graphics card issue. It may be overheating due to a clogged
fan intake or even the case fan has died. I assume you have already checked
your drivers are up to date.
Run a memory check and check cooling.




Charlie

G4EST

www.g4est.me.uk










From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf
Of davebacon1377
Sent: 04 February 2020 13:22
To: Support@HamApps.groups.io
Subject: [HamApps] Computer monitors go black



This is a shot in the dark but has anyone reported that while running JTAlert
and WSJT-X their computer monitors go black?

The computer also locks up and must be unplugged to reboot.



Sam

KD2T







Sent from my Verizon, Samsung Galaxy smartphone






This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com
<http://www.bullguard.com/tracking.aspx?affiliate=bullguard&buyaffiliate=smtp&url=/>




locked Re: Computer monitors go black

chas cartmel
 

That sounds like a PC failure somewhere, power supply or  memory perhaps. Could even be a graphics card issue. It may be overheating due to a clogged fan intake or even the case fan has died. I assume you have already checked your drivers are up to date.
Run a memory check and check cooling.


Charlie

G4EST

www.g4est.me.uk

 




 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of davebacon1377
Sent: 04 February 2020 13:22
To: Support@HamApps.groups.io
Subject: [HamApps] Computer monitors go black

 

This is a shot in the dark but has anyone reported that while running JTAlert and WSJT-X their computer monitors go black?

The computer also locks up and must be unplugged to reboot.

 

Sam

KD2T 

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


locked Computer monitors go black

davebacon1377
 

This is a shot in the dark but has anyone reported that while running JTAlert and WSJT-X their computer monitors go black?
The computer also locks up and must be unplugged to reboot.

Sam
KD2T 



Sent from my Verizon, Samsung Galaxy smartphone


locked Re: False alert for P29ZL

davebacon1377
 

I agree with that statement. Thanks for your help.

 

73

Sam

KD2T

 

From: Uwe
Sent: Tuesday, February 4, 2020 4:25 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] False alert for P29ZL

 

Thanks Laurie,
Excellent level of support (as always)! Looking forward to the new version...
73 de Uwe, DG2YCB

 


locked Re: False alert for P29ZL

Uwe, DG2YCB
 

Thanks Laurie,
Excellent level of support (as always)! Looking forward to the new version...
73 de Uwe, DG2YCB


locked Re: Double entries on JTAlert Decodes window with instances / Clue

asobel@...
 

Dear Laurie

 

Here is your clue. See the attached files. It's just the filter.

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: יום ב 03 פברואר 2020 06:46
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:

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: TI9A reports as Cocos (Keeling) rather than Cocos Island.

HamApps Support (VK3AMA)
 

Walt,

Tnx for the report.

This is a cosmetic defect, affecting the Country name display only.

Internally, JTAlert uses the correct dxcc #37 (Cocos Island) for alerting and logging of TI9A.

This has been corrected for the next release (later this week).

de Laurie VK3AMA

On 4/02/2020 10:23 am, Walt Flesher wrote:

Running 2.15.8 here.

--
73 de W6SA

Walt Flesher


locked unable to start up JTAlert for WSJT-X

Jim Sharp
 

When i launch 2.15.8     it starts up ok but then displays "Select Sound Output Device" with a blank drop down.
Closing this window bombs out JT Alert
Help please


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

HamApps Support (VK3AMA)
 

On 4/02/2020 9:17 am, WA2NDV via Groups.Io wrote:
Unfortunately that did not fix the issue.

I have noticed that new log entries show up immediately in the HRD log whereas in the past I would have to refresh the logbook to see new entries--however the name was always there.

Ill send you the logs .

73
Frank
WA2NDV
The problem is that you don't have an XML service enabled in JTAlert, so the only Name data that gets logged is the Name found from a previous QSOs search of your log.

If a new, never worked B4 callsign, and no XML service enabled than JTAlert has nothing to add to the basic QSO data, like Name, QTH, etc, and in that case you will have to perform the XML lookups in HRDLogbook post logging.

de Laurie VK3AMA


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

WA2NDV <frankatcvc@...>
 

Laurie,

Unfortunately that did not fix the issue.

I have noticed that new log entries show up immediately in the HRD log whereas in the past I would have to refresh the logbook to see new entries--however the name was always there.



Ill send you the logs .

73
Frank
WA2NDV


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