Menu
▾
▴
wsjt-devel — WSJT software development
You can subscribe to this list here.
| 2007 |
Jan
(30) |
Feb
|
Mar
(10) |
Apr
(60) |
May
(62) |
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(10) |
Oct
(17) |
Nov
(1) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
(21) |
Mar
(4) |
Apr
(15) |
May
(37) |
Jun
(98) |
Jul
(120) |
Aug
(1) |
Sep
(14) |
Oct
|
Nov
(31) |
Dec
(8) |
| 2009 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(25) |
May
(88) |
Jun
(5) |
Jul
(31) |
Aug
(25) |
Sep
(4) |
Oct
(19) |
Nov
(119) |
Dec
(11) |
| 2010 |
Jan
(3) |
Feb
(19) |
Mar
(4) |
Apr
|
May
(7) |
Jun
(17) |
Jul
|
Aug
(4) |
Sep
(20) |
Oct
(3) |
Nov
(29) |
Dec
(86) |
| 2011 |
Jan
(6) |
Feb
|
Mar
(6) |
Apr
(8) |
May
(1) |
Jun
(12) |
Jul
(9) |
Aug
(4) |
Sep
(7) |
Oct
(9) |
Nov
|
Dec
(1) |
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
(5) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(10) |
Feb
(7) |
Mar
(4) |
Apr
(76) |
May
(66) |
Jun
(101) |
Jul
(210) |
Aug
(255) |
Sep
(83) |
Oct
(18) |
Nov
(3) |
Dec
(3) |
| 2014 |
Jan
(187) |
Feb
(139) |
Mar
(99) |
Apr
(173) |
May
(106) |
Jun
(61) |
Jul
(50) |
Aug
(66) |
Sep
(342) |
Oct
(238) |
Nov
(251) |
Dec
(189) |
| 2015 |
Jan
(96) |
Feb
(295) |
Mar
(260) |
Apr
(271) |
May
(358) |
Jun
(531) |
Jul
(311) |
Aug
(231) |
Sep
(267) |
Oct
(219) |
Nov
(452) |
Dec
(390) |
| 2016 |
Jan
(367) |
Feb
(128) |
Mar
(208) |
Apr
(308) |
May
(237) |
Jun
(272) |
Jul
(90) |
Aug
(289) |
Sep
(153) |
Oct
(214) |
Nov
(167) |
Dec
(282) |
| 2017 |
Jan
(194) |
Feb
(173) |
Mar
(267) |
Apr
(102) |
May
(39) |
Jun
(201) |
Jul
(1064) |
Aug
(363) |
Sep
(383) |
Oct
(289) |
Nov
(237) |
Dec
(185) |
| 2018 |
Jan
(175) |
Feb
(198) |
Mar
(489) |
Apr
(222) |
May
(414) |
Jun
(297) |
Jul
(329) |
Aug
(136) |
Sep
(383) |
Oct
(590) |
Nov
(834) |
Dec
(1114) |
| 2019 |
Jan
(425) |
Feb
(177) |
Mar
(319) |
Apr
(515) |
May
(337) |
Jun
(447) |
Jul
(525) |
Aug
(252) |
Sep
(119) |
Oct
(108) |
Nov
(211) |
Dec
(228) |
| 2020 |
Jan
(158) |
Feb
(141) |
Mar
(94) |
Apr
(99) |
May
(545) |
Jun
(470) |
Jul
(211) |
Aug
(142) |
Sep
(181) |
Oct
(128) |
Nov
(219) |
Dec
(213) |
| 2021 |
Jan
(243) |
Feb
(514) |
Mar
(279) |
Apr
(101) |
May
(97) |
Jun
(259) |
Jul
(164) |
Aug
(205) |
Sep
(149) |
Oct
(301) |
Nov
(139) |
Dec
(159) |
| 2022 |
Jan
(116) |
Feb
(70) |
Mar
(63) |
Apr
(46) |
May
(50) |
Jun
(114) |
Jul
(173) |
Aug
(106) |
Sep
(127) |
Oct
(65) |
Nov
(117) |
Dec
(102) |
| 2023 |
Jan
(139) |
Feb
(99) |
Mar
(52) |
Apr
(132) |
May
(238) |
Jun
(75) |
Jul
(91) |
Aug
(25) |
Sep
(36) |
Oct
(64) |
Nov
(45) |
Dec
(91) |
| 2024 |
Jan
(156) |
Feb
(56) |
Mar
(30) |
Apr
(16) |
May
(40) |
Jun
(53) |
Jul
(327) |
Aug
(171) |
Sep
(67) |
Oct
(53) |
Nov
(43) |
Dec
(78) |
| 2025 |
Jan
(112) |
Feb
(27) |
Mar
(46) |
Apr
(49) |
May
(58) |
Jun
(54) |
Jul
(42) |
Aug
(8) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Lee B. <kx...@ya...> - 2025-06-01 02:07:51
|
GM Marco, I think the phrase "No news is good news" applies here. Keep the faith! 73 de Lee KX4TT Hello, I'm feeling kind of premonition that WSJT-X could has reached its End Of Life? I don't see many messages here on the mailing-list from some time, and this is not a good sign for me. Of course I hope that my feelings being wrong, but I would like to know better from someone that has the answer. Thanks! --- 73 de Marco, PY1ZRJ (former IK5BCU) --- 73 de Marco, PY1ZRJ (former IK5BCU) _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Marco C. <PY...@ou...> - 2025-06-01 01:56:10
|
Hi Joe, Very *glad* to see your resolute answer! Thanks! Marco, PY1ZRJ Il 31/05/25 22:06, Joseph Taylor ha scritto: > Marco -- > > Your feelings are very wrong. > > — 73, Joe, K1JT > ------------------------------------------------------------------------ > *From:* Marco Calistri via wsjt-devel <wsj...@li...> > *Sent:* Saturday, May 31, 2025 8:07 PM > *To:* 'WSJT software development' <wsj...@li...> > *Cc:* Marco Calistri <PY...@ou...> > *Subject:* [wsjt-devel] WSJT-X - E.O.L.? > Hello, > > I'm feeling kind of premonition that WSJT-X could has reached its End > Of Life? > > I don't see many messages here on the mailing-list from some time, and > this is not a good sign for me. > > Of course I hope that my feelings being wrong, but I would like to > know better from someone that has the answer. > > Thanks! > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Lance C. W. <w7...@bi...> - 2025-06-01 01:48:25
|
Hi Marco, I am not sure why you are asking your question. Q65-60A with Q65 Pileup option is now the standard mode used worldwide for 6m EME, and other Q65 modes are widely used on other EME bands. In addition, FT8 mode continues to be the favored mode on 6m and many HF bands, because of its great sensitivity. WSJT-X has revolutionized amateur radio, and has made challenging things like 6m EME DXpeditions POSSIBLE! MNI MNI thanks to K1JT and the entire WSJT-X team! VY 73, Lance On 6/1/2025 00:07:38, Marco Calistri via wsjt-devel wrote: > Hello, > > I'm feeling kind of premonition that WSJT-X could has reached its End Of Life? > > I don't see many messages here on the mailing-list from some time, and this is not > a good sign for me. > > Of course I hope that my feelings being wrong, but I would like to know better from > someone that has the answer. > > Thanks! > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, FO/W7GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ, H40GJ) P.O. Box 73 Frenchtown, MT 59834-0073 USA TEL: (406) 626-5728 QTH: DN27ub URL: http://www.bigskyspaces.com/w7gj Skype: lanceW7GJ 2m DXCC #11 - 6m DXCC #815 - FFMA #7 Interested in 6m EME? Ask me about subscribing to the new Magic Band EME email group, or just fill in the request box at the bottom of my web page (above)! |
|
From: Marco C. <PY...@ou...> - 2025-06-01 00:23:10
|
Hello, I'm feeling kind of premonition that WSJT-X could has reached its End Of Life? I don't see many messages here on the mailing-list from some time, and this is not a good sign for me. Of course I hope that my feelings being wrong, but I would like to know better from someone that has the answer. Thanks! --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Glenn W. <af...@al...> - 2025-05-31 03:15:48
|
I was inspired to "get with the program" (pun intended) to ask for opinions on the 6-second jump problem. The way I did that was to ask https://grok.com/ (Artificial Intelligence) some questions about system time and WSJT-X. In one of the requests I accidentally hit the Enter key too soon but what Grok came back with was many pages of good critique. Not bad by itself. All three critiques are in https://hamfaqs.com/wsjtx/ to prevent having that much email here. Non-programmers will be happy about that. -Glenn, AF8C On 5/25/2025 8:23 AM, Glenn Williams via wsjt-devel wrote: > Evidence: > 1 Linux time is always correct and advances monotonically. > 2 Restarting WSJT-X for WSPR fixes the problem. > 3 No one has mentioned this about WSJT-X running, for example, FT8. (?) > 4 But does this happen on machines that run different motherboards and > or processors (i.e. Intel vs AMD vs ARM)? At least we know that it > happens with different flavors of Linux. > > Conclusions: > 1 Inside the WSPR code there is a (let's call it) "register" that has > been informed of Linux time at the start of WSJT-X execution. > 2 Guess: Perhaps the register does not contain enough bits for holding > Linux time and when the register reaches maximum count it overflows and > resets to 000000... (But time jumping ahead does not agree with > this prediction because a reset would be backwards.) > 3 The delta of 6 seconds is a clue to how many counts are missed at the > least significant bits end of the register. > 4 In the code someone left out a CONST declaration. Etc. > 5 It's a fixable bug. > 6 WSPR code was at least partially written by someone different from the > other code(s) so that declarations of variables are different. > 7 Or it's caused by some other "bug". A family tree of possible bugs > is larger than what I am imagining. See 5. > 8 I am probably be wrong again. :) > > I could subscribe to the Digest. But maybe I don't want that much email. > > --Glenn, AF8C > > On 5/24/2025 5:26 PM, Paul Simon via wsjt-devel wrote: >> On 5/23/2025 9:16 AM, Josh Rovero via wsjt-devel wrote: >>> I see similar behavior about every 72 hours or so on Fedora Core 41, >>> 64-bit. >>> >>> Restarting wsjtx seems to cure it for another 72 hours .. >>> >>> Josh Rovero >>> KK1D >>> >> >> ------------------------------------------ >>> >>> I have been running wspr 24/7 using the linux version of wsjtx. >>> After >>> about two days, dt seems to increase by 6 seconds, in a single jump, >>> not >>> gradually. This does not happen on Windows. >>> >>> 1. The same happens on two different machines running Ubuntu and >>> Mageia,v 2.61 and v 2.7.0-rc8. >>> >>> 2. Computer clock is correct: checked vs. time.is <http://time.is>, >>> NIST controlled >>> clock, etc. Time measured manually is within one second. >>> >>> 3. Closing and reopening wsjtx immediately results in correct dt. >>> >>> 4. Running wsjtx under WINE gives same result. >>> >>> 5. Waterfall timing is correct and can see the six second early >>> start of >>> sequence. >>> >>> 6. Only happens if transmit box is ticked. >>> >>> Could someone please confirm and/or suggest possible solutions? >>> >>> Paul W6EXT >>> >> >> --------------- >> Well, good luck Josh. No response from anyone else. No developers >> either. Some of the links on the SourceForge pages are dead. One of >> the SourceForge pages states that WSPR is of historical interest. >> >> >> "So Long, and Thanks for All the Fish" >> >> Paul, W6...@ar... >> >> >> >> >> >> >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > -- This email has been checked for viruses by Avast antivirus software. www.avast.com |
|
From: Paul S. <ps...@so...> - 2025-05-29 19:59:00
|
Hello Reino, Thanks very much following up. I will do my best to answer your questions. Feel free to ask for more clarification as needed. Number 5. I am not sure whether or not I saw both rx and tx early on the waterfall. I will have to wait and look again. I do know that the 6 second early dt shows up in the station received list. I have seen the delay but not sure if it was one or the other or both rx and tx. I took a look at wspr.live and could not really figure out how to use to check my own transmitted signal. I’m very familiar with using databases and did some consulting after I retired, but the whole interface to wspr.live is not clear to me. The advantage would be I could see the dt received by other stations. I don’t know how they get it as it is not sent to wspr.net. I was hoping that someone else would hear my signal and be able to report the dt to me. I don’t know if you can hear me on wspr. I run only 500 mw but could easily raise it. The xmit power is quite accurate I believe as I am using an LP-100a to set it. Number 6. I’m not quite sure I understand you question. I can only record dt on received signals and it is not on wspr.net. There are horizontal lines on the waterfall on the even minutes with the band displayed at the left. Those lines are timed correctly with respect to the system clock, but the sequences I receive (and transmit?) are not. Again, I don’t know if it is only rx or tx but the early start is clearly visible on the waterfall. I don’t know much about FST4W. Is it rx only from particular beacons? I still would need to get dt from both tx and rx. Finally, I am pretty sure this is a software bug. It is as if there is a variable/register that accumulates dt offsets and at six seconds adds a shift of six seconds to the received dt. I would not be surprised if it added another six seconds after another two days. I’m not that good a programmer to dig into wsjtx, besides I am 86 and would rather spend the time doing other things. Thanks again and 73 Paul |
|
From: Marco C. <PY...@ou...> - 2025-05-27 10:14:18
|
Hi Reino, list! I need to correct my previous message, since I have been able to hear my CW-ID when using MSK144 mode. Then this feature is still working on latest WSJTX version! So far so good 😊 73 de Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ Da: Marco Calistri via wsjt-devel <wsj...@li...> Inviato: Mercoledì, Maggio 14, 2025 12:09:27 PM A: WSJT software development <wsj...@li...> Cc: Marco Calistri <PY...@ou...> Oggetto: Re: [wsjt-devel] FW: CW-ID is not being sent That's all right Reino! The inconvenience is that here I wasn't able to notice my CW-ID emission, despite of the several settings I have tried. Best regards! Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Reino Talarmo via wsjt-devel <wsj...@li...> Sent: Wednesday, May 14, 2025 2:41:43 AM To: 'WSJT software development' <wsj...@li...> Cc: Reino Talarmo <rei...@ko...> Subject: [wsjt-devel] FW: CW-ID is not being sent Hello Maco! Of course there are no global “correct” parameter values. User Guide sets the T/R to 15 s, but any value would work except the same T/R value and the same Tx even/1st value and then both stations would send and receive at the same timeslots! The CW ID is really a matter of local regulations. E.g. in Finland we don’t need to send it at all as the monitoring station could decode MSK144 at a short range better than any CW, typically no human listening needed. The same with FT8. In many regions 10 minutes is set in the regulations and so the CW ID should be set to 10 and possibly activate the ‘CW ID after 73’ as it could be the last transmission. The CW ID is intended for a strong signal identification and your QSO partner normally would not hear it, just short pings. For the regulation purposes the CW ID is working as it should. For QSO point of view it may steal your ‘73’ if you send it only once and you are using T/R 5s. 73, Reino OH3mA From: Marco Calistri <PY...@ou...<mailto:PY...@ou...>> Sent: Tuesday, May 13, 2025 10:23 PM To: Reino Talarmo <rei...@ko...<mailto:rei...@ko...>>; 'WSJT software development' <wsj...@li...<mailto:wsj...@li...>> Subject: Re: [wsjt-devel] CW-ID is not being sent Hello Reino! Thanks for the time you spent for the tests! The main issues, IMHO are: what are the correct parameters both for the CW id time interval and the MSK T/R seconds? Since it's not much worth that CW-ID being working only with few parameters combination that we can't use for normal MSK144 mode. For example here in Brazil the T/R is normally set to 30 s. Best regards, Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Reino Talarmo <rei...@ko...<mailto:rei...@ko...>> Sent: Tuesday, May 13, 2025 4:04:51 PM To: PY...@ou...<mailto:PY...@ou...> <PY...@ou...<mailto:PY...@ou...>>; 'WSJT software development' <wsj...@li...<mailto:wsj...@li...>> Subject: RE: [wsjt-devel] CW-ID is not being sent Hi Marco, I set up v2.7.0 GA (latest version) and selected in General the CW ID interwall to ‘1’. I listened to the audio and there is my CW id once a minute! When I set T/R to 5 s, then the CW ID replaces the first MSK144 transmission. When the T/R period is longer, then the last 5 s of the transmission is replaced. If I also select CW ID after 73, then the last 5 s of the ‘73’ message is stolen for the CW ID. The once a minute CW ID transmission may not be the first time of the minute. At least with 10 s T/R sends it at 45 seconds mark. At T/R 5 s the whole ‘73’ message is stolen and no ’73’ is sent (may be a bug). The CW ID seems to work. 73, Reino OH3mA From: Marco Calistri via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> Sent: Tuesday, May 13, 2025 12:25 AM To: wsj...@li...<mailto:wsj...@li...> Cc: Marco Calistri <PY...@ou...<mailto:PY...@ou...>> Subject: Re: [wsjt-devel] CW-ID is not being sent Hi Andy! In reality I was asking in general the correct usage of CW-ID, which at least here it seems is not working. Then I would like to get the confirmation about it. Best regards, Marco, PY1ZRJ |
|
From: Reino T. <rei...@ko...> - 2025-05-27 08:40:59
|
Paul, Thanks for detailed answers to the questions. May I ask further clarification what's happening. You said earlier: "5. Waterfall timing is correct and can see the six second early start of sequence." Do you mean early start of the transmission sequence? Can you still decode other transmissions after that instance? I try to figure out whether only the transmission timing is starting too early or both transmission and reception. Do you see your transmissions on wspr.live? I am not used it myself and could not spot W6EXT at all but may be my fault. You could use it to monitor your transmissions. "6. Only happens if transmit box is ticked." That may be an answer, but are also receptions stepped six seconds? I assume not as you say that the waterfall timing is correct. I mean also after the instance. By the way FST4W beacon mode is more advanced than WSPR providing 1.8 dB better performance in 120 s sub-mode. It also can send all information in a single message. For some reason on some bands WSPR is still used more than FST4W. Perhaps the reason is a bit more complex waveform of the 4-GFSK with smooth frequency transitions requiring a bit more complex frequency controls of frequency synthesizers. 73, Reino OH3mA |
|
From: Joseph T. <jo...@Pr...> - 2025-05-27 03:24:04
|
Hi Nico, WSJT-X has no way of knowing that you disabled a second screen. But the "missing" window is still alive. It may be visible in your system tray, and can be moved from there manually. — Joe, K1JT ________________________________ From: nico--- via wsjt-devel <wsj...@li...> Sent: Monday, May 26, 2025 1:49 PM Cc: ni...@pa... <ni...@pa...>; wsj...@li... <wsj...@li...> Subject: [wsjt-devel] Astronomical data on second screen Hello, Previously sent from the wrong email address, sorry It's not a big problem but I want to mention it anyway. Sometimes I park wsjt-x on a second screen. When that screen is no longer connected wsjt-x starts normally but the position of Astronomical data remains on the 2nd screen and is therefore no longer visible. Version 2.7.0 OS Windows 10 Kind regards, Nico PA3ESH |
|
From: Paul S. <ps...@so...> - 2025-05-26 19:38:47
|
Gentlemen, Thank you all for your responses. To move this along, my responses: Alan G0TLK Linux time jumps: From what I have Googled, the magnitudes are very large and seem to be reversible. Also, the system time stays correct, and the horizontal line separating two minute sequences is always at the correct time. Restarting WSPR periodically might work except that ticking the transmit button turns off at the second sequence after startup. Another bug. I think finding the bug is more important and your suggestion would work if the above bug were also solved. Comment 3. Has problem arisen running FT8? Not as far as I know. I got one response from Josh, KK1D, who wrote that he observed similar behavior every 72 hours on Fedora Core 41, 64 bit. Restarting runs another 72 hours. Comment 4. Does this happen on machines with different motherboards and/or different processors? Yes, it does. Josh’s comment as well as I have run it with a HP laptop and my own, Intel Core i7-8700, ASUS Z370 mb and 16 Gb memory. Glen, AF8C Yes, I agree. I think there is a register/variable that overflows at some point. Perhaps the six seconds, is the +/- limit for decoding and at some cumulative point it does a six second shift. If this is the case, the register should reset at some point and not continue to accumulate and “overflow” so to speak. Nic, G3YEG Memory leak problem? See above. It could be but the bug would have to found before we could make that conclusion. Reino, OH3MA Yes, as far I have tested, it is a Linux only problem. It does not appear on my windows laptop. The transmission is not continuous, about 30 per cent. I can only tell on receive as that is the only place I can see DT. Perhaps someone could check me at their QTH. WSPR is currently running on windows, so no error. The error occurs with band hopping as well as on one band only. I hope our suggestions can lead to a solution. There is another minor bug that I have found but we can discuss it another time. WSPR seems to be the orphan of WSJTX. Paul, W6EXT |
|
From: <ni...@pa...> - 2025-05-26 18:21:38
|
Hello, Previously sent from the wrong email address, sorry It's not a big problem but I want to mention it anyway. Sometimes I park wsjt-x on a second screen. When that screen is no longer connected wsjt-x starts normally but the position of Astronomical data remains on the 2nd screen and is therefore no longer visible. Version 2.7.0 OS Windows 10 Kind regards, Nico PA3ESH |
|
From: Reino T. <rei...@ko...> - 2025-05-26 05:46:49
|
Welcome Nic to the discussion. The program is an open source one and all information is available for you to study it to the bottom. As far as I have noted it is a Linux related problem. At least: “Message: 1 Date: Thu, 22 May 2025 15:31:13 -0700 From: Paul Simon <mailto:ps...@so...> To: mailto:wsj...@li... Subject: [wsjt-devel] wsjtx wspr#dt error Message-ID: <100o8jh$ju5$mailto:1...@ci...> Content-Type: text/plain; charset=UTF-8; format=flowed I have been running wspr 24/7 using the linux version of wsjtx. After about two days, dt seems to increase by 6 seconds, in a single jump, not gradually. This does not happen on Windows." States so. I have not seen any details how WSPR is set for transmission, see user guide (10.) WSPR Mode. E.g. is the transmission continuous or is there also reception periods, and is a Band Hopping used or just a single band? With your expertise it would nice, if you could spend some time for a study session about the "memory leak" assumption. 73, Reino OH3mA |
|
From: Doug B. Sr. <dou...@gm...> - 2025-05-25 21:41:16
|
Not sure if this is a red herring but maybe another piece of data for you guys: I was just running Linux Mint and the latest Wsjtx and after my phone died, which had a hotspot the laptop was using, my Rx seemed to get really bad. I couldn't see many signals and couldn't make any more QSOs. Then an operator from Arizona wrote to me and said my clock was off by 2 seconds (or more?). Never had that happen before, at least, no one has ever told me my clock was off. Note, it was an old laptop, and an old ICOM 706, and the battery was almost dead on the laptop also. Probably just one of those battery related issues or something, but the clock being off seemed atypical, empirically speaking. HTH, 73 Doug KC1UUH On Sun, May 25, 2025, 3:01 PM Nic Sears via wsjt-devel < wsj...@li...> wrote: > Could it be a memory leak type of problem? > > Nic G3YEG - ex comms programmer/ debug specialist > > On 25 May 2025 13:23, Glenn Williams via wsjt-devel < > wsj...@li...> wrote: > > Evidence: > 1 Linux time is always correct and advances monotonically. > 2 Restarting WSJT-X for WSPR fixes the problem. > 3 No one has mentioned this about WSJT-X running, for example, FT8. (?) > 4 But does this happen on machines that run different motherboards and > or processors (i.e. Intel vs AMD vs ARM)? At least we know that it > happens with different flavors of Linux. > > Conclusions: > 1 Inside the WSPR code there is a (let's call it) "register" that has > been informed of Linux time at the start of WSJT-X execution. > 2 Guess: Perhaps the register does not contain enough bits for holding > Linux time and when the register reaches maximum count it overflows and > resets to 000000... (But time jumping ahead does not agree with > this prediction because a reset would be backwards.) > 3 The delta of 6 seconds is a clue to how many counts are missed at the > least significant bits end of the register. > 4 In the code someone left out a CONST declaration. Etc. > 5 It's a fixable bug. > 6 WSPR code was at least partially written by someone different from the > other code(s) so that declarations of variables are different. > 7 Or it's caused by some other "bug". A family tree of possible bugs > is larger than what I am imagining. See 5. > 8 I am probably be wrong again. :) > > I could subscribe to the Digest. But maybe I don't want that much email. > > --Glenn, AF8C > > On 5/24/2025 5:26 PM, Paul Simon via wsjt-devel wrote: > > On 5/23/2025 9:16 AM, Josh Rovero via wsjt-devel wrote: > >> I see similar behavior about every 72 hours or so on Fedora Core 41, > >> 64-bit. > >> > >> Restarting wsjtx seems to cure it for another 72 hours .. > >> > >> Josh Rovero > >> KK1D > >> > > > > ------------------------------------------ > >> > >> I have been running wspr 24/7 using the linux version of wsjtx. > >> After > >> about two days, dt seems to increase by 6 seconds, in a single jump, > >> not > >> gradually. This does not happen on Windows. > >> > >> 1. The same happens on two different machines running Ubuntu and > >> Mageia,v 2.61 and v 2.7.0-rc8. > >> > >> 2. Computer clock is correct: checked vs. time.is <http://time.is>, > >> NIST controlled > >> clock, etc. Time measured manually is within one second. > >> > >> 3. Closing and reopening wsjtx immediately results in correct dt. > >> > >> 4. Running wsjtx under WINE gives same result. > >> > >> 5. Waterfall timing is correct and can see the six second early > >> start of > >> sequence. > >> > >> 6. Only happens if transmit box is ticked. > >> > >> Could someone please confirm and/or suggest possible solutions? > >> > >> Paul W6EXT > >> > > > > --------------- > > Well, good luck Josh. No response from anyone else. No developers > > either. Some of the links on the SourceForge pages are dead. One of the > > SourceForge pages states that WSPR is of historical interest. > > > > > > "So Long, and Thanks for All the Fish" > > > > Paul, W6...@ar... > > > > > > > > > > > > > > > > > > _______________________________________________ > > wsjt-devel mailing list > > wsj...@li... > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > -- > This email has been checked for viruses by Avast antivirus software. > www.avast.com > > _______________________________________________ > 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 > |
|
From: Nic S. <nic...@ta...> - 2025-05-25 18:56:22
|
<div dir='auto'>Could it be a memory leak type of problem? <div dir="auto"><br></div><div dir="auto">Nic G3YEG - ex comms programmer/ debug specialist</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 25 May 2025 13:23, Glenn Williams via wsjt-devel <wsj...@li...> wrote:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Evidence:<br> 1 Linux time is always correct and advances monotonically.<br> 2 Restarting WSJT-X for WSPR fixes the problem.<br> 3 No one has mentioned this about WSJT-X running, for example, FT8. (?)<br> 4 But does this happen on machines that run different motherboards and<br> or processors (i.e. Intel vs AMD vs ARM)? At least we know that it <br> happens with different flavors of Linux.</p> <p dir="ltr">Conclusions:<br> 1 Inside the WSPR code there is a (let's call it) "register" that has<br> been informed of Linux time at the start of WSJT-X execution.<br> 2 Guess: Perhaps the register does not contain enough bits for holding <br> Linux time and when the register reaches maximum count it overflows and<br> resets to 000000... (But time jumping ahead does not agree with<br> this prediction because a reset would be backwards.)<br> 3 The delta of 6 seconds is a clue to how many counts are missed at the<br> least significant bits end of the register.<br> 4 In the code someone left out a CONST declaration. Etc.<br> 5 It's a fixable bug.<br> 6 WSPR code was at least partially written by someone different from the<br> other code(s) so that declarations of variables are different.<br> 7 Or it's caused by some other "bug". A family tree of possible bugs<br> is larger than what I am imagining. See 5.<br> 8 I am probably be wrong again. :)</p> <p dir="ltr">I could subscribe to the Digest. But maybe I don't want that much email.</p> <p dir="ltr">--Glenn, AF8C</p> <p dir="ltr">On 5/24/2025 5:26 PM, Paul Simon via wsjt-devel wrote:<br> > On 5/23/2025 9:16 AM, Josh Rovero via wsjt-devel wrote:<br> >> I see similar behavior about every 72 hours or so on Fedora Core 41, <br> >> 64-bit.<br> >><br> >> Restarting wsjtx seems to cure it for another 72 hours ..<br> >><br> >> Josh Rovero<br> >> KK1D<br> >><br> > <br> > ------------------------------------------<br> >><br> >>     I have been running wspr 24/7 using the linux version of wsjtx. <br> >> After<br> >>     about two days, dt seems to increase by 6 seconds, in a single jump,<br> >>     not<br> >>     gradually.  This does not happen on Windows.<br> >><br> >>     1. The same happens on two different machines running Ubuntu and<br> >>     Mageia,v 2.61 and v 2.7.0-rc8.<br> >><br> >>     2. Computer clock is correct: checked vs. time.is <http://time.is>,<br> >>     NIST controlled<br> >>     clock, etc.  Time measured manually is within one second.<br> >><br> >>     3. Closing and reopening wsjtx immediately results in correct dt.<br> >><br> >>     4. Running wsjtx under WINE gives same result.<br> >><br> >>     5. Waterfall timing is correct and can see the six second early<br> >>     start of<br> >>     sequence.<br> >><br> >>     6. Only happens if transmit box is ticked.<br> >><br> >>     Could someone please confirm and/or suggest possible solutions?<br> >><br> >>     Paul W6EXT<br> >><br> > <br> > ---------------<br> > Well, good luck Josh.  No response from anyone else. No developers <br> > either. Some of the links on the SourceForge pages are dead.  One of the <br> > SourceForge pages states that WSPR is of historical interest.<br> > <br> > <br> > "So Long, and Thanks for All the Fish"<br> > <br> > Paul, W6...@ar...<br> > <br> > <br> > <br> > <br> > <br> > <br> > <br> > <br> > _______________________________________________<br> > wsjt-devel mailing list<br> > wsj...@li...<br> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel<br></p> <p dir="ltr">-- <br> This email has been checked for viruses by Avast antivirus software.<br> www.avast.com<br></p> <p dir="ltr">_______________________________________________<br> wsjt-devel mailing list<br> wsj...@li...<br> https://lists.sourceforge.net/lists/listinfo/wsjt-devel<br> </p> </blockquote></div><br></div> |
|
From: Glenn W. <af...@al...> - 2025-05-25 16:57:29
|
Evidence: 1 Linux time is always correct and advances monotonically. 2 Restarting WSJT-X for WSPR fixes the problem. 3 No one has mentioned this about WSJT-X running, for example, FT8. (?) 4 But does this happen on machines that run different motherboards and or processors (i.e. Intel vs AMD vs ARM)? At least we know that it happens with different flavors of Linux. Conclusions: 1 Inside the WSPR code there is a (let's call it) "register" that has been informed of Linux time at the start of WSJT-X execution. 2 Guess: Perhaps the register does not contain enough bits for holding Linux time and when the register reaches maximum count it overflows and resets to 000000... (But time jumping ahead does not agree with this prediction because a reset would be backwards.) 3 The delta of 6 seconds is a clue to how many counts are missed at the least significant bits end of the register. 4 In the code someone left out a CONST declaration. Etc. 5 It's a fixable bug. 6 WSPR code was at least partially written by someone different from the other code(s) so that declarations of variables are different. 7 Or it's caused by some other "bug". A family tree of possible bugs is larger than what I am imagining. See 5. 8 I am probably be wrong again. :) I could subscribe to the Digest. But maybe I don't want that much email. --Glenn, AF8C On 5/24/2025 5:26 PM, Paul Simon via wsjt-devel wrote: > On 5/23/2025 9:16 AM, Josh Rovero via wsjt-devel wrote: >> I see similar behavior about every 72 hours or so on Fedora Core 41, >> 64-bit. >> >> Restarting wsjtx seems to cure it for another 72 hours .. >> >> Josh Rovero >> KK1D >> > > ------------------------------------------ >> >> I have been running wspr 24/7 using the linux version of wsjtx. >> After >> about two days, dt seems to increase by 6 seconds, in a single jump, >> not >> gradually. This does not happen on Windows. >> >> 1. The same happens on two different machines running Ubuntu and >> Mageia,v 2.61 and v 2.7.0-rc8. >> >> 2. Computer clock is correct: checked vs. time.is <http://time.is>, >> NIST controlled >> clock, etc. Time measured manually is within one second. >> >> 3. Closing and reopening wsjtx immediately results in correct dt. >> >> 4. Running wsjtx under WINE gives same result. >> >> 5. Waterfall timing is correct and can see the six second early >> start of >> sequence. >> >> 6. Only happens if transmit box is ticked. >> >> Could someone please confirm and/or suggest possible solutions? >> >> Paul W6EXT >> > > --------------- > Well, good luck Josh. No response from anyone else. No developers > either. Some of the links on the SourceForge pages are dead. One of the > SourceForge pages states that WSPR is of historical interest. > > > "So Long, and Thanks for All the Fish" > > Paul, W6...@ar... > > > > > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- This email has been checked for viruses by Avast antivirus software. www.avast.com |
|
From: <al...@al...> - 2025-05-25 10:54:01
|
I don't at the moment use Linux but there's quite a number of search results on "linux time jump" that seem to indicate this might perhaps be something to do with the way Linux uses time? Maybe you need to write some kind of script to restart WSJT-X at regular intervals? Alan G0TLK On 24/05/2025 22:26, Paul Simon via wsjt-devel wrote: > On 5/23/2025 9:16 AM, Josh Rovero via wsjt-devel wrote: >> I see similar behavior about every 72 hours or so on Fedora Core 41, >> 64-bit. >> >> Restarting wsjtx seems to cure it for another 72 hours .. >> >> Josh Rovero >> KK1D >> > > ------------------------------------------ >> >> I have been running wspr 24/7 using the linux version of wsjtx. >> After >> about two days, dt seems to increase by 6 seconds, in a single jump, >> not >> gradually. This does not happen on Windows. >> >> 1. The same happens on two different machines running Ubuntu and >> Mageia,v 2.61 and v 2.7.0-rc8. >> >> 2. Computer clock is correct: checked vs. time.is <http://time.is>, >> NIST controlled >> clock, etc. Time measured manually is within one second. >> >> 3. Closing and reopening wsjtx immediately results in correct dt. >> >> 4. Running wsjtx under WINE gives same result. >> >> 5. Waterfall timing is correct and can see the six second early >> start of >> sequence. >> >> 6. Only happens if transmit box is ticked. >> >> Could someone please confirm and/or suggest possible solutions? >> >> Paul W6EXT >> > > --------------- > Well, good luck Josh. No response from anyone else. No developers > either. Some of the links on the SourceForge pages are dead. One of > the SourceForge pages states that WSPR is of historical interest. > > > "So Long, and Thanks for All the Fish" > > Paul, W6...@ar... > > > > > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Paul S. <ps...@so...> - 2025-05-24 21:32:32
|
On 5/23/2025 9:16 AM, Josh Rovero via wsjt-devel wrote: > I see similar behavior about every 72 hours or so on Fedora Core 41, 64-bit. > > Restarting wsjtx seems to cure it for another 72 hours .. > > Josh Rovero > KK1D > ------------------------------------------ > > I have been running wspr 24/7 using the linux version of wsjtx. After > about two days, dt seems to increase by 6 seconds, in a single jump, > not > gradually. This does not happen on Windows. > > 1. The same happens on two different machines running Ubuntu and > Mageia,v 2.61 and v 2.7.0-rc8. > > 2. Computer clock is correct: checked vs. time.is <http://time.is>, > NIST controlled > clock, etc. Time measured manually is within one second. > > 3. Closing and reopening wsjtx immediately results in correct dt. > > 4. Running wsjtx under WINE gives same result. > > 5. Waterfall timing is correct and can see the six second early > start of > sequence. > > 6. Only happens if transmit box is ticked. > > Could someone please confirm and/or suggest possible solutions? > > Paul W6EXT > --------------- Well, good luck Josh. No response from anyone else. No developers either. Some of the links on the SourceForge pages are dead. One of the SourceForge pages states that WSPR is of historical interest. "So Long, and Thanks for All the Fish" Paul, W6...@ar... |
|
From: Josh R. <jos...@gm...> - 2025-05-23 16:17:06
|
I see similar behavior about every 72 hours or so on Fedora Core 41, 64-bit. Restarting wsjtx seems to cure it for another 72 hours .. Josh Rovero KK1D On Fri, May 23, 2025, 08:57 <wsj...@li...> wrote: > Send wsjt-devel mailing list submissions to > wsj...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > or, via email, send a message with subject or body 'help' to > wsj...@li... > > You can reach the person managing the list at > wsj...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of wsjt-devel digest..." > > > Today's Topics: > > 1. wsjtx wspr#dt error (Paul Simon) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 22 May 2025 15:31:13 -0700 > From: Paul Simon <ps...@so...> > To: wsj...@li... > Subject: [wsjt-devel] wsjtx wspr#dt error > Message-ID: <100o8jh$ju5$1...@ci...> > Content-Type: text/plain; charset=UTF-8; format=flowed > > I have been running wspr 24/7 using the linux version of wsjtx. After > about two days, dt seems to increase by 6 seconds, in a single jump, not > gradually. This does not happen on Windows. > > 1. The same happens on two different machines running Ubuntu and > Mageia,v 2.61 and v 2.7.0-rc8. > > 2. Computer clock is correct: checked vs. time.is, NIST controlled > clock, etc. Time measured manually is within one second. > > 3. Closing and reopening wsjtx immediately results in correct dt. > > 4. Running wsjtx under WINE gives same result. > > 5. Waterfall timing is correct and can see the six second early start of > sequence. > > 6. Only happens if transmit box is ticked. > > Could someone please confirm and/or suggest possible solutions? > > Paul W6EXT > > > > > ------------------------------ > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > ------------------------------ > > End of wsjt-devel Digest, Vol 135, Issue 32 > ******************************************* > |
|
From: Paul S. <ps...@so...> - 2025-05-22 22:31:31
|
I have been running wspr 24/7 using the linux version of wsjtx. After about two days, dt seems to increase by 6 seconds, in a single jump, not gradually. This does not happen on Windows. 1. The same happens on two different machines running Ubuntu and Mageia,v 2.61 and v 2.7.0-rc8. 2. Computer clock is correct: checked vs. time.is, NIST controlled clock, etc. Time measured manually is within one second. 3. Closing and reopening wsjtx immediately results in correct dt. 4. Running wsjtx under WINE gives same result. 5. Waterfall timing is correct and can see the six second early start of sequence. 6. Only happens if transmit box is ticked. Could someone please confirm and/or suggest possible solutions? Paul W6EXT |
|
From: Nic S. <nic...@ta...> - 2025-05-18 06:40:16
|
<div dir='auto'>Ok thanks uwe</div><div class="gmail_extra"><br><div class="gmail_quote">On 17 May 2025 22:32, DG2YCB via wsjt-devel <wsj...@li...> wrote:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div> <div dir="auto"> <div dir="auto">Hi Nic,</div><div dir="auto"><br /></div><div dir="auto">It is enough to submit the URL to Norton:</div><div dir="auto"><a href="https://submit.norton.com/">https://submit.norton.com/</a></div><div dir="auto"><br /></div><div dir="auto" style="color:black"><div dir="auto">73 de DG2YCB,</div><div dir="auto">Uwe</div><div dir="auto">_________________________________________</div><div dir="auto">German Amateur Radio Station DG2YCB</div><div dir="auto">Dr. Uwe Risse</div><div dir="auto">eMail: DG2YCB@gmx.de</div><div dir="auto">Info: <a href="http://www.qrz.com/db/DG2YCB">www.qrz.com/db/DG2YCB</a></div><div dir="auto"><br /></div></div><div dir="auto"><br /></div> <div style="color:black"> <div> <div style="color:black"> <p style="color:black;font-size:10pt;font-family:sans-serif;margin:8pt 0">Am 16. Mai 2025 18:09:46 schrieb Nic Sears via wsjt-devel <wsjt-devel@lists.sourceforge.net>:</p> <blockquote style="margin:0 0 0 0.75ex;border-left:1px solid #808080;padding-left:0.75ex"> <p>Hi Uwe,</p> <p>Nic G3YEG here.</p> <p>When I downloaded the windows plus 250501.exe using the link below - Norton put the file in quarantine as it said it had a virus. F00038D <br /> </p> <p>Any ideas ?</p> <p>73 Nic<br /> </p> <p><br /> </p> <div>On 01/05/2025 01:22, Uwe, DG2YCB via wsjt-devel wrote:<br /> </div> <blockquote> Dear Users,<br /> <br /> I'm glad to announce a "250501" update of WSJT-X Improved 2.8.0, which brings the following improvements:<br /> <br /> In programs QMAP and MAP65:<br /> <ul><li>Introduction of a new "LiveCQ" feature. It allows messages that you decode with QMAP and/or MAP65 to be uploaded automatically via the internet to the new website: <a href="https://w3sz.com/livecq.html">https://w3sz.com/livecq.html</a>. The idea is to provide spots of active EME stations so that others will know where to look. Read <a href="https://wsjt-x-improved.sourceforge.io/wsjtx-main_en.html#_livecq">section 16.14 of the User Guide</a> for more information.<br /> </li><li>Fixed a long-standing flaw in QMAP which could cause the program to crash after a few hours of operation.<br /> </li></ul> <p>In program WSJT-X:</p> <ul><li>The dial frequency can now be controlled via mouse (useful for EME operations, or when a DXpedition is not on the standard DXp QRGs). If you hover the mouse pointer over the frequency display, you have two new options:<br /> </li><li><ul><li>Left-click to decrease the rig dial frequency by 1 kHz, or right-click to increase it by 1 kHz.</li><li>Turn the mouse wheel to scroll the kHz values.</li></ul> </li><li>You can now choose between “worked today” and “worked today or yesterday” for the three respective Hide/Ignore/Highlight Quick Filters. Switching is done via a new checkbox under Settings/Filters.<br /> </li><li>Fixed some inconsistencies around the Tx watchdog. The countdown now only starts when Enable Tx is active (important for Wait & Call).</li><li>Repeated use of the rig (ATU) tuning function now works more reliably.</li><li>Minor bug fixes and performance improvements.</li><li>Slightly more detailed explanations in the WSJT-X Improved <a href="https://wsjt-x-improved.sourceforge.io/wsjtx-main_en.html">User Guide</a>.<br /> </li><li>Update to Hamlib 4.6.2.</li><li>Last not least: The Qt6 source code can now also be compiled with Qt 6.8.x (important for Linux Fedora, etc.).<br /> </li></ul> <div>As usual, you will <a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/"><b>find the downloadable files on my SourceForge page</b></a>. Here are the direct links to download the most important packages:<br /> <ul><li><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_PLUS_250501.exe/download"><strong>wsjtx-2.8.0-win64_improved_PLUS_250501</strong></a><strong><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_PLUS_250501.exe/download">.exe</a> (Windows 64-bit, WSJT-X GUI)</strong></li><li><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_AL_PLUS_250501.exe/download"><strong>wsjtx-2.8.0-win64_improved_AL_PLUS_25</strong><strong>0501</strong></a><strong><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_AL_PLUS_250501.exe/download">.exe</a> (Windows 64-bit, AL GUI)</strong></li><li><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501.exe/download"><strong>wsjtx-</strong><strong>2.8.0-win64</strong><strong>_improved_widescreen_PLUS_25</strong><strong>0501</strong></a><strong><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501.exe/download">.exe</a> (Windows 64-bit, widescreen GUI)</strong></li><li><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_PLUS_250501_amd64.deb/download"><strong>wsjtx_2.8.0_improved_PLUS_</strong><strong>25</strong><strong>0501</strong></a><strong><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_PLUS_250501_amd64.deb/download">_amd64.deb</a> (Linux</strong><strong>, WSJT-X GUI</strong><strong>)</strong></li><li><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_AL_PLUS_250501_amd64.deb/download"><strong>wsjtx_2.8.0_improved_AL_PLUS_</strong><strong>25</strong><strong>0501</strong></a><strong><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_AL_PLUS_250501_amd64.deb/download">_amd64.deb</a> (Linux</strong><strong>, AL GUI</strong><strong>)</strong></li><li><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_Darwin.dmg/download"><strong>wsjtx-2.8.0_improved_PLUS_</strong><strong>25</strong><strong>0501</strong></a><strong><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_Darwin.dmg/download">_Darwin.dmg</a> (macOS x86_64</strong><strong>, WSJT-X GUI</strong><strong>)</strong></li><li><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_M1.zip/download"><strong>wsjtx-2.8.0_improved_PLUS_</strong><strong>25</strong><strong>0501</strong></a><strong><a href="https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_M1.zip/download">_M1.zip</a> (macOS M1</strong><strong>, WSJT-X GUI</strong><strong>)</strong></li></ul> Thanks to everyone who contributed to this great new release!</div> <div><br /> 73 de DG2YCB,<br /> Uwe<br /> ________________________________________<br /> German Amateur Radio Station DG2YCB<br /> Dr. Uwe Risse<br /> eMail: <a href="mailto:dg2ycb@gmx.de">dg2ycb@gmx.de</a><br /> Info: <a href="http://www.qrz.com/db/DG2YCB">www.qrz.com/db/DG2YCB</a><br /> <br /> <br /> </div> <br /> <fieldset></fieldset> <br /> <fieldset></fieldset> <pre>_______________________________________________ wsjt-devel mailing list <a href="mailto:wsjt-devel@lists.sourceforge.net">wsjt-devel@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/wsjt-devel">https://lists.sourceforge.net/lists/listinfo/wsjt-devel</a> </pre> </blockquote> <div>_______________________________________________</div> <div>wsjt-devel mailing list</div> <div><a href="mailto:wsjt-devel%40lists.sourceforge.net">wsjt-devel@lists.sourceforge.net</a></div> <div><a href="https://lists.sourceforge.net/lists/listinfo/wsjt-devel">https://lists.sourceforge.net/lists/listinfo/wsjt-devel</a></div> <div><br /></div></blockquote> </div> </div> </div><div dir="auto"><br /></div> </div></div> </blockquote></div><br></div> |
|
From: Mike L. <k7...@ho...> - 2025-05-17 22:16:46
|
Update: There are 3 Windows versions. If you download the 2nd and 3rd, it seems to not trigger the virus defense (in Defender) and you can keep it per the screenshots I posted below. I then downloaded the 1st version, wsjtx-2.8.0-win64_improved_PLUS_250501.exe, and that one triggered the warning and the download was canceled. You should have received a notification about there being a virus detected. I click on it (or go to it in settings), it opens up the Virus and Protection settings, and I went into Protection History where I expanded the latest one. Then under Actions button, I chose Allow. If you want to avoid this then try downloading the 2nd or 3rd version instead. Also in this process I chose the Report app as Safe option which opens a feedback page online. [cid:image003.png@01DBC73A.0F4E4560] From: Mike Lewis Sent: Saturday, May 17, 2025 2:18 PM To: WSJT software development <wsj...@li...> Cc: Dan Coughlin <hot...@ho...> Subject: RE: [wsjt-devel] v2.8.0 "250501" available For the case of Defender (no Norton), in your browser download status you have the option to keep the file. Click on the 3 dots, select Keep. [cid:image004.png@01DBC73A.0F4E4560] Then you get another trust question dialog, click on Show More and you will see this, choose Keep Anyway. [cid:image005.png@01DBC73A.0F4E4560] From: Dan Coughlin via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> Sent: Saturday, May 17, 2025 1:38 PM To: software development WSJT <wsj...@li...<mailto:wsj...@li...>> Cc: Dan Coughlin <hot...@ho...<mailto:hot...@ho...>> Subject: Re: [wsjt-devel] v2.8.0 "250501" available And Windows just plain deletes it from the downloads folder so the file cannot even be sent to them for checking. Even with all the defender stuff turned off, the file is deleted. Sent from my iPhone On May 16, 2025, at 12:14 PM, Nic Sears via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> wrote: Hi Uwe, Nic G3YEG here. When I downloaded the windows plus 250501.exe using the link below - Norton put the file in quarantine as it said it had a virus. F00038D Any ideas ? 73 Nic On 01/05/2025 01:22, Uwe, DG2YCB via wsjt-devel wrote: Dear Users, I'm glad to announce a "250501" update of WSJT-X Improved 2.8.0, which brings the following improvements: In programs QMAP and MAP65: * Introduction of a new "LiveCQ" feature. It allows messages that you decode with QMAP and/or MAP65 to be uploaded automatically via the internet to the new website: https://w3sz.com/livecq.html. The idea is to provide spots of active EME stations so that others will know where to look. Read section 16.14 of the User Guide<https://wsjt-x-improved.sourceforge.io/wsjtx-main_en.html#_livecq> for more information. * Fixed a long-standing flaw in QMAP which could cause the program to crash after a few hours of operation. In program WSJT-X: * The dial frequency can now be controlled via mouse (useful for EME operations, or when a DXpedition is not on the standard DXp QRGs). If you hover the mouse pointer over the frequency display, you have two new options: * Left-click to decrease the rig dial frequency by 1 kHz, or right-click to increase it by 1 kHz. * Turn the mouse wheel to scroll the kHz values. * You can now choose between “worked today” and “worked today or yesterday” for the three respective Hide/Ignore/Highlight Quick Filters. Switching is done via a new checkbox under Settings/Filters. * Fixed some inconsistencies around the Tx watchdog. The countdown now only starts when Enable Tx is active (important for Wait & Call). * Repeated use of the rig (ATU) tuning function now works more reliably. * Minor bug fixes and performance improvements. * Slightly more detailed explanations in the WSJT-X Improved User Guide<https://wsjt-x-improved.sourceforge.io/wsjtx-main_en.html>. * Update to Hamlib 4.6.2. * Last not least: The Qt6 source code can now also be compiled with Qt 6.8.x (important for Linux Fedora, etc.). As usual, you will find the downloadable files on my SourceForge page<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/>. Here are the direct links to download the most important packages: * wsjtx-2.8.0-win64_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_PLUS_250501.exe/download>.exe<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_PLUS_250501.exe/download> (Windows 64-bit, WSJT-X GUI) * wsjtx-2.8.0-win64_improved_AL_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_AL_PLUS_250501.exe/download>.exe<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_AL_PLUS_250501.exe/download> (Windows 64-bit, AL GUI) * wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501.exe/download>.exe<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501.exe/download> (Windows 64-bit, widescreen GUI) * wsjtx_2.8.0_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_PLUS_250501_amd64.deb/download>_amd64.deb<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_PLUS_250501_amd64.deb/download> (Linux, WSJT-X GUI) * wsjtx_2.8.0_improved_AL_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_AL_PLUS_250501_amd64.deb/download>_amd64.deb<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_AL_PLUS_250501_amd64.deb/download> (Linux, AL GUI) * wsjtx-2.8.0_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_Darwin.dmg/download>_Darwin.dmg<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_Darwin.dmg/download> (macOS x86_64, WSJT-X GUI) * wsjtx-2.8.0_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_M1.zip/download>_M1.zip<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_M1.zip/download> (macOS M1, WSJT-X GUI) Thanks to everyone who contributed to this great new release! 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> _______________________________________________ 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 |
|
From: DG2YCB <DG...@gm...> - 2025-05-17 21:32:55
|
Hi Nic, It is enough to submit the URL to Norton: https://submit.norton.com/ 73 de DG2YCB, Uwe _________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: DG...@gm... Info: www.qrz.com/db/DG2YCB Am 16. Mai 2025 18:09:46 schrieb Nic Sears via wsjt-devel <wsj...@li...>: > Hi Uwe, > Nic G3YEG here. > When I downloaded the windows plus 250501.exe using the link below - Norton > put the file in quarantine as it said it had a virus. F00038D > Any ideas ? > 73 Nic > > On 01/05/2025 01:22, Uwe, DG2YCB via wsjt-devel wrote: >> Dear Users, >> >> I'm glad to announce a "250501" update of WSJT-X Improved 2.8.0, which >> brings the following improvements: >> >> In programs QMAP and MAP65: >> >> Introduction of a new "LiveCQ" feature. It allows messages that you decode >> with QMAP and/or MAP65 to be uploaded automatically via the internet to the >> new website: https://w3sz.com/livecq.html. The idea is to provide spots of >> active EME stations so that others will know where to look. Read section >> 16.14 of the User Guide for more information. >> Fixed a long-standing flaw in QMAP which could cause the program to crash >> after a few hours of operation. >> In program WSJT-X: >> The dial frequency can now be controlled via mouse (useful for EME >> operations, or when a DXpedition is not on the standard DXp QRGs). If you >> hover the mouse pointer over the frequency display, you have two new options: >> Left-click to decrease the rig dial frequency by 1 kHz, or right-click to >> increase it by 1 kHz. >> Turn the mouse wheel to scroll the kHz values. >> You can now choose between “worked today” and “worked today or yesterday” >> for the three respective Hide/Ignore/Highlight Quick Filters. Switching is >> done via a new checkbox under Settings/Filters. >> Fixed some inconsistencies around the Tx watchdog. The countdown now only >> starts when Enable Tx is active (important for Wait & Call). >> Repeated use of the rig (ATU) tuning function now works more reliably. >> Minor bug fixes and performance improvements. >> Slightly more detailed explanations in the WSJT-X Improved User Guide. >> Update to Hamlib 4.6.2. >> Last not least: The Qt6 source code can now also be compiled with Qt 6.8.x >> (important for Linux Fedora, etc.). >> As usual, you will find the downloadable files on my SourceForge page. Here >> are the direct links to download the most important packages: >> >> wsjtx-2.8.0-win64_improved_PLUS_250501.exe (Windows 64-bit, WSJT-X GUI) >> wsjtx-2.8.0-win64_improved_AL_PLUS_250501.exe (Windows 64-bit, AL GUI) >> wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501.exe (Windows 64-bit, >> widescreen GUI) >> wsjtx_2.8.0_improved_PLUS_250501_amd64.deb (Linux, WSJT-X GUI) >> wsjtx_2.8.0_improved_AL_PLUS_250501_amd64.deb (Linux, AL GUI) >> wsjtx-2.8.0_improved_PLUS_250501_Darwin.dmg (macOS x86_64, WSJT-X GUI) >> wsjtx-2.8.0_improved_PLUS_250501_M1.zip (macOS M1, WSJT-X GUI) >> Thanks to everyone who contributed to this great new release! >> 73 de DG2YCB, >> Uwe >> ________________________________________ >> German Amateur Radio Station DG2YCB >> Dr. Uwe Risse >> eMail: dg...@gm... >> Info: www.qrz.com/db/DG2YCB >> >> >> >> >> >> _______________________________________________ >> 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 |
|
From: Mike L. <k7...@ho...> - 2025-05-17 21:17:41
|
For the case of Defender (no Norton), in your browser download status you have the option to keep the file. Click on the 3 dots, select Keep. [cid:image001.png@01DBC736.6C194B40] Then you get another trust question dialog, click on Show More and you will see this, choose Keep Anyway. [cid:image002.png@01DBC736.6C194B40] From: Dan Coughlin via wsjt-devel <wsj...@li...> Sent: Saturday, May 17, 2025 1:38 PM To: software development WSJT <wsj...@li...> Cc: Dan Coughlin <hot...@ho...> Subject: Re: [wsjt-devel] v2.8.0 "250501" available And Windows just plain deletes it from the downloads folder so the file cannot even be sent to them for checking. Even with all the defender stuff turned off, the file is deleted. Sent from my iPhone On May 16, 2025, at 12:14 PM, Nic Sears via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> wrote: Hi Uwe, Nic G3YEG here. When I downloaded the windows plus 250501.exe using the link below - Norton put the file in quarantine as it said it had a virus. F00038D Any ideas ? 73 Nic On 01/05/2025 01:22, Uwe, DG2YCB via wsjt-devel wrote: Dear Users, I'm glad to announce a "250501" update of WSJT-X Improved 2.8.0, which brings the following improvements: In programs QMAP and MAP65: * Introduction of a new "LiveCQ" feature. It allows messages that you decode with QMAP and/or MAP65 to be uploaded automatically via the internet to the new website: https://w3sz.com/livecq.html. The idea is to provide spots of active EME stations so that others will know where to look. Read section 16.14 of the User Guide<https://wsjt-x-improved.sourceforge.io/wsjtx-main_en.html#_livecq> for more information. * Fixed a long-standing flaw in QMAP which could cause the program to crash after a few hours of operation. In program WSJT-X: * The dial frequency can now be controlled via mouse (useful for EME operations, or when a DXpedition is not on the standard DXp QRGs). If you hover the mouse pointer over the frequency display, you have two new options: * Left-click to decrease the rig dial frequency by 1 kHz, or right-click to increase it by 1 kHz. * Turn the mouse wheel to scroll the kHz values. * You can now choose between “worked today” and “worked today or yesterday” for the three respective Hide/Ignore/Highlight Quick Filters. Switching is done via a new checkbox under Settings/Filters. * Fixed some inconsistencies around the Tx watchdog. The countdown now only starts when Enable Tx is active (important for Wait & Call). * Repeated use of the rig (ATU) tuning function now works more reliably. * Minor bug fixes and performance improvements. * Slightly more detailed explanations in the WSJT-X Improved User Guide<https://wsjt-x-improved.sourceforge.io/wsjtx-main_en.html>. * Update to Hamlib 4.6.2. * Last not least: The Qt6 source code can now also be compiled with Qt 6.8.x (important for Linux Fedora, etc.). As usual, you will find the downloadable files on my SourceForge page<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/>. Here are the direct links to download the most important packages: * wsjtx-2.8.0-win64_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_PLUS_250501.exe/download>.exe<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_PLUS_250501.exe/download> (Windows 64-bit, WSJT-X GUI) * wsjtx-2.8.0-win64_improved_AL_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_AL_PLUS_250501.exe/download>.exe<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_AL_PLUS_250501.exe/download> (Windows 64-bit, AL GUI) * wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501.exe/download>.exe<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501.exe/download> (Windows 64-bit, widescreen GUI) * wsjtx_2.8.0_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_PLUS_250501_amd64.deb/download>_amd64.deb<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_PLUS_250501_amd64.deb/download> (Linux, WSJT-X GUI) * wsjtx_2.8.0_improved_AL_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_AL_PLUS_250501_amd64.deb/download>_amd64.deb<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_AL_PLUS_250501_amd64.deb/download> (Linux, AL GUI) * wsjtx-2.8.0_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_Darwin.dmg/download>_Darwin.dmg<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_Darwin.dmg/download> (macOS x86_64, WSJT-X GUI) * wsjtx-2.8.0_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_M1.zip/download>_M1.zip<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_M1.zip/download> (macOS M1, WSJT-X GUI) Thanks to everyone who contributed to this great new release! 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> _______________________________________________ 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 |
|
From: Dan C. <hot...@ho...> - 2025-05-17 20:38:16
|
And Windows just plain deletes it from the downloads folder so the file cannot even be sent to them for checking. Even with all the defender stuff turned off, the file is deleted. Sent from my iPhone On May 16, 2025, at 12:14 PM, Nic Sears via wsjt-devel <wsj...@li...> wrote: Hi Uwe, Nic G3YEG here. When I downloaded the windows plus 250501.exe using the link below - Norton put the file in quarantine as it said it had a virus. F00038D Any ideas ? 73 Nic On 01/05/2025 01:22, Uwe, DG2YCB via wsjt-devel wrote: Dear Users, I'm glad to announce a "250501" update of WSJT-X Improved 2.8.0, which brings the following improvements: In programs QMAP and MAP65: * Introduction of a new "LiveCQ" feature. It allows messages that you decode with QMAP and/or MAP65 to be uploaded automatically via the internet to the new website: https://w3sz.com/livecq.html. The idea is to provide spots of active EME stations so that others will know where to look. Read section 16.14 of the User Guide<https://wsjt-x-improved.sourceforge.io/wsjtx-main_en.html#_livecq> for more information. * Fixed a long-standing flaw in QMAP which could cause the program to crash after a few hours of operation. In program WSJT-X: * The dial frequency can now be controlled via mouse (useful for EME operations, or when a DXpedition is not on the standard DXp QRGs). If you hover the mouse pointer over the frequency display, you have two new options: * Left-click to decrease the rig dial frequency by 1 kHz, or right-click to increase it by 1 kHz. * Turn the mouse wheel to scroll the kHz values. * You can now choose between “worked today” and “worked today or yesterday” for the three respective Hide/Ignore/Highlight Quick Filters. Switching is done via a new checkbox under Settings/Filters. * Fixed some inconsistencies around the Tx watchdog. The countdown now only starts when Enable Tx is active (important for Wait & Call). * Repeated use of the rig (ATU) tuning function now works more reliably. * Minor bug fixes and performance improvements. * Slightly more detailed explanations in the WSJT-X Improved User Guide<https://wsjt-x-improved.sourceforge.io/wsjtx-main_en.html>. * Update to Hamlib 4.6.2. * Last not least: The Qt6 source code can now also be compiled with Qt 6.8.x (important for Linux Fedora, etc.). As usual, you will find the downloadable files on my SourceForge page<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/>. Here are the direct links to download the most important packages: * wsjtx-2.8.0-win64_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_PLUS_250501.exe/download>.exe<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_PLUS_250501.exe/download> (Windows 64-bit, WSJT-X GUI) * wsjtx-2.8.0-win64_improved_AL_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_AL_PLUS_250501.exe/download>.exe<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_AL_PLUS_250501.exe/download> (Windows 64-bit, AL GUI) * wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501.exe/download>.exe<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501.exe/download> (Windows 64-bit, widescreen GUI) * wsjtx_2.8.0_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_PLUS_250501_amd64.deb/download>_amd64.deb<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_PLUS_250501_amd64.deb/download> (Linux, WSJT-X GUI) * wsjtx_2.8.0_improved_AL_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_AL_PLUS_250501_amd64.deb/download>_amd64.deb<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_AL_PLUS_250501_amd64.deb/download> (Linux, AL GUI) * wsjtx-2.8.0_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_Darwin.dmg/download>_Darwin.dmg<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_Darwin.dmg/download> (macOS x86_64, WSJT-X GUI) * wsjtx-2.8.0_improved_PLUS_250501<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_M1.zip/download>_M1.zip<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_M1.zip/download> (macOS M1, WSJT-X GUI) Thanks to everyone who contributed to this great new release! 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> _______________________________________________ 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 |
|
From: Charles S. <g3...@gm...> - 2025-05-16 16:53:19
|
---------- Forwarded message --------- From: Uwe, DG2YCB via Wsjt-x-improved-community < wsj...@li...> Date: Thu, 15 May 2025 at 13:05 Subject: Re: [Wsjt-x-improved-community] False positive virus alerts To: Wsjt Improved <wsj...@li...> By the way: The page where each of you can *report false-positive virus alerts to Microsoft *is this one: *https://www.microsoft.com/en-us/wdsi/filesubmission <https://www.microsoft.com/en-us/wdsi/filesubmission>* The other providers of antivirus software certainly have a similar website. 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB Am 14.05.2025 um 10:16 schrieb Uwe, DG2YCB: Dear Users, In the past days I received some emails telling me that some antivirus software gave alerts for the latest WSJT-X Improved Windows installer. I can assure you that no program compiled by me has ever contained any virus or Trojan. In addition, every file on SourceForge is scanned again for viruses. This leaves only the minimal theoretical risk of a so-called man-in-the-middle attack, i.e. someone intervening during the download and injecting malicious code. With https connections, however, the probability of this happening is as low as being hit by a comet today. *The procedure for such false positives is always the same: Please contact the antivirus software providers concerned and ask them to scan the file in question. So far, not a single real virus has ever been detected in any program compiled on my computers* (i.e. all WSJT-X, WSJT-X Improved or JTDX Improved programs of the last 3 years). The reliability of antivirus programs has diminished considerably in recent times. Instead of scanning themselves, other criteria are simply used nowadays. If the file is from companies such as Microsoft, etc., it is classified as harmless. If the provider is not on such lists, the program is already “suspicious”. If then the program also has to communicate via TCP or UDP, it is immediately classified as virus-infected, regardless of whether it actually contains a virus or not. I probably don't need to mention what I think of this, because conversely, it also means that such antivirus software is just as unlikely to detect real threats. Remember: With WSJT-X (or WSJT-X Improved, but that's just an extended version of it), PSK Reporter has to communicate over the Internet. For the connection to JTAlerts and to the logging software we need communication via UDP. The radio must be connected via COM ports. In addition, we have shared memory usage between wsjtx.exe, qmap.exe and jt9.exe. It's no wonder that antivirus programs initially classify this as “suspicious”. But now comes the important difference: In the past, these providers really scanned such program files (and then came to the correct result: everything is virus-free), nowadays it is simply classified as supposedly contaminated with viruses. And the thousands of users of such antivirus software are so stupid that they still trust them, hi. *Again, the only solution to this is for you users to send the files in question to these providers for analysis (with the suspicion of a false positive alert). Preferably dozens or hundreds of you should do that! * This is the only way to finally stop this nonsense. 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB _______________________________________________ Wsjt-x-improved-community mailing list Wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-x-improved-community |
68 messages has been excluded from this view by a project administrator.
