Outpost Packet Message Manager, v2.2.2c027, UPDATE, 4-June-2008 Copyright (c) 2003 - 2008 Jim Oberhofer KN6PE 1. Overview 2. Who should install v2.2.2c027 3. Installation Notes 4. Changes in v2.2.2c027 ---------------------------------- 1. OVERVIEW ---------------------------------- The v2.2.2c027 release is an UPDATE to all Outpost program files that were delivered as part of the original Outpost v2.2 general release. This update assumes that the version 2.2c194 release or newer updates previously were installed. This release does not result in any data file changes. No data migration to v2.2.2c027 is required. If you choose to update to v2.2.2c027, you only need to copy the 7 files from the zip file to the current Outpost directory. ---------------------------------- 2. WHO SHOULD INSTALL v2.2.2c027 ---------------------------------- This upgrade adds several enhancements that you may find of interest as well as resolves a couple of problems found since the v2.2 release. There is no compelling reason for installing v2.2.1 other than taking advantage of these new features. See Section 4 below for a description of the changes. ---------------------------------- 3. INSTALLATION NOTES ---------------------------------- Version v2.2.2c027 is FULLY compatible with the original v2.2c194 release and subsequent updates. To use this update, Outpost v2.2c194 or greater MUST previously have been installed. Installing this UPDATE on top of any pre-v2.2 release will cause problems. All users wishing to use this UPDATE must have previously downloaded and installed at least v2.2c194. The v2.2.2c027 distribution is not a full installation package. Instead, it only contains the executables to replace specific files that previously were installed with the v2.2 release. To install this UPDATE, proceed as follows: 1. Confirm that Outpost v2.2c194 or greater was previously installed. 2. Go to where Outpost was installed, probably in the directory... c:\program files\Outpost. 3. Open the op222c027.zip file. You will find the following files: Hxdata.dat Ipagwpe.exe (v2.2.2 c19) Ipserial.exe (v2.2.2 c19) Iptelnet.exe (v2.2.2 c19) Opdirect.exe (v1.0.91) Outpost.exe (v2.2.2 c027) README222c027.txt 4. Copy the contents to the Outpost directory. 5. Run Outpost. Press Help > About Outpost. Confirm the version says it is v2.2.2c027. ---------------------------------- OUTPOST WORKAROUND FOR WL2K by TELNET (#605) ---------------------------------- The following workaround is required to use Outpost with WL2K by Telnet. When setting up the Telnet interface to a WL2K station, do the following: 6. Setup > TNC Settings. Select Tab 4. Fill in the Remote Host and Remote Port as usual. 7. For the Logon field, enter your logon name preceded with a "." (dot). for instance, if your call sign is KN6PE, enter ".kn6pe" . 8. Enter the WL2K password as usual. Press OK. A correction is planned for the Outpost v2.3 release to handle this more elegantly (Enhancement Request #606). 9. Run Outpost as usual. ---------------------------------- APPLYING THE AGWPE-NODE-BBS FIX (#574) ---------------------------------- 10. If you use AGWPE and access your BBS off of a node, after installing this version, do one of the following: 1. Delete the file TncInfo.dat, and re-enter your AGWPE configuration 2. Update the TncInfo.dat file. - Run Outpost. - Setup > TNC Settings. - Make a field change so that the Apply button becomes enabled (easiest is enter something in the description field). - Press OK. 11. Run Outpost as usual. ----------------------------- 4. CHANGES IN v2.2.2c027 ----------------------------- NEW FEATURES ----------------- #525: Add Drag and Drop for moving messages between Outpost folders. One or more messages can be selected from the currently displayed folder, then dragged and dropped on the folder button of the destination folder. #682: Adds TNC Initialization file capability. Allows the user to define a list of TNC commands to be sent to the TNC both prior to a BBS connect as well as immediately after a BBS disconnect. #698: Enhanced Channel Monitoring. Outpost now determines if ipserial.exe is running and, if so, directs that program to disconnect from the Comm Port. Outpost will then run its Send/Receive Session as usual. Once the session is over, Outpost tells ipserial.exe to reconnect to the Comm Port and resume monitoring. #709: Support multi-message deletes. Builds on the multi-message select capability of Drag and Drop, this allows one or more messages to be selected and deleted at one time. ENHANCEMENTS ----------------- Adds Support for the following BBSs: #604: TNOS #596: SNOS #696: HAMSERV #207: Brings an already open message to the top of the disaplay list. #519: Adds 4 hot-keys to opens a report form in a message with a single Function Key press. #603: Expands the number of message retrieval filters from 10 to unlimited. The 10 individual fields have been replaced with a single field where the user can enter an unlimited number of retrieval filters separated by commas. #634: Force Com Port Echo Command to On. Comm Port Echo must be ON for Outpost to process the BBS response correctly. #658: Expands the number of time slots from 4 to unlimited. The 4 individual slot time fields have been replaced with a single field where the user can enter an unlimited number of times separated by commas. #674: Allows the user to retrieve his/her own NTS messages. This would be used in the event the message is no longer relevant AND was never retrieved for servicing. #676: Adds a menu option to the 3 Interactive Packet Programs to read a file and dump the text into the respective text window for transmitting to the BBS. #685: Handles smtp email addresses. Required since JNOS and some other BBSs allow users to enter a standard smtp email address (user@domain) for mailing into the internet. #687: Allows access to NOS Message Areas. Uses the Retrieved Filter Messages option for selecting a JNOS or TNOS message area, then retrieving the messages. #694: Sets the default notifications options to ON. All 4 Notifications Options -- N0 (Application Errors), N1 (Problems needing immediate attention), N2 (Unexpected BBS disconnects), and N3 (Other non-critical issues) are now turned on at first time installation. #705: Adds a new subject line identification option in the form: yymmddhhmmss. DEFECTS ADDRESSED ----------------- #675: Ensures message number field in Report Settings is populated before exiting the form. #693: Handles any “>” characters in the BBS message number that is not part of the BBS prompt. #703: Resolves specific forms buttons from getting chopped off during a form resize. #707: Adds clarify to some form instruction text. #710: Fixes interface data logging for iptelnet.exe. #711: Resolves problem where there were duplicate subject line message numbers when using opdirect.exe. #712: Resolves incomplete message printing of a new message that was not yet saved. Best Regards, Jim O KN6PE Cupertino, CA --------------- 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