Date   

locked Re: Is there an update order of priority for upgrading programs ?

Jim N6VH
 


On 7/14/2021 4:43 PM, Bob Frostholm wrote:

Hi Laurie,

I've been reading to emails today about the new versions of so many pieces of software. I'm waiting for the dust to settle before leaping in but I do want to ask if there is a particular order in which the pieces should be updated... or does it not make any difference.

I am currently operating the following (all older versions):

Net 5.0.8 (KB5004698)

JTAlert 2.50.0

WSJT-x v2.2.2

This combination works pretty well, although I have noticed that when I work a new grid on 6M and confirm that the contact is correct in both JTAlert and WSJT-x .adi logs that grid does not show up in the no longer Wanted Grids page even after I initiate rebuild alerts database. I have to exit JTAlert,(which also properly closes WSJT-x) restart it  (often several times) before the grid shows... time duration has been up to 30 minutes on occasion during which I'm being told about new grids I'm decoding that are not really new.... Hopefully it's the result of my combination of "not" up to date versions of the programs.

Cheers


--
Bob
KO6LU
_._,_._,_


Bob,

This won't answer all of your questions, but I suggest moving to WSJT-X 2.4.0 and JTAlet 2.50.4. The order might not matter (not sure, though), but I would do WSJT-X first, then JTAlert. Net 5.0.8 is good - the latest one available.

Since the no longer needed grid finally shows up, that probably means it met you confirmation requirements to start with. If so, it should show as soon as you do a database rebuild. What logging program are you using?

73,

Jim N6VH


locked Re: Upgrade with big jump in versions.

Jim N6VH
 


On 7/15/2021 11:02 AM, HamApps Support (VK3AMA) wrote:
On 15/07/2021 8:52 pm, David Gould wrote:
I am currently on v2.16.15.  Assuming I can insyall the .NET 5.0.8 successfully on my W7 Home Premium machine,
 
With JTAlert can I jump from 2.16.15  to  2.50.4?    I am still on old WSJT-X  2.3.1.

73,  Dave G3UEG

Yes, you can go straight to 2.50.4, provided you installed the NET 5.0.x Desktop Runtime.

de Laurie VK3AMA

_._,_._,_


Dave,

I would also suggest moving to WSJT-X 2.4.0.

73,

Jim N6VH



locked Re: Upgrade with big jump in versions.

HamApps Support (VK3AMA)
 

On 15/07/2021 8:52 pm, David Gould wrote:
I am currently on v2.16.15.  Assuming I can insyall the .NET 5.0.8 successfully on my W7 Home Premium machine,
 
With JTAlert can I jump from 2.16.15  to  2.50.4?    I am still on old WSJT-X  2.3.1.

73,  Dave G3UEG

Yes, you can go straight to 2.50.4, provided you installed the NET 5.0.x Desktop Runtime.

de Laurie VK3AMA


locked Re: Loss of text whilst using JTAlert

HamApps Support (VK3AMA)
 

On 16/07/2021 2:26 am, Trev wrote:
Hi Guys, sorry for the vague title, my problem is this.  For several days I have had a problem with any text I type in any program stopping part way through a sentence at seemingly random points.  I spent quite some time changing keyboards, wired and wireless but the problem always remained.  I then noticed by chance that the problem occurred each time the JTAlert window 'refreshed' which seems to be once a minute.  It is at that time the typing cursor disappears apparently 'highjacked by the JTAlert program.  I can get it back by a mouse click but, as I am not a touch typist, I generally don't notice the problem until I glance at the screen to find my cursor missing and the text having stopped at that point.
I looked through the files here but coulddn't see any mention of this which surprised me.  
Has anyone had similar and short of switching off JTAlert how did you cure the problem?
Many thanks,
Trev

If JTAlert is stealing keyboard focus it will likely be due to having the "To Top" setting enabled.
Bring up the Settings window, "Settings -> Manage Settings" menu of the main JTAlert window. Look under the "Applications -> WSJT-X / JTDX" section..

   

de Laurie VK3AMA



locked Re: JTAlert version 2.50.4

Alan Sorum WL7CG
 

Ditto - Thanks

73 Alan WL7CG


locked Loss of text whilst using JTAlert

Trev
 

Hi Guys, sorry for the vague title, my problem is this.  For several days I have had a problem with any text I type in any program stopping part way through a sentence at seemingly random points.  I spent quite some time changing keyboards, wired and wireless but the problem always remained.  I then noticed by chance that the problem occurred each time the JTAlert window 'refreshed' which seems to be once a minute.  It is at that time the typing cursor disappears apparently 'highjacked by the JTAlert program.  I can get it back by a mouse click but, as I am not a touch typist, I generally don't notice the problem until I glance at the screen to find my cursor missing and the text having stopped at that point.
I looked through the files here but coulddn't see any mention of this which surprised me.  
Has anyone had similar and short of switching off JTAlert how did you cure the problem?
Many thanks,
Trev


locked Re: Opening Multiple Callsign Windows

Michael Black
 

