wsjt-devel — WSJT software development

Re: [wsjt-devel] Message Creator/QSY Monitor Request for feature

[Reino T. <rei...@ko...>]

Hi Scott,

Interesting proposal to extend the Message System outside a QSO. As it is presented in the user guide the recipient should know the sender from previous messages, whether your current QSO partner or DXpedition station. 

You are implying that some other station, who may or may not have called you earlier (but you have not answered), is sending that message to you, aren’t you. That feature would require what you described, but still the sending station is identified only by the received frequency. The nature of the Message System is more or less broadcasting and only implied one to one.

There are already other services that present active stations’ callsigns on the frequency scale. 

 

73, Reino OH3mA

 

From: Scott Armstrong via wsjt-devel <wsj...@li...> 
Sent: Wednesday, January 15, 2025 11:45 AM
To: Uwe, DG2YCB <dg...@gm...>
Cc: Scott Armstrong <aa5...@gm...>; WSJT software development <wsj...@li...>
Subject: Re: [wsjt-devel] Message Creator/QSY Monitor Request for feature

 

Hi Uwe,

I don't think you understand what I am proposing.
I agree it would be nice if we could use the free form text message to convey that information but that is not an option.

What I am proposing does not use the message payload.

I'll try to show you with the following picture/text.  Follow the numbers.

#1. W5ABC has a QSO with me.
#2  AA5AM sends a QSY message to W5ABC and he receives it. Pop up window opens. Message appears in the QSY Monitor window. 

 Imagine a crowded band,  lots of signals. Who is the message from where do I point my antenna?

Now for my proposal to determine who the message is from.

#3 Take the DF of the received QSY Message.

#4 Compare the DF of the QSY Message with the DF of previous decodes and try to match one or more that are within maybe +/- 2Hz.   ( DF QSY = DF QSO decode(s))
#5  DFs match!  Oh. The message is from AA5AM.
# 6. Add AA5AM  to the Pop up window and QSY monitor window.


Thoughts?

73,

Scott AA5AM



 

On Wed, Jan 15, 2025 at 2:31 AM Uwe, DG2YCB <dg...@gm... <mailto:dg...@gm...> > wrote:

Hi Scott,

I agree this would be useful, but unfortunately this is not possible for technical reasons. We use normal freetext messages for the new message system, and already make full use of the 13 characters available.


73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm... <mailto:dg...@gm...> 
Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB> 



 

Am 15.01.2025 um 01:27 schrieb Scott Armstrong via wsjt-devel:

Hey Guys,

Small issue.   If I receive a QSY message from someone, I have no idea who sent that message other than trying to track down the  station by his DF and that is only good if he hasn't moved.
This will not work so well on a busy band in the heat of the contest.

I could  blindly QSY to that band but in the case of a band with highly directional antennas, where do I aim the antenna? Not as much of an issue on the lower bands but could still be a problem.

This is what I see displayed in the QSY monitor window. It doesn't even show the DF the message came in at.




I have a request,

Can some functionality be added that will take the DF of the QSY message and match that to the DF maybe within +/- a few Hz to other prior decodes, pull the callsign of that station that sent the message and display that callsign in the QSY monitor window?

Thank you and 73,

Scott AA5AM

 

_______________________________________________
wsjt-devel mailing list
wsj...@li... <mailto:wsj...@li...> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

Re: [wsjt-devel] Message Creator/QSY Monitor Request for feature

[Uwe, D. <dg...@gm...>]

Hi Scott,

It might be a possibility, but as you have already said, DF is not
specific to the caller. I will forward this to the developer of this
feature though. So, if we display something like this in the QSY Monitor
widget, then only as additional information.

73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm...
Info: www.qrz.com/db/DG2YCB




