Date   

locked QSL Flags ver. 2.50.2

JA9IFF Jim Nakajima
 

Dear Laurie,

Various QSL flag displays are grouped in the upper right corner, making it difficult to judge just by the difference in symbols.
Is it possible to set it back to the original corner position?

JA9IFF
Jim Nakajima


locked Re: Filters - A feature request

HamApps Support (VK3AMA)
 

On 23/06/2021 8:50 am, Seb wrote:
Laurie the Decodes DX panel doesn't appear to be working.  I'm seeing DX stations on the other panels (RR73, CQ, and Distant decodes).

Regardless, this is an incredible update.

73 de W4AS

That's correct behavior. If you have multiple panels visible, a DX callsign may appear in multiple panels/views depending on the type of decode that panel is set for. A DX station calling CQ will appear in both CQ and DX panels if you have both visible. They are not mutually exclusive.

The DX Decodes view will show all callsigns that originate from a country other than your own regardless of the type of decode or Alerts triggered.

de Laurie VK3AMA


locked Re: New install

Chris Levingston
 

20.50.2 fixed the problem, thanks heaps, Laurie - Chris


locked Re: Filters - A feature request

Seb
 

Laurie the Decodes DX panel doesn't appear to be working.  I'm seeing DX stations on the other panels (RR73, CQ, and Distant decodes).

Regardless, this is an incredible update.

73 de W4AS


locked #Important : JTDX users MUST use the JTAlert JTDX shortcut #Important

HamApps Support (VK3AMA)
 

In recent weeks there have been a number of users repeatedly spotting FT4 spots to HamSpots as Q65.

This is caused by the user using the JTAlert WSJT-X shortcut when running JTDX.

The problem stems from changes the JTDX people made to the WSJT-X UDP protocol. Specifically, the UDP decode message contains a single character that identifies the mode for the decode. The WSJT-X standard uses ":" to identify Q65, but JTDX chose to use ":" to identity FT4 decodes.

JTAlert overcomes this by using an alternate character to mode mapping table for JTDX users.

To change the character to mode mapping JTAlert needs to know what application you have JTAlert working against, WSJT-X or JTDX, this is why there are different shortcuts to start JTAlert, the Red "X" icon for WSJT-X and the Blue "X" icon for JTDX. This has been in place for quite some time.

Recently a number of users have been using the WSJT-X shortcut when running JTDX, as a result, if they are working FT4 all spots to HamSpots are flagged as Q65.

The fix is simple, use the correct JTAlert shortcut.


de Laurie VK3AMA


locked JTAlert 2.50.2 install on Windows 10 Edge #FT8

Pedro Alonso
 

I tried to install JtAlert 2.50.2 and get this message: " JTAlert 2.50.2 install x64.exe was blocked because it could harm your devise" 
Is there a way to install it on Windows 10, running Edge browser ?

Thank you,
Pedro


locked Re: Filters - A feature request

HamApps Support (VK3AMA)
 

On 23/06/2021 7:08 am, Mike Flowers wrote:
I think 'Decodes DX' view type excludes DX stations with a B4 status - is this correct?
Only if you have the "Alerts -> Filters -> Do not show B4 Callsigns" filter set on the main JTAlert window, otherwise the B4's should flow through to the "Decodes DX" view (and all other views).

If you don't have the B4 filter enabled and the callsigns are not displayed in Callsigns window let me know and I will do some investigation.

FYI, Filtering that is set in the main JTAlert window will eventually migrate over to the new Callsigns window, but that is unlikely in the near future.

de Laurie VK3AMA


locked Re: Filters - A feature request

Mike Flowers
 

I have installed v2.50.2 and it's working great!  Thank you very much for all the effort you've put into JTAlert!!  It's awesome!

I think 'Decodes DX' view type excludes DX stations with a B4 status - is this correct?


locked Re: Help with JTAlert 2.50.1

Dave Garber
 



on a first install, nothing will be set.  I believe there are instructions around to fix this



Dave Garber
VE3WEJ / VE3IE