Inline image

Mike W9MDB 




On Thursday, July 15, 2021, 09:48:49 AM CDT, Patrick Hung <pathung@...> wrote:


Where do I go to open more callsign window "panes" than just two? I have two right now, and would like perhaps two more to show additional alerts. There is no such option under the "hamburger" settings menu.

Thanks.
--
73,

Patrick - W6AJR


locked Opening Multiple Callsign Windows

Patrick Hung
 

Where do I go to open more callsign window "panes" than just two? I have two right now, and would like perhaps two more to show additional alerts. There is no such option under the "hamburger" settings menu.

Thanks.
--
73,

Patrick - W6AJR


locked Re: JTAlert version 2.50.4

 

2.50.4 Works like a charm!  Thanks Laurie!

73, Greg, KM5GT


locked Re: JTAlert version 2.50.4

Ed Wilson
 

2.50.4 seems to be working fine here!

Ed, K0KC


locked Upgrade with big jump in versions.

David Gould
 

I am currently on v2.16.15.  Assuming I can insyall the .NET 5.0.8 successfully on my W7 Home Premium machine,
 
With JTAlert can I jump from 2.16.15  to  2.50.4?    I am still on old WSJT-X  2.3.1.

73,  Dave G3UEG


locked Re: 2.50.3 problems

chas cartmel
 

No problems encountered here. Mine are installed away from the program files folders, actually on separate SSDs and their locations whitelisted in my AV/Firewall software (Bullguard). I avoid the Program Files folders when I can, and have also granted full access to my main user account which has administrator privileges.

73 Charlie
G4EST
www.g4est.me.uk
Stay safe out there

-----Original Message-----
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Phil Cooper via groups.io
Sent: 14 July 2021 16:41
To: Support@HamApps.groups.io
Subject: Re: [HamApps] 2.50.3 problems

Hi all,

Rather than what hardware/OS works, or doesn't, it may be more pertinent to see where JTAlert and WSJTx are installed.

My WSJTx is installed at C:\WSJT\wsjtx\bin\wsjtx.exe
And JTAlert is installed at C:\HamApps\JTAlert2.5\JTAlert\

It may well be that some programs installed into the Program Files folder are causing issues due to OneDrive saving copies.
This was exactly what my problem was with N1MM+, and meant I had to relocate it to a directory outside the Program Files area.

So, who has one or both installed in the Program files directory?

73 de Phil GU0SUP





This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


locked Re: [Request] menu for "lookups" for Log4OM2

kiyo
 

Hi Rick.
I just started using Log4OM2 this week and I don't know how to use it due to lack of study, so I learned to display it in the Vew menu "Worked before" of Log4OM2, so I will use it. Thank you.