Am 15.01.2025 um 10:44 schrieb Scott Armstrong:
> Hi Uwe,
>
> I don't think you understand what I am proposing.
> I agree it would be nice if we could use the free form text message to
> convey that information but that is not an option.
>
> What I am proposing does not use the message payload.
>
> I'll try to show you with the following picture/text.  Follow the numbers.
>
> #1. W5ABC has a QSO with me.
> #2  AA5AM sends a QSY message to W5ABC and he receives it. Pop up
> window opens. Message appears in the QSY Monitor window.
>
>  Imagine a crowded band,  lots of signals. Who is the message from
> where do I point my antenna?
>
> Now for my proposal to determine who the message is from.
>
> #3 Take the DF of the received QSY Message.
> #4 Compare the DF of the QSY Message with the DF of previous decodes
> and try to match one or more that are within maybe +/- 2Hz.   ( DF QSY
> = DF QSO decode(s))
> #5  DFs match!  Oh. The message is from AA5AM.
> # 6. Add AA5AM  to the Pop up window and QSY monitor window.
>
>
> Thoughts?
>
> 73,
> Scott AA5AM
>
> image.png
>
> On Wed, Jan 15, 2025 at 2:31 AM Uwe, DG2YCB <dg...@gm...> wrote:
>
>     Hi Scott,
>
>     I agree this would be useful, but unfortunately this is not
>     possible for technical reasons. We use normal freetext messages
>     for the new message system, and already make full use of the 13
>     characters available.
>
>     73 de DG2YCB,
>     Uwe
>     ________________________________________
>     German Amateur Radio Station DG2YCB
>     Dr. Uwe Risse
>     eMail: dg...@gm...
>     Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB>
>
>
>
>
>     Am 15.01.2025 um 01:27 schrieb Scott Armstrong via wsjt-devel:
>>     Hey Guys,
>>
>>     Small issue.   If I receive a QSY message from someone, I have no
>>     idea who sent that message other than trying to track down
>>     the  station by his DF and that is only good if he hasn't moved.
>>     This will not work so well on a busy band in the heat of the contest.
>>
>>     I could  blindly QSY to that band but in the case of a band with
>>     highly directional antennas, where do I aim the antenna? Not as
>>     much of an issue on the lower bands but could still be a problem.
>>
>>     This is what I see displayed in the QSY monitor window. It
>>     doesn't even show the DF the message came in at.
>>
>>     image.png
>>
>>
>>     I have a request,
>>
>>     Can some functionality be added that will take the DF of the QSY
>>     message and match that to the DF maybe within +/- a few Hz to
>>     other prior decodes, pull the callsign of that station that sent
>>     the message and display that callsign in the QSY monitor window?
>>
>>     Thank you and 73,
>>     Scott AA5AM
>>
>>
>>     _______________________________________________
>>     wsjt-devel mailing list
>>     wsj...@li...
>>     https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Message Creator/QSY Monitor Request for feature

[Scott A. <aa5...@gm...>]

Hi Uwe,

I don't think you understand what I am proposing.
I agree it would be nice if we could use the free form text message to
convey that information but that is not an option.

What I am proposing does not use the message payload.

I'll try to show you with the following picture/text.  Follow the numbers.

#1. W5ABC has a QSO with me.
#2  AA5AM sends a QSY message to W5ABC and he receives it. Pop up window
opens. Message appears in the QSY Monitor window.

 Imagine a crowded band,  lots of signals. Who is the message from where
do I point my antenna?

Now for my proposal to determine who the message is from.

#3 Take the DF of the received QSY Message.
#4 Compare the DF of the QSY Message with the DF of previous decodes and
try to match one or more that are within maybe +/- 2Hz.   ( DF QSY = DF QSO
decode(s))
#5  DFs match!  Oh. The message is from AA5AM.
# 6. Add AA5AM  to the Pop up window and QSY monitor window.


Thoughts?

73,
Scott AA5AM

[image: image.png]

On Wed, Jan 15, 2025 at 2:31 AM Uwe, DG2YCB <dg...@gm...> wrote:

> Hi Scott,
>
> I agree this would be useful, but unfortunately this is not possible for
> technical reasons. We use normal freetext messages for the new message
> system, and already make full use of the 13 characters available.
>
> 73 de DG2YCB,
> Uwe
> ________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail: dg...@gm...
> Info: www.qrz.com/db/DG2YCB
>
>
>
>
> Am 15.01.2025 um 01:27 schrieb Scott Armstrong via wsjt-devel:
>
> Hey Guys,
>
> Small issue.   If I receive a QSY message from someone, I have no idea who
> sent that message other than trying to track down the  station by his DF
> and that is only good if he hasn't moved.
> This will not work so well on a busy band in the heat of the contest.
>
> I could  blindly QSY to that band but in the case of a band with highly
> directional antennas, where do I aim the antenna? Not as much of an issue
> on the lower bands but could still be a problem.
>
> This is what I see displayed in the QSY monitor window. It doesn't even
> show the DF the message came in at.
>
> [image: image.png]
>
>
> I have a request,
>
> Can some functionality be added that will take the DF of the QSY message
> and match that to the DF maybe within +/- a few Hz to other prior decodes,
> pull the callsign of that station that sent the message and display that
> callsign in the QSY monitor window?
>
> Thank you and 73,
> Scott AA5AM
>
>
> _______________________________________________
> wsjt-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>

Re: [wsjt-devel] Message Creator/QSY Monitor Request for feature

[Uwe, D. <dg...@gm...>]

Hi Scott,

I agree this would be useful, but unfortunately this is not possible for
technical reasons. We use normal freetext messages for the new message
system, and already make full use of the 13 characters available.

73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm...
Info: www.qrz.com/db/DG2YCB




Am 15.01.2025 um 01:27 schrieb Scott Armstrong via wsjt-devel:
> Hey Guys,
>
> Small issue.   If I receive a QSY message from someone, I have no idea
> who sent that message other than trying to track down the  station by
> his DF and that is only good if he hasn't moved.
> This will not work so well on a busy band in the heat of the contest.
>
> I could  blindly QSY to that band but in the case of a band with
> highly directional antennas, where do I aim the antenna? Not as much
> of an issue on the lower bands but could still be a problem.
>
> This is what I see displayed in the QSY monitor window. It doesn't
> even show the DF the message came in at.
>
> image.png
>
>
> I have a request,
>
> Can some functionality be added that will take the DF of the QSY
> message and match that to the DF maybe within +/- a few Hz to other
> prior decodes, pull the callsign of that station that sent the message
> and display that callsign in the QSY monitor window?
>
> Thank you and 73,
> Scott AA5AM
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Message Creator/QSY Monitor Request for feature

