VarAC v8.0.6 (latest version) does not log to the ADI file even though it is set in INI as: ADIFLogPath=C:\VarAC\VarAC_qso_log.adi
In fact, my VarAC has not logged to that file since June 12, 2023.
Instead, it logs in non-ADI format to a new file, VarAC.log (which is mentioned nowhere in the INI file).
So there is no usable ADI file that can be imported into other logging apps, such as QRZ.com
What's the story? Thanks.
73
Lyn, W0LEN
My apologies to all (esp. Irad ...).
Yes, my QSOs are being logged correctly. The problem was misstated. I was advised that v8.0.6 no longer logs Beacons as it once did. They disappear after a time, and cannot be retrieved.
I have no way to verify.
73
Lyn, WØLEN
I carefully backed up the critical files and reinstalled it.
Looked at the ADIF file location to make sure it matched.
Problem disappeared and I will probably never know why because I made sure the ADIF file location was correct.
TU Irad. Great piece of Software.
Mark / W7EAZ
I am unable to determin the cause of what you are experiancing. Best thing would be in this case is :
Backup your VarAC.db / VarAC_qso_log.adi / VarAC.ini files
Uninstall all VarAC instances and re-install in C:\VarAC
Make sure VarAC is closed
Place all the files from step 1 into the c:\VarAC directory (ru n over the defauly files)
Start VarAC
Irad -
I found the 2 instances shown on attacheg JPG image. Both are indeed in the C:\VarAC folder.
Tha one labeled "BACKUP" is the last file that has any log info (from June 9).
I created the other file when I first noticed the problem, and nothing has been written to it.
I used to be able to load these files into my existing logs without error, so apparently the "adi" file is close enough to "adif" to be recognizable as such.
73
Lyn, WØLEN
Irad -
I forgot to mention that yes - I do run VarAC as Administrator.
Lyn
The main VarAC Logs drop down menu does not open the current log as defined in the .ini file.
I have the same issue as noted above by Lyn. It should be:
C:\Program Files (x86)\VarAC\VarAC_qso_log.adi
During reinstallation I saw the following path blink by and I found the 'real' log in:
C:\Users\End User\AppData\Local\VirtualStore\Program Files (x86)\VarAC
In order to find it, I had to unhide system files and follow the path because MS in their infinite wisdom changed where AppData is located under some hidden folders. ARRRRGH!
ALSO, I just noticed that when I start VarAC as administrator I get a totally different motif than when I start it as a user.
Pardon my ignorance on how MS starts programs under Admin mode but this is just not behaving as I was anticipating.
The first photo is how I start it normally, the second is when I start it as Admin:
I start the same program from the same desktop icon just as user or admin.
Puzzling.
Mark / W7EAZ
if it doesn't log - there should be an error message on the VarAC.log . this is probably what you see what you say "it logs in non-ADI format to a new file, VarAC.log ".
Please attach the section of the log where it shows this.
My guess is that it is a permissions issues... you probably need to run VarAC as administrator...
But if you add the log file section I can guide you to where the problem might be.
Irad