[Dx4win] VUCC Grid award problems
I recently decided to start counting/tracking HF grids. I'm assuming I do this in v9 by going to the awards dialog (QSO_Window->Awards->Reports), going to the "VUCC Grid" tab, and ticking the proper boxes for what bands etc. I want. Let's say 20, 15, and 10 meters. However, nothing I do on the "VUCC Grid" tab 'sticks' after I click OK. I only have this problem with *this award* - i.e. if I make changes on the DXCC or WAZ or whatever other tab, I see the new results right away in the corresponding window or awards report. But my VUCC window and report are stuck on bands "6/2/70/Sat" no matter what I do (which, suspiciously, are the values it has displayed since I migrated from v5 two years ago). Is there a known problem with the VUCC Grid tab (or tracking)? Tnx & 73 Len K1NU __ 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] Not getting WPX credit for AC9 and AC0
The second point seems hard to believe. ‘Not currently issued’ is not the same as ‘not authorized by the ITU’. AC9 and AC0 are both valid standard United States prefixes (not special issues). So they shouldn’t go to the deleted pile. And, a quick scan of QRZ shows many current AC9’s & 0’s. I’m sure most have been continuously allocated since 1979 (when the FCC started issuing 2x1s). Len K1NU > On Aug 6, 2018, at 1:11 AM, WA7AA wrote: > > This file is supposed to list prefixes that have been deleted, i.e. are not > currently valid for the WPX honor roll, according to WPX rules: "Prefixes > will be deleted from the Honor Roll listing ten years after they are no > longer authorized for use by the governing authority or by the ITU". I > suppose since all AC9 and AC0 callsign licenses expired at some point and no > new calls were issued, they met the 10 year rule and found themselves in this > file (among other prefixes). __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] Log printing bug
Not sure where bug reports go, so I'll try here... I periodically print out my log as a backup (also it's nice to have for a quick scan sometimes). Today I tried to print for the first time since I upgraded to v9 a couple months ago. I print the Callsign Notes and QSO Notes fields, among others. The bug seems to be that no matter what I choose for the 'note width' in the Report Editor, D4W sizes the boxes of both Callsign and QSO Notes fields on the printout to around 20 characters, so it winds up overwriting them onto the next field (I can send a snapshot if Paul or someone wants to see it). This problem did not exist in v5. I realize printing bugs are probably low in the backlog :) 73 Len K1NU __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] Importing FT8 to DX4WIN
I also delete the wsjt_log.adi file each time after I import it. Otherwise it will keep appending QSOs, and you will be making D4W process the same QSOs over and over again each time you import. Not a problem I guess if you select 'imported QSO is ignored' but it doesn't seem very efficient. :) (And it'll always be in the recycle bin if I need it) 73 Len K1NU On 2018-07-24 17:38, Carol Richards wrote: Hello all, Thanks for all of the responses. For some reason, DX4WIN didn't like my WSJT_X adi file because it kept hanging with the message, " Reading WSJT_log.adi (not responding)". I worked around the problem by importing the file to N1MM and then to DX4WIN. Not the most ideal way, but I will have to look into the problem a bit more closely. I have never had this problem before...strange. Carol __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to k...@k1nu.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] Import of ADIF "Comment" field
When you import an ADIF file (e.g., from WSJT) into D4W, whatever is in the "" field gets imported into the D4W "Callsign notes" field. This seems wrong to me; in the WSJT example, this field contains the signal reports. A better match seems like "QSO Notes". So, is there an ADIF field that D4W will match to "QSO Notes" on import? If so, I could do a text replace before I import the ADIF file to D4W. Len K1NU __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] Corrupt state file?
Thanks Jim and group, that solved it. Found a few contacts with "DC" that must have been populated from LOTW. Cleared those out, restarted, and all is good. 73 Len On 2018-06-22 12:08, Jim Reisert AD1C wrote: On Fri, Jun 22, 2018 at 9:16 AM Dave N4QS wrote: Yes, I had the same problem a few weeks ago. As I recall, I had imported a contest log that included DC as the state. To find it, I did a search (F8) for DC in the state field. There was one QSO that came up. I merely deleted DC and cleared the state field and saved the QSO. That got me back to 50 states. You also have to exit DX4WIN and re-start, otherwise the strange entry will still be at the bottom of your WAS | Listing. __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] Corrupt state file?
Hi all, After I downloaded the most recent update files, I seem to have a corrupted ‘state’ file. Now, when I do a Reports->WAS->Listing, I have a bogus state entry under Wyoming, and my Summary window says I have 51 states confirmed on some bands. Anyone else see this? I tried renaming country.dat to try to make D4W download it again, but then I get an error when I launch D4W. Sent from Mail for Windows 10 __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] Upgrading v5 to v9
Hi Mike, Thanks for the suggestion. I’m still running the demo version, so at the moment the menu choices on the Import/Export window are grayed out… guess I’ll have to wait to get my license key to try it out. 73 Len > On May 28, 2018, at 7:11 PM, Mike Cizek W0VTT wrote: > > Hello Len, > > Yes, it is a different process; the file format is different in version 9. > I can't remember for sure, but rather than just copying and opening it, try > importing it: > > File > Import/Export > DX4WINVersion 4.06 & later > > That should work. > > -- > 73, > Mike Cizek WŘVTT > > -Original Message- > From: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net] > On Behalf Of Leonard Kay > Sent: Monday, May 28, 2018 17:57 > To: DX4WIN@mailman.qth.net > Subject: [Dx4win] Upgrading v5 to v9 > > Hello all, > > I’m finally upgrading from v5 (all the new modes finally did it…) and I have > an issue. > > I installed 9.03 yesterday and copied over my v5 log file. However, when I > open it, all my “SSB” QSOs come up as “TOR”, and the bands are all wrong. > Other QSO data seems fine. > > This does *not* happen if I open my v5 log file in 8.04 (I happened to have > a demo version laying around). > > Is upgrading from v5 to v9 a two-step process or something? Am I the first > to do this? :) > > Tnx & 73 > Len K1NU > __ > DX4WIN mailing list > Home: http://mailman.qth.net/mailman/listinfo/dx4win > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:DX4WIN@mailman.qth.net > Message delivered to mgci...@gmail.com > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] Upgrading v5 to v9
Hello all, I’m finally upgrading from v5 (all the new modes finally did it…) and I have an issue. I installed 9.03 yesterday and copied over my v5 log file. However, when I open it, all my “SSB” QSOs come up as “TOR”, and the bands are all wrong. Other QSO data seems fine. This does *not* happen if I open my v5 log file in 8.04 (I happened to have a demo version laying around). Is upgrading from v5 to v9 a two-step process or something? Am I the first to do this? :) Tnx & 73 Len K1NU __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] QSL sent info
As long as we're on the subject... :^) If anything, I would rather see just the reverse - leave the F2 key alone but add a QSL Recd field. I like to keep track of how long it took to get QSLs. Right now I put a note that I can search on like RECD xxx in the QSO Notes field. Len K1NU - Original Message - From: Jim Reisert AD1C [EMAIL PROTECTED] To: Paul van der Eijk [EMAIL PROTECTED]; dx4win@mailman.qth.net Sent: Thursday, March 27, 2003 9:23 PM Subject: Re: [Dx4win] QSL sent info While we're on the subject... What about changing the QSL date to the current date once the QSO is *confirmed*, i.e. via F2 key? This way I would know when I received the card, since I no longer care when I sent it. Opinions anyone? - Jim -- 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 ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
