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
(10) |
Sep
|
Oct
|
Nov
|
Dec
|
|
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 |
|
From: Charles S. <g3...@gm...> - 2025-05-16 16:49:10
|
Hi Nic False positive. Uwe wrote about this a couple of days ago, and what to do about it. I'll see if I still have his email and forward it. 73 Charlie DL3WDG On Fri, 16 May 2025 at 18:15, 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_25**0501* > <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_25**0501* > <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_**25**0501* > <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_**25**0501* > <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_**25**0501* > <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_**25**0501* > <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... > Info: www.qrz.com/db/DG2YCB > > > > > _______________________________________________ > 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 > |
|
From: Nic S. <nic...@ta...> - 2025-05-16 16:07:43
|
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 > <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: > o Left-click to decrease the rig dial frequency by 1 kHz, or > right-click to increase it by 1 kHz. > o 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_25**0501* > <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_25**0501* > <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_**25**0501* > <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_**25**0501* > <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_**25**0501* > <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_**25**0501* > <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... > Info: www.qrz.com/db/DG2YCB > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Marco C. <PY...@ou...> - 2025-05-14 15:04:17
|
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-14 05:41:56
|
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: Marco C. <PY...@ou...> - 2025-05-13 19:23:26
|
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...> Sent: Tuesday, May 13, 2025 4:04:51 PM To: PY...@ou... <PY...@ou...>; 'WSJT software development' <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...> Sent: Tuesday, May 13, 2025 12:25 AM To: wsj...@li... Cc: Marco Calistri <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-13 19:05:04
|
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...> Sent: Tuesday, May 13, 2025 12:25 AM To: wsj...@li... Cc: Marco Calistri <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: Marco C. <PY...@ou...> - 2025-05-12 21:24:58
|
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 Il 12/05/25 09:05, Andrew Neumeier via wsjt-devel ha scritto: > Marco is referring I think only to the use of the cw ID while using > the short message format on 2 meter msk144. On that band/mode > operators do not exchange signal reports and turn to the short message > format (known as Sh) to complete a meteor scatter qso with quickly > decaying meteor trails. Time is of the essence. However, a > monitoring station often can not decode the callsigns of stations > using the Sh format. With this in mind, two meter meteor scatter > operators, when involved in a particularly long qso, will use the > cw-id to identify their station to comply with regulations. Meteor > scatter contacts on 2 meters can take a long time, I've seen them last > a hour or more. > > Sometimes the use of the SWL format, (ticking the SWL box in MSK144) > will reveal the callsign of the station using the Sh format, but > sometimes it does not. Hence he use of the cw-ID. > > 73, > Andy, ka2uqw > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Andrew N. <ka...@ya...> - 2025-05-12 12:06:59
|
Marco is referring I think only to the use of the cw ID while using the short message format on 2 meter msk144. On that band/mode operators do not exchange signal reports and turn to the short message format (known as Sh) to complete a meteor scatter qso with quickly decaying meteor trails. Time is of the essence. However, a monitoring station often can not decode the callsigns of stations using the Sh format. With this in mind, two meter meteor scatter operators, when involved in a particularly long qso, will use the cw-id to identify their station to comply with regulations. Meteor scatter contacts on 2 meters can take a long time, I've seen them last a hour or more. Sometimes the use of the SWL format, (ticking the SWL box in MSK144) will reveal the callsign of the station using the Sh format, but sometimes it does not. Hence he use of the cw-ID. 73,Andy, ka2uqw |
|
From: Reino T. <rei...@ko...> - 2025-05-11 17:37:55
|
Marco, I am not an expert, but I assume that you need to select ‘ID CW dopo 73’ for the activation. I read is so that the CW ID is sent in your settings only after every third sending of the ‘73’. It may be so that it will be sent only as a part of QSOs, not otherwise. I have not used it as it is not a mandatory issue in Finland. 73, Reino OH3mA From: Marco Calistri via wsjt-devel <wsj...@li...> Sent: Sunday, May 11, 2025 7:55 PM To: Patrick 9A5CW <pat...@gm...>; WSJT software development <wsj...@li...> Cc: Marco Calistri <PY...@ou...> Subject: Re: [wsjt-devel] CW-ID is not being sent Thanks Patrick! I'm using latest WSJT-X version and I was expecting to see the CW-ID during MSK144 operation. 73 de Marco PY1ZRJ Il 11/05/25 13:33, Patrick 9A5CW ha scritto: CW id was used b4 in past on old modes. Not sure if is still used nowdays. JT65a, JT6M had CW ID. ned, 11. svi 2025. 18:28 Marco Calistri via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > je napisao: Hello, I started to use MSK144 and among other things, I'm not understanding if I'm doing something wrong that prevents my CW-ID to be sent every time-frame I selected. Are there some details that I'm missing? How could I verify the CW-ID transmission? These are my current settings: I've tried 1, and 7 as well but I never noticed CW-ID being sent. Thanks! --- 73 de Marco, PY1ZRJ (former IK5BCU) _______________________________________________ wsjt-devel mailing list wsj...@li... <mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel EFE62hMo0AA5GaSX.jpeg ZpqOWexRd030VPJP.png --- 73 de Marco, PY1ZRJ (former IK5BCU) |
|
From: Marco C. <PY...@ou...> - 2025-05-11 16:55:35
|
Thanks Patrick! I'm using latest WSJT-X version and I was expecting to see the CW-ID during MSK144 operation. 73 de Marco PY1ZRJ Il 11/05/25 13:33, Patrick 9A5CW ha scritto: > > CW id was used b4 in past on old modes. Not sure if is still used nowdays. > JT65a, JT6M had CW ID. > > > ned, 11. svi 2025. 18:28 Marco Calistri via wsjt-devel > <wsj...@li...> je napisao: > > Hello, > > I started to use MSK144 and among other things, I'm not > understanding if I'm doing something wrong that prevents my CW-ID > to be sent every time-frame I selected. > > Are there some details that I'm missing? > > How could I verify the CW-ID transmission? > > These are my current settings: > > > > I've tried 1, and 7 as well but I never noticed CW-ID being sent. > > Thanks! > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > EFE62hMo0AA5GaSX.jpeg > > > ZpqOWexRd030VPJP.png > --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Patrick 9. <pat...@gm...> - 2025-05-11 16:33:54
|
CW id was used b4 in past on old modes. Not sure if is still used nowdays. JT65a, JT6M had CW ID. ned, 11. svi 2025. 18:28 Marco Calistri via wsjt-devel < wsj...@li...> je napisao: > Hello, > > I started to use MSK144 and among other things, I'm not understanding if > I'm doing something wrong that prevents my CW-ID to be sent every > time-frame I selected. > > Are there some details that I'm missing? > > How could I verify the CW-ID transmission? > > These are my current settings: > > > > I've tried 1, and 7 as well but I never noticed CW-ID being sent. > > Thanks! > --- > > *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-05-11 16:19:52
|
Hello, I started to use MSK144 and among other things, I'm not understanding if I'm doing something wrong that prevents my CW-ID to be sent every time-frame I selected. Are there some details that I'm missing? How could I verify the CW-ID transmission? These are my current settings: I've tried 1, and 7 as well but I never noticed CW-ID being sent. Thanks! --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Marco C. <PY...@ou...> - 2025-05-10 19:32:47
|
Thanks Charlie for your additional recommendations! Best 73's de PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Charles Suckling <g3...@gm...> Sent: Saturday, May 10, 2025 4:20:02 PM To: PY...@ou... <PY...@ou...>; WSJT software development <wsj...@li...> Subject: Re: [wsjt-devel] Hints for MSK144 operation Hi Marco QRM from terrestrial stations certainly makes MSK144 somewhat difficult especially during showers. Here in Europe we generally use 30s periods, although some use 15s, which can block out half a period! There are supposed rules for even and odd periods based on beam headings in use, and also local rules about first and second period. Sometimes the rules are in conflict! One thing we have learned is to try not to conduct QSOs on a calling channel, but many do this with consequent QRM. Better is to reply to stations who call CQ with a QSY frequency, so the actual QSO is conducted off the calling channel, 73 Charlie DL3WDG On Sat, 10 May 2025 at 20:17, Marco Calistri via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> wrote: Thanks Reino, Yes, I read the User Guide relatively to MSK144, but I like to have direct experience sharing with other users too. Both my HW are not so kind of new products: radio is a Yaesu FT-100 and computer is a Lenovo Ideapad Core i5, with 8G and 1T SSD disk. I've been able to do a MSK144 QSO with a station which is about 250 Km away from my QTH, then it has not been a meteor scatter QSO. But what let me more doubtful about MSK144 are the lack of decoding during reception of local transmissions by nearby stations: I mean is it caused by some wrong settings in WSJTX? And the other is related to the antenna requirements, since my antenna is a small 2 elements not steerable Moxon. 73's de Marco PY1ZRJ Il 10/05/25 12:41, Reino Talarmo ha scritto: Hello Marco, User Guide 9.5 MSK144 gives answers to most of your questions. Please note that MSK144 is a totally different protocol than e.g. FT8. It uses the whole audio bandwidth and, in that sense, there is only a single ‘correct’ audio transmit and reception frequency, in most if not all rigs it is 1500 Hz. Your receiver bandwidth should be 300 Hz to 2400 Hz or more. If possible, I would set it wider as the then the receiver should perform better. Also a symmetric bandwidth around 1500 Hz should be a good selection on the decoding point of view. The selection of the Decode level and Ftol depends on your computer capabilities. A modern one should manage Deep and 200 Hz. You may try Tx even/1st selection, but I don’t know whether in your region has a rule how to select it depending on the antenna direction. 73, Reino OH3mA From: Marco Calistri via wsjt-devel <wsj...@li...><mailto:wsj...@li...> Sent: Saturday, May 10, 2025 2:57 PM To: 'WSJT software development' <wsj...@li...><mailto:wsj...@li...> Cc: Marco Calistri <PY...@ou...><mailto:PY...@ou...> Subject: [wsjt-devel] Hints for MSK144 operation Hello, I'm totally new to MSK world and I would like to get some hints by experienced users about right settings to use with WSJT-X, as well as additional directions. Let's see the settings first: [cid:ii_196bb9d48f24cff311] 1. Decoding: FAST, NORMAL, DEEP (what is the format used normally?) 2. F Tol: I let this always to 200 3. RX: here I would like to ask: why program start with 160 Hz if the majority of ham operators use 1500 Hz? 4. T/R: here we have to set to 15 or 30 seconds? Other doubt is related to monitoring local stations that are not coming trough scatter reflection, in this case (direct propagation to nearby station) normally the decoding fails and WSJT-X doesn't show any message, is this normal? * What are the best hours to expect a possible MSK144 propagation (of course considering the availability of a meteor shower), I mean during the day or during the night? * Is it necessary to use an AZ/EL antenna to operate MSK or not? Many thanks for your kindest attention! --- 73 de Marco, PY1ZRJ (former IK5BCU) [cid:ii_196bb9d48f35b006a2] _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Charles S. <g3...@gm...> - 2025-05-10 19:20:33
|
Hi Marco QRM from terrestrial stations certainly makes MSK144 somewhat difficult especially during showers. Here in Europe we generally use 30s periods, although some use 15s, which can block out half a period! There are supposed rules for even and odd periods based on beam headings in use, and also local rules about first and second period. Sometimes the rules are in conflict! One thing we have learned is to try not to conduct QSOs on a calling channel, but many do this with consequent QRM. Better is to reply to stations who call CQ with a QSY frequency, so the actual QSO is conducted off the calling channel, 73 Charlie DL3WDG On Sat, 10 May 2025 at 20:17, Marco Calistri via wsjt-devel < wsj...@li...> wrote: > Thanks Reino, > > Yes, I read the User Guide relatively to MSK144, but I like to have direct > experience sharing with other users too. > > Both my HW are not so kind of new products: radio is a Yaesu FT-100 and > computer is a Lenovo Ideapad Core i5, with 8G and 1T SSD disk. > > I've been able to do a MSK144 QSO with a station which is about 250 Km > away from my QTH, then it has not been a meteor scatter QSO. > > But what let me more doubtful about MSK144 are the lack of decoding during > reception of local transmissions by nearby stations: > > I mean is it caused by some wrong settings in WSJTX? > > And the other is related to the antenna requirements, since my antenna is > a small 2 elements not steerable Moxon. > > 73's de Marco PY1ZRJ > > > Il 10/05/25 12:41, Reino Talarmo ha scritto: > > Hello Marco, > > User Guide 9.5 MSK144 gives answers to most of your questions. Please note > that MSK144 is a totally different protocol than e.g. FT8. It uses the > whole audio bandwidth and, in that sense, there is only a single ‘correct’ > audio transmit and reception frequency, in most if not all rigs it is 1500 > Hz. Your receiver bandwidth should be 300 Hz to 2400 Hz or more. If > possible, I would set it wider as the then the receiver should perform > better. Also a symmetric bandwidth around 1500 Hz should be a good > selection on the decoding point of view. > > The selection of the Decode level and Ftol depends on your computer > capabilities. A modern one should manage Deep and 200 Hz. > > You may try Tx even/1st selection, but I don’t know whether in your > region has a rule how to select it depending on the antenna direction. > > > > 73, Reino OH3mA > > > > *From:* Marco Calistri via wsjt-devel <wsj...@li...> > <wsj...@li...> > *Sent:* Saturday, May 10, 2025 2:57 PM > *To:* 'WSJT software development' <wsj...@li...> > <wsj...@li...> > *Cc:* Marco Calistri <PY...@ou...> <PY...@ou...> > *Subject:* [wsjt-devel] Hints for MSK144 operation > > > > Hello, > > I'm totally new to MSK world and I would like to get some hints by > experienced users about right settings to use with WSJT-X, as well as > additional directions. > > Let's see the settings first: > > > > > 1. *Decoding*: FAST, NORMAL, DEEP (what is the format used > normally?) > 2. *F Tol: *I let this always to 200 > 3. *RX*: here I would like to ask: why program start with 160 Hz > if the majority of ham operators use 1500 Hz? > 4. *T/R*: here we have to set to 15 or 30 seconds? > > Other doubt is related to monitoring local stations that are not > coming trough scatter reflection, in this case (direct propagation to > nearby station) normally the decoding fails and WSJT-X doesn't show > any message, is this normal? > > - What are the best hours to expect a possible MSK144 propagation > (of course considering the availability of a meteor shower), I mean during > the day or during the night? > > > - Is it necessary to use an AZ/EL antenna to operate MSK or not? > > > Many thanks for your kindest attention! > > > > --- > > *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-05-10 18:12:39
|
Thanks Reino, Yes, I read the User Guide relatively to MSK144, but I like to have direct experience sharing with other users too. Both my HW are not so kind of new products: radio is a Yaesu FT-100 and computer is a Lenovo Ideapad Core i5, with 8G and 1T SSD disk. I've been able to do a MSK144 QSO with a station which is about 250 Km away from my QTH, then it has not been a meteor scatter QSO. But what let me more doubtful about MSK144 are the lack of decoding during reception of local transmissions by nearby stations: I mean is it caused by some wrong settings in WSJTX? And the other is related to the antenna requirements, since my antenna is a small 2 elements not steerable Moxon. 73's de Marco PY1ZRJ Il 10/05/25 12:41, Reino Talarmo ha scritto: > > Hello Marco, > > User Guide 9.5 MSK144 gives answers to most of your questions. Please > note that MSK144 is a totally different protocol than e.g. FT8. It > uses the whole audio bandwidth and, in that sense, there is only a > single ‘correct’ audio transmit and reception frequency, in most if > not all rigs it is 1500 Hz. Your receiver bandwidth should be 300 Hz > to 2400 Hz or more. If possible, I would set it wider as the then the > receiver should perform better. Also a symmetric bandwidth around 1500 > Hz should be a good selection on the decoding point of view. > > The selection of the Decode level and Ftol depends on your computer > capabilities. A modern one should manage Deep and 200 Hz. > > You may try Tx even/1^st selection, but I don’t know whether in your > region has a rule how to select it depending on the antenna direction. > > 73, Reino OH3mA > > *From:*Marco Calistri via wsjt-devel <wsj...@li...> > *Sent:* Saturday, May 10, 2025 2:57 PM > *To:* 'WSJT software development' <wsj...@li...> > *Cc:* Marco Calistri <PY...@ou...> > *Subject:* [wsjt-devel] Hints for MSK144 operation > > Hello, > > I'm totally new to MSK world and I would like to get some hints by > experienced users about right settings to use with WSJT-X, as well as > additional directions. > > Let's see the settings first: > > > > 1. *Decoding*: FAST, NORMAL, DEEP (what is the format used normally?) > 2. *F Tol: *I let this always to 200 > 3. *RX*: here I would like to ask: why program start with 160 Hz if > the majority of ham operators use 1500 Hz? > 4. *T/R*: here we have to set to 15 or 30 seconds? > > Other doubt is related to monitoring local stations that are not > coming trough scatter reflection, in this case (direct propagation to > nearby station) normally the decoding fails and WSJT-X doesn't > show any message, is this normal? > > * What are the best hours to expect a possible MSK144 propagation > (of course considering the availability of a meteor shower), I > mean during the day or during the night? > > * Is it necessary to use an AZ/EL antenna to operate MSK or not? > > > Many thanks for your kindest attention! > > --- > *73 de Marco, PY1ZRJ (former IK5BCU) > *** > |
|
From: Reino T. <rei...@ko...> - 2025-05-10 15:42:15
|
Hello Marco,
User Guide 9.5 MSK144 gives answers to most of your questions. Please note that MSK144 is a totally different protocol than e.g. FT8. It uses the whole audio bandwidth and, in that sense, there is only a single ‘correct’ audio transmit and reception frequency, in most if not all rigs it is 1500 Hz. Your receiver bandwidth should be 300 Hz to 2400 Hz or more. If possible, I would set it wider as the then the receiver should perform better. Also a symmetric bandwidth around 1500 Hz should be a good selection on the decoding point of view.
The selection of the Decode level and Ftol depends on your computer capabilities. A modern one should manage Deep and 200 Hz.
You may try Tx even/1st selection, but I don’t know whether in your region has a rule how to select it depending on the antenna direction.
73, Reino OH3mA
From: Marco Calistri via wsjt-devel <wsj...@li...>
Sent: Saturday, May 10, 2025 2:57 PM
To: 'WSJT software development' <wsj...@li...>
Cc: Marco Calistri <PY...@ou...>
Subject: [wsjt-devel] Hints for MSK144 operation
Hello,
I'm totally new to MSK world and I would like to get some hints by experienced users about right settings to use with WSJT-X, as well as additional directions.
Let's see the settings first:
1. Decoding: FAST, NORMAL, DEEP (what is the format used normally?)
2. F Tol: I let this always to 200
3. RX: here I would like to ask: why program start with 160 Hz if the majority of ham operators use 1500 Hz?
4. T/R: here we have to set to 15 or 30 seconds?
Other doubt is related to monitoring local stations that are not coming trough scatter reflection, in this case (direct propagation to nearby station) normally the decoding fails and WSJT-X doesn't show any message, is this normal?
* What are the best hours to expect a possible MSK144 propagation (of course considering the availability of a meteor shower), I mean during the day or during the night?
* Is it necessary to use an AZ/EL antenna to operate MSK or not?
Many thanks for your kindest attention!
---
73 de Marco, PY1ZRJ (former IK5BCU)
|
|
From: Marco C. <PY...@ou...> - 2025-05-10 12:29:54
|
Hello,
I'm totally new to MSK world and I would like to get some hints by
experienced users about right settings to use with WSJT-X, as well as
additional directions.
Let's see the settings first:
1. *Decoding*: FAST, NORMAL, DEEP (what is the format used normally?)
2. *F Tol: *I let this always to 200*
*
3. *RX*: here I would like to ask: why program start with 160 Hz if the
majority of ham operators use 1500 Hz?
4. *T/R*: here we have to set to 15 or 30 seconds?
Other doubt is related to monitoring local stations that are not
coming trough scatter reflection, in this case (direct propagation to
nearby station) normally the decoding fails and WSJT-X doesn't
show any message, is this normal?
* What are the best hours to expect a possible MSK144 propagation
(of course considering the availability of a meteor shower), I mean
during the day or during the night?
* Is it necessary to use an AZ/EL antenna to operate MSK or not?
Many thanks for your kindest attention!
---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**
|
|
From: George J M. <ge...@mo...> - 2025-05-05 17:56:18
|
Another option is something like a small Dell Optiplex 3070 with an intel Core i5. Picked one up at a hamfest for a song and it works great for Win11. Even runs SmartSDR for Flex users (that software doesn’t run on ARM chips). George J Molnar, KF2T FM19ma - Maryland, USA |
|
From: Leslie L <ll...@gm...> - 2025-05-05 17:30:08
|
$139 with coupon now on amazon. On Mon, May 5, 2025, 8:50 AM <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. Re: Windows compatibility WSJT-X and improved (Hasan N0AN) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 5 May 2025 06:44:29 -0500 > From: Hasan N0AN <hba...@gm...> > To: WSJT software development <wsj...@li...> > Cc: "Uwe, DG2YCB" <dg...@gm...>, Andy Durbin <a.d...@ms...> > Subject: Re: [wsjt-devel] Windows compatibility WSJT-X and improved > Message-ID: > <CAM4UQf1Ob3VJfBFH4MFm-FfrW94HH2FZZp17RhW4= > TfN...@ma...> > Content-Type: text/plain; charset="utf-8" > > For anyone on a tight budget, this NUC runs WSJT-X, DXLab Suites, Browser, > JTAlert, PJ Client and a host of other software, including zoom video, all > at the same time, with no more than 25% CPU use (and that is peak usage > during 50 decodes on FT8) > > It is available, new, on Amazon, priced as low as $149, 16 gB RAM, 512 gB > SSD, USB 2 and 3, BlueTooth, Wireless ...Windows 11 Pro. 3 HDMI out, > Ethernet. It has all the bells and whistles. > > > https://www.amazon.com/dp/B0DRV3G7G1?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_3&th=1 > > I bought two, one for me and one for my wife to replace Win10 machines and > they run all my ham software better than an 8 gB, I5 Lenovo Refurb that I > paid $249 for 3 years ago. > > If you want a cheap, but effective computer for Windows 11 Pro that will > run all your ham software and then some, $150 to $200 (price fluctuates) > should end your sorrows. > > 73, N0AN > > Hasan > > > On Thu, May 1, 2025 at 9:08?AM Uwe, DG2YCB via wsjt-devel < > wsj...@li...> wrote: > > > Hi Andy, > > > > You are causing a lot of confusion with such half-baked statements. Like > > always, and for good reasons, the Windows installation packages for all > > WSJT-X Improved versions are being created using Qt 5.12.12. This gives > the > > best possible backwards compatibility (down to Windows 7), as well as the > > rest results in terms of rendering the various controls (also when Dark > > Style is enabled). This tool chain has not been changed over the past > > months. > > > > As you know, we've spent many days of work trying to help you with your > > "special" setup on an old Windows 8.1. system. During these tests, you > > confirmed that all is working well on your Windows 10 computer. And no > one > > else has ever reported similar issues than you with your setup. > > > > Please do me a favor and stop confusing others. If you don't understand > > why we invest months of work to offer a data set for Qt6 in addition to > the > > existing Qt5 source code, then any further discussion about it here is > not > > worthwhile anyway. Other OMs who know what this is for are very grateful > > for this work. And if at some point in the future you should buy more > > modern equipment (maybe even Linux-based), then you will be grateful to > us > > one day why we were so wise and foresighted in 2024 and 2025 to develop > the > > necessary source code for it and keep it up to date. > > > > 73 de DG2YCB, > > Uwe > > ________________________________________ > > German Amateur Radio Station DG2YCB > > Dr. Uwe Risse > > eMail: dg...@gm... > > Info: www.qrz.com/db/DG2YCB > > > > > > Am 01.05.2025 um 13:55 schrieb Andy Durbin via wsjt-devel: > > > > "Both Windows 7 or 8.x version support will not be available for Qt 6. > > Microsoft discontinued the support for both Windows versions some time > ago, > > and as a vendor, we can no longer maintain support for these windows > > versions in Qt 6. Windows 7 (both 32bit and 64bit) was supported as a > > target in Qt 5.15 LTS and Windows 8.1 (both 32bit and 64bit) as a target > in > > Qt 5.12 LTS. This means that we will not have 32bit Windows support > > available. Additionally, it will no longer be possible to create UWP > applications > > on Windows 10." > > > > ref - https://www.qt.io/blog/qt6-development-hosts-and-targets > > > > I have found that 2.8.0 improved is not compatible with Win 8.1 and no > one > > has said that it works for them. > > > > Should the WSJT-X Windows compatibility statement be revised? It > > currently states - " (Windows 7 and later)" which was true for 2.7.0 but > > may not be true if later official releases use Qt6. > > > > 73, > > Andy, k3wyc > > > > > > > > _______________________________________________ > > 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 > > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > > > ------------------------------ > > 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 11 > ******************************************* > |
|
From: Hasan N. <hba...@gm...> - 2025-05-05 11:45:02
|
For anyone on a tight budget, this NUC runs WSJT-X, DXLab Suites, Browser, JTAlert, PJ Client and a host of other software, including zoom video, all at the same time, with no more than 25% CPU use (and that is peak usage during 50 decodes on FT8) It is available, new, on Amazon, priced as low as $149, 16 gB RAM, 512 gB SSD, USB 2 and 3, BlueTooth, Wireless ...Windows 11 Pro. 3 HDMI out, Ethernet. It has all the bells and whistles. https://www.amazon.com/dp/B0DRV3G7G1?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_3&th=1 I bought two, one for me and one for my wife to replace Win10 machines and they run all my ham software better than an 8 gB, I5 Lenovo Refurb that I paid $249 for 3 years ago. If you want a cheap, but effective computer for Windows 11 Pro that will run all your ham software and then some, $150 to $200 (price fluctuates) should end your sorrows. 73, N0AN Hasan On Thu, May 1, 2025 at 9:08 AM Uwe, DG2YCB via wsjt-devel < wsj...@li...> wrote: > Hi Andy, > > You are causing a lot of confusion with such half-baked statements. Like > always, and for good reasons, the Windows installation packages for all > WSJT-X Improved versions are being created using Qt 5.12.12. This gives the > best possible backwards compatibility (down to Windows 7), as well as the > rest results in terms of rendering the various controls (also when Dark > Style is enabled). This tool chain has not been changed over the past > months. > > As you know, we've spent many days of work trying to help you with your > "special" setup on an old Windows 8.1. system. During these tests, you > confirmed that all is working well on your Windows 10 computer. And no one > else has ever reported similar issues than you with your setup. > > Please do me a favor and stop confusing others. If you don't understand > why we invest months of work to offer a data set for Qt6 in addition to the > existing Qt5 source code, then any further discussion about it here is not > worthwhile anyway. Other OMs who know what this is for are very grateful > for this work. And if at some point in the future you should buy more > modern equipment (maybe even Linux-based), then you will be grateful to us > one day why we were so wise and foresighted in 2024 and 2025 to develop the > necessary source code for it and keep it up to date. > > 73 de DG2YCB, > Uwe > ________________________________________ > German Amateur Radio Station DG2YCB > Dr. Uwe Risse > eMail: dg...@gm... > Info: www.qrz.com/db/DG2YCB > > > Am 01.05.2025 um 13:55 schrieb Andy Durbin via wsjt-devel: > > "Both Windows 7 or 8.x version support will not be available for Qt 6. > Microsoft discontinued the support for both Windows versions some time ago, > and as a vendor, we can no longer maintain support for these windows > versions in Qt 6. Windows 7 (both 32bit and 64bit) was supported as a > target in Qt 5.15 LTS and Windows 8.1 (both 32bit and 64bit) as a target in > Qt 5.12 LTS. This means that we will not have 32bit Windows support > available. Additionally, it will no longer be possible to create UWP applications > on Windows 10." > > ref - https://www.qt.io/blog/qt6-development-hosts-and-targets > > I have found that 2.8.0 improved is not compatible with Win 8.1 and no one > has said that it works for them. > > Should the WSJT-X Windows compatibility statement be revised? It > currently states - " (Windows 7 and later)" which was true for 2.7.0 but > may not be true if later official releases use Qt6. > > 73, > Andy, k3wyc > > > > _______________________________________________ > 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 > |
|
From: Gene M. <w8...@me...> - 2025-05-02 01:05:19
|
Exactly John! Retired CIO/CSO, IT since it WAS IT! ;) 73 de W8NET Miles “Gene” Marsh ARRL A1 Operator 3905 Century Club Master #47 3905 Century Club 8th Area Director Hurricane Watch Net member Portage County Amateur Radio Service trustee > On May 1, 2025, at 3:05 PM, John L. Broughton via wsjt-devel <wsj...@li...> wrote: > > I am sorry but I could not resist. Some of us do have old cars. I am not driving my first car, but I do drive a 1957 Pontiac. A 1957 Pontiac was my 3rd and 4th car. I had one before I went into the US Army and another when I got out and could not resist buying this one when it came up for sale here in Prescott Valley, AZ, in 2014. It has won eight trophies at car shows since I bought it.: > > https://tinyurl.com/My1957pontiacchieftain > > John > Retired computer programmer/course developer and instructor/document writer AT&T Bell Laboratories/Lucent Technology > > John L. Broughton > 2si...@gm... > www.wb9vgj.us > >> On 5/1/2025 8:22 AM, Greg Walls via wsjt-devel wrote: >> As a former IT Professional of 32 years, why would anyone be on an unsupported platform, especially when upgrades to Windows 11 are free? I wonder if these guys are still driving their first car. >> >> Greg >> > > -- > This email has been checked for viruses by AVG antivirus software. > www.avg.com > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Joseph T. <jo...@Pr...> - 2025-05-01 23:17:21
|
Please, guys! ... The purpose of this email list is to aid development of WSJT and its sister programs. It is not the place for discussing relative merits of different OS varieties and versions. — 73, Joe, K1JT ________________________________ From: Joe via wsjt-devel Sent: Thursday, May 1, 2025 3:32 PM To: Doug Breault, Sr.; WSJT software development Cc: Joe Subject: Re: [wsjt-devel] Windows compatibility WSJT-X and improved Yeah and not use 90% of my programs. On 5/1/2025 2:28 PM, Doug Breault, Sr. wrote: Switch to Linux already! ;) On Thu, May 1, 2025, 3:25 PM Joe via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> wrote: I agree, My win 10 machine here can outperform 75% of available win 11 machines ya can buy. but it can't use Win 11 because of the security crap it insists on having. let ME decide if i want the extra level of security. All Win 11 is a way for them to make everyone buy new stuff Joe WB9SBD On 5/1/2025 10:57 AM, Larry Banks via wsjt-devel wrote: $$$ and upgrade difficulty, especially if the CPU is too old. Larry / W1DYJ On 5/1/2025 11:22, Greg Walls via wsjt-devel wrote: As a former IT Professional of 32 years, why would anyone be on an unsupported platform, especially when upgrades to Windows 11 are free? I wonder if these guys are still driving their first car. Greg Sent from my iPad On May 1, 2025, at 10:06 AM, Uwe, DG2YCB via wsjt-devel <wsj...@li...><mailto:wsj...@li...> wrote: Hi Andy, You are causing a lot of confusion with such half-baked statements. Like always, and for good reasons, the Windows installation packages for all WSJT-X Improved versions are being created using Qt 5.12.12. This gives the best possible backwards compatibility (down to Windows 7), as well as the rest results in terms of rendering the various controls (also when Dark Style is enabled). This tool chain has not been changed over the past months. As you know, we've spent many days of work trying to help you with your "special" setup on an old Windows 8.1. system. During these tests, you confirmed that all is working well on your Windows 10 computer. And no one else has ever reported similar issues than you with your setup. Please do me a favor and stop confusing others. If you don't understand why we invest months of work to offer a data set for Qt6 in addition to the existing Qt5 source code, then any further discussion about it here is not worthwhile anyway. Other OMs who know what this is for are very grateful for this work. And if at some point in the future you should buy more modern equipment (maybe even Linux-based), then you will be grateful to us one day why we were so wise and foresighted in 2024 and 2025 to develop the necessary source code for it and keep it up to date. 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm...<mailto:dg2ycb@gmxde> Info: www.qrz.com/db/DG2YCB<http://www.qrz.com/db/DG2YCB> Am 01.05.2025 um 13:55 schrieb Andy Durbin via wsjt-devel: "Both Windows 7 or 8.x version support will not be available for Qt 6. Microsoft discontinued the support for both Windows versions some time ago, and as a vendor, we can no longer maintain support for these windows versions in Qt 6. Windows 7 (both 32bit and 64bit) was supported as a target in Qt 5.15 LTS and Windows 8.1 (both 32bit and 64bit) as a target in Qt 5.12 LTS. This means that we will not have 32bit Windows support available. Additionally, it will no longer be possible to create UWP applications on Windows 10." ref - https://www.qt.io/blog/qt6-development-hosts-and-targets I have found that 2.8.0 improved is not compatible with Win 8.1 and no one has said that it works for them. Should the WSJT-X Windows compatibility statement be revised? It currently states - " (Windows 7 and later)" which was true for 2.7.0 but may not be true if later official releases use Qt6. 73, Andy, k3wyc _______________________________________________ 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...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Joe <ns...@mw...> - 2025-05-01 19:32:48
|
Yeah and not use 90% of my programs. On 5/1/2025 2:28 PM, Doug Breault, Sr. wrote: > > Switch to Linux already! ;) > > > On Thu, May 1, 2025, 3:25 PM Joe via wsjt-devel > <wsj...@li...> wrote: > > I agree, My win 10 machine here can outperform 75% of available > win 11 machines ya can buy. > > but it can't use Win 11 because of the security crap it insists on > having. > > let ME decide if i want the extra level of security. > > All Win 11 is a way for them to make everyone buy new stuff > > Joe WB9SBD > > On 5/1/2025 10:57 AM, Larry Banks via wsjt-devel wrote: >> $$$ and upgrade difficulty, especially if the CPU is too old. >> >> Larry / W1DYJ >> >> >> On 5/1/2025 11:22, Greg Walls via wsjt-devel wrote: >>> As a former IT Professional of 32 years, why would anyone be on >>> an unsupported platform, especially when upgrades to Windows 11 >>> are free? I wonder if these guys are still driving their first car. >>> >>> Greg >>> >>> >>> >>> Sent from my iPad >>> >>>> On May 1, 2025, at 10:06 AM, Uwe, DG2YCB via wsjt-devel >>>> <wsj...@li...> >>>> <mailto:wsj...@li...> wrote: >>>> >>>> Hi Andy, >>>> >>>> You are causing a lot of confusion with such half-baked >>>> statements. Like always, and for good reasons, the Windows >>>> installation packages for all WSJT-X Improved versions are >>>> being created using Qt 5.12.12. This gives the best possible >>>> backwards compatibility (down to Windows 7), as well as the >>>> rest results in terms of rendering the various controls (also >>>> when Dark Style is enabled). This tool chain has not been >>>> changed over the past months. >>>> >>>> As you know, we've spent many days of work trying to help you >>>> with your "special" setup on an old Windows 8.1. system. During >>>> these tests, you confirmed that all is working well on your >>>> Windows 10 computer. And no one else has ever reported similar >>>> issues than you with your setup. >>>> >>>> Please do me a favor and stop confusing others. If you don't >>>> understand why we invest months of work to offer a data set for >>>> Qt6 in addition to the existing Qt5 source code, then any >>>> further discussion about it here is not worthwhile anyway. >>>> Other OMs who know what this is for are very grateful for this >>>> work. And if at some point in the future you should buy more >>>> modern equipment (maybe even Linux-based), then you will be >>>> grateful to us one day why we were so wise and foresighted in >>>> 2024 and 2025 to develop the necessary source code for it and >>>> keep it up to date. >>>> >>>> 73 de DG2YCB, >>>> Uwe >>>> ________________________________________ >>>> German Amateur Radio Station DG2YCB >>>> Dr. Uwe Risse >>>> eMail: dg...@gm... <mailto:dg2ycb@gmxde> >>>> Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB> >>>> >>>> >>>> Am 01.05.2025 um 13:55 schrieb Andy Durbin via wsjt-devel: >>>>> "Both Windows 7 or 8.x version support will not be available >>>>> for Qt 6. Microsoft discontinued the support for both Windows >>>>> versions some time ago, and as a vendor, we can no longer >>>>> maintain support for these windows versions in Qt 6. Windows 7 >>>>> (both 32bit and 64bit) was supported as a target in Qt 5.15 >>>>> LTS and Windows 8.1 (both 32bit and 64bit) as a target in Qt >>>>> 5.12 LTS. This means that we will not have 32bit Windows >>>>> support available. Additionally, it will no longer be possible >>>>> to create UWP applications on Windows 10." >>>>> >>>>> ref - https://www.qt.io/blog/qt6-development-hosts-and-targets >>>>> >>>>> I have found that 2.8.0 improved is not compatible with Win >>>>> 8.1 and no one has said that it works for them. >>>>> >>>>> Should the WSJT-X Windows compatibility statement be revised? >>>>> It currently states - " (Windows 7 and later)" which was true >>>>> for 2.7.0 but may not be true if later official releases use Qt6. >>>>> >>>>> 73, >>>>> Andy, k3wyc >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> >>> _______________________________________________ >>> 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 > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
68 messages has been excluded from this view by a project administrator.
