Date   

Expired QSOs

Peter Jordahl
 

Dave,
I would like to suggest that if an entity (or band-entity) is
represented only by a QSO or QSO's that have been marked 'X'
in the QSL-RCVD box then the 'W' in the DXVIEW status listing
should be either removed or changed to an 'X'.

Yes, the contact was made, but hope of obtaining a QSL has
now evaporated. Perhaps for that reason an 'X' in the status
table would be preferable to showing a blank. The 'X' would
be replaced with a 'W' when another, non-expired, QSO was
made with that band-entity.

In my case I had a 1978 40M QSO with ZD8HR (later N6HR) which
resulted in a 'W' in the status view. He passed away in
2007 before I really started "data-mining" my log. I
just inserted an 'X' in the QSL box but the 'W' persists.

Obviously if one inserted hundreds of 'X's at one time
it could cause a major subsequent but short-lived
slowdown in DXKeeper,but I doubt that that happens.

Thanks and 73
Pete K5GM
Pete Jordahl, K5GM
k5gm@amsat.org


Re: Pathfinder/QRZ Problem

Dave AA6YQ
 

Its looks like the format of the information displayed by QRZ.com has been
changed. Joe W4TV just sent me an example that I thought was a formatting
error specific to one callsign, but I see that its happening for all
callsigns. I'll see what I can do...

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
empennage2003
Sent: Tuesday, September 01, 2009 6:05 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Pathfinder/QRZ Problem


I'm running DXKeeper 8.1.5, Pathfinder 4.5.6. I've updated the QRZ URL in
Pathfinder "Config" and the QRZ button per earlier posts and AA7BQ's QRZ
Website Link Policy Update. When accessing QRZ via DXKeeper and Pathfinder,
the information posted in DXKeeper is incomplete, inconsistent and never
entirely correct. When I inspect the Pathfinder Error Log text, I can see
extra random characters added to the QRZ response which DXKeeper is
misinterpreting. For example, when using Pathfinder to search on my
callsign-KJ4WD, the error log contains the following:

01-Sep-2009 21:48:49 > Result = <callsign>KJ4WD<name>CARL J
PONTO<addr1>e5de E96F314F80DC52 ae96f314f80dc52<addr2>5116 BEAVER CREEK
RD<country>NEW HILL, NC 27562<grid>FM05mq<state>North
Carolina<county>Chatham

As a result, DXKeeper displayed my name correctly but displayed "Beaver
Creek" as my QTH. Note the random data in the <addr1> field. If it would be
helpful in diagnosing this problem, I can send the Pathfinder Error Log file
via email. 73

Carl KJ4WD
KJ4WD@ARRL.NET



------------------------------------

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/01/09
06:52:00


Pathfinder/QRZ Problem

empennage2003
 

I'm running DXKeeper 8.1.5, Pathfinder 4.5.6. I've updated the QRZ URL in Pathfinder "Config" and the QRZ button per earlier posts and AA7BQ's QRZ Website Link Policy Update. When accessing QRZ via DXKeeper and Pathfinder, the information posted in DXKeeper is incomplete, inconsistent and never entirely correct. When I inspect the Pathfinder Error Log text, I can see extra random characters added to the QRZ response which DXKeeper is misinterpreting. For example, when using Pathfinder to search on my callsign-KJ4WD, the error log contains the following:

01-Sep-2009 21:48:49 > Result = <callsign>KJ4WD<name>CARL J PONTO<addr1>e5de E96F314F80DC52 ae96f314f80dc52<addr2>5116 BEAVER CREEK RD<country>NEW HILL, NC 27562<grid>FM05mq<state>North Carolina<county>Chatham

As a result, DXKeeper displayed my name correctly but displayed "Beaver Creek" as my QTH. Note the random data in the <addr1> field. If it would be helpful in diagnosing this problem, I can send the Pathfinder Error Log file via email. 73

Carl KJ4WD
KJ4WD@ARRL.NET


Re: Another Pathfinder/QRZ problem?

Dave AA6YQ
 

On Pathfinder's Config window, What URL is shown for QRZ.com ?

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
pcooper
Sent: Tuesday, September 01, 2009 11:58 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] RE: Another Pathfinder/QRZ problem?



