<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:193348914;
mso-list-type:hybrid;
mso-list-template-ids:-12534306 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:321663868;
mso-list-type:hybrid;
mso-list-template-ids:-1438730290 -53212698 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-start-at:3;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks Bob.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>No Anti-Virus and all other programs killed as well. The tuning
graphs are the culprit, that was my conclusion as well.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:18.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I mean the function of the partner window to display the callsign
field of the other station in the upper row of the partner window. Not the
stacked calls in the lower part. The partner window is updated in real time when
the other station is typing into callsign window. But not at all updated and
left blank when callsign is grabbed with INSERT by the support operator. So RUN
operator does not see it unless the support op puts it into stack or manually does
something more on the callsign field like deleting the last letter and adding
it again.<o:p></o:p></span></p>
<p class=MsoListParagraph><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>4.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>No scripts. And no DEFINEKEYS issue as it acted this way with
original Insert key as well. No ESM.<o:p></o:p></span></p>
<p class=MsoListParagraph><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>5.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have to admit, I have neglected $NEXT. This might help. Not Partner
window related now as I want the gtail end function for SO. So if I have TU
message defined as: </span>TU $CR $NEXT $F2, <span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>then if I have just entered 1
or 2 characters of the call by the time WT starts fulfilling the $NEXT macro,
will it let me finish the call and accept the other characters or it fixes the
contents of the callsign window at the time when it reaches $NEXT in the
message and later typing is ignored?<o:p></o:p></span></p>
<p class=MsoListParagraph><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>But what about this script thing? Can I not add ALT-K into a
message like PSE QSY $ALT-K somehow with that?<o:p></o:p></span></p>
<p class=MsoListParagraph><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> rawilson@gmail.com
[mailto:rawilson@gmail.com] <b>On Behalf Of </b>Bob Wilson, N6TV<br>
<b>Sent:</b> Wednesday, September 29, 2010 12:05 AM<br>
<b>To:</b> support@win-test.com; Tõnno Vähk<br>
<b>Subject:</b> Re: [WT-support] ALERT! CQWW RTTY RULES FOR MS??<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>On Tue, Sep 28, 2010 at 1:11 PM, Tõnno Vähk <<a
href="mailto:Tonno.Vahk@gafm.ee">Tonno.Vahk@gafm.ee</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>1. WT and MMTTY seems to require very powerful computer? I
had one of my older but very decent laptops running at one station and the CPU
usage was constantly running close to 100% and RTTY code was often delayed.
Sometimes it took more than 3 seconds of solid carrier after starting TX for
the code to start slowly coming. Is there something that can make it easier for
the computer or I just need more powerful machines?:)<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
Did you have any Anti-Virus software running on this machine? I've noticed
that the latest Anti-Virus programs cause Win-Test and any other program to run
very slowly, just after you update the .exe file. Then after some period
of use, the Anti-Virus program seems to "learn" the ports that the
program uses to communicate, and it adds an automatic "exception,"
and then the program runs at normal speed.<br>
<br>
MMTTY <i>does</i> use a lot of CPU time, especially to update the tuning graphs
in real time.<o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm'>
<p class=MsoNormal>3. Partner window is updated only when something written or
deleted on the other station's callsign field. BUT... when the callsign is
grabbed with Insert from RTTY window then Partner window stays blank! This is a
small detail maybe but I guess could be classified as bug? In RTTY thus the
partner window becomes very inefficient.<o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal><br>
Alt-Enter has to be used to put callsign in the partner window. Are you
saying when the run op presses Insert the callsign disappears from partner
window is emptied? Are you sure that $GRABPARTNER wasn't specifed in an
S&P message, and you were accidentally in S&P mode instead of RUN mode?<br>
<o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm'>
<p class=MsoNormal>4. Grabbing callsign with INSERT from RTTY window did not
work for RUN station when it was in Advanced SO2R mode. I did not test it
extensively, just switched to SO1R and it worked OK. But it had to do something
with scenarios. My INSERT key was defined as: $LOGGEDCALL $SPACEBAR $GUESSEXCH
$F2, F2 was defined as $RST $ZONE and in scenarios F2 was defined as $R2R2 $F2
$R1R2 I think. This might be an serious issue for SO2R operator. Somebody might
want to try if he can replicate this problem. For me it seemed to trigger
2xSPACEBAR moving the cursor to S/P field and not grabbing anything from RTTY
window.<o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
Did you have any LUA scripts assigned to the spacebar or $F2? Type
SCRIPTS [Enter] or select Tools | Scripts Manager to check this. Also
check DEFINEKEYS.<br>
<br>
Were you using ESM mode or NOESM?<o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm'>
<p class=MsoNormal>5. The old thing of wishing to have $KEYB Macro to be
inserted in a message to trigger ALT-K (keyboard mode) to be able to program
for example TU NEXT $KEYB to do tail ending. Or to send PSE QSY $KEYB to QSY a
multiplier. I am not 100% sure - you guys have not already implemented it, have
you?? I long for this every CW and now also RTTY contest.<o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal><br>
$CORRECT TU $CR NOW $GRABPARTNER $NEXT $F2<br>
<br>
is about the only mechanism available for stacking QSOs in Win-Test I think.<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><br>
73,<br>
Bob, N6TV<o:p></o:p></p>
</div>
</body>
</html>