FW: [Dx4win] FYI on 4O prefix - Report of fix

[Dick White]

Results of my post,

Jim, AD1C, answered the post I sent and helped me resolve the problem. With
a few e-mails and my following Jim's instructions, we solved the 4O prefix
problem. I sent Jim my old DX4WIN.CTY file, which he evaluated. He had me
 download and install the latest .CTY and .pmp files, which I did. But
DX4WIN still did not recognize 4O calls as Montenegro when I put a call in
the call box. Jim then asked me to go to  FILE - PREFERENCES - QSO  to see
if the CALL SIGN UPDATE box was checked. It was not checked and I checked
it, as per Jim's instructions. Now DX4WIN pops up Montenegro immediately
when I put in any 4O or 4O/xxxx call. Problem solved.  If you have this
problem, be sure the "call sign update" box is checked. It might be the
solution.

As always, Jim rescued another one of use. What a great asset he is to ham
radio. I don't know what some of us would do without his timely help. He is
an example of what I consider ham radio to be all about. We do really share
our knowledge and do help one another.

73  Dick  KS0M

-----Original Message-----
[mailto:dx4win-bounces at mailman.qth.net]On Behalf Of Dick White
Sent: Tuesday, April 01, 2008 11:09 AM
To: DX4WIN Reflector Post
Subject: [Dx4win] FYI on 4O prefix

I worked the 4O/YU1YU call yesterday, CW, and found that DX4WIN did not
recognize it as Montenegro. I entered a fake 4O call and it worked ok. I
also entered other 4O/YU3XXX calls and it still did not know what country it
was. The country data base was looked at and it is correct. For the $o/YU1YU
call I put Montenegro in the prefix box and the call is now in the data
base. This is no big problem for me, but I wonder why this happened ?
Evidently the 4O/YU combination is confusing to DX4WIN.

73  Dick  KS0M
_