[Dx4win] where do I get version 9.0.9.1259?
Recovering from a Windows 11 "upgrade" disaster... I was able to recover my dx4win log file from said machine. I tried to open it on another machine running 9.0.3.1160 and got an error message along the lines of "log file needs newer version". Oddly, the currently downloadable on dx4win.com seems to be 9.0.3.1160. I managed to recover my dx4win.exe file as well and it says it is 9.0.9.1259, and it does open my log file with no problem. So I'm whole, but the question is: in the interest of future insurance, where does one download 9.0.9.1259? Thanks, -- Scott NX7U __ 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] Oddities importing QSL credit list from LoTW
You can download all your credited DXCC QSOs (or QSLs if you prefer)
from LoTW in ADIF format.
When I import this ADIF file into DX4WIN9, I get a number of errors.
One is from LoTW itself (for some reason there is no explicit
callout on phone QSOs), but I can fix that in the ADIF file itself.
The strange one is that DX4WIN remaps several QSOs to different DXCC.
For example, ZK1CQ from 1989 is North Cooks...the ADIF record even has
the correct : index...yet DX4WIN calls it South Cooks.
Same for 3D2AM from 1990. It's Conway Reef with the correct index, but
DX4WIN calls it Fiji.
A slightly different issue is with V51NAM from 1990...the error is
"prefix empty" and sure enough in the imported log there is no prefix
and therefore no entity identified...except for again, the DXCC index is
correct in the ADIF record.
Any hints as to what is up here? I can't look at my country file
("Country Editor not available") so I can't check valid dates in the
database (although these are all valid...and I have the cards to prove it!).
Thanks,
--
Scott NX7U
__
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] Automating Internet/packet connections
To connect to a telnet packet cluster is normally many steps: Right-click in the packet window and select Internet Connection Select my telnet host from a list Click a function key to login with my callsign Click another function key to sh/dx Is there any way to make all of this happen with a single function key? The bit that is stumping me is that there is no apparent keyboard shortcut for Internet Connection. I use DX4win while mobile, and occasionally have to reset the connection due to cellular coverage. All those steps (*especially* the right-click!) force me to pull over to reset. If I could just reach over and punch a button that would be oh so much better. Thanks in advance, __ 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] Automating Internet/packet connections
Great tip! Thanks! > On Dec 13, 2015, at 13:27, Duane Calvin <ac...@ac5aa.com> wrote: > > As Jim, AD1C, pointed out recently, as long as your cursor is in the lower > part of the packet window, just hit "Enter" three times and you will come up > to the "enter callsign" prompt from the telnet server. If you program your > callsign into one of the F-key's, then all you need to connect is three > "Enter's", and one F-key. Hope this helps. > >73, Duane > > Duane Calvin, AC5AA > Austin, Texas > ac...@ac5aa.com > > > -Original Message- > From: DX4WIN [mailto:dx4win-boun...@mailman.qth.net] On Behalf Of Scott > Townley > Sent: Sunday, December 13, 2015 9:37 AM > To: dx4win@mailman.qth.net > Subject: [Dx4win] Automating Internet/packet connections > > To connect to a telnet packet cluster is normally many steps: > Right-click in the packet window and select Internet Connection Select my > telnet host from a list Click a function key to login with my callsign Click > another function key to sh/dx > > Is there any way to make all of this happen with a single function key? The > bit that is stumping me is that there is no apparent keyboard shortcut for > Internet Connection. > > I use DX4win while mobile, and occasionally have to reset the connection due > to cellular coverage. All those steps (*especially* the right-click!) force > me to pull over to reset. If I could just reach over and punch a button > that would be oh so much better. > > Thanks in advance, > > > __ > 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 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] 8.02 issues
AD1C says: Hi Dave, According to CQ Magazine (and DX4WIN Award database), the single-band WAZ award for 17 meters only counts QSOs starting 01/01/1991; your confirmed Zone 19 QSO is in 1990. There's more to this actually. While a WAZ report correctly reflects the date limits (e.g., for the 12-17-30m bands), the Zone window does not. I have a similar contact where the report shows blank (which is correct...I have not worked that zone since the cutoff date) but the Zone window shows C (which is correct as well, as I have it confirmed but before the cutoff date). To me this is a bit confusing, since I would like to see the awards status of my QSOs without referring to a report. Is this considered the desired behaviour, or is it a bug? Scott Townley NX7U Gilbert, AZ DM43di mailto:n...@cox.net http://members.cox.net/nx7u __ 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] Mailed cutoff - explain?
Either I misunderstand Mailed Cutoff or it's not working correctly in 8.01. Example: Mailed Cutoff value = 730 (days, as I understand)...so 2 years. My understanding is that any QSL Date earlier than 2007-08-29 should show up W instead of M. I have a particular QSO whose QSL date was 2000-02-26. This QSO (the only one in its band-mode combination) shows up M in the Country window. No matter the date (even ridiculous ones like 1930-01-01). The only way to make it show up W is to completely erase the QSL date field. I do have all the electronic QSL date fields blank as well. So it's not that. What I was planning on doing to work-around the M problem is I copy my log to another file, NX7U_packet.dxl and in that log I globally erase all the electronic QSL dates. I had hoped that would restore the original Mailed Cutoff behaviour but no dice. Or like I said, maybe I misunderstand how it works. TIA, Scott Townley NX7U Gilbert, AZ DM43di mailto:n...@cox.net http://members.cox.net/nx7u __ 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] Mailed cutoff - explain?
Like I said, though: the QSO in question *did not have a date entered for any form of electronic QSL*...either LoTW or eQSL. So as far as the log knew, nothing is uploaded and paper is the only thing... At 12:26 2009-08-29, Mel wrote: Hold fire on this... apparently there are some changes coming in 8.02. I believe the M can be an indication that the QSO was uploaded to LotW in 8.01... I haven't really looked at it since it's going to change... Scott Townley wrote: Either I misunderstand Mailed Cutoff or it's not working correctly in 8.01. Example: Mailed Cutoff value = 730 (days, as I understand)...so 2 years. My understanding is that any QSL Date earlier than 2007-08-29 should show up W instead of M. I have a particular QSO whose QSL date was 2000-02-26. This QSO (the only one in its band-mode combination) shows up M in the Country window. No matter the date (even ridiculous ones like 1930-01-01). The only way to make it show up W is to completely erase the QSL date field. I do have all the electronic QSL date fields blank as well. So it's not that. What I was planning on doing to work-around the M problem is I copy my log to another file, NX7U_packet.dxl and in that log I globally erase all the electronic QSL dates. I had hoped that would restore the original Mailed Cutoff behaviour but no dice. Or like I said, maybe I misunderstand how it works. TIA, Scott Townley NX7U Gilbert, AZ DM43di mailto:n...@cox.net http://members.cox.net/nx7u __ 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 Scott Townley NX7U Gilbert, AZ DM43di mailto:n...@cox.net http://members.cox.net/nx7u __ 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] New version?
I have to admit not following these threads closely, so this may have been raised before, but I would like the WAZ tracking to reflect the actual award...for example, if I set the DX Spotting window to WAZ, it colors/announces zones like DXCC, but the single band WAZ awards are single-mode as well. So if I have zone 23 confirmed on 15m CW, but not SSB, then JT1AB on 21.290 comes up nothing. At 23:35 2002-11-12 -0500, Jim Reisert AD1C wrote: At 01:03 PM 11/12/2002 +0100, Radi Kar F6GNZ wrote: Aren't you satisfied with the current version of DX4WIN? What is wrong with it? What is missing for you? Most of us are more than happy with it.. I'm happy with it too, but it could stand some improvement 1. Fix IOTA editor so it doesn't crash when adding new reference numbers 2. Copy IOTA field from previous QSO to current one. This functionality used to be there, but somehow got lost. 3. Improve the US County reports so that they have the same capabilities as the other awards, i.e. mode support, needed lists, double-click on report creates logbook filter, etc. 4. Interface to MMTTY via API rather than complicated serial-port loopback. 5. Have it work BS7 and VU4 for me when they come on the air, even if I'm not home! :-) 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 ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
