Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven!uvaarpa!murdoch!fuggles.acc.Virginia.EDU!mer6g
From: mer6g@fuggles.acc.Virginia.EDU (Marc Rouleau)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: NCSA vs CUTCP. What's the difference?
Message-ID: <1991Apr15.170113@fuggles.acc.Virginia.EDU>
Date: 15 Apr 91 21:01:12 GMT
References: <1881@manta.NOSC.MIL> <1991Apr15.184621.14336@ux1.cso.uiuc.edu>
Sender: usenet@murdoch.acc.Virginia.EDU
Reply-To: marc@Virginia.EDU
Distribution: na
Organization: UVa Academic Computing
Lines: 22

berger@iboga (Mike Berger) writes:
|Telnet doesn't seem to be a high priority for NCSA anymore.  Note
|that the latest version is in its 13th or so Beta-test implementation!
|Clarkson came out with a packet driver version much sooner.  NCSA is
|unlikely to come out with 3270 support in the foreseeable future (we
|need that even if everybody else doesn't).
|
|Clarkson provides more active support and a more robust product.

But they *don't* provide source.  From our point of view that's a
crucial failing.  Brad Clements has taken great pains to point out
that he does not support this product in any official capacity.
The official Clarkson attitude seems to be "use it at your own risk".
In other words, if it's broken in your environment Brad'll fix it
if he feels like it, but under no circumstances will you be allowed
to fix it yourself.  And if you need to modify it to do something
that's important to your site but not to Brad, you're just out of
luck.

Sigh.

    -- Marc Rouleau