¿ªÔÆÌåÓýThat is really unbelievable Tom. Several other sysops have noticed and
reported it happening. As I suggested in my original message on this thread, the
sysop can cause a message to fail or be incomplete by either clicking the abort
button during the early stages of an across-the-table connection or by selecting
a P2P mode while doing the same. Alternatively, he can have a client do that for
him. Then watch the Trimode panel and u will see no ¡®connection summary¡¯ line
and there will be no entry in the log. If u r running a Gateway, please try that
urself.
Other sysops reading this thread, please chime in
with ur observations.
de DoC
? From: Tom Whiteside
Sent: Sunday, January 06, 2019 21:04
Subject: Re: [w1eo] New file uploaded to
[email protected] ?
Phil says he has never even looked at the code that generates the .adi files ¨C so no changes to Trimode we are aware of.??? ? Tom N5TW ? From: [email protected]
[mailto:[email protected]] On Behalf Of DoC ? Most of the failed/incomplete record log entries are missing Tom. Lately a few of the apparently complete connections do not result in a ¡®connection summary¡¯ line in the Trimode panel and no record adi log entries. These changes/errors were introduced with update to version 1.3.21.0! I have passed this information on to Phil and the WDT but have not received any response. Very frustrating. See my original message in this thread. I hope u can help get us back to version 1.3.20.0 logging. Thanks in advance for anything u can do de DoC, W1EO ? From: [email protected] [mailto:[email protected]] On Behalf Of Tom
Whiteside ? Is it just the failed or incomplete contacts that you see missing??? I will get the information to W4PHS but want to describe it as completely as possible. ? Tom N5TW ? From: [email protected] [mailto:[email protected]] On Behalf Of
DoC ? Any suggestions as to what to do about RMS Analyzer? It is no
longer very informative when Trimode adi logs are missing important information.
It seems futile to make any further updates now. .I do hope these WDT actions
are not intentional. Eliminating the log records for failed/incomplete
connections to make the Winlink network performance appear better than it really
is seems to border on being fraudulent. ? |