locked Re: : Re: Re:: New - JTAlert 2.7.3 available - New Features, Changes and Fixes
toggle quoted messageShow quoted text
I uninstalled 2.7.3 this morning and went back to 2.7.1 this morning so that I could do some JT65/JT9 operating today. I will have to reinstall 2.7.3 to try your suggestion below. I will let you know the results. I did not mention it, but a station that I worked this morning showed up as Worked B4 in the log information area, but not in the call display area. I would not have called him if I had realized that we had worked before, but he graciously completed a contact with me. I guess I was just too quick on the trigger by double-clicking in the JTAlert call sign area.
I am using HRD Log 5.24 and my OS is Win 10/32. I will delete that debug file if you send me the location and name and send you a configuration as a test if it works.
From: "'Laurie, VK3AMA' groups08@... [HamApps]"
Sent: Thursday, May 26, 2016 4:10 PM
Subject: Re: : Re: [HamApps] Re:: New - JTAlert 2.7.3 available - New Features, Changes and Fixes
Are you using HRD logging, I suspect so.
Please visit the JTAlert Settings, Logging->HRD V5/V6 section and reselect the correct DSN or Log name for your HRD log. Even if the correct DSN/Log is currently shown, click the combo box and select the entry again (this is to force an update and save). After performing that task, close the Settings and JTAlert and then start JTAlert again.
Let me know if that corrects the problem.
A "Memory Configuration Error" may be due to an excessively large debug file, which is likely if there are HRD ODBC DSN errors being recorded. Let me know what Windows version tour running and I will advise the location of that debug file so it can be deleted.
de Laurie VK3AMA
On 26/05/2016 10:52 PM, Ed Wilson ed.wilson@... [HamApps] wrote: