开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. DXLab
  2. Messages
Expanded Topics Messages Polls
Date
DXKeeper 1.1.6 is available

Dave Bernstein
 

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
.

73,

Dave, AA6YQ
DXKeeper 1.1.5 is available

Dave Bernstein
 

Along with the DXCC database support described below, this release
also includes updated online help, which is accessible via
.

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
 

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
 

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
Re: Progress window

 

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

 

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
Re: Progress window

Dave Bernstein
 

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
 

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

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

Pathfinder Users: updated searches for the FR and LZ callbooks

Dave, AA6YQ
 

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
. The Pathfinder Web
Client ( ) 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 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 .
Re: Progress window

Dave, AA6YQ
 

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.
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
Re: Progress window

Dave Bernstein
 

Yes, if there's a country code present in the imported QSO, DXKeeper
respects it.

The procedure you suggest will result in each imported callsign being
checked by DXView to determine a country code.

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

73,

Dave, AA6YQ

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
I'm not sure if DXView was open when I did the import. However, it
was open when I did the recompute. I just did that again to make
sure, it didn't help. However, I just noticed something else. When
I click on 3G0Y in DXKeeper, the correct prefix, CE0Y shows up in
DXView but the QSO window in DXKeepr shows CE which isn't right.
When I do a lookup in the new capture window it correctly shows
CE0Y. Does that tell you anything?

Ah!!! That gave me a clue. What if Logger exported the wrong
prefix. I just checked that and that's what happened. So, what
that says is that recompute looks first in the log to see if there
is a prefix present and only checks DXView if there is not one
there. Is that the way you want it to work? If so, I can probably
fix it by removing all the prefixes from the import ADIF file,
removing the current DXKeeper log and doing the import again. That
should force everything to be looked up in DXView - Right?

-------
73, Rich - W3ZJ

-----Original Message-----
From: Dave Bernstein [mailto:dhb@m...]
Sent: Wednesday, March 21, 2001 13:30 PM
To: dxlab@y...
Subject: [dxlab] Re: Progress window


Without seeing your log, I can't know for sure, but my
suspicion is
that many of your DXKeeper log entries are missing DXCC country
codess -- likely because DXView was not running when
these entries
were created or imported.

At the moment, DXKeeper relies on DXView to determine
the DXCC entity
associated with a callsign. I'll be adding this capability to
DXKeeper before releasing it to beta test.

If my diagnosis is correct, you can update your log entries by
starting DXView and then recomputing progress.

Let me know how it goes...

73,

Dave


--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Dave,

When I click on a callsign in DXKeeper, obviously I
have worked
the guy, but the progress window does not always indicate any
contact with his country. Also, I have worked 3G0Y 8 times on
80,30,20,10 meter CW, and 10, 15 meter SSB. The
progress window
shows only an F in CW and 40 meters. DXView shows
that the prefix
is CE0E. So I entered that in the filter window and
clicked DXCC
it came up with another station on Easter Island that
I had worked
on 40 CW but nothing for 3G0Y. I did a recompile in
the progress
window but nothing changed. Also, when I do a DXCC Summary, it
shows 97 countries worked and 96 confirmed. Logger,
which has a
duplicate of the same log shows 252 countries worked and 52
confirmed which is correct. There are just short of
5000 entries
in my log dating back to November 1999. Most of the entries in
DXKeeper were imported from Logger.

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

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

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



Your use of Yahoo! Groups is subject to
Re: Progress window

 

I'm not sure if DXView was open when I did the import. However, it
was open when I did the recompute. I just did that again to make
sure, it didn't help. However, I just noticed something else. When
I click on 3G0Y in DXKeeper, the correct prefix, CE0Y shows up in
DXView but the QSO window in DXKeepr shows CE which isn't right.
When I do a lookup in the new capture window it correctly shows
CE0Y. Does that tell you anything?

