<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0mm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0mm;
mso-margin-bottom-alt:auto;
margin-left:0mm;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Bob,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Check version 4.4 . I believe they had an
issue with the cut number conversion being left in place for con<st1:PersonName
w:st="on">test</st1:PersonName>s where it shouldn’t be. Best would have
been an option to turn it on and off. WT 4.4 worked great here. Exchange
guessing also worked very well. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>73 <st1:PersonName w:st="on">Olof</st1:PersonName>
G0CKV<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> support-bounces@win-<st1:PersonName
w:st="on">test</st1:PersonName>.com [mailto:support-bounces@win-<st1:PersonName
w:st="on">test</st1:PersonName>.com] <b><span style='font-weight:bold'>On
Behalf Of </span></b>Bob Henderson<br>
<b><span style='font-weight:bold'>Sent:</span></b> 22 March 2010 05:48<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">support@win-<st1:PersonName
w:st="on">test</st1:PersonName>.com</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> [WT-support] RDXC Woes</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I set up WT (V4.2.0) for RDXC. Everything looked good, with a
short dummy run failing to highlight any issues. Apparently, I should
have tried logging contacts with letters as opposed to numbers in the exchange
field but didn't !<br>
<br>
As soon as the con<st1:PersonName w:st="on">test</st1:PersonName> got under way
my nightmare started. Exchanges received from Russian stations were
guessed correctly but then immediately munged by what I guess is a cut number
converter, as soon as the contact was logged. I took a quick look through
the menus and made a cursory examination of the Wiki in my quest to slay this
monster but failed to find success. I rather optimistically, entered
'CUTOFF' in the call field but WT immediately responded with an 'error in
field' response. Frustrated, I abandoned WT in favour of an old version
of another logger. I lost only 10 minutes, which is hardly the end of the
world so far as RDXC is concerned but I also lost the opportunity to give my
finely honed ESM script a proper work out. Ah well, next time.<br>
<br>
A look through the archives appears to confirm this effect to be the work of a
cut number converter but suggests it is enabled/disabled automatically
depending upon its compatibility with the con<st1:PersonName w:st="on">test</st1:PersonName>
loaded. RDXC an oversight perhaps?<br>
<br>
I imagine there is something I should have done but didn't. I'll really
appreciate it if someone can tell me what it is.<br>
<br>
Bob, 5B4AGN<br>
<br>
PS If there isn't already a way to switch this feature on/off depending upon
operator preference, I would like to make a plea that such be
implemented. After 40+ years of CW con<st1:PersonName w:st="on">test</st1:PersonName>ing
my brain is hard wired with a cut number converter.<o:p></o:p></span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>No
virus found in this incoming message.<br>
Checked by AVG - www.avg.com<br>
Version: 9.0.730 / Virus Database: 271.1.1/2760 - Release Date: 03/21/10
19:33:00</span></font><o:p></o:p></p>
</div>
</body>
</html>