开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. DXLab
  2. Messages
Expanded Topics Messages Polls
Date
Re: Pathfinder 3.0

Dave Bernstein
 

Alternatively, you can avoid all of this by using the Pathfinder Web
Client -- this is a web-based version of Pathfinder that require no
downloading, installation, or search library updates. Its a little
less flexible, in that you have no control of which searches are on
buttons, but updates are automatic.

Give it a try at

73,

Dave, AA6YQ


--- In dxlab@y..., "Dave Bernstein" <dhb@m...> wrote:
When you install Pathfinder 3.0, the included search library is
obsolete. Step 7 of the download/installation instructions (
) suggests that
you
immediately upgrade your search library. The problems you and Robin
cite, now that I recall the search changes since Pathfinder 3.0 was
released, are almost certainly due obsolete searche files.

To update your search files, follow the instructions at
. After
performing this download, you must update the searches associated
with buttons, e.g. QRZ and DXS. This procedure is described in
.

I acknowledge that this process could be more automated -- the
original Pathfinder design assumed that users would update searches
themselves, and directly exchange the files, rather than rely on a
centralized repository that a few people maintain. I do plan a
major
Pathfinder update that will make search library updating a
completely
automatic process.

73,

Dave, AA6YQ
--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
I find that I can bring up QRZ.com OK but it does not put the
callsign that I have entered into the search window and find it. I
have to type it in again and do the search from there. The same
thing happens with BUCK.COM, WM7D works fine. DXC R gives me a 404
Object not found error, DXS gives me an Internal Server Error, DXM
gives me a 404 error. When I type in my own callsign in the
Pathfinder window, the pop up site that comes up is Deja (very
strange for a W3 call) clicking on Deja gives me a 400 Bad Request
error.

73 - Rich - W3ZJ

-----Original Message-----
From: RTrebil640@a... [mailto:RTrebil640@a...]
Sent: Friday, March 30, 2001 13:29 PM
To: dxlab@y...
Subject: [dxlab] Re: Pathfinder 3.0


Can't be that Dave. I access qrz.com almost every day
by typing the
URL into my web browser, with no problems. It is only
when I try to
access it with Pathfinder that I get the message "You are not
authorised to view this page" But for the record, I did
change the
security settings, with no effect
Robin gw3zcf


--- In dxlab@y..., "Dave Bernstein" <dhb@m...> wrote:
Pathfinder is subject to the security settings maintained by
Internet
Explorer. It sounds like yours are a bit too tight.

To verify this, start Internet Explorer and display
. If you get the "you're not authorized..."
message, then modify security settings as suggested
in the next
paragraph. If qrz.com works fine, then my hypothesis
is incorrect.

To change security settings from within Internet
Explorer, click on
its Tools menu, and select the "Internet Security"
tab. You can use
as a test case -- if you've sufficiently
loosened
security to the point where Internet Explorer will
display this
page,
then then Pathfinder should be able to display QSL
information
pages.

Let me know how it goes...

73,

Dave, AA6YQ

--- In dxlab@y..., RTrebil640@a... wrote:
I have just downloaded and installed Pathfinder 3.0
But when I
enter a call sign and press one of the buttons, I
just get a page
which says "You are not authorised to view this page"
What have I missed?
Robin gw3zcf

------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@y...



Your use of Yahoo! Groups is subject to
Re: Pathfinder 3.0

Dave Bernstein
 

When you install Pathfinder 3.0, the included search library is
obsolete. Step 7 of the download/installation instructions (
) suggests that you
immediately upgrade your search library. The problems you and Robin
cite, now that I recall the search changes since Pathfinder 3.0 was
released, are almost certainly due obsolete searche files.

To update your search files, follow the instructions at
. After
performing this download, you must update the searches associated
with buttons, e.g. QRZ and DXS. This procedure is described in
.

I acknowledge that this process could be more automated -- the
original Pathfinder design assumed that users would update searches
themselves, and directly exchange the files, rather than rely on a
centralized repository that a few people maintain. I do plan a major
Pathfinder update that will make search library updating a completely
automatic process.

73,

Dave, AA6YQ

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
I find that I can bring up QRZ.com OK but it does not put the
callsign that I have entered into the search window and find it. I
have to type it in again and do the search from there. The same
thing happens with BUCK.COM, WM7D works fine. DXC R gives me a 404
Object not found error, DXS gives me an Internal Server Error, DXM
gives me a 404 error. When I type in my own callsign in the
Pathfinder window, the pop up site that comes up is Deja (very
strange for a W3 call) clicking on Deja gives me a 400 Bad Request
error.

