	Outpost Packet Message Manager, v2.1.2 FULL, 5-November-2006
   	       Copyright (c) 2003 - 2006 Jim Oberhofer KN6PE


1. Overview
2. Who should install v2.1.2
3. Installation Notes
4. Post-Installation changes
5. Creating Floppy Install Disks
6. What’s new in v2.1.2


1.  OVERVIEW
----------------------------------
The v2.1.2 release is an UPGRADE of all Outpost programs.  This release builds
on the v2.1 release of new features with Tactical Call Support, and KA-NODE/NETROM
support being some of the top two.

This release does not make any data file changes.  No message or configuration
migration from the v2.1 release is required.  

This Release Note only addresses the application installation.

See the details below on how to preserve your data.


2. WHO SHOULD INSTALL v2.1.2
----------------------------------
There are two packages posted to the website: 

1. An UPGRADE package is a full installation that requires you to ininstall 
the previous version of iutpost and perform a clean install of the new version.

2. An UPDATE package is intended for v2.1 users that updates only the main 
executable program only.  This is not a full installation and does not require
uninstalling the current versino of Outpost.

This upgrade consolidates the contents of the v2.1 release plus resolves several
problems found since v2.1 was released. 

***If you are a v2.0.4 user and interested in the changes offered in the v2.1 
release, I recommend installing this release.

***If you are a v2.1 user, an easier upgrade path would be to install the v2.1.2
UPDATE package (executable file only, not a full install).  

***If you are Santa Clara County RACES user that installed v2.1, the v2.1.2
UPDATE package (executable file only, not a full install) is required.


3. INSTALLATION NOTES
----------------------------------
While version 2.1.2 programs are FULLY compatible with the v2.0 data files, 
this is a full install package that brings all files up to date.  To use 
this release, previous Outpost versions MUST be uninstalled.  

Outpost runs on the following Window Operating Systems: 98, NT, 
2000, ME, and XP.  A single Installation package supports all of 
these operating systems.

3.1.  If you are downloading Outpost from the Website, I recommend 
creating a directory for the op212.zip file (something like c:\optemp, 
or whatever).  Download the zip file and open it.  You will find 
5 files...

Outpos1.CAB -- compressed copy of all program and document files
Outpos2.CAB -- compressed copy of all program and document files
setup.exe -- the setup program... double-click on this to start the setup.
SETUP.LST -- the setup control file... please don't change this!

3.2.  Save the current configuration files.  
NOTE: If you are on a release earlier than v2.0, then SKIP this step.  
If you are on v2.0 or greater, OK to proceed.

The v2.0 installation delivered several data files used to store 
the configurations for TNCs and BBSs.  The v2.0 uninstall process
will attempt remove them.  The v2.1.2 release does not include any of
these files, and your v2.0 files will work fine.  

To save these files, do the following:

1.  Go the c:\Program Files\Outpost directory
2.  Rename tncinfo.dat to tncinfo.v20
3.  Rename bbsinfo.dat to bbsinfo.v20
4.  Rename outpost.odb to outpost.v20

3.3. Uninstall any previous version of Outpost.

3.4  From the c:\optemp directory created above, run setup.exe. 
Setup starts by copying 2 files required to support the installation 
process.  It is now unlikely that you will be prompted to perform a 
reboot.  However, if you are, approve the reboot, then run the setup 
again (sorry, not one of those wizzy setup programs).

3.5  The balance of the installation process is straight forward.  
Follow the prompts and on completion, Outpost is ready to run.

3.6  Restore the configuration files.
NOTE: If you are on a release earlier than v2.0, SKIP this 
step.  If you are on v2.0 or greater, OK to proceed.

Do the following:
1.  Rename tncinfo.v20 to tncinfo.dat
2.  Rename bbsinfo.v20 to bbsinfo.dat
3.  Rename outpost.v20 to outpost.odb


4. POST INSTALLATION CHANGES
----------------------------------
There are three steps that should be performed once Outpost v2.1.2 has
been installed.

4.1 REQUIRED: Correct Advanced BBS Prompts risk.
	1.  Run Outpost
	2.  Select Setup > BBS
	3.  If you previously DID NOT set up a BBS with Advanced Prompts, 
	    do the following
		- select 2nd tab "BBS Prompts"
		- press "Advanced", press "OK"
		- check the "Default to Command Prompt" box
		- Press OK
	4. Repeat for each BBS configured.

4.2 OPTIONAL: Import the v2.1.2 Welcome messages and Updated How-To files.
	1. Run Outpost
	2. Select File > Import
	3. Change the directory to the Outpost main program directory
	4. Select the file "op210-messages.oaf"
	5. Confirm 19 messages were loaded.

