Re: [Hamlib-developer] Rig Control Error

[Nate B. <n0...@n0...>]

* On 2025 09 Nov 12:05 -0600, prb...@gm... wrote:
> I'm not very good at technical things, I have your document "How to deal
> with Rig control errors" but get a bit lost.

Hi Peter.

I'm not sure that is a document provided by Hamlib.  It doesn't sound at
all familiar to me.

> Number 3. says update Hamlib to the latest version, but I get an error when
> I try,  "error loading Hamlib-4.dll  TLS Initialization failed"?

That is strange.  Is that an error you're getting when trying to
download from the Internet?  If so, the link name had to change due to
the elimination of personal Web space hosting by SourceForge.net.  The
main page is now https://hamlib.sourceforge.net/snapshots/ and the
.DLLs are at:

https://hamlib.sourceforge.net/snapshots/dll32/libhamlib-4.dll
https://hamlib.sourceforge.net/snapshots/dll64/libhamlib-4.dll

The former is for 32 bit Windows and the latter for 64 bit.

> Number 4 says click to save menu on diagnostics mode? Which I don't
> understand?

Neither do I!

> The error I get from the main screen is shown below.
> 
>  
> 
> If there is anyway you could assist me, that would be great.

We have a utility, rigctl, that we much prefer to see diagnostics from.
I think WSJT-X includes it but I'm not sure as I don't use that software
on Windows.

You can start reading this section of our README.betatester file:

https://github.com/Hamlib/Hamlib/blob/55feb026fa0de001cd4306f90691f0b00214f04e/README.betatester#L209

The key difference is that you will use something like "COM8" for the
-r option.  The -vvvvv option is very important from our perspective as
that is the maximum amount of debugging output that Hamlib will
generate.  Post all of that output here, please.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819