[Dx4win] DX4Win and LOTW
Has anyone successfully reconciled their DX4Win logs with LOTW? I've tried many times using AD1Cs program and it always ends in frustration. I guess I've killed off too many brain cells over the years to understand the process. 73, Roger __ 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] DX4WIN to LOTW
Thanks Jim, After doing a more detailed search I discovered about half the errors were due to a bad frequency in the Freq (khz) box and the other half were bad calls. The bad calls were actually years of Armed Forces Day calls such as WAR, AIR, NNVR, NMC, NBM, etc, etc. I log them the same as regular calls but they don't match the normal callsign format so LOTW rejects them. No problem there as I would guess the Armed Forces Day special stations don't use LOTW so I will just ignore those errors. The bad frequency errors came from a 2004 IOTA contest log when I used the free ED5DI IOTA Contest logger program. I forgot if I used the ED5DI ADIF or Cabrillo file to upload to DX4WIN (this was before your great ADIF to DXQ program). What it did was to cut off the actual frequency. Example, instead of 14250.0 it downloaded the freq as 14.250 and then after the import in the DX4WIN Freq (khz) window it became 0.01425 and so the error. Since they were all in one group I just scanned through each QSO and wiped out the Freq (khz) box and left it blank. I then resubmitted those corrected only QSO's to LOTW and this time they were accepted using just the BAND info. Every day you learn something new! I have now submitted 26,254 LOTW QSO's for K7ACZ with 12,394 QSL matches. I know many DX stations don't use LOTW so I won't have a match. But what if I messed up the time or freq and that is why there is no match? Is there an easy way to determine if the DX did use LOTW but my QSO does not match his info? I will continue further with your Compare DX4WIN DXCC Credit Status with LoTW program but it does not appear to be able to help me with mis-matched contacts. I have another 40K or so from K6ACZ in Calif before 2003 but I know I need another certificate for a different call. I won't worry about those older QSO's before 2003. Thanks for all the help! 73, Alan, K7ACZ -Original Message- From: jjreis...@gmail.com [mailto:jjreis...@gmail.com] On Behalf Of Jim Reisert AD1C Sent: Thursday, May 15, 2014 3:15 PM To: k7...@cox.net Cc: DX4WIN Group Subject: Re: DX4WIN to LOTW Alan, I think that's the best you can do. The program for signing/uploading logs does compare the BAND against the FREQUENCY if both fields are present in the ADIF file, and reports errors if they don't match, as you saw. In your case, you'll have to assume BAND field is correct. Are these from QSOs you logged in real time, or ones you imported? If the QSOs were imported, and you have the original source, we can try to find out how to fix them. Also note that if you export your log to ADIF or DX4WIN8 format, then import the resulting file into a new DX4WIN log, it will also help identify these kinds of problems. 73 - Jim AD1C On Thu, May 15, 2014 at 3:10 PM, ALAN ZACK k7acz wrote: I recently made a submission to LOTW using the instruction by Jim AD1C: WORKING WITH LOTW and DX4WIN I got many error messages tagged as ERROR: FREQUENCY 0.01431 (and other such freq notations) IS OUT OF RANGE FOR BAND 20M ON LINE xxx When I look up the QSO record on DX4WIN I see in the Freq (khz) box that I had entered 14.31. I suppose I meant to enter 14.310.0 but for whatever reason it shows 14.31. Others show 14.01 instead of 14.010.0, 14.19 instead of 14.190.0, etc. When the QSO record is converted to the ADIF file for the LOTW TQSL conversion it is changed to the 0.01431 notation. I printed out the list of errors and it appears I have about 100 of these error messages. It seems LOTW rejected the QSO's with these errors as when I am in the LOTW webpage YOUR LOGBOOK QSO's and search for these calls with error messages they do not show up even though on the page Here you can query Logbook to find out the last time log data was uploaded for a particular call sign the station in question did upload his QSO's to LOTW in the timeframe to be a match for me. So it appears I must go into DX4WIN, search for the calls showing this error message, correct or blank out the Freq (khz) box, and resubmit a corrected file to LOTW. Is this correct? If so, is there an easier way of doing this other than doing 100 or so individual callsign searches for the offending entries? What is interesting is that with many of my QSO entries I had left the Freq (khz) block blank but LOTW seems to have accepted those QSO's. I am guessing it just accepted the entries in the BAND box as the frequency. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, 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] DX4WIN to LOTW
On Fri, May 16, 2014 at 1:44 PM, ALAN ZACK k7acz wrote: I have now submitted 26,254 LOTW QSO's for K7ACZ with 12,394 QSL matches. I know many DX stations don't use LOTW so I won't have a match. But what if I messed up the time or freq and that is why there is no match? Is there an easy way to determine if the DX did use LOTW but my QSO does not match his info? No. This protects against looking up your (busted) call in someone's log that you never worked, and trying to get confirmation for it. Time must be fairly close, I don't know how long the window is (somewhere between 1-60 minutes). Call, date, band and mode must all match. I believe TQSL converts FREQ (only) to FREQ + BAND. 73 - Jim AD1C -- Jim Reisert AD1C, jjreis...@alum.mit.edu, 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
[Dx4win] DX4WIN to LOTW
Ref: DX4WIN ver 8.05 and LOTW TQSL ver 2.0.1 I recently made a submission to LOTW using the instruction by Jim AD1C: WORKING WITH LOTW and DX4WIN I got many error messages tagged as ERROR: FREQUENCY 0.01431 (and other such freq notations) IS OUT OF RANGE FOR BAND 20M ON LINE xxx When I look up the QSO record on DX4WIN I see in the Freq (khz) box that I had entered 14.31. I suppose I meant to enter 14.310.0 but for whatever reason it shows 14.31. Others show 14.01 instead of 14.010.0, 14.19 instead of 14.190.0, etc. When the QSO record is converted to the ADIF file for the LOTW TQSL conversion it is changed to the 0.01431 notation. I printed out the list of errors and it appears I have about 100 of these error messages. It seems LOTW rejected the QSO's with these errors as when I am in the LOTW webpage YOUR LOGBOOK QSO's and search for these calls with error messages they do not show up even though on the page Here you can query Logbook to find out the last time log data was uploaded for a particular call sign the station in question did upload his QSO's to LOTW in the timeframe to be a match for me. So it appears I must go into DX4WIN, search for the calls showing this error message, correct or blank out the Freq (khz) box, and resubmit a corrected file to LOTW. Is this correct? If so, is there an easier way of doing this other than doing 100 or so individual callsign searches for the offending entries? What is interesting is that with many of my QSO entries I had left the Freq (khz) block blank but LOTW seems to have accepted those QSO's. I am guessing it just accepted the entries in the BAND box as the frequency. Any help and or suggestions would be appreciated. Thank you, Alan, K7ACZ Alan Zack Amateur Radio Station K7ACZ Official USCG Auxiliary Comm Station Las Vegas, Nevada, USA http://www.qrz.com/db/K7ACZ __ 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] DX4WIN to LOTW
Alan, I think that's the best you can do. The program for signing/uploading logs does compare the BAND against the FREQUENCY if both fields are present in the ADIF file, and reports errors if they don't match, as you saw. In your case, you'll have to assume BAND field is correct. Are these from QSOs you logged in real time, or ones you imported? If the QSOs were imported, and you have the original source, we can try to find out how to fix them. Also note that if you export your log to ADIF or DX4WIN8 format, then import the resulting file into a new DX4WIN log, it will also help identify these kinds of problems. 73 - Jim AD1C On Thu, May 15, 2014 at 3:10 PM, ALAN ZACK k7acz wrote: I recently made a submission to LOTW using the instruction by Jim AD1C: WORKING WITH LOTW and DX4WIN I got many error messages tagged as ERROR: FREQUENCY 0.01431 (and other such freq notations) IS OUT OF RANGE FOR BAND 20M ON LINE xxx When I look up the QSO record on DX4WIN I see in the Freq (khz) box that I had entered 14.31. I suppose I meant to enter 14.310.0 but for whatever reason it shows 14.31. Others show 14.01 instead of 14.010.0, 14.19 instead of 14.190.0, etc. When the QSO record is converted to the ADIF file for the LOTW TQSL conversion it is changed to the 0.01431 notation. I printed out the list of errors and it appears I have about 100 of these error messages. It seems LOTW rejected the QSO's with these errors as when I am in the LOTW webpage YOUR LOGBOOK QSO's and search for these calls with error messages they do not show up even though on the page Here you can query Logbook to find out the last time log data was uploaded for a particular call sign the station in question did upload his QSO's to LOTW in the timeframe to be a match for me. So it appears I must go into DX4WIN, search for the calls showing this error message, correct or blank out the Freq (khz) box, and resubmit a corrected file to LOTW. Is this correct? If so, is there an easier way of doing this other than doing 100 or so individual callsign searches for the offending entries? What is interesting is that with many of my QSO entries I had left the Freq (khz) block blank but LOTW seems to have accepted those QSO's. I am guessing it just accepted the entries in the BAND box as the frequency. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, 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] DX4Win and LoTW
Hi Noticed the same difference ... Nothing wrong with DX4Win... theres an overlap in the QSL report downloaded from LOTW. Apprently the QSL'ed since date is rounded off to midnight. The overlap QSO's is then reported in DX4WIN as not found / Dublicates... Example File 2) is downloaded 6 days after 1) : 1) FILE:Downloaded: 2010-05-10 08:55:12 ARRL Logbook of the World Status Report Generated at 2010-05-10 08:56:21 for oz1axg Query: QSL ONLY: YES QSL SINCE: 2010-05-05 00:00:00 PROGRAMID:4LoTW APP_LoTW_LASTQSL:192010-05-10 08:55:12 2) FILE:Downloaded: 2010-05-16 21:01:11 ARRL Logbook of the World Status Report Generated at 2010-05-16 21:02:56 for oz1axg Query: QSL ONLY: YES QSL SINCE: 2010-05-10 00:00:00 PROGRAMID:4LoTW APP_LoTW_LASTQSL:192010-05-16 21:01:11 The QSL SINCE date is rounded off to midnight in file two making all QSL Received between 2010-05-10 00:00:00 and 2010-05-10 08:56:21 present in both files thus causing a warning in Dx4Win ... -- OZ1AXG Flam - Original Message - From: Jim Reisert AD1C jjreis...@alum.mit.edu To: Andy P Hewitt andyphew...@btopenworld.com Cc: dx4...@mailman. Qth. Net dx4win@mailman.qth.net Sent: Tuesday, June 01, 2010 10:12 PM Subject: Re: [Dx4win] DX4Win and LoTW Hi Andy, What version are you running? If version 8, then ONLY the LoTW Cnfm box should be set to Y. QSL card Cnfm box is just for that only - QSL cards. There is NO overlap between the Cnfm boxes for eQSL, LoTW and paper QSL. If you use the right function to import the log (import for LoTW or import for eQSL), then the right thing should happen. Can you send me your .DXL file (before the LoTW import) and the LoTW file you are trying to import? I can try the same import here. Also tell me what version you're running. - Jim On Tue, Jun 1, 2010 at 1:04 PM, Andy P Hewitt andyphew...@btopenworld.com wrote: Hi, Could somebody please give me some guidance? Recently I uploaded my recent log to LoTW and today downloaded the LoTW report. Everything seemed to be OK until I imported the report into DX4Win. I received a window telling me that 41 QSOs had been imported but that 32 QSOs were not found and telling me to look in the save directory for File: LOTWreport 09May10.not found.. When I looked in the DX4Win save directory I found two files the one mentioned and another LOTWreport 01Jun10.not found. The May file has about 90 QSOs and the June file has 32. I had not noticed anything untoward when I imported the last report in May. I opened the two files with Notepad and checked the existence of the QSOs in my log they are all there each one has had the upload flag changed to N and where relevant the LOTW confirmed box changed to Y. There are a wide variety of qsos on different dates/bands/modes. The only other oddity is that I thought that when a QSO was confirmed by LoTW it also set the QSL Card Confirmed to Y, none of the QSOs I have checked have this happen. Can anyone tell me what has happened and what I should do about it please? -- Jim Reisert AD1C, jjreis...@alum.mit.edu, 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 No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.819 / Virus Database: 271.1.1/2910 - Release Date: 06/01/10 08:25:00 __ 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] DX4Win and LoTW
Hi, Could somebody please give me some guidance? Recently I uploaded my recent log to LoTW and today downloaded the LoTW report. Everything seemed to be OK until I imported the report into DX4Win. I received a window telling me that 41 QSOs had been imported but that 32 QSOs were not found and telling me to look in the save directory for File: LOTWreport 09May10.not found.. When I looked in the DX4Win save directory I found two files the one mentioned and another LOTWreport 01Jun10.not found. The May file has about 90 QSOs and the June file has 32. I had not noticed anything untoward when I imported the last report in May. I opened the two files with Notepad and checked the existence of the QSOs in my log they are all there each one has had the upload flag changed to N and where relevant the LOTW confirmed box changed to Y. There are a wide variety of qsos on different dates/bands/modes. The only other oddity is that I thought that when a QSO was confirmed by LoTW it also set the QSL Card Confirmed to Y, none of the QSOs I have checked have this happen. Can anyone tell me what has happened and what I should do about it please? 73 Andy G3SVD __ 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] DX4Win and LoTW
Hi Andy, What version are you running? If version 8, then ONLY the LoTW Cnfm box should be set to Y. QSL card Cnfm box is just for that only - QSL cards. There is NO overlap between the Cnfm boxes for eQSL, LoTW and paper QSL. If you use the right function to import the log (import for LoTW or import for eQSL), then the right thing should happen. Can you send me your .DXL file (before the LoTW import) and the LoTW file you are trying to import? I can try the same import here. Also tell me what version you're running. - Jim On Tue, Jun 1, 2010 at 1:04 PM, Andy P Hewitt andyphew...@btopenworld.com wrote: Hi, Could somebody please give me some guidance? Recently I uploaded my recent log to LoTW and today downloaded the LoTW report. Everything seemed to be OK until I imported the report into DX4Win. I received a window telling me that 41 QSOs had been imported but that 32 QSOs were not found and telling me to look in the save directory for File: LOTWreport 09May10.not found.. When I looked in the DX4Win save directory I found two files the one mentioned and another LOTWreport 01Jun10.not found. The May file has about 90 QSOs and the June file has 32. I had not noticed anything untoward when I imported the last report in May. I opened the two files with Notepad and checked the existence of the QSOs in my log they are all there each one has had the upload flag changed to N and where relevant the LOTW confirmed box changed to Y. There are a wide variety of qsos on different dates/bands/modes. The only other oddity is that I thought that when a QSO was confirmed by LoTW it also set the QSL Card Confirmed to Y, none of the QSOs I have checked have this happen. Can anyone tell me what has happened and what I should do about it please? -- Jim Reisert AD1C, jjreis...@alum.mit.edu, 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
[Dx4win] DX4WIN to LoTW DXCC compare version 1.2 released
I have released version 1.2 of the program to compare DX4WIN DXCC status with LoTW. You can find it at: http://dx4win.ad1c.us/dxcc.htm This version should support all DX4WIN entiity prefixes since I started working on them over 2 years ago. I renamed the program from dxcc.exe to dx4wlotw.exe. I'm sure everyone will love that name, but dxcc.exe is too generic. Also note that the name of the .ZIP file includes the release date. When you download and run the program, make sure it reports version 1.2: Compare DXCC LoTW credit listing to DX4WIN - Version 1.2 Jim Reisert, AD1C - Dec 17 2006 00:10:48 As usual, please let me know of any problems or suggestions. 73 - Jim AD1C -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.us
[Dx4win] DX4WIN to LoTW DXCC compare version 1.1 released
I have released version 1.1 of the program to compare DX4WIN DXCC status with LoTW. You can find it at: http://dx4win.ad1c.us/dxcc.htm When you download and run the program, make sure it reports version 1.1: Compare DXCC credit listing to DX4WIN - Version 1.1 Jim Reisert, AD1C - Dec 4 2006 20:16:13 This version is compatible with the prefix changes introduced in DX4WIN.CTY Release #34. It also adds Swains Island, KH8/S. 73 - Jim AD1C -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.us
[Dx4win] DX4WIN and LOTW
Hi John Not to my knowledge but it is quite simple using DX4win itself, first off select reports/change award flags and clear your awards flags so that you are starting from scratch (this is a one time only process) now in File/Prefrences/Qso, select Upload confirmed save changes and exit, now do a submission and this will submit all your LoTW stats, now its simple from here using Reports/change award flags again select submitted-checked now all your LoTW Q's are marked as C Clearing all award flags at the beginning only works if you dont already have qsls checked manually by the ARRL (like me) but if you have some C's already in then you should be careful what you clear first off. Let me know if you already have cards already marked as checked and i will try to get round this (i have a couple of ideas) 73s de MM0EAX Dave www.eu009.com
[Dx4win] DX4WIN and LOTW
At 09:37 PM 1/8/2006, John (N1JP) wrote: Is there a file from LOTW which can be downloaded to change the 'Submitted' field to 'Checked' field for those Qs which have been awarded is it a manual process? No. -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.us
[Dx4win] DX4Win and LoTW results
Larry when you imported these to DX4WIN how did they show up as a LoTW confirmation so you won't be looking for a card that you don't have, when you make a submission to the ARRL. Because of that I have not tried to import from LoTW yet. Rod WC7N - Original Message - From: Paul van der Eijk [EMAIL PROTECTED] To: Larry Gauthier (K8UT) [EMAIL PROTECTED] Cc: dx4win@mailman.qth.net Sent: Saturday, November 22, 2003 6:51 PM Subject: Re: [Dx4win] DX4Win and LoTW results Larry, You should have a file called adif.pmp in the import directory. This file maps prefixes between adif and dx4win. Check under the entry 291; is that mapped correctly to the USA? Paul At 08:36 PM 11/22/2003 -0500, you wrote: Hi! I completed my first LoTW upload on Friday - shipping about 11,500 QSOs up, and receiving confirmation of 744 QSLs. Very cool - everything seemed to be working fine _until_ after it was all over, and I attempted to import the resulting LoTWdownload.ADI file into DX4WIN to analyze my results. During import into DX4WIN, I received hundreds of error messages - but upon inspection discovered that there were really only 4 errors: All W/K QSOs - Error:Prefix=291 ( for hundreds of QSOs with W/K calls - what does that mean?) DL2FAG - Error:OtherPfx=DL/D (5 errors for 5 different QSOs with the DL2FAG... all other DL QSOs were fine ) 3B6RF - Error:Prefix=4 ( 6 errors for 6 QSOs with 3B6RF ) T88ZZ - Error:Prefix=22 ( 2 errors for 2 QSOs with T88ZZ ) So, are these DX4WIN import errors, or LoTW export errors? Has anyone else had the same problems? -larry K8UT ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] DX4Win and LoTW results
Larry, You should have a file called adif.pmp in the import directory. This file maps prefixes between adif and dx4win. Check under the entry 291; is that mapped correctly to the USA? Paul At 08:36 PM 11/22/2003 -0500, you wrote: Hi! I completed my first LoTW upload on Friday - shipping about 11,500 QSOs up, and receiving confirmation of 744 QSLs. Very cool - everything seemed to be working fine _until_ after it was all over, and I attempted to import the resulting LoTWdownload.ADI file into DX4WIN to analyze my results. During import into DX4WIN, I received hundreds of error messages - but upon inspection discovered that there were really only 4 errors: All W/K QSOs - Error:Prefix=291 ( for hundreds of QSOs with W/K calls - what does that mean?) DL2FAG - Error:OtherPfx=DL/D (5 errors for 5 different QSOs with the DL2FAG... all other DL QSOs were fine ) 3B6RF - Error:Prefix=4 ( 6 errors for 6 QSOs with 3B6RF ) T88ZZ - Error:Prefix=22 ( 2 errors for 2 QSOs with T88ZZ ) So, are these DX4WIN import errors, or LoTW export errors? Has anyone else had the same problems? -larry K8UT ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] DX4Win and LoTW results
Paul, Checking the adif.pmp file in my V6.02, I noted that all seems to map OK, except I did find this puzzling entry on lines 52 - 54: 8Z568 93 93 9A497 Whatever country number 93 is, is listed under 93, rather than a callsign prefix. K is mapped to 291. 73, Joe WD0M At 07:51 PM 11/22/2003, Paul van der Eijk wrote: Larry, You should have a file called adif.pmp in the import directory. This file maps prefixes between adif and dx4win. Check under the entry 291; is that mapped correctly to the USA? Paul
[Dx4win] Dx4win and LoTW
Once you get past the authentication (postcards, passwords, etc) everything is pretty easy. I was impressed with how quickly I was about to upload 11,000 QSOs, but not impressed with the turnaround time in the authentication process. But that's a once-per-callsign process, so it's more than tolerable. And the multiple callsign support is much better than eQSL.cc was, since they can't associate callsigns together for awards purposes. 73, Byron At 04:02 AM 11/12/2003, [EMAIL PROTECTED] wrote: Anyone have any problems with uploading or whatever I need to be aware of before I start this?
[Dx4win] Dx4win and LoTW
Anyone have any problems with uploading or whatever I need to be aware of before I start this? Thanks john
[Dx4win] Dx4win and LoTW
At 04:50 PM 11/11/03 -0500, N3DRK wrote: Anyone have any problems with uploading or whatever I need to be aware of before I start this? No problems at all, although some folks using earlier DX4WIN have had some problems with mode translations, I think, which were discussed earlier on the ARRL-LotW group at Yahoogroups.com. I uploaded 77,000 QSOs from DX4WIN with minimal problems -- mostly typos on my part, like an Oh instead of a Zero. 73, Pete N4ZR The World HF Contest Station Database was updated October 29. 2469 stations are listed -- 29 new and over 100 updated. Are you current? www.pvrc.org/wcsd/wcsdsearch.htm
