Outpost Packet Message Manager, v2.2.0c194, 6-April-2007 Copyright (c) 2003 - 2007 Jim Oberhofer KN6PE 1. Overview 2. Who should install v2.2.0 3. Installation Notes 4. Post-Installation changes 5. Creating Floppy Install Disks 6. What’s new in v2.2.0 ---------------------------------- 1. OVERVIEW ---------------------------------- The v2.2 release is a full release of all Outpost programs and files that delivers Telpac terminal emulation support ans other BBS handling improvements to the Outpost user community. Other select features requested by Outpost users are also included. See the "What's New..." section below for details. Because this release does change 2 of the Outpost data files, an update program is provided that will migrate your current message and BBS data file information to the new v2.2 data structures. There should be no loss of messages or configurations with this approach. As with the previous release, a separate .zip file is also provided for first-time users to check out sample TNC and BBS configurations. This approach also lets current users preserve their TNC and BBS configurations. An Outpost Archive message file is also provided that includes all new HOW TO messages. See the "Post-Installation..." notes for details. This README file exclusively addresses the Outpost v2.2 application installation. ---------------------------------- 2. WHO SHOULD INSTALL v2.2 ---------------------------------- This release adds several enhancements that may be of interest, as well as addresses several problems found since the v2.1.0 release. There is no compelling reason for installing v2.2 other than taking advantage of these new features. ---------------------------------- 3. INSTALLATION NOTES ---------------------------------- This is a full install package that brings all files up to date. To use this release, all previously installed versions of Outpost MUST be uninstalled. Outpost runs on the following Window Operating Systems: 98, NT, 2000, ME, XP, and Vista. 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 op220c194.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! README220.TXT -- this file 3.2. Save the current configuration files. If you are on a release earlier than v2.0, do the following: 1. Export pre-v2.0 messages. From Outpost main form, select File >> Export >> All Folders. Note the file name. You will need this when you import them after the v2.2 installation. If you are on a release v2.0 or later, proceed with the installation process. 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. 3.6 If you previously had a version earlier than v2.0, from the Outpost menu, select File >> Import. Enter the file name. Press OK. This is the reverse of step 3.2 above. 3.7. For users of v2.0 or greater: update any existing message and BBS data files by running (double-click on) the program titled "opupdate22.exe." Press "OK" each time you are prompted to proceed. Updated copies of Outpost.odb and BbsInfo.dat will be created. The previous version of these data files are renamed as follows: Outpost.odb -> outpost.o20 BbsInfo.dat -> BbsInfo.020 3.8. Run (double-click on) the program titled "Outpost.exe." Verify the program main form opens. Verify your previously retrieved messages and previously configured BBSs are displayed. ---------------------------------- 4. POST INSTALLATION CHANGES ---------------------------------- There are 2 optional steps that can be performed once Outpost v2.2 has been installed. 4.1 OPTIONAL: Import the v2.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 "op220-messages.oaf" 5. Confirm 3 messages were loaded into the In Tray and the 18 HOW-TO messages into the Draft Folder. 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 "op220ConfigFiles.zip" off the Outpost website 2. Unzip the file 3. Exit form Outpost if it is running. 4. Copy the 4 files (TncInfo.dat, BbsInfo.dat, AA6WK-2.pth, README220-CONFIG.txt) to the Outpost programs directory. 5. Read the README220-CONFIG.txt for a description of the config files 6. 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. ----------------------------- 6. WHATS NEW IN OUTPOST 2.2 ----------------------------- NEW FEATURES ----------------- #480, #436: adds support for Telpac by terminal emulation. Includes support for multi-address destinations. See limitations for Telpac Access.  #550: explicit BBS identification. Reads the BBS SIDs to determine the BBS type during the Send/Receive session. Additionally, support is cleaned up or is now added for the following BBSs: -AEA232 PBBS (#391) -DXNET BBS (#551) -MFJ-1270 PBBS (#507, #533) -MFJ-1278 PBBS (#568) -Data Engine PBBS (#574) -MSYS handling changes to support SID identification (#552) -Telpac (#480) -W0RLI BBS (#32) #221: Implements Notifications feature so that, on an unexpected BBS disconnect or other Send/Receive error, a pop=up box shows the user what happened. This box persists beyond the end of the Send/Receive Session. #270, #510: Improves message readability by (i) storing BBS message headers separately from the source message (viewable from the message form), and (ii) finds and deletes message trailer lines that F6FBB and AA4RE BBSs add to the message. #527: Presents sorted Bbs and Tnc entries in their respective setup forms. #537: Provides the tool for updating message, Bbs, and Tnc Data Files from the previous release (opupdate22.exe for this release). #555: Improves Export/Import Message Handling. #559: Automatically populates specific BBS settings for non-configurable BBS and PBBSs. #562: Removes BBS Advanced prompt button; splits default controls for better prompt management. #565: Added capability to auto-identify the BBS prompts. There is no need to determine and fill in the prompts any more. #566: First implementation of Diagnostic trace calls. ----------------- DEFECTS ADDRESSED ----------------- #543: Date/Time data storage is changed to an internal data data type; allows Window's "Regional and Language Options" settings for date to apply on all displayed dates. #556, #560: Resolves defect with message display date sorts when adding or updating a message entry. #557: Resolves defect with Bbs and Tnc Setups when deleting all entries. #563: Resolves defect for handling Read and Delivery Receipts when BBSs change after the message was received, but prior to the receipt being sent. #564: Resolves defect for handling a BBS or TNC entry where the command was entered as a series of blanks. #569: Defect, resolves multiple ARL messages on cancel. #570: Defect, cleanup abort on telnet session #571: Defect, resolves incorrect handling of AGWPE, now an obvious issue due to message header processing. #572: Defect, resolves incorrect handling of AGWPE for AA4RE, non-prompting message processing. #573: Defect, resolved situation where message forms could not be recovered f minimized, then closed. Best Regards, Jim O KN6PE Emergency Coordinator Cupertino ARES/RACES Cupertino, CA --------------- Readme.txt; v2.2.0, 06-Apr-07 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