[Dx4win] Tweaking Award Manager settings
Hi Folks, Not all possible award combinations are turned on by default. For example, in the County and IOTA awards, only the Mixed mode award is enabled. If you try to do (for example), a 40 meter or CW needed listing for those awards, you will get an empty window as a result. You can fix this by going into the Award manager (File | Awards) and enabling the award type(s) you want to track in the box underneath the Awards header (mixed/band/mode). You will need to do this separately for each award you are interested in. When done, click on the OK button. The Awards settings don't seem to affect the summary windows (QSO Window: Window | IOTA or Window | County for example). If you are only tracking a Mixed award (not band or mode), the summary window will still show a matrix of all bands and modes (that are enabled in your station preferences). I first noticed this with the VUCC award. Paul will look into it. 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] Something wrong with the key file
I've the same problem of Roger, W1EM. I placed the key (IZ4GWE_lic.dx4w8) in dx4w801 folder and when save the log, also a new log, i get a message: Something wrong with the key file and after An exception occurred! Previleged instruction and the program not save nothing. The PC has Win XP Prof. and i running as administrator. Is it a problem of key ? Michele, IZ4GWE __ 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] Something wrong with the key file
At 11:52 PM 8/4/2009, IZ4GWE - Michele - Ravenna wrote: Is it a problem of key ? Yes. Problem detected and corrected. New keys going out ASAP. Dick -- Dick Flanagan K7VC d...@k7vc.com __ 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] V8.01 Observations (long)
Yes, Randy, I find same problem with DXCC CW statistic, that majority of checked countries is only as confirmed! So I hope it will be solved. 73, Milos, OK1MP Message: 9 Date: Tue, 04 Aug 2009 20:27:57 -0500 From: Randy Farmer w...@tx.rr.com Subject: [Dx4win] V8.01 Observations (long) To: dx4win@mailman.qth.net Message-ID: 20090805012758316.fddc18...@cdptpa-omta01.mail.rr.com Content-Type: text/plain; charset=us-ascii; format=flowed I downloaded and had a look at the new version today. I don't yet have my license key, but I was able to import my version 7 log and check out some of the new features. Importing the Version 6/7 format log file into Version 8 was absolutely trouble free. I did have to re-do some of my custom Logbook Report formats to account for the new fields, but this was no problem at all. All of my Selections and Group definitions imported perfectly. I'm especially glad to see the improvements to the LOTW record keeping and the elimination of the need to explicitly filter the log by date selection to get accurate DXCC CW statistics. The testing I've done so far has concentrated on checking out the DXCC CW reporting. Unfortunately, I have found some problems. I have around 56K QSOs in my log, the vast majority being CW. The log files go back to 1965, so there are a good many CW QSOs in the log that were made prior to being eligible for CW DXCC credit. Some of these have been submitted for Mixed and Band DXCC credit. I also keep track of my DXCC records using a fairly elaborate Excel spreadsheet and make sure it's updated every time the DX4WIN log changes and/or I receive new DXCC credits from ARRL. My standard procedure is to do a quick compare of the DX4WIN DXCC Summary reports against this spreadsheet each time after importing LOTW data or making any other changes to the log. I checked out the Version 8 DXCC Summary reports and found right away that regardless of the selection made in the dropdown boxes the Summary report ALWAYS gives the stats for All Bands / All Modes. The good news is that these stats are completely accurate, including the CW numbers. I tried all combinations of the Modes and Bands dropdown choices and always got the All modes / All bands report. I then took a look at the Listing reports for various band and mode combinations.To use the Listings data, I use the Write to File option to dump the report data to csv format to import into Excel. It's disappointing that while the Listing report format has changed slightly, it STILL uses the asterisk (*) character to designate Checked status. The asterisk is a special wild card character in Excel, and directly importing the csv file makes it impossible to edit and manipulate the data -- weird things happen. This means I still need to first run the csv file through Wordpad or some similar text editor to do a search and replace of the asterisk with some other character so I can use the file in Excel. It would be real nice if the report output used some other character to show Checked status. All of the DXCC reports except for CW were completely correct. There were multiple discrepancies for CW DXCC, which upon close examination all turned out to be the result of counting pre-1975 QSOs for CW credit. If these old records were excluded from the statistics, the CW report would be totally accurate. I have taken great care in setting the Mixed, Band and Mode credit flags for these older QSOs in the log file, and none has the Mode credit flag set, yet the report claimed that they were credited for CW. Apparently the internal logic of the program looks at neither the QSO date nor the status of the DXCC Mode flag when it generates the DXCC report. So we're almost there... The Summary gets the CW statistics correct, so there's clearly some logic that runs on QSO date, but it's obviously incompletely implemented. Also regarding the Listing report, when including Deleted entities the new version sorts its output in alphabetical Prefix order without regard for whether the prefix is for a Deleted entity or not. The older versions put all the Deleteds in alphabetical order at the bottom of the prefix list, a MUCH better way to present the data. I had to immediately re-sort the imported csv files to get them in the same order as the data from Version 7. Please restore the Version 8 Listing report to the same format as the Version 7 and earlier listings! There is also some sort of internal coding error that caused me a bit of hair pulling. For some reason, while the prefix for Minami Torishima is JD1/M, the Listing report renders it as JD1/W and thus interchanges the lines for Minami Torishima and Ogasawara, JD1/O. It was no fun dealing with this until I took a close look at the report and saw the incorrect prefix. Apart from these small problems, I like the looks of the enhancements to this new version of DX4WIN. I'm looking forward to getting my license key and doing
Re: [Dx4win] V8.01 Observations (long)
Hi Randy, I do second your very accurate review. I've found the same CW problems; yes, should be nice to change the asterisk in the reports and get back the listing report to the version 7 format as well. 73 DX de PY2YP - Cesar Randy Farmer wrote: I downloaded and had a look at the new version today. I don't yet have my license key, but I was able to import my version 7 log and check out some of the new features. Importing the Version 6/7 format log file into Version 8 was absolutely trouble free. I did have to re-do some of my custom Logbook Report formats to account for the new fields, but this was no problem at all. All of my Selections and Group definitions imported perfectly. I'm especially glad to see the improvements to the LOTW record keeping and the elimination of the need to explicitly filter the log by date selection to get accurate DXCC CW statistics. The testing I've done so far has concentrated on checking out the DXCC CW reporting. Unfortunately, I have found some problems. I have around 56K QSOs in my log, the vast majority being CW. The log files go back to 1965, so there are a good many CW QSOs in the log that were made prior to being eligible for CW DXCC credit. Some of these have been submitted for Mixed and Band DXCC credit. I also keep track of my DXCC records using a fairly elaborate Excel spreadsheet and make sure it's updated every time the DX4WIN log changes and/or I receive new DXCC credits from ARRL. My standard procedure is to do a quick compare of the DX4WIN DXCC Summary reports against this spreadsheet each time after importing LOTW data or making any other changes to the log. I checked out the Version 8 DXCC Summary reports and found right away that regardless of the selection made in the dropdown boxes the Summary report ALWAYS gives the stats for All Bands / All Modes. The good news is that these stats are completely accurate, including the CW numbers. I tried all combinations of the Modes and Bands dropdown choices and always got the All modes / All bands report. I then took a look at the Listing reports for various band and mode combinations.To use the Listings data, I use the Write to File option to dump the report data to csv format to import into Excel. It's disappointing that while the Listing report format has changed slightly, it STILL uses the asterisk (*) character to designate Checked status. The asterisk is a special wild card character in Excel, and directly importing the csv file makes it impossible to edit and manipulate the data -- weird things happen. This means I still need to first run the csv file through Wordpad or some similar text editor to do a search and replace of the asterisk with some other character so I can use the file in Excel. It would be real nice if the report output used some other character to show Checked status. All of the DXCC reports except for CW were completely correct. There were multiple discrepancies for CW DXCC, which upon close examination all turned out to be the result of counting pre-1975 QSOs for CW credit. If these old records were excluded from the statistics, the CW report would be totally accurate. I have taken great care in setting the Mixed, Band and Mode credit flags for these older QSOs in the log file, and none has the Mode credit flag set, yet the report claimed that they were credited for CW. Apparently the internal logic of the program looks at neither the QSO date nor the status of the DXCC Mode flag when it generates the DXCC report. So we're almost there... The Summary gets the CW statistics correct, so there's clearly some logic that runs on QSO date, but it's obviously incompletely implemented. Also regarding the Listing report, when including Deleted entities the new version sorts its output in alphabetical Prefix order without regard for whether the prefix is for a Deleted entity or not. The older versions put all the Deleteds in alphabetical order at the bottom of the prefix list, a MUCH better way to present the data. I had to immediately re-sort the imported csv files to get them in the same order as the data from Version 7. Please restore the Version 8 Listing report to the same format as the Version 7 and earlier listings! There is also some sort of internal coding error that caused me a bit of hair pulling. For some reason, while the prefix for Minami Torishima is JD1/M, the Listing report renders it as JD1/W and thus interchanges the lines for Minami Torishima and Ogasawara, JD1/O. It was no fun dealing with this until I took a close look at the report and saw the incorrect prefix. Apart from these small problems, I like the looks of the enhancements to this new version of DX4WIN. I'm looking forward to getting my license key and doing more testing with live hardware. Thanks to Paul for a significant improvement in this new generation of
[Dx4win] Minor bug carried forward from Ver 7
D4W still looks for the help file in the Current Directory. If you use the Common Dialog Control and change the current directory... for example, merging another file... the help menu fails to find the help file. Could the program open the help file with the path prepended to the file name? In C# I use: Application.StartupPath + \\foofilename. This should work with D4W since the help is in the same directory as the executable. Mel, VE2DC __ 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] Minor bug carried forward from Ver 7
I had this problem last night on my laptop. I exited DX4WIN8 and started again and the problem went away, never to return. 73 - Jim AD1C On Wed, Aug 5, 2009 at 9:38 AM, Melve...@videotron.ca wrote: D4W still looks for the help file in the Current Directory. If you use the Common Dialog Control and change the current directory... for example, merging another file... the help menu fails to find the help file. Could the program open the help file with the path prepended to the file name? In C# I use: Application.StartupPath + \\foofilename. This should work with D4W since the help is in the same directory as the executable. Mel, VE2DC -- 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] Region-2 40 Meter bandplan
Region-2 7 MHz Bandplan FREQUENCY(kHz) MAX BANDWIDTH(Hz) PREFERRED MODE AND USAGE 7000 - 7025 200 CW, contest preferred 7025 - 7040 200 CW, 7030 kHz - QRP Centre of Activity 7040 - 7047 500 Narrow band modes - digimodes 7047 - 7050 500 Narrow band modes - digimodes, automatically controlled data stations (unattended) 7050 - 7053 2700 All modes - digimodes, automatically controlled data stations (unattended) (*) 7053 - 7060 2700 All modes - digimodes 7060 - 7100 2700 All modes, SSB contest preferred 7070 kHz - Digital Voice Centre of Activity 7090 kHz - SSB QRP Centre of Activity 7100 - 7130 2700 All modes, 7110 kHz - Region 1 Emergency Centre of Activity 7130 - 7200 2700 All modes, SSB contest preferred, 7165 kHz - Image Centre of Activity 7175 - 7200 2700 All modes, priority for intercontinental operation For those who are interested in having more accurate spot colors On 40M band with the new bandplan(few months old) you can change the CW Frequency cutoff to 7,060 instead of 7,040 File Preferences QSO CW cutoff 40M 7,060 Save changes and exit Guy ON4AOI __ 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] RES: V8.01 Observations (long)
Ola amigo Você vai para Natal?? Um abraço Atilano -Mensagem original- De: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net] Em nome de PY2YP Enviada em: quarta-feira, 5 de agosto de 2009 12:35 Para: Dx4win@mailman.qth.net Assunto: Re: [Dx4win] V8.01 Observations (long) Hi Randy, I do second your very accurate review. I've found the same CW problems; yes, should be nice to change the asterisk in the reports and get back the listing report to the version 7 format as well. 73 DX de PY2YP - Cesar Randy Farmer wrote: I downloaded and had a look at the new version today. I don't yet have my license key, but I was able to import my version 7 log and check out some of the new features. Importing the Version 6/7 format log file into Version 8 was absolutely trouble free. I did have to re-do some of my custom Logbook Report formats to account for the new fields, but this was no problem at all. All of my Selections and Group definitions imported perfectly. I'm especially glad to see the improvements to the LOTW record keeping and the elimination of the need to explicitly filter the log by date selection to get accurate DXCC CW statistics. The testing I've done so far has concentrated on checking out the DXCC CW reporting. Unfortunately, I have found some problems. I have around 56K QSOs in my log, the vast majority being CW. The log files go back to 1965, so there are a good many CW QSOs in the log that were made prior to being eligible for CW DXCC credit. Some of these have been submitted for Mixed and Band DXCC credit. I also keep track of my DXCC records using a fairly elaborate Excel spreadsheet and make sure it's updated every time the DX4WIN log changes and/or I receive new DXCC credits from ARRL. My standard procedure is to do a quick compare of the DX4WIN DXCC Summary reports against this spreadsheet each time after importing LOTW data or making any other changes to the log. I checked out the Version 8 DXCC Summary reports and found right away that regardless of the selection made in the dropdown boxes the Summary report ALWAYS gives the stats for All Bands / All Modes. The good news is that these stats are completely accurate, including the CW numbers. I tried all combinations of the Modes and Bands dropdown choices and always got the All modes / All bands report. I then took a look at the Listing reports for various band and mode combinations.To use the Listings data, I use the Write to File option to dump the report data to csv format to import into Excel. It's disappointing that while the Listing report format has changed slightly, it STILL uses the asterisk (*) character to designate Checked status. The asterisk is a special wild card character in Excel, and directly importing the csv file makes it impossible to edit and manipulate the data -- weird things happen. This means I still need to first run the csv file through Wordpad or some similar text editor to do a search and replace of the asterisk with some other character so I can use the file in Excel. It would be real nice if the report output used some other character to show Checked status. All of the DXCC reports except for CW were completely correct. There were multiple discrepancies for CW DXCC, which upon close examination all turned out to be the result of counting pre-1975 QSOs for CW credit. If these old records were excluded from the statistics, the CW report would be totally accurate. I have taken great care in setting the Mixed, Band and Mode credit flags for these older QSOs in the log file, and none has the Mode credit flag set, yet the report claimed that they were credited for CW. Apparently the internal logic of the program looks at neither the QSO date nor the status of the DXCC Mode flag when it generates the DXCC report. So we're almost there... The Summary gets the CW statistics correct, so there's clearly some logic that runs on QSO date, but it's obviously incompletely implemented. Also regarding the Listing report, when including Deleted entities the new version sorts its output in alphabetical Prefix order without regard for whether the prefix is for a Deleted entity or not. The older versions put all the Deleteds in alphabetical order at the bottom of the prefix list, a MUCH better way to present the data. I had to immediately re-sort the imported csv files to get them in the same order as the data from Version 7. Please restore the Version 8 Listing report to the same format as the Version 7 and earlier listings! There is also some sort of internal coding error that caused me a bit of hair pulling. For some reason, while the prefix for Minami Torishima is JD1/M, the Listing report renders it as JD1/W and thus interchanges the lines for Minami Torishima and Ogasawara, JD1/O. It was no fun dealing with this until I took a close look at the report
Re: [Dx4win] V8.01 Observations (long)
I too am excited that Paul finally implemented a start date for DXCC CW. I also have QSOs dating back to 1967. I have been comparing the Summary totals and the Listing totals for CW between ver 8.0 and 7.07. I personally like the way that Paul has implemented the DXCC Listing for CW. For example, I have a CW contact with ZL4OL/A from 1971 that I had submitted for DXCC Mixed and 20M Band credit. Prior versions would always attempt to submit this contact for DXCC CW credit. Now it does not. When I do a DXCC Listing for CW mode, there is an asterisk on 20M for that contact -- and that is correct since I did make a CW contact on that band -- and I want to see it since I may have submitted it for DXCC Band/Challenge credit. However, the new Listing for CW does not have an asterisk for that contact under the first column which is CW mode. And that is correct also, since it occurred prior to 1975. The Listing also works fine for Deleted Countries prior to 1975. For example, I have a number of KZ5 contacts on CW that prior versions would always try to submit for CW credit. The Listing shows asterisks on the bands on which I made those QSOs on CW, but does not show an asterisk under the CW mode column -- which is exactly the way that I would want the data displayed. Now that you explain it this way, I see your point. I was myopically trying to do stats only for DXCC-eligible CW contacts, but since there's no per band CW DXCC award there's really no point in segregating the older CW QSOs from the analysis. If you think of the asterisk as an indicator that means Don't bother submitting this one for DXCC CW as opposed to This one has already been credited for CW DXCC (a subtle but important distinction) Paul's logic all makes sense for the reasons you cite. I can and will live happily with this convention in my own offline record keeping. As you point out, the entity CW DXCC credits are correct now. I'm still trying to figure out if there's some sort of a bug in 8.01 in the Reports - Summary function, however. No matter what selections I make from the dropdown list of options I ALWAYS get the summary for All bands / All modes. Does this happen to just me (on two different installations on two different computers) or does anyone else see this problem? It for sure worked just fine in version 7 and earlier. I still do not see a way to easily submit both Lotw and Card confirmations for DXCC. I wish the Submission report would list how the contacts were confirmed -- e.g. Lotw, Card, etc. That way I could more easily separate out Lotw submissions from Card submissions when making an online submission of both types via the Lotw website. This is what originally drove me to set up separate tracking functions in Excel. Since the inception of LoTW I had nothing but troubles getting submissions together. It took work in Excel to figure out what was going on anyway, so I just started doing the whole submission thing that way. The fact that the program logic also will invariably select a Phone QSO for a Band or Mixed submission when there's a perfectly good CW QSO that could fill the same bill doesn't help, either. I'm just a CW kind of guy, and I'll always submit CW stuff when I can :) Thanks for the slap upside the head that got me out of a bad rut in my thinking. I'll now quit bellyaching about the handling of DXCC CW and enjoy the features of the new version. 73... Randy, W8FN __ 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] That darn asterisk
I had mentioned in my post yesterday that somehow the Report Listing file had mysteriously converted the Minami Torishima prefix from JD1/M to JD1/W. I did a little detective work today and found out what happened. When I edit the csv Listing file in Wordpad to change the asterisk to something that Excel finds more digestible, I also routinely convert all the M flags (and the L flags in Version 7) to W, since my Excel application really only cares about whether something is Worked (W), Confirmed (C) or Credited (X). I've been doing this for the three years or so since I started using Excel to track my DXCC stats and set up submissions. It works fine. It turns out that even when you tick the Match whole word only box in the Search and Replace function in Wordpad, it goes ahead and changes every occurrence of /M to /W (thanks, Bill). So not only was JD1/M getting changed to JD1/W, HK0/M turned into HK0/W, etc. This never caused me any problem with the Version 7 report files, because I just dumped the csv file into Excel, selected the 160 through 6 data cells and pasted the cell contents into my main spreadsheet. The spreadsheet is set up just like the Version 6 listing file, with the active prefixes sorted alphabetically at the top of the list followed by the deleted prefixes sorted alphabetically at the bottom of the list. But... the Version 8 Listing format has changed, and now the prefixes are listed in straight alphabetical order, with the deleted prefixes interleaved with the active prefixes. This means to get the data in the order I need for my spreadsheet I have to do a sort by first the D field and then the Prefix field. When I do this sort, the erroneous JD1/W now gets put behind Ogasawara, JD1/O and the Ogasawara and Minami Torishima data lines are now reversed. All of this is a long way of explaining why I'm making a request to revise Version 8 in two ways: 1. Use some character other than * to flag entries ineligible for DXCC submission in the Report module. 2. PLEASE restore the Prefix order in the Report Listing format to that used in Version 7, with the active prefix list followed by the deleted prefix list. Since there will undoubtedly be some fine tuning happening after the initial release of V8.01 this would be a good time to make these changes. The asterisk issue is really pretty minor, but fixing it would make life easier for those of us who import the report file into Excel for whatever reason without forcing an intermediate editor session to replace the character. The change in the Listing prefix order is really a giant step backwards in user friendliness. There's really no point in cluttering the report with dozens of dead prefixes that most users never have, and certainly never will, encounter in their logs. Put the deleted prefixes at the end of the listing where they won't bother those who don't need them. It may sound like I'm incessantly whining about small things, and perhaps I am. But I still really like the new version. I'm looking forward to getting my license key so I can start using it in earnest. 73... Randy, W8FN __ 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] iota
How do I save the Iota list and where do I put it again? Thanks- John EMAIL: j...@w9rpm.com WEBPAGE: http://www.w9rpm.com/ DX and CONTEST CLUB: http://www.w9idx.com/ AOL IM: W9RPM YAHOO: W9RPM __ 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] iota
Close your log Goto file Databases Iota File Export iota data Afterwards Import data there GUY ON4AOI -Oorspronkelijk bericht- Van: dx4win-boun...@mailman.qth.net [mailto:dx4win- boun...@mailman.qth.net] Namens W9RPM Verzonden: donderdag 6 augustus 2009 6:39 Aan: DX4WIN Onderwerp: [Dx4win] iota How do I save the Iota list and where do I put it again? Thanks- John EMAIL: j...@w9rpm.com WEBPAGE: http://www.w9rpm.com/ DX and CONTEST CLUB: http://www.w9idx.com/ AOL IM: W9RPM YAHOO: W9RPM __ 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
