Date   

locked Re: Mini-JTAlert Tool Bar

Thomas Webb
 

Yes, wasn't sure what its' proper name was.

Tom, WA9AFM


locked Re: 2.50.0 with WSJT-X 2.3.1 crashes

John, DK9JC / AK9JC
 

On Thu, Apr 15, 2021 at 10:30 PM, HamApps Support (VK3AMA) wrote:
See the Help File (not the 2.50.0 features help file), "WSJT-X UDP Setup" topic for correct setup.

Roger. Tu for looking.


locked Re: DxLab menus #DXLAB

thierry ben
 

Thank you Laurie 
73
De Thierry F5SIB 


locked Re: 2.50.0 with WSJT-X 2.3.1 crashes

HamApps Support (VK3AMA)
 

On 15/04/2021 7:11 am, John, DK9JC / AK9JC wrote:
Is there anything I can do or can I provide any other data/info?

Try setting up WSJT-X to use multicast UDP.

See the Help File (not the 2.50.0 features help file), "WSJT-X UDP Setup" topic for correct setup.

de Laurie VK3AMA


locked Re: JTAlert 2.50.0 Upgrade help needed

N2TK, Tony
 

I installed .Net, 64 bit. At the end of the installation, "download and install" am I supposed to do anything else in NET?
I have had no luck with "dotnet" at a command prompt. I get an alarm that "Windows cannot find dotnet".
Any ideas?
Tnx
N2TK, Tony. 


-----Original Message-----
From: Fred Roberts <fred5352@...>
To: Support@hamapps.groups.io
Sent: Tue, Apr 13, 2021 1:39 pm
Subject: Re: [HamApps] JTAlert 2.50.0 Upgrade help needed

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: Q65 decodes not showing

HamApps Support (VK3AMA)
 

On 16/04/2021 5:43 am, Seb wrote:
By the way, in the past you had mentioned you were re-writing JTAlert, is that still the plan, since there are so many great additions in the latest version.

Yes the re-write is happening, JTAlertV3.
The new features & functionality of 2.50.0 are taken directly from the JTAlertV3 code-base.

V3 was taking too long to release, so I abandoned hopes of a fully-featured V3 release in the near future and instead have focused on bringing the new V3 code into V2 piecemeal over several releases. JTAlert 2.50.0 is a hybrid of the old and the unreleased new code. That will continue until eventually the old V2 code is gone and we only have V3 code, at that point I will rebrand to JTAlertV3.

de Laurie VK3AMA


locked Re: Access newest Help file prior to installation?

HamApps Support (VK3AMA)
 

On 16/04/2021 12:04 am, neil_zampella wrote:
You CAN install v2.50 to a different directory and not mess up the earlier version

Sorry, that is incorrect. While installing to a different directory is the normal solution for installing multiple versions of an application. It wont work with JTAlert. The old install directory will loose files and there is no facility for creating a version specific Windows start-menu groups for the shortcuts.

This limitation is historical dating back to the early days of JTAlert. Eventually when the old code is gone I will move JTAlert to support multiple version installations.

de Laurie VK3AMA


locked Re: Mini-JTAlert Tool Bar

Wyndell - K5WJF
 

Could he be referring to this?

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Thursday, April 15, 2021 14:23
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Mini-JTAlert Tool Bar

 

On 16/04/2021 12:51 am, Thomas Webb wrote:

Is there a way to not have the 'mini-tool bar' not pop up when opening JTAlert 2.5?  It's doesn't present a problem, but it's one more thing to shut down when exiting the program.

Tom WA9AFM


What mini-toolbar? 2.50.0 doesn't have one.

There was some discussion yesterday about the old JTAlert main window eventually being replaced with a small tool-bar, but that was just a discussion.

All the new JTAlert 2.50.0 windows, with the gear icon in the lower-right of the window, can be set to auto-open on startup. That can be turned off. See the "Open at startup" setting on the "Window " section of the "Options" popup.

   

de Laurie VK3AMA

   




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



locked Re: Q65 decodes not showing

Seb
 

Hi Laurie, I'm using the latest beta of WSJT-X, 2.4.0-rc4.

By the way, in the past you had mentioned you were re-writing JTAlert, is that still the plan, since there are so many great additions in the latest version.


locked Re: Messaging Window, feature request

HamApps Support (VK3AMA)
 

On 16/04/2021 12:30 am, Willi Passmann wrote:
what do you think about some memories for the Messaging Window?
It would be handy for standard phrases like "please wait, I'll call you
next".

Would be a nice feature, especially in combination with the new callsign
window that can display several stations that are replying to a cq call.

Thanks for all your work!

vy 73,
Willi, DJ6JZ

That's already available.
See the Help File, it discusses the reusable messages function.

de Laurie VK3AMA
 


locked Re: Q65 decodes not showing

HamApps Support (VK3AMA)
 

On 16/04/2021 1:43 am, Seb wrote:
I’m still not seeing any Q65 calls being displayed either in the Decodes or Callsigns windows.

73 de Sebastian, W4AS

What version of WSJT-X?

I am certain that was fixed a couple of months ago, but I may have broken something in the period between when Q65 was added and when I released 2.50.0. I clearly remember the hurdles in setting up a multi-instance Q65 environment to simulate a live session of Q65 decodes.


