Date   

locked No problem!

W1UU
 

No problem for me to install 2.50.0

Like anything, one has to get use to software changes to match operating styles.

I just need to pick and choose some of the optional settings. Part of the fun of JT Alert is choosing!

Peter W1UU



--
Peter Butler
W1UU


locked Re: Ver 2.50.0 issues

Fred Roberts
 

Laurie.....
       Good news! The answer to my question....should I have chosen the x64 version is YES!!!!....no problem uninstalling the x86 version, I just sorted by date installed, followed the link you provided in your install instructions, choose the CORRECT version, and 2.50.0 is up and running!
Tnx es 73,
Fred
WB4QOC



Sent from my phone.....Fred


On Tue, Apr 13, 2021, 8:26 AM Fred Roberts via groups.io <fred5352=gmail.com@groups.io> wrote:
Good morning Laurie.....
      A bit of help needed. Installed 2.50.0 and after a minute or two wait I get the following pop up window:
     I am running Windows 10 Home. I did get the warning that . Net 5 wasn't installed, and I installed it (I choose the x86 version - should I have used x64?)  
I've also included a shot of the WSJT-x settings.
     Thanks for your help, and a great program!
73,
Fred
WB4QOC



On Tue, Apr 13, 2021, 7:59 AM Bill Barrett <billbarrett174@...> wrote:
Hello Laurie-

Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA

Attachments:


locked Re: 2.50.0 Display priority callsigns/callers

Andy k3wyc
 

On Tue, Apr 13, 2021 at 05:35 AM, Andy k3wyc wrote:
Is there any way to inhibit the display of callers?
I found the "disable" option in the display position list.

73,
Andy, k3wyc


locked 2.50.0 Display priority callsigns/callers

Andy k3wyc
 

First of all thanks for this feature rich update to JtAlert.  As I became familiar with it I found several things I would like to change and, sure enough, there was an option that allowed me to configure the way I wanted.

So far I have not found no way to change the relative priority for displaying callsigns vs callers.   I have set a fixed size for the callers and adjusted the window size and position but not locked size or position.  My chosen settings allow 4 rows of 8 callsigns.   When someone calls me the auto-open callers display blocks the bottom line of my callsign display.  Since I usually consider these callers to be low priority I'd prefer they did not block the callsigns.

Is there any way to make callsigns have priority over callers  i.e. only display callers if there is space available?
is there a way to have the window size automatically increase to add callers?
Is there any way to inhibit the display of callers?

Thanks and 73,
Andy, k3wyc



locked Re: independent windows #JTDX

sv1hep@...
 

I fount it !! False alarm.


locked Re: Ver 2.50.0 issues

Fred Roberts
 
Edited

Good morning Laurie.....
      A bit of help needed. Installed 2.50.0 and after a minute or two wait I get the following pop up window:
     I am running Windows 10 Home. I did get the warning that . Net 5 wasn't installed, and I installed it (I choose the x86 version - should I have used x64?)  
I've also included a shot of the WSJT-x settings.
     Thanks for your help, and a great program!
73,
Fred
WB4QOC
 
 

On Tue, Apr 13, 2021, 7:59 AM Bill Barrett <billbarrett174@...> wrote:
Hello Laurie-
 
Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:
 
1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.
 
2.) Instance #1 does not always display the Band and Mode.
 
3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.
 
The new call window is very flexible.
 
Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA

 

 

 

 


locked independent windows #JTDX

sv1hep@...
 
Edited

New version is fantastic. Please can you in next updates to make the 2 windows minimized and maximized not to be interdependently. 
Thank you for hard work


locked Re: Ver 2.50.0 issues

Bill Barrett
 

I think it's the "MSK144" mode.


On Tue, Apr 13, 2021 at 7:59 AM Bill Barrett via groups.io <billbarrett174=gmail.com@groups.io> wrote:
Hello Laurie-

Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA


locked Re: Ver 2.50.0 issues

Bill Barrett
 

Hello Laurie-

Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA


locked Re: 2.50 Like It

Mike G0LQI
 

Very good Laurie and, as you have said before, there is a treasury of adjustments behind the little cog wheel. Perhaps you ought to label it, "Open Sesame".
vy 73 Mike G0LQI


