Date   

Re: DXKeeper 1.1.7 is available

Richard B Drake
 

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
http://docs.yahoo.com/info/terms/



DXKeeper 1.1.7 is available

Dave, AA6YQ <dhb@...>
 

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

Richard B Drake
 

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
> > http://docs.yahoo.com/info/terms/
> >
> >
> >
>
>
> 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
> http://docs.yahoo.com/info/terms/
>
>
>


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
http://docs.yahoo.com/info/terms/



Re: DXKeeper 1.1.6 is available

Dave, AA6YQ <dhb@...>
 

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
> > http://docs.yahoo.com/info/terms/
> >
> >
> >
>
>
> 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
> http://docs.yahoo.com/info/terms/
>
>
>


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

Richard B Drake
 

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
> http://docs.yahoo.com/info/terms/
>
>
>


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
http://docs.yahoo.com/info/terms/



Re: DXKeeper 1.1.6 is available

Dave, AA6YQ <dhb@...>
 

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
> http://docs.yahoo.com/info/terms/
>
>
>


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

Richard B Drake
 

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
http://docs.yahoo.com/info/terms/



Re: DXKeeper 1.1.6 is available

Dave, AA6YQ <dhb@...>
 

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.


Re: DXKeeper 1.1.6 is available

Richard B Drake
 

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


DXKeeper 1.1.6 is available

Dave Bernstein <dhb@...>
 

DXKeeper 1.1.6 corrects a defect that prevents addition of the first
QSO to a log via the Capture Window. This release also includes
further improvements to the online help.

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

If a previous version of DXKeeper is not already installed on your
PC, you can obtain this release via
http://www.qsl.net/dxkeeper/download.htm .

73,

Dave, AA6YQ


DXKeeper 1.1.5 is available

Dave Bernstein <dhb@...>
 

Along with the DXCC database support described below, this release
also includes updated online help, which is accessible via
http://www.qsl.net/dxkeeper/Help/index.htm .

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

73,

Dave, AA6YQ


--- In dxlab@y..., "Dave Bernstein" <dhb@m...> wrote:
To ensure its ability to perform callsign lookups, DXKeeper will
from
now on include a copy of the DXCC database previously only packaged
with DXView. During startup, DXKeeper will determine whether DXView
is installed. If so, it will reference DXView's copy of this
database, ignoring its own copy -- this permits a single point of
database maintenance, e.g. when adding a new DXCC entity. If DXView
is not installed, then DXView will refer to its own copy of the
database.

Callsign lookups during import operations will directly reference a
DXCC database, either DXView's (if installed) or DXKeeper's. DXView
itself will not participate in import operations, which should
speed
things up quite a bit.

For callsign lookups during interactive operations (such as logging
a
QSO), DXKeeper will attempt the callsign lookup via DXView if its
running; in performing this lookup, DXView updates its information
display. If DXView is not running, then DXKeeper will perform the
lookup using its copy of the database.

So import operations run fast and don't depend on (or overload)
DXView, interactive operations use DXView if its running, but in no
case will DXKeeper create a QSO that's missing DXCC prefix or
country
code information.

There's more complexity here than I'd like, but most of it is
hidden
from the user. If you've installed DXView, then you can use it to
maintain your DXCC database and DXKeeper will automatically be
consistent. If you aren't using DXView, then DXKeeper has its own
DXCC database (though you lack a tool to update it, and thus have
to
download updates from DXKeeper web site).

Comments?

The above approach is implemented (in DXView 1.1.5) and appears to
work, but I'd like to test a few more cases before posting it.

73,

Dave, AA6YQ

--- In dxlab@y..., "Dave, AA6YQ" <dhb@m...> wrote:
Sounds like there's a latent defect in the DDE connection between
DXKeeper
and DXLab. I suggest you hold off until I release a version of of
DXKeeper
that performs the country code lookup without consulting DXView.
Shouldn't
take too long...

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@w...]
Sent: Wednesday, March 21, 2001 17:50 PM
To: dxlab@y...
Subject: RE: [dxlab] Re: Progress window


