locked Saved Data #WSJTX_config


Robert Snyder
 

Using WSJT-X V2.5.4 and Windows 10 64bit
I recently had a total wipeout of my computer and lost all my ADIF files (hundreds of FT's, years worth) plus all other modes. Thankfully I still have my QRZ.COm with all the QSO's. The problem being is when I save an FT QSO in WSJT-x, I can't locate it in the saved directory, as it no longer exists (I had to install a completely new Win10). Can I change the saved file to a file I can locate? The install program puts the saved data in "C:/Users/shogu/AppData/Local/WSJT-X". This file no longer exists in my file system. I find what I have is "C:/Users/shogu/shogu/AppData/Local/WSJT-X". How do I change the "Save Directory" to what I have.? I'm unable to log any QSO's except manually. I made about ten QSO yesterday and they were saved, but I can't get them in the right directory as it doesn't exist.... Same with the AzEl Directory.

Thanks to any who can help.

Bob/KH6Y


Joseph Rork
 

Bob, have you tried any advanced recovery on that drive? Typically you can get those files back.

On Aug 18, 2022, at 12:33 PM, Robert Snyder <shogunsent@...> wrote:

Using WSJT-X V2.5.4 and Windows 10 64bit
I recently had a total wipeout of my computer and lost all my ADIF files (hundreds of FT's, years worth) plus all other modes. Thankfully I still have my QRZ.COm with all the QSO's. The problem being is when I save an FT QSO in WSJT-x, I can't locate it in the saved directory, as it no longer exists (I had to install a completely new Win10). Can I change the saved file to a file I can locate? The install program puts the saved data in "C:/Users/shogu/AppData/Local/WSJT-X". This file no longer exists in my file system. I find what I have is "C:/Users/shogu/shogu/AppData/Local/WSJT-X". How do I change the "Save Directory" to what I have.? I'm unable to log any QSO's except manually. I made about ten QSO yesterday and they were saved, but I can't get them in the right directory as it doesn't exist.... Same with the AzEl Directory.

Thanks to any who can help.

Bob/KH6Y





Tim Dawson
 

One option is to simply recreate the missing directory tree . . . Maybe not ideal, but it would get things back quickly.

On August 18, 2022 11:33:07 AM CDT, Robert Snyder <shogunsent@...> wrote:
Using WSJT-X V2.5.4 and Windows 10 64bit
I recently had a total wipeout of my computer and lost all my ADIF files (hundreds of FT's, years worth) plus all other modes. Thankfully I still have my QRZ.COm with all the QSO's. The problem being is when I save an FT QSO in WSJT-x, I can't locate it in the saved directory, as it no longer exists (I had to install a completely new Win10). Can I change the saved file to a file I can locate? The install program puts the saved data in "C:/Users/shogu/AppData/Local/WSJT-X". This file no longer exists in my file system. I find what I have is "C:/Users/shogu/shogu/AppData/Local/WSJT-X". How do I change the "Save Directory" to what I have.? I'm unable to log any QSO's except manually. I made about ten QSO yesterday and they were saved, but I can't get them in the right directory as it doesn't exist.... Same with the AzEl Directory.

Thanks to any who can help.

Bob/KH6Y




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Reino Talarmo
 

Hi Bob,
I don't know why you got that directory ../shogu/shogu/.. in first place. Where wsjt-x directs you by the File | Open log directory. Your logging file wsjtx_log.adi should be there. There should be also file wsjt-x.ini. That file contains information of the AzEl directory.

If the Open log directory fails, then probably best action could be to re-install wsjt-x, perhaps to another directory that can be defined during the installation.

By the way you can download you QSOs as an adi file from the QRZ.com, then you may name it as wsjtx_log.adi and put into the Log directory.

73, Reino OH3mA

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Robert Snyder
Sent: 18. elokuutata 2022 19:33
To: main@WSJTX.groups.io
Subject: [WSJTX] Saved Data #WSJTX_config

Using WSJT-X V2.5.4 and Windows 10 64bit I recently had a total wipeout of my computer and lost all my ADIF files (hundreds of FT's, years worth) plus all other modes. Thankfully I still have my QRZ.COm with all the QSO's. The problem being is when I save an FT QSO in WSJT-x, I can't locate it in the saved directory, as it no longer exists (I had to install a completely new Win10). Can I change the saved file to a file I can locate? The install program puts the saved data in "C:/Users/shogu/AppData/Local/WSJT-X". This file no longer exists in my file system. I find what I have is "C:/Users/shogu/shogu/AppData/Local/WSJT-X". How do I change the "Save Directory" to what I have.? I'm unable to log any QSO's except manually. I made about ten QSO yesterday and they were saved, but I can't get them in the right directory as it doesn't exist.... Same with the AzEl Directory.

Thanks to any who can help.

Bob/KH6Y


 

Well thanks for all the help. I got it working this morning. I did a fresh install with the frame work 6.0 and reloaded JTALET and WSJT-X . Now it's working great.

73's to all for the help.

Dave NU4N

On 8/18/2022 1:05 PM, Reino Talarmo wrote:
Hi Bob,
I don't know why you got that directory ../shogu/shogu/.. in first place. Where wsjt-x directs you by the File | Open log directory. Your logging file wsjtx_log.adi should be there. There should be also file wsjt-x.ini. That file contains information of the AzEl directory.

If the Open log directory fails, then probably best action could be to re-install wsjt-x, perhaps to another directory that can be defined during the installation.

By the way you can download you QSOs as an adi file from the QRZ.com, then you may name it as wsjtx_log.adi and put into the Log directory.

73, Reino OH3mA

-----Original Message-----
From:main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Robert Snyder
Sent: 18. elokuutata 2022 19:33
To:main@WSJTX.groups.io
Subject: [WSJTX] Saved Data #WSJTX_config

Using WSJT-X V2.5.4 and Windows 10 64bit I recently had a total wipeout of my computer and lost all my ADIF files (hundreds of FT's, years worth) plus all other modes. Thankfully I still have my QRZ.COm with all the QSO's. The problem being is when I save an FT QSO in WSJT-x, I can't locate it in the saved directory, as it no longer exists (I had to install a completely new Win10). Can I change the saved file to a file I can locate? The install program puts the saved data in "C:/Users/shogu/AppData/Local/WSJT-X". This file no longer exists in my file system. I find what I have is "C:/Users/shogu/shogu/AppData/Local/WSJT-X". How do I change the "Save Directory" to what I have.? I'm unable to log any QSO's except manually. I made about ten QSO yesterday and they were saved, but I can't get them in the right directory as it doesn't exist.... Same with the AzEl Directory.

Thanks to any who can help.

Bob/KH6Y









--
73's Dave NU4N
--
*73'S DAVE NU4N*


Craig
 

Hey Bob - any chance of setting your OLD system drive to a data drive using
the drive on-board jumpers and then seeing if you can read that data on the
new system? Just a thought... I have done that before when the system
drive crashes...

Good luck.

Craig NZ4CW

On Thu, Aug 18, 2022 at 12:33 PM Robert Snyder <shogunsent@...> wrote:

Using WSJT-X V2.5.4 and Windows 10 64bit
I recently had a total wipeout of my computer and lost all my ADIF files
(hundreds of FT's, years worth) plus all other modes. Thankfully I still
have my QRZ.COm with all the QSO's. The problem being is when I save an FT
QSO in WSJT-x, I can't locate it in the saved directory, as it no longer
exists (I had to install a completely new Win10). Can I change the saved
file to a file I can locate? The install program puts the saved data in
"C:/Users/shogu/AppData/Local/WSJT-X". This file no longer exists in my
file system. I find what I have is
"C:/Users/shogu/shogu/AppData/Local/WSJT-X". How do I change the "Save
Directory" to what I have.? I'm unable to log any QSO's except manually.
I made about ten QSO yesterday and they were saved, but I can't get them in
the right directory as it doesn't exist.... Same with the AzEl Directory.

Thanks to any who can help.

Bob/KH6Y






Robert Snyder
 

Wasn't a hard drive crash but a BIOS hangup. Got in a loop and couldn't get out no matter what I did so just decided to reload windows 10, saving programs and files. It worked but lost half the programs and the associated files. WSJT was one of the programs lost so had to reload it but ended up with the two users "shogun" but the first user doesn't have AppData so wsjt-x can't find the directory which is down one more level. I'm going to reinstall WSJT this afternoon and see what I end up with. I've lost all my QSO'a (few thousand) so I guess will have to just put up with the dupes. I'm thinking I can download the ADIF file from QRZ and put everything in the directory (once I figure it out) and take it from there. I'm still looking for any way of changing the directory that is listed on the setup page to what I want. Mahalo (thanks) to all who might help. I'm sure I'm not the first fool to have this problem.

Bob/KH6Y


Pietro Molina
 

After installed wsjt, without run it, you can move the directory from
appdata/......./wsjtx where you want and then put in its place an hard link
(google it for instruction).

Pietro (via Tablet)

Il ven 19 ago 2022, 01:16 Robert Snyder <shogunsent@...> ha scritto:

Wasn't a hard drive crash but a BIOS hangup. Got in a loop and couldn't
get out no matter what I did so just decided to reload windows 10, saving
programs and files. It worked but lost half the programs and the associated
files. WSJT was one of the programs lost so had to reload it but ended up
with the two users "shogun" but the first user doesn't have AppData so
wsjt-x can't find the directory which is down one more level. I'm going to
reinstall WSJT this afternoon and see what I end up with. I've lost all my
QSO'a (few thousand) so I guess will have to just put up with the dupes.
I'm thinking I can download the ADIF file from QRZ and put everything in
the directory (once I figure it out) and take it from there. I'm still
looking for any way of changing the directory that is listed on the setup
page to what I want. Mahalo (thanks) to all who might help. I'm sure I'm
not the first fool to have this problem.

Bob/KH6Y







Martin G0HDB
 

On Fri, Aug 19, 2022 at 07:15 AM, Pietro Molina wrote:

After installed wsjt, without run it, you can move the directory from
appdata/......./wsjtx where you want and then put in its place an hard link
(google it for instruction).
I install WSJT-X onto my E: drive, which is a logical partition on the same physical disk as the C: drive, and I then put all what I call the 'user data' for WSJT-X into a folder titled E:\WSJT-X\User Data. I then use the WIndows 'mklink' command to create a directory junction between the default location on the C: drive and the User Data folder; the command to do this is:

mklink /J "C:\Users\<username>\AppData\Local\WSJT-X" "E:\WSJT-X\User Data"

This ensures that all of WSJT-X's data, including the wsjtx_log.adi log file, is stored on the E: drive but as far as WSJT-X is concerned it's still in the default location on the C: drive. Having the user data on the E: drive means that it's much less vulnerable to being lost in the event of a crash or other issue with the C: drive and it also means that the WSJT-X program plus all its user data can be backed-up from (and swiftly restored to) the E: drive without needing to take a backup of the user data from the default location on the C: drive.

HTH,

--
Martin G0HDB


Mike Koralewski K8VA
 

On Fri, Aug 19, 2022 at 11:52 AM, Martin G0HDB wrote:


On Fri, Aug 19, 2022 at 07:15 AM, Pietro Molina wrote:

After installed wsjt, without run it, you can move the directory from
appdata/......./wsjtx where you want and then put in its place an hard link
(google it for instruction).
I install WSJT-X onto my E: drive, which is a logical partition on the same
physical disk as the C: drive, and I then put all what I call the 'user data'
for WSJT-X into a folder titled E:\WSJT-X\User Data. I then use the WIndows
'mklink' command to create a directory junction between the default location
on the C: drive and the User Data folder; the command to do this is:

mklink /J "C:\Users\<username>\AppData\Local\WSJT-X" "E:\WSJT-X\User Data"

This ensures that all of WSJT-X's data, including the wsjtx_log.adi log file,
is stored on the E: drive but as far as WSJT-X is concerned it's still in the
default location on the C: drive. Having the user data on the E: drive means
that it's much less vulnerable to being lost in the event of a crash or other
issue with the C: drive and it also means that the WSJT-X program plus all its
user data can be backed-up from (and swiftly restored to) the E: drive without
needing to take a backup of the user data from the default location on the C:
drive.

HTH,

--
Martin G0HDB
Question Martin,?
If the E: Drive is a partition on the physical C: Drive... Woulnot a crash of the physical C: Drive also impact the E: partition?
I just ordered a new desktop, I do like the idea of mklinking, wonder if I can do it on a separate physical SSD drive.
-l
73 Mike 73 K8VA


Martin G0HDB
 

On Fri, Aug 19, 2022 at 07:38 PM, Mike Koralewski K8VA wrote:

Question Martin,?
If the E: Drive is a partition on the physical C: Drive... Woulnot a crash of
the physical C: Drive also impact the E: partition?
I just ordered a new desktop, I do like the idea of mklinking, wonder if I
can do it on a separate physical SSD drive.
Hello Mike, you're correct - a serious crash of the physical disk that hosts both the C: and E: drives could well result in the E: drive becoming inaccessible, so using a separate physical drive for E: would most definitely be preferable and more resilient. However...

Perhaps I've been fortunate over the years but I've found that it's very often the boot sector of a (rotating) drive that gets damaged or corrupted; whenever this has occurred I've found it has been possible to read and recover the contents of the E: drive (and often also the C: drive filesystem) because, presumably, the disk's partition table is still intact even though the O/S can't boot from the drive. I put the non-booting drive into a caddy that I connect via USB to a PC - usually Windows but sometimes Linux - and use a file explorer to try to recover stuff. There was one Linux app I found (I can't remember what it was!) that enabled me to recover almost everything that was on a badly corrupted hard disk that wasn't amenable to being explored using the usual tools.

FWIW, I take dual backups, to separate NAS's, of my PCs' E: drives every night and the PCs' C: drives every week.

73
--
Martin G0HDB


Radioman ZeroZero
 

You should see your previous windows in stall under c:users it may have been renamed by windows.

--
Thanks
Steve M0ZEH