Topics

Important Announcement : The next release of JTAlert requires the .NET 5 desktop runtime


Fred Roberts
 

What new features will the next release include? Sorry....this is the first news I've seen on any new releases. And 2.16.17 is very stable, and a pleasure to use.
Fred
WB4QOC

Sent from my phone.....Fred

On Tue, Apr 6, 2021, 9:48 PM Fred Roberts <fred5352@...> wrote:
What new features will the next release include? Sorry....this is the first news I've seen on any new releases. And 2.16.17 is very stable, and a pleasure to use.
Fred
WB4QOC



Sent from my phone.....Fred

On Tue, Apr 6, 2021, 5:46 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
The next release of JTAlert, version 2.50.0, requires the installation of the Microsoft .NET 5 Desktop Runtime.

The JTAlert installer will automatically check if you have the required runtime installed. If the runtime is not found you will be given the option to install the needed file.

The correct 64bit (x64) or 32bit (x86) version needs to be installed matching your Windows OS architecture

If you wish to install the runtime ahead of the new JTAlert release, it can be obtained here...
https://dotnet.microsoft.com/download/dotnet/5.0/runtime/





When
JTAlert 2.50.0 is released the JTAlert download pages will be updated with this new requirement.

JTAlert 2.50.0 will be publicly released in approx 7 days time.

de Laurie VK3AMA


HamApps Support (VK3AMA)
 



On 7/04/2021 11:49 am, Fred Roberts wrote:
What new features will the next release include? Sorry....this is the first news I've seen on any new releases. And 2.16.17 is very stable, and a pleasure to use.
Fred
WB4QOC