Ah!!! That gave me a clue. What if Logger exported the wrong
prefix. I just checked that and that's what happened. So, what
that says is that recompute looks first in the log to see if there
is a prefix present and only checks DXView if there is not one
there. Is that the way you want it to work? If so, I can probably
fix it by removing all the prefixes from the import ADIF file,
removing the current DXKeeper log and doing the import again. That
should force everything to be looked up in DXView - Right?

-------
73, Rich - W3ZJ

-----Original Message-----
From: Dave Bernstein [mailto:dhb@...]
Sent: Wednesday, March 21, 2001 13:30 PM
To: dxlab@...
Subject: [dxlab] Re: Progress window


Without seeing your log, I can't know for sure, but my
suspicion is
that many of your DXKeeper log entries are missing DXCC country
codess -- likely because DXView was not running when
these entries
were created or imported.

At the moment, DXKeeper relies on DXView to determine
the DXCC entity
associated with a callsign. I'll be adding this capability to
DXKeeper before releasing it to beta test.

If my diagnosis is correct, you can update your log entries by
starting DXView and then recomputing progress.

Let me know how it goes...

73,

Dave


--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Dave,

When I click on a callsign in DXKeeper, obviously I
have worked
the guy, but the progress window does not always indicate any
contact with his country. Also, I have worked 3G0Y 8 times on
80,30,20,10 meter CW, and 10, 15 meter SSB. The
progress window
shows only an F in CW and 40 meters. DXView shows
that the prefix
is CE0E. So I entered that in the filter window and
clicked DXCC
it came up with another station on Easter Island that
I had worked
on 40 CW but nothing for 3G0Y. I did a recompile in
the progress
window but nothing changed. Also, when I do a DXCC Summary, it
shows 97 countries worked and 96 confirmed. Logger,
which has a
duplicate of the same log shows 252 countries worked and 52
confirmed which is correct. There are just short of
5000 entries
in my log dating back to November 1999. Most of the entries in
DXKeeper were imported from Logger.

-----
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: Progress window

Dave Bernstein
 

Without seeing your log, I can't know for sure, but my suspicion is
that many of your DXKeeper log entries are missing DXCC country
codess -- likely because DXView was not running when these entries
were created or imported.

At the moment, DXKeeper relies on DXView to determine the DXCC entity
associated with a callsign. I'll be adding this capability to
DXKeeper before releasing it to beta test.

If my diagnosis is correct, you can update your log entries by
starting DXView and then recomputing progress.

Let me know how it goes...

73,

Dave

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Dave,

When I click on a callsign in DXKeeper, obviously I have worked
the guy, but the progress window does not always indicate any
contact with his country. Also, I have worked 3G0Y 8 times on
80,30,20,10 meter CW, and 10, 15 meter SSB. The progress window
shows only an F in CW and 40 meters. DXView shows that the prefix
is CE0E. So I entered that in the filter window and clicked DXCC
it came up with another station on Easter Island that I had worked
on 40 CW but nothing for 3G0Y. I did a recompile in the progress
window but nothing changed. Also, when I do a DXCC Summary, it
shows 97 countries worked and 96 confirmed. Logger, which has a
duplicate of the same log shows 252 countries worked and 52
confirmed which is correct. There are just short of 5000 entries
in my log dating back to November 1999. Most of the entries in
DXKeeper were imported from Logger.

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

 

Dave,

When I click on a callsign in DXKeeper, obviously I have worked
the guy, but the progress window does not always indicate any
contact with his country. Also, I have worked 3G0Y 8 times on
80,30,20,10 meter CW, and 10, 15 meter SSB. The progress window
shows only an F in CW and 40 meters. DXView shows that the prefix
is CE0E. So I entered that in the filter window and clicked DXCC
it came up with another station on Easter Island that I had worked
on 40 CW but nothing for 3G0Y. I did a recompile in the progress
window but nothing changed. Also, when I do a DXCC Summary, it
shows 97 countries worked and 96 confirmed. Logger, which has a
duplicate of the same log shows 252 countries worked and 52
confirmed which is correct. There are just short of 5000 entries
in my log dating back to November 1999. Most of the entries in
DXKeeper were imported from Logger.

