[Ham-Mac] Replacement for MacTNC v.1.1 ?

[Steve Hellyer]

This is rather confusing.  I see your point.

Perhaps Steve was having trouble compiling the new version, but 
actually the "old version" seems to work ok.
It could have also been one of the system updates to 10.3 (as I 
mentioned I am on 10.3.4) which corrected the problem he might have had 
with 10.3.0?

Anyway I hope it works for you.  If not here are some possible 
alternatives I know about.

Zterm - http://www.versiontracker.com/dyn/moreinfo/macosx/10529

MacLoggerDX - http://www.versiontracker.com/dyn/moreinfo/macosx/14364
This does much more than TNC.

RDCP/Mac - http://www.winternet.com/~nedbalek/rdcp_mac_2.html

73
Steve
VA3SPH

On 16-Jul-04, at 11:48 AM, Chuck Counselman wrote:

> As I mentioned previously, MacTNC v.1.1 works fine for me under Mac OS 
> 10.2.8.  I never tried to use it under 10.3.x because -- I believe, 
> although I may have misunderstood -- Steve Muncy, its author, told me 
> that it wouldn't work.
>
> Searching my email archive for my correspondence with him, just now I 
> found that on November 12, 2003, he told me that he had a later 
> version, 1.2, that  ran under Panther.  He did not say what version of 
> Panther, but perhaps you can guess from the date.  He also sent me 
> MacTNC 1.2, and I was embarrassed to discover just now that v.1.2 is 
> what I have actually been running since that date.
>
> I was confused partly because, on Steve's web page for MacTNC 
> <http://www.machamradio.com/software/ni5v/mactnc/index.html>, it is 
> presently (July 16, 2004) stated that "The most recent version is 
> Version 1.1."  Also, Steve wrote to me on November 12, 2003, that 
> "Unfortunately, it looks like I'll be unable to continue updates to 
> MacTNC. The third-party serial class used to link into the BSD 
> lower-level serial routines is totally  broken in the latest compiler 
> and won't work with Panther.  If the author  of that class updates it 
> for the newer compilers, perhaps other changes and updates can be made 
> to MacTNC -- but if that doesn't happen, MacTNC would need to be 
> completely rewritten."
>
>
> Thanks for helping to straighten me out.
>
>
> 73 de Chuck W1HIS