Date   

locked Re: 2nd instance Callsign window not following JTAlert main window on minimize - Defect Confirmed.

Gary Yarbrough, KE5TD
 



On Tuesday, April 13, 2021, 07:31:12 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 14/04/2021 5:45 am, Gary Yarbrough via groups.io wrote:
>From the settings window in the Callsign window I have ticked the box for the Callsign window to follow the JTAlert main window and it works on the 1st instance.  On the 2nd instance I also ticked the box  but the Callsign window does not minimize when I minimize the JTAlert main window. Anyone else having this issue ?

Gary / KE5TD

Gary,

Thanks for the report. I can confirm this is a defect.

I'll correct it for the next release.

de Laurie VK3AMA


Laurie,

Also the Callsign window on 2nd instance is auto closing after about 5 minutes..  The 1st instance is running normal with no issues.

Thanks for the new version I really like it !

73, Gary
KE5TD


locked V 2.50.x Observations

John Petrocelli
 

Hello,

  I installed 2.50.x on a spare laptop running Windows 10 and I offer some observations.
  All are intended to be constructive and I welcome any input & critique

  I do like the new release although the new window structure will require a bit of adjustment in my thinking - not too much though.

  The callsign window seems to have some limitation on its text size.
  For someone who is visually challenged, this could be an issue.

  The Main Window used to be attached to the callsign window along with the Menu.
  It would be nice if the Menu would be also available on the callsign window or an option to put (attach) the Main Window on the Callsign Window.

  As others have observed, (I use an ADIF file) the ADIF reading seems very much longer.
  My ADIF file has about 182,000 records Version 2.17.x took about 15 seconds to read it.
  Version 2.50.x takes about 95 seconds.
  As someone mentioned, this may be due to the .NET but I am not sure.
  The above numbers were on the same machine under Windows 10

  I did successfully make 1 QSO with the new version before going back to version 2.17.x/
  Note that I an running 2.17.x on a Windows 7 machine but I may try to get the .NET 5.0 working on that machine.
  If not, I shall clone my Win 10 machine so I can work with the new version without adversely impacting my primary desktop.

  Thank you Laurie for all your great efforts !!!

John
-- 


John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com

Virus-free. www.avast.com


locked Callsigns not always decoding into Callsigns window.

Walt Flesher, W6SA
 

I upgrade to the newest version yesterday.  I already had Net 5.0 installed.

After the upgrade it took a while before I had any decoding.  No idea what I may have done to start it.

There is no persistence to my callsigns window.  I am presented with a blank window.  After clicking on different menus brought up by the settings icon in the lower right of the callsign screen it will suddenly start to decode for a short time and then present me with a blank screen again.  It seems to work whenever it wants to.

This happens over and over.  I cannot consistently make a contact without the screen going blank while I am transmitting and does not always come back with any calls.  It has been like this since I upgraded.  What am I missing here?  

Great looking program and features if I could only decode consistently it would be a pleasure.

73
Walt, W6SA


locked Re: api-ms-win-crt-runtime-l1-1-0.dll missing ->> try reinstalling the program to fix

HamApps Support (VK3AMA)
 

On 14/04/2021 11:15 am, Jim wrote:
after installing JTAlert 2.50.0 on my windows 7 computer I get this message.  What did I do incorrectly and how do I fix it?   

Yes I know reinstall it, but I have done that multiple times and it didnt install the file needed.  What do I do now?

Jim K3ybn

Reinstall the NET 5 Desktop Runtime. That particular file is not bundled with the JTAlert installer, it is part of the Runtime.

If reinstalling the Runtime doesn't work, it could mean that your WIn7 PC wont work with the new version.

As it is now, WIn7 SP1 is not officially supported without a paid ESU being installed. That may or may not be your problem. Several Win7 SP1 users have reported success without having the ESU installed. I believe they were all Win7 Pro, are you perhaps running Win7 Home or never updated to SP1?

de Laurie VK3AMA


locked Re: Can't find call sign window

HamApps Support (VK3AMA)
 

On 14/04/2021 11:11 am, HamApps Support (VK3AMA) via groups.io wrote:
For your callsign the are located at %localappdata\HamApps\KF0CUD\config\
Sorry missing an "%" The correct location is %localappdata%\HamApps\KF0CUD\config\

de Laurie VK3AMA


locked Re: Ver 2.50.0 issues

HamApps Support (VK3AMA)
 

On 14/04/2021 10:41 am, Bill Barrett wrote:
Moved over to Multicast and all is well now.

Couple of "Nice to Haves"

