Outpost Packet Message Manager Platform Support |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Here's what you will find on this page... Serial Terminal Node Controllers (TNCs) One of the critical design assumptions around Outpost was that it would (or could be made to) work with any TNC out there. The TNC setup window allows you to either use the default TAPR2 TNC commands, or define a different set if your TNC requires that. So far, all Outpost users have reported that the default command set has worked with what they have. Needless to say, not all TNCs have been verified.
Confirmed Functional
1. Notes on AEA PK-232, PK-88 You have to first load the TNC's with basic settings using Packrat... then they work fine with Outpost.
2. Notes on the Kenwood D700. Please see the note from George SV2AGW and his information on the Kenwood D7 Handhelds and D700 Mobile at http://www.elcom.gr/sv2agw/hardware.htm. He has done a nice job summarizing the situation and the deficiencies of these 2 radios, particularly their use with Packet.
7/1/07. Excerpts from the Outpost users group on the D700: "The Kenwood Radios with the TNCs built in are only to be used for APRS they are not suitable for Outpost or Winlink in that configuration, but with the TNC turned off and a out- board TNC of good quality, the radio works very well."
Additionally, "The Tasco modem chipset used in the Kenwood and Alinco data radios have very limited buffers. They were created to receive the relatively short APRS data streams. For APRS and DXCluster messages, I think they work fine. They are just unsuitable for general purpose packet messaging where the message size overloads the buffer."
3. Note on KAM Very early versions of this TNC apparently have problems. For instance, for KAM firmware versions as early as v2.06, at least one user has reported receiving a INVALID STREAM messages when connecting to a telpac node, resulting in Outpost exiting unintentionally. While complete testing has not been performed, early versions of KAM firmware may be problematic. See the Kantronics/Firmware website for the history.
4. Notes on KPC's and KAMs There are a few TNC commands that are popping up that need to be set correctly at the Outpost side for the TNC to work. These settings are:
cmd: LFadd OFF cmd: Streamev OFF cmd: Streamsw 0
See the TNC's users guide for details on these commands.
5. Problematic The following TNCs have been reported to be problematic and are not supported.
6. Pending verification The following TNCs have not been verified.
If you have verified a different TNC, please let me know and I will add it to the list. AGWPE-supported TNCs Because Outpost supports AGWPE, all of the AGWPE-supported TNCs should work with Outpost as well. However, they all have not been confirmed with Outpost. If you have tried one and can confirm it operational, please let me know and I will update the list below accordingly. Check out George SV2AGW's link of AGWPE drivers and modems (TNCs) for what is supported with AGWPE and on what O/S, as well as the AGWPE download section. In the meantime, the following is a list of the AGWPE supported TNCs..
If you do not see your specific TNC on this list, it may still work, but just not listed. George SV2AGW's drivers and modems link states that all TNCs with KISS mode is supported (last entry). This may also apply to off-board sound-card TNCs such as the Tigertronics Signalink USB TNC. You may need to experiment with AGWPE and different options with you particular device to determine if it is supported. Verified Operating Systems Outpost has been confirmed to work on the following OS platforms:
Microsoft Operating Systems
One user has Outpost running on Windows 95 (out of Microsoft Support life); see the Outpost-on-Window95 application note. If you get Outpost to work on a Windows '95 platform, please do the following: Go to START, Select Run, then type winver (for Windows Version), then press enter. The current Windows OS information will be displayed. Please send me the information listed on this form. Linux
March 2007. Two users have successfully installed and used Outpost v2.1 under Wine on a laptop running Linux. While extensive testing was not performed, it was reported that the user was able to transfer messages both via TNC/radio (a Kenwood D7A no less) and via telnet connection. Another user reported it running on his laptop, but was painfully slow. Watch for an update or application note in the area. Intel MAC Book Pro 7 August 2007. John KC9KKO reported the following: "This week I installed Outpost on my INTEL Mac Book Pro and it runs nicely. First I installed a product called Crossover MAC from the Codeweavers site, then ran the OUTPOST installation executable, and then ran OUTPOST. I configured it to access the BBS’s using the TELNET. It works, and it didn’t take any effort thanks to a well written application. I might tackle serial port access in a couple of weeks." General Feedback Please send any feedback to updated: July 11, 2008 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||