[Scott A. <aa5...@gm...>]

Hey Guys,

Small issue.   If I receive a QSY message from someone, I have no idea who
sent that message other than trying to track down the  station by his DF
and that is only good if he hasn't moved.
This will not work so well on a busy band in the heat of the contest.

I could  blindly QSY to that band but in the case of a band with highly
directional antennas, where do I aim the antenna? Not as much of an issue
on the lower bands but could still be a problem.

This is what I see displayed in the QSY monitor window. It doesn't even
show the DF the message came in at.

[image: image.png]


I have a request,

Can some functionality be added that will take the DF of the QSY message
and match that to the DF maybe within +/- a few Hz to other prior decodes,
pull the callsign of that station that sent the message and display that
callsign in the QSY monitor window?

Thank you and 73,
Scott AA5AM

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Marco C. <PY...@ou...>]

I agree with you Sam, WB6RJH.

Attackers nowadays are so dangerously skilled, that potentially can infect every OS.

The point is that Windowa is (most likely) still the most used OS in the world, for this reason is the most attacked too.

73 de PY1ZRJ

Inviato da Outlook per Android<https://aka.ms/AAb9ysg>
________________________________
From: Sam Sjogren via wsjt-devel <wsj...@li...>
Sent: Tuesday, January 14, 2025 3:57:30 PM
To: DG2YCB <DG...@gm...>
Cc: Sam Sjogren <wb...@gm...>; WSJT software development <wsj...@li...>
Subject: Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

Uwe et.al<http://et.al>.,

Thank you for submitting the files to Microsoft. I've not encountered a false positive like this before, I will know what to do in the future. And I appreciate your reassurance in the preventative measures in place. I'll check again in a few days after the virus signature files get update. Btw, I note that Firefox doesn't flag the download as infected even though Chrome does.

As for comments from others, I don't think that OSes other than Windows are inherently completely secure (note the XZ compression library breach, just for one case) nor do I think it generally is a good idea to turn off virus protection. As for me, I'm retired from development, including security software, and am just going to flag these sorts of warnings (and in the future submit the cases to Microsoft).  I do use various other operating systems, but for a lot of use cases Windows does the job that I want it to even if those systems are outnumbered by Linux and macOS systems for other uses and users in my home/lab technomenagerie.

73,
-Sam
 WB6RJH

On Tue, Jan 14, 2025 at 9:08 AM DG2YCB <DG...@gm...<mailto:DG...@gm...>> wrote:
Hi Sam and all,

Today I sent all four RC8 Windows 64-bit installation files (WSJT-X and wsjt-x_improved) to Microsoft for analysis. Last time it took about 3 days for the files to be confirmed as virus-free and for the virus scanner signature to be updated. But once again: You can (and should) do this yourself in such cases. The installers I have created have never contained any viruses. My computer is strictly monitored in this respect; and SourceForge also tests every file again.

73 de DG2YCB,
Uwe
_________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: DG...@gm...<mailto:DG...@gm...>
Info: www.qrz.com/db/DG2YCB<http://www.qrz.com/db/DG2YCB>



Am 14. Januar 2025 05:41:37 schrieb Sam Sjogren via wsjt-devel <wsj...@li...<mailto:wsj...@li...>>:

Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from SourceForge on a Win10 system. Chrome said a virus was detected. A Windows Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and said "This program is dangerous and executes commands from an attacker."

--
73,
-Sam
 WB6RJH

_______________________________________________
wsjt-devel mailing list
wsj...@li...<mailto:wsjt-devel%40lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




--
73,
-Sam
 WB6RJH

Re: [wsjt-devel] Workaround if RC8 crashes or cannot be started

[Andreas J. <an...@n6...>]

That worked for me!

Thanks.

73, Andreas, N6NU


