<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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 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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The first line should read could = could not<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>
<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"'>
support-bounces@win-test.com [mailto:support-bounces@win-test.com] <b>On Behalf
Of </b>Tõnno Vähk<br>
<b>Sent:</b> Thursday, June 03, 2010 10:31 AM<br>
<b>To:</b> support@win-test.com<br>
<b>Cc:</b> k5zd@charter.net<br>
<b>Subject:</b> Re: [WT-support] Feature request: PARTNER WINDOW<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I could agree less with you 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=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>We have been there and this argument is finished and it has been
very clearly communicated and agreed that there is no limit to physical
stations/receivers/transmitters/computers as long as there is ONE SIGNAL IN THE
AIR AT A TIME (in this case). Or two signals in M2 case.<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'>Every serious MS participant (at least in EU) has more than one
transmitter (3 to 6 as a rule at least). This is 100% coherent with the rules
and accusing anyone in violating the rules is wrong, unjust and shortsighted.<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'>What I am doing is to try to make WT help stations to fulfill
the rules. Improve WT to support correct ONE SIGNAL AT A TIME management. I am
afraid there are stations who are not following TX blocking requirement and
that is a real problem.<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'>So those enhancements I am asking would encourage following the
rules not opposite! I am amazed you have got it upside down.<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'>If WPX wanted to limit number of transceivers in use in station
it could do so. IOTA contest has done it. WPX has not.<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'>I CC Randy here because it is really sad that this argument is coming
up. The same as SOAB operators “accused” in using SO2R (exactly the same
wording in the rules – one transmitted signal at a time). Come on!<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'>Tonno<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"'>
support-bounces@win-test.com [mailto:support-bounces@win-test.com] <b>On Behalf
Of </b>Bob Wilson, N6TV<br>
<b>Sent:</b> Thursday, June 03, 2010 1:26 AM<br>
<b>To:</b> support@win-test.com<br>
<b>Subject:</b> Re: [WT-support] Feature request: PARTNER WINDOW<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Using multiple transmitters in
an "octopus" arrangement while competing as Multi-Single would be
against the spirit of the new WPX Rules. This is clearly spelled out in
this blog entry by WPX contest director K5ZD. Please read it all:<br>
<br>
<a href="http://www.cqwpx.com/blog/?m=200912">http://www.cqwpx.com/blog/?m=200912</a><br>
<br>
The new MS rules are clearly designed to <i>discourage</i> the use of an
octopus in the multi-single category. Such stations are encouraged to
enter as Multi-Two or Multi-Multi.<br>
<br>
I don't think Win-Test should make any enhancements that would encourage
further violation of the spirit of the rules, such as the enhancements
described below, at least not for WPX.<br>
<br>
73,<br>
Bob, N6TV<o:p></o:p></p>
<div>
<p class=MsoNormal>On Wed, Jun 2, 2010 at 1:24 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>I have been trying to solve the communication problems in
Multi Op between ops. Especially hard it is now in WPX MS where only one signal
is allowed at a time and one serial number sequence. Well, you might say 5
stations in that category is a bit overdone but that is what it takes to
compete with E7DX and RU1A:)<br>
<br>
So the problem is that while S&P stations have TX priority over RUN (they
need to be able to cut CQ message) they don't always know when RUN is TXing and
what it is sending. That makes the work unefficient.<br>
<br>
PARNTER window shows content of callsign field, that is good. Is it possible to
upgrade PARTNER window to show:<br>
<br>
- content of the EXCHANGE RECEIVED window<br>
- TX/RX status (I know you don't know abt footswitch, let's talk about button
generated TX only)<br>
- BUTTON THAT ACTIVATED MESSAGE BEING SENT (this is most important. When F1 is
shown - CQ, when INSERT or F2 is show - EXCHANGE)<br>
<br>
Another thing:<br>
<br>
It is possible to have more than 1 RUN station (for example in M/2 or M/S with
alternate CQ). Now the Support stations are displaying only one RUN station
window. This is VERY bad because the two RUN stations conflict and PARTNER
window is not correct.<br>
<br>
What we need is two more options under Real time-><br>
<br>
1. As Runner send to 1st, 2nd or 3rd slot<br>
2. As Support display 1, 2 or 3 slots<br>
<br>
Can you comment please! This would really take the communication and efficiency
of multi op work to a new level.<br>
<br>
73<br>
Es5tv<br>
<br>
p.s. when can we expect the new WRCT release? Restoring the ITU.DTB is very
important! We really need some time to test it as well..<o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>