The release notes for the new build...
2.50.0

  *** The Microsoft .NET 5 desktop runtime is required to be installed for this
  *** version of JTAlert (and all future versions). The JTAlert installer will
  *** automatically run a runtime check utility which will offer to install the
  *** necessary runtime if it is not detected installed on your PC.

  *** Important note regarding Q65 mode: Q65 support is only partial.
  *** Accurate Q65 B4 checks and Q65 logging are fully supported.
  *** There is no Alerting for Q65 DXCCs, States, Grids, Prefixes, etc.

  *** Includes Callsign database file version 2021-04-05 (2021-Apr-05)

  New Features:

    *** Important: Please review the new "JTAlert 2.50 features" help file for
    *** a complete description (with loads of images) of the new Callsigns,
    *** Activity, Messaging & BandHeat windows and the location of their
    *** respective settings. See under the "Help" window of the main JTAlert
    *** window or the shortcut in the "HamApps JTAlert" Windows start-menu group.

    - Callsigns window: This replaces the old callsigns display grid embedded
       in the main JTAlert window. This window is fully resizable with no limit
       on the number of Callsigns displayed, except for available screen space
       and the number of decodes produced at the end of a period.

    - Messaging window: This replaces the old Text Messages window. It will
       show both sent and received messages and retain them for 7 days.
       Previously sent/received messages can be saved for reuse. The message
       limit is 2048 character (old window was 256 characters).

    - Activity window: This replaces the old Mode Activity window. It is resizable,
       supports the new FST4 and Q65 modes as well as the 560m, 8m, & 5m bands.
       Individual bands and modes can be turned off and not displayed.

    - Band Heat window: This replaces the old Activity Bands display that was
       embedded in the main JTAlert window. It is now an independent window,
       supports the 560m, 8m & 5m bands, and can be set to display vertically
       or horizontally (the default). Individual bands can be turned off and hidden.

  Changes:

    - Decodes window: Frequency column can be set to either KHz or MHz.

    - QSL flags: The Lotw and Eqsl flag positions on the Callsigns display
       and Decodes window are no longer changeable. They are fixed in location.
        Lotw -> bottom left of the Callsign.
        Eqsl -> bottom right of the Callsign.

    - Hotkeys: No longer user-changeable, they are now hard-coded.
        F1 -> Help window
        F2 -> Settings window
        F3 -> Callsigns window
        F4 -> Decodes window
        F5 -> Text Messages widow
        F6 -> Call History window
        F7 -> Alert Status window
        F8 -> Macros window
        F9 -> not used
        F10 -> not used
        F11 -> Activity window
        F12 -> BandHeat window

        Alt + H -> Open browser to HamSpots.net
        Alt + Q -> Open browser to QRZ.com

    - Callsign Display Grid: Has been removed and is now a separate,
       resizable window, simply called the "Callsigns" window.

    - Text Messages Window: Now called "Messaging" Window, is only launchable
       from the JTAlert first instance (#1).

    - WSJT-X: B4 & Ignored callsigns are now highlighted in WSJT-X when
       they are hidden in JTAlert due to filtering.

    - Menus: Several menus associated with the new Windows introduced with
       this release (Activity, Messaging & Callsigns) have been removed from
       the main JTAlert window. All necessary options/settings for these new
       windows can be set from the Options popup for each of these windows.

  Fixes:

    - Q65 mode: Callsigns not being displayed in the Callsign display and
       decodes not being displayed in the Decodes window.

    - DXKeeper: non-AG eQSL member QSLs marked as "received" incorrectly considered
       as confirmed when running the Alert database rebuild. That is QSOs marked as
       confirmed from non-AG callsigns will no longer be considered during the rebuild.

    - HRDLogbook V6+: Lat & Lon data missing from logging instruction sent to
       Log via its TCP interface

    - Text Messages: Online status randomly incorrectly shows offline when the
       Callsign is online and has been sending messages.

    - JTAlert debug data: Some session files not being truncated as part of
       the automated maintenance routines.

    - JTAlert Installer: The desktop shortcuts checkbox settings when the installer was
       last run are now remembered and restored.


de Laurie VK3AMA


Joe - W9RF
 

Fred,


Don't mean to hijack your post but I have not received an email about any changes.



I certainly hope these new changes do not require Windows 10?

AND why did I not receive an email about the changes?

Laurie VK3AMA  was the original email posted here on HamApps.groups.io?


W9RF - Joe







On Tuesday, April 6, 2021, 8:50:18 PM CDT, Fred Roberts <fred5352@...> wrote:


What new features will the next release include? Sorry....this is the first news I've seen on any new releases. And 2.16.17 is very stable, and a pleasure to use.
Fred
WB4QOC

Sent from my phone.....Fred

On Tue, Apr 6, 2021, 9:48 PM Fred Roberts <fred5352@...> wrote:
What new features will the next release include? Sorry....this is the first news I've seen on any new releases. And 2.16.17 is very stable, and a pleasure to use.
Fred
WB4QOC



Sent from my phone.....Fred

On Tue, Apr 6, 2021, 5:46 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
The next release of JTAlert, version 2.50.0, requires the installation of the Microsoft .NET 5 Desktop Runtime.

The JTAlert installer will automatically check if you have the required runtime installed. If the runtime is not found you will be given the option to install the needed file.

The correct 64bit (x64) or 32bit (x86) version needs to be installed matching your Windows OS architecture

If you wish to install the runtime ahead of the new JTAlert release, it can be obtained here...
https://dotnet.microsoft.com/download/dotnet/5.0/runtime/





When
JTAlert 2.50.0 is released the JTAlert download pages will be updated with this new requirement.

JTAlert 2.50.0 will be publicly released in approx 7 days time.

de Laurie VK3AMA


HamApps Support (VK3AMA)
 

On 7/04/2021 1:43 pm, Joe - W9RF via groups.io wrote:
I certainly hope these new changes do not require Windows 10?

AND why did I not receive an email about the changes?

Laurie VK3AMA  was the original email posted here on HamApps.groups.io?


W9RF - Joe

I never email people about future changes to JTAlert, apart from the Test team.

Sometimes I will drop hints, in this group, about upcoming new features, changes or fixes.

I don't normally publish the release notes for a new release ahead of time. Today's announcement of the NET5 requirement and publishing of the release notes was done due to the large amount of changes and to give people a chance to install the NET5 runtime ahead of time.

If you're still using Win 7 (why?) and don't have Extended Security Updates installed then you're likely out of luck and will have to stay with JTAlert 2.16.17. Info on getting Extended Security Updates for Win7 can be found here...

https://docs.microsoft.com/troubleshoot/windows-client/windows-7-eos-faq/windows-7-extended-security-updates-faq.

The list of .NET 5 supported Operating Systems can be found here...
https://github.com/dotnet/core/blob/main/release-notes/5.0/5.0-supported-os.md

The NET 5 requirement for JTAlert 2.50.0 and all future versions is a done deal, there is no going back. There is a lot of new code that is dependent on NET 5 functionality.


de Laurie VK3AMA



John Petrocelli
 

Hello,

   If I understand, I shall need to install the "ESU" before I install the "Net 5" on my windows machine.

   I still run Windows 7 and have not yet planned to update to Windows 10

   Additional input and comments are welcome

Thanks in advance
John
John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 2021-04-07 05:26, HamApps Support (VK3AMA) wrote:
On 7/04/2021 1:43 pm, Joe - W9RF via groups.io wrote:
I certainly hope these new changes do not require Windows 10?

AND why did I not receive an email about the changes?

Laurie VK3AMA  was the original email posted here on HamApps.groups.io?


W9RF - Joe

I never email people about future changes to JTAlert, apart from the Test team.

Sometimes I will drop hints, in this group, about upcoming new features, changes or fixes.

I don't normally publish the release notes for a new release ahead of time. Today's announcement of the NET5 requirement and publishing of the release notes was done due to the large amount of changes and to give people a chance to install the NET5 runtime ahead of time.

If you're still using Win 7 (why?) and don't have Extended Security Updates installed then you're likely out of luck and will have to stay with JTAlert 2.16.17. Info on getting Extended Security Updates for Win7 can be found here...

https://docs.microsoft.com/troubleshoot/windows-client/windows-7-eos-faq/windows-7-extended-security-updates-faq.

The list of .NET 5 supported Operating Systems can be found here...
https://github.com/dotnet/core/blob/main/release-notes/5.0/5.0-supported-os.md

The NET 5 requirement for JTAlert 2.50.0 and all future versions is a done deal, there is no going back. There is a lot of new code that is dependent on NET 5 functionality.


de Laurie VK3AMA




Virus-free. www.avast.com


HamApps Support (VK3AMA)
 

On 7/04/2021 5:14 pm, John Petrocelli via groups.io wrote:
   If I understand, I shall need to install the "ESU" before I install the "Net 5" on my windows machine.

   I still run Windows 7 and have not yet planned to update to Windows 10

   Additional input and comments are welcome

Thanks in advance
John
John R. Petrocelli - WA2HIP

That's how I read it.
If you're on Win7 SP1 you need the ESU according to this...
https://github.com/dotnet/core/blob/main/release-notes/5.0/5.0-supported-os.md

de Laurie VK3AMA


John Petrocelli
 

Thanks for the reply.

I shall
  1) look into setting up ESU on the Win 7 machine

  2) consider doing an upgrade to Win 10 in the near future

