HFTerm

[David Hambly]

Walt,

For whatever reason, I did not get your post until today.

While it is true that HFTerm is pretty picky about it's configuration, I use 
RedHat 6.0 (older free OSS) and an AWE64 soundcard (SB16 is best) this is 
because of the 20ppm accuracy requirement of the protocol, The more I think 
about the TCP mailbox socket HFTerm provides, the more I see how this socket 
can be used to add-on valuable apps.  While HFTerm is open source, I think 
simply developing applications with TCP socket connectivity would allow 
integration with HFTerm and others (F6FBB etc.).   I am experimenting with 
JNOS as an add-on for HFTerm but I need to do a little more research.

In my mind, whether 30 baud (MFSK) or up to 600 baud (FS-1052) the key to 
successful emcomm is in traffic handling, ARQ is not an option when handling 
emergency traffic, this is why PacTOR 1 and AmTOR A remain most important 
modes for HF.  Normally the cost of PacTOR 1 is between $500 and $2000, 
HFTerm can get you in for about $5 (depending on your junk drawer).

I hope to see mt63 evolve into a psuedo ARQ mode because MARS tests have 
shown this mode simply "gets through" when other won't.  FNpsk is absolutely 
the best idea to come along in a long time and if integrated with mt63 and 
refined a little, will undoubtedly have a significant impact on emcomm.  
NetManager really does a great job of accounting, which is also a very 
important aspect of emcomm.  Combine all three above, keep cost low (HFTerm) 
and you will have THE killer app for emcomm.

I will be watching the list and will do whatever I can to help.

73
Dave