<div dir="ltr">Steef,<div><br></div><div>Is packet "Stream Logging" enabled? Right click on the Alt-O window to see if that option is enabled (checked). If so, it means every single byte of incoming RBN traffic is being written to disk, which causes a huge amount of I/O overhead. Opening a browser at the same time will slow down this disk I/O even more. Uncheck it.</div><div><br></div><div>Stream logging may be the root cause of the all keying delays (WinKey) or CW Stutter (COM port DTR keying) that you see. <b>Please disable Stream Logging</b> in the Alt-O window, and <b>disable Incoming spots logging </b>in the Alt-A window, and repeat your test. Does the CW still stutter?</div><div><br></div><div>Take a look in your /log directory. Chances are high you will see a huge .pkt file there, probably tens of megabytes. There is also a separate incoming spots log (.dxc file) written disk (from the Alt-A window).</div><div><br></div><div>In sum, disabling all spots logging may resolve all the delay / stutter problems. Please test and report.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature">73,<div>Bob, N6TV</div></div></div>
<br><div class="gmail_quote">On Wed, Dec 3, 2014 at 5:13 AM, Steef PA2A <span dir="ltr"><<a href="mailto:pa2a@xs4all.nl" target="_blank">pa2a@xs4all.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div lang="EN-GB" link="blue" bgcolor="#ffffff" vlink="purple">
<div><font face="Arial">Don,</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">At PI4CC we had the same problem while the cluster
window was streaming the unreadable combined skimmer clusters. Closing it down
by ALT-O solved the problem. The ALT-O window has a 65000 lines buffer, a heavy
duty for WT to fill and empty the buffer.</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">Looking for missing zone KL7 by ALT-T I
sent about 10 times per second "sh/dx KL7 on 15m" by putting in an
ALT-T macro. The unreadable cluster screen stopped for a while and then all KL7
spots had scrolled by without being able to read them. While this
happened the CW got hung up for a few seconds.</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">We use the good old COM1 ports for CW so the amount
of telnet traffic seems to cause the problem. Opening an Internet Explorer
screen also influences the CW. Maybe we should buy faster video cards! I
wonder if XP users had the same problem while we have recently gone to
W7.</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">73s Steef PA2A</font></div>
<blockquote style="BORDER-LEFT:#000000 2px solid;PADDING-LEFT:5px;PADDING-RIGHT:0px;MARGIN-LEFT:5px;MARGIN-RIGHT:0px">
<div style="FONT:10pt arial">----- Original Message ----- </div>
<div style="FONT:10pt arial;BACKGROUND:#e4e4e4"><b>From:</b>
<a title="g3ozf@btinternet.com" href="mailto:g3ozf@btinternet.com" target="_blank">Don
Beattie</a> </div>
<div style="FONT:10pt arial"><b>To:</b> <a title="support@win-test.com" href="mailto:support@win-test.com" target="_blank">support@win-test.com</a> </div>
<div style="FONT:10pt arial"><b>Sent:</b> Tuesday, December 02, 2014 11:51
AM</div>
<div style="FONT:10pt arial"><b>Subject:</b> [WT-support] KEYING DELAY</div>
<div><br></div>
<div>
<p class="MsoNormal">In CQWW CW this weekend at G5W we were using new computers,
which did not have LPT ports (:-(<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">So we had to use USB control of Microham and EZMaster on
the two stations. We experienced random delay in the CW starting when pressing
a function key. As far as I can see, everything is properly installed. Is this
a known problem with USB control of Microham and EZM (yes I know that is an
old product) and if so, what is the fix. This never happened with LPT
keying.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I did wonder whether it was the load of running TelNet with
high spot volume that was causing the problem, but the computers are fast,
with lots of memory.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Any ideas ? <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b><span>Don,
G3BJ<u></u><u></u></span></b></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p></div>
<p>
</p><hr>
<p></p>_______________________________________________<br>Support mailing
list<br><a href="mailto:support@win-test.com" target="_blank">support@win-test.com</a><br><a href="http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br><p></p></blockquote></div>
<br>_______________________________________________<br>
Support mailing list<br>
<a href="mailto:support@win-test.com">support@win-test.com</a><br>
<a href="http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
<br></blockquote></div><br></div></div>