	Outpost Packet Message Manager, v2.2.0, 6-April-2007
	    Copyright (c) 2003 - 2007 Jim Oberhofer KN6PE


1. Introduction
2. The sample TncInfo.dat file
3. The sample BbsInfo.dat file


----------------------------------
1.  INTRODUCTION
----------------------------------
This .zip file has been updated to support v2.2.  This file is not 
compatable with any previous version of Outpost.

This .zip file contains 3 files that are now delivered as optional.  
This reason for this file is two-fold:

  1. Allows users that have existing TNC and BBS config file. They
     do not have to re-enter all the configurations that are previously
     set up.
  2. Offers new users the option of looking at some sample configurations
     to help them set up their own TNCs and BBSs. 


There are 3 files that are included.  This README file explains what you
will find and describes the examples that are presented.  The 3 files are:

  1. TncInfo.dat - contains sample device configuratrions
  2. BbsInfo.dat - sample BBS configuratrions
  3. aa6wk-2.pth - example of a KA-Node path file referenced by a BBS 


-------------------
2. TncInfo.dat file
-------------------
This file holds the configurations for serial devices (TNCs), AGWPE
setups, and telnet setups.  NOTE: you should never NEVER make changes
to this file through any means other than Outpost.  Editing this file
directly will corrupt it.

KPC3 - This is a KPC-3 TNC that is directly connected to the computer 
on Com-1.  This is typical configuration for a TNC.  If you have a TNC,
other than checking the Comm Port settings, all default settings will
work.

AGW-LOCAL - This is an AGWPE configuration where AGWPE is running on 
the local PC, and the device to which AGWPE is talking is also connected
to the local PC.  In this case, the device could either be a TNC (and
AGWPE supports many types), or it could be the local sound card.  When
you configure AGWPE (not from Outpost), you set up the device and assign
it a Radio Port.  In this instance, Radio Port = 1 and is associated with
the local TNC.  Your configuration may vary.

AGW-GARAGE - This is an AGWPE configuration where AGWPE is actually
running on a remote PC (in the garage) on my home network.  For this
example, I configured the remote AGWPE to require a logon and password 
to access it, and set up Outpost to issue the Logon and Password.
The Remote Host can either be the computer name (garage98d) or an IP
address (192.168.1.104, as assigned by my router).

TELNET - This is an example of a BBS on the internet (not on my home
network) that can be accessed by Telnet.  The BBS sysop needs to provide
the bulk of the information to you... internet name, Port, and your
logon and password.


-------------------
3. BbsInfo.dat file
-------------------
This file holds the configurations for a couple of different BBSs that 
are known to be out there.  NOTE: you should never NEVER make changes
to this file through any means other than Outpost.  Editing this file
directly will corrupt it.

WA6ZTY (runing the AA4RE BBS).  The AA4RE BBS package is a standard BBS 
that works well with Outpost.  In almost all cases, you should be able 
to check the BBS Type as "Let Outpost determine the BBS and set up the 
Prompts".  However, the AA4RE BBS does not self-identify.  Other than 
the connect name, the main setting you need to make is check the AA4RE 
BBS box.

W6XSC-1 (running a modified AA4RE BBS).  Similar to the above description,
this version contains a customization developed exclusively for Santa
Clara County CA RACES.  The key difference is that it prompts for a
tactical call, then uses the provided tactical call for all interaction 
with the BBS (see the BBS Prompts Tab).  If you are part of Santa Clara 
County RACES, set the BBS Type to "AA4RE BBS with Tactical Call 
Customization".  

KN6PE-1 (running the KPC-3 PBBS).  This PBBS is in my garage and 
also works well with Outpost.  Set the BBS Type to "Let Outpost 
determine the BBS and set up the Prompts".  All other default 
settings work as is.

AA6WK-2 (running the KPC-3 PBBS).  This is similar to the above
example, except Skip AA6WK's PBBS is accessable through a KA-NODE
between me and his station.  On the Path Tab, the KA-NODE/Netrom
Access button is checked.  By clicking on the "Create/Update Path" 
button, you will see that I get to the AA6WK-2 PBBS through the 
K6FB-7 node (a KPC3 KA-Node).  Multiple nodes can be added, and 
re-arranged as necessary.  The path information is stored in the 
AA6WK-2.pth file... also not directly user-editable.

K6FB-2 (running the KPC-3 PBBS).  This is similar to the above
example, but is accessable through 2 digipeater stations.  On
the Path Tab, observe that the "Via digipsater(s)" button is 
checked, and 2 digipeaters are entered.

-------------------------
NOTES ON ALL OF THE ABOVE
-------------------------
1.  The above configurations are shown as examples only.

2.  The description field is useful for providing information
on the BBS, such as the frequency, location, and anything 
else that may help when a different operator comes in for
a shift.


Best Regards,

Jim O  KN6PE
kn6pe@arrl.net
www.outpostpm.org
