<html><body><div dir="auto">Hi René, </div><div dir="auto"><br></div><div dir="auto">Keith's case is with HamClock users exclusively.</div><div dir="auto"><br></div><div dir="auto">I have updated more than 7 nodes, and I have not noticed any connection problems or user downloads.<br></div><div dir="auto"><br></div><div dir="auto">Kin EA3CV</div><div id="ms-outlook-mobile-signature" dir="auto"><div><br></div><br></div><div id="mail-editor-reference-message-container" dir="auto"><br><hr style="display:inline-block;width:98%"><div id="divRplyFwdMsg" style="font-size: 11pt;"><strong>De:</strong> Rene Olsen <rene@rcolsen.dk><br><strong>Enviado:</strong> sábado, septiembre 21, 2024 5:25:09 a. m.<br><strong>Para:</strong> The DXSpider Support list <dxspider-support@tobit.co.uk><br><strong>CC:</strong> Kin <ea3cv@cronux.net><br><strong>Asunto:</strong> Re: [Dxspider-support] New mojo version<br></div><br>Hi.<br><br>Still waiting for a replay as to why G6NHU-2 lost like 75% of his users before I do anything with <br>the new version.<br><br>So, will at least wait until next week. Like W1NR, I never update just before or during a <br>weekend.<br><br>Vy 73 de René / OZ1LQH<br><br>On 20 Sep 2024 at 17:44, Kin via Dxspider-support wrote:<br><br>> Hi,<br>> <br>> The new build is working very well for me.<br>> Only 60 out of 318 dxspider have been updated.<br>> Cheer up, it's been in testing for a while and it's stable.<br>> <br>> 73 de Kin EA3CV<br>> <br>> <br>> De: Dxspider-support <dxspider-support-bounces@tobit.co.uk> En nombre de Dirk Koopman via Dxspider-support<br>> Enviado el: jueves, 19 de septiembre de 2024 15:24<br>> Para: Dxspider-Support <dxspider-support@dxcluster.org><br>> CC: Dirk Koopman <djk@tobit.co.uk><br>> Asunto: [Dxspider-support] New mojo version<br>> <br>> There is a new mojo version which has been under test by a few brave sysops and they have determined that it is stable. Please look at the Changes file for the list of issues dealt with.<br>> <br>> One of the issues that has become apparent is the random lock status (historically) granted to new nodes that appear on the network. For some reason they defaulting to "unlocked". I don't understand why this has suddenly become a problem AGAIN, but it does seem to affect longer running nodes more than newer ones. <br>> <br>> This release is an attempt to fix this. It will lock all nodes that are not specifically unlocked via explicit unset/lock or set/spider type commands. Unfortunately, previous attempts to deal with this may have got this all confused and it *MAY* (and I stress this) mean that a (very) few of your older node partners *MIGHT* get locked out. If this happens then simply unset/lock or set/spider any of these nodes manually.<br>> <br>> There is new spot deduping code which seems to reduce the number of dupes, but since I have not been able to reproduce this further than making sure that nodes that issue multiple dupe spots with the same sequence number don't cause dupes.<br>> <br>> 73 Dirk G1TLH <br>> <br><br><br><br><br></div></body></html>