73 - Rich - W3ZJ

-----Original Message-----
From: RTrebil640@a... [mailto:RTrebil640@a...]
Sent: Friday, March 30, 2001 13:29 PM
To: dxlab@y...
Subject: [dxlab] Re: Pathfinder 3.0


Can't be that Dave. I access qrz.com almost every day
by typing the
URL into my web browser, with no problems. It is only
when I try to
access it with Pathfinder that I get the message "You are not
authorised to view this page" But for the record, I did
change the
security settings, with no effect
Robin gw3zcf


--- In dxlab@y..., "Dave Bernstein" <dhb@m...> wrote:
Pathfinder is subject to the security settings maintained by
Internet
Explorer. It sounds like yours are a bit too tight.

To verify this, start Internet Explorer and display
. If you get the "you're not authorized..."
message, then modify security settings as suggested
in the next
paragraph. If qrz.com works fine, then my hypothesis
is incorrect.

To change security settings from within Internet
Explorer, click on
its Tools menu, and select the "Internet Security"
tab. You can use
as a test case -- if you've sufficiently
loosened
security to the point where Internet Explorer will
display this
page,
then then Pathfinder should be able to display QSL
information
pages.

Let me know how it goes...

73,

Dave, AA6YQ

--- In dxlab@y..., RTrebil640@a... wrote:
I have just downloaded and installed Pathfinder 3.0
But when I
enter a call sign and press one of the buttons, I
just get a page
which says "You are not authorised to view this page"
What have I missed?
Robin gw3zcf

------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@y...



Your use of Yahoo! Groups is subject to
Re: Pathfinder 3.0

 

I find that I can bring up QRZ.com OK but it does not put the
callsign that I have entered into the search window and find it. I
have to type it in again and do the search from there. The same
thing happens with BUCK.COM, WM7D works fine. DXC R gives me a 404
Object not found error, DXS gives me an Internal Server Error, DXM
gives me a 404 error. When I type in my own callsign in the
Pathfinder window, the pop up site that comes up is Deja (very
strange for a W3 call) clicking on Deja gives me a 400 Bad Request
error.

73 - Rich - W3ZJ

-----Original Message-----
From: RTrebil640@... [mailto:RTrebil640@...]
Sent: Friday, March 30, 2001 13:29 PM
To: dxlab@...
Subject: [dxlab] Re: Pathfinder 3.0


Can't be that Dave. I access qrz.com almost every day
by typing the
URL into my web browser, with no problems. It is only
when I try to
access it with Pathfinder that I get the message "You are not
authorised to view this page" But for the record, I did
change the
security settings, with no effect
Robin gw3zcf


--- In dxlab@y..., "Dave Bernstein" <dhb@m...> wrote:
Pathfinder is subject to the security settings maintained by
Internet
Explorer. It sounds like yours are a bit too tight.

To verify this, start Internet Explorer and display
. If you get the "you're not authorized..."
message, then modify security settings as suggested
in the next
paragraph. If qrz.com works fine, then my hypothesis
is incorrect.

To change security settings from within Internet
Explorer, click on
its Tools menu, and select the "Internet Security"
tab. You can use
as a test case -- if you've sufficiently
loosened
security to the point where Internet Explorer will
display this
page,
then then Pathfinder should be able to display QSL
information
pages.

Let me know how it goes...

73,

Dave, AA6YQ

--- In dxlab@y..., RTrebil640@a... wrote:
I have just downloaded and installed Pathfinder 3.0
But when I
enter a call sign and press one of the buttons, I
just get a page
which says "You are not authorised to view this page"
What have I missed?
Robin gw3zcf

------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
Re: Pathfinder 3.0

[email protected]
 

Can't be that Dave. I access qrz.com almost every day by typing the
URL into my web browser, with no problems. It is only when I try to
access it with Pathfinder that I get the message "You are not
authorised to view this page" But for the record, I did change the
security settings, with no effect
Robin gw3zcf


--- In dxlab@y..., "Dave Bernstein" <dhb@m...> wrote:
Pathfinder is subject to the security settings maintained by
Internet
Explorer. It sounds like yours are a bit too tight.

To verify this, start Internet Explorer and display
. If you get the "you're not authorized..."
message, then modify security settings as suggested in the next
paragraph. If qrz.com works fine, then my hypothesis is incorrect.