Initially I saw many people had issues with Win 10 changing things around during updates. 
I am running Win 7 on a Dell 990 which has a quad-core CPU and an SSD

To accomplish #2 above, I an thinking of cloning the Win 7 system drive (SSD) to another SSD and then trying the upgrade on that clone.

BTW, I use Macrium Reflect Free (home use) to accomplish creating the image and then restoring the image to a "new" SSD

Regards,
John
John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 2021-04-07 07:30, HamApps Support (VK3AMA) wrote:
On 7/04/2021 5:14 pm, John Petrocelli via groups.io wrote:
   If I understand, I shall need to install the "ESU" before I install the "Net 5" on my windows machine.

   I still run Windows 7 and have not yet planned to update to Windows 10

   Additional input and comments are welcome

Thanks in advance
John
John R. Petrocelli - WA2HIP

That's how I read it.
If you're on Win7 SP1 you need the ESU according to this...
https://github.com/dotnet/core/blob/main/release-notes/5.0/5.0-supported-os.md

de Laurie VK3AMA



Virus-free. www.avast.com


Willi Passmann
 

...according to the link, "Windows 7 SP1 is supported with Extended Security Updates installed".
These Updates are chargeable. After having read two looong pages dealing with this matter, I still don't know what the fee would be or how the procedure works.
I will try to update JTAlert, but in case of doubt I'll keep my (running) W7Pro system...

vy 73,
Willi, DJ6JZ


Am 07.04.2021 um 09:30 schrieb HamApps Support (VK3AMA):

That's how I read it.
If you're on Win7 SP1 you need the ESU according to this...
https://github.com/dotnet/core/blob/main/release-notes/5.0/5.0-supported-os.md



Dave Corio
 

On 4/7/2021 4:26 AM, John Petrocelli via groups.io wrote:
Thanks for the reply.

I shall
� 1) look into setting up ESU on the Win 7 machine

� 2) consider doing an upgrade to Win 10 in the near future

Initially I saw many people had issues with Win 10 changing things around during updates.�
I am running Win 7 on a Dell 990 which has a quad-core CPU and an SSD


