¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

N1MM to DXK Gateway

n4lv
 

Hi All,
Thought I would try the real time logging into DXK from N1MM. So far, no luck in getting it to work. I went into the .ini files and changed DoWebUpdate=1 to =0 (don't have a website) and DoDXKGateway=0 to =1 to enable real time logging, also the radiotype. It is installed in it's own directory under program files. (WinXP) Anyone using this that could give me hint at what I may be missing?
Thanks!

73,
Glenn N4LV


Re: DXK rejects Ukraine entries

Kurt Arseneault
 

I had just tried that, discovered a couple of qsl's in the cue, deleted
them, did a recompute and "Bingo"...... the gremlins have gone somewhere
else! Thanks for your help. The learning curve continues!
73 de Kurt

2009/9/2 Dave AA6YQ <aa6yq@...>

OK, then clicking the "Recompute" button at the bottom of the "Check
Progress" tab of DXKeeper's Main window should be sufficient.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kurt
Arseneault
Sent: Wednesday, September 02, 2009 1:47 PM
To: dxlab@...
Subject: Re: [dxlab] DXK rejects Ukraine entries


Thanks for your prompt reply Dave, my DXCC database is 2.2.7.
Regards,
Kurt VE1TT



2009/9/2 Dave AA6YQ <aa6yq@...>

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kurt
Arseneault
Sent: Wednesday, September 02, 2009 9:39 AM
To: dxlab@...
Subject: [dxlab] DXK rejects Ukraine entries


FIrst of all, I want to express my thanks to you for such a powerful
suite
of programs. I have been using DX Lab Suites for several months and love
it.
Your level of support for the software through the group is something I
have
rarely seen and you are to be commended for it.

However, I am experiencing one rather strange situation. I am unable to
enter Ukraine calls into my log. The DXCC field flashes red. The Code box
reads 288. After I exit, (delete the QSO),I get a box which reads there
"The
DXCC Progress table contains no entry for DXCC prefix UT". I examined the
DXCC database in Access and UT appears there. I have all the latest
updates
installed. Gremlins have crept in somewhere I suspect.

First, verify that you have the current version of the DXCC database
installed; on the General tab of DXKeeper's Config window, click the
"Database Info" button at the bottom. If the DXCC database version is not
2.2.7, then terminate DXKeeper (and SpotCollector, if its running), open
the
Databases tab of DXView's Config window, and click the button to upgrade
your DXCC database.

Then restart DXKeeper (if you had to terminate it to upgrade the DXCC
database), and click the Recompute button at the bottom of the Main
window's
"Check Progress" tab.

If this doesn't clear up the "no entry for DXCC prefix UT" problem,
please let me know.

73,

Dave, AA6YQ



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

Yahoo! Groups Links




--
***Here is an Important Message for anyone who receives this email:***
If you forward this correspondence, please delete the forwarding history,
which includes my email address! It is a courtesy to me and others who may
not wish to have their email addresses sent all over the world! Erasing the
history helps prevent Spammers from mining addresses and viruses from being
propagated!



Kurt Arseneault

273 Meadow Lane,
Kentville, NS B4N 3V8
Canada

807 E 21 ST, Unit 11,
Mission, TX 78572

(956) 584-1769 (condo)
902-679-9783 (home Nova Scotia)
902-680-6230 (cell Nova Scotia)






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

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/02/09
05:50:00



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

Yahoo! Groups Links



--
***Here is an Important Message for anyone who receives this email:***
If you forward this correspondence, please delete the forwarding history,
which includes my email address! It is a courtesy to me and others who may
not wish to have their email addresses sent all over the world! Erasing the
history helps prevent Spammers from mining addresses and viruses from being
propagated!



Kurt Arseneault

273 Meadow Lane,
Kentville, NS B4N 3V8
Canada

807 E 21 ST, Unit 11,
Mission, TX 78572

(956) 584-1769 (condo)
902-679-9783 (home Nova Scotia)
902-680-6230 (cell Nova Scotia)


Re: DXK rejects Ukraine entries

 

OK, then clicking the "Recompute" button at the bottom of the "Check
Progress" tab of DXKeeper's Main window should be sufficient.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Kurt
Arseneault
Sent: Wednesday, September 02, 2009 1:47 PM
To: dxlab@...
Subject: Re: [dxlab] DXK rejects Ukraine entries


Thanks for your prompt reply Dave, my DXCC database is 2.2.7.
Regards,
Kurt VE1TT



2009/9/2 Dave AA6YQ <aa6yq@...>

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kurt
Arseneault
Sent: Wednesday, September 02, 2009 9:39 AM
To: dxlab@...
Subject: [dxlab] DXK rejects Ukraine entries


FIrst of all, I want to express my thanks to you for such a powerful suite
of programs. I have been using DX Lab Suites for several months and love
it.
Your level of support for the software through the group is something I
have
rarely seen and you are to be commended for it.

However, I am experiencing one rather strange situation. I am unable to
enter Ukraine calls into my log. The DXCC field flashes red. The Code box
reads 288. After I exit, (delete the QSO),I get a box which reads there
"The
DXCC Progress table contains no entry for DXCC prefix UT". I examined the
DXCC database in Access and UT appears there. I have all the latest
updates
installed. Gremlins have crept in somewhere I suspect.

First, verify that you have the current version of the DXCC database
installed; on the General tab of DXKeeper's Config window, click the
"Database Info" button at the bottom. If the DXCC database version is not
2.2.7, then terminate DXKeeper (and SpotCollector, if its running), open
the
Databases tab of DXView's Config window, and click the button to upgrade
your DXCC database.

Then restart DXKeeper (if you had to terminate it to upgrade the DXCC
database), and click the Recompute button at the bottom of the Main
window's
"Check Progress" tab.

If this doesn't clear up the "no entry for DXCC prefix UT" problem,
please let me know.

73,

Dave, AA6YQ



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

Yahoo! Groups Links




--
***Here is an Important Message for anyone who receives this email:***
If you forward this correspondence, please delete the forwarding history,
which includes my email address! It is a courtesy to me and others who may
not wish to have their email addresses sent all over the world! Erasing the
history helps prevent Spammers from mining addresses and viruses from being
propagated!



Kurt Arseneault

273 Meadow Lane,
Kentville, NS B4N 3V8
Canada

807 E 21 ST, Unit 11,
Mission, TX 78572

(956) 584-1769 (condo)
902-679-9783 (home Nova Scotia)
902-680-6230 (cell Nova Scotia)






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

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/02/09
05:50:00


Re: DXK rejects Ukraine entries

Kurt Arseneault
 

Thanks for your prompt reply Dave, my DXCC database is 2.2.7.
Regards,
Kurt VE1TT



2009/9/2 Dave AA6YQ <aa6yq@...>

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kurt
Arseneault
Sent: Wednesday, September 02, 2009 9:39 AM
To: dxlab@...
Subject: [dxlab] DXK rejects Ukraine entries


FIrst of all, I want to express my thanks to you for such a powerful suite
of programs. I have been using DX Lab Suites for several months and love
it.
Your level of support for the software through the group is something I
have
rarely seen and you are to be commended for it.

However, I am experiencing one rather strange situation. I am unable to
enter Ukraine calls into my log. The DXCC field flashes red. The Code box
reads 288. After I exit, (delete the QSO),I get a box which reads there
"The
DXCC Progress table contains no entry for DXCC prefix UT". I examined the
DXCC database in Access and UT appears there. I have all the latest updates
installed. Gremlins have crept in somewhere I suspect.

First, verify that you have the current version of the DXCC database
installed; on the General tab of DXKeeper's Config window, click the
"Database Info" button at the bottom. If the DXCC database version is not
2.2.7, then terminate DXKeeper (and SpotCollector, if its running), open
the
Databases tab of DXView's Config window, and click the button to upgrade
your DXCC database.

Then restart DXKeeper (if you had to terminate it to upgrade the DXCC
database), and click the Recompute button at the bottom of the Main
window's
"Check Progress" tab.

If this doesn't clear up the "no entry for DXCC prefix UT" problem,
please let me know.

73,

Dave, AA6YQ



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

Yahoo! Groups Links



--
***Here is an Important Message for anyone who receives this email:***
If you forward this correspondence, please delete the forwarding history,
which includes my email address! It is a courtesy to me and others who may
not wish to have their email addresses sent all over the world! Erasing the
history helps prevent Spammers from mining addresses and viruses from being
propagated!



Kurt Arseneault

273 Meadow Lane,
Kentville, NS B4N 3V8
Canada

807 E 21 ST, Unit 11,
Mission, TX 78572

(956) 584-1769 (condo)
902-679-9783 (home Nova Scotia)
902-680-6230 (cell Nova Scotia)


Re: DXK rejects Ukraine entries

 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Kurt
Arseneault
Sent: Wednesday, September 02, 2009 9:39 AM
To: dxlab@...
Subject: [dxlab] DXK rejects Ukraine entries


FIrst of all, I want to express my thanks to you for such a powerful suite
of programs. I have been using DX Lab Suites for several months and love it.
Your level of support for the software through the group is something I have
rarely seen and you are to be commended for it.

However, I am experiencing one rather strange situation. I am unable to
enter Ukraine calls into my log. The DXCC field flashes red. The Code box
reads 288. After I exit, (delete the QSO),I get a box which reads there "The
DXCC Progress table contains no entry for DXCC prefix UT". I examined the
DXCC database in Access and UT appears there. I have all the latest updates
installed. Gremlins have crept in somewhere I suspect.

First, verify that you have the current version of the DXCC database
installed; on the General tab of DXKeeper's Config window, click the
"Database Info" button at the bottom. If the DXCC database version is not
2.2.7, then terminate DXKeeper (and SpotCollector, if its running), open the
Databases tab of DXView's Config window, and click the button to upgrade
your DXCC database.

Then restart DXKeeper (if you had to terminate it to upgrade the DXCC
database), and click the Recompute button at the bottom of the Main window's
"Check Progress" tab.

If this doesn't clear up the "no entry for DXCC prefix UT" problem,
please let me know.

73,

Dave, AA6YQ


Re: Expired QSOs

wc5m
 

Another example: The YASME Foundation answers QSL Requests for Lloyd Colvin and his XYL (Both SK) since they sponsored many of their DXpeditions. I recently got them to send me a card for a QSO in 1985.

Mark WC5M

--- In dxlab@..., "FireBrick" <w9ol@...> wrote:

There have been many cases where a 3rd party has been able to take over qsl
duties for a deceased ham.
I don't know if there is an 'official procedure', for such a continuation.
But I have seen notices that a xyl or family member has turned over the logs
to a friend or club member of the deceased.

I and other QSL Manager Assoc. members took over possesion and qsl duties
when one of the big qsl managers passed a few year back.


On 9/2/2009 12:46:23 AM, Peter Jordahl (k5gm@...) wrote:
Thanks Art and Dave,
I had not thought to also mark the electronic confirmations as 'X'.
That will
be easily done and solves the problem. I have several such
QSO's; does
anyone
know whether others can QSL for an SK ham given that they have a log
showing
the QSO (I have in mind specifically 3A2GL, now SK) just as if they were
a
QSL manager?

Obviously I should have kept more up-to-date with my QSLs!

73
Pete K5GM

On Wed, 02 Sep 2009 01:42 +0000, "aa6yq" <aa6yq@...> wrote:
I believe the current implementation to be correct: if you are so
certain
that a QSL will never be confirmed that you don't
want it counted as
"worked" in your DXCC award progress, then set both "QSL Rcvd" and
"LotW
QSL Rcvd" to 'X' as Art suggests below; if you no longer wanted
it
counted towards your WAZ award progress, then also set "eQSL QSL Rcvd"
to
'X'.

If you've written off a QSO in this way, I don't see the point of
highlighting its existence in award progress displays and reports.

73,

Dave, AA6YQ


Re: Pathfinder/QRZ Problem

Larry - K2GN
 

I see the same thing when I do a "cut and paste" of the address from normal QRZ.com.
de K2GN/Larry


DXK rejects Ukraine entries

Kurt Arseneault
 

FIrst of all, I want to express my thanks to you for such a powerful suite
of programs. I have been using DX Lab Suites for several months and love it.
Your level of support for the software through the group is something I have
rarely seen and you are to be commended for it.

However, I am experiencing one rather strange situation. I am unable to
enter Ukraine calls into my log. The DXCC field flashes red. The Code box
reads 288. After I exit, (delete the QSO),I get a box which reads there "The
DXCC Progress table contains no entry for DXCC prefix UT". I examined the
DXCC database in Access and UT appears there. I have all the latest updates
installed. Gremlins have crept in somewhere I suspect.

Your thoughts would be appreciated Dave......

Kurt VE1TT


Kurt Arseneault

273 Meadow Lane,
Kentville, NS B4N 3V8
Canada

807 E 21 ST, Unit 11,
Mission, TX 78572

(956) 584-1769 (condo)
902-679-9783 (home Nova Scotia)
902-680-6230 (cell Nova Scotia)


Re: Database?? & printing

 

There is no password. Just double click on w4ijy.mdb and it should open automatically in Access. If not, something is wrong with your Access installation or your default file associations.

73, Rich - W3ZJ

w4ijy wrote:

And I have been trying to import the w4ijy.mdb file to my Access 2007 for further analysis specific to my needs. When accessing the w4ijy file I am queryed for the password. Is the password the developer's use only?


Re: Expired QSOs

FireBrick
 

There have been many cases where a 3rd party has been able to take over qsl duties for a deceased ham.
I don't know if there is an 'official procedure', for such a continuation. But I have seen notices that a xyl or family member has turned over the logs to a friend or club member of the deceased.

I and other QSL Manager Assoc. members took over possesion and qsl duties when one of the big qsl managers passed a few year back.

On 9/2/2009 12:46:23 AM, Peter Jordahl (k5gm@...) wrote:
Thanks Art and Dave,
I had not thought to also mark the electronic confirmations as 'X'.
That will
be easily done and solves the problem. I have several such
QSO's; does
anyone
know whether others can QSL for an SK ham given that they have a log
showing
the QSO (I have in mind specifically 3A2GL, now SK) just as if they were
a
QSL manager?

Obviously I should have kept more up-to-date with my QSLs!

73
Pete K5GM

On Wed, 02 Sep 2009 01:42 +0000, "aa6yq" <aa6yq@...> wrote:
I believe the current implementation to be correct: if you are so certain
that a QSL will never be confirmed that you don't
want it counted as
"worked" in your DXCC award progress, then set both "QSL Rcvd" and
"LotW
QSL Rcvd" to 'X' as Art suggests below; if you no longer wanted
it
counted towards your WAZ award progress, then also set "eQSL QSL Rcvd"
to
'X'.

If you've written off a QSO in this way, I don't see the point of
highlighting its existence in award progress displays and reports.

73,

Dave, AA6YQ


Re: Expired QSOs

 

Thanks Art and Dave,
I had not thought to also mark the electronic confirmations as 'X'.
That will
be easily done and solves the problem. I have several such QSO's; does
anyone
know whether others can QSL for an SK ham given that they have a log
showing
the QSO (I have in mind specifically 3A2GL, now SK) just as if they were
a
QSL manager?

Obviously I should have kept more up-to-date with my QSLs!

73
Pete K5GM

On Wed, 02 Sep 2009 01:42 +0000, "aa6yq" <aa6yq@...> wrote:
I believe the current implementation to be correct: if you are so certain
that a QSL will never be confirmed that you don't want it counted as
"worked" in your DXCC award progress, then set both "QSL Rcvd" and "LotW
QSL Rcvd" to 'X' as Art suggests below; if you no longer wanted it
counted towards your WAZ award progress, then also set "eQSL QSL Rcvd" to
'X'.

If you've written off a QSO in this way, I don't see the point of
highlighting its existence in award progress displays and reports.

73,

Dave, AA6YQ





--- In dxlab@..., Art Searle <w2nra@...> wrote:

Hi Pete,

If you mark both QSL Rcvd and LotW QSL Rcvd to X then it won't appear
in DXView as W. For if both are not marked X, you haven't truly given
up on the QSL.

I do like your idea of X showing in DXView if only one is marked X.
However I have a feeling that would be a major undertaking. Perhaps
adding it as a feature request for when Dave has more time to
implement it.

73 Art W2NRA
"Keep to the Code!"
w2nra.com

On Sep 1, 2009, at 6:41 PM, Peter Jordahl <k5gm@...> wrote:

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@...



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

Yahoo! Groups Links





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

Yahoo! Groups Links


Pete Jordahl, K5GM
k5gm@...


Pathfinder 4.5.7 is available

 

When performing a QRZ.com callbook lookup for DXKeeper, this release correctly decodes the new QRZ.com display format.

Note: I do not believe that the QRZ.com display format was changed to impede the free use of QRZ.com by applications like Pathfinder; if that were the goal, it would be easy to display the information in an image rather than as text, as is done on the HamCall web page. The owner of QRZ.com makes just as much revenue from the advertisements displayed by Pathfinder as he does when these ads are displayed by a conventional web browser.

Pathfinder 4.5.7 is available via the DXLab Launcher and via

<www.dxlabsuite.com/download.htm>

73,

Dave, AA6YQ


Re: Database?? & printing

 

AA6YQ comments below
--- In dxlab@..., "w4ijy" <w4ijy@...> wrote:

I am new to DXLab

Welcome!
and have been impressed. However, I can not print out the log for permanent files.

To generate a text report containing all QSOs in the Log Page Display, click the Report button on the Main window's Log QSOs tab.

And I have been trying to import the w4ijy.mdb file to my Access 2007 for further analysis specific to my needs. When accessing the w4ijy file I am queryed for the password. Is the password the developer's use only?

DXKeeper does not password-protect your log file; I don't know why Access is prompting your for a password.
It is all too easy to inadvertently modify your log file in Access, and the result could be unreadable by DXKeeper; thus I strongly suggest using Windows Explorer to make a copy of your log file and limiting your Access explorations to that copy. Also, you should direct Access to open the copy of your log file, not import it.
73,

Dave, AA6YQ


Re: Expired QSOs

 

I believe the current implementation to be correct: if you are so certain that a QSL will never be confirmed that you don't want it counted as "worked" in your DXCC award progress, then set both "QSL Rcvd" and "LotW QSL Rcvd" to 'X' as Art suggests below; if you no longer wanted it counted towards your WAZ award progress, then also set "eQSL QSL Rcvd" to 'X'.

If you've written off a QSO in this way, I don't see the point of highlighting its existence in award progress displays and reports.

73,

Dave, AA6YQ

--- In dxlab@..., Art Searle <w2nra@...> wrote:

Hi Pete,

If you mark both QSL Rcvd and LotW QSL Rcvd to X then it won't appear
in DXView as W. For if both are not marked X, you haven't truly given
up on the QSL.

I do like your idea of X showing in DXView if only one is marked X.
However I have a feeling that would be a major undertaking. Perhaps
adding it as a feature request for when Dave has more time to
implement it.

73 Art W2NRA
"Keep to the Code!"
w2nra.com

On Sep 1, 2009, at 6:41 PM, Peter Jordahl <k5gm@...> wrote:

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@...



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

Yahoo! Groups Links



Database?? & printing

w4ijy
 

I am new to DXLab and have been impressed. However, I can not print out the log for permanent files. And I have been trying to import the w4ijy.mdb file to my Access 2007 for further analysis specific to my needs. When accessing the w4ijy file I am queryed for the password. Is the password the developer's use only?

Any help will be appreciated.

73, W4IJY Dwight


Re: Expired QSOs

Art Searle
 

Hi Pete,

If you mark both QSL Rcvd and LotW QSL Rcvd to X then it won't appear in DXView as W. For if both are not marked X, you haven't truly given up on the QSL.

I do like your idea of X showing in DXView if only one is marked X. However I have a feeling that would be a major undertaking. Perhaps adding it as a feature request for when Dave has more time to implement it.

73 Art W2NRA
"Keep to the Code!"
w2nra.com

On Sep 1, 2009, at 6:41 PM, Peter Jordahl <k5gm@...> wrote:

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@...



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

Yahoo! Groups Links



Expired QSOs

 

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@...


Re: Pathfinder/QRZ Problem

 

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@... [mailto:dxlab@...]On Behalf Of
empennage2003
Sent: Tuesday, September 01, 2009 6:05 PM
To: dxlab@...
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@...



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

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

 

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@...


Re: Another Pathfinder/QRZ problem?

 

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

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
pcooper
Sent: Tuesday, September 01, 2009 11:58 AM
To: dxlab@...
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