[Ares-races] (no subject)

[Rockingham Computer]

I just thought I would make a couple points with respect to
the on-going discussion of operating systems and packet radio
and their us with respect to ARES.

Operating packet really has some other implications from 
what I see in these messages, and operating systems really
come into play as you need to perform "higher" functions.

1) Running a digi.
------------------
  I consider this a low level function.

  In most cases this does not require any operating system.  The
software is integrated / included in the TNC (granted there may be
setup or there might be some TNC's where the software is actually in a
host PC), but for the most part I believe they can run all by
themselves.

  (See BBS's for built in mailboxes).


2) Minimal setup.
-----------------
   I consider this a low level function.

   What is needed for a minimal setup is a "Terminal".  You can make a
direct connection to another station or connections to a BBS (Bulletin
Board System).  Type your messages to the other end, to the BBS system
or read your messages from the BBS system.  Traffic can be transfered
to written logs or sometimes printed as it comes in.


3) Better Setup.  
---------------- 
   I consider this to have components of both low and high level functions.

   A terminal program and a PC to run it on.  This allows you to turn
a computer into a terminal (and if you use a windowing operating
system, you can do things in other windows).  I have used several DOS
programs, Window's programs and on unix "tip" windows.

   It is usually best to have a terminal program the can
"log" all traffic you send/recv into a file.  This might
include capturing a list to a separate file.

   Where the operating system often comes into play is
often really using an editor to prepare lists and/or 
print them.  Unix can be difficult in this case if you
are not familiar with unix editors like vi or emacs.
The print commands and syntax can be "not obvious" to
most people.

   With respect to training, this can represent a challenge
from some people.  It should also be noted that you might
wish to make use of volunteers (for example at a shelter) to
help with data entry and transmission.  I consider this to
require an expert operator to be near by, but not necessarily
doing all the typing.


4) BBS systems.
---------------
   I consider this to be either a low level or high level function
   depending on which approach is used.

   Many TNC's come with built in mailboxes.  I consider these
low level functions because they don't usually require another
computer to be use.

   Other BBS's on the other had run on computer equipment.  I consider
these systems to be high level and is probably where the operating
system reliability comes into play.  If you are running a BBS chances
are it was designed to run on as an application under some operating
system.  You pretty much need to keep it online for extended periods
of time.

   Aside from acting as a message handler, it can also keep
track of the traffic and manny bulletin boards also have chat
type functions that would allow multiple people to round table
while using the connected protocol to ensure message integrity.

5) APRS
-------
   I consider this a high level funciton.

   I have my concerns about the message passing in this environment.
However it is a great system for position reporting.  For specific
types of emergencies this is a very valuable tool.

NOTE:
   I suspect that this tool will change in the very near future.
Hams have done some very nice ground breaking in terms of demonstrating
how position reporting is key to a great deal of communications.  The
next step here is upon us.  I am making reference to garmin's latest
product announcement that integrates the radio/gps/position reporting
screen into one product.  I see a bright future for products similar
to the rhino (in telephones, public safety and amateur equipment.  It
is the integration that makes it truely useful.

/Jim /N1CRZ