This is Version 3 of the Software Development Kit for I-Net 225.

A variety of changes and improvements have occured, due to user
input. The detail of those changes can be found in the file
CHANGES in this directory.

This archive and its contents are Copyright © 1996 by Interworks.

Below is the README from Version 2 and Version 1 of the SDK.

Michael B. Smith
for Interworks, Inc.
April 9, 1996
===============================================================================

This is Version 2 of the Software Development Kit for I-Net 225.

A variety of changes and improvements have occured, due to user
input. The detail of those changes can be found in the file
CHANGES in this directory.

This archive and its contents are Copyright © 1996 by Interworks.

Below is the README from Version 1 of the SDK.

Michael B. Smith
for Interworks, Inc.
April 7, 1996
===============================================================================
This is the Software Development Kit for I-Net 225, from Interworks.

This archive and its contents are Copyright © 1996 by Interworks.

Parts of this shared socket library and the associated header files are
derived from code which is:

-------------------------------------------------------------------------------
Copyright (c) 1980-1995 Regents of the University of California.
All rights reserved.

Redistribution and use in source and binary forms are permitted
provided that the above copyright notice and this paragraph are
duplicated in all such forms and that any documentation,
advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed
by the University of California, Berkeley.  The name of the
University may not be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
-----------------------------------------------------------------------------

This archive is being released to the public as freely-distributable, which
means that the files may be copied and spread in any manner, but that
Interworks still retains any and all copyrights and complete ownership of the
archive.

Other restrictions may be applied as they see fit.

The main restrictions are

	These files are provided AS-IS, with no warranty either expressed or
	implied, and all risk is the responsibility of the user.  Neither
	Interworks, nor any of its employees nor contractors shall be held
	liable in the event of any problems either with the files provided,
	or with any program(s) created using the supplied files or other
	information.  Use of the supplied files or other information implies
	acceptance of risk on the part of the user.

and

	This archive must remain intact, and AS-IS.  No files may be modified,
	added, or removed.

There are 4 subdirectories in this archive:

	include - Do NOT copy these to your INCLUDE: directory.  Simply add an
		  'INCLUDEDIR=' directive to your compiler options to point to
		  these files when compiling network code.

	examples - Some simple examples of network code.

	lib - 2 link libraries to make porting network code easier.  These are

		unixS.lib - SAS/C specific UNIX compatibility functions.  See
			    'unix.doc' for AutoDocs for these functions.  Yes,
			    some of these are duplicates of routines in the SAS
			    libraries, but they are more UNIX compatible than
			    the SAS versions.

		rpc.lib   - contains RPC and XDR routines.  See any decent UNIX
			    docs for their use.  If you don't know how to use
			    them, you probably don't need to.

	password - files & information so you can build your own library for
		   handling passwords for the network.	No .library file is
		   provided, but with the included info, one of our Beta
		   testers created a password.library file that worked fine on
		   the first try, and it only took 20 minutes!

Two files in this directory provide AutoDoc entries for routines in the socket
library (socket.doc), and the unixS.lib functions (unix.doc).

Please read the README files in each subdirectory, particularly the one inside
the "examples" directory.


Good luck!

	- Jim Cooper
	  Lead Programmer, I-Net 225
	  March 28, 1996