1. Filter USA calls only. I run HF - 6M on my 6700 so want to see: Caribbean, Mexico, Canada which are filtered out by the N.A. filter. 
   Filtering out USA calls in the Callsigns window would reduce the number of entries on busy bands like 40 & 20M. 
   Finally, it would be nice if each Callsigns window could have it's own filters.

2. Sort Callsigns window by 1, CQ  2. 73 3. DX 4. all others.

Thanks, could not operate FT8 without this app.

Bill W2PKY

Good stuff!

1. USA only filtering is on the todo list along with every other Country. It's unlikely to happen in the near future however. The same applies for Filtering at the Callsigns window level. Everything displayed in the Callsigns window is still coming from the old JTAlert code and there are issues with trying to implement this currently.

2. Sorting, very unlikely to happen. Sorting by its nature consumes extra CPU resources, depending on the algorithm used adding to a slowdown of the Callsigns display. The biggest problem however is that to sort a list of decodes, by any criteria (frequency, db, message type, country, etc) requires that all the decodes are available prior to sorting which means hanging onto the decodes and waiting till they have all been received and then applying the sort.  That would add seconds to the time to display the Callsigns. With WSJT-X now supporting early decoding and up to 3 passes, holding off the Callsigns display until all have been received is a show-stopper, IMO.

There are alternate solutions to sorting in batches but they will result in a continuous shuffling of the Callsigns in the display as each is received from WSJT-X, with the shuffling ending only after all decodes have been received.


de Laurie VK3AMA




locked api-ms-win-crt-runtime-l1-1-0.dll missing ->> try reinstalling the program to fix

Jim
 
Edited

after installing JTAlert 2.50.0 on my windows 7 computer I get this message.  What did I do incorrectly and how do I fix it?   
This is a new installation of JTAlert of course and the new .net seems to work or at least I didnt get any errors from it. 
Yes I know reinstall it, but I have done that multiple times and it didnt install the file needed.  What do I do now?

Jim K3ybn


locked Re: Do Callsign Alerts work with /MM callsigns?

HamApps Support (VK3AMA)
 

On 14/04/2021 10:49 am, Jim Reisert AD1C wrote:
I tried to add YU2AX/MM (maritime mobile) as a wanted callsign, but
I'm not seeing the correct alert highlighting.  Do /MM callsigns break
the algorithm?

They shouldn't. But I will have to run some tests to confirm, it has been many moons since I went near that code.

Easiest solution is to enter the Wanted Callsign as "YU2AX%".

de Laurie VK3AMA




locked Re: Can't find call sign window

HamApps Support (VK3AMA)
 

On 14/04/2021 6:07 am, Brad@... wrote:
I did the install for the new JTAlert and all was good. I turned off everything and when I restarted I can no longer see the call sign window. I've checked behind all the other open window. No luck. I also now notice a red icon with JT Manager running as well. Any thoughts on where to start with this?
Brad, KF0CUD

Since there are minimal settings involved, try shutting down JTAlert and then deleting the Callsigns config file.
For your callsign the are located at %localappdata\HamApps\
KF0CUD\config\
Delete any files starting with "Callsigns_", there will always be 2 files, but more if you're running multiple instances.

de Laurie VK3AMA


locked Re: JTAlert Will Not Install

HamApps Support (VK3AMA)
 

On 14/04/2021 5:08 am, Ed Wilson via groups.io wrote:
I seem to recall that there is a way of checking to see that it was installed properly, but I must have deleted the post where that information was given. Would you kindly let me know how to verify that the .NET update was actually installed?

See https://hamapps.groups.io/g/Support/message/33835

de Laurie VK3AMA


locked Re: Thank You!!

Fred Roberts
 

What Charlie said!!!!
Fred
WB4QOC



Sent from my phone.....Fred


On Tue, Apr 13, 2021, 6:10 PM Charlie - K5EY <aggie61@...> wrote:
Thank you for making this awesome upgrade available to the ham community. JTAlert ver. 2.50.0 is truly amazing. No problems with installation or setup. Very intuitive and all the controls are right where one would expect them to be. All of the enhancements are super, but three stand out for me:
  1. Ability to zoom individual windows with a simple ctrl+mouse wheel.
  2. Badges and other information on the callsigns.
  3. Improved messaging.
Thanks again. The ham world is in your debt.
--
Charlie -- K5EY


locked Re: the .NET 5 Desktop Runtime 64bit (x64)

HamApps Support (VK3AMA)
 

On 14/04/2021 10:20 am, Russ - KA1ERL wrote:

