inet sockets on ibmpc:what software and where

Thu May 30 21:08:57 AEST 1991

>From JAMES at UK.AC.POLY-EAST-LONDON Thu May 30 08:55 GMT 1991
Via:        spidergate    ; 30 May 1991 08:54:56-GMT
Sorry I posted to alt.sources to start with and annoyed some of you.
Hope this is in the right place now.

The question was:

I would like to know how to use bsd type internet sockets on a pc. I have access to the internet for ftp so any pd libraries on there would be especially appreciated, otherwise what commerically avail

My preference is for turbo C, and the stuff must work on this grotty XT
Will I need to replace the clarkson packet driver?

public domain stuff first.  Someone else made a similar request and got a good answer..here it is.
--
> I'm looking for some public domain TCP/IP implementation for the IBM/PC that
> will allow me to make TCP/IP calls from my programs, (calls like "write",
> etc.).  C preferred.

The two most common are:

PCIP (from CMU and Harvard [long story about lineage omitted])
	husc6.harvard.edu:pub/pcip [128.103.1.56]

and NCSA Telnet (also modified by Clarkson U and called CUTCP)
	ftp.ncsa.uiuc.edu. - the original source; up to ver 2.3b15 or so.
	omnigate.clarkson.edu - V2.2TN 3270 version; also CUTCP versions

A newer one is called WATTCP and comes from U of Waterloo.
	sunee.uwaterloo.ca:/pub/wattcp/ [129.97.128.196]

Also, a nice PC SNMP package by crosson at cam.nist.gov (Bob Crosson)
comes with source and is therefore a good source of IP/UDP layer code:
	enh.nist.gov:snmpsrc1.tar_z [129.6.16.1]

Some Comments:

PCIP has weak TCP support, it leans heavily in the direction of UDP-
  based applications.  PCIP libraries create small stand-alone apps
  (and there are a ton of them!)  It is somewhat dated, and even one
  of the original hackers-upon-it has suggested that there are now
  better ways to go.

NCSA Telnet has strong TCP support (especially multiple TCP ports which
  PCIP lacks), but has scrimped on UDP (only allows one UDP port at a
  time; mainly for BOOTP and RARP).  It creates one large (monolithic)
  application with all your desired smaller apps (like FTP) built-in.

  I have found that the NCSA Telnet Version 2.2D (aka 2.2TN) is easy to
  hack upon, but you have to read all the sources closely as there is
  little programmer documentation.  However, I was able to strip down the
  libraries, port to Zortech C and create small apps like "ping" with
  it.

CUTCP - later versions are not provided with source, so no hacking.

WATTCP takes a minimalist approach (which I favour), but the early
  version of the library I played with had some bugs.  That early
  version (with no source for the libs) has since been upgraded and
  released with source, but I haven't had time to reinvestigate.  I think
  this package "has promise" and I intend to do some work with it.

SNMPMON (PC SNMP) - I haven't had a chance to evaluate this yet.

--
         "Remember, only *you* can prevent emacs!"
bmw at isgtec.uucp  [ ..uunet!utai!lsuc!isgtec!bmw ]  Bruce Walker

---
The author of this wattcp thang responded to my request.  Here's what he said:

Commercial versions rely on MS C.  The following are the two free 'socket'ish
packages for DOS.  Both use turbo C.

Phil Karn's KA9Q or NOS compiles under Turbo C and feels very much like
Unix for programming and later using those tools.  It includes multitasking
and its own simple shell.  You link your module in.  A typical configuration
of NOS compiles to about 400 to 500 Kbytes.  Ftp source from
flash.bellcore.com.

My Waterloo TCP package also compiles under Turbo C but is
intended for single applications like FINGER, LPR, PING, or simple servers.
It does not include a multitasker and not nearly as flexible as NOS, but
it is very useful for some applications where NOS is not.  A typical
application under my system is about 30 Kbytes.  Ftp source from
sunee.uwaterloo.ca in pub/wattcp and get src.zip for the applications
source or may15.zip for the kernal source.

To get a feel for the difference, NOS takes quite a while to program a new
feature and you must then load the entire package to run that command.  My
stuff is often used as a quick command, eg. LPR up this file then exit.

Both packages use Clarkson packet drivers.

Erick
--

As for commerical stuff:

bj at inmos.co.uk & alan at oetll.scf.lmsc.lockheed.com both informed me about sun nfs (cliff.ustein at east.sun.com for more details) and pc/ftp from ftp software (info at ftp.com for details)

Hewlett-Packard have a nice commercial implementation of Sockets
that runs on MS-DOS and OS/2.  The libraries will work with Turbo C, I believe.

I've seen HP LAN cards work with the Clarkson packet driver, but
haven't tried their protocol stack with it.

You'll need to pay extra if you want a disclaimer!  :-)

Paul Gillingwater, paul at actrix.gen.nz

We purchased Excelan's Socket Library, for MSC6.0/5.1, Lattice C, etc. It is commercial, though it should work with any vendors TCP/IP implementation.

Barry B. Floyd ( barry_floyd at mts.rpi.edu )
--

Try sunee.uwaterloo.ca and look for /pub/wattcp. Get the .zip files. You need only the latest of the "dated" files.

Tarjei Jensen <tarjeij at no.uio.ulrik>
--

FTP Dev kit, of course, from FTP Software Inc, about $500, try jsl at ftp.com

Your DOS should be >= 3.1. FTP is written in MicroSoft 5.x, and there is no
claim from MicroSoft that it can be mixed with Borland.

>Will I need to replace the clarkson packet driver?

No, but I think you will need to buy the generic TCP/IP (ethdrv) for PC as well!

hagen at ch.cern.cernvax
--

Thanks to everyone who responded
===============================================================================
janet: james at pel   internet:james%pel at nsfnet-relay
James Andrews, User Support, Computer Centre, PEL, Longbridge Road,
Barking, Essex, RM8 2AS                       Tel:081-590 7722 x2089
===============================================================================