Gary, Joe and All, Just ignore hashtags and don’t use those, if you don’t want to use features hashtags provide. You may continue as before, no need to web page at all. 73, Reino OH3mA PS.

Hi, Anyone ro help how to set up WSJTX for contest with serial number? TNX/73 Dusan YU1EA

Ooops! I know this version won't make it until then, but just to let you know so that you can fix it for the GR... As I was going back through my settings to ensure everything was the same, I noticed

Hello again wsjtx team, I think it would be really helpful to add a 'color'/function into the settings. That would be a "new grid", but with a user defined specific target... In other works, "new grid

Hello wsjtx team, First, thank you very much for fixing the "Halt TX" button, and making it work as it should, like it did before. So far, so good with -rc3... only small issue, could you please move

I also experienced several WSJTX (v2.2.2) crashes during the RTTY RU contest. I was using FT4 via N1MM. I had to reboot the PC each time. Below are screenshots of the error messages I got in the

Karl, If you'll permit me to comment, it's not a matter of revising the software to work with one design. LF/MF users, where the FST4 modes are targeted, very often use highly efficient, non-linear

Gary, I agree 100% This is not twitter, there are ways to search and ways to mute the subject already, we don't need to make things more complicated. I vote for a new hashtag #TRAINWRECK W9RF - Joe

I have to agree with you Gary -- this will probably prevent me from contributing anything of use. Hashtags do not belong in email. 73 -- Larry -- W1DYJ

I wouldn’t know a hashtag if it jumped up and bit me. I’m not on social media at all, and I don’t intend to have to partake in or log into a web page in order to make use of this or any other

PAUL - I hope you are not suggesting that the widely accepted WSJT-X software should be revised to work with one specific homebrew amplifier circuit design. In the long run that would set an

I just installed WSJT-X 2.3.0- rc3 and initial tests show that the problem I had with rc2 is still there in the new RC. When I am in MSK144 after the first TX Cycle I get a pulsing interference on

On 06/01/2021 23:32, David Kaplan wrote: Hi David, extra ADIF fields are no problem. The DXCC Entities of prior QSOs are determined purely from the call prefixes and overrides

Bill, Thanks for the quick reply.. Will try this Fri. RB

The wsjt-x program closed. I did have to reboot one time, but I may have not been patient enough to see if it was working properly. That was early on. JTAlert starts WSJT-X. On some occasion someone

On 06/01/2021 23:42, Rick Boswell wrote: Hi Rick, yes, using Commander's secondary rig control port is the way to go. SDRUno can accept Kenwood style CAT commands and

Bill, Yes, I understand. However, John said that he uploaded "from WSJTX to LOTW". That isn't quite the same as what you said. I was just wondering if he had found a way to do it

I recently rebuilt my Mac fresh to get rid of years of “crud”. My extensive backup system missed the wsjtx_log.adi file. (That won’t happen again!) I wasn’t too concerned as I had my

On Wed, Jan 6, 2021 at 02:38 PM, Rick Boswell wrote: Any alternatives you can suggest to achieve what I am trying to do?After doing some digging in the DX Lab (voluminous) documentation, I may have

On Wed, Jan 6, 2021 at 01:43 PM, Bill Somerville wrote: any use of VSPE as a port splitter is not supported by WSJT-X, nor by DX Lab Suite Commander AFAIK.Hmmm .... well, this might be important to