Date   

locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

BOBBY E Chandler <bobbye@...>
 

Laurie, what I meant was the problem of clicking a call in JTAlert would work the first time and sometimes the second, but after that it would not enable the transmit. After a restart, it would work a one or two times but then not transmitting. I am running WSJTX on Windows 10. Hope this clears it up.

Bobby/N4AU

-- 


  Bobby Chandler
bobbye@...
   n4au@...  


locked Sound alert new callsign

ulidf5sf2002 <uli@...>
 

Hello,

is it possible to get a sound alert, only if a new station (callsign) is calling cq ?
Maybe in a future version ?

Tnx es 73
Uli
DF5SF


locked Re: Download of 2.13.0 shows a virus

Adrian
 

I use AVG and it delayed install for awhile until program analysed by AVG

Adrian

On 11 Mar 2019, at 14:14, John <jonie41@bell.net> wrote:

I'll wager that he is using Norton.

John
VE3KKQ

---------- Original Message ----------
From: "Michael Black via Groups.Io" <mdblack98=yahoo.com@groups.io>
Date: March 10, 2019 at 10:23 PM


It's quite common for some antivirus programs to report JTAlert as a Trojan on
new releases until somebody sends in the executable to be analyzed.
You don't say what antivirus you're using but report it to them and they'll
quite likely release an update to clear it.
de Mike W9MDB



On Sunday, March 10, 2019, 10:17:27 PM CDT, K8TS
<dalecole3502@comcast.net> wrote:

Good Day
Just downloaded 2.13.0, and got a notification that I had a trojan. Clicking
on the virus check just below where the download link is showed the following:
Antivirus>Rising>Trojan Win32.Agent_.pb (CLASSIC) also shown was
Antivirus>Trapmine>malicious.moderate.ml.score
From previous posts, I have seen that your software is clean although machines
may say not.
Are these to be worried about, or has it detected something my antivirus
(Webroot and Windows) missed?
Running Windows 10 (1803),All updates have been done, did two scans and they
still showed.
Thanks, Dale K8TS




locked Re: Download of 2.13.0 shows a virus

John
 

I'll wager that he is using Norton.

John
VE3KKQ

---------- Original Message ----------
From: "Michael Black via Groups.Io" <mdblack98=yahoo.com@groups.io>
Date: March 10, 2019 at 10:23 PM


It's quite common for some antivirus programs to report JTAlert as a Trojan on
new releases until somebody sends in the executable to be analyzed. 
You don't say what antivirus you're using but report it to them and they'll
quite likely release an update to clear it.
de Mike W9MDB



On Sunday, March 10, 2019, 10:17:27 PM CDT, K8TS
<dalecole3502@comcast.net> wrote:

Good Day
Just downloaded 2.13.0, and got a notification that I had a trojan.  Clicking
on the virus check just below where the download link is showed the following:
Antivirus>Rising>Trojan Win32.Agent_.pb (CLASSIC) also shown was
Antivirus>Trapmine>malicious.moderate.ml.score
From previous posts, I have seen that your software is clean although machines
may say not.
Are these to be worried about, or has it detected something my antivirus
(Webroot and Windows) missed?
Running Windows 10 (1803),All updates have been done, did two scans and they
still showed.
Thanks, Dale K8TS



locked Re: Download of 2.13.0 shows a virus

Michael Black
 

It's quite common for some antivirus programs to report JTAlert as a Trojan on new releases until somebody sends in the executable to be analyzed. 

You don't say what antivirus you're using but report it to them and they'll quite likely release an update to clear it.

de Mike W9MDB




On Sunday, March 10, 2019, 10:17:27 PM CDT, K8TS <dalecole3502@...> wrote:


Good Day
Just downloaded 2.13.0, and got a notification that I had a trojan.  Clicking on the virus check just below where the download link is showed the following:
Antivirus>Rising>Trojan Win32.Agent_.pb (CLASSIC) also shown was Antivirus>Trapmine>malicious.moderate.ml.score
From previous posts, I have seen that your software is clean although machines may say not.
Are these to be worried about, or has it detected something my antivirus (Webroot and Windows) missed?
Running Windows 10 (1803),All updates have been done, did two scans and they still showed.
Thanks, Dale K8TS


locked Download of 2.13.0 shows a virus

K8TS
 

