Date   

locked Re: 2.16.13 setup files are corrupt

Rich - K1HTV
 

Eliot,
I also had to temporarily turn off virus protection, then create an exception for the setup file before turning the protection back on. If I didn't, the setup file got quarantined before I could even run it.

73,
Rich - K1HTV


locked Gray colored CQ - additional information

Rich - K1HTV
 

I forgot to mention that in addition to the previously worked 8P and 6E prefix stations calling CQ not having a gray background in the WSJT-X Band activity column, I also have noticed that they also Do NOT APPEAR in the JTAlert matrix of displayed callsigns for the 15 second sequence when they appear in WSJT-X.

73,
Rich - K1HTV


locked Gray color on worked stations calling CQ

Rich - K1HTV
 

In WSJT-X, when stations that I have not worked call CQ, colors the entire decoded CQ line is green. as is expected. When a station has been worked before on a band, the background of the callsign is gray, as expected. However, I have noticed in versions 12 and 13, that when three Barbados stations 8P6PE, 8P6EX and 8P6QA and also Mexican station 6E6E, all that I have already worked call CQ on 20M FT8, the gray background is missing. The entire CQ line is green. This gives the indication that I have not worked them before and results in duplicate QSOs on that band. 

I am using WSJT-X 2.2.2 and the latest version of DXKeeper is used for logging. I checked the DXK database and it shows that I have worked all of the above mentioned stations on 20M FT8 in recent months.

Can I assume that all of the gray background color behind the callsigns of stations already worked on a band in the WSJT-X "Band Activity" column are the result of JTAlert's determination that they are in the DXK database?  Or does JTAlert rely on the wsjtx_log.adi file? All of the 20M QSOs made with the above mentioned stations appear in both the wsjtx_log.adi and DXK mdb database files,.

Is there a bug in the way that JTAlert handles station callsigns starting with 8 or 6, when it comes to the gray background for indicating worked before? I worked 5K87LK and subsequent CQs by that station have a gray background as expected. I haven't yet checked the CQs of stations with calls starting with other numbers.

73,
Rich - K1HTV


locked Re: 2.16.13 setup files are corrupt

James Hertel
 

Turn off Virus Protection ... for download...

On 8/30/2020 5:53 AM, Hasan Schiers N0AN wrote:
worked fine here
Hasan


On Sun, Aug 30, 2020 at 6:58 AM Eliot - KE0N via groups.io <ke0n=rocketmail.com@groups.io> wrote:
Hello-
Attempting to download the 2.16.13 latest rev and met with setup files are corrupt. Anyone else having this issue?


locked Re: 2.16.13 setup files are corrupt

Hasan Schiers N0AN
 

worked fine here
Hasan


On Sun, Aug 30, 2020 at 6:58 AM Eliot - KE0N via groups.io <ke0n=rocketmail.com@groups.io> wrote:
Hello-
Attempting to download the 2.16.13 latest rev and met with setup files are corrupt. Anyone else having this issue?


locked Re: The JTAlert test team is looking for some additional members.

Guy G4DWV 4X1LT
 
Edited

Hi Laurie,

I will be happy to help, but I am not a power user by any means for my contribution may not be useful. I NEVER use any JT modes without JTAlert. I am computer savvy having been online well before the Internet and I started computing as a hobby in April 1992.

--
73 de Guy G4DWV 4X1LT


locked 2.16.13 setup files are corrupt

Eliot - KE0N
 

Hello-
Attempting to download the 2.16.13 latest rev and met with setup files are corrupt. Anyone else having this issue?


locked Re: The JTAlert test team is looking for some additional members.

Tom Schaefer NY4I
 

I think this was the first test, “ If your (sic) interested, please email me direct (vk3ama.ham.apps [at] gmail.com)...”

:)

Tom NY4I 

Principal Solutions Architect
Better Software Solutions, Inc. 
727-437-2771


locked Re: double-click in JTAlert not working #FT8

ildarin@...
 