Running windows 10 64bit version.

Attached is the log generated by the error.


Sorry, not much I can do about this. You will need to engage with Microsoft support to sort it out.

I note "Failed to extract all files" messages in the log. Perhaps your file is corrupt or your Protection software is interfering.

Depending on your ISP, downloading the NET 5 installer again may result in them delivering the same corrupt file, assuming it is corrupt. Try installing an earlier version.

X64 direct download links...
5.0.4 https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-desktop-5.0.4-windows-x64-installer
5.0.3 https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-desktop-5.0.3-windows-x64-installer
5.0.2 https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-desktop-5.0.2-windows-x64-installer

de Laurie VK3AMA


locked Re: UDP ERROR

n1uz@...
 

OK, I DID   WSJT-X = 2237
                 JT ALERT = 2334
Still not working
Sorry im a pain the a##


locked Re: the .NET 5 Desktop Runtime 64bit (x64)

Russ - KA1ERL
 

 

This is a screen shot of the 0x80070570 error

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Tuesday, April 13, 2021 19:59
To: Support@HamApps.groups.io
Subject: Re: [HamApps] the .NET 5 Desktop Runtime 64bit (x64)

 

On 14/04/2021 5:15 am, Russ - KA1ERL wrote:

When I try to install the above, I receive and error 0x80070570.
How do I fix this error.  I scanned my drive and no file errors.
Thank you


Please post an image of the error message.

Are you sure you're running a 64bit version of Windows?

What Windows version are running, Win7, 8.1 or 10?

de Laurie VK3AMA


locked My Errors with JTAlert 2.50 32 bit Windows 10 PC

William Wagaman
 

Hello Bill here N3GTY has anyone had this error with the new version of JTAlert:
I have 2 computers the 64bit PC windows 10 no issues ... but the errors below are on my 32bit machine. 32 Bit system because it is an older dual core with 4gb ram also windows 10 Any suggestion would be appreciated. Thanks in advance Bill

Unable to execute file:
C:\Program Files\HamApps\JTAlert\pulginsX\FrameworkChecke.exe
 
CreateProcess Failed; code 216
This version of %1 is not compatible with the version of 
Windows your're running. Check your computer's system
information and then contact the software publisher.

I get this when it is checking the Dot Net Version
I get this error when attempting to run JTAlert

 


locked Do Callsign Alerts work with /MM callsigns?

Jim Reisert AD1C
 

I tried to add YU2AX/MM (maritime mobile) as a wanted callsign, but
I'm not seeing the correct alert highlighting. Do /MM callsigns break
the algorithm?

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://www.ad1c.us


locked Re: Ver 2.50.0 issues

Bill Barrett
 

Hello Laurie-

Moved over to Multicast and all is well now.

Couple of "Nice to Haves"

1. Filter USA calls only. I run HF - 6M on my 6700 so want to see: Caribbean, Mexico, Canada which are filtered out by the N.A. filter. 
   Filtering out USA calls in the Callsigns window would reduce the number of entries on busy bands like 40 & 20M. 
   Finally, it would be nice if each Callsigns window could have it's own filters.

2. Sort Callsigns window by 1, CQ  2. 73 3. DX 4. all others.

Thanks, could not operate FT8 without this app.

Bill W2PKY

On Tue, Apr 13, 2021 at 8:25 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 9:59 pm, Bill Barrett 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




Likely its the port 2333 you're trying to use. That should not be a problem, but I have seen many users set to use 2333 and things stop working because they also have the WSJT-X secondary server enabled and it is set to 2333.
   

Make sure it is turned off. Also check that you don't have JTAlert set to rebroadcast UDP messages on the same port (under the "Applications -> WSJT-X /JTDX" section of the main JTAlert Settings window).

If you still have problems, use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA



locked Re: UDP ERROR

HamApps Support (VK3AMA)
 

On 14/04/2021 10:37 am, n1uz@... wrote:
I have my setup the exact as my friend n1mgo, only difference is that his is working and i am not
I keep getting the WSJT-X   UDP error message  127.0.0.1    2334 UDP PORT

Change the port to 2237 in WSJT-X.

de Laurie VK3AMA


locked UDP ERROR

n1uz@...
 

I have my setup the exact as my friend n1mgo, only difference is that his is working and i am not
I keep getting the WSJT-X   UDP error message  127.0.0.1    2334 UDP PORT


locked UDP ERROR

n1uz@...
 

i have all my setting setup exact same as my friend N1MGO 

3401 - 3420 of 37288