I'll investigate.

de Laurie VK3AMA



locked Re: Callsigns window disappears and reappears after a while

HamApps Support (VK3AMA)
 

On 16/04/2021 4:18 am, Robert, SP8SN wrote:
I have installed the new version 2.50. Everything works OK but there is a problem with the "callsigns" window. It displays the decoded characters and disappears after a few dozen seconds, reappears by itself after a few seconds. I have two programs running for two transcivers. It is the same in both. What's the problem. I reinstalled 2.16 and it's ok.
--
Robert, SP8SN

The Callsigns window closing and reappearing a couple of seconds later is an indication that the JTAlertV2.Manager.exe process, which owns that window, is shutting down and being restarted.

Something is causing the Manager process to close, either an internal error or by a third party force closing the process, like your PC Protection software. If it is due to an internal error, there should be a record of the event in the JTAlert session files, I will need to examine them. 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: DxLab menus #DXLAB

HamApps Support (VK3AMA)
 

On 16/04/2021 3:53 am, thierry ben via groups.io wrote:
Menu to Dxlab Applications have disappeared from the context window ? Or i just forgot something 
73
Thierry 

Sorry, they have not been implemented.
Its on the todo list to make them available again.

de Laurie VK3AMA


locked Re: Mini-JTAlert Tool Bar

HamApps Support (VK3AMA)
 

On 16/04/2021 12:51 am, Thomas Webb wrote:
Is there a way to not have the 'mini-tool bar' not pop up when opening JTAlert 2.5?  It's doesn't present a problem, but it's one more thing to shut down when exiting the program.

Tom WA9AFM

What mini-toolbar? 2.50.0 doesn't have one.

There was some discussion yesterday about the old JTAlert main window eventually being replaced with a small tool-bar, but that was just a discussion.

All the new JTAlert 2.50.0 windows, with the gear icon in the lower-right of the window, can be set to auto-open on startup. That can be turned off. See the "Open at startup" setting on the "Window " section of the "Options" popup.

   

de Laurie VK3AMA

   


locked Re: .net.50 download

HamApps Support (VK3AMA)
 

On 15/04/2021 11:44 pm, Jim Cary wrote:
When I download the .NET.50, all I get is a screen with a bunch of labels on the left, but nothing to execute.  Please see the attached screen shot.  What am I doing wrong?

Jim

see https://hamapps.groups.io/g/Support/message/34284

de Laurie VK3AMA


locked Re: Q65 decodes not showing

Ron W3RJW
 

On Thu, Apr 15, 2021 at 11:44 AM, Seb wrote:
I’m still not seeing any Q65 calls being displayed either in the Decodes or Callsigns windows
If you are referring to version JTAlert 2.50.0, I concur.  I know it's only partially supported according to release notes, but should show something.  Logs the QSO's just fine.
 
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0 rc4, JTAlert 2.50.0, HRD Deluxe v6.7.0.323
FTdx-3000, SignaLink USB


locked Re: .NET 5 Desktop Runtime Download

HamApps Support (VK3AMA)
 

On 16/04/2021 2:18 am, KI0KK - Greg Wolfe wrote:
I ran the FrameworkCheck.exe test for the .NET 5 App and got the message that I needed to install .NET 5. I selected the option to download the APP and got a strange looking web page with no options for downloading anything? I get the same results by going to the .NET 5 link from the Ham Apps web page. I have attached a screen shot of the web page display.

I am running WIN10 Home OS.

Greg
KI0KK

The URL works fine for me with 3 different browser. Perhaps it is a transient issue. Try again.

If still no joy try one of these direct download links to the .NET installer.
Be sure to choose the correct architecture type, it needs to be the same as your Windows architecture, X64 or X86.

de Laurie VK3AMA


locked Re: .DotNet

HamApps Support (VK3AMA)
 

On 15/04/2021 11:17 pm, Todd (N3PKJ) wrote:
Trying to get .dotnet stuff for the current release & 3 different browsers & the page only does this. Anyone else having this issue?

What URL are you using?

The download URL shown on the JTAlert download page works for me.
Just now tested using Firefox, Chrome & Edge without problem.
   
    https://dotnet.microsoft.com/download/dotnet/5.0/runtime/

de Laurie VK3AMA


locked Re: Q65 decodes not showing

Seb
 

Thanks but WSJT-X is able to display and decode the Q65 signals, my issue is that they don't show up with JTAlert (others such as FT8 display fine).  I'm hoping that Laurie will have some suggestions.


locked Re: Bad Command on JTAlert 2.16.17 #FT8

HamApps Support (VK3AMA)
 

On 15/04/2021 10:44 pm, Gene Sullivan wrote:
Hi, I'm new to the group, but using JTAlert for a good while.
I tried to update to 2.5, but had problems, so I reverted back to 2.16.17 for now. I have attached the bad command screenshot.
I've been using Winlog32 with it and is logging fine to it.
Any ideas on what I'm missing ?
Thanks for any info.
WA4NUF 

This is occurring because there is no input file set for the adif importer. See the --in="" command-line parameter.
   

Your adif log file location set in the JTAlert Settings is empty. Set the path then restart JTAlert.

de Laurie VK3AMA

2901 - 2920 of 36964