>
> Does this explain the large variance in confirmed countries
you
> mentioned earlier?
>

I don't know, but I am having a great deal of difficulty with
the
import. I took out all the DXCC entries in the ADIF file to
force
a lookup in DXView. It starts off going OK, pretty slow but I
can
live with that. Then it suddenly seems to lose communication
with
DXView and starts flying along without putting in a DXCC prefix.
The first time I tried it, it only put in about 10 prefixes
before
that happened. I tried again and this time it got to about 400
before it lost the connection. In any case it will not handle my
5000 entry log in one go. It gets up to QSO# 3762 and dies. I
can
handle that by doing it in two pieces but I don't know what to
do
about the loss of communication with DXView.

----
73, Rich - W3ZJ


Yahoo! Groups Sponsor

iWin.com - The Place to Win Stuff!


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



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




Re: Progress window

Dave Bernstein <dhb@...>
 

I should have a new version of DXKeeper ready tonite -- it doesn't
use DXView during imports, and thus should eliminate the performance
problem. Then we can determine whether there is an additional
progress tracking problem, or whether that was a side effect of the
DXView lookup problem.

Loss of the DDE link between DXKeeper and DXView may be nothing more
than a timeout -- I left this at the 5 second default, and have not
yet added autorecovery code to re-establish the link should it break.

Do check for the presence of error logs in your DXView and DXKeeper
folders.

73,

Dave, AA6YQ

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
OK, a bunch of stuff here.

First I have succeeded in getting the import to work with DXView.
Here is what I did:

1) Closed all applications and closed my dial up connection.

2) Disabled Norton Antivirus autoprotect, disabled task scheduler.
I'm not sure this was necessary but my object was to eliminate any
possible interference from external software interrupts.

3) Opened DXView, Opened DXKeeper.

4) Started the Import. It proceeded to import and fill in the
prefix info for the first 3762 QSO's, then halted as before.

5) Created another ADIF file containing only the remaining 1238
QSO's and started again.

It completed normally. Its interesting that after staring the
import, the DXKeeper window is on top and has the focus. Clicking
on the DXView window so that it becomes the top window with the
focus speeds up the import by a ratio of at least ten times, maybe
more.

This did not fix the summary discrepancy of countries worked. It
also did not fix the 3G0Y problem, though he now shows with the
proper CE0Y prefix, my contacts with him still do not show in the
progress window. What it looks like is that it just stops
recording info in the progress window at some point. For example,
if I search for the ZS prefix using filter DXCC it shows I have
worked a bunch of them, yet no contacts with ZS show up in the
progress window. I'm not sure how to find exactly where it stops
counting. The summary shows 96 countries (mixed band/mode), there
are actually 252.

------
73, Rich - W3ZJ


Re: Progress window

Dave Bernstein <dhb@...>
 

Yes, multiple databases are to be avoided. I started with the notion
of one DXCC database managed by DXView, with other applications
invoking DXView for callsign lookups, etc. But its unacceptable for
DXKeeper to record QSOs without DXCC prefixes and country codes just
because DXView is either not installed, or installed but not running.
And we see that relying on DXView for batch operations like "import"
significantly reduces performance. Its no problem to have DXKeeper
directly access DXView's database (rather than send a message to
DXView to perform that access on its behalf) -- that eliminates the
performance problem, and the requirement that DXView be running. But
it does require DXView to be installed, which may not be the case. So
providing a duplicate copy of the database with DXKeeper, and
arranging for DXKeeper to automatically use it if DXView isn't
installed solves the problem in a manner that's completely
transparent to the user.

