<p dir="ltr">OK. Note that there is a time shifting option in the Tools menu that you can try to use to fix each log, them try merging again.</p>
<p dir="ltr">73,<br>
Bob, N6TV</p>
<div class="gmail_quote">On Dec 1, 2015 7:34 PM, "Chris Plumblee" <<a href="mailto:chris.plumblee@gmail.com">chris.plumblee@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi Bob,<br><br></div>I think we had some time differences on the computers, which probably explains the dupes. <br><br></div>Dates were correct. I think there is an option to make one station the master and distribute its time across the network, and it's possible that I neglected to check that box. We had a power supply failure on the computer I was planning to use to distribute packet spots and handle the time synch shortly before the contest, and in the rush to set up an alternate computer, then get WTDXTelnet configured on the second best computer, I may have neglected to check that box. <br><br></div>Oh well, I learn something new every day.<br><br></div>Chris WF3C<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 1, 2015 at 8:08 PM, Bob Wilson, N6TV <span dir="ltr"><<a href="mailto:n6tv@arrl.net" target="_blank">n6tv@arrl.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">There have been two revisions to the Win-Test network protocol, one in WT 4.17 and another in WT 4.19. It's possible something doesn't work as well as it used to.<div><br></div><div>Using 4.19 at K3LR, with 11 logging computers and some spares, I saw one (and only) QSO that didn't seem to propagate around the network properly.</div><div><br></div><div>File | Merge should work fine, you shouldn't end up with 23000 dupes unless some computer wasn't set to the proper time.</div><div><br></div><div>I suggest writing a Cabrillo file for each log and examine the timestamps, especially the date.</div><div class="gmail_extra"><br clear="all"><div><div>73,<div>Bob, N6TV</div></div></div><div><div>
<br><div class="gmail_quote">On Tue, Dec 1, 2015 at 7:47 AM, Chris Plumblee <span dir="ltr"><<a href="mailto:chris.plumblee@gmail.com" target="_blank">chris.plumblee@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I cannot answer why it happened, but I can confirm we had the same problem running 4.19 at N4WW on six computers, none connected wirelessly. <div><br></div><div>We had three XP computers and three Win7 computers. Two XP computers agreed exactly, the third was slightly higher. The three Win7 machines ranged from the lowest to the highest final score. </div><div><br></div><div>I tried to merge the logs last night and ended up with a bunch of dupes (30000 QSOs total, < 7000 non-dupes). I opted to submit the largest log as-is in the absence of better options. </div><div><br></div><div>When we used 4.15 on the same computers for ARRL DX CW in February all six totals agreed exactly at the end of the contest. </div><div><br></div><div>73, Chris WF3C <div><div><span></span><br><br>On Tuesday, December 1, 2015, Steve HA0DU <<a href="mailto:ha0du@dx.hu" target="_blank">ha0du@dx.hu</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear WinTesters,<br>
<br>
During the recent CQWW CW test we experienced that some of the computers had different QSO numbers than others. Our system consists of six computers, of which, five are connected to a hub, and a sixth one is connected via WiFi. We can imagine the WiFi machine has connectivity problems because of the RF power radiated over the place, but the other five are connected by wires, still the five machines sometimes had four different bottom lines...<br>
Now this is not a problem most of the time, but when it comes to the number of band changes, it can be a serious problem!!!<br>
<br>
Of course sychronization is enabled.<br>
<br>
Could someone give us an idea what can be the reason?<br>
<br>
73 Steve HA0DU<br>
<br>
<br>
---<br>
Ezt az e-mailt az Avast víruskereső szoftver átvizsgálta.<br>
<a href="http://www.avast.com" target="_blank">http://www.avast.com</a><br>
<br>
_______________________________________________<br>
Support mailing list<br>
<a>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>
</blockquote></div></div></div><span><font color="#888888"><br><br>-- <br>Chris Plumblee<br><a href="tel:407.494.5155" value="+14074945155" target="_blank">407.494.5155</a><br>
</font></span><br>_______________________________________________<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" rel="noreferrer" target="_blank">http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
<br></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<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" rel="noreferrer" target="_blank">http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div>Chris Plumblee<br><a href="tel:407.494.5155" value="+14074945155" target="_blank">407.494.5155</a></div>
</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" rel="noreferrer" target="_blank">http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
<br></blockquote></div>