John - Also running a Dell 990 (i5 2400) quad-core w/16G RAM. Runs Win 10 with no problem. Even supports two monitors without a separate video card. Been running JTAlert and WSJT-X on it for months with no trouble.

As a caveat, though, keep these two facts in mind:

1. Win 10 is near end-of-support (May 2021) for versions 1909 and lower.

2. My 990 would not accept the upgrade to take it above vers 1909, therefore leaving it about to stop receiving updates.

I've been running Win 10 on several PCs since they released the free upgrade years ago. Other than the problem with the version upgrade I've not had a single crash or BSD happen. The "End-of Support" issue means the OS will no longer receive critical security or Windows apps updates. The OS will still work and Defender will still receive antivirus data.

In general, Win 10 has been MUCH more stable than Win 7 or 8. The final decision, of course, is yours.

73

Dave - K1DJE



W6SA
 

The Microsoft link for a free upgrade to Windows 10 was still working within the past two years.  It may still be available.  Do a search for Free Windows 10 Upgrade and take a look to see if it is still active.  I was able to upgrade my wife's Windows 7 machine with no problem.  Be sure to check a couple of posts as I saw some possible issues with existing software.

73

Walt - W6SA


Jim Cooper
 

On 7 Apr 2021 at 8:26, John Petrocelli via groups.io wrote:

> Initially I saw many people had issues with Win 10 changing things
> around during updates.

fwiw, a couple of months ago I was able to still
use the free upgrade from 7 to 10 and it went
amazingly smoothly.  And has been running on 10
just fine ever since.

I DID run a full backup to a spare hard drive
'just in case' but did not need it.  (Believe me,
I went into the project with extreme apprehension!)

I used the instructions at


Hope that helps.

Jim  W2JC

  


Dave Cole
 

I have been running W10 all along, and just went to 20H2, and am having ZERO issues, with jtalert, and wsjt-x, no issues of any kind.

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

On 4/7/21 8:53 AM, Jim Cooper wrote:
On 7 Apr 2021 at 8:26, John Petrocelli via groups.io wrote:

Initially I saw many people had issues with Win 10 changing things
around during updates.
fwiw, a couple of months ago I was able to still
use the free upgrade from 7 to 10 and it went
amazingly smoothly.  And has been running on 10
just fine ever since.
I DID run a full backup to a spare hard drive
'just in case' but did not need it.  (Believe me,
I went into the project with extreme apprehension!)
I used the instructions at
_https://www.howtogeek.com/509087/how-to-upgrade-from-windows-7-to-windows-10-for-free/_
Hope that helps.
Jim  W2JC


John Petrocelli
 

Hello Dave,

  Thanks for your input and observations.

  Since I recently upgraded my 4 desktops to Optiplex 990 MT I7, I still have an Optiplex 755. 1 is running Windows 10  The others run Win 7 and on of those 3 is my "radio" computer.

  I may try installing Windows 10 on the older Optiplex and then seeing what problems surface with WSJT-X and JTAlert.

Regards,
John
John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 2021-04-07 11:29, Dave Corio via groups.io wrote:
On 4/7/2021 4:26 AM, John Petrocelli via groups.io wrote:
Thanks for the reply.

I shall
� 1) look into setting up ESU on the Win 7 machine

� 2) consider doing an upgrade to Win 10 in the near future

Initially I saw many people had issues with Win 10 changing things around during updates.�
I am running Win 7 on a Dell 990 which has a quad-core CPU and an SSD


John - Also running a Dell 990 (i5 2400) quad-core w/16G RAM. Runs Win 10 with no problem. Even supports two monitors without a separate video card. Been running JTAlert and WSJT-X on it for months with no trouble.

As a caveat, though, keep these two facts in mind:

1. Win 10 is near end-of-support (May 2021) for versions 1909 and lower.

2. My 990 would not accept the upgrade to take it above vers 1909, therefore leaving it about to stop receiving updates.

I've been running Win 10 on several PCs since they released the free upgrade years ago. Other than the problem with the version upgrade I've not had a single crash or BSD happen. The "End-of Support" issue means the OS will no longer receive critical security or Windows apps updates. The OS will still work and Defender will still receive antivirus data.

In general, Win 10 has been MUCH more stable than Win 7 or 8. The final decision, of course, is yours.

73

Dave - K1DJE




Virus-free. www.avast.com