开云体育

Tom; Not one |>| failed session marked in ur attachment. If u indeed tried the Abort and the P2P connections that proves my claim. De DoC Sent: Saturday, January 12, 2019 14:42 To:

Tom et al; I am not ranting. I am reacting to the apparent indifference to this issue by the WDT.I think most Gateway sysops do care about the number of failed connections, contrary to your claim in

Meant to include this showing the data parsed with ADIF Master Tom N5TW Sent: Saturday, January 12, 2019 8:42 AM To: '[email protected]' <[email protected]> Subject: RE: [w1eo] New file

Doc, It is a wonder with the previous and now this accusatory and frankly paranoid rants that I can get Phil to care about your program at all. I for one have spent some hours looking into this

Wow! In a single public email, you have all but accused the author of intentional stonewalling, fraud, and inability to conduct proper code development. Is this really where you want to go with

Tom; Like the cartoon vulture said, “patience hell, I’m going to kill something”. I have the distinct sense that Phil is stonewalling the repair of this incorrect log processing for

Now here is one that terminated with a “FQ” but did not create a ‘Connection Summary’ and consequently no log entry. It is hard for me to believe that the code change that caused this is so

I have neglected to mention that most if not all adi log entries for incomplete sessions had “>” for the termination byte and the ‘connection summary’ also showed the last commend as “>”

Hope that helps Tom. This is really being drawn out considerably. de DoC Sent: Monday, January 07, 2019 21:11 To: [email protected] Subject: Re: [w1eo] New file uploaded to [email protected] Okay –

Okay – sent along. Thanks! Tom Sent: Monday, January 7, 2019 2:42 PM To: [email protected] Subject: Re: [w1eo] New file uploaded to [email protected] Tom, some fodder. First two snapshots of

Tom, some fodder. First two snapshots of the Trimode panel. First is a real (not test) incomplete connection from K1RMC at 19:57:14. Second is a complete connection from my cross desk test client,

I’m sure he will take it with higher belief if u have been able to duplicate my findings Tom. Please try!! Sent: Monday, January 07, 2019 20:08 To: [email protected] Subject: Re: [w1eo] New file

No. Next step for me is seeing what Phil makes of it. I have sent him your earlier detailed note with some more annotations added. Tom Sent: Monday, January 7, 2019 1:49 PM To:

Is there any way we both could re-activate 1.3.20.0 so we could all see what used to happen during/after an incomplete session? My update was an overwrite so I no longer have a copy of 1.3.20.0

I’m reluctant to allow an update until we lick this one Tom. Unless there is some indication that it too got fixed. So have u tried my suggested tests? Sent: Monday, January 07, 2019 19:36 To:

BTW, the revision history file indicates that 1.3.21.0 was released on December 14th. I updated a few (2?) days later so the log snippet I sent would reflect the later day change over. I am reluctant

I’m sorry – I misunderstood about what you were stopping. Agree stopping a client is a legit test. And yes, looks like one of my Trimode instances updated to .22 Tom Sent: Monday,

I am stopping an across-the-desk client by clicking its abort button. The client call sign is not the same as my Gateway so I don’t see how that would be different from any other client aborting

From what Colin said, I’m not so sure this really started with version 1.3.21.0. And I’m not sure how things should be logged that you stop yourself… I will pass along what you have sent

Tom; I think I have done exactly that already. Snapshots of Trimode panel and snapshots of adi log files, including my most recent where Trimode version changed. I really don’t know what else I can