And what rig would this be?

Try the latest DLL from here....

https://n0nb.users.sourceforge.net/

Mike W9MDB








On Saturday, March 18, 2023 at 03:50:12 AM CDT, bruceheimlich@... <
bruceheimlich@...> wrote:





Hi,

I have a Windows 11 box, that was running WSJT-X V 2.54 without any
issues. After ugrading it to 2.61,same exact settings, I no longer have any
CAT control. Nothing I have tried works. If I roll it back to 2.54,
everything works fine.

I suspect it might be some kind of hamlib issue but cannot figure it out.
Other people say 2.61 works fine on their machines.

I am running the latest version of Windows 11 on a Microsift SurfaceBook
2, if that helps.

I was going to try to do a 2.60 install to see if that works but cannot
find an installer package for that.

Any suggestions? I am wasting so much time with this and driving me
cookoo. :-)

Thanks!


-Bruce

Hi Michael,

The rig is the K3. I will try the newer hamlib.

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 7:21 AM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

And what rig would this be?

Try the latest DLL from here....

https://n0nb.users.sourceforge.net/

Mike W9MDB








On Saturday, March 18, 2023 at 03:50:12 AM CDT, bruceheimlich@... <
bruceheimlich@...> wrote:





Hi,

I have a Windows 11 box, that was running WSJT-X V 2.54 without any
issues. After ugrading it to 2.61,same exact settings, I no longer have any
CAT control. Nothing I have tried works. If I roll it back to 2.54,
everything works fine.

I suspect it might be some kind of hamlib issue but cannot figure it out.
Other people say 2.61 works fine on their machines.

I am running the latest version of Windows 11 on a Microsift SurfaceBook
2, if that helps.

I was going to try to do a 2.60 install to see if that works but cannot
find an installer package for that.

Any suggestions? I am wasting so much time with this and driving me
cookoo. :-)

Thanks!


-Bruce

Can you please tell me the path to that .dll?

On Sat, Mar 18, 2023 at 9:42 AM Bruce Heimlich <bruceheimlich@...>
wrote:

Hi Michael,

The rig is the K3. I will try the newer hamlib.

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 7:21 AM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

And what rig would this be?

Try the latest DLL from here....

https://n0nb.users.sourceforge.net/

Mike W9MDB








On Saturday, March 18, 2023 at 03:50:12 AM CDT, bruceheimlich@...
<bruceheimlich@...> wrote:





Hi,

I have a Windows 11 box, that was running WSJT-X V 2.54 without any
issues. After ugrading it to 2.61,same exact settings, I no longer have any
CAT control. Nothing I have tried works. If I roll it back to 2.54,
everything works fine.

I suspect it might be some kind of hamlib issue but cannot figure it
out. Other people say 2.61 works fine on their machines.

I am running the latest version of Windows 11 on a Microsift SurfaceBook
2, if that helps.

I was going to try to do a 2.60 install to see if that works but cannot
find an installer package for that.

Any suggestions? I am wasting so much time with this and driving me
cookoo. :-)

Thanks!


-Bruce

I tried the latest hamlib but still getting the same error and why does it
always refer to kenwood when the rig is a K3?:

Hamlib error: kenwood_transaction: read_string(expected=128,
len=4)='K22;'

kenwood_transaction: wrong reply K2 for command OM

kenwood_transaction: retry_read=0, rs->rigport.retry=1

read_string_generic called, rxmax=128 direct=1, expected_len=1

read_string_generic(): RX 6 characters, direct=1

0000 49 44 30 31 37 3b ID017;

kenwood_transaction: read_string(expected=128, len=6)='ID017;'

kenwood_transaction: wrong reply ID for command OM

kenwood_transaction: retry_read=1, rs->rigport.retry=1

kenwood.c(624):kenwood_transaction returning2(-8) Protocol error


kenwood.c(676):kenwood_safe_transaction returning2(-8) Protocol error


2:rig.c(7478):async_data_handler_stop entered

2:rig.c(7508):async_data_handler_stop returning(0)

ser_close: restoring options

1:rig.c(1273):rig_open returning(-8) Protocol error


Protocol error

Protocol error

while opening connection to rig