I could make DXKeeper delete its DXCC database if it finds that
DXView is installed; this eliminates any user confusion as to which
database to update (e.g. adding a new DXCC entity) and saves the disk
space. Its only a problem if the user subsequently uninstalls DXView,
but this could be corrected by downloading a DXCC database from the
DXKeeper web site.

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Wow, that is a bit complex but it sounds like you have a good
handle on it. The problem of keeping two copies of a database in
sync without requiring data to be entered in two places is always
a bit tricky. I take it from this that when DXView is installed it
is the master, DXKeeper is the slave and one should never directly
update DXkeeper (assuming that there will eventually be a tool to
do it). You sure are fast at this stuff!!

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave Bernstein [mailto:dhb@m...]
Sent: Thursday, March 22, 2001 3:20 AM
To: dxlab@y...
Subject: [dxlab] Re: Progress window


To ensure its ability to perform callsign lookups,
DXKeeper will from
now on include a copy of the DXCC database previously
only packaged
with DXView. During startup, DXKeeper will determine
whether DXView
is installed. If so, it will reference DXView's copy of this
database, ignoring its own copy -- this permits a
single point of
database maintenance, e.g. when adding a new DXCC
entity. If DXView
is not installed, then DXView will refer to its own copy of the
database.

Callsign lookups during import operations will directly
reference a
DXCC database, either DXView's (if installed) or
DXKeeper's. DXView
itself will not participate in import operations, which
should speed
things up quite a bit.

For callsign lookups during interactive operations
(such as logging a
QSO), DXKeeper will attempt the callsign lookup via
DXView if its
running; in performing this lookup, DXView updates its
information
display. If DXView is not running, then DXKeeper will
perform the
lookup using its copy of the database.

So import operations run fast and don't depend on (or overload)
DXView, interactive operations use DXView if its
running, but in no
case will DXKeeper create a QSO that's missing DXCC
prefix or country
code information.

There's more complexity here than I'd like, but most of
it is hidden
from the user. If you've installed DXView, then you can
use it to
maintain your DXCC database and DXKeeper will automatically be
consistent. If you aren't using DXView, then DXKeeper
has its own
DXCC database (though you lack a tool to update it, and
thus have to
download updates from DXKeeper web site).

Comments?

The above approach is implemented (in DXView 1.1.5) and
appears to
work, but I'd like to test a few more cases before posting it.

73,

Dave, AA6YQ

--- In dxlab@y..., "Dave, AA6YQ" <dhb@m...> wrote:
Sounds like there's a latent defect in the DDE
connection between
DXKeeper
and DXLab. I suggest you hold off until I release a
version of of
DXKeeper
that performs the country code lookup without
consulting DXView.
Shouldn't
take too long...

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@w...]
Sent: Wednesday, March 21, 2001 17:50 PM
To: dxlab@y...
Subject: RE: [dxlab] Re: Progress window


>
> Does this explain the large variance in confirmed
countries you
> mentioned earlier?
>

I don't know, but I am having a great deal of
difficulty with the
import. I took out all the DXCC entries in the ADIF
file to force
a lookup in DXView. It starts off going OK, pretty
slow but I can
live with that. Then it suddenly seems to lose
communication with
DXView and starts flying along without putting in a
DXCC prefix.
The first time I tried it, it only put in about 10
prefixes before
that happened. I tried again and this time it got
to about 400
before it lost the connection. In any case it will
not handle my
5000 entry log in one go. It gets up to QSO# 3762
and dies. I can
handle that by doing it in two pieces but I don't
know what to do
about the loss of communication with DXView.

----
73, Rich - W3ZJ


Yahoo! Groups Sponsor

iWin.com - The Place to Win Stuff!


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



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



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



Re: Progress window

Richard B Drake
 

OK, a bunch of stuff here.

First I have succeeded in getting the import to work with DXView.
Here is what I did:

1) Closed all applications and closed my dial up connection.

2) Disabled Norton Antivirus autoprotect, disabled task scheduler.
I'm not sure this was necessary but my object was to eliminate any
possible interference from external software interrupts.

3) Opened DXView, Opened DXKeeper.

4) Started the Import. It proceeded to import and fill in the
prefix info for the first 3762 QSO's, then halted as before.

