Re: [Dx4win] [WriteLog] CTY-2702 Country Files - 14 February 2017
Jim and WriteLog users I am using WriteLog ver 12.11D Nov 2016. I will upgrade to ver 12.15 (or later) in time for the CQWWDX in the fall. If I understand WRITELOG things correctly before each contest I start a new contest log (example last weekend's ARRL DX SSB). Then I go to FILE>WEB UPDATE and click on WEB UPDATE COUNTRY FILES. This places a folder WL_CTY.ZIP in my C: PROGRAM DATA/WRITELOG folder. I go to this WL_CTY.ZIP file and right click and select EXTRACT ALL. This then places many DAT and BIN files into my C: PROGRAM DATA/WRITELOG folder. I go to the file WL_CTY.DAT and open it using Notepad. I do a search for VERSION and find VERSION= Mauritus 3B8. So I assume I have the correct CTY file in use. Am I correct to assume this? If so, I need to warn everyone who used WriteLog in the ARRL DX SSB last weekend that the call WP2AA comes up as United States and NOT U.S. Virgin Islands. I worked them on four bands and corrected my log from United States to KP2 U.S. Virgin Islands after each contact. After the contest I went back to the above mentioned WL_CTY.DAT file and searched for WP2AA. It shows WP2AA as a USA entry WP2AA(5)[8]. What is strange is when I enter WP2AA into my regular logger DX4WIN it shows up as KP2 U.S. Virgin Islands. But I have not updated my DX4WIN CTY file for awhile so maybe the latest DX4WIN CTY file also has WP2AA mapped incorrectly. Just wanted to throw this out there for anyone who worked WP2AA in the ARRL DX SSB 73 Alan Zack Amateur Radio Station K7ACZ -Original Message- From: WriteLog [mailto:writelog-boun...@contesting.com] On Behalf Of Jim Reisert AD1C Sent: Tuesday, February 14, 2017 7:31 AM To: write...@contesting.com Subject: [WriteLog] CTY-2702 Country Files - 14 February 2017 The Country (CTY) Files were updated on 14 February 2017: http://www.country-files.com/cty-2702-14-February-2017/ For installation instructions, start at: http://www.country-files.com/ Hover your mouse over the word Contest in the menu, then select the software you are using. To install the file, follow the link to your software at the top of the page. If you are interested in a bigger CTY.DAT for everyday logging, you can get it here: http://www.country-files.com/big-cty/ Note that the release notes (and Version Entity) for this larger file are different than what is shown below. There is a separate link to them. Here are the release notes: 14 February 2017 (CTY-2702) VER20170214, Version entity is Mauritius, 3B8 Added/changed Callsigns/prefixes: * 4X6TT/JY1 is Israel, 4X * VP8DPE is Antarctica, CE9 in ITU zone 73 * OJ1ABOA is Antarctica, CE9 in CQ zone 38, ITU zone 67 * RI1ANN is Antarctica, CE9 in CQ zone 39, ITU zone 69 * EA1RCG/CPV is Spain, EA * TO1A is French Guiana, FY * GB2MOF, GB2OL and GB5AG are all Scotland, GM * GB6BLB, GB6RNLI and GB8MG are all Wales, GW * 4U7FOC is Italy, I * AB8YZ, K9WM, KE9B, KZ9V, N3BBQ, W9RNY, WB7PVL and WN7Y are all United States, K in CQ zone 4, ITU zone 7 * KU4UK is United States, K in CQ zone 4, ITU zone 8 * AB8RL, K8FC, K8GU, KC8GCR, KD9LA, N7EO, W8HGH, W8LMG and WG8Y are all United States, K in CQ zone 5, ITU zone 8 * N0J and W3FM are both Mariana Islands, KH0 * KB7G, KE7IZS and N6AI are all Hawaii, KH6 * K5DOW, KE5NLG and W2KRZ are all Alaska, KL * K2D is US Virgin Islands, KP2 * LU9ERA/H is Argentina, LU * LU6DO/V is Argentina, LU in ITU zone 16 * R80RTL, RA9KU/1, RM94AE, RX3XX/N, UA0XAK/6 and UE28AFG are all European Russia, UA * RZ5D/4 is European Russia, UA in ITU zone 30 * R8CZ/4 is European Russia, UA in CQ zone 17, ITU zone 30 * RA/DK8DX is Asiatic Russia, UA9 in CQ zone 18, ITU zone 31 * R71RRC is Asiatic Russia, UA9 in CQ zone 19, ITU zone 25 * UR5KGG/WAP, UT1KY/WAP and UT7UA/WAP are all Ukraine, UR * CF7AAW/1 is Canada, VE * CG2NNX/P, VA2UA and VE2ENB are all Canada, VE in CQ zone 2, ITU zone 4 * VK8RR/9 and VK9AA are both Cocos (Keeling) Islands, VK9C * VK9VKL is Christmas Island, VK9X Removed Callsigns/prefixes: * 8T2BH and VU3BPZ/P in Antarctica, CE9 * EA1RCI/YOA and EA3HSD/P in Spain, EA * EA5IKT/6 in Balearic Islands, EA6 * EA3EGB/9 and EB9PH/P in Ceuta & Melilla, EA9 * ET3AA/YOTA in Ethiopia, ET * TO200SPM in St. Pierre & Miquelon, FP * GB2ZE in Scotland, GM * GB100CSW and GB75ATC in Wales, GW * IZ1CLA/N in Italy, I * II0EUDX and II3EUDX in Sardinia, IS * K1DC, KA9VVQ, KV1E, N0FCD, N1KW, N2WN, N3AIU, W9UK, WA8WZG, WB5NHL, WL7YQ and WY5I in United States, K * K2NMA and W2ONH in Mariana Islands, KH0 * KB7UQH, KJ6TJZ and KM6EPQ in Hawaii, KH6 * KC2PCV, KC7OQZ and KI4SET in Alaska, KL * KE0GFK in Puerto Rico, KP4 * LU1ALF/D,
Re: [Dx4win] Call sign letters to big
How many of you are wanting this ability? For those that do, EXACTLY how are you indicating the "long" call in the Notes field? And which Notes field (QSO or Call Notes)? I think it should be fairly simple to automate the editing of the ADIF file if the "long" name in the Notes field is consistent so a program could look for it and then change the corresponding shortcall to longcall. Going the other way (ADIF -> DX4WIN to set the LoTW Cnfm flag) would be more of a challenge but possible. If you are interested in one or both programs, let me know. If there is enough interest, I will see what I can come up with. 73, Lee N7NU >>> WA7AA 3/6/2017 1:27 PM >>> On 06-Mar-17 12:55, w...@att.net wrote: > > Specifically, the "Notes for this QSO" notes. That way you can keep > track of all the call changes separately, i.e. > > VE100VIMY/VE# > VE100VIMY/VO# > VE100VIMY/VY# > For those of us who upload to LoTW, however, you're going to have to edit the ADI file for these and any other incomplete entries (> 12 chars) in order to have a QSO match, otherwise there will likely be no QSL (I am assuming the logs will not match unless there is a full callsign match - correct me if I'm wrong, please). This is what it should look like: Any line that contains VE100VIMY has to be edited to VE100VIMY/XXX where XXX has to obviously be the suffix of the worked station, i.e. VE1, VY0, etc. Once there's a match in the LoTW, you'll then have to check the LoTW Cnfm box for the relevant QSO in the log manually. All this goes for any other callsign longer than 12 characters. Convoluted, but the only workaround for LoTW and any other electronic file upload/download, until Paul expands the Callsign entry field beyond 12 characters. With the proliferation of such calls in recent years, this seems a must. 73, Zoran WA7AA __ 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 !SIG:58bdd466192451957511090! __ 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] Call sign letters to big
That is what I do plus I add the province as well Example: VE100VIMY/VE9 NB I am curious if this group will be using LoTW and if so how are they submitting the calls they use Alan K7ACZ -Original Message- From: DX4WIN [mailto:dx4win-boun...@mailman.qth.net] On Behalf Of Jim Reisert AD1C Sent: Monday, March 6, 2017 12:42 PM To: Art - W6KY Cc: dx4win@mailman.qth.net Subject: Re: [Dx4win] Call sign letters to big On Sun, Mar 5, 2017 at 3:03 PM, Art - W6KY wrote: > Put the real callsign in the 'notes'. Specifically, the "Notes for this QSO" notes. That way you can keep track of all the call changes separately, i.e. VE100VIMY/VE# VE100VIMY/VO# VE100VIMY/VY# -- Jim Reisert AD1C, , http://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] Call sign letters to big
On 06-Mar-17 12:55, w...@att.net wrote: Specifically, the "Notes for this QSO" notes. That way you can keep track of all the call changes separately, i.e. VE100VIMY/VE# VE100VIMY/VO# VE100VIMY/VY# For those of us who upload to LoTW, however, you're going to have to edit the ADI file for these and any other incomplete entries (> 12 chars) in order to have a QSO match, otherwise there will likely be no QSL (I am assuming the logs will not match unless there is a full callsign match - correct me if I'm wrong, please). This is what it should look like: Any line that contains VE100VIMY has to be edited to VE100VIMY/XXX where XXX has to obviously be the suffix of the worked station, i.e. VE1, VY0, etc. Once there's a match in the LoTW, you'll then have to check the LoTW Cnfm box for the relevant QSO in the log manually. All this goes for any other callsign longer than 12 characters. Convoluted, but the only workaround for LoTW and any other electronic file upload/download, until Paul expands the Callsign entry field beyond 12 characters. With the proliferation of such calls in recent years, this seems a must. 73, Zoran WA7AA __ 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] Call sign letters to big
RR QSL Tnx! 73 de Bernie/WO2N.> Sent from my iPhone 6s> > On Mar 6, 2017, at 3:41 PM, Jim Reisert AD1C wrote: > >> On Sun, Mar 5, 2017 at 3:03 PM, Art - W6KY wrote: >> >> Put the real callsign in the 'notes'. > > Specifically, the "Notes for this QSO" notes. That way you can keep > track of all the call changes separately, i.e. > > VE100VIMY/VE# > VE100VIMY/VO# > VE100VIMY/VY# > > -- > Jim Reisert AD1C, , http://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] Call sign letters to big
On Sun, Mar 5, 2017 at 3:03 PM, Art - W6KY wrote: > Put the real callsign in the 'notes'. Specifically, the "Notes for this QSO" notes. That way you can keep track of all the call changes separately, i.e. VE100VIMY/VE# VE100VIMY/VO# VE100VIMY/VY# -- Jim Reisert AD1C, , http://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