Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!mips!wrdis01!emory!gatech!purdue!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: <1991Apr17.101536@fuggles.acc.Virginia.EDU>
Date: 17 Apr 91 14:15:36 GMT
References: <1881@manta.NOSC.MIL> <1991Apr15.184621.14336@ux1.cso.uiuc.edu> <1991Apr15.170113@fuggles.acc.Virginia.EDU> <280BEBD9.6548@orion.oac.uci.edu>
Sender: usenet@murdoch.acc.Virginia.EDU
Reply-To: marc@Virginia.EDU
Distribution: na
Organization: UVa Academic Computing
Lines: 18

jstern@orion.oac.uci.edu (Jeff Stern) writes:
>(This is NOT directed at anyone in particular, PLEASE) BUT, I have paid
>alot more for software from "professional, supportive, (you fill in the
>blank)" companies, and gotten the same response! :) So for the money...

So far, the support Brad Clements has given CUTE/CUTCP is comparable
to that afforded many commercial products, but he explicitly disavows
all responsibility to continue that support.  I tend to think that
the product is mature enough now that whether or not he'll continue
to fix bugs and correct critical functional deficiencies is not such
an important issue.

But if you need to do something special-purpose with it (port
whois or webster or finger or add a new way of getting the
workstation's IP address or whatever), you can't.  And with NCSA's
product (that's what we were comparing it to, right?), you can.

    -- Marc Rouleau