> On Jan 10, 2025, at 1:36 PM, Charles Suckling via wsjt-devel <wsj...@li...> wrote:
> 
> https://sourceforge.net/projects/wsjt-x-improved/
> 
> On Fri, 10 Jan 2025 at 22:03, Andreas Junge via wsjt-devel <wsj...@li... <mailto:wsj...@li...>> wrote:
>> Hi all,
>> 
>> Maybe if I have to ask, I don’t deserve the answer, but where do I find the dev releases? :-)
>> 
>> Thanks es 73,
>> 
>> Andreas, N6NU
>> 
>>> On Jan 10, 2025, at 10:50 AM, John L. Broughton via wsjt-devel <wsj...@li... <mailto:wsj...@li...>> wrote:
>>> 
>>> I found it. It is under the View menu at the top of the window.
>>> 
>>> 73,
>>> John, WB9VGJ
>>> John L. Broughton
>>> 2si...@gm... <mailto:2si...@gm...>
>>> www.wb9vgj.us <http://www.wb9vgj.us/>
>>> 
>>> On 1/9/2025 10:43 PM, Alan McDonald via wsjt-devel wrote:
>>>> A bit of context would help Charlie,
>>>> Where is that check box?
>>>>  
>>>> <image001.png>
>>>>  
>>>> Alan McDonald
>>>>  
>>>> From: Charles Suckling via wsjt-devel <wsj...@li...> <mailto:wsj...@li...>
>>>> Sent: Friday, 10 January 2025 3:55 PM
>>>> To: WSJT software development <wsj...@li...> <mailto:wsj...@li...>
>>>> Cc: Charles Suckling <g3...@gm...> <mailto:g3...@gm...>
>>>> Subject: Re: [wsjt-devel] Workaround if RC8 crashes or cannot be started
>>>>  
>>>> John
>>>>  
>>>> Its this that Uwe was referring to:
>>>>  
>>>> <image002.png>
>>>>  
>>>> 73
>>>>  
>>>> Charlie DL3WDG
>>>>  
>>>> On Fri, 10 Jan 2025 at 03:07, John L. Broughton via wsjt-devel <wsj...@li... <mailto:wsj...@li...>> wrote:
>>>> I downloaded v2.7.0-rc8 e183d4 a few days ago and I do not find an "Enable QSY Popups" option on any menu page. 73, John, WB9VGJ 
>>>> John L. Broughton
>>>> 2si...@gm... <mailto:2si...@gm...>
>>>> www.wb9vgj.us <http://www.wb9vgj.us/>
>>>>  
>>>> 
>>>> On 1/8/2025 10:21 AM, Brian Morrison via wsjt-devel wrote:
>>>> On Wed, 8 Jan 2025 17:50:13 +0100
>>>> "Uwe, DG2YCB via wsjt-devel" <wsj...@li...> <mailto:wsj...@li...> wrote:
>>>>  
>>>> Hi all,
>>>>  
>>>> We have just found out that the problems encountered by some users of
>>>> RC8, i.e. that the program cannot be started or crashes in individual
>>>> cases, only occur when “Enable QSY Popups” is switched off. We are
>>>> working on finding the root cause.
>>>>  
>>>> But this results in the following workaround: *Leave “Enable QSY
>>>> Popups” switched on*. This should prevent the error.
>>>> It's "Enable Message Popups" in the menu (well it is here using the
>>>> improved version) just in case anyone struggles to find the setting.
>>>>  
>>>>  
>>>>  
>>>> <~WRD0000.jpg> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>	
>>>> Virus-free.www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>> _______________________________________________
>>>> wsjt-devel mailing list
>>>> wsj...@li... <mailto:wsj...@li...>
>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> wsjt-devel mailing list
>>>> wsj...@li... <mailto:wsj...@li...>
>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>> 
>>> _______________________________________________
>>> wsjt-devel mailing list
>>> wsj...@li... <mailto:wsj...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> 
>> _______________________________________________
>> wsjt-devel mailing list
>> wsj...@li... <mailto:wsj...@li...>
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Sam S. <wb...@gm...>]

Uwe et.al.,

Thank you for submitting the files to Microsoft. I've not encountered a
false positive like this before, I will know what to do in the future. And
I appreciate your reassurance in the preventative measures in place. I'll
check again in a few days after the virus signature files get update. Btw,
I note that Firefox doesn't flag the download as infected even though
Chrome does.

As for comments from others, I don't think that OSes other than Windows are
inherently completely secure (note the XZ compression library breach, just
for one case) nor do I think it generally is a good idea to turn off virus
protection. As for me, I'm retired from development, including security
software, and am just going to flag these sorts of warnings (and in the
future submit the cases to Microsoft).  I do use various other operating
systems, but for a lot of use cases Windows does the job that I want it to
even if those systems are outnumbered by Linux and macOS systems for other
uses and users in my home/lab technomenagerie.

73,
-Sam
 WB6RJH

On Tue, Jan 14, 2025 at 9:08 AM DG2YCB <DG...@gm...> wrote:

> Hi Sam and all,
>
> Today I sent all four RC8 Windows 64-bit installation files (WSJT-X and
> wsjt-x_improved) to Microsoft for analysis. Last time it took about 3 days
> for the files to be confirmed as virus-free and for the virus scanner
> signature to be updated. But once again: You can (and should) do this
> yourself in such cases. The installers I have created have never contained
> any viruses. My computer is strictly monitored in this respect; and
> SourceForge also tests every file again.
>
> 73 de DG2YCB,
> Uwe
> _________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail: DG...@gm...
> Info: www.qrz.com/db/DG2YCB
>
>
> Am 14. Januar 2025 05:41:37 schrieb Sam Sjogren via wsjt-devel <
> wsj...@li...>:
>
>> Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from
>> SourceForge on a Win10 system. Chrome said a virus was detected. A Windows
>> Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and
>> said "This program is dangerous and executes commands from an attacker."
>>
>> --
>> 73,
>> -Sam
>>  WB6RJH
>>
>> _______________________________________________
>> wsjt-devel mailing list
>> wsj...@li...
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>>
>

-- 
73,
-Sam
 WB6RJH

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[<k2...@co...>]

Answered my own question.  I renamed the WSJT-X folder and then installed the RC8 version as new.  This time the install went as expected and all is well.
 
