<html><head></head><body><div>
<div id="compose-body-wrapper" dir="auto"><div dir="auto"><br/></div><div dir="auto"><br/></div><div dir="auto" id="tmjah_g_1299"><span> <b>EA1DR & KL1DX </b> <br/><br/> Óscar Luis <br/><br/>oscarea1dr@gmail.com <br/><br/> <b> 73`s ✓ DX</b></span></div><br/></div><div class="replyHeader" dir="auto">En 4 de julio de 2026, en 10:40, Laurent HAAS - F6FVY <<a href="mailto:support@win-test.com">support@win-test.com</a>> escribió:<br/></div><br/><br/><div><blockquote type="cite" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hi</div><div><br/></div><div>Like every year, Win-Test 4.59.0-HQ is available here :</div><div><br/></div><div>https://download.win-test.com/v4/hq/wt-4.59.0-HQ.exe</div><div><br/></div><div>This special FREE version, reserved for the HQ teams, does not require any registration.</div><div><br/></div><div>To prevent confusion with your current Win-Test setup, especially for operators who bring their laptops to a remote QTH, the exe is named wt-hq.exe, and the associated ini file is wt_hq.ini. You can copy the content of your current wt.ini to wt_hq.ini to keep the same configuration settings.</div><div><br/></div><div>This version is compatible with the official 4.59.0, so you can mix them together on LAN and on WAN.</div><div><br/></div><div>You must use wtTunnel (client) version 1.18.0 available here :</div><div><br/></div><div>https://download.win-test.com/utils/wtTunnel-1.18.0.zip</div><div><br/></div><div>The tunnel server hasn't changed :</div><div><br/></div><div>https://www.win-test.com/hq05/tunnel/server/ (chose your flavor)</div><div><br/></div><div>Usual reminders :</div><div><br/></div><div>- One (and only one) wtTunnel (client) per LAN.</div><div>- To enable sync on the WAN, one WT must be set as BridgeHead in each LAN (Options / Interfaces / Network advanced settings). CAUTION : One bridgehead per LAN. As this log is used to sync LAN and WAN, I suggest to use a fast PC, and not assign it to a RUN position.</div><div>- The wtDxTelnet frames (packet cluster) are not forwarded on the tunnel. So, use one separate wtDxTelnet per LAN.</div><div><br/></div><div>Good luck !</div><div><br/></div><div>73</div><div><br/></div><div>Larry - F6FVY</div><div><br/></div><div>-- </div><div>support mailing list</div><div>support@win-test.com</div><div>https://lists.win-test.com/cgi-bin/mailman/listinfo/support</div></blockquote></div>
</div></body></html>