|
|
Post by K0XM on Mar 22, 2022 19:52:21 GMT
A friend upgraded to 158, and he noticed it took a long time for VFO A to move and then VFO B was 5-6 seconds later. He called and I moved him back to 156 and all was fine. This was through HamLib. Has anyone else seen this?
Chuck K0XM
|
|
|
|
Post by w9mdb on Mar 22, 2022 19:58:17 GMT
Fir thing try...then if that doesn't work follow the next message. New hamlib for Windows installation directions #1 Shut down WSJTX/JTDX #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times. If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there. n0nb.users.sourceforge.net/dll32/libhamlib-4.dlln0nb.users.sourceforge.net/dll64/libhamlib-4.dll#3 If you don't save directly you need to open a file browser and move the file that way. If you're not familiar with that here's a video on the file browser - www.youtube.com/watch?v=AyVqCJrs9dkMike W9MDB |
|
|
|
Post by w9mdb on Mar 22, 2022 19:58:45 GMT
2nd thing to try if #1 above does not solve the problem. Download the debug version of JTDX MS Windows, 64bit cloud.mail.ru/public/7ksV/ihDgYKHgCchecksum jtdx-2.2.159-rc4-debug-win64.exe SHA-256: BB46D1531DF3FCA63F7FA1CE9E5A08AE418685988A2488490A730E8B2D00FBAA Two logs will be recorded: in %TEMP% directory, file name is JTDX_trace.log in JTDX QSO log directory, file name is jtdx_debug.txt Duplicate the problem and send me the logs Mike W9MDB |
|
|
|
Post by K0XM on Mar 23, 2022 13:08:32 GMT
Ok Mike, I will try that later today.
|
|
|
|
Post by K0XM on Apr 5, 2022 19:49:27 GMT
Mike, All is well with the new hamlib....
Chuck K0XM
|
|
