Date   

locked Continent filter

Michael Black
 

Was working with another user and noticed that if you turn off the NA continent filter, add United States to the Wanted DXCC, that you still hear "Wanted DXCC" even though the NA checkbox is disabled.

Mike W9MDB




locked Re: Auto-Selecting WSJT-X On Start-Up

 

Yes.  Edit the JTAlert shortcut to include “/wsjtx” (without the quotes) at the end of the shortcut command line.

 

__________

Dan – K4SHQ

CFI/II

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Patrick Hung
Sent: Friday, December 4, 2020 11:50 AM
To: Support@HamApps.groups.io
Subject: [HamApps] Auto-Selecting WSJT-X On Start-Up

 

My incurable and inherent laziness prompts me to ask this: each time I start JTALERT, the program asks me to select between WSJT-X, JTD9, and another - is there a way to set WSJT-X as default, as I do not use the other programs?

Also, is there a setting where I can have the Decodes Window open automatically upon start-up?

Thanks.
--
Patrick - W2TAR


--
Dan - K4SHQ


locked Auto-Selecting WSJT-X On Start-Up

Patrick Hung
 

My incurable and inherent laziness prompts me to ask this: each time I start JTALERT, the program asks me to select between WSJT-X, JTD9, and another - is there a way to set WSJT-X as default, as I do not use the other programs?

Also, is there a setting where I can have the Decodes Window open automatically upon start-up?

Thanks.
--
Patrick - W2TAR


locked Re: Displaying Signal report

Michael Black
 

Settings/Manage Settings
Inline image
Mike W9MDB





On Friday, December 4, 2020, 08:19:04 AM CST, VE3JI <ve3ji@...> wrote:


Hi All

I was wondering if there is any way to display the signal report on the call sign tile .. much like US states or the country are displayed.  the reason being I often do not want to try and call really weak stations.

thanks in advance Ian VE3JI


locked Re: New Country alarm is sounding but the countries listed in JTAlert are not wanted

Ed Stallman
 

I sleep on this over night again , woke up thinking I didn't tell the whole story . I'm using a second Flex it's a 6600 with all the same software  as the 6500 .  I have them both running this morning but I didn't execute ACLog on the 6600 and now I'm not hearing the faults  alarms I wrote about . Is their a way to do this that I'm over looking ? 
Thanks Ed N5DG


locked Displaying Signal report

VE3JI
 

Hi All

I was wondering if there is any way to display the signal report on the call sign tile .. much like US states or the country are displayed.  the reason being I often do not want to try and call really weak stations.

thanks in advance Ian VE3JI


locked JT Alert control of cursor

Fred Collins
 

When I have JT Alert running with WSJT , seems to be working fine, and I am multitasking on another screen, when ever JT Alert comes up it seems to automatically grab control of the cursor.
If in the middle of typing something say into Telegram or a WP program, unless watching the screen, you don't realize your typing has stopped, cursor gone. It seems JT Alert has automatically taken over.
Is there a setting to prevent this or do I just need to turn JT off while I use other programs?
Using WIN7, and V 2.15.10
Thanks Fred W1FC


locked Re: Older version

Tom Melvin
 

Mark

Just a FYI I am running 2.16.16 on a Windows 7 machine and is working fine.

I have not seen any feedback/announcements to say that JTAlert will no longer support (or proposed drop) of Win 7.

It will come at some point but it’s not now.

Will agree with Neil - don’t do back - use the current release, sent a support request in and work out what in your system is misconfigured. It may help with other applications you run.

Tom
GM8MJV


On 4 Dec 2020, at 00:23, Mark Robinson <markrob@...> wrote:

I am running 2.14.2 on a Windows 7 machine. I suspect that the newer versions of JTAlert don't support win 7 now.

I have tried disabling my ZoneAlarm a/v prog but it didn't help. On one occaision the sound and dx lab communication worked but the next time I ran JTAlert it had stopped working.  Probably a win 10 upgrade would fix these issues.

73 Mark N1UK