73, Russ – K2TXB
W2DRZ Controllers, LLC.
 
 
From: k2txb--- via wsjt-devel <wsj...@li...> 
Sent: Tuesday, January 14, 2025 7:41 AM
To: 'WSJT software development' <wsj...@li...>
Cc: k2...@co...
Subject: Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe
 
I had / have the same problem.  By turning off all virus protection I was finally able to download RC8.  But when trying to install, it gives me a error “Error opening file for writing:  C:\WSJT\wsjts\bin\Qt5Core.dll”
 
I checked and the file is there and not read-only.  I tried this twice with two different browsers with identical results (Chrome and Edge).
 
Any ideas???
 
73, Russ – K2TXB
 
 
 
From: Charles Suckling via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > 
Sent: Tuesday, January 14, 2025 12:28 AM
To: WSJT software development <wsj...@li... <mailto:wsj...@li...> >
Cc: Charles Suckling <g3...@gm... <mailto:g3...@gm...> >
Subject: Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe
 
Adding to Mike's comment, I suggest looking at this article.  Note the recommendation to submit the file (or URL) for further analysis by your AV provider. 
 
https://learn.microsoft.com/en-us/defender-endpoint/defender-endpoint-false-positives-negatives
 
73
 
Charlie DL3WDG
 
 
 
 
 
On Tue, 14 Jan 2025 at 06:06, Adrian via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > wrote:
That is devastating, let us all beware !
On 14/1/25 14:40, Sam Sjogren via wsjt-devel wrote:
Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from SourceForge on a Win10 system. Chrome said a virus was detected. A Windows Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and said "This program is dangerous and executes commands from an attacker."
 
-- 
73,
-Sam
 WB6RJH
 
_______________________________________________
wsjt-devel mailing list
wsj...@li... <mailto:wsj...@li...> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsj...@li... <mailto:wsj...@li...> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[DG2YCB <DG...@gm...>]

Hi Sam and all,

Today I sent all four RC8 Windows 64-bit installation files (WSJT-X and
wsjt-x_improved) to Microsoft for analysis. Last time it took about 3 days
for the files to be confirmed as virus-free and for the virus scanner
signature to be updated. But once again: You can (and should) do this
yourself in such cases. The installers I have created have never contained
any viruses. My computer is strictly monitored in this respect; and
SourceForge also tests every file again.

73 de DG2YCB,
Uwe
_________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: DG...@gm...
Info: www.qrz.com/db/DG2YCB

Am 14. Januar 2025 05:41:37 schrieb Sam Sjogren via wsjt-devel
<wsj...@li...>:
> Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from
> SourceForge on a Win10 system. Chrome said a virus was detected. A Windows
> Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and
> said "This program is dangerous and executes commands from an attacker."
>
> --
> 73,
> -Sam
> WB6RJH
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Marco C. <PY...@ou...>]

Yes, I see.

But he received already the answers he needs: mostly false positive warning by Windows antivirus.

Regards,

PY1ZRJ



Inviato da Outlook per Android<https://aka.ms/AAb9ysg>
________________________________
From: Hasan N0AN via wsjt-devel <wsj...@li...>
Sent: Tuesday, January 14, 2025 10:37:54 AM
To: WSJT software development <wsj...@li...>
Cc: Hasan N0AN <hba...@gm...>
Subject: Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

Please, don't turn this into a Linux vs Windows debate, it's off topic. He needs help with Windows, not Linux.

Hasan


On Tue, Jan 14, 2025 at 7:23 AM Doug Breault, Sr. via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> wrote:

Ditto. Too much drama on Windows. When I was using Windows, I used to get viruses all the time until I turned off all the "virus protection".

Windows is the CNN of the OS world.

On Tue, Jan 14, 2025, 8:13 AM Marco Calistri via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> wrote:
This is one of the several reasons that I prefer to use Linux and not Windows.

73 de PY1ZRJ

Inviato da Outlook per Android<https://aka.ms/AAb9ysg>
________________________________
From: Sam Sjogren via wsjt-devel <wsj...@li...<mailto:wsj...@li...>>
Sent: Tuesday, January 14, 2025 1:40:18 AM
To: wsj...@li...<mailto:wsj...@li...> <wsj...@li...<mailto:wsj...@li...>>
Cc: Sam Sjogren <wb...@gm...<mailto:wb...@gm...>>
Subject: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from SourceForge on a Win10 system. Chrome said a virus was detected. A Windows Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and said "This program is dangerous and executes commands from an attacker."

--
73,
-Sam
 WB6RJH

_______________________________________________
wsjt-devel mailing list
wsj...@li...<mailto:wsj...@li...>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsj...@li...<mailto:wsj...@li...>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Hasan N. <hba...@gm...>]

Please, don't turn this into a Linux vs Windows debate, it's off topic. He
needs help with Windows, not Linux.

Hasan


On Tue, Jan 14, 2025 at 7:23 AM Doug Breault, Sr. via wsjt-devel <
wsj...@li...> wrote:

