Re: [wsjt-devel] Call for information about PC systems being used for WSJT-X
On 09/06/2021 00:38, Bill Somerville wrote: all I need to know is who or how many of you are using the older CPU architectures Hello Bill My radio PC uses an Intel Xeon 5450. It does not support AVX. 73 Nick G3VNC ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] wsjtx-2.3.0 - No TX audio following band change
wsjtx-2.3.0 GA release, Qt5.13.0 Linux Mint 19.3 Tricia - Cinnamon Linux LM19-3 4.15.0-140-generic #144-Ubuntu SMP Fri Mar 19 14:12:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Rig: TenTex Delta 580 - No CAT. PTT via DTR - /dev/ttyUSB0, Belkin USB to RS-232, homebrew PTT interface to rig. Start wsjtx on last used band. Tune - all OK. QSO - all OK. Change wsjtx band. Tune button - all OK. QSO - PTT OK - RX OK - No audio on TX. While on TX - Halt TX - Enable TX clears fault, as does restarting wsjtx. 73 Nick G3VNC ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Version 2.3.0 and Fedora 32
On 05/02/2021 11:36, jarmo wrote: Has anyone managed install version 2.3.0 into F32? 2.3.0 has depencies to BOOST 1.73 and in F32 there is BOOST 1.69. So anyone solved this? Jarmo, oh1mrr On Linux Mint 19.3 I did $ sudo apt install libboost-all-dev as per the 2.3.0 User Guide and built 2.3.0 from source with no issues. The libboost-all-dev version that was installed from the repo is 1.65.1.0ubuntu1. Am I missing something? Nick ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X won't connect to a COM Port
Mike Instead of running VSPManager as administrator could you add an entry for the non privileged user to the registry key ACL and set the required permissions there? Obviously backup the registry first ;) Nick G3VNC On 06/11/2020 17:07, Black Michael via wsjt-devel wrote: I just helped him and that's exactly what we had to do. VSPManager was giving a permission error on a registry key. Mike W9MDB On Friday, November 6, 2020, 10:48:04 AM CST, Neil Zampella wrote: It is NEVER a good idea to run 'as Administrator' as that raises the permissions of the program and often causes other programs issues as they can't communicate with it. In fact, no well written Windows program should be run 'as Administrator'. Neil, KN3ILZ On 11/6/2020 7:56 AM, John Clark wrote: Run VSPMgr as Administrator? 73 TI4JWC ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