4.3 OPTIONAL: For new users, download the sample TNC and BBS configuration
    files.  NOTE: For existing users, be careful not to overright your 
    existing config files.
	1. Download the file "op210ConfigFiles.zip" off the Outpost website
	2. Unzip the file
	3. Cope the 4 files (TncInfo.dat, BbsInfo.dat, AA6WK-2.pth, 
	   README210-CONFIG.txt) to the Outpost programs directory
	4. Read the README210-CONFIG.txt for a description of the config
	   files
	5. Run Outpost as usual, and check out the TNC and BBS 
	   configurations.


5. CREATING FLOPPY INSTALL DISCS
--------------------------------
If you do not have access to the internet on the target machine and 
do not have a CD-ROM drive, you can create a floppy installable version 
by doing the following:

5.1.  Download the installation package to a temp directory.
5.2.  Unzip the download package.
5.3.  Mark 2 formatted floppy discs as "Outpost Disc 1" and "Outpost Disc 2".
5.4.  Copy the following files to Floppy 1...
	Outpos1.CAB
	setup.exe
	SETUP.LST
5.5.  Copy the following files to Floppy 2...
	Outpos2.CAB
5.6.  Insert Floppy 1 in the target system.  Navigate to the floppy, and 
      run setup.exe.
5.7.  The installation program will prompt you to insert the 2nd floppy.


6a. WHATS NEW IN OUTPOST 2.1.2
-----------------------------
#541 Resolve Splash Screen problem
#542 Fixes problem when Tactical Call turned on, any change or OK in BBS 
     resets it to off.

6b. WHATS NEW IN OUTPOST 2.1.1
-----------------------------
#536  Adds a report tag for Tactical Call <taccall>
#538  Resolves the VB401 "show non-modal" error when NTS Message Maker is 
      open and send/receive runs
#539  Fixes W6XSC-1 BBS tactical call problem for Santa Clara County RACES
#540  Corrects multiple signature lines added to new messages

6c. WHATS NEW IN OUTPOST 2.1
-----------------------------
NEW FEATURES
-----------------
#320 BBS Access through KA- & NET/ROM-Nodes.
#434 Non-prompting Tactical Calls; allows users to use Tactical Calls 
     on Packet.

ENHANCEMENTS - FORM NAVIGATION
-----------------
#305: Make the In-Box and Out-Box sort order stay as previous set from 
      run to run.
#417: Select Text in a field when tabbed to it.  
#512: Enhance dialog boxes to respond to ESC for Cancel.
#524: Fixes message sorting by Date or Size.  
#529: Added splash screen to cover application startup activities, 
      particularly useful when there are a large number of messages to 
      be initialized.

ENHANCEMENTS - MESSAGE HANDLING
-----------------
#504: Define and insert a Signature in a message at message-create time 
      for the named user.
#514: Added a "Select All" from Edit in message form.
#520: If a message is created as a reply/forward, then the user chooses 
      to add a report, put the report on the top, not the bottom of the 
      message.
#522: Defect: On NTS Message Maker, removed the BT from after the preamble.
#525: Defect: resolved a file handling problem.
#531: Improves ability for message numbers to be as large as 9 digits.
#535: Defect: resolved problem where a Report template's <subj> text was 
      not being placed onto the subject line.

ENHANCEMENTS - SETUPS
-----------------
#528: Improved data field management on TNC and BBS Setup forms; should 
      be transparent to the user.
#530: Defect: Resolved a problem with Advanced BBS Prompts feature and 
      how the fields get updated.

ENHANCEMENTS - SEND/RECEIVE CHANGES
-----------------
#521: Added independent print and number of copy options for outgoing 
      messages and incoming messages.

ENHANCEMENTS - TNC, BBS HANDLING
-----------------
#502: Defect: Resolves the situation where F6FBB BBS messages has to 
      many @ signs when downloading bulletins by telnet and serial port.
#513: Reduces the Session Abort delays for TNCs between sending the 
      "cntl-D" and sending the "D" command; this is a point of confusion 
      and caused users to unnecessarily press Abort a second time.
#518: Defect: BBS busy is not detected when connecting to KPC PBBS. 

ENHANCEMENTS - INTERACTIVE PACKET ENHANCEMENTS
-----------------
#514: Added a "Select All" from Edit in message form.
#516: Added option to immediately turn Monitor On when connecting to 
      the TNC in ipserial.exe.
#517: Defect: Resolved the problem when attempting to Create a Message 
      from the Interactive Packet Window programs.


Best Regards,

Jim O  KN6PE
Emergency Coordinator
Cupertino ARES/RACES
Cupertino, CA

---------------
Readme.txt; v2.1.2, 05-Nov-06
Readme.txt; v2.1.1, 17-Oct-06
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