locked Re: 2.50 Like It

G. E. Janssens - K5WW
 

Many fantastic, and welcomed improvements and new features!

Including the very last one on the list, which has been a pain in my lower back for years. I know, minor gripe (which I never reported - mea culpa) but...

Thanks Laurie!

73,

Erik - K5WW


locked New JTAlert

Jamie GOLLY
 

Laurie, the new JTAlert is fantastic!

I really like how the spots include if they are calling DX or looking for a state. The customization of the program is so nice in so many ways.

I am surprised at how fast the new program is.

Thank you for all that you do for the amateur radio community.




Jamie
K6NGN


locked Re: 2.50 Like It

Jon KM8V
 

I like it too. Very nice, Laurie!

Personally, I'd love to ditch the "main" window for the callsigns window, if there was a way to get to the menu from there.

Also it'd be cool if in addition to DX Call in the status bar, there was an option to display the other information that gets looked up in the main window, like Name, QTH, Grid, Country, State, CQZ, ITUZ, Continent and a QRZ button in the status bar.

Nice work! 73


locked Re: 2.5.0 -- AutoIt Error

Michael Black
 

I have GeForce GTX 1660 Super which is close enough that the video card would seem unlikely to be the problem.

Fast enough CPU and plenty of RAM.

The only thing that sounds different is the virtual screens.  Can you turn that off and see if it makes a difference>

Mike W9MDB




On Monday, April 12, 2021, 05:27:02 PM CDT, David - AK2L <ak2l.radio@...> wrote:


Intel i7-9700 @ 3.0 GHz
64 GB RAM
Primary disk is NVME, secondary is HDD.  Neither is close to full.
NVIDIA GeForce GTX 1660 Ti
27" monitor - 2560x1440
Windows 10 Pro - 20H2 - OS Build 19042.906 - Feature Experience Pack 120.2212.551.0
I use several virtual screens as supported by Windows 10


locked Re: Windows Defender false positive : Release 2.50.0

Ron / W4MMP
 

Microsoft has cleared the file.


jtalert.2.50.0.install.exe
Submission ID: d22fef71-d261-4d07-b46b-f11002269118
Status: Completed
Submitted by: w4mmp@...
Submitted: Apr 12, 2021 6:35:30 PM
User Opinion: Incorrect detection
Analyst comments:


                We have removed the detection.  Please follow the steps below to clear cached detection and obtain the latest malware definitions.

The next release of the definition file may have the correction.

73,
Ron / W4MMP
On 4/12/2021 22:18, Doug Rosser wrote:

And you may need to exclude the directory that contains the .exe from Defender’s periodic scans as well.

Doug VK2EY  


locked Re: Ver 2.50.0 issues

HamApps Support (VK3AMA)
 

On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA


locked Re: Windows Defender false positive : Release 2.50.0

 

And you may need to exclude the directory that contains the .exe from Defender’s periodic scans as well.

Doug VK2EY  


locked Re: JTAlert and Virus - Read on

WB5JJJ - George
 

Won't quarantine or remove as requested.  I think it's probably a bug in Defender.  
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: JTAlert and Virus - Read on

Joe WB9SBD
 

Where is the defender quarantine folder located anyway?

Joe WB9SBD

On 4/12/2021 8:26 PM, WB5JJJ - George wrote:
Yes, but it still shows in the Download folder.  There is no JTA files there.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: 2.50 Like It

HamApps Support (VK3AMA)
 

On 13/04/2021 11:32 am, James F. Boehner, MD via groups.io wrote:

My last computer on Windows 7 is my FT8 computer.  Fortunately, the 64-bit 5.0.5 framework loaded without a hitch.  I do not have the paid updates (I didn’t know they existed).  My Windows version is 6.1.7601 Service Pack 1.

’73 de JIM N2ZZ


Good to hear. I suspect however, that eventually, the .NET 5 runtime will have issues with Win7 SP1 per the Microsoft announcement. Likely the intention is that Win7 will not be supported without the ESU, but the underlying code has not reached that point or they simply forgot to enable a switch. Only time will tell.

de Laurie VK3AMA

3521 - 3540 of 37312