[WT-support] keying delay

[José Nunes CT1BOH]

I think Win-Test default is "incoming spots loggin" - ON
Perhaps WT default should be off??

José Nunes
CT1BOH

On Wed, Dec 3, 2014 at 9:06 PM, Bob Wilson, N6TV <n6tv at arrl.net> wrote:

> Steef,
>
> 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.
>
> Stream logging may be the root cause of the all keying delays (WinKey) or
> CW Stutter (COM port DTR keying) that you see.  *Please disable Stream
> Logging* in the Alt-O window, and *disable Incoming spots logging *in the
> Alt-A window, and repeat your test.  Does the CW still stutter?
>
> 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).
>
> In sum, disabling all spots logging may resolve all the delay / stutter
> problems.  Please test and report.
>
> 73,
> Bob, N6TV
>
> On Wed, Dec 3, 2014 at 5:13 AM, Steef PA2A <pa2a at xs4all.nl> wrote:
>
>>  Don,
>>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> 73s Steef PA2A
>>
>> ----- Original Message -----
>> *From:* Don Beattie <g3ozf at btinternet.com>
>> *To:* support at win-test.com
>> *Sent:* Tuesday, December 02, 2014 11:51 AM
>> *Subject:* [WT-support] KEYING DELAY
>>
>>  In CQWW CW this weekend at G5W we were using new computers, which did
>> not have LPT ports (:-(
>>
>>
>>
>> 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.
>>
>>
>>
>> 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.
>>
>>
>>
>> Any ideas ?
>>
>>
>>
>> *Don, G3BJ*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>>
>>
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>>
>>
>
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
>


-- 
José Nunes
CONTEST CT1BOH - http://www.qsl.net/ct1boh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20141204/1f5951e3/attachment.html>