开云体育

Is this happening on the same PC where DXKeeper generated an errorlog showing unexpected database failures when synchronizing with LotW or eQSL? 73, Dave, AA6YQ

gm all, since migrating dxlab to a new (old) PC (macmini running XP3 via bootcamp) I'm stuck with loading new eQSL-databases. It's only a minor glitch as I don't use eQSLing so far ... but it's

DXKeeper refers to the DXCC database, so if you have DXCC database 2.2.7 installed and logged QSOs with Poltavska Oblast in Ukraine, then yes the wrong primary subdivision code would be logged. You

i just use dx keeper dave, any problem with this error in dx keeper? have not logged any oblasts yet from the ukraine so do not know how to fix if indeed a problem in dxkeeper. thanks joe kl7lf

The two Ukrainian entries in the DXCC database for Poltavska Oblast specify an incorrect primary administrative subdivision code. They currently specify Poltavska Oblast <Pri:HO> but should specify

I missed it also. Thank You.

Oh dear me, I missed that news, sad...

I have been somewhat out of touch of late and missed that. Thanks 73, Larry W6NWS

Ernie, KS4Q, died in early July. http://forums.qrz.com/showthread.php?t=209929 Jim N7US

I have not been able to connect to KS4Q cluster via telnet. I was wondering if anyone else was having a problem. A few months ago there was problem and for a short while changed to port 7373 but moved

The resolution of this is that George was only using the "DX Summit via IRC" spot source, from which SpotCollector does not currently capture WWV spots. He's adding a telnet cluster as a spot source

Dave, U are simply INCREDIBLE ! Joey

Please place your DXKeeper log file in a zip archive, and attach this archive to an email message. In the email message, please indicate the starting and ending dates of the contest, and then send the

Dave: I checked in DX Keeper and it is not registering most of the information you pointed out. The only fields being registered are CALL DXCC, Starting UTC BAND MODE, SENT, REceived. It is not

In the previous QSO that wasn't reported, what was logged as the Contest ID, band, mode, and QSO Date? 73, Dave, AA6YQ

Thanks for response, however this is not the case in my setup. I found this problem when I called a station that I had already worked but did not show as previously worked. When the station responded

With contest mode enabled, only previous contacts made in the current contest are displayed; this means QSOs logged in the current year with the current Contest ID. 73, Dave, AA6YQ

Hi Group: Just found a problem with the LAST QSO info on WW ver 6.4.8. I am running a local contest and noticed that I worked a station previously worked and did not get the message that I had already

Tnx Rich & Dave - I was under the impression that VOACAP would not run with NTFS, but I returned to Greg's site and read a bit more carefully - it is NTFS compressed that is the problem. I was not

I doubt anyone is going to release a 64-bit version of IONCAP. Its in all respects inferior to VOACAP and ICEPAC. Like Rich, I use ICEPAC. 73, Dave, AA6YQ