<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.5730.11" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN
class=107034215-25102006><snip></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=107034215-25102006></SPAN></FONT>Actually, if WA4KJH-7 actually supported
Wn-N, you would see the KF4OWQ-2 London, KY digi, because when in the Cumberland
gap, I could hear both fine and I could bounce via both of them when using a
capatible path (WIDE1-1,TN on the London side, and TN,WIDE2-1 on the TN
side). It's good to hear about the new sites. <SPAN
class=107034215-25102006><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV><SPAN class=107034215-25102006><FONT face=Arial color=#0000ff
size=2><snip></FONT></SPAN></DIV>
<DIV><SPAN class=107034215-25102006></SPAN> </DIV>
<DIV><SPAN class=107034215-25102006><FONT face=Arial color=#0000ff
size=2>Huh? A plain "SS" alias like TN is obsolete too. I hope
you meant "WIDE1-1,TN1-1 on the London side and TN1-1,WIDE2-1 on the TN
side". But to be heard through both digis, why not simply use
the standard recommended mobile path of WIDE1-1,WIDE2-1 or the equivalent from
home or Base, plain WIDE2-2 for those two hops? </FONT></SPAN></DIV>
<DIV><SPAN class=107034215-25102006><FONT face=Arial color=#0000ff size=2>73,
Cap</FONT></SPAN></DIV></BODY></HTML>