My strange tale starts with finally getting around to upgrading to
V8. In preparation I decided to run various reports of my existing V7
log so as to establish a baseline for comparison once the upgrade was
complete. I noticed something wrong with my various totals. Upon
inspecting the log
I'm posting this for another DX4WIN user who is not on the reflector.
He posed the following question: How to set up DX spots to call out
only band/mode countries never worked before and ignore band mode
countries that have not been confirmed. (He only pursues working DX
and doesn't bother
Jim,
Please eliminate potential for confusion and follow the DXCC
spelling. Hawaii should be Hawaii.
Thanks, Tony N2SS
Hi Jim,
Just read of your plan to add those provisional IOTA numbers - great
idea. I want to express my thanks and appreciation for all the effort
you put into the databases you maintain and all the support you
provide to the DX4WIN user community. Look forward to seeing you in
Dayton next
RigExpert Interface. I would like to get information on this one with
DX4WIN. Haven't tried RTTY but radio control is fine and it works great on
PSK31. Problem is when I use it for Comport CW keying through DX4WIN, if I
start or stop the radio my fully updated WINXP PC crashes.
As far as the
I am using DX4WIN version 7.01 in conjunction with a RigExpert interface
box. I can get to the point of rig control and CW keying and sending, but
if I click on Radio Stop or Radio Start my WinXP PC crashes and the
Blue Screen indicates the file ks.sys as the culprit. I have tried various
Anyone successfully using the RigExpert interface box with DX4WIN? Thanks,
Tony N2SS
Posted this question previously with no response, so I thought I would try
it one more time: Anyone using the RigExpert Plus with DX4WIN? If so, any
issues with interfacing or station/radio control? Thanks, Tony N2SS
I spent a number of years on the DX Advisory Committee and this issue was
raised several times. The prevailing feeling at HQ at the time was that
they didn't want to open it up to include pre-1975 due to the anticipated
increased workload that it would entail. That was back in the day prior to
Pete, I would agree that a new mode should take precedence over a new band.
However, this is not the situation that I have described. In what I have
described an unconfirmed mode (not a new mode) is taking precedence over a
new band. Perhaps, it is a matter of personal choice and Paul made a
.
Tony N2SS
At 03:27 PM 9/2/2003, Jim Reisert AD1C wrote:
--- Anthony R Gargano N2SS [EMAIL PROTECTED] wrote:
Pete, I would agree that a new mode should take precedence over a new
band.
However, this is not the situation that I have described. In what I have
described an unconfirmed mode
Yann, there seems to be a Priority problem in the current version of the
program. Based on the Priority definitions, my expectation is that an all
time new band which is Priority 3 (Red Bolded) would take precedence over
an unconfirmed mode which is Priority 4 (Blue).
However, I have now noted
. Similar situation appears if
there is a comment to address a different mode (i.e. ask him for SSB).
Please, check QSX and comments.
73, Thomas
Anthony R Gargano N2SS [EMAIL PROTECTED] schrieb am 01.09.03 15:08:41:
Yann, there seems to be a Priority problem in the current version
13 matches
Mail list logo
