All,
WINMOR was designed to be an open alternative to Pactor. The WINMOR protocol spec is fully documented and released for public distribution and use. It is available at: http://groups.yahoo.com/group/WINMOR and http://groups.yahoo.com/group/Winlink_Program_Group and http://www.winlink.org/WINMOR and http://www.arrl.org/FandES/field/regulations/techchar/WINMOR.pdf A Google on "WINMOR" will turn up these and other references. There is also a helper application Virtual WINMOR TNC which can be used by other applications to create, clients, monitors, keyboard to keyboard utilities etc. This helper app is used by RMS WINMOR and RMS Express and has already been used by at least 2 other programmers to create non Winlink WINMOR supported applications like BPQ32. The Virtual WINMOR TNC has a complete spec for the application interface. Because it is both ARQ and normally sends messages using compressed binary transmission it is difficult to monitor content when not connected. It is not a question of "missing a few frames" because even a single missed frame in a message normally makes the decompression fail. Monitoring the compressed code is pure gibberish. This is the same situation that exists when monitoring any B1 or B2 compressed FBB forwarding session in Pactor or Packet. RMS Express does have a monitor function that logs Call signs and Grid square ID frames as well as CWID at the end of a session. ID frames are sent at the end and every 10 minutes during a session. The WINMOR FEC mode which is designed for keyboard to keyboard or broadcast is not compressed but used very robust Viterbi +RS encoded 4FSK so can be monitored very easily using the WINMOR Virtual TNC. The next version of RMS Express will support both connected and FEC Broadcast keyboard modes using uncompressed data. Normal FBB/Winlink B2 forwarding sessions will continue to use only compressed data since it give approximately a 2:1 improvement in throughput and handles attachment and multiple address encapsulation. The programs RMS Express and WINMOR TNC are available at either of the two yahoo group sites above. There are no plans to release the source code of RMS Express or WINMOR TNC but the protocol is fully documented and open to anyone who wishes to write a DSP TNC module and test it for conformance to the spec. If there are any questions or issues please contact me at rmuethingATcfl.rr.com 73, Rick KN6KB No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.733 / Virus Database: 271.1.1/2681 - Release Date: 02/12/10 14:35:00