To change security settings from within Internet Explorer, click on
its Tools menu, and select the "Internet Security" tab. You can use
as a test case -- if you've sufficiently
loosened
security to the point where Internet Explorer will display this
page,
then then Pathfinder should be able to display QSL information
pages.

Let me know how it goes...

73,

Dave, AA6YQ

--- In dxlab@y..., RTrebil640@a... wrote:
I have just downloaded and installed Pathfinder 3.0 But when I
enter a call sign and press one of the buttons, I just get a page
which says "You are not authorised to view this page"
What have I missed?
Robin gw3zcf
Re: Pathfinder 3.0

Dave Bernstein
 

Pathfinder is subject to the security settings maintained by Internet
Explorer. It sounds like yours are a bit too tight.

To verify this, start Internet Explorer and display
. If you get the "you're not authorized..."
message, then modify security settings as suggested in the next
paragraph. If qrz.com works fine, then my hypothesis is incorrect.

To change security settings from within Internet Explorer, click on
its Tools menu, and select the "Internet Security" tab. You can use
as a test case -- if you've sufficiently loosened
security to the point where Internet Explorer will display this page,
then then Pathfinder should be able to display QSL information pages.

Let me know how it goes...

73,

Dave, AA6YQ

--- In dxlab@y..., RTrebil640@a... wrote:
I have just downloaded and installed Pathfinder 3.0 But when I
enter a call sign and press one of the buttons, I just get a page
which says "You are not authorised to view this page"
What have I missed?
Robin gw3zcf
Pathfinder 3.0

[email protected]
 

I have just downloaded and installed Pathfinder 3.0 But when I
enter a call sign and press one of the buttons, I just get a page
which says "You are not authorised to view this page"
What have I missed?
Robin gw3zcf
Pathfinder Users: new YB search

Dave, AA6YQ
 

Thanks to Fred K3ZO, Pathfinder can now search the online Indonesian
callbook. Access to this site can be a little slow, as requests and results
must traverse the Amateur Packet Radio (AMPR) Network, making response time
dependent on channel utilization and the load at the AMPRNet-Internet
gateway.

To update your search library, click Pathfinder's "Info" button, or link to
. The Pathfinder Web
Client ( ) has been updated with
the above addition; the only action required of its users is to click their
Browser's "refresh" button.

As always, reports of new online QSL sources or changes to existing sources
are greatly appreciated.

73,

Dave, AA6YQ

Pathfinder is a free program that makes it easy to find QSL information from
more than 100 web-accessible sources. See for
additional information and download instructions. Or use the Pathfinder Web
Client -- its a little less flexible, but requires no downloading or
installation and runs in any Javascript-supporting browser on Windows,
MacOS, Linux, or Unix; just visit .
DXLab 1.1.8 is available

Dave, AA6YQ
 

This release

- corrects a defect that produced a crash if you tried to close DXKeeper
while it was iconified

- in the QSO Capture window, clearing all fields leaves the text entry
cursor in the callsign field

If you've already installed DXKeeper 1.1.1 or later, you can upgrade to
version 1.1.8 by downloading and then running
www.qsl.net/dxkeeper/DXKeeper118Update.exe -- your online help will be
updated by this process.


73,

Dave, AA6YQ
Re: Capture window clear button.

 

Come on! For what we are paying you, you should be right on top of
all this :-) Just kidding of course, I am amazed that you are able
to respond as fast as you do to these things.

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave Bernstein [mailto:dhb@...]
Sent: Monday, March 26, 2001 3:12 AM
To: dxlab@...
Subject: [dxlab] Re: Capture window clear button.


This is easily implemented, and the "crash while
iconified" defect is
easily repaired -- but work committments will push this
out a few
days.

73,

Dave, AA6YQ
--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
It would be nice after clicking "clear" in the
capture window if
the keyboard focus would go to the callsign entry window as it
does after clicking "log". I often find myself trying
to type a
new callsign into the clear button :-)

-----
73, Rich - W3ZJ
www.w3zj.com

------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
Re: Capture window clear button.

Dave Bernstein
 

This is easily implemented, and the "crash while iconified" defect is
easily repaired -- but work committments will push this out a few
days.

73,

Dave, AA6YQ

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
It would be nice after clicking "clear" in the capture window if
the keyboard focus would go to the callsign entry window as it
does after clicking "log". I often find myself trying to type a
new callsign into the clear button :-)

-----
73, Rich - W3ZJ
www.w3zj.com
Capture window clear button.

 

