Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!m.cs.uiuc.edu!vela!srodawa
From: srodawa@vela.acs.oakland.edu (Ron Srodawa)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: NCSA vs CUTCP. What's the difference?
Message-ID: <5716@vela.acs.oakland.edu>
Date: 8 Apr 91 21:03:56 GMT
References: <1881@manta.NOSC.MIL>
Reply-To: srodawa@vela.acs.oakland.edu (Ron Srodawa)
Distribution: na
Organization: Oakland University, Rochester MI
Lines: 24

In article <1881@manta.NOSC.MIL> psm@manta.NOSC.MIL (Scot Mcintosh) writes:
>Can someone enlighten me on the history behind this
>seeming schism?

NCSA began as just that, a program from the National Center for Supercomputer
Applications at UIUC.  Clarkson picked it up and added several improvements.
These included support of the packet driver spec, 3270 emulation, Turbo C
compatability, bug fixes, environment variable specification of the Config.Tel
file location, etc.  The real NCSA group chose to not accept all these improve-
ments.  That cast the die for two divergent products.  Clarkson then renamed
theirs CUTCP to avoid confusion.  The lack of source from Clarkson happened
independently of all that.  It was available freely for the earlier versions.
You can blame that on overzealous university attorneys.  These are my
personal impressions of what has happened.  Perhaps others see it differently.

It is too bad that NCSA and Clarkson can't combine their efforts for a single
unified program.  Being universities, they have meager resources.  It would
be nice if those resources could be conserved by joint program improvements.

-- 
| Ronald J. Srodawa               | Internet: srodawa@vela.oakland.edu      |
| School of Engineering and CS    | UUCP:     srodawa@vela.UUCP             |
| Oakland University              | Voice:    (313) 370-2247                |
| Rochester, Michigan  48309-4401 |                                         |