Timestamp: 2023-03-18T16:53:54.384Z

On Sat, Mar 18, 2023 at 9:47 AM Bruce Heimlich <bruceheimlich@...>
wrote:

Can you please tell me the path to that .dll?

On Sat, Mar 18, 2023 at 9:42 AM Bruce Heimlich <bruceheimlich@...>
wrote:

Hi Michael,

The rig is the K3. I will try the newer hamlib.

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 7:21 AM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

And what rig would this be?

Try the latest DLL from here....

https://n0nb.users.sourceforge.net/

Mike W9MDB








On Saturday, March 18, 2023 at 03:50:12 AM CDT, bruceheimlich@...
<bruceheimlich@...> wrote:





Hi,

I have a Windows 11 box, that was running WSJT-X V 2.54 without any
issues. After ugrading it to 2.61,same exact settings, I no longer have any
CAT control. Nothing I have tried works. If I roll it back to 2.54,
everything works fine.

I suspect it might be some kind of hamlib issue but cannot figure it
out. Other people say 2.61 works fine on their machines.

I am running the latest version of Windows 11 on a Microsift
SurfaceBook 2, if that helps.

I was going to try to do a 2.60 install to see if that works but cannot
find an installer package for that.

Any suggestions? I am wasting so much time with this and driving me
cookoo. :-)

Thanks!


-Bruce

Can I use the hamlib.dll for 2.54 on 2.61 and where would I locate that?
Would there be any operational issues?

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 9:55 AM Bruce Heimlich <bruceheimlich@...>
wrote:

I tried the latest hamlib but still getting the same error and why does

it

always refer to kenwood when the rig is a K3?:

Hamlib error: kenwood_transaction: read_string(expected=128,
len=4)='K22;'

kenwood_transaction: wrong reply K2 for command OM

kenwood_transaction: retry_read=0, rs->rigport.retry=1

read_string_generic called, rxmax=128 direct=1, expected_len=1

read_string_generic(): RX 6 characters, direct=1

0000 49 44 30 31 37 3b ID017;

kenwood_transaction: read_string(expected=128, len=6)='ID017;'

kenwood_transaction: wrong reply ID for command OM

kenwood_transaction: retry_read=1, rs->rigport.retry=1

kenwood.c(624):kenwood_transaction returning2(-8) Protocol error


kenwood.c(676):kenwood_safe_transaction returning2(-8) Protocol error


2:rig.c(7478):async_data_handler_stop entered

2:rig.c(7508):async_data_handler_stop returning(0)

ser_close: restoring options

1:rig.c(1273):rig_open returning(-8) Protocol error


Protocol error

Protocol error

while opening connection to rig


Timestamp: 2023-03-18T16:53:54.384Z

On Sat, Mar 18, 2023 at 9:47 AM Bruce Heimlich <bruceheimlich@...>
wrote:

Can you please tell me the path to that .dll?

On Sat, Mar 18, 2023 at 9:42 AM Bruce Heimlich <bruceheimlich@...

wrote:

Hi Michael,

The rig is the K3. I will try the newer hamlib.

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 7:21 AM Michael Black via groups.io

<mdblack98=

yahoo.com@groups.io> wrote:

And what rig would this be?

Try the latest DLL from here....

https://n0nb.users.sourceforge.net/

Mike W9MDB








On Saturday, March 18, 2023 at 03:50:12 AM CDT,

bruceheimlich@...

<bruceheimlich@...> wrote:





Hi,

I have a Windows 11 box, that was running WSJT-X V 2.54 without any
issues. After ugrading it to 2.61,same exact settings, I no longer

have any

CAT control. Nothing I have tried works. If I roll it back to 2.54,
everything works fine.

I suspect it might be some kind of hamlib issue but cannot figure it
out. Other people say 2.61 works fine on their machines.

I am running the latest version of Windows 11 on a Microsift
SurfaceBook 2, if that helps.

I was going to try to do a 2.60 install to see if that works but

cannot

find an installer package for that.

Any suggestions? I am wasting so much time with this and driving me
cookoo. :-)

Thanks!


-Bruce

why does it always refer to kenwood when the rig is a K3?

