<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1528" name=GENERATOR>
<STYLE>@font-face {
font-family: Wingdings;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2>Hello,</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>with
the old WT-Telnet v1.1 we(DF0CG/DR1A) have had the problem, too. After a few
hours the WT-Telnet program receives cluster-spots, but WT-commands(Alt-T)
doesn´t take effect at the cluster. </FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>My
solution:I cut the cluster-connection, closed the WT-Telnet program. 5 to
10 secondas later I started the WT-Telnet program again and everything works
well as known for 6h-max 24 hours.</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>The
german Telecom cuts every 24h our at 00:00 localtime the DSL-connection and
after that the WT-Telnet programm tries to reconnect the
DX-Cluster.</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>After
the reconnection we only can receive the spots, a lot of time and nothing
happend by sending commands to the cluster.</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>I had
tested 3 different DX-Clusters(PI4CC,DB0SUE,K1TTT), but on every cluster
the same problem.</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>The
station is only 1,5km away from the city of Goch, but for a DSL-connection it is
a far way to go to the gateway in the city. </FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>We
have a 2MBit-connection, but it is very very "thin". </FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>So I
thought that the cluster problem is caused by this slow/thin/bad
DSL-connection??!!??</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>With
the "new" WT-Telnet v2.0 this problem are blown away.....ok, in the CQWW-SSB we
got it one time, saturday morning...but WT-Telnet was started on october 21th in
WAG-Contest and running more than 150h. Reconnecting to cluster works well,
too.</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>From
July to October(CQWW) I had tested v2.0 in 5 or 6 contests (ca.500h) without any
problem....all the time everything works fine.</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>Sorry,
but now it will be madly:</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>From
January to Mai I tested a few times during contests second,third,...
cluster-connections from other PCs with the Windows-Telnet program. Sorry, not
in the last months....it was when using WT-Telnet v1.1</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2>Sometimes I got the same problem like in
WT-Telnet!!!!</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>But
why???</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>Could
it be based on windows-network-settings, outside of the Win-Test/WT-Telnet
program???</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>BTW,
we are running 15 PCs with W2k SP4, 192-256MB RAM, P2
350Mhz....</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>So,
I´m very happy that WT-Telnet v2.0 is running much better than
v1.1</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>Now I
known that I´m not alone....;-)</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2>Larry, is it possible to add a feature to the WT-Telnet
program. I think it could take a positive effect to the problem, when the
WT-Telnet program sends automatically(intervall 5-60min) a CR to the
DX-Cluster...a "keep alive" function to keep alive the cluster-connection in
both directions(TX & RX).</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2>Hw???</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff size=2>73 de
Thorsten - DO1ET</FONT></SPAN></DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=960150700-04112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Ursprüngliche Nachricht-----<BR><B>Von:</B>
support-bounces@win-test.com [mailto:support-bounces@win-test.com]<B>Im
Auftrag von </B>Dave Zeph<BR><B>Gesendet:</B> Donnerstag, 2. November 2006
19:41<BR><B>An:</B> support@win-test.com<BR><B>Betreff:</B> [WT-support]
Problem with wtDxTelnet V2.0<BR><BR></FONT></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Over the weekend, we had 13 PC’s
Networked at the K3LR Multi-Multi. For the first time we went through
the 48 hours without a crash, and all of the PC’s had identical QSO Totals and
Scores at the end. It was truly painless. All of the PC’s ran
Win-Test V3.5 and Windows-XP Professional. All of the op’s were very
familiar with CT, but most of them had only seen a screen shot of Win-Test
sent to them before the Contest. When someone who has never even seen
Win-Test before sits down and starts off with a 171-QSO hour, you’ve got to
congratulate Laurent and Olivier!<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The 160 Multiplier Position has no
associated radio equipment (at this time). However this PC is always
On-Line and serves as a “hot spare” which can be quickly substituted for any
of the other PC’s should one of them fail.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The 12 Band-Position PC’s are
built with ASUS A8N-VM Motherboards, AMD 64 4000+ CPU’s, 1Gb RAM, and a Turtle
Beach “Santa Cruz” Sound Card. We also have one additional 1Ghz
Pentium-III PC that serves as a Status Display of COUNTRIES and ZONES.
All 13 PC’s support 10/100 LAN. The PC’s and the Linksys RV042 Router
are connected using a 16-Port Linksys SD216 10/100
Switch.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">We ran both Win-Test V3.5.0, and
wtDxTelnet V2.0 on the 160 Multipler PC. The 160 Multiplier PC linked
our LAN to the N3RA AR-Cluster.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><B><FONT face=Arial size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">The problem we
experienced, repeatedly, was loosing the ability to SEND ANYTHING to the N3RA
Cluster. We always RECEIVED SPOTS / WWV / TALK, but consistently lost
the ability to SEND SPOTS, or run commands on the N3RA Cluster via the Packet
TALK Window. <o:p></o:p></SPAN></FONT></B></P>
<P class=MsoNormal><B><FONT face=Arial size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></B></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">This happened at random intervals
…. perhaps every couple of hours? It’s impossible to give an exact
interval because the problem would only be discovered when one of the op’s
tried to send a Spot and HAPPENED to note that it hadn’t been added to the
BandMap, or didn’t show up in the ALT-O display. Not everyone had the
Packet Window open or was looking for the
problem.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">When this happened, shutting down
and restarting Win-Test and wtDxTelnet on the 160 Multiplier PC didn’t seem to
restore the outbound communications. wtDxtelnet would reconnect to N3RA
correctly. However, commands entered via the Packet Talk window on any
PC on the LAN would NOT “show” on the wvDxTelnet Window – nor would they be
transmitted to the Cluster.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">All of the PC’s were set up with
two accounts – ADMINISTRATOR and CONTEST_USER. The CONTEST_USER account
is a Limited Account and was purposefully limited to preclude WEB Browsing and
other activities unrelated to the Contest. The ADMINISTRATOR Account has
a Password – the CONTEST_USER does not. The PC’s are configured to
automatically boot into the CONTEST_USER Account and load Win-Test. The
simplest way we found to reset the wtDxTelnet problem was to LOG-OFF
CONTEST_USER, and then immediately LOG-IN – restarting Win-Test - which was
set to automatically load wtDxTelnet.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">This was the only problem we
experienced – and we hope that the cause can be discovered and fixed before
the CQ WW CW Contest. Tim, K3LR will be detailing a list of features /
options we’d like added or changed – but this problem is one that is REALLY
important.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">73 -</SPAN></FONT><FONT
face=Wingdings size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Wingdings">à</SPAN></FONT><FONT
face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> Dave,
W9ZRX<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>