Outpost Packet Message Manager, v2.2.1c085, UPDATE, 29-Jan-2008 Copyright (c) 2003 - 2008 Jim Oberhofer KN6PE 1. Overview 2. Who should install v2.2.1c085 3. Installation Notes 4. Changes in v2.2.1c085 ---------------------------------- 1. OVERVIEW ---------------------------------- The v2.2.1c085 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.1c085 is required. If you choose to update to v2.2.1c085, you only need to copy the 7 files from the zip file to the current Outpost directory. ---------------------------------- 2. WHO SHOULD INSTALL v2.2.1c085 ---------------------------------- This upgrade adds several enhancements that you may find of interest as well as addresses 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.1c085 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 v2.2c194. The v2.2.1c085 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 op221u085.zip file. You will find the following files: Hxdata.dat Ipagwpe.exe (v2.2.1 c15) Ipserial.exe (v2.2.1 c15) Iptelnet.exe (v2.2.1 c15) Opdirect.exe (v1.0.91) Outpost.exe (v2.2.1 c085) README221c085.txt 4. Copy the contents to the Outpost directory. 5. Run Outpost. Press Help > About Outpost. Confirm the version says it is v2.2.1 c085. ---------------------------------- OUTPOST WORKAROUND FOR WL2K by TELNET (#605) ---------------------------------- The following workaround is required to use Outpost with WL2K by Telnet. When setting up the interface, 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 preceeded 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 next Outpost 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.1c085 ----------------------------- Adds BBS Support for the following: #589: Add support for JNOS BBS #669: Add support for the KPC-2 PBBS #613: Expand Notifications to 4 levels. Notifications was previously introduced as a single level runtime reporting aid and announced a mix of events that needed to persist beyond the Send/Receive Session. Four user-selectable levels of notifications (Tools > Send/Receive Settings, "Other" tab) are now available for the following areas: N0: Application Errors. Defaults to ON. N1: Problems that need immediate attention to proceed, such as Comm Port or Telnet problems, missing the KANODE Path File, or could not identify the BBS Type. Defaults to ON. N2: Unexpected BBS Disconnects. Defaults to OFF. N3: Other non-critical errors. Defaults to OFF #615: For newly created incomplete messages, Outpost highlights these messages in the message list area in Blue. #625: Makes the "L1: Send/Receive Session windows logging" setting persist across app restarts. The "L2: Interface Data Logging" and "L3: Diagnostic Logging" settings are reset to off every time Outpost is run. #626: When using Tactical calls with the TNC, resets the TNC's mycall setting back to the FCC call at the end of a Send/Receive Session. This ensures that for any beaconing, the TNC identifies correctly. #632: Update the message form caption when tabbing out of a new message subject area. #640: Adds an NTS HX pull down menu to select the Handling Instructions option. #644: Adds an option to allow formatted NTS messages to be sent as PRIVATE messages. #646: Adds an option to insert a separator character (:, -, etc.) between the 3 character Tac ID and the next Message Number. This addition makes the subject line look more readable in particular if the 3 character Tac ID includes numerals such as S45 (Station 45). The result would be: "S45-132: ..." #652: Adds minimize button to Opdirect.exe. DEFECTS ADDRESSED ----------------- #534: Implements a check during Send/Receive to determine if the Path File is already open for a BBS Path Update. #597: Implements a check to determine if a previously configured printer is still there at startup. #598: Implements a check to determine if the application subdirectories files are present at startup. If not, they are created. #612: Enhanced Error Handling for Send/Receive Session Manager. The focus of this effort was to resolve several reported problems with telnet access and hopefully addresses the source of the 40006 error caused by telnet commands being sent after a disconnect occurred. Minimally, these errors will be trapped and reported leaving Outpost running. #621: Check and report if specific Outpost data files (TncInfo.dat, BbsInfo.dat, Outpost.ini, and Outpost.odb) are set to Read Only. These files have been found as Read Only when copied off of a CD as part of a supplemental user installation process. #631: Resolves the situation when a data file size mismatch occurs, Outpost leaves the base form up without exiting. #650: Resolves the problem when receiving a message that has no text (after stripping off the headers), the message was not saved. #660: Resolves the F6FBB message retrieval problem created when addressing DXNET operations.  #661: Adds the "Save As No Headers" option to the Outpost main file menu. #662: Resolves the problem where not all Telnet connects worked. #663: Removes all superfluous spaces when applying a cut-and-paste of the host name into an Outpost field. #664: Resolves the problem in calculating N0ARY prompts due to the BBS putting the last message number as part of the prompt. N0ARY prompts are now set to "]>". #665: Resolves the problem where Outpost could not connect to an F6FBB BBS with a Tactical Call by a digipeater when using AGWPE. #666: Resolves the problem where Outpost could not connect to a DXNET BBS by AGWPE. #668: Resolves the problem when manually closing after a fail, the iptelnet.exe main form reloads. Best Regards, Jim O KN6PE Cupertino, CA --------------- 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