It would be nice after clicking "clear" in the capture window if
the keyboard focus would go to the callsign entry window as it
does after clicking "log". I often find myself trying to type a
new callsign into the clear button :-)

-----
73, Rich - W3ZJ
www.w3zj.com
Run-time error

 

Closing DXKeeper while it is minimized on the task bar by right
clicking on the task bar icon and selecting close, produces the
following error:

"Run-time error '384' A form can't be moved or sized while
minimized or maximized"

-----
73, Rich - W3ZJ
www.w3zj.com
Re: DXKeeper 1.1.7 is available

 

You have it cooking now Dave.

73, Rich - w3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Saturday, March 24, 2001 22:40 PM
To: dxlab@...
Subject: [dxlab] DXKeeper 1.1.7 is available


This release

- corrects a defect that prevented the import
operation from properly
crediting QSOs that were worked but not confirmed

- corrects a defect that caused PSK QSOs to not be
included in Mixed
results

- can generate a detailed progress report (click the
"Report" button on
the Progress tab)

- when the "Import from Logger" box is checked,
relocates the second and
subsequent words of the incoming Name field to the Notes field.

If you've already installed DXKeeper 1.1.1 or later,
you can upgrade to
version 1.1.7 by downloading and then running
www.qsl.net/dxkeeper/DXKeeper117Update.exe -- your
online help will be
updated by this process.


73,

Dave, AA6YQ





------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to



DXKeeper 1.1.7 is available

Dave, AA6YQ
 

This release

- corrects a defect that prevented the import operation from properly
crediting QSOs that were worked but not confirmed

- corrects a defect that caused PSK QSOs to not be included in Mixed
results

- can generate a detailed progress report (click the "Report" button on
the Progress tab)

- when the "Import from Logger" box is checked, relocates the second and
subsequent words of the incoming Name field to the Notes field.

If you've already installed DXKeeper 1.1.1 or later, you can upgrade to
version 1.1.7 by downloading and then running
www.qsl.net/dxkeeper/DXKeeper117Update.exe -- your online help will be
updated by this process.


73,

Dave, AA6YQ
Re: DXKeeper 1.1.6 is available

 

I think the answer that would best satisfy the most people (and
certainly me), is place the first word in the name field and every
thing else in the comment field. It won't be 100% but it will be
right more often than wrong.

----
73, Rich

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Saturday, March 24, 2001 17:28 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


If there's no standard for how the information is
jammed together, then it
will be difficult to satisfy everyone. Sounds like
"Import from Logger"
should mean "place the contents of the name field into
the comments field",
or maybe "place everything after the first word of the
name field into the
comments field".

I'll leave it as it is for now, but suggests would be
greatly appreciated...

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 15:58 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Yes, of course I saw that too and Logger is a bit
flaky on that
score because it doesn't have separate fields for
name and QTH and
the exports the comment field with the <NAME> tag. I could see
what your difficulty was there and actually I thought
you did a
pretty good job of unscrambling the mess. Keep in
mind that Logger
does not require a colon between the name and the rest of the
comment field, the only real separator is white
space. Some of my
entries have a colon because they were imported from
yet another
logging program that I used early on. More recent entries that
were made directly into Logger do not have a colon.
That may help
you as you attempt to refine the parsing process but
you'll never
get it perfect. That comment field is totally free
form and can
contain almost anything. Most of my entries do have
"name" as the
first word but what comes after that is anybody's
guess, it's not
necessarily QTH, in fact I only rarely log QTH.

----
73, Rich - W3ZJ

