Problems that have plagued me

1.  Windows 10 updates

After my first W10 update headache a few years ago, the problem was resolved by using the Task Manager – Startup listing to disable the default automated startup of DAX and CAT so they would not be running unless specifically called.  Since I use my computer for other matters, I wrote two simple batch files with desktop icons to open and close the ham radio programs I use (Ham ON, and Ham OFF for SmartSDR, CAT, DAX, DXLab suite, 2K-FA control panel). 

There has never been a problem with W10 updates since then.

2.  FT8 decoding limitations and skips

For digital modes, there are two similar batch files (HamDIGU ON, HamDIGU OFF) to open and close SmartSDR, CAT, DAX, DXLab suite, 2K-FA control panel, and JTAlert (with JTAlert to internally open WSJT-X).  In my case the FT8 decoding problem was resolved by adjusting the CPU use.  Even though the computer is fast (3.34 GHz Duo CPU), Task Manager – Processes and Performance showed that CPU usage frequently hit 100% during FT8, thus disrupting the decoding process.  The problem was not the necessary programs for FT8 but, instead, other background processes demanding CPU time.  The solution was to note CPU usage for various running Background and Windows processes and Ham radio processes and adjust their priorities (right click process in Task Manager – Details) higher for JTAlert, WSJT-X, etc. and lower for other processes such as “Carbonite” file backups, etc. 

There is, however, one further glitch in this solution:  priority changes in Task Manager cannot be made permanent in W10 and, therefore, priorities revert to their default values at every reboot of the computer.  The solution to this is to download and install the free program “Process Hacker 2” which then displays a “Task Manager” view where priority setting changes are permanent.

FT8 now decodes perfectly.