Hi Bill, MNI TNX for the clarification on this! VY 73, Lance -- Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ,

Hi Lance, MSK144 modulation bandwidth is a little bit wider than a typical SSB Tx filter, that means that the outermost sidebands are attenuated, and therefore the signal is not quite constant

My WSJT-X / JTAlert combination do noy log contacts automatically to HRD Logbook. Set up as defined in the user manuals.

Joe, The ITU call sign blocks are recommendations and guidelines, not law or not regulations. There are many non-ITU call signs in use, including several DXCC entities. They are not "illegal" and

I have The Sovereign Military Order of Malt 1A0C (on JT65), and 1A0KM (CW and SSB), both confirmed on LoTW and by paper QSLs. Cheers Kai, KE4PT

Several of us have wondered why the wattmeter drops when the mode is switched from FT8, JT65, or tune, etc. to MSK144. I checked the User Guide but couldn't find any information about it. Is there

Any prefix that starts with the number 1 is not valid - the 1AA-1ZZ block is not used by the ITU (also 0AA-0ZZ and QAA-QZZ). This would appear to be a "false decode" although I wonder why K1JT et.

Hi Bill. Ctrl-Alt- Esc worked (new for me). The keyboard is a Logitech K520 connected to a LogiLink USB reciver. WSJTx has now been running for over 5 hours without any problems. Have put it on the

Hi Dick, You are not alone, see https://klubnl.pl/rsgb_lf_group-archives/html/rsgb_lf_group/2019-04/msg00032.html 73, Reino OH3mA

Dick, Not in the least. There are some false calls that come up many times "spotted" from a number of stations. And once you have made a bad decode then it is stored in the hashtable, so might

Greetings Everyone I had two different time-slot decodes for 1IO/IL0HBU on 80-meter WSPR I can not identify (see below) When I enter that call in the WSPRNET map nothing shows up for that call. Seems

I need your help, please. Things going fine this AM, couple far eastern contacts then stopped by Hamlib error: IO error while testing getting current VFO. Can’t get rid of the error. Turned

As it is, the version of Hamlib in WSJT-X is actually more up to date as it has been constantly been added to, and corrected, whereas the main Hamlib code was not. In fact, the last Hamlib update that

Hi Eric, as has been reported here a few times, WSJT-X v2.2.2 has a known issue with WSPR band hopping. Please revert to WSJT-X v2.1.2 if you need to run WSPR Band Hopping. 73 Bill G4WJS.

Hi Lars, something is seriously wrong with your PC if Ctrl+Alt+Del does not bring up the blue menu. Error messages from WSJT-X are the least of your issues. Are you sure you do

Randy, as has been posted here several times, there is a known issue with WSJT-X v2.2.2 which means that owners of Yaesu FT-817, FT-818, and FT-897 rigs must select the FT-857 option. That's it, it

Bruce, sure we could do that but the current release of Hamlib is many Years old, so to satisfy your rant we would have to remove many Years of new rig support and bug fixes.

Sorry… After 4 hours this morning the ”Error in Sound Input” is back. WSJTx is looked. Does not respond on ”Control C” in the error pop up. Does not respond on Ctrl-Alt-delete or anything I

Randy, As Neil has pointed out that some Hamlib files are incorporated within the dot exe of WSJT-X then that is where the problem begins. Instead of the files being within WSJT-X it would be better

FWIW ... the latest version of Hamlib is compiled in with WSJT-X. As far as earlier versions, they are always available on Sourceforge here: