I'm pleased with the new version of DX4WIN. I'm still trying to fully understand the upload confirmed feature which allows one to take the adif report generated by LOTW and import it into DX4WIN to mark QSOs as having been confirmed electronically. I imported the adif report from the LOTW website and chose to set the "Upl Cnf" flag. However, this flag doesn't seem to impact any of my DXCC award totals. I assume that this is by design. I know that I can import the adif file and choose to set the confirmed flag, but would prefer to leave these two fields distinct so that I know whether I have a hardcopy or electronic QSL. It would be nice if there were some way to get the Upl Cnf flag to feed into the award worked totals. Still, it's a good first step towards integration with LOTW.
Richard Eckman KO4MR From [EMAIL PROTECTED] Tue May 11 13:16:28 2004 From: [EMAIL PROTECTED] (Jim Reisert AD1C) Date: Tue May 11 13:17:35 2004 Subject: [Dx4win] 6.03 upload confirmed feature In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> --- Richard Eckman <[EMAIL PROTECTED]> wrote: > I'm pleased with the new version of DX4WIN. I'm still trying to fully > understand the upload confirmed feature which allows one to take the adif > report generated by LOTW and import it into DX4WIN to mark QSOs as having > been confirmed electronically. I imported the adif report from the LOTW > website and chose to set the "Upl Cnf" flag. However, this flag doesn't seem > to impact any of my DXCC award totals. I assume that this is by design. I > know that I can import the adif file and choose to set the confirmed flag, > but would prefer to leave these two fields distinct so that I know whether I > have a hardcopy or electronic QSL. It would be nice if there were some way > to get the Upl Cnf flag to feed into the award worked totals. Still, it's a > good first step towards integration with LOTW. You need to go into your QSO preferences and set "Confirmed QSOs" to "Card or Upload". It may also be true that you need to EXPORT first (from the QSO Windows, Labels -> Export for LoTW) before the "Upload Cnf" flags become active. 73 - Jim AD1C ===== Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC From [EMAIL PROTECTED] Tue May 11 13:36:59 2004 From: [EMAIL PROTECTED] (Steve Bookout) Date: Tue May 11 13:38:31 2004 Subject: [Dx4win] DX4WIN 6.03 NEW USER ONLY glitch Message-ID: <[EMAIL PROTECTED]> Hello all, No matter how hard you try... This should only affect first time installations (new users; new computers) When you install DX4WIN, it determines which operating system you have, 16 bit or 32 bit (Win95/98 vs 2000/XP/NT) and installs the operating system specific port driver. Well, 6.03 *apparently* has it backwards and tries to do just the opposite of what it should. If this is a new install in a new machine, you will get a message that the port driver was not loaded and the program will not run. For those of you with previous installs of DX4WIN this should not be an issue. Those previous installs did install the correct driver into Windows, which version 6.03 will use, so it works as it should. No one caught this because all the beta testers, and Paul and I, all have had previous versions of DX4WIN installed, so none of them bombed. Paul expects, barring any real off the wall issues, to have this resolved this evening, with 6.03.1 being released later tonight. 73 de Steve, NR4M --------------------------------------------- -Steve Bookout, NR4M (ex NJ4F) Rapidan Data Systems 'DX4WIN...The way logging programs should be!' Free demo at http://www.dx4win.com