> I noticed a lot of "truncated name" messages. With the
> "Import from Logger"
> box checked, I look for names and qths being
> concatenated in the name field,
> separated by a colon; its easy to split these and place
> the name and QTH in
> their proper fields. But there are lots of situations
> where the name field
> contains contest info, or names and QTHs without a
> separating colon. In
> DXView117, I added code to detect this condition and
> put the contents of the
> name field into the comment field (where there is
> plenty of room); let me
> know if you think this is a bad idea, or have a better
> suggestion.
>
> I've imported your .ADI files several times without a
> crash, but clearly
> there's a latent defect. I'll take a look at QSO# 3757
> to see if it contains
> anything unusual, and will add instrumentation to 117
> so that we can track
> it down.
>
> Has CI-V Commander created any error log files for you
> when you rapidly QSY
> your TenTec?
>
> 73,
>
> Dave, AA6YQ
> -----Original Message-----
> From: Richard B Drake [mailto:rich@...]
> Sent: Saturday, March 24, 2001 13:32 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> Dave,
>
> The import went fine, except for the program error
> that occurs at
> QSO #3757. I found that all I have to do to recover
> from that is
> to close and reopen DXKeeper, then start the
import again. The
> first 3757 are then duplicates and after passing those it
> completes normally. Performance is much improved.
> I'll send you
> the entire ADIF file (privately) so you can see that too.
>
> ---
> 73, Rich - W3ZJ
>
> > -----Original Message-----
> > From: Dave, AA6YQ [mailto:dhb@...]
> > Sent: Saturday, March 24, 2001 12:33 PM
> > To: dxlab@...
> > Subject: RE: [dxlab] DXKeeper 1.1.6 is available
> >
> >
> > That's a pretty good clue, Rich -- it implies that the
> > import operation is
> > not properly handling worked-but-not-confirmed QSOs.
> > I've imported my 13K
> > QSOs (from the first-generation DXLab, which began life
> > as an alternative
> > user interface for log files created by LOGic) and the
> > worked/confirmed/verified numbers match exactly, but
> > perhaps your logging
> > program does things a bit differently, ADIF not
> withstanding.
> >
> > Could you send me the ADIF file you're importing, or at
> > least a fragment
> > containing several worked-but-not-confirmed QSOs?
> >
> > Was the import operation reliable? How was import
> performance?
> >
> > 73,
> >
> > Dave, AA6YQ
> > -----Original Message-----
> > From: Richard B Drake [mailto:rich@...]
> > Sent: Saturday, March 24, 2001 12:17 PM
> > To: dxlab@...
> > Subject: RE: [dxlab] DXKeeper 1.1.6 is available
> >
> >
> > Dave,
> >
> > I am still having a problem with the Progress Table
> > not showing
> > correct results for imported log entries. I did a
> little more
> > research and found that the only entries that were
> > appearing in
> > the table were QSO's marked confirmed. The table
> contains all
> > "F's" and no "W's". All the DXCC prefixes for
> worked but not
> > confirmed countries look correct. As a test, I
> entered a new
> > country in the capture window and logged it. Indeed,
> > that contact
> > now shows up as the only "W" in the progress
> table. Doing a
> > recompute doesn't change things. I have no idea
> > what's going on
> > but maybe that's clue for you. If you like I can zip
> > up a copy of
> > my mdb file and mail it to you.
> >
> > ----
> > 73, Rich - W3ZJ
> >
> >
> > Yahoo! Groups Sponsor
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > dxlab-unsubscribe@...
> >
> >
> >
> > Your use of Yahoo! Groups is subject to the Yahoo!
> > Terms of Service.
> >
> >
> >
> >
> >
> >
> > ------------------------ Yahoo! Groups Sponsor
> >
> > To unsubscribe from this group, send an email to:
> > dxlab-unsubscribe@...
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> >
> >
> >
> >
>
>
> Yahoo! Groups Sponsor
>
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo!
> Terms of Service.
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
>
>
>
>


Yahoo! Groups Sponsor

iWin.com - The Place to Win Stuff!


To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service.






------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
Re: DXKeeper 1.1.6 is available

Dave, AA6YQ
 

If there's no standard for how the information is jammed together, then it
will be difficult to satisfy everyone. Sounds like "Import from Logger"
should mean "place the contents of the name field into the comments field",
or maybe "place everything after the first word of the name field into the
comments field".

I'll leave it as it is for now, but suggests would be greatly appreciated...

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 15:58 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Yes, of course I saw that too and Logger is a bit flaky on that
score because it doesn't have separate fields for name and QTH and
the exports the comment field with the <NAME> tag. I could see
what your difficulty was there and actually I thought you did a
pretty good job of unscrambling the mess. Keep in mind that Logger
does not require a colon between the name and the rest of the
comment field, the only real separator is white space. Some of my
entries have a colon because they were imported from yet another
logging program that I used early on. More recent entries that
were made directly into Logger do not have a colon. That may help
you as you attempt to refine the parsing process but you'll never
get it perfect. That comment field is totally free form and can
contain almost anything. Most of my entries do have "name" as the
first word but what comes after that is anybody's guess, it's not
necessarily QTH, in fact I only rarely log QTH.

----
73, Rich - W3ZJ

