Does it have to be on C: ? Hamlib doesn't work.

Fred k1io
Users

Posts: 42

Does it have to be on C: ? Hamlib doesn't work. Apr 27, 2024 21:25:05 GMT

Quote

Post by Fred k1io on Apr 27, 2024 21:25:05 GMT

I have my Windows 10 systems set up so that the C: drive is for system stuff and programs that insist on being there, while data and programs that don't need to be on C: are on D:. This reduces the potential loss of data should there be a catastrophic failure that requires the rebuilding of the system partition. Frankly it astonishes me how Windows tries to configure everything on the system partition, but then I suppose they have many users for whom the notion of partition management might be a bit much.

None of my digital mode programs work when I specify the radio (G90) as the device. Not JTDX, not WSJT-X (I now sometimes use the -Improved version, which copies some features from JTDX), not fldigi. I just point them all to flrig which takes care of everything (thanks Dave!). But why? JTDX doesn't give much of an error message when I try to use the COM3 interface (the Xiegu-provided serial to USB cable) directly, just that a protocol error prevents setting the frequency. WSJT-X-Improved however does. At one point it did mention IIRC \users\fred\hamlib, a directory that does not exist on my system. Here's the error I got today:

Hamlib error: icom.c(2511):icom_get_mode_without_data returning2(-11) Feature not available

icom.c(2617):icom_get_mode returning2(-11) Feature not available

network.c(1328): Starting multicast receiver
rig_get_mode(2913): freqMainA=18100055, modeMainA=, widthMainA=0
rig_get_mode(2913): freqMainB=18100500, modeMainB=, widthMainB=0
*0:cache.c(36):rig_set_cache_mode entered
rig_set_cache_mode(38): freqMainA=18100055, modeMainA=, widthMainA=0
rig_set_cache_mode(38): freqMainB=18100500, modeMainB=, widthMainB=0
rig_set_cache_mode(149): freqMainA=18100055, modeMainA=, widthMainA=0
rig_set_cache_mode(149): freqMainB=18100500, modeMainB=, widthMainB=0
*0:cache.c(150):rig_set_cache_mode returning(0)
*0:cache.c(150):rig_set_cache_mode returning(0)
rig_get_mode(2968): freqMainA=18100055, modeMainA=, widthMainA=0
rig_get_mode(2968): freqMainB=18100500, modeMainB=, widthMainB=0
event.c(85): Starting rig poll routine thread
*-1:rig.c(2972):rig_get_mode returning(-11) Feature not available

Feature not available
while getting current mode

There is file libhamlib-4.dll in the D:\JTDX64 directory. Also in D:\WSJT\wsjtx\bin, which is where the program that produced the above error is located.

So I'm wondering if WSJT and its derivatives are somewhere hard-coded to think that they are on C: . BTW I use a hard link so that the two programs write to the same log file.

Arvo ES1JA Administrator Posts: 429	Does it have to be on C: ? Hamlib doesn't work. Apr 28, 2024 16:44:09 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Arvo ES1JA on Apr 28, 2024 16:44:09 GMT No installation not needed to be on c:. Just copy libhamlib-4.dll from wsjtx improved installation.

Fred k1io Users Posts: 42	Does it have to be on C: ? Hamlib doesn't work. Apr 30, 2024 4:34:44 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Fred k1io on Apr 30, 2024 4:34:44 GMT Where do I copy it to? I already have it in the D:\JTDX\[ver]\bin directory.

w9mdb Users Posts: 252	Does it have to be on C: ? Hamlib doesn't work. Apr 30, 2024 4:42:22 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by w9mdb on Apr 30, 2024 4:42:22 GMT You copy the wsjtx\bin\libhamlib.dll to \JTDX\][ver]\bin

Fred k1io Users Posts: 42	Does it have to be on C: ? Hamlib doesn't work. May 3, 2024 14:08:14 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Fred k1io on May 3, 2024 14:08:14 GMT As noted in my previous reply, libhamlib-4.dll (the only one I see) is already there, and in the WSJTX directory, and it doesn't work in either case.

Fred k1io
Users

Posts: 42

Does it have to be on C: ? Hamlib doesn't work. May 4, 2024 4:36:53 GMT

Quote

Post by Fred k1io on May 4, 2024 4:36:53 GMT

Going through some old hamlib documentation, I saw that it likes to be in the system Path. That's a blast from the past of DOS days... but I had hamlib 4.6 in its own D:\Program Files directory so I added that to the path environment variable. Now JTDX doesn't throw the same errors. It "almost" works with my G90. It gives the green go-ahead that CAT is connected, and can change bands, but doing so creates quite the racket as the radio jumps around several times, and it doesn't actually work right. Then after a few tries to use it, JTDX gives an error that it isn't reading frequency from the radio. SO I went back to flrig.

It is possible that hamlib just doesn't like the G90. I tried it with both its G90 and IC-7100 settings (that is what the G90's CI-V instruction set is said to be roughly based on).

w9mdb
Users

Posts: 252

Does it have to be on C: ? Hamlib doesn't work. May 4, 2024 4:51:09 GMT

Quote

Post by w9mdb on May 4, 2024 4:51:09 GMT

Let's do some testing with WSJT-X improved first.
Update the hamlib in WSJT-X improved in the bottom left of the Radio tab.
Then turn on Save/Diagnostic mode -- restart WSJT-X -- recreate the problem -- shut it down -- and send me the WSJT-X_RigControl.log file that will be on your desktop in the "logs" directory.

Fred k1io
Users

Posts: 42

Does it have to be on C: ? Hamlib doesn't work. May 5, 2024 5:11:46 GMT

Quote

Post by Fred k1io on May 5, 2024 5:11:46 GMT

I sent you a private message with a lot of RigControl -- it is too long to want to put here. Basically WSJT-X-I acted the same as before. I had already used the update hamlib function in WSJT-X-Improved and it didn't do anything, and having another albeit earlier hamlib 4.6 in the Path didn't impact that program either.

Does it have to be on C: ? Hamlib doesn't work.

Post by Fred k1io on Apr 27, 2024 21:25:05 GMT

Post by Arvo ES1JA on Apr 28, 2024 16:44:09 GMT

Post by Fred k1io on Apr 30, 2024 4:34:44 GMT

Post by w9mdb on Apr 30, 2024 4:42:22 GMT

Post by Fred k1io on May 3, 2024 14:08:14 GMT

Post by Fred k1io on May 4, 2024 4:36:53 GMT

Post by w9mdb on May 4, 2024 4:51:09 GMT

Post by Fred k1io on May 5, 2024 5:11:46 GMT