Well, MSHV did "bypassed" it already by not providing lockout as they should, in my mind. 73, Reino OH3mA Original message: The F/H "lockout" is only strong enough to keep honest people honest. It

The F/H "lockout" is only strong enough to keep honest people honest. It is easy enough for someone who it tech savvy to bypass it. Not saying that anyone does, but it can

There is no F/H bit in the FT8 air interface protocol so an automatic detection of a FOX is next to impossible. Also MSHV user guide recommends that multiple streams should be used only on special

You are misleading. Switching configurations does not 'rewrite' anything, in fact its using the same .ini file, just a different area of it as the program restarts. As long as you

Most of the recent DXpeditions have been using MSHV's multi-stream mode on standard FT8 channels, but are NOT running Fox/Hound. WSJT-X is programmed so that Fox/Hound mode won't work on standard

Hi, If I am not mistaking, when you switch configurations, WSJT-X offloads and reloads its entire environment including rewriting and reloading its configuration file. Not as efficient as simply

Single click switching between F/H and normal mode is already available. Simply create a new configuration for FT8 F/H mode and save it. Then to switch between normal and F/H modes, click

First, thank you for such an incredible application! It is; however, tedious switching between normal FT8 and Hound operation to work a Fox, then work a normal FT8 station. It would be wonderful if

Bill, You are so correct as usual. I found that the cables supplied by Digirig were faulty. I changed to a combination of Signalink and a CAT cable...forgot name. So far things seem to be working just

On 28/10/2021 21:21, Kenneth Blackwell wrote: Hi Ken, the second result is showing that a process running wsjtx with PID 1944 is holding the lock. That means the previous run

Bill, The problem came back. I executed the two items that you told me to check. Results below. ken@ken-X510UNR:~$ ls -l /tmp/WSJT-X.lock -rw-rw-r-- 1 ken ken 93 Oct 28 14:38

I recently switched to 2.5.1. Now I cannot band hop with WSPR as before. When I click “Schedule” it doesn’t open. All other functions are OK. My radio is the IC-7610 and my computer is Raspberry

Hi Freddy, I suggest you start with the WSJT-X User Guide instructions: https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.5.1.html#INSTALL_LINUX 73 Bill G4WJS.

Hi everyone, I currently run wsjt-x 2.3.0 on Ubuntu 21.10. I plan to upgrade, but can not find precise instruction on how to manage this. Do I need to remove de previous version, or is it ok to simply

FWIW ... I always restart the computer when I see an error like that. Restarting (no matter what OS) will normally clear the environment, and release any files that are locked.

Bill, . Thanks a bunch. It was locked up and pressing Yes would not remove the other copy. After a while including uninstall, reinstall, I gave up and wrote the note above. Then I powered-down and

I'm posting this on Moon-net, where the discussion started, and here as requested by Bill. I was having a CAT rig control problem relating to trying to change Tx frequency while transmitting. I

Hi Tom, Steven had entered a non-existent network server address for rig control, that triggered a defect in WSJT-X which caused it to crash while trying to shutdown. It will

Out of interest what were to two changes you made? Can’t see anything in previous messages, Tom GM8MJV

My computer came with W11. I made a change on WSJT that started my problem. Working now.