> I noticed a lot of "truncated name" messages. With the
> "Import from Logger"
> box checked, I look for names and qths being
> concatenated in the name field,
> separated by a colon; its easy to split these and place
> the name and QTH in
> their proper fields. But there are lots of situations
> where the name field
> contains contest info, or names and QTHs without a
> separating colon. In
> DXView117, I added code to detect this condition and
> put the contents of the
> name field into the comment field (where there is
> plenty of room); let me
> know if you think this is a bad idea, or have a better
> suggestion.
>
> I've imported your .ADI files several times without a
> crash, but clearly
> there's a latent defect. I'll take a look at QSO# 3757
> to see if it contains
> anything unusual, and will add instrumentation to 117
> so that we can track
> it down.
>
> Has CI-V Commander created any error log files for you
> when you rapidly QSY
> your TenTec?
>
> 73,
>
> Dave, AA6YQ
> -----Original Message-----
> From: Richard B Drake [mailto:rich@...]
> Sent: Saturday, March 24, 2001 13:32 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> Dave,
>
> The import went fine, except for the program error
> that occurs at
> QSO #3757. I found that all I have to do to recover
> from that is
> to close and reopen DXKeeper, then start the import again. The
> first 3757 are then duplicates and after passing those it
> completes normally. Performance is much improved.
> I'll send you
> the entire ADIF file (privately) so you can see that too.
>
> ---
> 73, Rich - W3ZJ
>
> > -----Original Message-----
> > From: Dave, AA6YQ [mailto:dhb@...]
> > Sent: Saturday, March 24, 2001 12:33 PM
> > To: dxlab@...
> > Subject: RE: [dxlab] DXKeeper 1.1.6 is available
> >
> >
> > That's a pretty good clue, Rich -- it implies that the
> > import operation is
> > not properly handling worked-but-not-confirmed QSOs.
> > I've imported my 13K
> > QSOs (from the first-generation DXLab, which began life
> > as an alternative
> > user interface for log files created by LOGic) and the
> > worked/confirmed/verified numbers match exactly, but
> > perhaps your logging
> > program does things a bit differently, ADIF not
> withstanding.
> >
> > Could you send me the ADIF file you're importing, or at
> > least a fragment
> > containing several worked-but-not-confirmed QSOs?
> >
> > Was the import operation reliable? How was import
> performance?
> >
> > 73,
> >
> > Dave, AA6YQ
> > -----Original Message-----
> > From: Richard B Drake [mailto:rich@...]
> > Sent: Saturday, March 24, 2001 12:17 PM
> > To: dxlab@...
> > Subject: RE: [dxlab] DXKeeper 1.1.6 is available
> >
> >
> > Dave,
> >
> > I am still having a problem with the Progress Table
> > not showing
> > correct results for imported log entries. I did a
> little more
> > research and found that the only entries that were
> > appearing in
> > the table were QSO's marked confirmed. The table
> contains all
> > "F's" and no "W's". All the DXCC prefixes for
> worked but not
> > confirmed countries look correct. As a test, I
> entered a new
> > country in the capture window and logged it. Indeed,
> > that contact
> > now shows up as the only "W" in the progress
> table. Doing a
> > recompute doesn't change things. I have no idea
> > what's going on
> > but maybe that's clue for you. If you like I can zip
> > up a copy of
> > my mdb file and mail it to you.
> >
> > ----
> > 73, Rich - W3ZJ
> >
> >
> > Yahoo! Groups Sponsor
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > dxlab-unsubscribe@...
> >
> >
> >
> > Your use of Yahoo! Groups is subject to the Yahoo!
> > Terms of Service.
> >
> >
> >
> >
> >
> >
> > ------------------------ Yahoo! Groups Sponsor
> >
> > To unsubscribe from this group, send an email to:
> > dxlab-unsubscribe@...
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> >
> >
> >
> >
>
>
> Yahoo! Groups Sponsor
>
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo!
> Terms of Service.
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
>
>
>
>


Yahoo! Groups Sponsor

iWin.com - The Place to Win Stuff!


To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
Re: DXKeeper 1.1.6 is available

 

Yes, of course I saw that too and Logger is a bit flaky on that
score because it doesn't have separate fields for name and QTH and
the exports the comment field with the <NAME> tag. I could see
what your difficulty was there and actually I thought you did a
pretty good job of unscrambling the mess. Keep in mind that Logger
does not require a colon between the name and the rest of the
comment field, the only real separator is white space. Some of my
entries have a colon because they were imported from yet another
logging program that I used early on. More recent entries that
were made directly into Logger do not have a colon. That may help
you as you attempt to refine the parsing process but you'll never
get it perfect. That comment field is totally free form and can
contain almost anything. Most of my entries do have "name" as the
first word but what comes after that is anybody's guess, it's not
necessarily QTH, in fact I only rarely log QTH.