Good thought.
Tried that.
Troubles remain... :-(
JTAlert simply isn't reacting to mouse clicks in the callsign window (clicking on menu settings produces the expected result)


locked Re: The JTAlert test team is looking for some additional members.

asobel@...
 

Laurie

 

I will be happy to help. Join me in!

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Sunday, August 30, 2020 1:16 AM
To: Support@HamApps.groups.io
Subject: [HamApps] The JTAlert test team is looking for some additional members.

 

I am looking for some additional members to participate in JTAlert testing.

My expectation is that members of this group are computer savvy, are frequent users of WSJT-X and its modes, are comfortable with using JTAlert and Windows and don't need hand-holding when it comes to using Windows File Explorer and file management, installing and uninstalling applications.

The group message volume is very small, sometimes going a week without a posting, but Members are encouraged to provide feedback on any new JTAlert build posted for testing.

The main purpose of the Testing group is to provide members with early access to JTAlert releases and interim builds and to use these releases as part of their normal Digital activity to shake out any bugs or behavioral problems that may have crept in during coding and to test any new features. I don't expect members to exercise all functions of JTAlert with every build released.

Users of WSJT-X/JTDX, and one of the major loggers supported by JTAlert, ADIF, DXKeeper, ACLog, Log4OM or HRD, are needed.

Note: Users who become members of the Test team but don't contribute to any of the online discussion for an extended period (3 months) will automatically be removed from the Team.

If your interested, please email me direct (vk3ama.ham.apps [at] gmail.com) with a brief outline of your operating environment, Windows version, Logger used, if using WSJT-X or JTDX, if using multiple JTAlert instances, how long using JTAlert, etc.

de Laurie VK3AMA
   


locked Feature request

John C
 

Hello Laurie, I hope all is well up there.   I have had a request from a mate who is not a forum member to ask for this, and I also think its might be handy.

FT8 is soooooo popular now that jtalert cannot at times, display all of the decoded calls that are on air, so, would it be possible to increase the current maximum number of callsign lines from the present 4 and also increase the maximum 'per line' from the current 9 ?????

 

regards

John
VK7XX


locked Re: double-click in JTAlert not working #FT8

Dwaine Pipe
 

Hi

 

You could try updating to the latest WSJT-X (vers 2.2.2) and see if your troubles magically disappear.

 

Just my 2c 😊

 

Cheers

David

VK7YUM

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of ildarin@...
Sent: Sunday, 30 August 2020 11:11 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] double-click in JTAlert not working #FT8

 

Unchecking "Show DXCC, grid, etc" doesn't change anything.
WSJT-X 2,1.0
JTAlert 2.16.13
Win 7

If I double-click on a CQ in WSJT-X it the Tx 1 field in WSJT-X is populated and transmission begins.

If I double-click on a CQ in JTAlert, nothing happens.


locked Re: double-click in JTAlert not working #FT8

ildarin@...
 

Unchecking "Show DXCC, grid, etc" doesn't change anything.
WSJT-X 2,1.0
JTAlert 2.16.13
Win 7

If I double-click on a CQ in WSJT-X it the Tx 1 field in WSJT-X is populated and transmission begins.

If I double-click on a CQ in JTAlert, nothing happens.


locked deouble-click in JTAlert not working #FT8

ildarin@...
 

I see numerous posts on this topic, but no solutions. Unchecking "Color Band Activity" had no effect.
I have the same problem.
Double-clicking in the WSJT-X window works as expected.
.
Tested on Win 7.


locked Re: COMMENT

Kyle K7KE
 

Your post lacked specifics. Here's my take. I've used HRD since 2014. I've found it to be solid and the couple of times I have needed support, the support provided was excellent. I use a pristine ham radio-only PC and Windows updates have never been a problem. And lastly, Laurie is not a 'she'.

Just me 2 cents.

Kyle
K7KE


locked Re: COMMENT

Robert Lorenzini
 

You skate on thin ice.

Bob - wd6dod

On 8/29/2020 3:29 PM, Tim wrote:
I still use 8.1 and have auto update turned off. I want to control when an update is allowed into the QTH computer.

Tim - N8NEU
FN00ah



-------- Original message --------
From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...>
Date: 8/29/20 16:16 (GMT-05:00)
Subject: Re: [HamApps] COMMENT

On 29/08/2020 11:57 pm, WN8HGZ wrote:
> Every time I have windows upgrade I have problems with software that
> was running good begins to not work properly: SOOO! I now set windows
> to up grade when I want and I hold off as long as can. Since there are
> so many parameter's to set when u first get started u don't know what
> is causing the problem. Sooooo! of its working don't fix it. I have
> found that Laurie VK3AMA  to be right on with her help, very sharp and
> thanks so much. HRD had bad  file and she gave me the answer. HRD was
> ZERO help and wanted a fee for maintenance which I found ok however: 
> I paid the fee for 2 years and they still couldn't help me  with
> certain issues. Just some thoughts and sharing my experiences .

FYI, Laurie is an OM name here in VK.

de Laurie (OM) VK3AMA






locked Re: The JTAlert test team is looking for some additional members.

Dwight Bosselman
 

Hi Laurie and I'm willing to help however I can.