Bruce
The answer to your question is yes. Mike W9MDB has detailed how to do that
a number of times; if you peruse the wsjt message archive you should be
able to find detailed instructions. You could also do a search using File
Manager f or that DLL.

Dennis W1UE

On Sat, Mar 18, 2023 at 13:52 Bruce Heimlich <bruceheimlich@...>
wrote:

Can I use the hamlib.dll for 2.54 on 2.61 and where would I locate that?
Would there be any operational issues?

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 9:55 AM Bruce Heimlich <bruceheimlich@...>
wrote:

I tried the latest hamlib but still getting the same error and why does

it

always refer to kenwood when the rig is a K3?:

Hamlib error: kenwood_transaction: read_string(expected=128,
len=4)='K22;'

kenwood_transaction: wrong reply K2 for command OM

kenwood_transaction: retry_read=0, rs->rigport.retry=1

read_string_generic called, rxmax=128 direct=1, expected_len=1

read_string_generic(): RX 6 characters, direct=1

0000 49 44 30 31 37 3b ID017;

kenwood_transaction: read_string(expected=128, len=6)='ID017;'

kenwood_transaction: wrong reply ID for command OM

kenwood_transaction: retry_read=1, rs->rigport.retry=1

kenwood.c(624):kenwood_transaction returning2(-8) Protocol error


kenwood.c(676):kenwood_safe_transaction returning2(-8) Protocol error


2:rig.c(7478):async_data_handler_stop entered

2:rig.c(7508):async_data_handler_stop returning(0)

ser_close: restoring options

1:rig.c(1273):rig_open returning(-8) Protocol error


Protocol error

Protocol error

while opening connection to rig


Timestamp: 2023-03-18T16:53:54.384Z

On Sat, Mar 18, 2023 at 9:47 AM Bruce Heimlich <

bruceheimlich@...>

wrote:

Can you please tell me the path to that .dll?

On Sat, Mar 18, 2023 at 9:42 AM Bruce Heimlich <

bruceheimlich@...

wrote:

Hi Michael,

The rig is the K3. I will try the newer hamlib.

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 7:21 AM Michael Black via groups.io

<mdblack98=

yahoo.com@groups.io> wrote:

And what rig would this be?

Try the latest DLL from here....

https://n0nb.users.sourceforge.net/

Mike W9MDB








On Saturday, March 18, 2023 at 03:50:12 AM CDT,

bruceheimlich@...

<bruceheimlich@...> wrote:





Hi,

I have a Windows 11 box, that was running WSJT-X V 2.54 without any
issues. After ugrading it to 2.61,same exact settings, I no longer

have any

CAT control. Nothing I have tried works. If I roll it back to 2.54,
everything works fine.

I suspect it might be some kind of hamlib issue but cannot figure it
out. Other people say 2.61 works fine on their machines.

I am running the latest version of Windows 11 on a Microsift
SurfaceBook 2, if that helps.

I was going to try to do a 2.60 install to see if that works but

cannot

find an installer package for that.

Any suggestions? I am wasting so much time with this and driving me
cookoo. :-)

Thanks!


-Bruce

Hi Dennis,

Thanks. I am trying to find the hamlib version for 2.54 but cannot seem to
find the 64 bit .exe. I would like to try using ot on 2.61 to see if it
will work.....
Thanks,

-Bruce

On Sat, Mar 18, 2023 at 11:00 AM Dennis W1UE <egan.dennis88@...>
wrote:

Bruce
The answer to your question is yes. Mike W9MDB has detailed how to do

that

a number of times; if you peruse the wsjt message archive you should be
able to find detailed instructions. You could also do a search using

File

Manager f or that DLL.

Dennis W1UE

On Sat, Mar 18, 2023 at 13:52 Bruce Heimlich <bruceheimlich@...>
wrote:

Can I use the hamlib.dll for 2.54 on 2.61 and where would I locate

that?

Would there be any operational issues?

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 9:55 AM Bruce Heimlich <

bruceheimlich@...>

wrote:

I tried the latest hamlib but still getting the same error and why

does

it

always refer to kenwood when the rig is a K3?:

Hamlib error: kenwood_transaction: read_string(expected=128,
len=4)='K22;'