Good Day
Just downloaded 2.13.0, and got a notification that I had a trojan.  Clicking on the virus check just below where the download link is showed the following:
Antivirus>Rising>Trojan Win32.Agent_.pb (CLASSIC) also shown was Antivirus>Trapmine>malicious.moderate.ml.score
From previous posts, I have seen that your software is clean although machines may say not.
Are these to be worried about, or has it detected something my antivirus (Webroot and Windows) missed?
Running Windows 10 (1803),All updates have been done, did two scans and they still showed.
Thanks, Dale K8TS


locked FRIDAY March 15th - Nobel Laureate Speaks at FLARC

Jim Cooper
 

FLARC.net     http://blog.FairLawnARC.org     @FairLawnARC
View this email in your browser

Amateur Radio Club Station   W 2 N P T


Click on image to download PDF of this flyer.

 

Copyright © 2019 Bergen Amateur Radio Association BARA, All rights reserved.
You are receiving this email as a licensed amateur radio operator.

Our mailing address is:
Bergen Amateur Radio Association BARA
286 Ridgewood Blvd North
Washington Township, NJ 07676

Add us to your address book


Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list

Email Marketing Powered by Mailchimp


locked #JTDX #IMPORTANT #ANNOUNCEMENT : JTDX incompatible with JTAlert 2.13.0 #JTDX #Important #Announcement

HamApps Support (VK3AMA)
 

JTDX is not compatible with JTAlert 2.13.0 with respect to Callsign highlighting instructions sent by JTAlert.

JTDX users need to turn off the "Color Band Activity Callsign with alert colors" checkbox in the Settings, "Applications -> WSJT-X" section.
   
   