On 03-Dec-20 5:32 PM, HamApps Support (VK3AMA) wrote:
On 4/12/2020 7:19 am, Mark Robinson wrote:
I managed to go back to an earlier version by just running the earlier install file over the top of the later version. It all seemed to install OK.  Do you still have the earlier install file?

For the guy who asked why...the sound alerts would not work on the later version and I also had issues with the UDP not talking the DXlab so I went back to the fault free earlier version.

73 Mark N1UK

That version is?

Regarding the sound problems, that is likely a UDP issue as well. JTAlert itself doesn't produce sounds, but sends a UDP command to the JTAlertV2.Manager.exe process which is responsible for playing all audio. JTAlert doesn't talk UDP to DXLab, that is purely DDE and TCPIP, and both of those are handled by the same manager process.

It sounds to me like your Protection software (what are you running?) didn't like the newer builds of JTAlert and was blocking all the network traffic to/from the Manager process. There is nothing I can do about overly aggressive or configured Protection software.

de Laurie VK3AMA




locked New Country alarm is sounding but the countries listed in JTAlert are not wanted

Ed Stallman
 

New Country alarm is sounding but the countries listed in JTAlert are not wanted , also none of the audio alerts are colored yellow after the alarm is sounded . I'm using a Flex 6500 , WSJTv2.2.2, ACLog  and JTAlert 2.16.15 . with 2  instances of WSJT and JTAlerts running.. I have JTAlert set to not show NA but as a test I unchecked all continents in JTAlert and still get the audio alarm "New Country" ... Not on all decodes , it's random but happens very often.
 
I've tried many thing . Complete uninstall JTAlerts using REVO Uninstaller , tried other versions of JTAlert , reinstalled new country list plus the sound files, did the scan and rebuild , setup the 2  instances up manually and also used an app called slice master. Each time I change anything in settings , I exit out of both  instances then back up., at time's I'd do a reboot .

Best I can tell , when I hear the audio alert with no colors showing there not real . I made a list after a decode , then looked in settings at the wanted / not wanted . The fault alarms show as " Not Wanted " I tested this by moving countries like France Spain Germany to the " Wanted " list and they do show yellow with red text.  

I've spent allot of time with no joy , I just know I'm messing up somewhere 

Thanks Ed N5DG


locked Re: Colors not working after reinstall.

wa6hoo@...
 

That worked!  Thank you and thank you for JTAlerts.

Do the other two check boxes also need to be checked, as shown in your example?

phil


locked Re: Older version

Mark Robinson
 

I am running 2.14.2 on a Windows 7 machine. I suspect that the newer versions of JTAlert don't support win 7 now.

I have tried disabling my ZoneAlarm a/v prog but it didn't help. On one occaision the sound and dx lab communication worked but the next time I ran JTAlert it had stopped working.  Probably a win 10 upgrade would fix these issues.

73 Mark N1UK





On 03-Dec-20 5:32 PM, HamApps Support (VK3AMA) wrote:
On 4/12/2020 7:19 am, Mark Robinson wrote:
I managed to go back to an earlier version by just running the earlier install file over the top of the later version. It all seemed to install OK.  Do you still have the earlier install file?

For the guy who asked why...the sound alerts would not work on the later version and I also had issues with the UDP not talking the DXlab so I went back to the fault free earlier version.

73 Mark N1UK

That version is?

Regarding the sound problems, that is likely a UDP issue as well. JTAlert itself doesn't produce sounds, but sends a UDP command to the JTAlertV2.Manager.exe process which is responsible for playing all audio. JTAlert doesn't talk UDP to DXLab, that is purely DDE and TCPIP, and both of those are handled by the same manager process.

It sounds to me like your Protection software (what are you running?) didn't like the newer builds of JTAlert and was blocking all the network traffic to/from the Manager process. There is nothing I can do about overly aggressive or configured Protection software.

de Laurie VK3AMA



locked Re: Colors not working after reinstall.

HamApps Support (VK3AMA)
 

