+ AA6YQ comments below + Sounds like you have auto-scroll enabled. Click the flashing words "auto-scroll" in the Main window's upper-right corner. 73, Dave, AA6YQ

They are functional, but if I scroll "up" to the top of the list, it then scrolls back down to the bottom (oldest) spot. Previously, unless I am imagining things, it would hold the scroll at the top

Hi Bjorn, I did do that, but it still failed. I suspect I have something wrong in one of the fields, but cannot work out what. 73 de Phil GU0SUP

Dave: will do when at the computer Phil: I had to restart PathFinder to make it work. -- Björn, SM0SBL

+ AA6YQ comments below + What leads you to the conclusion that Google has a problem with SpotCollector's "security bits"? + Please review the recommended Gmail settings

Of all my email accounts, the only outgoing SMTP server (Yahoo, Network Solutions, Google) I could make work was Google. Google is not liking the third-party app logging in due to it's impression of

+ AA6YQ comments below + Are you saying that neither the vertical scroll bar along the right side of the Spot Database Display nor the "VCR-like controls" in the Main window's upper-right corner are

+ AA6YQ comments below + It's Windows that is reporting "insufficient system resources". Every log that's been sent to me has been immediately upgraded by directing my instance of DXKeeper to open it.

+ AA6YQ comments below + Please place your log file in a zip archive, attach the zip archive to an email message, and send the email message to me via aa6yq (at) ambersoft.com + What's stopping from

I typically have SC set to sort "Rcv", meaning the most recent spot is at the top. Recently I've noticed that SpotCollector will get into a state where it's now scrolled all the way to the bottom, and

Tom, Have patience. Despite my initial concern, Dave was able to modify my recently backed up log and has sent in back to me within a few hours. That's very little downtime, but the

Jerry, you are lucky, Not only will ver. 16.1.5 not open I can no longer o back to 15.9.9. Fortunately I have my old Win EQF logger to fall back to. Tom NQ7R

+ AA6YQ comments below + Please place your log file (probably N9EP.mdb) in a zip archive, attach the zip archive to an email message, and send the email message to me via aa6yq (at) ambersoft.com

hi folks: I upgraded to version 16.1.5 today, and when I started it, I got a window saying it was "EXPANDING QSO MODE FIELD WIDTH TO 12" Then I got the error message Existing fields were not

+ AA6YQ comments below I updated as of your instructions but the french callbook does not work, at least not for me. The web page seam to have changed name to nomenclature.r-e-f.org

Bjorn and the group, I've just tried modifying the French callbook lookup, and cannot get it to work with your link. I have put the following into the F.txt file: {SearchName}F

I updated as of your instructions but the french callbook does not work, at least not for me. The web page seam to have changed name to nomenclature.r-e-f.org If I manually edit the F.txt and change

+ AA6YQ comments below Regarding my use of the words, "data leak," in Windows 10. I saw those in previous correspondence and repeated it below. I am sorry if I propagated an error. I have rolled

My comments below are not entirely correct. When I open my log, it now complains about the data-width of multiple PSK modes. This happens with DXKeeper 15.9.9 and my recovered log which

Dave, Regarding my use of the words, "data leak," in Windows 10. I saw those in previous correspondence and repeated it below. I am sorry if I propagated an error. I have rolled