Date   

locked Re: JTAlert Will Not Install

HamApps Support (VK3AMA)
 

On 14/04/2021 3:52 am, Ed Wilson via groups.io wrote:
I have been unable to install the latest version of JTAlert under Windows 10 with the latest update. I have attached screen shots of the errors that I encounter


Ed, K0KC

Have you installed the .NET 5 Desktop Runtime?

de Laurie VK3AMA


locked Re: icon messaging #FT8

HamApps Support (VK3AMA)
 

On 14/04/2021 1:54 am, f8nhf wrote:
in the old version we could see which station had activated the messaging, the callsign was underlined. with version 2.50.0 apparently  
would it be possible to enlarge the star or put another icon more visible (like CQ, DX, 73 alerts)

73 Denis  F8NHF

The "Online for messaging" icon (star) size is tied to the size of the Lotw/Eqsl flags. They share the same size selector.

   
 
If increasing the flag size to increase the online Star icon is undesirable, that is the flags become too large in order to produce a suitable Star size, let me know I will look inyo adding an independent size control.

de Laurie VK3AMA


locked Re: Same problem as K5VP Kevin

HamApps Support (VK3AMA)
 

On 14/04/2021 2:59 am, WA9WYI Neal wrote:
have the same issue as Kevin, K5VP.  I installed the 32 bit version of .NET5 and have the same errors.  I excluded this file in Windows Defender, but there was no change in operaton.

What windows version? Is it 32bit or 64bit?

Check task manager and see if JTAlertV2.Manager.exe is running. Is it constantly stopping & restarting?

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

de Laurie VK3AMA


locked Re: Slow ADIF import

HamApps Support (VK3AMA)
 

On 14/04/2021 1:41 am, Michael Black via groups.io wrote:
Sometimes this can be sped up dramatically by wrapping the entire import in a transaction

That is already happening.

de Laurie VK3AMA


locked Re: Slow ADIF import

HamApps Support (VK3AMA)
 

On 14/04/2021 1:35 am, John Holmes W9ILY wrote:

As you may recall my ADI fie is over 85 MB for over 249,000 records and the load time took over 116,000 ms to complete. Can this be improved? Thanks for all of your latest enhancements!

 

John W9ILY

John,

I neglected to ask in my last message, what sort of import times were you getting with the old JTAlert?

de Laurie VK3AMA


locked Re: Slow ADIF import

HamApps Support (VK3AMA)
 

On 14/04/2021 1:35 am, John Holmes W9ILY wrote:

As you may recall my ADI fie is over 85 MB for over 249,000 records and the load time took over 116,000 ms to complete. Can this be improved? Thanks for all of your latest enhancements!

 

John W9ILY


John,

I am very surprised. This new version should be faster.

Please send me direct your FULL04012021.ADI file and I will test and compare my results with your published results.

de Laurie VK3AMA


locked JTAlert Will Not Install

Ed Wilson
 

I have been unable to install the latest version of JTAlert under Windows 10 with the latest update. I have attached screen shots of the errors that I encounter


Ed, K0KC

k0kc@...
http://k0kc.us/


locked Re: JTAlert 2.50.0 Upgrade help needed

Fred Roberts
 

Bill.....
      As I did, you may have installed the wrong version of .Net. The problems you described are exactly what I experienced. I had to go to remove programs, search by date, and remove .Net, then go back to the JTalert installation website, click the link provided, and then install the correct version of .Net. The x86 version is for 32 bit versions of Windows, the x64 is for 64 bit versions of Windows.
Hope this helps.
Fred
WB4QOC



Sent from my phone.....Fred


On Tue, Apr 13, 2021, 1:09 PM Bill Rogers <k2ter@...> wrote:
I upgraded JTAlert to 2.50.0 from 2.16.10 (I think) for use with WSJT-X.  After the install the Callsign Window and others like "About" don't come up when selected. I am also getting an Unable to communicate with the WSJT-X process: UDP Port 2237 IP Address 127.0.0.1. 

I did not modify my setup after the installation and it appears WSJT-X is still set up to use port 2237.

Is there a remedy or something to try?

Is there a way to go back to the older version safely?

Thanks,
Bill K2TER


locked Re: 2.50.0 with WSJT-X 2.3.1 crashes

Ray, W4BYG <w4byg@...>
 

Are you configured for a "multicast" address from WSJT-X to your clients?
Ray, W4BYG

On 4/13/2021 14:56, John, DK9JC / AK9JC wrote:

After some hours JTAlert 2.50.0 freezes.

WSJT-X 2.3.1 with Log4OM.
WSJT-X decode is fine, but nothing showing on JTAlert Callsign window and after a QSO, it's logged the WSJT-X adif, but QSO does not move into the Log4OM Log.

After a restart of JTAlert it works for some time until it crashed agn.

Win 10 Pro latest build and latest net installed.


-- 
They say a smart person learns from their mistakes.  A
wise person learns from the mistakes of others.

Virus-free. www.avg.com


locked JTAlert 2.50.0 Upgrade help needed

Bill Rogers
 

I upgraded JTAlert to 2.50.0 from 2.16.10 (I think) for use with WSJT-X.  After the install the Callsign Window and others like "About" don't come up when selected. I am also getting an Unable to communicate with the WSJT-X process: UDP Port 2237 IP Address 127.0.0.1. 

I did not modify my setup after the installation and it appears WSJT-X is still set up to use port 2237.

Is there a remedy or something to try?

Is there a way to go back to the older version safely?

Thanks,
Bill K2TER


locked Callsign window in V2.50 opens independently from applications scheduled to open when starting

WU9D <mike@...>
 

To start with I am not pleased at all with the callsign window. I use a laptop for mobile operations and desktop space is at a premium. So I liked it better the way it was before.

That being said, the callsign window opens BEFORE any applications I have specified to open FIRST. The callsign window needs to open AFTER any applications specified, just like the JT Alert main window.


locked Re: 2.50 Like It

mma2
 

Laurie,

 

Just installed v2.50 on my Win10 PC and am amazed at the improvements!  I’ve been using the various versions of JTAlert for 8 years and have loved your app.  This is the very best version yet!

 

Thank you for a wonderful app!!!

 

Blessings,

 

Rick

K6HOM

 

Sent from Mail for Windows 10

 


locked Re: dB vs Grid?

Scott Armstrong
 

Bill,

That function/feature already exists in WSJT-X.
Double right click on the Tx1 button. The Tx1 message box will grey out and all QSO will start with the  Tx2 message.

-Scott AA5AM



On Tue, Apr 13, 2021 at 10:54 AM Bill - AA4M <MrBill@...> wrote:
I just downloaded 2.50.0 and spent about 2 hours working with it.  All I can say is FLAWLESS, WOW!

I did have one request for an enhancement.  Anybody who's ever worked DX knows that they often start a QSO with the dB report rather than a grid.  I like this, especially in marginal conditions.  What I'd like to see in JTAlert is an option to make my response to a CQ or tailgate (by double clicking in the callsign window) begin with my sending dB rather than grid location.  Can such a feature ever be implemented?

Thanks for the great software Laurie!

73, Bill  AA4M


locked Same problem as K5VP Kevin

WA9WYI Neal
 

I have the same issue as Kevin, K5VP.  I installed the 32 bit version of .NET5 and have the same errors.  I excluded this file in Windows Defender, but there was no change in operaton.

 

Sent from Mail for Windows 10

 


locked km vs miles

Fred Roberts
 

Hey all....just downloaded 2.50.0...it's incredible. I've spent the last 30 minutes trying to find the setting to change km to miles when I hover over a station in the decodes window. 
I have 'display distance in miles' checked in WSJT-x 2.2.2.
I must be blind because I can't find the option in JTalert.
Thanks,
Fred
WB4QOC



Sent from my phone.....Fred


On Tue, Apr 13, 2021, 12:27 PM Glenn Jensen <WA6BJQ@...> wrote:

I too like the new version – would be ideal to ‘sort’ by db….

Hey, version 2.6 …

Good stuff – Kudos – 73’s Glenn

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Bill - AA4M
Sent: Tuesday, April 13, 2021 8:55 AM
To: Support@HamApps.groups.io
Subject: [HamApps] dB vs Grid?

 

I just downloaded 2.50.0 and spent about 2 hours working with it.  All I can say is FLAWLESS, WOW!

I did have one request for an enhancement.  Anybody who's ever worked DX knows that they often start a QSO with the dB report rather than a grid.  I like this, especially in marginal conditions.  What I'd like to see in JTAlert is an option to make my response to a CQ or tailgate (by double clicking in the callsign window) begin with my sending dB rather than grid location.  Can such a feature ever be implemented?

Thanks for the great software Laurie!

73, Bill  AA4M


locked Re: dB vs Grid?

Glenn Jensen
 

I too like the new version – would be ideal to ‘sort’ by db….

Hey, version 2.6 …

Good stuff – Kudos – 73’s Glenn

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Bill - AA4M
Sent: Tuesday, April 13, 2021 8:55 AM
To: Support@HamApps.groups.io
Subject: [HamApps] dB vs Grid?

 

I just downloaded 2.50.0 and spent about 2 hours working with it.  All I can say is FLAWLESS, WOW!

I did have one request for an enhancement.  Anybody who's ever worked DX knows that they often start a QSO with the dB report rather than a grid.  I like this, especially in marginal conditions.  What I'd like to see in JTAlert is an option to make my response to a CQ or tailgate (by double clicking in the callsign window) begin with my sending dB rather than grid location.  Can such a feature ever be implemented?

Thanks for the great software Laurie!

73, Bill  AA4M


locked Re: JTAlert for JTDX and WSJT-X - ver. 2.50

EDMUNDO CAMPUSANO
 

Hi John

Do you work with more monitors? Maybe it's on the other monitor.-

Greetings

73 Edmundo CE2EC

El mar, 13 de abr. de 2021 a la(s) 11:23, Jim N6VH (N6VH@...) escribió:

On 4/13/2021 8:13 AM, John Profita wrote:
> I downloaded the 5.0.5-win-64 Framework being it was not on my Win 10 computer. Then I downloaded the JTALERT for both JTDX and WSJT-X. But all I see is the decodes window, see attached. There is no JTALERT that I can get into settings etc. I deleted from program files (x86) the unins000.exe and that went well? I tried again to download both from HamApps  and still does the same thing.
>
> Tnx John
> ND1X

John,

It is possible that the Callsigns window is on top of the main JTAlert
window. Try moving the Callsigns window. If the window won't move, click
on the cog to open the settings. Go to "Window", and make sure "Position
locked" is not checked.

73,

Jim N6VH








--
Edmundo 73, CE2EC
La Serena


locked dB vs Grid?

Bill - AA4M
 

I just downloaded 2.50.0 and spent about 2 hours working with it.  All I can say is FLAWLESS, WOW!

I did have one request for an enhancement.  Anybody who's ever worked DX knows that they often start a QSO with the dB report rather than a grid.  I like this, especially in marginal conditions.  What I'd like to see in JTAlert is an option to make my response to a CQ or tailgate (by double clicking in the callsign window) begin with my sending dB rather than grid location.  Can such a feature ever be implemented?

Thanks for the great software Laurie!

73, Bill  AA4M


locked icon messaging #FT8

f8nhf
 

Hello

the new version is great I had no problem. Great work thank you Laurie and your team of testers
question anyway hi hi hi

in the old version we could see which station had activated the messaging, the callsign was underlined. with version 2.50.0 apparently  
would it be possible to enlarge the star or put another icon more visible (like CQ, DX, 73 alerts)

73 Denis  F8NHF


locked Re: 2.5.0 -- AutoIt Error

David - AK2L
 

You don't turn off virtual screens -- they are a part of Windows 10.  But I did as you asked anyway and moved everything to what I will call "desktop 0".  I then re-enabled HRD6 logging.  JTAlert silently quit within 60 seconds.

Clearly, JTAlert doesn't like being connected to my HRD installation.  This is not a new problem; it existing in earlier versions of JTAlert as well.  But with the earlier versions, it would usually happen only once when I changed a setting.  I would then restart JTAlert and all would be well until I changed another setting.  With v2.50, it happens every time.

I would be interested to hear from other HRD6 users to see if they have seen any problems.

For now, I will look at logging directly from WSJT-X or perhaps changing my logging program altogether.

3841 - 3860 of 37662