5) Created another ADIF file containing only the remaining 1238
QSO's and started again.

It completed normally. Its interesting that after staring the
import, the DXKeeper window is on top and has the focus. Clicking
on the DXView window so that it becomes the top window with the
focus speeds up the import by a ratio of at least ten times, maybe
more.

This did not fix the summary discrepancy of countries worked. It
also did not fix the 3G0Y problem, though he now shows with the
proper CE0Y prefix, my contacts with him still do not show in the
progress window. What it looks like is that it just stops
recording info in the progress window at some point. For example,
if I search for the ZS prefix using filter DXCC it shows I have
worked a bunch of them, yet no contacts with ZS show up in the
progress window. I'm not sure how to find exactly where it stops
counting. The summary shows 96 countries (mixed band/mode), there
are actually 252.

------
73, Rich - W3ZJ


Re: Progress window

Richard B Drake
 

Wow, that is a bit complex but it sounds like you have a good
handle on it. The problem of keeping two copies of a database in
sync without requiring data to be entered in two places is always
a bit tricky. I take it from this that when DXView is installed it
is the master, DXKeeper is the slave and one should never directly
update DXkeeper (assuming that there will eventually be a tool to
do it). You sure are fast at this stuff!!

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave Bernstein [mailto:dhb@...]
Sent: Thursday, March 22, 2001 3:20 AM
To: dxlab@...
Subject: [dxlab] Re: Progress window


To ensure its ability to perform callsign lookups,
DXKeeper will from
now on include a copy of the DXCC database previously
only packaged
with DXView. During startup, DXKeeper will determine
whether DXView
is installed. If so, it will reference DXView's copy of this
database, ignoring its own copy -- this permits a
single point of
database maintenance, e.g. when adding a new DXCC
entity. If DXView
is not installed, then DXView will refer to its own copy of the
database.

Callsign lookups during import operations will directly
reference a
DXCC database, either DXView's (if installed) or
DXKeeper's. DXView
itself will not participate in import operations, which
should speed
things up quite a bit.

For callsign lookups during interactive operations
(such as logging a
QSO), DXKeeper will attempt the callsign lookup via
DXView if its
running; in performing this lookup, DXView updates its
information
display. If DXView is not running, then DXKeeper will
perform the
lookup using its copy of the database.

So import operations run fast and don't depend on (or overload)
DXView, interactive operations use DXView if its
running, but in no
case will DXKeeper create a QSO that's missing DXCC
prefix or country
code information.

There's more complexity here than I'd like, but most of
it is hidden
from the user. If you've installed DXView, then you can
use it to
maintain your DXCC database and DXKeeper will automatically be
consistent. If you aren't using DXView, then DXKeeper
has its own
DXCC database (though you lack a tool to update it, and
thus have to
download updates from DXKeeper web site).

Comments?

The above approach is implemented (in DXView 1.1.5) and
appears to
work, but I'd like to test a few more cases before posting it.

73,

Dave, AA6YQ

--- In dxlab@y..., "Dave, AA6YQ" <dhb@m...> wrote:
Sounds like there's a latent defect in the DDE
connection between
DXKeeper
and DXLab. I suggest you hold off until I release a
version of of
DXKeeper
that performs the country code lookup without
consulting DXView.
Shouldn't
take too long...

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@w...]
Sent: Wednesday, March 21, 2001 17:50 PM
To: dxlab@y...
Subject: RE: [dxlab] Re: Progress window


>
> Does this explain the large variance in confirmed
countries you
> mentioned earlier?
>

I don't know, but I am having a great deal of
difficulty with the
import. I took out all the DXCC entries in the ADIF
file to force
a lookup in DXView. It starts off going OK, pretty
slow but I can
live with that. Then it suddenly seems to lose
communication with
DXView and starts flying along without putting in a
DXCC prefix.
The first time I tried it, it only put in about 10
prefixes before
that happened. I tried again and this time it got
to about 400
before it lost the connection. In any case it will
not handle my
5000 entry log in one go. It gets up to QSO# 3762
and dies. I can
handle that by doing it in two pieces but I don't
know what to do
about the loss of communication with DXView.

