I don't think this works if the window, as configured, has more vertical pixels than your monitor can display. That was my problem with the default configuration 73, Pete N4ZR Check out the Reverse Be

Thanks to several guys for suggesting the obvious - I didn't realize that the Log QSOs page could be reconfigured by unchecking various panels. All I had to do was get rid of the Auxiliaries panel, et

I get the double-headed arrow all right at the top or bottom edges, but it doesn't do anything. At the top it looks like it is reducing the height of the page, but it's really just moving the bottom o

This has to be an easy question, but I haven't found the answer so far. When I open DXKeeper's log page, it is just a little too tall for my monitor, which cuts off the line of buttons at the bottom f

This might also be something in your browser. Depends on which one, I guess, but I've had some of these "install this now" critters that actually turned out to be bogus Chrome extensions. 73, Pete N4Z

Rick, I suggest you get the free version of Malwarebytes and run it on your system. This is probably malware. 73, Pete N4ZR Check out the Reverse Beacon Network at <http://reversebeacon.net>, now spot

Thanks, Dave. 73, Pete N4ZR Check out the Reverse Beacon Network at <http://reversebeacon.net>, now spotting RTTY activity worldwide. For spots, please use your favorite "retail" DX cluster. On 5/29/2

It's from ARRL, somehow changed from the original block format to that line. The only difference from what you expect is that the callsign is present. I also noticed that looking at my DXCC record onl

Wonderful (JK). The next sound you hear will be me slogging through some 500 calls x 4 lookups from the DXCC record. I'll probably resurface sometime next week. 73, Pete N4ZR Check out the Reverse Bea

Say I have an entry in this report as follows: "149 851347831 card 6Y5BF 82 1976-01-01 20M CW no exact match found in log, new Entity, Entity-Band, Entity-Mode" Is the part following the mode received

Oh I know they exist, Joe - I have a number of them myself. Fortunately, my DXKeeper log goes back to 1971, so I'll be able to find most of them. There may be a few issues, because that's also the yea

I just wonder how many others are in the same boat. 73, Pete N4ZR Check out the Reverse Beacon Network at <http://reversebeacon.net>, now spotting RTTY activity worldwide. For spots, please use your f

Guys, the fact is that my DXCC record shows some countries with country codes only, as Bill says, but for most pre-1990 records, it shows call, date in years only, mode and band. For example: Worked S

Bill, the problem is that ARRL apparently made the decision back when not to enter data from its pre-LOTW/pre-computer era records beyond the callsign, band, mode, and year of each QSO. All of the cre

Still trying to get the DXCC status in my log to match with DXCC info from ARRL. Ran this routine and it worked great for recent QSOs, updating their QSL status to verified, but it left 525 DXCC credi

Still trying to get the DXCC status in my log to match with DXCC info from ARRL. Ran this routine and it worked great for recent QSOs, updating their QSL status to verified, but it left 525 DXCC credi

Dave, as usual you make perfect sense, but I need some more work to wrap my head around this. Thanks! 73, Pete N4ZR Check out the Reverse Beacon Network at <http://reversebeacon.net>, now spotting RTT

I ran a DXCC verification discrepancy report and was appalled to find 1063 discrepancies between my ARRL DXCC record and what DXKeeper displays. So I ran a DXCC Credit download, expecting to find a la

For what it's worth, I'm running CW Skimmer Server with DXLabs on an i5 - it has a solid state drive for the OS but otherwise sounds similar. I am not conscious of any sluggishness. 73, Pete N4ZR Chec

It's now called North Macedonia - the Greeks insisted! 73, Pete N4ZR Check out the Reverse Beacon Network at <http://reversebeacon.net>, now spotting RTTY activity worldwide. For spots, please use you