Dave and the group,

I just started PF to check an address, and it nicely told me a couple of things had been updated, but I am now getting a Google page whenever I try to find a call in QRZ.
It appears to work OK with Buckmaster, but QRZ seems to direct me to a Google search page for the call in question.

I tried QRZ in a browser window, and that works OK, but it still won't work with PF.

I even tried closing and restarting PF, but that had no effect.

Any one else getting this problem??

73 de Phil GU0SUP


------------------------------------

Yahoo! Groups Links



Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.72/2337 - Release Date: 09/01/09 06:52:00


Re: Another Pathfinder/QRZ problem?

JOE
 

I had this problem yesterday
evidently QRZ changed their format for requests?
I had to go to Pathfinder config
and change to
http://www.qrz.com/db/{TargetCallsign}

--- In dxlab@yahoogroups.com, " pcooper" <pcooper@...> wrote:


Dave and the group,

I just started PF to check an address, and it nicely told me a couple of things had been updated, but I am now getting a Google page whenever I try to find a call in QRZ.
It appears to work OK with Buckmaster, but QRZ seems to direct me to a Google search page for the call in question.

I tried QRZ in a browser window, and that works OK, but it still won't work with PF.

I even tried closing and restarting PF, but that had no effect.

Any one else getting this problem??

73 de Phil GU0SUP


Re: Another Pathfinder/QRZ problem?

pcooper <pcooper@...>
 

Dave and the group,

I just started PF to check an address, and it nicely told me a couple of things had been updated, but I am now getting a Google page whenever I try to find a call in QRZ.
It appears to work OK with Buckmaster, but QRZ seems to direct me to a Google search page for the call in question.

I tried QRZ in a browser window, and that works OK, but it still won't work with PF.

I even tried closing and restarting PF, but that had no effect.

Any one else getting this problem??

73 de Phil GU0SUP


Winwarbler frequency readout sourced from dxlabs-hrd gateway

Jeff Blaine AC0C <keepwalking188@...>
 

Is there a way to get Win Warbler to grab the frequency from the dxlabs_hrd gateway v1.02?

All the other dxlabs programs can see the frequency from that applet, but I for some reason cannot seem to figure out how to get Win Warbler to read it from anything other than commander.

Appreciate any suggestions!

73/jeff/ac0c


Re: eqsl error trying to sync...

Jim McHale <mchale@...>
 

Rich,
Thank you - It was the qth nickname... I must have defined it sometime in august...and just never resync'd....
73s
-jim NM1W

Rich - W3ZJ wrote:


I don't see any problem with your eQSL account John and I can't
duplicate that problem from here. Make sure that your QSL Configuration
panel for eQSL does *NOT* define a QTH Nickname for your account because
your on-line account does not have a Nickname.

73, Rich - W3ZJ
eQSL.cc Support Volunteer

Jim McHale wrote:
I've had this problem for past week or so... Also it shows up in the
latest dxkeeper 8.1.5;
I can upload qsos to eqsl, but when I click "sync eQSL.cc QSLs" I get
this error msg:
Error message from eQSL.cc: No such Username/Password found

I've checked the username password and its correct; I can login to eqsl
using them..

Anyone else seeing this issue or know of a workaround?
Thanks
-jim NM1W


Re: eqsl error trying to sync...

Richard B Drake
 

I don't see any problem with your eQSL account John and I can't duplicate that problem from here. Make sure that your QSL Configuration panel for eQSL does *NOT* define a QTH Nickname for your account because your on-line account does not have a Nickname.

73, Rich - W3ZJ
eQSL.cc Support Volunteer

Jim McHale wrote:

I've had this problem for past week or so... Also it shows up in the
latest dxkeeper 8.1.5;
I can upload qsos to eqsl, but when I click "sync eQSL.cc QSLs" I get
this error msg:
Error message from eQSL.cc: No such Username/Password found

I've checked the username password and its correct; I can login to eqsl
using them..

Anyone else seeing this issue or know of a workaround?
Thanks
-jim NM1W


eqsl error trying to sync...

Jim McHale <mchale@...>
 

