Re: [Dx4win] IOTAs and DX4WIN

2020-12-15 Thread Alan Zack
Yes, I make submissions on line from IOTA Contest logs, LoTW and ClubLog 
confirmations. Also thru my IOTA card checker when I only have a card, no 
electronic submission.

But, how do the DX4WIN flags get populated? What changes them from -- to S or 
C? How does DX4WIN know I made a submission?

I keep separate IOTA listings from the IOTA website. I haven't figured out how 
to have DX4WIN track when I have a confirmation.  To me it would be very 
difficult to have DX4WIN track IOTA confirmations. IOTA only needs ONE, only 
ONE confirmation. Any band, any mode. You could work the same IOTA over and 
over on many bands and modes but only the first confirmation is counted. Any 
after that are ignored. Not like DXCC where you get credit for different bands, 
modes, etc. For example, I started tracking my IOTA's in 1990. I worked T32HK 
in 1990 for OC-024. I have logged many stations on OC-024 on many bands and 
modes, 117 in total, but only the very first in 1990 counts.

Alan Zack
Amateur Radio Station K7ACZ

-Original Message-
From: dx4win-boun...@mailman.qth.net On Behalf Of Kostas SV1DPI
Sent: Tuesday, December 15, 2020 10:19 PM
To: dx4win@mailman.qth.net
Subject: Re: [Dx4win] IOTAs and DX4WIN

Hello Alan

that boxes are filled when you make an application in RSGB,  When you submit, S 
(submitted) is filled and when you have the QSOs checked you must change it to 
C (checked). DXCC flags work the same way. If you made a submission and you did 
not send the cards to the checker, you can clear them (reports>clear award 
flags)

73 Kostas SV1DPI

