I use DX4WIN version 6.04 ... not sure if I should upgrade ... I guess that's another story. Anyway:
A few days ago, I used DX4WIN to export a log for LoTW. I got an error report that listed maybe 8 or 10 calls that said "invalid amateur call" and the problem is that I seem to have entered the letter O instead of the digit zero for several call signs. Is there a way to edit the QSOs to fix the typo? Or, do I have to write down the QSO record data, enter a new QSO off-line, and delete the wrong one? ____________________________________________________________________________________ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. http://answers.yahoo.com/dir/?link=list&sid=396545367 From [EMAIL PROTECTED] Fri Jan 19 10:45:07 2007 From: [EMAIL PROTECTED] (Jim Reisert AD1C) Date: Fri Jan 19 10:46:26 2007 Subject: [Dx4win] Zero, not "O" (oh) In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Steve, just go in your DX4WIN log, edit the callsign(s) in error, and save the QSO(s) (F10). Before saving, take note of any text in the "Notes for this Call" field, as it may change/disappear when you change the call. Also set the Upload flag to Y and clear (erase) the Upload Date before saving the QSO. Now you can report the LoTW export process for the modified QSOs, sign and upload them. 73 - Jim AD1C --- Steve Jackson <[EMAIL PROTECTED]> wrote: > I use DX4WIN version 6.04 ... not sure if I should > upgrade ... I guess that's another story. Anyway: > > A few days ago, I used DX4WIN to export a log for > LoTW. > > I got an error report that listed maybe 8 or 10 calls > that said "invalid amateur call" and the problem is > that I seem to have entered the letter O instead of > the digit zero for several call signs. > > Is there a way to edit the QSOs to fix the typo? > > Or, do I have to write down the QSO record data, enter > a new QSO off-line, and delete the wrong one? -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Fri Jan 19 10:47:58 2007 From: [EMAIL PROTECTED] (Jim Reisert AD1C) Date: Fri Jan 19 10:49:16 2007 Subject: [Dx4win] Adding QSL Managers ?? In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> --- Kostas sv1dpi <[EMAIL PROTECTED]> wrote: > A good solution also is to make a txt file with notepad with the calls like > that > J41K,01/01/2001,SV1DPI > or > J41K,,SV1DPI (without date) Thanks, Kostas. However, watch the date format in this file, it must be: DD/MM/YYYY That may be "second nature" for Europeans, but not for Americans (many of whom still have not mastered the metric system). 73 - Jim AD1C -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Fri Jan 19 11:29:19 2007 From: [EMAIL PROTECTED] (Steve Jackson) Date: Fri Jan 19 11:30:38 2007 Subject: [Dx4win] Zero, not "O" (oh) In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Garry This worked; I never used that window before. Thanks for the 'lesson.' Also thanks to the other guys who responded with suggestions. /steve KZ1X --- Garry Shapiro <[EMAIL PROTECTED]> wrote: > Just double click on those QSO's from your Logbook > window, which moves them > into the Log Entry window, where you can edit the > QSO at your pleasure. > Carriage return brings up a window asking if you > want to save the changes. > But you knew that... ____________________________________________________________________________________ Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/ From [EMAIL PROTECTED] Fri Jan 19 13:11:41 2007 From: [EMAIL PROTECTED] (John Lawler) Date: Fri Jan 19 13:13:33 2007 Subject: [Dx4win] External data,Buckmaster Message-ID: <[EMAIL PROTECTED]> Hi Guys, I have solved this once before but cant remember how to enable call sign lookup from Buckmaster HamCall. What I remember was that I could set the curser on the QSO call sign, hit F3 and hamcall would come up with the specific Call sign information. Will this work ? My configuration is: DW4Win preference/external data/ data source=Buckmaster CD Rom, and Data Directory = C:\ham0\hamcall.dat. I have website callsign lookup disabled . This configuration and as many combinations as I can think of yields nothing. Thanks in advance John, N7EB From [EMAIL PROTECTED] Fri Jan 19 20:40:13 2007 From: [EMAIL PROTECTED] (Jim Reisert AD1C) Date: Fri Jan 19 20:41:34 2007 Subject: [Dx4win] Change your default band cutoffs (USA ops only) Message-ID: <[EMAIL PROTECTED]> Non-USA readers can skip this. As a result of the FCC rule changes that took effect in December, you should modify your band cutoffs. This will help DX4WIN differentiate CW from SSB packet spots on the two changed bands. Go to File -> Preferences -> QSO Look for CW Frequency Cutoff in the lower-right corner. Change the Band box to 80m and the frequency to 3,600 Change the Band box to 40m and the frequency to 7,125 Then File -> Save Changes and Exit. 73 - Jim AD1C -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Sat Jan 20 19:03:15 2007 From: [EMAIL PROTECTED] (Mike Rhodes) Date: Sat Jan 20 19:04:39 2007 Subject: [Dx4win] Re: System Reboots w/DX4Win Startup In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Greetings All, I think I have read of this problem before but naturally I cannot put my finger on the info. I recently reformatted my HD and reinstalled everything including my port expanders, etc. In attempting to get DX4Win communicating with everything again, I used the com port settings from the previous installation. At first, every time I installed the radio and tried to save the preferences, the system rebooted. So, I bypassed that step and configured the rest of the gear one at a time and saved the Preferences file after each attempt. Made it thru everything except the rig and figured I would do a little investigating to figure out which port the rig is actually on. So far so good? Not! I rebooted the system for some other reason and now, every time I try to launch DX4Win, the system restarts. Where do I go to change or remove the com port settings so I can start over again? Also, does anyone have a suggestion on how to find out what is on which port besides trial-and-error-and-error-and-error? Thanks, Mike / W8DN