I've had this problem for past week or so... Also it shows up in the latest dxkeeper 8.1.5;
I can upload qsos to eqsl, but when I click "sync eQSL.cc QSLs" I get this error msg:
Error message from eQSL.cc: No such Username/Password found

I've checked the username password and its correct; I can login to eqsl using them..

Anyone else seeing this issue or know of a workaround?
Thanks
-jim NM1W


Re: DXKeeper 8.1.5 is available

Dave AA6YQ
 

Here's a properly formatted URL for the new documentation file mentioned below:

<http://www.dxlabsuite.com/dxkeeper/Help/LogNewMain.htm#Logging%20Information%20Needed%20for%20Award%20Tracking>

73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, "aa6yq" <aa6yq@...> wrote:

This release

- ensures that the Address Editor window is properly displayed (tnx to John K1ESE and Rich W3ZJ)

- on the main window's "Check Progress" tab, renames the "Hungary" button to "WAHUC"

- generates a "Worked All Italian Provinces" (WAIP) progress report

- adds a new AwardInfo.htm documentation file that shows what items to log for each award supported by DXKeeper (see <http://www.dxlabsuite.com/dxkeeper/Help/LogNewMain.htm#Logging Information Needed for Award Tracking> or click one of DXKeeper's Help buttons and navigate to the "Logging Information needed for Award Tracking" topic in the "Logging and Managing QSOs" section)

- updates the index.htm, Log.htm, Progress.htm, and Scripts.htm documentation files

DXKeeper 8.1.5 is available via the DXLab Launcher and via

<http://www.dxlabsuite.com/download.htm>


73,

Dave, AA6YQ


DXKeeper 8.1.5 is available

Dave AA6YQ
 

This release

- ensures that the Address Editor window is properly displayed (tnx to John K1ESE and Rich W3ZJ)

- on the main window's "Check Progress" tab, renames the "Hungary" button to "WAHUC"

- generates a "Worked All Italian Provinces" (WAIP) progress report

- adds a new AwardInfo.htm documentation file that shows what items to log for each award supported by DXKeeper (see <http://www.dxlabsuite.com/dxkeeper/Help/LogNewMain.htm#Logging Information Needed for Award Tracking> or click one of DXKeeper's Help buttons and navigate to the "Logging Information needed for Award Tracking" topic in the "Logging and Managing QSOs" section)

- updates the index.htm, Log.htm, Progress.htm, and Scripts.htm documentation files

DXKeeper 8.1.5 is available via the DXLab Launcher and via

<http://www.dxlabsuite.com/download.htm>


73,

Dave, AA6YQ


Re: Another Pathfinder/QRZ problem?

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Mario Aviles
Sent: Monday, August 31, 2009 9:06 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] Another Pathfinder/QRZ problem?


Hi:

I tried this and now it is trasferring data from QRZ.COM to Winwarbler which
is something it did not do before, however my problem now is that the info
is not in the correct fields. For example, I tried my callsign and on Name I
get AN on QTH I get Mario Aviles. So there is something wrong with the
fields match.


QRZ.com is back up. When I direct WinWarbler to perform a lookup on your
call (via DXKeeper and Pathfinder), WinWarbler's "QSO Info" window is
properly populated with your name, QTH, Continent, CQ zone, ITU zone, and
grid square.

73,

Dave, AA6YQ


Re: Another Pathfinder/QRZ problem?

Dave AA6YQ
 

QRZ.com appears to be broken at the moment. Let's see what happens after its
repaired.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Mario Aviles
Sent: Monday, August 31, 2009 9:06 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] Another Pathfinder/QRZ problem?


Hi:

I tried this and now it is trasferring data from QRZ.COM to Winwarbler which
is something it did not do before, however my problem now is that the info
is not in the correct fields. For example, I tried my callsign and on Name I
get AN on QTH I get Mario Aviles. So there is something wrong with the
fields match.
Any ideas?

73�s

Mario /YS1MAE

----- Original Message -----
From: Anela Karacic
To: dxlab@yahoogroups.com
Sent: Monday, August 31, 2009 7:55 AM
Subject: Re: [dxlab] Another Pathfinder/QRZ problem?