Στις 16/12/2020 06:43, ο/η Alan Zack έγραψε:
> Hi Jim,
>
> Thanks for your interest in logging the IOTA's. I got big into IOTA 
> once I got 5BDXCC and needed a new challenge. Plus I have actually 
> been to many of the IOTA's. If there was a LORAN station on an IOTA, 
> USA manned or foreign manned, I have probably been there on USCG C-130 
> flights.
> One thing I don't understand with IOTA and DX4WIN. In the AWARDS area 
> (lower section of full main window) how does the IOTA awards box 
> become populated? Is that something you do manually? But I notice form 
> time to time I will see a C or S in that box. I wonder how it got 
> there? Is it from when I do a LoTW upload and one of my confirmations 
> is an IOTA? I do use REPORTS> IOTA to track my IOTA's (worked, QSL 
> mailed, confirmed). Is that where the awards box gets its inputs?
>
> Alan Zack
> Amateur Radio Station K7ACZ
>
> -Original Message-
> From: dx4win-boun...@mailman.qth.net On Behalf Of Jim Reisert AD1C
> Sent: Saturday, December 12, 2020 03:42 PM
> To: DX4WIN Reflector 
> Subject: [Dx4win] IOTAs and DX4WIN
>
> Hi Folks,
>
> There may be confusion as to how IOTAs (Islands on the Air) work in 
> DX4WIN, how they get updated, etc.  I would like to try to explain how 
> this works.  I started to write an application note for IOTA, but 
> never really finished it, nor did I make it visible on the web site (I 
> guess I'll do that).
>
>  http://dx4win.ad1c.us/appnotes/iota.html
>
> I'll just hit some of the high points below.
>
>
> The IOTA field in your logbook works like the State and Grid fields -- 
> it is stored with the QSO record, and does NOT change when a new 
> country file is released.
>
> When logging a QSO, DX4WIN may automatically fill in the IOTA field if 
> it can uniquely determine the IOTA from the callsign and date, based 
> on information contained in the country file.  Some DXCC entities like 
> Barbados, 8P have a single IOTA (NA-021).  Some IOTA are determined by 
> prefix, for example, IG9 is AF-019 and IH9 is AF-018.  And there are 
> thousands of callsigns in the country file that are mapped to a 
> particular IOTA, for example CE7KF is IOTA SA-018.  DX4WIN will also 
> attempt to assign IOTA when importing QSOs.
>
>   In DX4WIN 9.01 and later, there is a Multiple QSOs operation for 
> checking the IOTA fields in your log:
>
>  QSO | Multiple QSOs operations | Check IOTAs.
>
> This does the following four things:
>
> 1.  If the IOTA field is empty, and the IOTA can be determined from 
> both the callsign and date (i.e. via the country file), then an IOTA 
> is assigned to that QSO.
>
> 2.  If the IOTA field is not empty, is the IOTA correct based on the 
> callsign and date, given the information in the country file?  In 
> other words, if the IOTA field was blank, would DX4WIN have filled it 
> in with the same IOTA as you chose?  If they do not match, DX4WIN will 
> do the following two things:
>
>  a.  Put the "correct" IOTA into the IOTA field in the logbook.
>
>  b.  Add some information to the "Notes for this QSO field":
> "IOTAMSG: Bad IOTA=OC130"
>  In this case, OC130 was what your log had *before* running 
> Check IOTAs.
>
> I wrote "correct" because the country file can (and probably does) 
> have errors.  If you think that DX4WIN made an incorrect substitution, 
> and you have the QSO confirmed, please send me the information 

Re: [Dx4win] IOTA OC-298 -- Tatakoto Atoll

2020-12-15 Thread Alan Zack
Jim,

I have FO/DL5XU on 4 and 6 FEB 2001 OC-066 Rangiroa confirmed
I have FO/F6CTL on 8 JUL 2001 OC-066 Rangiroa confirmed
I have FO5RH 2012 IOTA Contest (JULY 2012) OC-066 Raroia confirmed
I have FO5RH 2013 IOTA Contest (JULY 2013) logged as OC-066 but with
the notation IOTAMSG: Bad Island=6050 What should it be?

I only show TX0T for OC-298, no others. Maybe FO5RH in 2013 S/B
OC-066/OC-298?

New IOTA Subject: Has anyone ever received a QSL for FO0DEH, OC-057 in
Oct 2000?. Op was ON4QM, now a SK. That was my one and only QSO with
OC-057

Merry Christmas

Alan Zack
Amateur Radio Station K7ACZ

-Original Message-
From: dx4win-boun...@mailman.qth.net On Behalf Of Jim Reisert AD1C
Sent: Wednesday, December 9, 2020 11:06 AM
To: DX4WIN Reflector 
Subject: [Dx4win] IOTA OC-298 -- Tatakoto Atoll

If you are not an IOTA chaser, you can skip reading this...

Recently Cezar VE3LYC operated from Tatakoto as TX0T which was then
qualified as IOTA OC-298.  There were several past operations from
this atoll.  These will now also count as IOTA OC-298 instead of IOTA
OC-066.
If you have received credit for IOTA OC-066 for one of these past
operations, you will lose that credit.  You will need to find another
QSO with IOTA OC-066 to submit for IOTA credit.

With the help of DX spots and DL6KVA, I have identified the following
past operations from Tatakoto Atoll.  The information on the IOTA
World web site does not include dates but does include callsigns:


https://www.iota-world.org/islands-on-the-air/iota-groups-islands/grou
p/1175.html

The next country file will have the following callsigns associated
with the new IOTA (they are listed chronologically):

FO0CLA   2000-04-20,2000-05-23
FO0CLA   2000-06-27,2000-08-01
FO5RH2004-07-20,2004-07-21
FO5RH2005-09-18,2005-09-27
FO5RH2008-05-14,
TX5TES   2010-07-11,2010-07-25
FO8AA/P  2015-03-01,2015-04-07
TX0T 2020-10-30,2020-11-05

Note that FO0CLA (who later became FO5RH) operated from many other
islands in French Polynesia starting in mid-1999, so the start and end
dates are important.  I have done my best to determine the correct
dates.  There may have been other operations from Tatakoto, other than
the dates given above.  If you have a QSL from such an operation,
please let me know and I will make the necessary changes to the
country file.

When the next country file is released later this week, you can use
Multiple QSO Operations | Check IOTA to determine which QSOs you may
need to change.

73 - Jim AD1C

--
Jim Reisert AD1C, , https://www.ad1c.us

__

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html


Re: [Dx4win] IOTAs and DX4WIN

2020-12-15 Thread Kostas SV1DPI

Hello Alan

that boxes are filled when you make an application in RSGB,  When you 
submit, S (submitted) is filled and when you have the QSOs checked you 
must change it to C (checked). DXCC flags work the same way. If you made 
a submission and you did not send the cards to the checker, you can 
clear them (reports>clear award flags)


73 Kostas SV1DPI

Στις 16/12/2020 06:43, ο/η Alan Zack έγραψε:

Hi Jim,

Thanks for your interest in logging the IOTA's. I got big into IOTA
once I got 5BDXCC and needed a new challenge. Plus I have actually
been to many of the IOTA's. If there was a LORAN station on an IOTA,
USA manned or foreign manned, I have probably been there on USCG C-130
flights.
One thing I don't understand with IOTA and DX4WIN. In the AWARDS area
(lower section of full main window) how does the IOTA awards box
become populated? Is that something you do manually? But I notice form
time to time I will see a C or S in that box. I wonder how it got
there? Is it from when I do a LoTW upload and one of my confirmations
is an IOTA? I do use REPORTS> IOTA to track my IOTA's (worked, QSL
mailed, confirmed). Is that where the awards box gets its inputs?