-----
73, Rich - W3ZJ
www.w3zj.com
CI-V Commander version 2.5.2 is available

Dave Bernstein
 

I've added additional error trapping to this version -- hopefully the
runtime error 6 crash W3ZJ's been experiencing will be replaced by an
entry in the error log that helps me track down the root cause. Its
quite possible that this error trapping will enable the program to
recover gracefully, so keep an eye out for an errorlog.txt file in
your CI-V Commander folder.

CI-V Commander version 2.5.2 is available by downloading
and saving
it into your CI-V Commander folder. You can then directly execute it.

73,

Dave, AA6YQ

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Dave,

I have been trying the new capture window and like it very much.
This morning, I got the run time error from CI-V commander without
WinWarbler running. What I had open was CI-V commander, DXKeeper
(with the new capture window) and DXview. One small change of
frequency from the radio dial and up came the error. It's not
consistent though, I can't reproduce it at will.

-----
73, Rich - W3ZJ
www.w3zj.com
Re: DXKeeper new capture window.

Dave Bernstein
 

Rich found the documentation on their web site. Given that its a DDE
interface, I'll need a copy of their software for testing. It'd be
best to get the software directly from the supplier -- as a customer,
perhaps you could ask them on my behalf.

73,

Dave, AA6YQ

--- In dxlab@y..., "Ron Eberson" <zx@c...> wrote:
it's use the paralel port as the printer.
I can send you the program


-----Oorspronkelijk bericht-----
Van: Dave Bernstein [mailto:dhb@m...]
Verzonden: dinsdag 20 maart 2001 22:12
Aan: dxlab@y...
Onderwerp: [dxlab] Re: DXKeeper new capture window.


If there's documentation for the RS232 command set, then yes its
possible. I checked the web site but didn't see this documentation.
If you have it, please forward me a copy.

73,

Dave, AA6YQ

--- In dxlab@y..., "Ron Eberson" <zx@c...> wrote:
Yep thats good

Is't posible to use the modem and software for EA4TX rotor
control?

see ,ea4tx.com

this is not a comurcial bud i run this and like it.

Ron
PA1ZX

-----Oorspronkelijk bericht-----
Van: Richard B Drake [mailto:rich@w...]
Verzonden: dinsdag 20 maart 2001 18:46
Aan: dxlab@y...
Onderwerp: [dxlab] DXKeeper new capture window.


Dave,

I have been trying the new capture window and like it very much.
This morning, I got the run time error from CI-V commander without
WinWarbler running. What I had open was CI-V commander, DXKeeper
(with the new capture window) and DXview. One small change of
frequency from the radio dial and up came the error. It's not
consistent though, I can't reproduce it at will.

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



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



Your use of Yahoo! Groups is subject to




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



Your use of Yahoo! Groups is subject to

Re: ARS rotor control

Ron Eberson
 

Correct

And his suport are great.

-----Oorspronkelijk bericht-----
Van: Richard B Drake [mailto:rich@...]
Verzonden: dinsdag 20 maart 2001 23:54
Aan: Dxlab
Onderwerp: [dxlab] ARS rotor control


Dave,

Take a look at the following link
which is some developers
information on the rotor control that Ron asked about. From what I
can gather it is not an RS232 interface but works with some plug
in boards and drivers that you can access through DDE or Windows
messaging. It looks like they would be happy to answer questions
or help with the interface if you want to get involved with that.
My guess is that the more software that supports them the happier
they are.

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



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



Your use of Yahoo! Groups is subject to

ARS rotor control

 

Dave,

Take a look at the following link
which is some developers
information on the rotor control that Ron asked about. From what I
can gather it is not an RS232 interface but works with some plug
in boards and drivers that you can access through DDE or Windows
messaging. It looks like they would be happy to answer questions
or help with the interface if you want to get involved with that.
My guess is that the more software that supports them the happier
they are.

-----
73, Rich - W3ZJ
www.w3zj.com
228481 - 228500 of 228513