They made some changes on QRZ.com
Now you need to change URL on Pathfinder.
Puth this one:
http://www.qrz.com/db/{TargetCallsign}
You need to change this on CONFIG, and do not forget todo the same on a
QRZ botton (ctrl + left mouse botton)
GL and 73
Anela - e74ee

________________________________
From: kbandy <kj9b@arrl.net>
To: dxlab@yahoogroups.com
Sent: Monday, August 31, 2009 2:18:07 PM
Subject: [dxlab] Another Pathfinder/QRZ problem?

Please excuse me if this has already been hashed over, but I scanned
through recent messages on the yahoogroup, and didn't see any mention of
this problem.

I hadn't been on the rig for a few days, and Sunday evening looked to see
what I could find. When starting up Pathfinder, I noticed there were a
couple of updates it wanted to do. After doing those, I worked a little PSK,
and when WinWarbler would try to find a name and QTH by using Pathfinder, I
would get a script error from QRZ.com. If I went to the Pathfinder window,
the QRZ opening web page would be up with the target callsign in the
Pathfinder window, at which time I could click on the "QRZ" button in
Pathfinder, and it would go to the proper record.

I figured the PC might have something "sideways", so I rebooted the PC.
After reboot and restarting the suite, I had the same problems. When trying
it this morning, I don't get the script error, but QRZ still only goes to
the opening page, and I get a dxlab window that pops up and says the target
callsign wasn't found (xx0xx not found).

I have all the latest versions of all components of the suite.

Thanks in advance for any help.

73,
Ken
KJ9B











------------------------------------

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.72/2337 - Release Date: 08/31/09
05:50:00


Re: Another Pathfinder/QRZ problem?

Mario Aviles <mario.aviles@...>
 

Hi:

I tried this and now it is trasferring data from QRZ.COM to Winwarbler which is something it did not do before, however my problem now is that the info is not in the correct fields. For example, I tried my callsign and on Name I get AN on QTH I get Mario Aviles. So there is something wrong with the fields match.
Any ideas?

73´s

Mario /YS1MAE

----- Original Message -----
From: Anela Karacic
To: dxlab@yahoogroups.com
Sent: Monday, August 31, 2009 7:55 AM
Subject: Re: [dxlab] Another Pathfinder/QRZ problem?


They made some changes on QRZ.com
Now you need to change URL on Pathfinder.
Puth this one:
http://www.qrz.com/db/{TargetCallsign}
You need to change this on CONFIG, and do not forget todo the same on a QRZ botton (ctrl + left mouse botton)
GL and 73
Anela - e74ee

________________________________
From: kbandy <kj9b@arrl.net>
To: dxlab@yahoogroups.com
Sent: Monday, August 31, 2009 2:18:07 PM
Subject: [dxlab] Another Pathfinder/QRZ problem?

Please excuse me if this has already been hashed over, but I scanned through recent messages on the yahoogroup, and didn't see any mention of this problem.

I hadn't been on the rig for a few days, and Sunday evening looked to see what I could find. When starting up Pathfinder, I noticed there were a couple of updates it wanted to do. After doing those, I worked a little PSK, and when WinWarbler would try to find a name and QTH by using Pathfinder, I would get a script error from QRZ.com. If I went to the Pathfinder window, the QRZ opening web page would be up with the target callsign in the Pathfinder window, at which time I could click on the "QRZ" button in Pathfinder, and it would go to the proper record.

I figured the PC might have something "sideways", so I rebooted the PC. After reboot and restarting the suite, I had the same problems. When trying it this morning, I don't get the script error, but QRZ still only goes to the opening page, and I get a dxlab window that pops up and says the target callsign wasn't found (xx0xx not found).

I have all the latest versions of all components of the suite.

Thanks in advance for any help.

73,
Ken
KJ9B


Re: Solar History display question

G4MUL <g4mul.hfdx@...>
 

----- Original Message -----
From: "Dave AA6YQ" <aa6yq@ambersoft.com>
To: <dxlab@yahoogroups.com>
Sent: Monday, August 31, 2009 5:11 PM
Subject: RE: [dxlab] Solar History display question


