Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!iuvax!valnet!joseph
From: joseph@valnet.UUCP (Joseph P. Hillenburg)
Newsgroups: comp.sys.amiga
Subject: Re: comm programs
Message-ID: <am67o1w163w@valnet>
Date: 8 Sep 90 21:33:21 GMT
References: <1990Sep7.203306.11973@cbnews.att.com>
Organization: Valley BBS Network
Lines: 30

My experience with NComm has been bad. Here are the faults I found with 
it:

1) It doesn't have many options, like JR-Comm. JR-Comm is full of 
   options, and that makes it very useful. I'd rather have my terminal
   set up my way, instead of the way the author wants it.

2) It's based on Comm. That alone speaks for itself.

3) Doesn't recogne XPR's properly. Sure, it accepts xprzmodem right, but  
   I added xprkermit.library, and it wouldn't take it. The program wasn't 
   even aware of it!

4) It's scripts are nonstandard. With VLT using ARexx, and ARexx possibly
   coming soon for JR-Comm, that makes those two programs far more useful
   than NComm.

5) It can only support 44 phone entries. JR-Comm supports am infinite 
   number of entries, only limited by RAM, and VLT also does, using 
   macros, but I can't get use to it. (Although this make the program 
   VERY flexible.


 -Joseph Hillenburg (Sultan of Asm)
INET: joseph@valnet.uucp            |MAIL: 1709 West Gray
UUCP: ...!iuvax!valnet!joseph       |MAIL: Bloomington, IN 47401
AT&T: 1-812-336-2969                |MAIL: United States
CompSci BBS: 3/12/24 1-812-876-4407 9:30 pm-7:30 am |Mail replies requested
              Those aren't bugs! Just undesirable features!
n't bugs! Just undesirable features!