> Ditto. Too much drama on Windows. When I was using Windows, I used to get
> viruses all the time until I turned off all the "virus protection".
>
> Windows is the CNN of the OS world.
>
> On Tue, Jan 14, 2025, 8:13 AM Marco Calistri via wsjt-devel <
> wsj...@li...> wrote:
>
>> This is one of the several reasons that I prefer to use Linux and not
>> Windows.
>>
>> 73 de PY1ZRJ
>>
>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg>
>> ------------------------------
>> *From:* Sam Sjogren via wsjt-devel <wsj...@li...>
>> *Sent:* Tuesday, January 14, 2025 1:40:18 AM
>> *To:* wsj...@li... <wsj...@li...>
>> *Cc:* Sam Sjogren <wb...@gm...>
>> *Subject:* [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe
>>
>> Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from
>> SourceForge on a Win10 system. Chrome said a virus was detected. A Windows
>> Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and
>> said "This program is dangerous and executes commands from an attacker."
>>
>> --
>> 73,
>> -Sam
>>  WB6RJH
>>
>> _______________________________________________
>> wsjt-devel mailing list
>> wsj...@li...
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Doug B. Sr. <dou...@gm...>]

Ditto. Too much drama on Windows. When I was using Windows, I used to get
viruses all the time until I turned off all the "virus protection".

Windows is the CNN of the OS world.

On Tue, Jan 14, 2025, 8:13 AM Marco Calistri via wsjt-devel <
wsj...@li...> wrote:

> This is one of the several reasons that I prefer to use Linux and not
> Windows.
>
> 73 de PY1ZRJ
>
> Inviato da Outlook per Android <https://aka.ms/AAb9ysg>
> ------------------------------
> *From:* Sam Sjogren via wsjt-devel <wsj...@li...>
> *Sent:* Tuesday, January 14, 2025 1:40:18 AM
> *To:* wsj...@li... <wsj...@li...>
> *Cc:* Sam Sjogren <wb...@gm...>
> *Subject:* [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe
>
> Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from
> SourceForge on a Win10 system. Chrome said a virus was detected. A Windows
> Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and
> said "This program is dangerous and executes commands from an attacker."
>
> --
> 73,
> -Sam
>  WB6RJH
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Marco C. <PY...@ou...>]

This is one of the several reasons that I prefer to use Linux and not Windows.

73 de PY1ZRJ

Inviato da Outlook per Android<https://aka.ms/AAb9ysg>
________________________________
From: Sam Sjogren via wsjt-devel <wsj...@li...>
Sent: Tuesday, January 14, 2025 1:40:18 AM
To: wsj...@li... <wsj...@li...>
Cc: Sam Sjogren <wb...@gm...>
Subject: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from SourceForge on a Win10 system. Chrome said a virus was detected. A Windows Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and said "This program is dangerous and executes commands from an attacker."

--
73,
-Sam
 WB6RJH

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[<k2...@co...>]

I had / have the same problem.  By turning off all virus protection I was finally able to download RC8.  But when trying to install, it gives me a error “Error opening file for writing:  C:\WSJT\wsjts\bin\Qt5Core.dll”
 
I checked and the file is there and not read-only.  I tried this twice with two different browsers with identical results (Chrome and Edge).
 
Any ideas???
 
73, Russ – K2TXB
 
 
 
From: Charles Suckling via wsjt-devel <wsj...@li...> 
Sent: Tuesday, January 14, 2025 12:28 AM
To: WSJT software development <wsj...@li...>
Cc: Charles Suckling <g3...@gm...>
Subject: Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe
 
Adding to Mike's comment, I suggest looking at this article.  Note the recommendation to submit the file (or URL) for further analysis by your AV provider. 
 
https://learn.microsoft.com/en-us/defender-endpoint/defender-endpoint-false-positives-negatives
 
73
 
Charlie DL3WDG
 
 
 
 
 
On Tue, 14 Jan 2025 at 06:06, Adrian via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > wrote:
That is devastating, let us all beware !
On 14/1/25 14:40, Sam Sjogren via wsjt-devel wrote:
Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from SourceForge on a Win10 system. Chrome said a virus was detected. A Windows Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and said "This program is dangerous and executes commands from an attacker."
 
-- 
73,
-Sam
 WB6RJH
 
_______________________________________________
wsjt-devel mailing list
wsj...@li... <mailto:wsj...@li...> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsj...@li... <mailto:wsj...@li...> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Wolfgang <oe...@gm...>]

Hello Charlie,

by the way, I rely entirely on the Defender in Windows 10 - and it hasn't reported anything. 
So, it was never an issue for me. I only did the uplaod to virustotal because of the message 
from Sam WB6RJH. 
 
As always, “feared to death is also dead” applies here too. Common sense must always be 
taken into account in these matters. We assume and can be sure that the WSJT-X team 
does not produce a virus slingshot. So, these messages are just a coincidental match of the 
same bit-patterns.
 

73 de Wolfgang
OE1MWW
 

Tuesday, January 14, 2025, 9:30:22 AM, you wrote:

> Wolfgang

> Probably your AV tools did not flag a false positive. 

>  If you look at the results from Virus Total, only a few indicate a positive.  And, the ones they find are not the same!  Other programs I use also show the occasional false positive.  

> 73

> Charlie DL3WDG

----------
under construction: https://www.oe1mww.work/

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Reino T. <rei...@ko...>]

Charlie, each virus checked has named the same detection differently. There is no “standard” on the virus names. Only the main functionality can be the same such as Troyan.

 