----
73, Rich - W3ZJ


Yahoo! Groups Sponsor

iWin.com - The Place to Win Stuff!


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



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
http://docs.yahoo.com/info/terms/



Re: Progress window

Dave Bernstein <dhb@...>
 

To ensure its ability to perform callsign lookups, DXKeeper will from
now on include a copy of the DXCC database previously only packaged
with DXView. During startup, DXKeeper will determine whether DXView
is installed. If so, it will reference DXView's copy of this
database, ignoring its own copy -- this permits a single point of
database maintenance, e.g. when adding a new DXCC entity. If DXView
is not installed, then DXView will refer to its own copy of the
database.

Callsign lookups during import operations will directly reference a
DXCC database, either DXView's (if installed) or DXKeeper's. DXView
itself will not participate in import operations, which should speed
things up quite a bit.

For callsign lookups during interactive operations (such as logging a
QSO), DXKeeper will attempt the callsign lookup via DXView if its
running; in performing this lookup, DXView updates its information
display. If DXView is not running, then DXKeeper will perform the
lookup using its copy of the database.

So import operations run fast and don't depend on (or overload)
DXView, interactive operations use DXView if its running, but in no
case will DXKeeper create a QSO that's missing DXCC prefix or country
code information.

There's more complexity here than I'd like, but most of it is hidden
from the user. If you've installed DXView, then you can use it to
maintain your DXCC database and DXKeeper will automatically be
consistent. If you aren't using DXView, then DXKeeper has its own
DXCC database (though you lack a tool to update it, and thus have to
download updates from DXKeeper web site).

Comments?

The above approach is implemented (in DXView 1.1.5) and appears to
work, but I'd like to test a few more cases before posting it.

73,

Dave, AA6YQ

--- In dxlab@y..., "Dave, AA6YQ" <dhb@m...> wrote:
Sounds like there's a latent defect in the DDE connection between
DXKeeper
and DXLab. I suggest you hold off until I release a version of of
DXKeeper
that performs the country code lookup without consulting DXView.
Shouldn't
take too long...

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@w...]
Sent: Wednesday, March 21, 2001 17:50 PM
To: dxlab@y...
Subject: RE: [dxlab] Re: Progress window


>
> Does this explain the large variance in confirmed countries you
> mentioned earlier?
>

I don't know, but I am having a great deal of difficulty with the
import. I took out all the DXCC entries in the ADIF file to force
a lookup in DXView. It starts off going OK, pretty slow but I can
live with that. Then it suddenly seems to lose communication with
DXView and starts flying along without putting in a DXCC prefix.
The first time I tried it, it only put in about 10 prefixes before
that happened. I tried again and this time it got to about 400
before it lost the connection. In any case it will not handle my
5000 entry log in one go. It gets up to QSO# 3762 and dies. I can
handle that by doing it in two pieces but I don't know what to do
about the loss of communication with DXView.

----
73, Rich - W3ZJ


Yahoo! Groups Sponsor

iWin.com - The Place to Win Stuff!


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



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




DXView 1.2.5 is available

Dave, AA6YQ <dhb@...>
 

The primary purpose of this release is to correct the defect in Hygain DCU
rotator support reported by Julio below. I learned from Ed at DataMatrix
(the developers of ProLog) that the "set bearing" and "move rotator"
commands must be separated by at least 150ms, which explains why clicking
the SP button once fails, but clicking it twice succeeds. Without a Hygain
rotator, my testing is limited, so Julio please let me know whether this
eliminates the problem. If anyone else is using a Hygain rotator -- with
either the Rotor EZ or standard Hygain controller -- I'd also appreciate a
works/fails report.

