<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>I'm sure I was not.</div><div><br></div><div>The only thing I can think of is that it happened right around the time that I switched my link with N6ZX from AXUDP on W2XSC to AX.25/RF on W4XSC. The hang occurred on W2XSC. </div><div><br></div><div>I can't say for sure when it happened and I can't imagine how that would affect anything. But restarting JNOS solved the problem.</div><div><br></div><div>Michael</div><div><br></div><div><br></div><div><br></div><div><br></div><div><div style="font-size:9px;color:#575757">Sent from my Verizon Wireless 4G LTE smartphone</div></div><br><br>-------- Original message --------<br>From: Wm Lewis <thunderft@hotmail.com> <br>Date:03/23/2014 11:47 PM (GMT-08:00) <br>To: TAPR xNOS Mailing List <nos-bbs@tapr.org> <br>Subject: Re: [nos-bbs] Message log jam <br><br><div dir="ltr">Michael:<br>
<br>
I need to you to rack your brain on this.....<br>
<br>
When you had your log jam, were you experimenting with 'TCP ACCESS' at the time ???<br>
<br>
I think I just found the source of my jam.....<br>
<br>
.... more to follow.....<br>
<br>
Bill<br>
KG6BAJ<br> <br>
<div>> From: n6mef@mefox.org<br>> To: nos-bbs@tapr.org<br>> Date: Fri, 21 Mar 2014 15:05:43 -0700<br>> Subject: Re: [nos-bbs] Message log jam<br>> <br>> Good to know, but I don't think this was my situation.<br></div> </div>
</body>