Re: [Dx4win] Asiatic Russian stations in Europe
Doesn't seem like a bug to me. Remember, UA9 and UA3 are separate countries and completely distinctive prefixes. A UA9 simply affixing a /3 to their call is technically NOT indicating he is in a different DXCC country; technically he should be signing UA9XX/UA3, not simply /3. It's the same as if a stateside station operating from Hawaii signed K5XX/6 instead of K5XX/KH6...the former would not (and should not) show up in the log as Hawaii. The solutions available are two: Log the station using the complete prefix (such as UA9XX/UA3) or enter an exception by changing the country prefix for this particular UA9XX/3 call from UA9 to UA3 (or whatever the standard prefix is for European Russia) in the logging window. I'd be inclined to do the former, but the latter should work as well. Computers can only operate under sets of rules...only our minds can deal with statements that can be paraphrased as don't listen to what I am saying, listen to what I mean! Greg KT0K Date: Wed, 4 Aug 2010 17:22:22 +0200 From: Mel SM0MPV sm0...@stockholm.bonet.se Subject: [Dx4win] Asiactic Russian stations in European part = UA9 To: dx4win Dx4win@mailman.qth.net Message-ID: aanlktikt44nm1=o7u9n+xoe_jmzg8jempptkhujqt...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 Hi, I checked my logs and found that all (i.e. 3) Asiatic Russian station that operated /3 or /6 in the European part of Russia (RV9FQ/6, RA0CCV/3 and UA0QJE/3) were registered as UA9 in the log. This was the only ones I got . When adding e.g. UA9ABC/4 it was loged as UA9. This was also true for UA9ABC/2, so it seems to be a bug. 73 de Mel - SM0MPV 8S0C Contest Call -- ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win End of Dx4win Digest, Vol 76, Issue 3 * __ 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] Remove Duplicate QSLs Revisited
I've read all the app notes and the list archives (going way back) and the manual, and this problem (or variations of it) has been mentioned many times before, so I was surprised to see it in V 8.02. The Remove Duplicate QSLs function is wonderful in concept...just what I need...but in operation it still does not conform to its description in the manual: [Remove Duplicate QSLs] will *not* clear the flag for QSOs that are confirmed already because you may be replying to cards that you just received and want to confirm. In fact, it does do that, which is not a good thing. To test this, I created a new (empty) log and entered just four fake QSOs with the same station, each on a different band. All are essentially new band/mode contacts for that station. All are flagged for labels and one is also checked Y for confirmed, as if I had just received a QSL card for that QSO; all QSL Date fields are empty. Of course I would want to QSL all contacts, even (especially) the one for which I had received a card. None of these contacts fits the description of duplicate QSO. Yet when I run the remove function, it changes the label flag for this QSO to N! Am I missing something, or is there a user-setting that needs to be changed for this to work properly? Am I wrong in what I expect of this function? If it really is a bug, has it been fixed in version 8.03? . I love DX4WIN, and don't like to complain, but this is a very important function to be without, especially for those of us who need to manage logs and QSLs for multiple, multiple actual duplicate QSOs! Thanks for any guidance, Greg KT0K __ 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] Unexpected Unlicensed Demo Version, Can't Save problem
This likely isn't a bug, but is something to be aware of. Yesterday upon exiting DX4WIN 8.02 and answering yes to the Log Modified, Do You Want to Save dialog box, I received the error message that I was using an unlicensed demo version and the log couldn't be saved. Very stupidly thinking it meant nothing because I knew it was licensed, my finger reflex hit the exit button and zap...the day's QSO's were gone. The only thing odd about this logging session was that it began with me double-clicking a DX4WIN shortcut icon in my quick-start bar (which should have been single-clicked) and two DX4WIN sessions tried to open at the same time. One failed (giving an error message) and I exited. The other one started successfully so I simply left that one running and used it. Assuming this was the cause of the unlicensed demo version warning, I have some suggestions: 1. If you are a habitual double-clicker, eliminate your quick-start single-click shortcuts. 2. If you accidently start two sessions simultaneously, exit BOTH and start again. Then test the session you are using to make sure it recognizes your license. 3. If your computer tells you something, LISTEN! Just because YOU know something doesn't mean your computer does! 4. If you get the demo version, can't save log message, don't ignore it...make a hard copy of your changes before exiting, either by capturing a screen dump or by printing the modified portion of your log (if the program lets you). 5. If you contacted KTØK on late 18 October thru early 19 October UTC, drop me an email with the QSO info!! Greg KTØK __ 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] Unexpected Unlicensed Demo Version, Can't Save problem
Hi Mel, I can understand your frustration, but if the demo mode problem I had actually was caused by my inadvertently opening two sessions of the program simultaneously, I wouldn't be so quick to call it a DX4WIN bug...it's probably more of an operator-error, Windows system-error issue, which I intend to avoid assiduously in the future! If, on the other hand, the same thing happens spontaneously without any apparent provocation, then perhaps it would be (was?) something Paul could fix. Personally, this is the first time I've ever experienced this in many, many years of using DX4WIN...so I've never seen it happen without the double-open, operator-goof that I just performed. And the loss of data was my own fault. A simple hit of the Print Screen key would have saved an image of my displayed log which I could have re-entered. DX4WIN is still at the top of my list of logging programs, no question. Greg KTØK -Original Message- From: Mel [mailto:ve...@videotron.ca] Sent: Monday, October 19, 2009 10:01 AM To: Gregory Brown Cc: dx4win@mailman.qth.net Subject: Re: [Dx4win] Unexpected Unlicensed Demo Version, Can't Save problem If that's the bug that plagued ver 7... you could not have saved your log... once in demo mode DX4Win will not allow you to save or even export your log which only resides in memory. I am truly sorry to hear this bug still exists. In ver 7 this bug would rarely manifest itself without any operator error. It may not happen often (twice in about 5 years for me) but it results in lost data which is intolerable. I had suggested that Paul create a transaction log to recover from such problems, but it wasn't implemented in ver 8. Personally... if I lose data one more time with DX4Win... I'm done with it... nonetheless I remain hopeful. Mel, VE2DC Gregory Brown wrote: This likely isn't a bug, but is something to be aware of. Yesterday upon exiting DX4WIN 8.02 and answering yes to the Log Modified, Do You Want to Save dialog box, I received the error message that I was using an unlicensed demo version and the log couldn't be saved. Very stupidly thinking it meant nothing because I knew it was licensed, my finger reflex hit the exit button and zap...the day's QSO's were gone. The only thing odd about this logging session was that it began with me double-clicking a DX4WIN shortcut icon in my quick-start bar (which should have been single-clicked) and two DX4WIN sessions tried to open at the same time. One failed (giving an error message) and I exited. The other one started successfully so I simply left that one running and used it. Assuming this was the cause of the unlicensed demo version warning, I have some suggestions: 1. If you are a habitual double-clicker, eliminate your quick-start single-click shortcuts. 2. If you accidently start two sessions simultaneously, exit BOTH and start again. Then test the session you are using to make sure it recognizes your license. 3. If your computer tells you something, LISTEN! Just because YOU know something doesn't mean your computer does! 4. If you get the demo version, can't save log message, don't ignore it...make a hard copy of your changes before exiting, either by capturing a screen dump or by printing the modified portion of your log (if the program lets you). 5. If you contacted KTØK on late 18 October thru early 19 October UTC, drop me an email with the QSO info!! Greg KTØK __ 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
[Dx4win] A strange Bug continues
I haven't seen this thread before, so forgive me if this has been mentioned. On several occasions when some program has acted very strangely in response to a seemingly unrelated keystroke, I've found that there was a problem (like a sticky key) with the keyboard. So you may think you are typing W5A, but in reality you may be typing Alt W5A, or Ctrl W5A, or some other bizarre combination. If you have a spare keyboard, try swapping it for the one you are using. If you don't have a spare, try blowing out the keyboard with a can of air and gently tapping the frame to dislodge any furch or stuck keys. Greg KT?K Per AD1C's suggestion, I've reloaded the latest .cty file (twice) and find no change in how the program handles the entry of any W5Axx call. It still instantly shuts down at the A keystroke. If I enter W5xx and backspace to insert A the entry is accepted. If I make the same entry on another of my computer's (a laptop, the program accepts the entry as it should. If any of you are so inclined, please make a test entry for W5ADC and see if your log crashes. I'm using 7.02.15, BTW Ken Kopp - K0PP [EMAIL PROTECTED] or [EMAIL PROTECTED]
[Dx4win] Re: Programatically inserting County into DX4WIN files (Alan Zack)
Great point, and one that needs repeating! The QRZ grid info is automatically generated from, apparently, your stations's zip code (or town name?). In most cases, there are several small grids within each, so there is a good chance that the grid reported in QRZ is wrong unless people have calculated it themselves and changed the info. I imagine that there are many people out there that are reporting their own grids (over the air) that they just grabbed from QRZ.COM without confirming them, so you can't even be sure if what they send is correct! Since QRZ.COM is now the defacto reference for such things, everyone should make it a point to go there and update their info. Personally, I think that the grid square info on QRZ should default to blank and only report a grid square if we add it manually. If you can't depend on the accuracy of the data, why have it there at all?? Sorry, that's the scientist in me talking! Greg KT0K -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, November 23, 2006 3:03 AM To: dx4win@mailman.qth.net Subject: Dx4win Digest, Vol 31, Issue 27 Send Dx4win mailing list submissions to dx4win@mailman.qth.net To subscribe or unsubscribe via the World Wide Web, visit http://mailman.qth.net/mailman/listinfo/dx4win or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of Dx4win digest... Today's Topics: 1. Re: Programatically inserting County into DX4WIN files (Alan Zack) -- Message: 1 Date: Wed, 22 Nov 2006 13:03:14 -0800 From: Alan Zack [EMAIL PROTECTED] Subject: Re: [Dx4win] Programatically inserting County into DX4WIN files To: Lee Hallin [EMAIL PROTECTED] Cc: dx4win@mailman.qth.net Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed DX4WIN does this automatically for me using data from QRZ.com. When I log a USA station DX4WIN automatically goes to QRZ.com and looks up the station info for me and places it in the F3 Window. For example, on Veterans Day I worked some special events stations including K0AIR. As soon as I typed K0AIR into the Callsign window the following info appeared in my F3 window: K0AIR Strategic Air Command Memorial ARC Paul W Schleck P.O.Box 1292 Bellevue, NE 68005 Coord: 95.908W 41.149N Grid: EN21bd County = Sarpy USA If I am pleased with this info I press the UPDATE QSO button in the F3 window and this info is logged. The only time I have discovered a problem is in the CQP where people leave their home QTH and activate a county other than their home county. As noted, there is no guarantee that the QRZ.COM info is 100 percent correct as to county and grid info. As for myself, I did change my grid from the one assigned to my PO Box QRZ.COM address to the actual grid down the road from my PO Box to my actual street address.
[Dx4win] RE: INI files
Thanks to everyone who answered my ini file question, both on the discussion list and directly. I think I now understand it well enough not to be dangerous! Greg KT0K
[Dx4win] ICOM 765 !
Lou, I don't have any experience with the interface you are considering, but I did have (apparently) the same problem with my CT-17 and faced the same quandry. My choice was to assume that the MAX232 chip in the CT-17 was fried (the IC is about the most fragile component in there) and decided to try replacing it. Using de-soldering braid and a 15 watt iron, it is quite easy to remove the old chip. Since I didn't want to risk heat damage to the new the new chip, I installed a chip socket instead, then simply plugged in the new chip. The CT-17 now works like a charm, and the job was much easier than I thought it would be. The replacement for the MAX232CPE chip cost $2.19, and the 16 pin solder-tail sockets sell for 10 cents each (but you have to by 10!) The real eye opener was when I priced all the components in the CT-17, and the total came out around 10 bucks! But then you wouldn't have that nice ICOM stencil on the box! Replacing the chip isn't like building your own interface, but it sure was easy and satisfying. Got my parts from Jameco Electronics. They do have a web-presence and a very nice catalog. Good luck! Greg KT0K
[Dx4win] ICOM 765 !
Mel, The point of my post was to let Lou, and anyone else facing the same problem with their CT-17s, know just how easy and inexpensive they are to fix. I wasn't attacking ICOM for overpricing their products, or complaining about the cost of technology. Everyone recognizes the value of research, development, design and marketing, so I didn't think it necessary to append a disclaimer to that effect to my post. It's just always amazed and amused me to find out how much cars, radios, or people for that matter, are worth if you simply total their parts, so I just thought I'd toss the CT-17 example in as an humorous aside to my post. That a $1.87 worth of organic chemicals can take about $2 worth of paint and canvas and turn it into a multi-million dollar work of art is pretty amazing. I sure as heck can't do that...but I *can* fix a CT-17 for $3.00, and hopefully now Lou and a few others might give it a try, too. I'll leave the creation of real Mona Lisas, such as DX4WIN, the ProII and superfluous responses to helpful posts, to real artists! ;-) Happy New Year to all of us common, parts-cheap, folk! Greg KT0K -Original Message- Reply-To: [EMAIL PROTECTED] From: Mel Martin (VE2DC) [EMAIL PROTECTED] To: 'Gregory Brown' [EMAIL PROTECTED], dx4win@mailman.qth.net Subject: RE: [Dx4win] ICOM 765 ! Date: Tue, 31 Dec 2002 20:19:46 -0500 If you added up the cost of the components of a Pro II, I doubt that would come out anywhere near the selling price either... But then, is the value of the Mona Lisa calculated in terms of a little canvas and some oil paint? Happy New year to all...
[Dx4win] RE: Dx4win digest, Vol 1 #209 - 2 msgs
Brian, If you have Quick Split set to On on the 756PROII, the behavior you mention is the default. The easiest way to accomplish the behavior you want is to set Quick Split to Off. Then clicking on spots will set the spit frequencies correctly and bring the main VFO VFO A into the foreground. Of course, if you wish to use the Quick Split feature on the radio (without DX4WIN control), you'll have to reset it to On. This is certainly something DX4WIN could be programmed to do, but probably not at the user level. To call for split operation, DX4WIN executes a series of commands, such as: set VFO A, switch VFO A -- B, set VFO A, split on. This command string does not change the default setting on the radio for Quick Split (which is what is calling for Select Sub VFO). An additonal command would have to be inserted into DX4WIN's split call command string to Select Main Readout (07D0). This should be easy enough to do for the programmer, but I don't know how to do it on the user end. Greg KT0K -Original Message- Has anyone figured out how to force VFO A to the foreground when selecting a spot, with the 756PRO II? If VFO B is active, and you select a spot, it drives the B VFO to that frequency. If the spot you selected is split, you wind up transmitting on the receive frequency unless you notice and manually force A to the foreground and re-select the spot.
[Dx4win] 756ProII rig file
Original message: Speaking of the 756Pro...I have a 756 Pro II, and I'd like to have it set filter 1 rather than filter 2 for SSB use. Before I start poking around and re-inventing the wheel, does anyone have a rig file specific to the Pro II that has this already set up? David, I'm using an older version of DX4WIN and am using the IC-775 radio file with my IC-756 PROII, but this command should work for your setup, too. To get DX4WIN to call the wide CW filter (filter 1), change the Set Mode command string to 060001FD. This will call the wide filter for SSB, too. I like to have the radio go to wide filter when clicking a spot, because the frequencies for spots are sometimes not highly accurate. If you would rather call the medium or narrow filters (for some reason). use the command strings 060002FD and 060003FD, respectively. Greg KT0K