I am displaying WSJT-X, JTALert and Log4OM2 in a small space and a small display device, so I want to see the past QSO situation without increasing the number of windows and moving the focus like when using DX Keeper. I wanted to use JTAlert to select nifty 73 messages such as "TU NEWBAND 73", "TU NEWMODE 73" and "TU x BANDS 73". Because of that, there are requests such as the request posted a while ago (# 35690) that wants to display the number of QSO bands regardless of the submode.

--
kiyo


locked Re: [Request] menu for "lookups" for Log4OM2

Rick VK6RK
 

Hi Kiyo,

This is different to Worked before (F10).

It opens another window, similar to below.
Columns are customisable just like other Log4OM windows.


73, Rick VK6RK

On 15/07/2021 10:18, kiyo wrote:
Hi Rick
Thank you.
I know about worked before (F10).
If possible, I wanted to display the window without putting it in
focus, just like with DXKeeper.

--
kiyo

2021年7月15日(木) 10:45 Rick VK6RK <rick@...>:
Hi Kiyo,

Just open the Worked Before window, using View - Worked before.  It will stay open all the time and show multiple worked before entries, for that particular call.

73, Rick VK6RK

On 15/07/2021 09:22, kiyo wrote:

Hello.
I recently changed from DXKeeper to Log4OM2. JTAlert is very comfortable to use.

The slightly inconvenient point is that it is troublesome to know the past QSO status immediately. Isn't the "DX Lab lookups" menu provided for DXkeeper also available for Log4OM2?

When you actually call the DX station, the character string is placed in the call sign of the other party of Log4OM2, so it does not seem to be so difficult compared to DX Keeper. If this menu addition is realized, Log4OM2 users will be happy because they can see the past QSO status by the same operation as DXKeeper before actually calling operation. In that case, there is no need to press "worked before (F10)" in the Log4OM2 window.

Please consider it.

I'm using:
WSJT-X 2.3.0 (I use this to avoid a bug that Tx5 generated by JTAlert is not sent when Tx4 is RRR)
JTAlert 2.50.4
Log4OM2

-
kiyo


locked Re: [Request] menu for "lookups" for Log4OM2

kiyo
 

Hi Rick
Thank you.
I know about worked before (F10).
If possible, I wanted to display the window without putting it in
focus, just like with DXKeeper.

--
kiyo

2021年7月15日(木) 10:45 Rick VK6RK <rick@vk6xlr.net>:


Hi Kiyo,

Just open the Worked Before window, using View - Worked before. It will stay open all the time and show multiple worked before entries, for that particular call.

73, Rick VK6RK

On 15/07/2021 09:22, kiyo wrote:

Hello.
I recently changed from DXKeeper to Log4OM2. JTAlert is very comfortable to use.

The slightly inconvenient point is that it is troublesome to know the past QSO status immediately. Isn't the "DX Lab lookups" menu provided for DXkeeper also available for Log4OM2?

When you actually call the DX station, the character string is placed in the call sign of the other party of Log4OM2, so it does not seem to be so difficult compared to DX Keeper. If this menu addition is realized, Log4OM2 users will be happy because they can see the past QSO status by the same operation as DXKeeper before actually calling operation. In that case, there is no need to press "worked before (F10)" in the Log4OM2 window.

Please consider it.

I'm using:
WSJT-X 2.3.0 (I use this to avoid a bug that Tx5 generated by JTAlert is not sent when Tx4 is RRR)
JTAlert 2.50.4
Log4OM2

-
kiyo



locked Re: [Request] menu for "lookups" for Log4OM2

Rick VK6RK
 

Jim,

Should have mentioned that "View - Worked before" was for Log4OM.

True, you can use F6 in JTSAlert however Log4OM gives more comprehensive info.

73, Rick VK6RK

On 15/07/2021 10:03, Jim Cooper wrote:
On 15 Jul 2021 at 9:44, Rick VK6RK wrote:

Just open the Worked Before window, using View - Worked before. It
will stay open all the time and show multiple worked before entries,
for that particular call.

73, Rick VK6RK
Rick, what version of JTalert are you using?

I am using 2.50.4 and under View tab it is the 
"Callsign History Window F6" ... the window 
itself has the title "QSO History" and shows 
all QSOs with that call using the mode you are 
currently using. 

w2jc


locked Re: [Request] menu for "lookups" for Log4OM2

Jim Cooper
 

On 15 Jul 2021 at 9:44, Rick VK6RK wrote:

Just open the Worked Before window, using View - Worked before. It
will stay open all the time and show multiple worked before entries,
for that particular call.

73, Rick VK6RK
Rick, what version of JTalert are you using?

I am using 2.50.4 and under View tab it is the
"Callsign History Window F6" ... the window
itself has the title "QSO History" and shows
all QSOs with that call using the mode you are
currently using.

w2jc


locked Re: [Request] menu for "lookups" for Log4OM2

Rick VK6RK
 

Hi Kiyo,

Just open the Worked Before window, using View - Worked before.  It will stay open all the time and show multiple worked before entries, for that particular call.

73, Rick VK6RK

On 15/07/2021 09:22, kiyo wrote:
Hello.
I recently changed from DXKeeper to Log4OM2. JTAlert is very comfortable to use.

The slightly inconvenient point is that it is troublesome to know the past QSO status immediately. Isn't the "DX Lab lookups" menu provided for DXkeeper also available for Log4OM2?

When you actually call the DX station, the character string is placed in the call sign of the other party of Log4OM2, so it does not seem to be so difficult compared to DX Keeper. If this menu addition is realized, Log4OM2 users will be happy because they can see the past QSO status by the same operation as DXKeeper before actually calling operation. In that case, there is no need to press "worked before (F10)" in the Log4OM2 window.

Please consider it.

I'm using:
WSJT-X 2.3.0 (I use this to avoid a bug that Tx5 generated by JTAlert is not sent when Tx4 is RRR)
JTAlert 2.50.4
Log4OM2

-
kiyo


locked [Request] menu for "lookups" for Log4OM2

kiyo
 

Hello.
I recently changed from DXKeeper to Log4OM2. JTAlert is very comfortable to use.

The slightly inconvenient point is that it is troublesome to know the past QSO status immediately. Isn't the "DX Lab lookups" menu provided for DXkeeper also available for Log4OM2?

When you actually call the DX station, the character string is placed in the call sign of the other party of Log4OM2, so it does not seem to be so difficult compared to DX Keeper. If this menu addition is realized, Log4OM2 users will be happy because they can see the past QSO status by the same operation as DXKeeper before actually calling operation. In that case, there is no need to press "worked before (F10)" in the Log4OM2 window.

Please consider it.

I'm using:
WSJT-X 2.3.0 (I use this to avoid a bug that Tx5 generated by JTAlert is not sent when Tx4 is RRR)
JTAlert 2.50.4
Log4OM2

-
kiyo


locked Re: JTAlert version 2.50.4

Robert Lorenzini
 

Well I hope so, Laurie needs a vacation after the last week.

Bob - wd6dod

On 7/14/2021 5:26 PM, Jamie GOLLY wrote:
Just downloaded and installed. Works Fantastic!!!


Thank you Laurie and team, this should make people happy.



Jamie
K6NGN

2341 - 2360 of 38435