Re: [Hamlib-developer] Log4OM and NET Rigctl problems

[J B. <syd...@gm...>]

On the debug options I see Bug, Error, Warning, Verbose, Trace and Cache. I
have some stuff captured as Cache. I'm attaching those here. I also noticed
that Log4OM is opening its rigctl in a different location and as a
different version than the version of hamlib rigctld I am using and opening
in my batch file. I am going to attempt to add the path that log4OM is
calling to the env variable path and then I am going to replace all of the
log4OM hamlib folder files with the latest 4.7.1 instead of 4.6.2 which
hamlib is calling. I suppose I will also change my called path from
C:\Program Files\hamlib-w64-4.7.1\bin to the folder that log4OM is calling
and see if that affects anything.

On Wed, May 6, 2026 at 4:44 PM Nate Bargmann <n0...@n0...> wrote:

> * On 2026 06 May 16:41 -0500, J Bowen wrote:
> > Im gonna try something right quick. I don't know if this takes
> attachments
> > but I'm gonna try a picture here. This is the Hamlib parameters screen
> > that's supposed to set up the CAT connection.
>
> What are the options for the "Debug" drop-down?
>
> 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
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
>