[wt4hq] Logsync issues; plan for this year?

[Mario Lorenz]

Dear Larry, dear all,

since planing for this year's HQ starts up, I am getting serious
questions what we are going to about this year's logging software setup.
For the xth year in a row, the log synchronization situation here is
a major disaster, as has been discussed last year after the contest.

Except last year you also stated you were able to finally reproduce some
of those issues at TM0HQ.

Some internal tests done by members of our team which consisted of
running logsync on local (same LAN) networks of multiple computers,
adding computers with clean logs, or adding computers that have been
disconnected for a while, also resulted in the logs not synchronizing
to equal QSO counts, with several dozen QSOs missing even after giving 
it several hours to synchronize.

So I would like to ask if

- you have any definite plans on how/when to fix this issue?
- you need help (anything; just ask...)

Specific question: I wonder if you have any reports at all that somebody
still uses the serial ports for networking (COM), in particular whether
this has been tested recently, and if there are any topology constraints
(loop vs. star vs. mesh) exist. I have a strong suspicion that Windows,
the firewall, or the network, does not cope too well with the
"broadcast-storm" style Win-Test traffic and several important packets
may get lost. So I am toying with the idea of setting up some
Win-Test nodes to network via COM ports, which would actually be virtual
com ports with a TCP (and hence reliable, flow-controlled) connection?


Best 73s,

Mario


-- 
Mario Lorenz                            Internet:    <ml at vdazone.org>
                                        Ham Radio:   DL5MLO at DB0ERF.#THR.DEU.EU