----
73, Rich - W3ZJ

I noticed a lot of "truncated name" messages. With the
"Import from Logger"
box checked, I look for names and qths being
concatenated in the name field,
separated by a colon; its easy to split these and place
the name and QTH in
their proper fields. But there are lots of situations
where the name field
contains contest info, or names and QTHs without a
separating colon. In
DXView117, I added code to detect this condition and
put the contents of the
name field into the comment field (where there is
plenty of room); let me
know if you think this is a bad idea, or have a better
suggestion.

I've imported your .ADI files several times without a
crash, but clearly
there's a latent defect. I'll take a look at QSO# 3757
to see if it contains
anything unusual, and will add instrumentation to 117
so that we can track
it down.

Has CI-V Commander created any error log files for you
when you rapidly QSY
your TenTec?

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 13:32 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Dave,

The import went fine, except for the program error
that occurs at
QSO #3757. I found that all I have to do to recover
from that is
to close and reopen DXKeeper, then start the import again. The
first 3757 are then duplicates and after passing those it
completes normally. Performance is much improved.
I'll send you
the entire ADIF file (privately) so you can see that too.

---
73, Rich - W3ZJ

> -----Original Message-----
> From: Dave, AA6YQ [mailto:dhb@...]
> Sent: Saturday, March 24, 2001 12:33 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> That's a pretty good clue, Rich -- it implies that the
> import operation is
> not properly handling worked-but-not-confirmed QSOs.
> I've imported my 13K
> QSOs (from the first-generation DXLab, which began life
> as an alternative
> user interface for log files created by LOGic) and the
> worked/confirmed/verified numbers match exactly, but
> perhaps your logging
> program does things a bit differently, ADIF not
withstanding.
>
> Could you send me the ADIF file you're importing, or at
> least a fragment
> containing several worked-but-not-confirmed QSOs?
>
> Was the import operation reliable? How was import
performance?
>
> 73,
>
> Dave, AA6YQ
> -----Original Message-----
> From: Richard B Drake [mailto:rich@...]
> Sent: Saturday, March 24, 2001 12:17 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> Dave,
>
> I am still having a problem with the Progress Table
> not showing
> correct results for imported log entries. I did a
little more
> research and found that the only entries that were
> appearing in
> the table were QSO's marked confirmed. The table
contains all
> "F's" and no "W's". All the DXCC prefixes for
worked but not
> confirmed countries look correct. As a test, I
entered a new
> country in the capture window and logged it. Indeed,
> that contact
> now shows up as the only "W" in the progress
table. Doing a
> recompute doesn't change things. I have no idea
> what's going on
> but maybe that's clue for you. If you like I can zip
> up a copy of
> my mdb file and mail it to you.
>
> ----
> 73, Rich - W3ZJ
>
>
> Yahoo! Groups Sponsor
>
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo!
> Terms of Service.
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
>
>
>
>


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service.






------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
Re: DXKeeper 1.1.6 is available

Dave, AA6YQ
 

The progress problem is a defect that was easily fixed; I'll send you a
progress report file so youc an verify that this was the only problem.

I noticed a lot of "truncated name" messages. With the "Import from Logger"
box checked, I look for names and qths being concatenated in the name field,
separated by a colon; its easy to split these and place the name and QTH in
their proper fields. But there are lots of situations where the name field
contains contest info, or names and QTHs without a separating colon. In
DXView117, I added code to detect this condition and put the contents of the
name field into the comment field (where there is plenty of room); let me
know if you think this is a bad idea, or have a better suggestion.

I've imported your .ADI files several times without a crash, but clearly
there's a latent defect. I'll take a look at QSO# 3757 to see if it contains
anything unusual, and will add instrumentation to 117 so that we can track
it down.

Has CI-V Commander created any error log files for you when you rapidly QSY
your TenTec?

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 13:32 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Dave,

The import went fine, except for the program error that occurs at
QSO #3757. I found that all I have to do to recover from that is
to close and reopen DXKeeper, then start the import again. The
first 3757 are then duplicates and after passing those it
completes normally. Performance is much improved. I'll send you
the entire ADIF file (privately) so you can see that too.

---
73, Rich - W3ZJ

