locked [Ham-Apps] Re: [jt65-hf] JT-Alert 1.5 Need Help making it log to DX-Keeper
Laurie, VK3AMA <groups03@...>
Hi David,toggle quoted messageShow quoted text
I have added additional troubleshooting popup warnings of critical conditions with JT-Alert and Logging and will be in 1.5.1
Are you getting a popup failure message when logging to DXKeeper? If not, it is most likely the recently identified missing backslash at the end of the JT65-HF Log path. Please see the message titled "## IMPORTANT ## - Bug in JT-Alert 1.5.0 logging."
If you have already confirmed that the Backslash is not the problem, I need to have a look at the session file JT-Alert creates. Under XP, have a look at the following path
C:\Documents and Settings\\Local Settings\Application Data\Ham-Apps\JT-Alert\\sessions\
Under Win7 (I assume also Vista) have a look at this path
substituting your Windows username and the Callsign used with JT-Alert. In that directory will be several files.
First, run JT-Alert and attempt to log a QSO so that the failure gets recorded in the session file, stop JT-Alert and then email me the sessions.txt file from the above directory.
de Laurie, VK3AMA
On 18-October-2011 23:26, David Westbrook wrote:
Laurie -- I just noticed I have the same issue ...