On Tue, Jun 22, 2021 at 3:37 PM <robertsimoneau1955@...> wrote:
I installed N3FJP Amateur Contract Log, WSJT-X, and JTAlert. When I start them, the JTAlert Window Title says [???m,,ACL,#1}, and the Call is not transferred to ACL for the lookup function. Hass anyone seen that ???m below.


locked Re: JTAlert version 2.50.2

Dave Garber
 

sometimes I have had things like this happen, but changing from EDGE to Chrome sometimes helps


Dave Garber
VE3WEJ / VE3IE


On Tue, Jun 22, 2021 at 4:37 PM Ronald Ford <rjf802@...> wrote:
I hope someone can give me some guidance...I have been downloading JTAlert for some time...never had an issue.  Today when I try to download the new version my Windows 10 and Window Defender will not allow me to even start installing the program.  It does not even show up in the download file area.  I receive a message:  Failed-Virus Detected.  Can someone give me a method to get around this...Thanks in advance....
--
73
Ronald, W4RJF


locked Re: JTAlert version 2.50.2

AB8WD-Willie
 

Windows security disable it download install update turn security back on

If you are getting a window that says hit run anyway use it 


locked JTAlert version 2.50.2

Ronald Ford
 

I hope someone can give me some guidance...I have been downloading JTAlert for some time...never had an issue.  Today when I try to download the new version my Windows 10 and Window Defender will not allow me to even start installing the program.  It does not even show up in the download file area.  I receive a message:  Failed-Virus Detected.  Can someone give me a method to get around this...Thanks in advance....
--
73
Ronald, W4RJF


locked Re: MS Shenanigans

 

Laurie has released 2.50.2 just a short while ago, and indeed it fixes the sound issue with .net 5.07.
Thanks Laurie for your awesome support as always!

Just a small warning: Windows Defender (fully updated) on Windows 10 pro flags 2.50.2 as a virus, so you have to do put in an exception, and then you can successfully  download and install it. I don't know about other anti-virus programs - norton, mcafee etc. -  since I don't use them.

73 de k1jbd
bammi


locked Re: MS Shenanigans

Joe Subich, W4TV
 

In the next day or two it won't make any difference. Laurie has already
announced the fixed code running and in the hands of the beta team.

73,

... Joe, W4TV

On 2021-06-22 10:35 AM, Mike KC7V wrote:
I have to uninstall 5.07 everyday (maybe more if I check) and install 5.06.  I have updates paused but it makes no difference.
--
Mike KC7V


locked #Announcement #NewRelease : JTAlert 2.50.2 is available - Fix for NET 5.0.7 defect #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The latest JTAlert version 2.50.2 is now available @ https://hamapps.com/JTAlert/

This release overcomes the NET 5.0.7 defect that breaks audio playback and causes the Callsigns window to open/close repeatedly.
The Callsigns window has undergone a major change introducing a multi-view layout
 
Please review the release notes at the end of this message.

de Laurie VK3AMA

Release Notes.

2.50.2 (2021-Jun-22)

  *** Includes Callsign database file version 2021-06-22 (2021-Jun-22)

  New:

    - Callsigns Window: New multi-panel display consisting of a main (non-removable)
       display panel and up to 6 optional sub-panels. Each display panel can be set
       to display a different decode view. Some decode views offer additional options
       like sorting by km for the distance view and sorting by dB value for the
       SNR decodes view. There are 25 different decode views available...
         "All Decodes", "Callers", "Decodes DX", "Decodes Local", "CQ", "CQ Directed",
         "SNR weak decodes", "SNR strong decodes", "Distant decodes", "QSL Lotw decodes",
         "QSL Eqsl decodes", "RR73/73 decodes", "Alerts None", "Alerts Only", "Alert DXCC",
         "Alert US State", "Alert VE Province", "Alert Continent", "Alert CQ Zone",
         "Alert ITU Zone", "Alert Grid", "Alert FFMA Grid", "Alert Prefix", "Alert Marathon",
         "Alert Wanted Call".
       Please refer to the 2.50 features help file, Callsigns Window topic.

    - Decodes Window: Callsigns generating DXCC, US State or VE Province alerts
       now highlight the Country, State and Province name entries.

    - Off-screen windows: Menu entry under the "View" menu to bring ALL 2.50.x
       introduced windows (Callsigns, Messaging, Activity and BandHeat) into
       view on the primary Windows display.

    - WSJT-X UDP: Dedicated "Help" menu entry to the WSJT-X UDP Setup topic.
       The help topic provides simplified 4 step multicast instructions.

  Changes:

    - Qsl flags: The flags used to indicate Lotw and Eqsl membership have been replaced
       with user-selectable symbols. See the "Callsigns" section of the Callsigns window
       options popup. All Qsl symbols and the Online symbol are grouped together and are
       automatically positioned depending on the Badge position and if the Country area
       is visible. Note: The Decodes window still uses the old style flags.

    - Online symbol: The symbol used to display if a Callsign has JTAlert messaging enabled
       is now user-selectable. Previously it was hard-coded to be a star symbol.

  Fixes:

    - Alert audio: Broken or no Alert audio and Callsigns window repeatedly opening/closing.
       Caused by a defect in the NET 5.0.7 Desktop Runtime causing a fatal error in the
       audio library used by JTAlert.

    - HRD Logging: Random QSOs logged with a Submode when not an MFSK Mode. (2.50.0 defect)

    - QSO History: Random showing FT4 results when in FT8 mode. (2.50.0 defect)

    - Marathon Alert: Triggered countries and zones not being shown in the callsign
       info tooltip of the Callsigns window. (2.50.0 defect)

    - Messaging: Only available on the first instance (#1) of JTAlert and its
       child windows. (2.50.0 design limitation).

    - Windows user accounts: JTAlert would not run correctly when used from multiple
      user accounts. It would typically work correctly for the user account under
      which JTAlert was first started.



locked Help with JTAlert 2.50.1

robertsimoneau1955@...
 

I installed N3FJP Amateur Contract Log, WSJT-X, and JTAlert. When I start them, the JTAlert Window Title says [???m,,ACL,#1}, and the Call is not transferred to ACL for the lookup function. Hass anyone seen that ???m below.


locked Re: MS Shenanigans

Mike KC7V
 

I have to uninstall 5.07 everyday (maybe more if I check) and install 5.06.  I have updates paused but it makes no difference.

--
Mike KC7V


locked Re: MS Shenanigans

Dave (NK7Z)
 

That's it...

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 6/21/21 8:24 PM, Jim Cooper wrote:
On 21 Jun 2021 at 19:59, Dave (NK7Z) wrote:

If you go to ADVANCED settings from
the UPDATE page, you can push
updates out a few weeks to a month. Look on the bottom of the page, there
is a drop down that goes out at
least a month.  This is Windows 10
graphic


locked Re: MS Shenanigans

Jim Cooper
 

On 21 Jun 2021 at 19:59, Dave (NK7Z) wrote:

> If you go to ADVANCED settings from
> the UPDATE page, you can push
> updates out a few weeks to a month.
> Look on the bottom of the page, there
> is a drop down that goes out at
> least a month.  This is Windows 10

graphic
  


locked Re: MS Shenanigans

Dave (NK7Z)
 

If you go to ADVANCED settings from the UPDATE page, you can push updates out a few weeks to a month. Look on the bottom of the page, there is a drop down that goes out at least a month. This is Windows 10 2Hx.

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 6/21/21 1:09 PM, Dave Garber wrote:
you should be able to at least tell updates to delay 7 days, and maybe select telling windows to download, but not install, unless you select yes.
Dave Garber
VE3WEJ / VE3IE
On Mon, Jun 21, 2021 at 2:23 PM Dave NT9E <nt9e@comcast.net <mailto:nt9e@comcast.net>> wrote:
I uninstalled 5.0.7 and installed 5.0.6 and when I leave the room
for a time 5.0.6 is uninstalled and 5.0.7 has been installed again
on it's own. If you can't stop Windows update at least pause it for
as long as you can to avoid this problem.
Dave NT9E

2201 - 2220 of 37662