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

[Dick White]

Paul,
Jim told me the same thing you are saying. But, I had the problem and what
he had me do fixed it. I have my DX4WIN program on this PC and an IBM lap
top. The problem was repeatable on the lap top as well as the PC. I am now a
happy camper.

Dick  KS0M

-----Original Message-----
From: Paul van der Eijk [mailto:pvandereijk at cox.net]
Sent: Wednesday, April 02, 2008 10:59 PM
To: Jim Reisert AD1C
Cc: Dick White
Subject: Re: FW: [Dx4win] FYI on 4O prefix - Report of fix

Jim,

I do not understand this solution; that option updates (recalculates)
the prefix after every character typed in the callsign field. But the
same calculation is applied as soon as the cursor leaves the callsign
field.

Dick White wrote:
> 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
> _
>
> _______________________________________________
> Dx4win mailing list
> Dx4win at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/dx4win
>
>

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Paul van der Eijk -- Photography
4900 Bradford Drive,
Annandale, VA 22003
(703) 750-9744 Cell: (703) 919-2182
pvandereijk at cox.net
http://members.cox.net/pvandereijk