kenwood_transaction: wrong reply K2 for command OM

kenwood_transaction: retry_read=0, rs->rigport.retry=1

read_string_generic called, rxmax=128 direct=1, expected_len=1

read_string_generic(): RX 6 characters, direct=1

0000 49 44 30 31 37 3b ID017;

kenwood_transaction: read_string(expected=128, len=6)='ID017;'

kenwood_transaction: wrong reply ID for command OM

kenwood_transaction: retry_read=1, rs->rigport.retry=1

kenwood.c(624):kenwood_transaction returning2(-8) Protocol error


kenwood.c(676):kenwood_safe_transaction returning2(-8) Protocol error


2:rig.c(7478):async_data_handler_stop entered

2:rig.c(7508):async_data_handler_stop returning(0)

ser_close: restoring options

1:rig.c(1273):rig_open returning(-8) Protocol error


Protocol error

Protocol error

while opening connection to rig


Timestamp: 2023-03-18T16:53:54.384Z

On Sat, Mar 18, 2023 at 9:47 AM Bruce Heimlich <

bruceheimlich@...>

wrote:

Can you please tell me the path to that .dll?

On Sat, Mar 18, 2023 at 9:42 AM Bruce Heimlich <

bruceheimlich@...

wrote:

Hi Michael,

The rig is the K3. I will try the newer hamlib.

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 7:21 AM Michael Black via groups.io

<mdblack98=

yahoo.com@groups.io> wrote:

And what rig would this be?

Try the latest DLL from here....

https://n0nb.users.sourceforge.net/

Mike W9MDB








On Saturday, March 18, 2023 at 03:50:12 AM CDT,

bruceheimlich@...

<bruceheimlich@...> wrote:





Hi,

I have a Windows 11 box, that was running WSJT-X V 2.54 without

any

issues. After ugrading it to 2.61,same exact settings, I no longer

have any

CAT control. Nothing I have tried works. If I roll it back to

2.54,

everything works fine.

I suspect it might be some kind of hamlib issue but cannot figure

it

out. Other people say 2.61 works fine on their machines.

I am running the latest version of Windows 11 on a Microsift
SurfaceBook 2, if that helps.

I was going to try to do a 2.60 install to see if that works but

cannot

find an installer package for that.

Any suggestions? I am wasting so much time with this and driving

me

cookoo. :-)

Thanks!


-Bruce

Bruce
Download and unzip2.54. It’s in there

On Sat, Mar 18, 2023 at 16:08 Bruce Heimlich <bruceheimlich@...>
wrote:

Hi Dennis,

Thanks. I am trying to find the hamlib version for 2.54 but cannot seem

to

find the 64 bit .exe. I would like to try using ot on 2.61 to see if it
will work.....
Thanks,

-Bruce

On Sat, Mar 18, 2023 at 11:00 AM Dennis W1UE <egan.dennis88@...>
wrote:

Bruce
The answer to your question is yes. Mike W9MDB has detailed how to do

that

a number of times; if you peruse the wsjt message archive you should be
able to find detailed instructions. You could also do a search using

File

Manager f or that DLL.

Dennis W1UE

On Sat, Mar 18, 2023 at 13:52 Bruce Heimlich <bruceheimlich@...>
wrote:

Can I use the hamlib.dll for 2.54 on 2.61 and where would I locate

that?

Would there be any operational issues?

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 9:55 AM Bruce Heimlich <

bruceheimlich@...>

wrote:

I tried the latest hamlib but still getting the same error and why

does

it

always refer to kenwood when the rig is a K3?:

Hamlib error: kenwood_transaction: read_string(expected=128,
len=4)='K22;'

kenwood_transaction: wrong reply K2 for command OM

kenwood_transaction: retry_read=0, rs->rigport.retry=1

read_string_generic called, rxmax=128 direct=1, expected_len=1

read_string_generic(): RX 6 characters, direct=1

0000 49 44 30 31 37 3b ID017;

kenwood_transaction: read_string(expected=128, len=6)='ID017;'

kenwood_transaction: wrong reply ID for command OM

kenwood_transaction: retry_read=1, rs->rigport.retry=1

kenwood.c(624):kenwood_transaction returning2(-8) Protocol error


