<html>
<body>
At 09:53 AM 6/5/2006, you wrote:<br>
<blockquote type=cite class=cite cite="">Just to clarify, any digi that
can support WIDEn-N automatically<br>
also supports W1-1. That was part of the beauty of the<br>
WIDE1-1,WIDE2-1 recommended path under the New-N.<br><br>
It works everywhere that WIDEn-N always works, but adds<br>
the ability to use fill-in-WIDE1-1-only digipeaters. The only<br>
digis that cannot support WIDE1-1 are the old one-hop-only<br>
fill-in diigs that used to only support RELAY as the alias. <br><br>
Yes, those are supposed to change to support only WIDE1-1<br>
from now on. Looking at KE4CJA-4 on FINDU indicates<br>
that it is already a WIDEn-N digi, although it is clear that<br>
it has not taken advantage of all the other advantages of<br>
the New-N Paradigm settings.<br><br>
Hope that helps<br>
Bob, WB4APR</blockquote>
<x-sigsep><p></x-sigsep>
They may support it, but if it is a KPC 3 with 8.2, it will not support
it correctly(unless you put WIDE1-1 in the UID field). It will digi the
WIDE1-1 and decrement it to WIDE1, which no one else will digi,
effectively cutting you off from being digi'd again.<br>
<tt>
==/===/===/===/===/===/===/===/===/===/===/===/===/===/===/===/===/<br>
Mike
Heskett<x-tab> </x-tab>email<x-tab>
</x-tab>
<a href="/ym/Compose?To=mheskett@mindspring.htm">
mheskett@mindspring.com</a><br>
WB5QLD<x-tab> </x-tab>WWW<x-tab>
</x-tab>
<a href="http://mheskett.home.mindspring.com/">
http://mheskett.home.mindspring.com/</a><br>
Hurst, TX<br>
O-<br><br>
</body>
</html>