[PE4BAS] (Guest post DB6LL) WSJT-X and JTDX sharing logs

[PE4BAS via rec.radio.amateur.moderated Admin]

PE4BAS Amateur Radio Weblog

///////////////////////////////////////////
(Guest post DB6LL) WSJT-X and JTDX sharing logs

Posted: 25 Feb 2021 11:14 AM PST
https://pe4bas.blogspot.com/2021/02/guest-post-db6ll-wsjt-x-and-jtdx.html


The case: Why should you use both programs on digimode? Well, WSJT-X
contains other modes like the new FST. Q65 and MSK, JTDX contains T10 and
other features. So sometimes you really need another package to work
another digimode or use other features. Since many HAMs use both WSJT-X and
JTDX making contacts it would be nice to see what you worked (B4, DXCC
etc.) in both software packages. Of course you can make a copy of
wsjtx_log.adi and paste it in both WSJT-X/JTDX directory every day. But it
is possible to automate something like this so WSJT-X and JTDX share the
same ADIF log. DB6LL Hartmut wrote about this for a German language
digimode FB page. I asked him if I could use this for my blog and he
responded by translate the whole document in English to share it with you
all. Isn't that great!
Before you mess up completely I advice to not try this when you don't know
much about computers, directories and DOS commands. Please make a back-up
from your wsjtx_adi files before trying to modify things.


A shared LOG file for WSJT-X and JTDX under Windows
There is a way to share wsjt_log.adi in Windows (7, 8.1 and 10) WSJT-X and
JTDXi. This makes it easier to work alternately with WSJT-X and JTDX and
both programmes and also JTAlert show all callsigns e.g. with B4 that you
have already worked. This trick works with the command mklink on the
command line level and is not quite trivial (keyword: hard link type
symlink). I have to assume a certain amount of computer knowledge so that
this explanation does not go on forever.
And as always: following these instructions is at your own risk!
<username> is the Windows user name on your system. In my case, I log in as
DB6LL, so there is a directory with the name DB6LL on my PC:



By the way, it can't hurt to make a back-up of the two wsjtx_log-adi files
before following this guide. You will find this file in the respective
directories:
C:\users\<username>\appdata\local\wsjt-x\
and
C:\users\<username>\appdata\local\jtdx\
First, open the "Run" window with the Windows key & R. Then enter the
command cmd.exe in the "Open" line and press ctrl+shift+Enter and answer
yes when windows is asking you if it is allright. You will run the command
as admin now.
A window called "Windows Command Prompt" opens.
The cursor flashes in the line C:\WINDOWS\system32
Enter the command cd c:\users\<username>\appdata\local\jtdx\ and Enter.
You are now in the JTDX directory where, among other things, the logbook
file wsjtx_log-adi is located.


With the command del C:\users\<username>\appdata\local\wsjt-x\wsjtx_log.adi
you first delete the log file of WSJT-X in the target directory. (Of course
this is when you want to use your JTDX wsjtx_log.adi as master).




Now you create a new
mklink /H C:\users\<username> \appdata\local\wsjt-x\wsjtx_log.adi
wsjtx_log.adi
a HardLink of the file wsjtx_log.adi from the JTDX directory to the WSJT-X
directory. It is then one and the same file with one name, which now
appears to be in two places.

If you read the message in the CMD window: Hardlink created for... in the
CMD window, the command has been executed correctly and you can see the
JDTX log file in the WSJT-X directory.
In future, both programmes will write the logged stations to the same log
file and display the same information (B4) in colours.
Note: The add-on programme JTAlert analyses the contacts from your main
logbook and the information does not have to match the stations in
wsjtx_log.adi, as it reports all contacts in all modes....
Good luck and in future always have a correct overview of which station you
already have in the log.

vy73 Hartmut, DB6LL
(edited by Bas, PE4BAS)
I've tested the above trick myself and it works very well.