开云体育

WinWarbler cannot use QRZ.com as a callbook unless both DXKeeper and Pathfinder are running, and the Callbook tab of DXKeeper's Config window is configured for "QRZ.com via Pathfinder". As a result of

--- In dxlab@..., "ke7ace" <ke7ace@...> wrote: when i hit the look up from dxkeeper it brings back the info from qrz but the name and part of the address is all just mixed letters and

when i hit the look up from dxkeeper it brings back the info from qrz but the name and part of the address is all just mixed letters and numbers just noticed this starting this past week not sure

yes it would be nice.. lot of work has been done by a lot of the guys on SQL's . Drop me a card to p.o. box 131 Ferguson Ky 42533 and ill get you a qsl asap. just a sae is all i need. will save a lot

The problem you describe is not a familiar one but the latest version of Commander is 7.9.2. The version 5.8.7 you have is a couple of years and two major revisions out of date. So, first get the

Hi Tony, That would be a very useful resource. I have to confess that my knowledge of SQL is not very good & it would be very useful to be able to refer to an index rather than keep asking for help. I

Hello to all! I downloaded and installed Commander 5.8.7. as a standalone. It was working perfectly in the beginning. I am using it mainly for tuning and saving the frequencies for my Yaesu FT-897.

does anyone keep a list of all the scripts that have been written over the years for dxlab ? got another station up and going this week. hope to get the last one next week then network all 5 computer

I have a problem with WW receive. TX works OK. I am using a Tigertronix Signalink USB interface. I had it working up through last night but when I turned on the computer this morning RX doesn't work.

Hi Steve, The original list i use counts 3359 SDOK's. But there are many dupes in it, sam SDOK but with different callsign. After filtering this list i still get 1935 SDOK's. example: 01ILLW Int.

The list of modes acceptable to eQSL.cc is available at http://www.eqsl.cc/qslcard/ADIFContentSpecs.cfm New modes are added as they are added by the ADIF specification by the ADIF Development group.

Thanks, that got it. I know there was a way to do that, just couldn't remember how. Lee

Hi Koen, The only answer then is to include all the "Sonder" DOKs both permanent & temporary in the file. I counted over 200 but looking at the DARC file there must be a lot more. Being a text file I

Hi Gang, I'm currently running with PF 4.5.7 and WW 6.4.8 and I have run into an issue where upon hitting return from entering a callsign in WW Call Box, the program will not auto populate the name

Hi Steve, For me it's OK also... But what if someone , like you did, update his logbook with old qsl cards. So then it's possible that he had a qsl card from 20 years old with that SDOK. Koen

Yawn. _____ From: dxlab@... [mailto:dxlab@...] On Behalf Of Paul M Dunphy Sent: Thursday, September 03, 2009 10:21 PM To: DXLabs Subject: RE: [dxlab] stupid /1440 Hiram Percy

-----Original Message----- From: dxlab@... [mailto:dxlab@...]On Behalf Of Bernard Grijpstra Sent: Thursday, September 03, 2009 4:04 PM To: DX-Lab Yahoo Group Subject: [dxlab]

Hi Koen, Thanks for the information & URLs. I think Dave's idea to leave users to enter their own additional DOKs as they need them is the best idea. There is no point in having a very large list

I have a release of DXKeeper that when synchronizing QSOs or QSLs with LotW, considers a QSO reported by LotW whose Mode is DATA to match a logged QSO whose mode "counts" as RTTY for ARRL awards.

Hi Steve, The list i follow is the list from DARC. http://www.darc.de/qsl-buero/sdok/pdf/sdok_s.pdf IBO is the special DOK for Friedrichshaven. And IBO83 is not in that list nor in the CSV file wich i