Overview
This page summarizes any known issues that might be encountered by our packet users. The integrated packet installer and all of its components are covered.
Integrated System (including installer)
- MS Windows Compatibility Note:
- Windows 10 is recommended
- Windows 7 or greater is required for auto-printing
- Windows 2000 or earlier is not supported
- As always, we recommend using a currently supported version of Windows. At the current time, this means Windows 8.1 (extended support only) or later (Windows 10).
- The integrated system (Outpost, PackItForms, PacFORMS) is supported on Windows 7 or later.
- It may also work (without auto-printing of add-on message types, like PackItForms) on Windows XP and Vista. But we have very limited ability to test and support these platforms. Any support is on a best-effort basis.
- It does NOT work on Windows 2000 and earlier versions of Windows.
Outpost
- MS Windows can cause Outpost to be blocked while waiting on PDF printer filename
- Using a PDF pseudo-printer is common for testing purposes. It may also be used for creating a permanent record of the final format messages.
- When printing to a PDF pseudo-printer, the MS Windows Operating System blocks the calling program while it waits on the user to select a PDF filename. If this happens during an Outpost Send/Receive session, Outpost is prevented from continuing, including the Send/Receive session. If the user does not enter a filename within the BBS session timeout, then when Outpost resumes, the Send/Receive session will have timed out.
- Workaround: When using a PDF pseudo-printer, enter the filename when prompted.
- Resolution: Outpost will be updated in a future release to include an intermediate program that can be blocked by the Operating System while allowing Outpost to continue running.
PackItForms (New forms)
- Compatibility Note: Submit via E-mail
- The "Submit via E-mail" feature works with MS Outlook, Windows 10 Mail, Mozilla Thunderbird, Eudora OSE
- It does NOT work with older/original Eudora (v7.1.0.9 and earlier), which was discontinued in 2006. If an "&" (ampersand) appears anywhere in a message submitted to Eudora, a bug in Eudora causes it to drop all content from the "&" to the end of the message, rendering the message unreadable by the recipient.
PacFORMS (Legacy forms)
- Compatibility Note: Older versions of PacFORMS
- The Severity field is only required on the ICS-213 Message form
- For compatibility with older versions of PacFORMS, the Severity field will remain in all other PacFORMS, but it will be optional
- When the form is submitted to Outpost, PacFORMS will construct the packet message Subject: line as follows:
- If the user selects a Severity, PacFORMS will generate an Outpost Subject Line with the old format:
- <MsgNbr>_<S>/<H>_<FormType>_<FormSpecificData>
- Where <S> is the Severity (E,U,O) and <H> is the Handling Order (I,P,R)
- If the user does not enter a severity, PacFORMS will generate an Outpost Subject Line with the new format:
- <MsgNbr>_<H>_<FormType>_<FormSpecificData>
- PacFORMS displays operator name incorrectly if it includes special characters
- Description: If the operator name configured in Outpost > Setup > Station ID > Legal > User Name contains special characters, such as a comma (",") or ampersand ("&"), PacFORMS may fail to open or may display only part of the name in the operator name field at the bottom of the form.
- Workaround: Use only alphanumeric (letters and numbers) in the User Name field.
- PacFORMS exhibits inconsistent treatment of double-quotes (") in a message
- Description: In some PacFORMS, double-quotes (") are converted to single-quotes (') when the message is submitted to Outpost. This can cause a message to be misinterpreted by the recipient if the difference in symbols is significant, such as in GPS coordinates or foot/inch measurements.
- Workaround: Avoid the use of double-quotes in a message if single-quotes are not a valid replacement.
[Top]
This page was last updated on 02-Dec-2020