Outpost Packet Message Manager, v2.1.0, 26-September-2006 Copyright (c) 2003 - 2006 Jim Oberhofer KN6PE 1. Introduction 2. The sample TncInfo.dat file 3. The sample BbsInfo.dat file 1. INTRODUCTION ---------------------------------- This .zip file contains 3 files that have previously been part of the base distribution, but are now delivered as optional. This split in the distribution is two-fold: 1. Addresses a request for users that have existing TNC and BBS config files. They do not have to re-enter all the configurations that are previously set up. 2. Prepares for a future Outpost release where configuration migration will be automatic from release to release. There are 3 files that are currently 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 chabnges 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 Com1. 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 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 at 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 chabnges 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. The primary setting you need to make is setting up the BBS Prompt. In this case, the BBS prompt as displayed by WA6ZTY is "Help>". Note, there is NO space between "Help" and the ">" character. This is critical since Outpost is looking for this exact string to know when it can proceed with sending another command. W6XSC-1 (running a modified AA4RE BBS). Similar to the above description, this version was a custom modification (as best as I can tell) for the Santa Clara County RACES org. The key difference is that it prompts for a tactical call, then uses that tac call for all interaction with the BBS (see the BBS Prompts Tab). Unless you have this version of the BBS, DO NOT CHECK THE "TACTICAL CALL REQUIRED" BOX. the BBS prompt is the same as above... "Help>". KN6PE-1 (running the KPC-3 PBBS). This PBBS is in my garage and also works well with Outpost. All default settings work as is, and the only setting you need to make is the BBS Prompt... "Help >". NOTE: Unlike the AA4RE BBS, this prompt has a space between the word "Help" and the ">" character. AA6WK-2 (running the KPC-3 PBBS). This is similar to the above example, but Skip AA6WK's PBBS is accessable through a KA-NODE between me and his station. On the Path Tab, the KA-NODE/NET ROM 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... again, not user-editable. K6FB-2 (running the KPC-3 PBBS). This is similar to the above example, but is accessable throufh 2 digipeater stations. On the Path Tab, observe that the "Via difipsater(s)" button is checked, and 2 digipeaters are configured. NOTE ON ALL OF THE ABOVE 1. The above configurations work in my environment, and are set up for 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 Emergency Coordinator Cupertino ARES/RACES Cupertino, CA --------------- Readme.txt; v2.1.0, 26-Sep-06 Readme.txt; v2.0.4, 03-Feb-06 Readme.txt; v2.0.2, 20-Aug-05 Readme.txt; v2.0.0, 18-Jun-05 Readme.txt; v1.3.4, 03-Jan-05 Readme.txt; v1.3.3, 29-Dec-04 Readme.txt; v1.3.1, 20-Dec-04 Readme.txt; v1.3.0, 17-Dec-04 Readme.txt; v1.2.7, 10-Oct-04 Readme.txt; v1.2.1, 04-Sep-04 Readme.txt; v1.2.0, 22-May-04 Readme.txt; v1.1.4, 20-Apr-04 Readme.txt; v1.1.2, 3-Apr-04 Readme.txt; v1.1.1, 14-Mar-04 Readme.txt; v1.1.0, 27-Feb-04 Readme.txt; v1.0.3, 09-Nov-03 Readme.txt; v1.0.2, 23-Oct-03 Readme.txt; v1.0.1, 19-Oct-03 Readme.txt; v096.2, 23-Jul-03 Readme.txt; v096.1, 01-Jul-03 Readme.txt; v095.2, 28-May-03