Alan Zack
Amateur Radio Station K7ACZ

-Original Message-
From: dx4win-boun...@mailman.qth.net On Behalf Of Jim Reisert AD1C
Sent: Saturday, December 12, 2020 03:42 PM
To: DX4WIN Reflector 
Subject: [Dx4win] IOTAs and DX4WIN

Hi Folks,

There may be confusion as to how IOTAs (Islands on the Air) work in
DX4WIN, how they get updated, etc.  I would like to try to explain how
this works.  I started to write an application note for IOTA, but
never really finished it, nor did I make it visible on the web site (I
guess I'll do that).

 http://dx4win.ad1c.us/appnotes/iota.html

I'll just hit some of the high points below.


The IOTA field in your logbook works like the State and Grid fields --
it is stored with the QSO record, and does NOT change when a new
country file is released.

When logging a QSO, DX4WIN may automatically fill in the IOTA field if
it can uniquely determine the IOTA from the callsign and date, based
on information contained in the country file.  Some DXCC entities like
Barbados, 8P have a single IOTA (NA-021).  Some IOTA are determined by
prefix, for example, IG9 is AF-019 and IH9 is AF-018.  And there are
thousands of callsigns in the country file that are mapped to a
particular IOTA, for example CE7KF is IOTA SA-018.  DX4WIN will also
attempt to assign IOTA when importing QSOs.

  In DX4WIN 9.01 and later, there is a Multiple QSOs operation for
checking the IOTA fields in your log:

 QSO | Multiple QSOs operations | Check IOTAs.

This does the following four things:

1.  If the IOTA field is empty, and the IOTA can be determined from
both the callsign and date (i.e. via the country file), then an IOTA
is assigned to that QSO.

2.  If the IOTA field is not empty, is the IOTA correct based on the
callsign and date, given the information in the country file?  In
other words, if the IOTA field was blank, would DX4WIN have filled it
in with the same IOTA as you chose?  If they do not match, DX4WIN will
do the following two things:

 a.  Put the "correct" IOTA into the IOTA field in the logbook.

 b.  Add some information to the "Notes for this QSO field":
"IOTAMSG: Bad IOTA=OC130"
 In this case, OC130 was what your log had *before* running
Check IOTAs.

I wrote "correct" because the country file can (and probably does)
have errors.  If you think that DX4WIN made an incorrect substitution,
and you have the QSO confirmed, please send me the information from
the QSL card (IOTA and Island Name) as well as the callsign and date,
and I'll look into it.

3.  If the IOTA Island field is empty, DX4WIN will populate that field
in the logbook if the IOTA group has only one island.  Some examples
of this are Barbados, 8P (IOTA NA021) and Luzon Island, DU4 (IOTA
OC042).

4.  If the IOTA Island field is not empty, check that it is a valid
island for the given IOTA group.  If the island if not valid, you will
get an error message like this:

 IOTAMSG: Bad Island=6312

The number above refers to the numerical code provided by the IOTA
committee to represent the island name in the IOTA group.  It is
unusual for this to happen, but not unheard of.  I had a number of
such errors in my logbook from QSOs which had the wrong prefix/country
assigned to them at one point in time, but subsequently changed based
on new information in the country file.

There is also a Multiple QSOs Operation to remove all the IOTA error
messages from your log, once you have resolved all the problems.

So in summary:

1.  DX4WIN assigns the IOTA field automatically if it can do so.
2.  Subsequent releases of the country file will not change the IOTA
field in any QSO.
3.  There is a Multiple QSOs Operation to check the IOTA fields in
your log.

Please reply to me directly or the reflector if there are any
questions about this.

73 - Jim AD1C

--

Re: [Dx4win] IOTAs and DX4WIN

2020-12-15 Thread Alan Zack
Hi Jim,

Thanks for your interest in logging the IOTA's. I got big into IOTA
once I got 5BDXCC and needed a new challenge. Plus I have actually
been to many of the IOTA's. If there was a LORAN station on an IOTA,
USA manned or foreign manned, I have probably been there on USCG C-130
flights.
One thing I don't understand with IOTA and DX4WIN. In the AWARDS area
(lower section of full main window) how does the IOTA awards box
become populated? Is that something you do manually? But I notice form
time to time I will see a C or S in that box. I wonder how it got
there? Is it from when I do a LoTW upload and one of my confirmations
is an IOTA? I do use REPORTS> IOTA to track my IOTA's (worked, QSL
mailed, confirmed). Is that where the awards box gets its inputs?