I run windows 10 Pro with the DXLab suite and been using JTAlert since the beginning of time. I have over 45000 qso's logged with the mode and use wsjt-x.

73 Dwight NS9I

On 8/29/2020 5:15 PM, HamApps Support (VK3AMA) wrote:
I am looking for some additional members to participate in JTAlert testing.

My expectation is that members of this group are computer savvy, are frequent users of WSJT-X and its modes, are comfortable with using JTAlert and Windows and don't need hand-holding when it comes to using Windows File Explorer and file management, installing and uninstalling applications.

The group message volume is very small, sometimes going a week without a posting, but Members are encouraged to provide feedback on any new JTAlert build posted for testing.

The main purpose of the Testing group is to provide members with early access to JTAlert releases and interim builds and to use these releases as part of their normal Digital activity to shake out any bugs or behavioral problems that may have crept in during coding and to test any new features. I don't expect members to exercise all functions of JTAlert with every build released.

Users of WSJT-X/JTDX, and one of the major loggers supported by JTAlert, ADIF, DXKeeper, ACLog, Log4OM or HRD, are needed.

Note: Users who become members of the Test team but don't contribute to any of the online discussion for an extended period (3 months) will automatically be removed from the Team.

If your interested, please email me direct (vk3ama.ham.apps [at] gmail.com) with a brief outline of your operating environment, Windows version, Logger used, if using WSJT-X or JTDX, if using multiple JTAlert instances, how long using JTAlert, etc.

de Laurie VK3AMA
   


locked Re: COMMENT

Tim
 

I still use 8.1 and have auto update turned off. I want to control when an update is allowed into the QTH computer.

Tim - N8NEU
FN00ah



-------- Original message --------
From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...>
Date: 8/29/20 16:16 (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] COMMENT

On 29/08/2020 11:57 pm, WN8HGZ wrote:
> Every time I have windows upgrade I have problems with software that
> was running good begins to not work properly: SOOO! I now set windows
> to up grade when I want and I hold off as long as can. Since there are
> so many parameter's to set when u first get started u don't know what
> is causing the problem. Sooooo! of its working don't fix it. I have
> found that Laurie VK3AMA  to be right on with her help, very sharp and
> thanks so much. HRD had bad  file and she gave me the answer. HRD was
> ZERO help and wanted a fee for maintenance which I found ok however: 
> I paid the fee for 2 years and they still couldn't help me  with
> certain issues. Just some thoughts and sharing my experiences .

FYI, Laurie is an OM name here in VK.

de Laurie (OM) VK3AMA





locked The JTAlert test team is looking for some additional members.

HamApps Support (VK3AMA)
 

I am looking for some additional members to participate in JTAlert testing.

My expectation is that members of this group are computer savvy, are frequent users of WSJT-X and its modes, are comfortable with using JTAlert and Windows and don't need hand-holding when it comes to using Windows File Explorer and file management, installing and uninstalling applications.

The group message volume is very small, sometimes going a week without a posting, but Members are encouraged to provide feedback on any new JTAlert build posted for testing.

The main purpose of the Testing group is to provide members with early access to JTAlert releases and interim builds and to use these releases as part of their normal Digital activity to shake out any bugs or behavioral problems that may have crept in during coding and to test any new features. I don't expect members to exercise all functions of JTAlert with every build released.

Users of WSJT-X/JTDX, and one of the major loggers supported by JTAlert, ADIF, DXKeeper, ACLog, Log4OM or HRD, are needed.

Note: Users who become members of the Test team but don't contribute to any of the online discussion for an extended period (3 months) will automatically be removed from the Team.

If your interested, please email me direct (vk3ama.ham.apps [at] gmail.com) with a brief outline of your operating environment, Windows version, Logger used, if using WSJT-X or JTDX, if using multiple JTAlert instances, how long using JTAlert, etc.

de Laurie VK3AMA
   


locked Correct Multicast UDP IP Range for WSJT-X/JTDX supported by JTAlert. #FIX

HamApps Support (VK3AMA)
 

In previous release notes the quoted JTAlert supported UDP Multicast IP range for WSJT-X was incorrect.

The correct range supported by JTAlert is 239.0.0.0 to 239.255.255.255

The previously suggested IP of 239.255.0.0 falls within this range and is still a valid choice.

WSJT-X/JTDX users are encouraged to convert from using the unicast 127.0.0.1 default to using a multicast address for the UDP Server settings in WSJT-X/JTDX. Nothing needs to be changed in JTAlert, it automatically adjusts per your WSJT-X/JTDX settings.

de Laurie VK3AMA