AA6YQ comments below
I suspect that adding horizontal connecting lines to the current chart
would degrade intelligibility for many ops, given the existing vertical
lines used to show the day's range for each parameter.
I agree Dave, leave it as it is please !

Regards
Dave
g4mul.hfdx@ntlworld.com


Re: QSL aging

OZREN SPASKOV
 

OK, thanks for help Dave,
my best regards,
73, de Z35T/Ozren




________________________________
From: Dave AA6YQ <aa6yq@ambersoft.com>
To: dxlab@yahoogroups.com
Sent: Monday, August 31, 2009 6:03:58 PM
Subject: RE: [dxlab] QSL aging

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of OZREN
SPASKOV
Sent: Monday, August 31, 2009 5:20 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] QSL aging


Hi Dave,
I am using DXKeeper more then one year, don't need to say that's EXCELLENT,
Brilliant etc...
I am interesting is some how possible filtering QSL aging on DXKeeper's
LogQSO window?
It will be easy to aging all missed QSL cards for band/mode, maybe IOTA,
etc. ( I don't know how ?)

Two steps:
1. on the Config window's Awards tab, make sure the "Expiration age" box in
the "QSL Aging" panel is blank. (along the right margin, half-way down)

2. on the Main window's "Check Progress" tab, click the "Card Aging" button

For a description of this function, see
<http://www.dxlabsuite.com/dxkeeper/Help/Progress.htm#Card Aging>

or click one of DXKeeper's Help buttons and navigate to the "Checking
Award Progress" section's "QSL Card Aging Analysis" topic.

73,

Dave, AA6YQ




------------------------------------

Yahoo! Groups Links


Re: Solar History display question

FireBrick <w9ol@...>
 

Kinda off topic, but any plot of the solar flux is pretty simple these days seeing as it is stuck at 68 and this is the 51st day without a sunspot. I think the programming effort would better be applied to the "Flux Enhancement Module" You know, a slide bar were we could drag the flux from 68 up to 200 while we are operating, and then put it back when we QRT for the day! :-)
73, Paul VE1DX
I second this feature request.
I'd be happy if the slider just went to 120 LOL


Re: Solar History display question

Paul M Dunphy
 

At 01:11 PM 8/31/2009, you wrote:
AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
vk2ca
Sent: Monday, August 31, 2009 7:19 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Solar History display question


Hi All

Would it be possible to have the dots joined in the History display with
relevant coloured lines. Just an asthetic suggestion but my eyes find all
the dots tend to meld over time. I know I can separate the readings but I
find lines tend to show a trend more dynamically.

Nothing major....just a suggestion.

I suspect that adding horizontal connecting lines to the current chart
would degrade intelligibility for many ops, given the existing vertical
lines used to show the day's range for each parameter.

In the "Solar and Geomagnetic Parameters" window's lower left corner,
there are A and K boxes. Try unchecking these boxes; is the solar flux trend
now easier to comprehend? There's an SFI box in the lower right corner that
can be unchecked when you want to focus on the A or K trend.

73,

Dave, AA6YQ
Kinda off topic, but any plot of the solar flux is pretty simple these days seeing as it is stuck at 68 and this is the 51st day without a sunspot. I think the programming effort would better be applied to the "Flux Enhancement Module" You know, a slide bar were we could drag the flux from 68 up to 200 while we are operating, and then put it back when we QRT for the day! :-)

73, Paul VE1DX


Re: Solar History display question

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
vk2ca
Sent: Monday, August 31, 2009 7:19 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Solar History display question


Hi All

Would it be possible to have the dots joined in the History display with
relevant coloured lines. Just an asthetic suggestion but my eyes find all
the dots tend to meld over time. I know I can separate the readings but I
find lines tend to show a trend more dynamically.

Nothing major....just a suggestion.

I suspect that adding horizontal connecting lines to the current chart
would degrade intelligibility for many ops, given the existing vertical
lines used to show the day's range for each parameter.

In the "Solar and Geomagnetic Parameters" window's lower left corner,
there are A and K boxes. Try unchecking these boxes; is the solar flux trend
now easier to comprehend? There's an SFI box in the lower right corner that
can be unchecked when you want to focus on the A or K trend.

73,

Dave, AA6YQ

136261 - 136280 of 208062