As Neil has pointed out that some Hamlib files are
incorporated within the dot exe
WSJT-X then that is where the problem begins. Instead of the
files being within WSJT-X
would be better to have the necessary Hamlib files in another
location that can be easily
and separate from the dot exe. Like this location,
Hamlib folder is where all necessary files are there and can
be easily updated.
would copy the entire Hamlib folder to another location for
safe keeping just in case
and then copy/paste the
updated Hamlib files into the Hamlib folder then start WSJT-X
your case select the correct radio (FT817) in the dropdown.
can be setup to read from this Hamlib folder the required
files for the operation.
realize that some people will criticize this idea but it will
most definitely solve the bugs
Hamlib unleashes by simply being able to update manually with
files that have been fixed.
stands now the only way for any updated Hamlib version to be
contained in WSJT-X
put out a new WSJT-X version. If a new radio comes out then
the Hamlib team
this and comes out with a version that includes the new radio,
copy this new
into the Hamlib folder--no need to update the entire WSJT-X.
course a new WSJT-X version will be needed too, as I said
earlier read from the
folder the required files, from then on just update the Hamlib
crazy for people to select a different radio in order to stop
the rig error popup.
now donning my Kevlar suit just waiting for the licking of the