> -----Original Message-----
> From: Dave, AA6YQ [mailto:dhb@...]
> Sent: Saturday, March 24, 2001 12:33 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> That's a pretty good clue, Rich -- it implies that the
> import operation is
> not properly handling worked-but-not-confirmed QSOs.
> I've imported my 13K
> QSOs (from the first-generation DXLab, which began life
> as an alternative
> user interface for log files created by LOGic) and the
> worked/confirmed/verified numbers match exactly, but
> perhaps your logging
> program does things a bit differently, ADIF not withstanding.
>
> Could you send me the ADIF file you're importing, or at
> least a fragment
> containing several worked-but-not-confirmed QSOs?
>
> Was the import operation reliable? How was import performance?
>
> 73,
>
> Dave, AA6YQ
> -----Original Message-----
> From: Richard B Drake [mailto:rich@...]
> Sent: Saturday, March 24, 2001 12:17 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> Dave,
>
> I am still having a problem with the Progress Table
> not showing
> correct results for imported log entries. I did a little more
> research and found that the only entries that were
> appearing in
> the table were QSO's marked confirmed. The table contains all
> "F's" and no "W's". All the DXCC prefixes for worked but not
> confirmed countries look correct. As a test, I entered a new
> country in the capture window and logged it. Indeed,
> that contact
> now shows up as the only "W" in the progress table. Doing a
> recompute doesn't change things. I have no idea
> what's going on
> but maybe that's clue for you. If you like I can zip
> up a copy of
> my mdb file and mail it to you.
>
> ----
> 73, Rich - W3ZJ
>
>
> Yahoo! Groups Sponsor
>
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo!
> Terms of Service.
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
>
>
>
>


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
Re: DXKeeper 1.1.6 is available

 

Dave,

The import went fine, except for the program error that occurs at
QSO #3757. I found that all I have to do to recover from that is
to close and reopen DXKeeper, then start the import again. The
first 3757 are then duplicates and after passing those it
completes normally. Performance is much improved. I'll send you
the entire ADIF file (privately) so you can see that too.

---
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Saturday, March 24, 2001 12:33 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


That's a pretty good clue, Rich -- it implies that the
import operation is
not properly handling worked-but-not-confirmed QSOs.
I've imported my 13K
QSOs (from the first-generation DXLab, which began life
as an alternative
user interface for log files created by LOGic) and the
worked/confirmed/verified numbers match exactly, but
perhaps your logging
program does things a bit differently, ADIF not withstanding.

Could you send me the ADIF file you're importing, or at
least a fragment
containing several worked-but-not-confirmed QSOs?

Was the import operation reliable? How was import performance?

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 12:17 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Dave,

I am still having a problem with the Progress Table
not showing
correct results for imported log entries. I did a little more
research and found that the only entries that were
appearing in
the table were QSO's marked confirmed. The table contains all
"F's" and no "W's". All the DXCC prefixes for worked but not
confirmed countries look correct. As a test, I entered a new
country in the capture window and logged it. Indeed,
that contact
now shows up as the only "W" in the progress table. Doing a
recompute doesn't change things. I have no idea
what's going on
but maybe that's clue for you. If you like I can zip
up a copy of
my mdb file and mail it to you.

----
73, Rich - W3ZJ


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service.






------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
Re: DXKeeper 1.1.6 is available

Dave, AA6YQ
 

That's a pretty good clue, Rich -- it implies that the import operation is
not properly handling worked-but-not-confirmed QSOs. I've imported my 13K
QSOs (from the first-generation DXLab, which began life as an alternative
user interface for log files created by LOGic) and the
worked/confirmed/verified numbers match exactly, but perhaps your logging
program does things a bit differently, ADIF not withstanding.

Could you send me the ADIF file you're importing, or at least a fragment
containing several worked-but-not-confirmed QSOs?

Was the import operation reliable? How was import performance?

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 12:17 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Dave,

I am still having a problem with the Progress Table not showing
correct results for imported log entries. I did a little more
research and found that the only entries that were appearing in
the table were QSO's marked confirmed. The table contains all
"F's" and no "W's". All the DXCC prefixes for worked but not
confirmed countries look correct. As a test, I entered a new
country in the capture window and logged it. Indeed, that contact
now shows up as the only "W" in the progress table. Doing a
recompute doesn't change things. I have no idea what's going on
but maybe that's clue for you. If you like I can zip up a copy of
my mdb file and mail it to you.

----
73, Rich - W3ZJ


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
228441 - 228460 of 228494