The problem is that JTDX developers have chosen to remove some of the standard WSJT-X UDP API commands, Callsign highlighting is one of the commands. Each UDP command has a unique identifying number (#13 in this case), so why JTDX is breaking when it receives a command it doesn't support is unknown, it should just ignore/dump unsupported UDP command packets, IMO.

The next JTAlert release
explicitly prevents sending the command to JTDX ignoring the state of this setting when using JTDX.

de Laurie VK3AMA


locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

Bob Davet
 

Laurie:

Just installed 2.13.0 and made the change. So far it has corrected the issue. I will give it a better workout later today and tomorrow and if anything comes up I will let you know.

Thanks

Bob
W8RID


locked Re: Changing name of Receiver in 2.13

HamApps Support (VK3AMA)
 

On 10/03/2019 2:56 pm, HamApps Support (VK3AMA) via Groups.Io wrote:
I chose to use the word Receiver rather than instance number as it is much easier to relate decodes to the WSJT-X instance producing the decodes (via its --rig-name).

I neglected to mention, "Receiver" is likely to be changed in a future version of the Decodes History.

I thought long and hard about what to use rather than "Instance" and came up with "Receiver", but I was never truly happy about that. I will likely change it to "Src" short for "Source", the source of the decodes, which I think is more fitting.

de Laurie VK3AMA
 


locked Re: Changing name of Receiver in 2.13

HamApps Support (VK3AMA)
 

On 10/03/2019 2:25 pm, Mark Hatch wrote:
First off, what a big improvement! The work done in the Decodes History makes  JTAlert so much easier to use. I no longer have to be "quick on the draw" to start a QSO with a desirable station. Buy looking at the Decodes history I can figure out who matches my time, relative signal strength, etc. Thank you!

One question....  Where is the name of the Receiver set? I am seeing "Default" in the decodes history window. I am using omnirig, log40m, and win4icom suite if these matter.

73
Mark
Mark,

From the "Filters" topic of the help file...
The "Rcvr" selector, short for "Receiver" is typically the "--rig-name" used with WSJT-X instances. The Decodes History does not use instance numbers (#1, #2, #3, etc). To show only the decodes of one WSJT-X instance, use the "Rcvr" selector. For WSJT-X instances without a --rig-name parameter, "Default" is used.

If your only running one instance of WSJT-X, you can hide the Rcvr column.

I chose to use the word Receiver rather than instance number as it is much easier to relate decodes to the WSJT-X instance producing the decodes (via its --rig-name).

Plus the future JTAlertV3, of which this new Decodes History is a component has no concept of instances, there is only one copy of JTAlert running managing multiple WSJT-X instances with no predefined startup order with WSJT-X being closed and opened at any time without needing a JTAlert restart, it simply manages any detected instance of WSJT-X automatically. As such, instance numbers are irrelevant, the better indicator is the WSJT-X --rig-name and I had to come up with a name for a default instance of WSJT-X running without a --rig-name, so chose "Default"

de Laurie VK3AMA


locked Changing name of Receiver in 2.13

Mark Hatch
 

First off, what a big improvement! The work done in the Decodes History makes  JTAlert so much easier to use. I no longer have to be "quick on the draw" to start a QSO with a desirable station. Buy looking at the Decodes history I can figure out who matches my time, relative signal strength, etc. Thank you!

One question....  Where is the name of the Receiver set? I am seeing "Default" in the decodes history window. I am using omnirig, log40m, and win4icom suite if these matter.

73
Mark


locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

HamApps Support (VK3AMA)
 

On 10/03/2019 12:12 pm, BOBBY E Chandler wrote:

Same problem with WSJTX. Back to prior JTAlert version and all OK.

Bobby/N4AU

What problem is that?

Are you referring to the problem reported by JTDX users? I can't see how that would be the case as their problem is related to how JTDX is coded internally.

Does this help...
https://hamapps.groups.io/g/Support/message/23581

de Laurie VK3AMA


locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

BOBBY E Chandler <bobbye@...>
 

Same problem with WSJTX. Back to prior JTAlert version and all OK.

Bobby/N4AU

-- 


  Bobby Chandler
bobbye@...
   n4au@...  


locked Re: changing callsign for hamspots.net site

Razvan Popescu
 

Thank you so much, Laurie!
R


locked Re: changing callsign for hamspots.net site

HamApps Support (VK3AMA)
 

On 10/03/2019 11:31 am, Razvan Popescu wrote:
I've changed my callsign and would like to update it in my registration for HamSpots.net. Unfortunately I found no mean to alter this setting (the only option is to update the password).  I would gladly register a new account with the new callsign, but that fails too, because I'm using the same email address...

Is there a way to change the callsign associated with this account (and keep the email address)??

Thanks,
Razvan
W2RP 
(previously WA2RP)
Razvan.

Unfortunately the Callsign management code used by HamSpots doesn't allow for users to change their Callsign. It is manual process performed by an Administrator.

I have made the Callsign change for you. Your password remains unchanged.

de Laurie VK3AMA


locked changing callsign for hamspots.net site

Razvan Popescu
 

Hi,
I've changed my callsign and would like to update it in my registration for HamSpots.net. Unfortunately I found no mean to alter this setting (the only option is to update the password).  I would gladly register a new account with the new callsign, but that fails too, because I'm using the same email address...

Is there a way to change the callsign associated with this account (and keep the email address)??

Thanks,
Razvan
W2RP 
(previously WA2RP)


locked Re: DOUBLE CLICK TO TX #FT8

HamApps Support (VK3AMA)
 

On 10/03/2019 11:10 am, Michael Paul wrote:
prior to JTAlertX 2.13.0 I was able to double click on a call in JTAlert and it would initiate a TX in JTDX.  After updating to JTAlertX 2.13.0 no amount of double clicking on call signs will enable a TX.  Double click on Callsign inside JTDX still initiates a reply. 

I have had a quick look over JTAlertX 2.13.0 settings and cannot find a double click to reply setting.

Anyone else found the same change in 2.13.0?

Mick.
See this message... https://hamapps.groups.io/g/Support/message/23581

Let me know if this corrects the JTDX problems you experienced.

de Laurie VK3AMA


locked Re: DOUBLE CLICK TO TX #FT8

Dave Garber
 

there is a click box, on the settings/general page of wsjt |" double click on call sets tx enable"

is that what you need??
Dave Garber
VE3WEJ / VE3IE


On Sat, Mar 9, 2019 at 7:10 PM Michael Paul <mickwpaul@...> wrote:
prior to JTAlertX 2.13.0 I was able to double click on a call in JTAlert and it would initiate a TX in JTDX.  After updating to JTAlertX 2.13.0 no amount of double clicking on call signs will enable a TX.  Double click on Callsign inside JTDX still initiates a reply. 

I have had a quick look over JTAlertX 2.13.0 settings and cannot find a double click to reply setting.

Anyone else found the same change in 2.13.0?

Mick.


locked DOUBLE CLICK TO TX #FT8

Michael Paul
 

prior to JTAlertX 2.13.0 I was able to double click on a call in JTAlert and it would initiate a TX in JTDX.  After updating to JTAlertX 2.13.0 no amount of double clicking on call signs will enable a TX.  Double click on Callsign inside JTDX still initiates a reply. 

I have had a quick look over JTAlertX 2.13.0 settings and cannot find a double click to reply setting.

Anyone else found the same change in 2.13.0?

Mick.

15021 - 15040 of 38542