kenwood.c(676):kenwood_safe_transaction returning2(-8) Protocol

error

2:rig.c(7478):async_data_handler_stop entered

2:rig.c(7508):async_data_handler_stop returning(0)

ser_close: restoring options

1:rig.c(1273):rig_open returning(-8) Protocol error


Protocol error

Protocol error

while opening connection to rig


Timestamp: 2023-03-18T16:53:54.384Z

On Sat, Mar 18, 2023 at 9:47 AM Bruce Heimlich <

bruceheimlich@...>

wrote:

Can you please tell me the path to that .dll?

On Sat, Mar 18, 2023 at 9:42 AM Bruce Heimlich <

bruceheimlich@...

wrote:

Hi Michael,

The rig is the K3. I will try the newer hamlib.

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 7:21 AM Michael Black via groups.io

<mdblack98=

yahoo.com@groups.io> wrote:

And what rig would this be?

Try the latest DLL from here....

https://n0nb.users.sourceforge.net/

Mike W9MDB








On Saturday, March 18, 2023 at 03:50:12 AM CDT,

bruceheimlich@...

<bruceheimlich@...> wrote:





Hi,

I have a Windows 11 box, that was running WSJT-X V 2.54 without

any

issues. After ugrading it to 2.61,same exact settings, I no

longer

have any

CAT control. Nothing I have tried works. If I roll it back to

2.54,

everything works fine.

I suspect it might be some kind of hamlib issue but cannot

figure

it

out. Other people say 2.61 works fine on their machines.

I am running the latest version of Windows 11 on a Microsift
SurfaceBook 2, if that helps.

I was going to try to do a 2.60 install to see if that works but

cannot

find an installer package for that.

Any suggestions? I am wasting so much time with this and driving

me

cookoo. :-)

Thanks!


-Bruce

I can only find a .exe download not zip..

Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0


C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location


For Linux put it in
~/.config
The WSJT-X_Rigcontrol.log file will be here:
~/.local/share/WSJT-X


For MacOS put it in
/Users/[username]/Library/Preferences

Restart WSJT-X and duplicate the problem.
Shut down WSJT-X


Then send me the WSJT-X_RigControl.log file
Mike W9MDB








On Saturday, March 18, 2023 at 12:52:17 PM CDT, Bruce Heimlich <
bruceheimlich@...> wrote:





I tried the latest hamlib but still getting the same error and why does it
always refer to kenwood when the rig is a K3?:

Hamlib error: kenwood_transaction: read_string(expected=128, len=4)='K22;'

kenwood_transaction: wrong reply K2 for command OM

kenwood_transaction: retry_read=0, rs->rigport.retry=1

read_string_generic called, rxmax=128 direct=1, expected_len=1

read_string_generic(): RX 6 characters, direct=1

0000 49 44 30 31 37 3b ID017;

kenwood_transaction: read_string(expected=128, len=6)='ID017;'

kenwood_transaction: wrong reply ID for command OM

kenwood_transaction: retry_read=1, rs->rigport.retry=1

kenwood.c(624):kenwood_transaction returning2(-8) Protocol error


kenwood.c(676):kenwood_safe_transaction returning2(-8) Protocol error


2:rig.c(7478):async_data_handler_stop entered

2:rig.c(7508):async_data_handler_stop returning(0)

ser_close: restoring options

1:rig.c(1273):rig_open returning(-8) Protocol error


Protocol error

Protocol error

while opening connection to rig


Timestamp: 2023-03-18T16:53:54.384Z

On Sat, Mar 18, 2023 at 9:47 AM Bruce Heimlich <bruceheimlich@...>
wrote:

Can you please tell me the path to that .dll?

On Sat, Mar 18, 2023 at 9:42 AM Bruce Heimlich <bruceheimlich@...>
wrote:

Hi Michael,

The rig is the K3. I will try the newer hamlib.

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 7:21 AM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

And what rig would this be?

Try the latest DLL from here....

https://n0nb.users.sourceforge.net/

Mike W9MDB








On Saturday, March 18, 2023 at 03:50:12 AM CDT,

bruceheimlich@...

<bruceheimlich@...> wrote:





Hi,

I have a Windows 11 box, that was running WSJT-X V 2.54 without any
issues. After ugrading it to 2.61,same exact settings, I no longer

have any

CAT control. Nothing I have tried works. If I roll it back to 2.54,
everything works fine.

I suspect it might be some kind of hamlib issue but cannot figure it
out. Other people say 2.61 works fine on their machines.

I am running the latest version of Windows 11 on a Microsift

SurfaceBook

2, if that helps.

I was going to try to do a 2.60 install to see if that works but cannot
find an installer package for that.

Any suggestions? I am wasting so much time with this and driving me
cookoo. :-)

Thanks!


-Bruce

Yup

https://www.dropbox.com/s/snmkzu8eif89yqs/libhamlib-4.dll?dl=0

Mike W9MDB







On Sunday, March 19, 2023 at 05:20:09 PM CDT, Bruce Heimlich <
bruceheimlich@...> wrote:





Hi Michael,

Were you able to throw together that modified .dll file?

Bruce

On Sat, Mar 18, 2023 at 3:21 PM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0


C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location


For Linux put it in
~/.config
The WSJT-X_Rigcontrol.log file will be here:
~/.local/share/WSJT-X


For MacOS put it in
/Users/[username]/Library/Preferences

Restart WSJT-X and duplicate the problem.
Shut down WSJT-X


Then send me the WSJT-X_RigControl.log file
Mike W9MDB








On Saturday, March 18, 2023 at 12:52:17 PM CDT, Bruce Heimlich <
bruceheimlich@...> wrote:





I tried the latest hamlib but still getting the same error and why does

it

always refer to kenwood when the rig is a K3?:

Hamlib error: kenwood_transaction: read_string(expected=128,

len=4)='K22;'

kenwood_transaction: wrong reply K2 for command OM

kenwood_transaction: retry_read=0, rs->rigport.retry=1

read_string_generic called, rxmax=128 direct=1, expected_len=1

read_string_generic(): RX 6 characters, direct=1

0000 49 44 30 31 37 3b ID017;

kenwood_transaction: read_string(expected=128, len=6)='ID017;'

kenwood_transaction: wrong reply ID for command OM

kenwood_transaction: retry_read=1, rs->rigport.retry=1

kenwood.c(624):kenwood_transaction returning2(-8) Protocol error


kenwood.c(676):kenwood_safe_transaction returning2(-8) Protocol error


2:rig.c(7478):async_data_handler_stop entered

2:rig.c(7508):async_data_handler_stop returning(0)

ser_close: restoring options

1:rig.c(1273):rig_open returning(-8) Protocol error


Protocol error

Protocol error

while opening connection to rig


Timestamp: 2023-03-18T16:53:54.384Z

On Sat, Mar 18, 2023 at 9:47 AM Bruce Heimlich <bruceheimlich@...>
wrote:

Can you please tell me the path to that .dll?

On Sat, Mar 18, 2023 at 9:42 AM Bruce Heimlich <

bruceheimlich@...>

wrote:

Hi Michael,

The rig is the K3. I will try the newer hamlib.

Thanks!

-Bruce

On Sat, Mar 18, 2023 at 7:21 AM Michael Black via groups.io

<mdblack98=

yahoo.com@groups.io> wrote:

And what rig would this be?

Try the latest DLL from here....

https://n0nb.users.sourceforge.net/

Mike W9MDB








On Saturday, March 18, 2023 at 03:50:12 AM CDT,

bruceheimlich@...

<bruceheimlich@...> wrote:





Hi,

I have a Windows 11 box, that was running WSJT-X V 2.54 without any
issues. After ugrading it to 2.61,same exact settings, I no longer

have any

CAT control. Nothing I have tried works. If I roll it back to 2.54,
everything works fine.

I suspect it might be some kind of hamlib issue but cannot figure it
out. Other people say 2.61 works fine on their machines.

I am running the latest version of Windows 11 on a Microsift

SurfaceBook

2, if that helps.

I was going to try to do a 2.60 install to see if that works but

cannot

find an installer package for that.

Any suggestions? I am wasting so much time with this and driving me
cookoo. :-)

Thanks!


-Bruce