OK John, Not getting a "success" or "fail" popup usually means that JT-Alert didn't try and log anything because it didn't detect a change in the JT65-HF log file. When you added the backslash to the

Good evening Laurie, I finally realized what you ment when you refered to the "Log Contact window (big Daaaaa on my part). However it already has a backslash at the end of it. (by the way for some rea

Tnx I just did what you suggested and HRD uses a LOT less than jt65 hf and jt alert my two biggest users are cleaner validator and system idle what ever they are I must google them Don zl1atb

"Cleaner validator" is part of Comodo System Cleaner, and it had a problem with consuming too much CPU...but that was fixed with newer updates. System Idle being high is a GOOD thing. It is a placehol

Thank you dave you beat me to it I had found the comodo bit and thanks I will look for an update

Hello Laurie, I just discovered your nice JT-Alert software. Thanks. It seems to work fine on my humble netbook (with Win 7 32-bit, JT65-HF, HRD and HRD Logbook with Access DB). Just a couple of sugge

Hi Tony, Glad HRD logging is working for you. There is an option for JT-Alert to be on-top of all other windows. I just checked my code, and I had disabled it during some testing I was doing for the d

Hi. Apologies for the delay, time difference & a busy morning is my only explanation. I have checked CPU and RAM usage in several situations. I first of all shut down everything I could with the excep

Laurie -- I just noticed I have the same issue ... I tried starting jt-alert before DXK, and starting DXK before Jt-alert, in case the connection between the two was lost, but still isn't logging. Oth

Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue. I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all

I have the same problem. I've gone back to 1.4 and JT65-HF 1.07. I'm running Vista, so I wonder if it's a Vista problem. Tom, AB0DI

Hi Laurie, appreciate you looking into this I know your a busy man. Love the new version and for now I'm just importing the JT65-hf adi file for now. All I can say is thank goodness I do backup the da

Hi Laurie, Ray W7RJC here. Well I've gotten rid of the multiple copies of JT65 v107 and have reloaded JT65 v107 and JT-Alert v1.5.0. Now I have an error message poping up at radum.(atleast I cann't re

Hi David, 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?

Hi Tom, Please see my response to David in this same message thread, message #117 If the Backslash fix doesn't work, please send me your session.txt file de Laurie, VK3AMA

Hi Ray, I assume you are using the HRD5 (Access) log Please email me direct you HRD log file that you have specified in the JT-Alert Log File Path de Laurie, VK3AMA

Hi Ron, File received, problems in db file easily identified. I will now take this off list while we work through what may be happening. QRX de Laurie, VK3AMA

### IMPORTANT ### If QSOs are still not being logged and you are NOT getting either a "Success" or "Failure" popup window, this is most likely caused by the JT65-HF log path containing a space. This i

Sweeet, worked for me. 73 KB0ASQ

Hi Lautie' In the process of getting the log file I realized that the address I put in JT-Alert was not complete I had left the last part off. Got that fixed and no more error messagees. I have not tr