Outpost Packet Message Manager, v2.4.0c099, 01 June 2010 Copyright (c) 2003 - 2010 Jim Oberhofer KN6PE 1. Overview 2. Who should install v2.4.0 3. Installation Notes 4. Changes in v2.4.0 ---------------------------------- 1. OVERVIEW ---------------------------------- This is an update to the initial v2.4 c074 release. See Section 4 for details. The v2.4 release delivers over 70 changes to the Outpost application suite covering new features, enhancements, and low priority defects. The key changes includes the Address Book and the 1st release of an ICS 213 messaging form. The v2.4 release updates all Outpost program and data files that Outpost uses. This installation can be applied either as a new installation for new users or as an update for existing users. This release will perform a data migration that automatically will be performed as part of the installation process. While the release has been thoroughly tested, I do not have all the configurations available to me that you may have locally. I strongly recommend that you perform your own check-out with your environment and confirm it is operational prior to a broader deployment. ---------------------------------- 2. WHO SHOULD INSTALL Outpost v2.4 ---------------------------------- This release adds several enhancements that you may find of interest as well as resolves a couple of problems found since the v2.3 release. There is no compelling reason for installing v2.4 other than taking advantage of these new features. See Section 4 below for a description of the changes. ---------------------------------- 3. INSTALLATION NOTES ---------------------------------- This release includes instructions for installing Outpost off of the web or downloading and running the install program locally, as well as support for building install floppies. Look for and download the opfloppy240ixx.zip file for details. Depending on who you are (NEW or EXISTING USER), please follow the instructions below. NEW USER / FIRST-TIME INSTALLATION ---------------------------------- If you never installed Outpost before, proceed as follows: 1. Download the opsetup240ixx.exe program from the Outpost website. "xx" is the latest release of this file. 2. Run the install program and, when prompted, select "First time installation for new users". All Options should be checked. This is a full install that includes all program files, documentation, sample scripts, sample reports, and sample configuration files (TncInfo.dat, BbsInfo.dat). 3. When done, run Outpost. Check out the HOW-TO pages on the Outpost website or the users guide that will be loaded into your Outpost\Docs directory. EXISTING USER / UPDATE INSTALLATION ------------------------------------ NOTE: This installation will migrate the Message, BBS, TNC, and any PATH data files to the format that Outpost v2.4. uses. Old files are renamed with an extension of *.o22 (just in case you really want to go back) and placed in an ..\Outpost\backup directory. 1. Make sure Outpost is not running. **If you have Outpost v2.3 or greater installed, SKIP to step 5. **If you have Outpost v2.2.2 or earlier installed, proceed as follows: 2. Navigate to the Outpost program directory (c:\program files\Outpost). The Hxdata.dat (NTS Handling Instructions) file was previously sent as a READ-ONLY file. Delete the file; it will be reinstalled correctly. 3. Uninstall Outpost (last time you should need to do this before a new install!). From Windows, select START > Settings > Control Panel. 4. Select "Add or Remove Programs" options. Find the entry for Outpost, highlight it, and then press the Remove Button. Old Outpost executables will then be removed. 5. Download the opsetup240ixx.exe program from the Outpost website. "xx" is the latest release of this file. 6. Run the install program and select "Update for existing users." This install option is for existing users with configurations that they want to preserve. Only the program files and documentation are installed. You may optionally choose to install the sample files (scripts, reports) if not previously downloaded. WARNING!!! DO NOT SELECT the Sample Configuration Files option if you are a current Outpost user... this could overwrite your existing TNC and BBS configuration files (TncInfo.dat and BbsInfo.dat). You will get a pop-up warning if this is attempted. 7. When done, run Outpost as usual. ----------------------------- 4f. UPDATES IN v2.4.0c099 ----------------------------- The Outpost User Guide is updated to reflect these changes. #801: allow Outpost to Telnet through BPQ to a BBS using BBS Paths. #817: Resolves problem of performing copies of BBSs with Path Files, and the Path File was not copied. Associates Path Files with BBS Friendly Name, not Connect Name. #847: if there was a BBS disconnect immediately after a connect, try to determine the reason, and report it. #848: Resolves Tools > Msg Settings > Advanced, Prompt option did not stick. #850: Adds ARL Number 47 for ARL numbering section, see latest FSD-3 form. #852: Ics213mm, Resolves situation where Signature and Position were not printed. #853: Further improves TNC initialization error and abort handling. #854: Aligns Outpost Telnet connect sequence to the Telnet Protocol Specification. #858: Enhances script handling for BBS names; now accepts Friendly Name or Connect Names. #859: Add a flag to wait for the script to complete before exiting Outpost. #862: Ignore Auto-receipts (Delivery and Read) for Bulletins. #864: Resolves erroneous error notification when abort is pressed with Retrieve Filters enabled. ----------------------------- 4e. UPDATES IN v2.4.0c089 ----------------------------- The Outpost User Guide is updated to reflect these changes. Outpost.exe #824: Removes the AA4RE LM check for my call sign in the To Listing; no longer needed. #825: Adds option to not put the message number on the subject line. #827: Resolves Outpost not retrieving filtered JNOS messages. #828: If "L" is entered as the Filter List message command, does not append the Area. Makes for more efficient message checking. #830: Adds ability to use the JNOS SC command (send copies) for multiple address processing (used when multiple addresses or a Dist List is on the TO: line). #832: Adds option to always reply with a delivery receipt. #834: Adds Notification levels to the Doc; changes the "L" flag to "N". #835: Resolves Send/Receive not exiting during a TNC connect prior to the BBS connect. #836: Allows BBS Area Filters to accept a "-" or a "_" for Area Names. #837: Resolves Note box and Session log not showing all application error data. #840: Resolves situation where S/R session is running while user changes the BBS selection. #841: Resolves problem where multiple addresses on a script TO: field were not displayed correctly. #844: Resolves N0ARY send message problem (returning "!! Abort Send Command" Error). Ipserial.exe #838: Adds a timestamp when we do a connect & disconnect by Outpost Opdirect.exe #831: Derives Subject Line from !PACF! header line. Requres PacFORMS v.30. ----------------------------- 4d. UPDATES IN v2.4.0c082 ----------------------------- Outpost ER#822: Fixes Address book problem with single Address entry. ER#823: Fixes BPQMailChat handling to exclude LFs on transmitted strings. ----------------------------- 4c. UPDATES IN v2.4.0c081 ----------------------------- Outpost ER#799: one more time; add change to allow BPQMailChat to support SMTP email. ER#811: corrects problems with Node Handling, Xconnect, and BBS connect commands. NOTE: READ THE UPDATED APP NOTE ON CONFIGURING KA-/NETROM NODES. ER#813: Supports BPQMailChat RMS: and RMS/ address structures for BPQMailChat- to-RMS node message passing. ----------------------------- 4b. UPDATES IN v2.4.0c077 ----------------------------- Outpost ER#508: Fix Address book to reformat the email address area from a list of entries to a line of entries. ER#799: Add change to allow BPQMailChat to support SMTP email. ER#802: Change PacForms handling for opening a message back in its native HTML page. ER#807: Scripts is not pulling up BBS by Connect Names instead of Friendly Names. ER#809: Allow current BBS, TNC, Retrieve options if not called out in Scripts. Ics213mm ER#803: Fixes problem where the program restarts after shutting it down. Opdirect ER#808: Change to write Ics213mm & PacForm messages to Out Tray vs Draft Folder. Opupdate24 ER#805: Updates the control button label. ----------------------------- 4a. CHANGES IN v2.4.0c074 ----------------------------- ER#508: Address Book Support. Allows alias and distribution lists to be created. Also, Outpost now processes distribution lists for all BBS types (not necessarily efficiently). ER#659: ICS213 support. This is a stand-alone program for ICS 213 data entry and message management. 4.1 BBS SUPPORT ER#576: MFJ-1274 PBBS ER#592: OpenBCM BBS. Popular in Europe and has a following on the East coast. ER#744: PK-96 PBBS. ER#777: BPQMailChat BBS. This is a new BBS currently in BETA release. ER#787: Add support for BBS KFJ-127x version MFJ-2.0 firmware. 4.2. Message Handling ER#656: Add control to manage on-line report and message printing. ER#684: Extend TO: address field size. ER#729: Automatically open ARL message maker when clicking on ARL on NTS form. ER#757: Message buttons were hidden when screen is sized too small. ER#761: Opdirect/PacForms: removed index page link. Use the BACK button to return. ER#771: Add on-line reports feature to set up the message TO: field with a tag. ER#781: Suppress the Opdirect popup when a message is created and queued with OpDirect. 4.3. Send/Receive Handling ER#619: Add node handling for KPC4 to support the "Xconnect" command. ER#708: Add option to connect to a BBS from a node by entering "BBS" instead of the connect command. ER#747: Consolidate same level notifications into a common window. ER#783: Skip SNOS messages when the Status contains "K" for killed. ER#784: Check KPC3 PBBS message date-time for invalid date and performs a 00/00/00 = 01/01/1980 translation as an indicator that the date was incorrect. 4.4. Setups and Configurations ER#628: Add BBS/TNC “Recently Used” Access. ER#677: Add Friendly name for BBS configuration. ER#695: Extend BBS Digipeat field size. ER#763: Correctly implement Winlink password handling; removes workaround. ER#764: Add clone BBS config as a BBS Setup option. ER#765: Add clone TNC config as a BBS Setup option. ER#776: Create a link for a BBS to its TNC/Device. ER#778: Removes the option to hide/display “Save w/o Headers”. ER#788: Add Station ID check-box to show at startup; sets focus on OK. ER#795: Change Signature error handling to be the same as all the others. 4.5. Scripting Changes ER#748: Startup script automation. ER#751: Kick off specific script from Outpost main at Outpost startup and shutdown. ER#758: Assigns Mycall to current Outpost Mycall if Opscript Mycall is blank. ER#782: Allows user to reconfigure the Send/Receive button to run a script. 4.6. Other ER#785: Change Outpost WindowState to always start up as Normal. 4.7. Resolved Problems ER#622: FROM: field is too short for some SMTP addresses. ER#737: Resolves ipserial.exe echo on/off control, now Echo ON as default. ER#755: Improves folder to folder Drag-and-Drop. ER#756: Differentiates between the 2 KPC-2 firmware revisions (KPC2-5.0-HM$ and KPC2-3.06-H) that do not behave the same. ER#759: Fixes the problem when the telnet password is blank. ER#760: Fixes the problem with SP, ST, and SB commands settings and use. ER#774: Fixes Opscript WriteFile failed with Windows98, but not on XP. ER#779: Directory Select option (Tools > Directory Settings) does not pick up and apply the Drive the directory list. ER#780: Fixes report form closing w/o confirming the report file actually exists. ER#789: Fixes the TNC Setup Apply Button not getting the form back to an initial state. ER#790: Fixes the BBS Setup Apply Button not getting the form back to an initial state. ER#791: Prevents manual entry into pull-down menus. ER#792: Added error checking for when Digipeat selected but no digis are defined. ER#794: Added error checking for when Default Destination option was checked and field was left blank. ER#796: Resolves NTS not trapping and handling the last period in the message. ER#797: Fixes situation where NTS was clearing the default destination setting if set to Private. Best Regards, Jim O KN6PE Cupertino, CA --------------- Readme.txt; v2.4c074, 29-Dec-09 Readme.txt; v2.3u030, 1-Sep-09 Readme.txt; v2.3u028, 29-Jun-09 Readme.txt; v2.3u027, 31-Dec-08 Readme.txt; v2.3.0, 12-Oct-08 Readme.txt; v2.2.2, 1-Jun-08 Readme.txt; v2.2.1, 19-Feb-08 Readme.txt; v2.2u232, 29-Jan-08 Readme.txt; v2.2u229, 22-Nov-07 Readme.txt; v2.2u228, 10-Nov-07 Readme.txt; v2.2u211, 04-Jul-07 Readme.txt; v2.2u209, 06-Jun-07 Readme.txt; v2.2u208, 03-Jun-07 Readme.txt; v2.2u205, 14-May-07 Readme.txt; v2.2c194, 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