While I was in the code, I added direct latitude/longitude entry, and added
the mechanism required for interoperation with PropView.

This release is available by downloading
http://www.qsl.net/dxview/DXView125Update.exe - store it in your DXView
folder and execute it. You can then run the extracted DXView125.exe .

73,

Dave, AA6YQ

-----Original Message-----
From: Julio [mailto:jperalta@...]
Sent: Monday, March 12, 2001 18:09 PM
To: Bernstein, Dave
Subject: Re: DXView


Dave I hope you don't construe this as complaining, at this point my
comments are to help, as I understand you are doing some beta testing or
something of that sort.

When I have the main DXView window up and I set a rotor heading either by
adding a callsign or clicking on a country it requires 2 clicks of the mouse
on the SP or LP button to start the rotor in motion. I've even tried the
clicks as long as 10 seconds apart and it will still activate the rotor
action. One click will not start the rotor! I'm not sure if this is how you
wanted it to work, but I suspect not.

Thanks again, 73's Julio


Re: Progress window

Ron Eberson <zx@...>
 

I import more than 1000 qso's from logger with out problems


-----Oorspronkelijk bericht-----
Van: Richard B Drake [mailto:rich@...]
Verzonden: woensdag 21 maart 2001 23:50
Aan: dxlab@...
Onderwerp: RE: [dxlab] Re: Progress window



Does this explain the large variance in confirmed countries you
mentioned earlier?
I don't know, but I am having a great deal of difficulty with the
import. I took out all the DXCC entries in the ADIF file to force
a lookup in DXView. It starts off going OK, pretty slow but I can
live with that. Then it suddenly seems to lose communication with
DXView and starts flying along without putting in a DXCC prefix.
The first time I tried it, it only put in about 10 prefixes before
that happened. I tried again and this time it got to about 400
before it lost the connection. In any case it will not handle my
5000 entry log in one go. It gets up to QSO# 3762 and dies. I can
handle that by doing it in two pieces but I don't know what to do
about the loss of communication with DXView.

----
73, Rich - W3ZJ



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



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


Pathfinder Users: updated searches for the FR and LZ callbooks

Dave, AA6YQ <dhb@...>
 

Our man Kurt, OE1002419, noticed that both the FR and LZ callbook URLs had
changed, tracked down the new URLs, and sent them my way. So we have him to
thank for the updated Pathfinder searches now available. Keep in mind that
the F callbook includes FR addresses, and so provides a second source of
Reunion QSL info.

To update your search library, click Pathfinder's "Info" button, or link to
http://www.qsl.net/pathfinder/UpdateSearchLibrary.htm. The Pathfinder Web
Client ( http://www.qsl.net/pathfinder/WebClient/ ) has been updated with
the above changes; 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 http://www.qsl.net/pathfinder/ 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 http://www.qsl.net/pathfinder/WebClient/ .


Re: Progress window

Dave, AA6YQ <dhb@...>
 

Sounds like there's a latent defect in the DDE connection between DXKeeper
and DXLab. I suggest you hold off until I release a version of of DXKeeper
that performs the country code lookup without consulting DXView. Shouldn't
take too long...

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Wednesday, March 21, 2001 17:50 PM
To: dxlab@...
Subject: RE: [dxlab] Re: Progress window


>
> Does this explain the large variance in confirmed countries you
> mentioned earlier?
>

I don't know, but I am having a great deal of difficulty with the
import. I took out all the DXCC entries in the ADIF file to force
a lookup in DXView. It starts off going OK, pretty slow but I can
live with that. Then it suddenly seems to lose communication with
DXView and starts flying along without putting in a DXCC prefix.
The first time I tried it, it only put in about 10 prefixes before
that happened. I tried again and this time it got to about 400
before it lost the connection. In any case it will not handle my
5000 entry log in one go. It gets up to QSO# 3762 and dies. I can
handle that by doing it in two pieces but I don't know what to do
about the loss of communication with DXView.

----
73, Rich - W3ZJ


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.