Many thanks to all for the comments. The computer is an i5 at 3GHz. RAM is a puny 8GB. I may have a suitable memory card in another computer I no longer use. I'll pop that in and see if there's a

All good points Mike. I was aiming at the lowest common denominator here, the ham that is not very computer savvy and just wants to make'ergofaster. The easiest answer there is to just get a bleeding

I’m with you Don……especially staying with ACLog 73 Frank NG1I

Hi Dennis, Thanks for your follow up. To change the Winkey settings in the software, click Settings > Transmit > CW. Then click the Winkeyer button on the form that appears, but I doubt you need to

What it sounds like is that the macros are keying the radio and sending CW, but not distinguishing the difference between a dot or dash. Is there a software setting in the CW transmission settings I

Mike, you hit the nail on the head….my laptop 32GB memory and 1T solid state drive…all works well Have a nice T-Day everyone! Frank NG1I

Problem solved. Turns out I inadvertently scrolled the window vertically. Feeling embarrassed! Thanx for your response. W8JRH From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> on

Well, I have a fairly fast Win10 machine with plenty of RAM, yet when I switch from "Last 50" to "All" it takes 13 seconds to display the data. I have about 24,000 records in ACLog. I can see how this

Good morning. There is more to it than just the volume of records. Amount of memory, amount of FREE memory, processor and speed, and what other programs running in the background can all make a

Responding to "I notice when logging FT8 QSOs in ACL from JTAlert/WSJT-X, that it takes 18 seconds for the QSO line entry to appear after clicking on OK in the J/W log pop-up window. I have 27k log

Yes, it will in Last 50 view. But it will bog down if you go to All view. "Lou Everett, Sr." <loueverettsr@...> wrote:

I have 50,000 in mine and it zips along fine. I am running an old computer. The op SYS is Win 7. Lou WA5LOU -- Lou WA5LOU

I've change my "Last NNN" to 500 and it seems to be fast enough, a good compromise if you want to quickly look at the past few months of Qs. 73 -- Larry -- W1DYJ

27,000 QSOs will slow the database down. That's just the way it is. You can either run in Last 50 mode like most of us probably do or you can buy the fastest bad-boy computer you can get your hands on

27000 ?

screenshot pls

what or jtalert

I notice when logging FT8 QSOs in ACL from JTAlert/WSJT-X, that it takes 18 seconds for the QSO line entry to appear after clicking on OK in the J/W log pop-up window. I have 27k log entries. As

All of a sudden I'm not seeing the top heading line, which shows menu, sort options, view, etc. The logging function seems to be running fine. What am I missing? Thinking I've done something

Jim, we all appreciate the giant effort you do to provide this valuable resource! -- 73, Bo W4GHV since '54