On 4/12/2020 10:13 am, wa6hoo@... wrote:
After having many Windows 10 problems, I decided to reinstall the OS or "Reset the PC" as Windows now describes it.  I have most of my software reinstalled (N3FJP's Amateur Contact Log V6.7, JTAlert V 2.16.16 and WSJT-X V2.2.2) and working but I can't get JTAlert to function as before the Windows reinstallation.  The colors remain just the same WSJT-X stock colors of Yellow for TX, Green for CQ and Red for MyCall.  The only one that I remember working previously was the B4 color of gray.  I don't recall making too many changes to the JTAlert software on the first install, so I was surprised that it just didn't work as before when I reinstalled it.

Any specific ideas or links to written instructions, outside of the ones that part of Amateur Contact Log, JTAlert and WSJT-X, which I've already tried.

Thanks much,

phil
WA6HOO!

I think your describing that JTAlert is not coloring the WSJT-X decodes with its Alert colors.
Is that the case? If so, simple, enable the "Accept UDP requests" option in WSJT-X.


This is not something JTAlert can do, it requires you to make the change.

de Laurie VK3AMA


locked Colors not working after reinstall.

wa6hoo@...
 

After having many Windows 10 problems, I decided to reinstall the OS or "Reset the PC" as Windows now describes it.  I have most of my software reinstalled (N3FJP's Amateur Contact Log V6.7, JTAlert V 2.16.16 and WSJT-X V2.2.2) and working but I can't get JTAlert to function as before the Windows reinstallation.  The colors remain just the same WSJT-X stock colors of Yellow for TX, Green for CQ and Red for MyCall.  The only one that I remember working previously was the B4 color of gray.  I don't recall making too many changes to the JTAlert software on the first install, so I was surprised that it just didn't work as before when I reinstalled it.

Any specific ideas or links to written instructions, outside of the ones that part of Amateur Contact Log, JTAlert and WSJT-X, which I've already tried.

Thanks much,

phil
WA6HOO!


locked Re: JT Alert Crashes Upon Any Sound Played

HamApps Support (VK3AMA)
 

On 3/12/2020 12:27 am, Bill Hicks wrote:
On Tue, Dec 1, 2020 at 11:59 AM, HamApps Support (VK3AMA) wrote:
  • What does "Crash" mean exactly? It shuts down and has to be restarted..
  • Is there an error dialog being shown, if so what does it say (post an image)?-No warning or dialog box is shown....
  • Is JTAlert just disappearing or is it becoming non-response?  just disappears
  • What was the last version of JTAlert that worked for you? it has been several versions now at least 4 updates would be my guess. i posted on this when it first started but just lived with it as i got busy with work.  trying to revisit it now.
  •  
I did notice there are four JT alert managers under firewall>allow apps...all are checked to allow all options.

Bill 

You didn't answer my questions. The answers to which would provide me with some insight into what may be happening. I still don't know what you mean by "Crash". Is there an error popup? Is JTAlert becoming non-repressive or simply closing without warning?

My best guess is that your Protection software is interfering and deliberately killing JTAlert as soon as it sees some network traffic.

The JTAlert.exe executable (the main window and process) itself does not play any audio, instead it offloads that task to a background process, the JTAlertV2.Manager.exe. That operation involves sending a UDP message to the Manager. My guess is that your PC protection software is directly interfering with JTAlert.exe as soon as it issues this UDP instruction.

What Protection software are you running?

de Laurie VK3AMA


locked Re: Support File Problem

HamApps Support (VK3AMA)
 

On 3/12/2020 8:46 am, John Becker wrote:
I don't always update software immediately to the latest release, so this may be a problem of my own making, but FWIW here's what I experienced recently.

I was running JTAlert v2.16.10 with whatever version of the Callsign Database was current with that release. I realized that the older Callsign Database was the reason all users were showing a last LoTW update in July. I installed the Callsign Database v2020.11.18 and that took care of the LoTW problem. But it introduced a NEW problem. When right-clicking on an alert to send a message to the operator, I was no longer getting an ONLINE or OFFLINE indication in the message window. I updated JTAlert to v2.16.16 and now all is well again.

I was not aware that updating the Callsign Database by itself could be a problem, but it was in this case.

Thanks for a great program!

73,

John, K9MM

John,

Sorry to "burst your bubble". Updating the Callsign database is not the fix. All that installer does is install 2 sqlite database files. That will not affect Text Messaging. Likely the Text Message service was either having issues at the time or one of its listening ports (there are 4) was temporarily down.

de Laurie VK3AMA


locked Re: 2.16.16 crashes

HamApps Support (VK3AMA)
 

On 4/12/2020 5:36 am, Coy Day wrote:
That didn't last long.  Now I'm getting the error with FT8.

Sorry, I don't have an answer at this time. I am unable to reproduce the defect. Part of the problem is that the line numbers in these errors are typically grossly incorrect and don't point at the true cause. There is likely a coding/logic error, but I haven't found it yet.

At this time, since you already tried 2.16.15, your best to downgrade JTAlert to 2.16.14

de Laurie VK3AMA


locked Re: New JTAlert issue today

HamApps Support (VK3AMA)
 

On 4/12/2020 3:26 am, Dennis wrote:
JTAlert was working fine when I shut down the station last night, but today when I open JTAlert it seems to be fine
until after the first few decode cycles, then this error appears:



When I click OK JTAlert closes.  I have uninstalled and reinstalled all
three applications with the same outcome.

Windows 7, WSJT-X v2.2.2, JTAlert 2.16.16

Dennis,

Sorry, I don't have an answer at this time. I am unable to reproduce the defect. Part of the problem is that the line numbers in these errors are typically grossly incorrect and don't point at the true cause. There is likely a coding/logic error, but I haven't found it yet.

At this time, your best to downgrade JTAlert to 2.16.15 or 2.16.14

de Laurie VK3AMA


locked Re: JTalert Time Setting ?

HamApps Support (VK3AMA)
 

On 3/12/2020 11:45 pm, Bill wrote:

I just noticed, that the contact complete notification popup time/Date of JTalert is completely wrong.

Going through all the menu's and settings, I found no way to set the displayed time and date correctly.

My JTalert somehow is set to March.

How is this corrected ?

Bill
K2WH


Doesn't sound like a JTAlert issue to me.

The only logging notification popup produced by JTAlert is either a "success" or "failure" popup produced post-logging and it doesn't contain any Date/Time information.

Please post an image of the popup you believe is from JTAlert.

Are the QSOs being logged with the correct Date/Time despite the popup error?

Are you perhaps referring to the wsjtx "Log QSO" window?


de Laurie VK3AMA


locked Re: Older version

HamApps Support (VK3AMA)
 

On 4/12/2020 7:19 am, Mark Robinson wrote:
I managed to go back to an earlier version by just running the earlier install file over the top of the later version. It all seemed to install OK.  Do you still have the earlier install file?

For the guy who asked why...the sound alerts would not work on the later version and I also had issues with the UDP not talking the DXlab so I went back to the fault free earlier version.

73 Mark N1UK

That version is?

Regarding the sound problems, that is likely a UDP issue as well. JTAlert itself doesn't produce sounds, but sends a UDP command to the JTAlertV2.Manager.exe process which is responsible for playing all audio. JTAlert doesn't talk UDP to DXLab, that is purely DDE and TCPIP, and both of those are handled by the same manager process.

It sounds to me like your Protection software (what are you running?) didn't like the newer builds of JTAlert and was blocking all the network traffic to/from the Manager process. There is nothing I can do about overly aggressive or configured Protection software.

de Laurie VK3AMA


locked Re: Older version

Mark Robinson
 

I managed to go back to an earlier version by just running the earlier install file over the top of the later version. It all seemed to install OK.  Do you still have the earlier install file?

For the guy who asked why...the sound alerts would not work on the later version and I also had issues with the UDP not talking the DXlab so I went back to the fault free earlier version.

73 Mark N1UK

On 03-Dec-20 1:00 AM, Mel - N7GCO - Cheney, WA wrote:
Is it possible to download an older version of JTAlert?
I didn't see how on the website.

4581 - 4600 of 36991