Alan Zack
Amateur Radio Station K7ACZ

-Original Message-
From: dx4win-boun...@mailman.qth.net On Behalf Of Jim Reisert AD1C
Sent: Saturday, December 12, 2020 03:42 PM
To: DX4WIN Reflector 
Subject: [Dx4win] IOTAs and DX4WIN

Hi Folks,

There may be confusion as to how IOTAs (Islands on the Air) work in
DX4WIN, how they get updated, etc.  I would like to try to explain how
this works.  I started to write an application note for IOTA, but
never really finished it, nor did I make it visible on the web site (I
guess I'll do that).

http://dx4win.ad1c.us/appnotes/iota.html

I'll just hit some of the high points below.


The IOTA field in your logbook works like the State and Grid fields --
it is stored with the QSO record, and does NOT change when a new
country file is released.

When logging a QSO, DX4WIN may automatically fill in the IOTA field if
it can uniquely determine the IOTA from the callsign and date, based
on information contained in the country file.  Some DXCC entities like
Barbados, 8P have a single IOTA (NA-021).  Some IOTA are determined by
prefix, for example, IG9 is AF-019 and IH9 is AF-018.  And there are
thousands of callsigns in the country file that are mapped to a
particular IOTA, for example CE7KF is IOTA SA-018.  DX4WIN will also
attempt to assign IOTA when importing QSOs.

 In DX4WIN 9.01 and later, there is a Multiple QSOs operation for
checking the IOTA fields in your log:

QSO | Multiple QSOs operations | Check IOTAs.

This does the following four things:

1.  If the IOTA field is empty, and the IOTA can be determined from
both the callsign and date (i.e. via the country file), then an IOTA
is assigned to that QSO.

2.  If the IOTA field is not empty, is the IOTA correct based on the
callsign and date, given the information in the country file?  In
other words, if the IOTA field was blank, would DX4WIN have filled it
in with the same IOTA as you chose?  If they do not match, DX4WIN will
do the following two things:

a.  Put the "correct" IOTA into the IOTA field in the logbook.

b.  Add some information to the "Notes for this QSO field":
"IOTAMSG: Bad IOTA=OC130"
In this case, OC130 was what your log had *before* running
Check IOTAs.

I wrote "correct" because the country file can (and probably does)
have errors.  If you think that DX4WIN made an incorrect substitution,
and you have the QSO confirmed, please send me the information from
the QSL card (IOTA and Island Name) as well as the callsign and date,
and I'll look into it.

3.  If the IOTA Island field is empty, DX4WIN will populate that field
in the logbook if the IOTA group has only one island.  Some examples
of this are Barbados, 8P (IOTA NA021) and Luzon Island, DU4 (IOTA
OC042).

4.  If the IOTA Island field is not empty, check that it is a valid
island for the given IOTA group.  If the island if not valid, you will
get an error message like this:

IOTAMSG: Bad Island=6312

The number above refers to the numerical code provided by the IOTA
committee to represent the island name in the IOTA group.  It is
unusual for this to happen, but not unheard of.  I had a number of
such errors in my logbook from QSOs which had the wrong prefix/country
assigned to them at one point in time, but subsequently changed based
on new information in the country file.

There is also a Multiple QSOs Operation to remove all the IOTA error
messages from your log, once you have resolved all the problems.

So in summary:

1.  DX4WIN assigns the IOTA field automatically if it can do so.
2.  Subsequent releases of the country file will not change the IOTA
field in any QSO.
3.  There is a Multiple QSOs Operation to check the IOTA fields in
your log.

Please reply to me directly or the reflector if there are any
questions about this.

73 - Jim AD1C

--
Jim Reisert AD1C, , https://www.ad1c.us 

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html


Re: [Dx4win] Merging/changing groups

2020-12-15 Thread Alan Zack
In my DX4WIN scheme I have two logs:
1. Stateside K6ACZ/K7ACZ
2. Portable DU. (all my ops from the Philippines)

I do this because you cannot combine your DX and home ops for the
various awards. If they were all in one log it would be hard to track
what country/zone/IOTA, etc you need for an award. I have 5BDXC for
the stateside call but only DXCC for /DU.

In the two separate logs I use a different GROUP number for each
contest.

More simple than your situation but there maybe some out there that
are unaware that you can actually have two separate logs in one
program under separate call.dxl.files.

Alan Zack
Amateur Radio Station K7ACZ

-Original Message-
From: dx4win-boun...@mailman.qth.net On Behalf Of Eric Rosenberg
Sent: Monday, December 14, 2020 01:53 PM
To: dx4win@mailman.qth.net
Subject: [Dx4win] Merging/changing groups

Over the years, I've operated from many QTH's and with a variety of
callsigns, both US and DX.

As a result, I have over 150 Groups in DX4Win for my US callsigns, all
based on activities, specifically contests.

I'd like to consolidate the US QSOs to create two levels of groups,
the top level one with callsign and QTH, the next level with activity
(in this case, contest name).

Can I do this? If so, how?

73,
Eric W3DQ
__

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html


[Dx4win] CW Window Help

2020-12-15 Thread George Rickley
Have just done V9 upgrade and everything seems OK, except I can't edit the
CW window messages. When I right click on the body I do not get the 'pop up
menu' at all. Anyone else encounter this or have a suggestion?
Thanks, George K1MA
__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html


Re: [Dx4win] Merging/changing groups

2020-12-15 Thread Jim Reisert AD1C
On Mon, Dec 14, 2020 at 2:55 PM Eric Rosenberg W3DQ wrote:

> Over the years, I've operated from many QTH's and with a variety of
> callsigns, both US and DX.
>
> As a result, I have over 150 Groups in DX4Win for my US callsigns, all
> based on activities, specifically contests.
>
> I'd like to consolidate the US QSOs to create two levels of groups, the top
> level one with callsign and QTH, the next level with activity (in this
> case, contest name).
>
> Can I do this? If so, how?

Eric, there is no automated way to do this.  But you can renumber each
existing group if you want:

Use F8 and search for the group number you want to change.  Then use
QSO | Multiple QSOs operations | Set Group number to change it.  When
you are asked if you want to use the existing filter, answer YES so
only the selected group number is changed.

-- 
Jim Reisert AD1C, , https://www.ad1c.us
__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html