[comp.protocols.tcp-ip.ibmpc] Are any of the IP packages for PC adaptable to other systems?

DEDOUREK@UNB.CA (11/10/88)

We have some PC's and some Unix systems built around the ICM32000
computer boards (which use the National 32016 processor).  The
national boards came with a binary only release of Unix System V,
with no TCP/IP support.  We are currently investigating the
possible use of the KA9Q package as an inexpensive method of
communicating among these systems, usinging asynch lines and slip.
I would appreciate comments on the following:
1) Has the KA9Q package been used in a Multi-User Unix environment?
   What modifications have been made to do this.
2) Are any of the other packages discussed in this group adaptable
   to this use? (e.g. NCSA)
3) Are there other packages of which we are not aware?
4) Are there other groups (accessible to BITNET) which might provide
   useful information on this topic?
This being a University, and the need for communication among these
systems being of a light sporadic nature, a heavy investment in
hardware/software cannot be justified at the present time.  Therefore
we are looking for rather economical solutions.

John DeDourek
School of Computer Science
University of New Brunswick
Fredericton, N.B. CANADA E3A 4Z6

E-mail:
dedourek@unb.ca     domain address
dedourek@unb        BITNET/NETNORTH address
dedourek@unbmvs1    BITNET/NETNORTH address for machines with old tables

timk@NCSA.UIUC.EDU (Tim Krauskopf) (11/14/88)

The TCP/IP in NCSA Telnet is specifially designed for non-blocking,
non-preemptive, event driven systems.  This is perfect for DOS and the
Macintosh.  One side-effect is that the code does not require mutual
exclusion or context saving anywhere.

Lightweight, but not very UNIX adaptable.


Tim Krauskopf                timk@ncsa.uiuc.edu (ARPA)

National Center for Supercomputing Applications (NCSA) 
University of Illinois, Urbana-Champaign