Scott, Maybe it is too early in the morning for me (still on first coffee), but I don't understand this statement... "it doesn't tell me there is a QSO not marked to be uploaded". Are you saying that

Hi John, I understand what you are say. I have been working on the logging components for so long, that I lost sight of the confusion the new setup scheme may cause. I have plans to correct this. Hope

Laurie, I think that Scott's problem is that he is using the external HRD Utilities rather than the HRD LoTW upload tool in HRD 5. Dave K3DCW

Larry, Are you receiving a popup message indicating that the logging had failed? If not, then the most likely cause is the missing trailing backslash on the JT65-HF log path (see my message titled "##

John, I haven't experienced that here. Tested under many environments (Win7 and XP with different memory configs). My live Ham PC is still XP (1.5 G Ram) running the full suite of DXlabs as well as JT

Hi Dave, I think the issue is that newly logged QSOs are not flagged for LoTW upload. I found log entries where these are set. It is an easy fix, I will add settings to enable flagging of QSOs with Lo

Dave, Yes, I was using the external one. That was working up until last night. Now I'm not able to use the HRD Utilities to upload to LoTW, and I'm not able to upload from within the Logbook. Working

Nothing like that on my end decoding jt65 and RTTY CPU is only 4% and my computer is no powerhouse 73 Ron VA7HZ

Laurie, Yes that fixed it. I missed that post I guess. Simple fix and now I'm getting the pop up saying success and the refresh logs the contact. Hey great work on this version, I love the new feature

Good to hear Larry. I'm missing all the 10M action (actually every band except 30m) as my SteppIR is off the tower on the ground in preparation for a new SteppIR arriving next week. Early Christmas pr

Hi Laurie, B4 alerts for stations worked on the current band is working great, but stations worked on other bands are not being flagged as worked B4. There's a note in the Worked B4 configuration scre

Hi John, So what you want is... say you have worked VK3AMA only on 20M, you are currently on 10M, VK3AMA is decoded on 10M calling CQ, you want that decode to show as a B4. Is that correct? If so, it

Hi all, I have tryed most of the afternoon to get JT-Alert to work with HRD logger .. to no avail. I don't even get any nasty grams. I have done the \ thing in JT65 as suggested. Perhaps I don't u

Hi Ray, You should get a popup window after logging, advising either success or failure. If you are not getting any popup, then it sounds like you don't have the correct path set for the Log file, or

Ray, I'm using Win7 myself, and the path I needed to put in was this: C:\Users\owner\AppData\Roaming\Simon Brown, HB9DRV\HRD Logbook\HRD My Logbook.mdb I don't know if this

Hi Laurie, That's exactly what I want to see happen. I want to see "B4" appear next to the call no matter what band I worked him on. I swear that feature was already available in v1.4.1. For me, it wo

This is going to be an option correct and not a full functional change to how B4's are handled? If I've worked John WA3CAS on 20m, but now operating on 40m and see him calling CQ I only want to see hi

Hello Laurie, VK3AMA After saving QSO I become three error messages: here the 2 (same) error message: 1. Sorry, there appears to be an error! err.description is : Syntaxisfout (komma) in query-express

Hi Laurie and the group, the issue I'm having is abit different from some of the others. First let me say I have latest versions of JT65-HF and JT-Alert Everything except the logging to HRD is working

Hi de Laurie and Scott also Thanks for the reply to my trouble with loginng records to HRD logger. AS was suggested I checked out what method I was (am) using. It is the HRD V5 (access). I have set th