Did it not save when you upgraded. Or did you uninstall it? Then reinstall. I am not home right now so i cant look it up but maybe frequency reset might bring them in or wait for the knowledgeable to

Try the ‘high contrast’ option in Windoze 10…works for me..takes some fiddling but I like it yahoo.com@groups.io> wrote: Eric J Evans Amateur Radio Operator: K4NDN Elkton, VA. USA, 22827 Grid:

I HAVE THE FREQ''S FREQ'S FOR 60 METRS. I FORGOT HOW TO SET UP 60 IN WSJT? THANKS -- *73'S DAVE NU4N*

Hi Palle, There is no bits for a contest "name" in the messages as such and contest specific messages a recognized only by the message construction as some stage of the QSO message exchange. Some of

I have noticed when manually trying to enter a contact in WSJT-X in FD mode while using N3FJP link, that entering the exchange in small letters gets a bad entry when sending to N3FJP. N3FJP requires

Hello all. Built it 2.6.0 on my Raspberry Pi 4B without any issues. I like the changes and hope to see a few more. So far everything that I use is working. 73. Carl - WC4h

Thanks to the team for ongoing work. One comment. Those of us active on 6M have long found the need for a VHF Contest Mode more important than Fox/Hound. It's needed not only during contests, but also

Yeah, I think the ghost is for this. Buto old WSJT-X does not list the ghosts, only the most powerful signal. Pietro (via Tablet) yahoo.com@groups.io> ha scritto:

Those of us around San Francisco and San Jose see this pretty often, thanks to multiple airports with lots of traffic. I'm 20 miles from the nearest airport and see it often. 73, Jim K9YC

That's interesting -- same here. I much prefer dark mode and it'd be great if this albeit very minor glitch could be fixed.

It would be better if WSJT could switch automatically to contest mode and back again. That is WSJT should always send the exchange wanted by the other QSO partner and then after the QSO go back to the

That was it here. Changing from dark mode eliminated the problem. Still not a major issue, but I hope it might be addressed somewhere down the road. 2.6.0 still performing well! Tnx es 73 Dave -

This is not a WSJTX problem so I am locking this thread. Please continue discussions on a JTALERT forum. 73 Roger GW4HZA Moderator

Hi Joe & wsjtx team, Interesting... Could you folks please elaborate on the following... - Correct the handling of messages starting with "CQ xxxx ..." What was 'wrong' with it, how is

Hi all this might be of help.Running here Windows 10 Dell.I tried several times and this error occurred.C:\WSJT\wsjtx\bin\qt5core.dll. Retry and ignore never worked.Check for file in WSJTX and it was

It could also be caused a power line ( 50 hz in EU) induced AM modulation. It could be power supply ripple on the RF PA, AC modulating the TX audio tones and even RF coupled to the AC lines with a

OK sorry guys, I didn't realize that window was generated by N1MM and not WSJT-X. Problem is being looked into. Bob, K2RET <pre>1</pre>

Dave, the issue seems to be the newest update release (2.51.5) of jtAlerts. When I reverted back to the last version I didn't get the error about not logging to dxlab when making a new qso. When I

For me, this screen shift occurs in the “dark mode.” When I restart WSJT-X in the “normal mode,” the shifting stops. 73, Chet W6XK

Could also have each occurrence send to a compatible free logging program. I have 3 wsjtx running 2 slices via slicemaster 1 not. All going into jtalert x 3 and sending to log4om. Then they can be