73, Reino OH3mA

 

From: Charles Suckling via wsjt-devel <wsj...@li...> 
Sent: Tuesday, January 14, 2025 10:30 AM
To: Wolfgang <oe...@gm...>; WSJT software development <wsj...@li...>
Cc: Charles Suckling <g3...@gm...>
Subject: Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

 

Wolfgang

 

Probably your AV tools did not flag a false positive. 

 

 If you look at the results from Virus Total, only a few indicate a positive.  And, the ones they find are not the same!  Other programs I use also show the occasional false positive.  

 

73

 

Charlie DL3WDG

 

 

 

On Tue, 14 Jan 2025 at 08:43, Wolfgang via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > wrote:

Yes, unfortunately... all of the RC8 files,  std. or 'improved' giving Virus entries, checked at https://www.virustotal.com/gui/home/upload

 

Btw., my Firefox during download and Windows 10 Defender during installation and operation did not give any alarm... strange (?)

 

73 de Wolfgang

OE1MWW

 

 

 

Tuesday, January 14, 2025, 5:40:18 AM, you wrote:

 

Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from SourceForge on a Win10 system. Chrome said a virus was detected. A Windows Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and said "This program is dangerous and executes commands from an attacker."

 

-- 

73,

-Sam

 WB6RJH

 

 

----------

under construction: https://www.oe1mww.work/

_______________________________________________
wsjt-devel mailing list
wsj...@li... <mailto:wsj...@li...> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Reino T. <rei...@ko...>]

Wolfgang, it seems that Firefox learns quite fast that a file safe or a virus detection is false. Now using it I don’t get any download warnings on wsjt-x rc8 or rc8 improved.

 

73, Reino OH3mA

 

From: Wolfgang via wsjt-devel <wsj...@li...> 
Sent: Tuesday, January 14, 2025 9:39 AM
To: WSJT software development <wsj...@li...>
Cc: Wolfgang <oe...@gm...>
Subject: Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

 

Yes, unfortunately... all of the RC8 files,  std. or 'improved' giving Virus entries, checked at https://www.virustotal.com/gui/home/upload

 

Btw., my Firefox during download and Windows 10 Defender during installation and operation did not give any alarm... strange (?)

 

73 de Wolfgang

OE1MWW

 

 

 

Tuesday, January 14, 2025, 5:40:18 AM, you wrote:

 

Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from SourceForge on a Win10 system. Chrome said a virus was detected. A Windows Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and said "This program is dangerous and executes commands from an attacker."

 

-- 

73,

-Sam

 WB6RJH

 

 

----------

under construction: https://www.oe1mww.work/

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Charles S. <g3...@gm...>]

Wolfgang

Probably your AV tools did not flag a false positive.

 If you look at the results from Virus Total, only a few indicate a
positive.  And, the ones they find are not the same!  Other programs I use
also show the occasional false positive.

73

Charlie DL3WDG



On Tue, 14 Jan 2025 at 08:43, Wolfgang via wsjt-devel <
wsj...@li...> wrote:

> Yes, unfortunately... all of the RC8 files,  std. or 'improved' giving
> Virus entries, checked at https://www.virustotal.com/gui/home/upload
>
>
>
> Btw., my Firefox during download and Windows 10 Defender during
> installation and operation did not give any alarm... strange (?)
>
>
>
> 73 de Wolfgang
>
> OE1MWW
>
>
>
>
>
> Tuesday, January 14, 2025, 5:40:18 AM, you wrote:
>
>
> Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from
> SourceForge on a Win10 system. Chrome said a virus was detected. A Windows
> Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and
> said "This program is dangerous and executes commands from an attacker."
>
> --
> 73,
> -Sam
>  WB6RJH
>
>
>
> ----------
>
> under construction: https://www.oe1mww.work/
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Wolfgang <oe...@gm...>]

Yes, unfortunately... all of the RC8 files,  std. or 'improved' giving Virus entries, checked at https://www.virustotal.com/gui/home/upload
 
Btw., my Firefox during download and Windows 10 Defender during installation and operation did not give any alarm... strange (?)
 
73 de Wolfgang
OE1MWW
 


Tuesday, January 14, 2025, 5:40:18 AM, you wrote:

> Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from SourceForge on a Win10 system. Chrome said a virus was detected. A Windows Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and said "This program is dangerous and executes commands from an attacker."


----------
under construction: https://www.oe1mww.work/

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Charles S. <g3...@gm...>]

Adding to Mike's comment, I suggest looking at this article.  Note the
recommendation to submit the file (or URL) for further analysis by your AV
provider.

https://learn.microsoft.com/en-us/defender-endpoint/defender-endpoint-false-positives-negatives

73

Charlie DL3WDG





On Tue, 14 Jan 2025 at 06:06, Adrian via wsjt-devel <
wsj...@li...> wrote:

> That is devastating, let us all beware !
> On 14/1/25 14:40, Sam Sjogren via wsjt-devel wrote:
>
> Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from
> SourceForge on a Win10 system. Chrome said a virus was detected. A Windows
> Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and
> said "This program is dangerous and executes commands from an attacker."
>
> --
> 73,
> -Sam
>  WB6RJH
>
>
>
> _______________________________________________
> wsjt-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Black M. <mdb...@ya...>]

