[Dx4win] DX4WIN.CTY Release #24 - second call

: [Dx4win] DX4WIN.CTY Release #24 - second call I have updated the release notes for DX4WIN.CTY Release #24: http://www.ad1c.us/dx4win/history.htm#24 This release contains over 750 new QSL manager entries. Some are for contest DX 2x1 and 1x2 callsigns, others for USA 1x1 callsigns

[Dx4win] DX4WIN.CTY Release #24 - second call

:09:10 2005 Subject: [Dx4win] DX4WIN.CTY Release #24 - second call References: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Yes Jim, I guess I didn't say what I wanted to say correctly. When I logged T32S it did come up as OC-024 but I changed it to OC-084 as per the operators instructions. I

[Dx4win] DX4WIN.CTY Release #24 - second call

--- Alan Zack [EMAIL PROTECTED] wrote: I guess I didn't say what I wanted to say correctly. When I logged T32S it did come up as OC-024 but I changed it to OC-084 as per the operators instructions. I was thinking this was a special trip to OC-084 in reference to your question if the

[Dx4win] DX4WIN.CTY Release #24 - second call

I have updated the release notes for DX4WIN.CTY Release #24: http://www.ad1c.us/dx4win/history.htm#24 This release contains over 750 new QSL manager entries. Some are for contest DX 2x1 and 1x2 callsigns, others for USA 1x1 callsigns. This is in addition to the usual new ones from DX