Important configuration changes and differences between the
last cutting edge version from the projects/nosaprs webpage,
and this latest version that ships with JNOS 2.0

* If you are running JNOS 2.0 already, then you can apply the
  patch without any problem.

* If you are NOT running JNOS 2.0, but an older version of JNOS
  with the original NOSaprs update kits, you can apply this patch,
  BUT ONLY IF you are already at the last cutting edge version
  from the original projects/nosaprs webpage.

 -----------------------------------------------------------------

1) This is now version 'NOSaprs 2.0', or version 'NOSaprs C-2.0'
   for the client only version.

2) The APRS Destination call is now 'APZ200', not 'APZ116' as was
   the previous version. If you have any 'ax25 route' entries for
   this destination call, make sure you change them !

3) The 'aprs logon' command has been changed !

   Before it was just :

     aprs logon ve4klm-10

   Forget the above, it is now as follows :

     aprs logon call ve4klm-10
     # Winnipeg is at Lat 49d54m, Long -97d7m
     # uncomment the following if you want a filter setup
     aprs logon filter r/50/-97/300

   In this particular autoexec.nos example, I have added a JavaAPRS filter
   feature that restricts the traffic I receive to stations within 300 km of
   the specified Lat/Long. Greatly reduces the data I get (firehose) from
   the APRS internet system.

   If you want to use the filter, you of course need to connect to a server
   that can handle it, so for example :

      aprs server add 134.173.254.38 14580

That's all for now.

Maiko Langelaar / VE4KLM
Dated : March 7, 2005