开云体育

I receive a script error when using pathfinder to look up a call in QRZ.com Line 889 Char 11 Error object doesn't support property or method 'some' Any suggestions ?

Perhaps I'm being overly precise, but one specifies a "Station Location" each time one directs TQSL to upload QSOs to LoTW. Thus "Station Location" is not considered a part of "TQSL Setup" - a term

Isn't that the same that it isn't set up correctly if it is missing something? If It isn't Correct,, so it must be incorrect,,, Joe WB9SBD

-----Original Message----- Sent: Monday, February 22, 2016 9:05 AM To: dxlab@... Subject: RE: [dxlab] NPOTA Thanks very much for that info Bob. I ran the report as you suggested and found

-----Original Message----- Sent: Monday, February 22, 2016 8:02 AM To: dxlab@... Subject: Re: [dxlab] NPOTA If I remember correctly this is not a DXL problem, it is a problem the

You should charge him for you work, Paul! At least you should as for free DXLab Suite upgrades for life :) If you're going to get into changing award objectives (etc.), it might be best to recommend

By all means, Dave, if you think it is useful go ahead. I didn't have to do this but it may be useful to add one more step: 10. Reconfigure your DXing objectives to normal if they were changed in

Thanks, Paul. With your permission, I'll place your step-by-step instructions in a "Getting Started with DXLab" article entitled "Conducting a DXCC Sprint". 73, Dave, AA6YQ

For what it's worth (in case others want to try it), I discovered another step necessary to do what I proposed below. Having successfully done this, I now believe the proper procedure is as

Rick N2AMG found that my firewall was not allowing fldigi to talk to Commander and the Yaesu FT-950. He made adjustments to the firewall settings and now all parts are communicating. Many thanks to

Thanks, Dave. Sorry for the late reply but just got around to working on this again. I understand it now and it works! Thanks again, Bob WA6MRK

Thanks very much for that info Bob. I ran the report as you suggested and found the last line in the record to have info just as shown in your post. So I wonder what the problem is now.

Joe is correct, the activator uploaded his log and was missing the proper park designator in the TQSL location. You can verify this by logging into LOTW select YOUR QSO's over on the left click

What data sub-mode is your K3 in? If it is in FSK D or AFSK A, the radio's dial displays the actual Mark frequency, not the suppressed carrier frequency, and you need to enter a correction in the

If I remember correctly this is not a DXL problem, it is a problem the activator does not have his TQSL set up correctly yet. and will have to fix it and up load all his Qs again. Joe WB9SBD Sig The

I'm not sure if this is a DXL problem or a LOTW problem but since the error message is coming from DXL I'll start here. Recently I worked a station that reported he was in TR23. Along with

I see the memory problem. I have 12 gigs with 4 terabytes between two drives and an i7 processor so would nt be a problem. I was talking about running Windws native, not in a VM. iPad Gil W0MN Hierro

W4TV and AA6YQ helped me reset my mark frequency in my K3 to 2125, after I had a problem where stations were saying I was off freq when responding. As part of that, I set the Optimal Offset Value for

<dxlab@...> wrote: You may be able to run the Solaris version of VirtualBox on OpenInd

-----Original Message----- Sent: Sunday, February 21, 2016 11:30 PM To: dxlab@... Subject: RE: [dxlab] clublog I read the information in the links below, but to me it appears that this