It's not devastating...it's a false alarm.

Mike W9MDB







On Monday, January 13, 2025 at 11:06:18 PM CST, Adrian via wsjt-devel <wsj...@li...> wrote: 






That is devastating, let us all beware !


On 14/1/25 14:40, Sam Sjogren via wsjt-devel wrote:


>  

Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from SourceForge on a Win10 system. Chrome said a virus was detected. A Windows Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and said "This program is dangerous and executes commands from an attacker."



-- 




73,

-Sam

 WB6RJH










_______________________________________________
wsjt-devel mailing list
wsj...@li...
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

_______________________________________________
wsjt-devel mailing list
wsj...@li...
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Adrian <vk...@gm...>]

That is devastating, let us all beware !

On 14/1/25 14:40, Sam Sjogren via wsjt-devel wrote:
> Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from 
> SourceForge on a Win10 system. Chrome said a virus was detected. A 
> Windows Defender scan showed the file infected 
> with Trojan:Win32/Wacatac.B!ml and said "This program is dangerous and 
> executes commands from an attacker."
>
> -- 
> 73,
> -Sam
>  WB6RJH
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] virus found in wsjtx-2.7.0-rc8-win64.exe

[Sam S. <wb...@gm...>]

Earlier this evening I downloaded wsjtx-2.7.0-rc8-win64.exe from
SourceForge on a Win10 system. Chrome said a virus was detected. A Windows
Defender scan showed the file infected with Trojan:Win32/Wacatac.B!ml and
said "This program is dangerous and executes commands from an attacker."

-- 
73,
-Sam
 WB6RJH

[wsjt-devel] FYI: Re: Release Candidate WSJT-X 2.7.0-rc8

[John B. <2si...@gm...>]

Bruce,

Some information on new WSJT-X function.

The QSY Monitor and Enable Message Popups are in the View menu. The 
Enable Message Popups should always be on.

I have some comments on the Texas v. Ohio State game for tomorrow.

73,
John

-- 
John L. Broughton
wb...@ar...
2si...@gm...
www.wb9vgj.us



On 1/6/2025 1:03 PM, Marco Calistri via wsjt-devel wrote:
> Il 06/01/25 10:33, Joe Taylor via wsjt-devel ha scritto:
>> Dear WSJT-X Users,
>>
>> We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc8 is
>> ready for download and use by beta testers. This revision introduces a
>> new Message System primarily intended for contests. Otherwise, RC8 is
>> mostly a bug-fix release of the well-functioning RC7.
>>
>> The WSJT-X Message System can be used to invite your QSO partner to QSY
>> to another frequency or mode (e.g. during contests), or to send some
>> general short messages. It consists of the Message Creator and the QSY
>> Monitor. Received messages are displayed as popups. To understand how to
>> use the Message System, be sure to read Section 8 of the updated WSJT-X
>> User Guide for RC8.
>>
>> Additional details on program changes since RC7 can be found in the
>> Release Notes:
>> https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.7.0-rc8.txt
>>
>> Release Candidates are intended for beta testers. If you download and
>> use WSJT-X 2.7.0-rc8, please provide relevant feedback on the new
>> features and anything that does not seem to work properly for you. If
>> your report involves something related to received signals, be sure to
>> provide one or more saved *.wav files that illustrate the perceived
>> problem. As a general matter, you should use the option "Save all" when
>> testing.
>>
>> Direct links to installation packages for Windows, Linux, and macOS can
>> be found on the WSJT-X page https://wsjt.sourceforge.io/wsjtx.html
>> Scroll down to the heading "Candidate release: WSJT-X 2.7.0-rc8".
>>
>> For those who like to compile from source, a source-code tarball is
>> available on the WSJT-X page.
>>
>> WSJT-X is licensed under the terms of Version 3 of the GNU General
>> Public License (GPL). Development of this software is a cooperative
>> project to which many amateur radio operators have contributed. If you
>> use our code, please have the courtesy to let us know about it. If you
>> find bugs or make improvements to the code, please report them to us in
>> a timely fashion.
>>
>> The authors and Copyright holders of WSJT-X request that derivative
>> works should not publish programs based on features in WSJT-X before
>> those features are made available in a General Availability (GA) release
>> of WSJT-X. Currently this caution applies to all SuperFox and SuperHound
>> features. We will cease making public Release Candidates if this request
>> is ignored.
>>
>> Feedback should be sent to this email list or one of the of the others
>> mentioned here in the User Guide:
>> https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc8.html#SUPPORT
>>
>> We hope you will enjoy using WSJT-X 2.7.0-rc8, and that you will help us
>> to create a new General Availability (GA) release soon.
>>
>>       -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG2YCB;
>>               Brian, N9ADG; John, G4KLA; and Charlie, DL3WDG.
>>
>>
>> _______________________________________________
>> wsjt-devel mailing list
>> wsj...@li...
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> Thanks to all the people that works behind this software!
>
> Happy new year and plenty of DX!
>
> ---
> *73 de Marco, PY1ZRJ (former IK5BCU)*
> **
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com