From: BBS Adminstration Account <bbsadm@sosco.sco.COM>
Subject: Q&A: SCO TCP/IP Release 1.2 and SCO NFS Release 1.2
Organization: XeniTec Consulting Services, Kitchener, ON, Canada
Date: Wed, 14 Oct 1992 14:22:10 GMT
X-Mailer: SCO System V Mail (version 3.2)
Followup-To: biz.sco.general

			SCO TCP/IP Release 1.2
				and
			  SCO NFS Release 1.2


			Questions and Answers

			   September 1992



Intended to improve your working knowledge of SCO TCP/IP and SCO NFS, these
questions and answers will help you better understand technical issues pertinent
to building fully distributed networks of heterogeneous systems. The questions
and answers are arranged in the following categories:

o  General Concepts and Terminology
o  SCO TCP/IP 
o  SCO NFS 
o  Programmatic Interfaces
o  System Requirements


General Concepts and Terminology
--------------------------------

1.	What is TCP/IP?

In general terms, TCP/IP started as the family of communications protocols that
the Defense Advanced Projects Research Agency (DARPA) adopted as the standard
for handling connectivity between computers on the ARPAnet.  The TCP/IP family
includes the baseline protocol sets, Internet Protocol (IP) and Transmission
Control Protocol (TCP), as well as other protocols including User Datagram
Protocol (UDP), Internet Control Message Protocol (ICMP), and others. TCP/IP
provides specifications for electronic mail, remote logins, file transfers, and
more.

As TCP/IP has evolved over time, additional protocols have been added to the
TCP/IP suite, such as Simple Network Management Protocol (SNMP), Berkeley Line
Printer Deamon distributed printing (LPD), and Point-to-Point dialup protocol
(PPP).  These protocols add considerable robustness and advanced features to
TCP/IP networks.

Today TCP/IP is widely used in corporate environments -- the interconnected
networks that are the descendents of the ARPAnet connect over 700,000 sites -- 
and there is a broad market of compatible TCP/IP-based products, ranging from
cabling and repeaters, to routers and bridges, to built-in or add-on connections
to all major computer OEMs' product lines.  TCP/IP has become the open systems
standard for configuring networks composed of a wide variety of machines and
operating systems.

2.	What is NFS?

NFS (Network File System) is the established, standard distributed file system
for open systems networks.  NFS is a good compliment to TCP/IP transports,
helping to create a larger integrated system out of machines networked together.
Originally developed by Sun Microsystems, NFS allows file sharing between
machines across TCP/IP LANs.  File sharing capability allows applications and
users to transparently access remote files as if they were local.  NFS is a
part of Sun's distributed environment system called Open Network Computing
(ONC), which also includes a remote procedure call mechanism and compiler (RPC),
and a data format mapping mechanism called eXternal Data Representation (XDR),
both of which are used by NFS.

3.	What is SCO TCP/IP?

SCO TCP/IP is an implementation of TCP/IP and related protocols for  SCO
operating systems.  SCO provides separate SCO TCP/IP software packages for the
SCO UNIX System V/386 Release 3.2 and SCO XENIX 386 Operating Systems, and
includes SCO TCP/IP for the SCO UNIX System in SCO Open Desktop, the integrated
open systems environment.  

Based on the latest functional and performance improvements of 4.3BSD TCP/IP,
SCO TCP/IP has been adapted to run within the Streams framework, and with the
LAN card Link Layer Interface (LLI) of SCO XENIX 386 and SCO UNIX System V/386.
It provides high-performance network connections to a wide variety of operating
systems and computers, over various types of physical connections.  SCO TCP/IP
provides network login, file transfer, network printing, and network
mail-transfer capabilities for end users.  It also provides programmers with a
high-level interface to network datagram and virtual-circuit services.

4.	What is SCO NFS?

SCO NFS is an implementation of Sun's Open Network Computing (ONC) system,
including NFS and related protocols for the SCO UNIX System V/386 Release 3.2
Operating System.  SCO NFS is also included in SCO Open Desktop.  SCO NFS gives
SCO UNIX System users fast, network-wide file- and data-sharing capabilities,
and allows them to share files and data easily over networks -- even
heterogeneous configurations.  With SCO NFS, users on one machine can
transparently access files and applications residing on a remote machine.



SCO TCP/IP 
----------

5.	What protocol sets and utilities are included with SCO TCP/IP?

TCP		Transmission Control Protocol (RFC793)
UDP		User Datagram Protocol (RFC768)
IP		Internet Protocol (RFC791)
ARP		Address Resolution Protocol (RFC826)
ICMP		Internet Control Message Protocol (RFC792)
RIP		Routing Information Protocol
RARP		Reverse ARP
TFTP		Trivial File Transfer Protocol
NTP		Network Time Protocol
SLIP		Serial Line IP Streams module
PPP		Point-to-Point Protocol *
SMTP		Simple Mail Transfer Protocol (RFC821)
Loopback	Loopback and test Streams module
SNMP		Simple Network Management Protocol *
BIND		Berkeley Internet Domain name service
		(client and server support)
LPD		Berkeley Distributed Print services *
gated		Enhanced Routing Service *
bootp		boot protocol *

SCO TCP/IP utilities include:

rcmd 	rsh 	rlogin 		rcp 	rwho 	ruptime 
rexec 	ping 	netstat 	finger 	tftp 	TELNET (RFC854) 
mail 	hostname		whois 		FTP (RFC959)	
...and many others

*Only available in SCO TCP/IP for the SCO UNIX System.

6. 	Can SCO TCP/IP be used to connect to machines running other 
        vendors' TCP/IP products?

Yes.  SCO TCP/IP offers high-performance network connections to any system that
runs an implementation of TCP/IP.

7.	What commercial network applications or distributed systems are 
	supported over SCO TCP/IP?

SCO TCP/IP is the standard protocol for SCO XENIX, SCO UNIX System V/386, and
SCO Open Desktop.  There are a wide variety of network applications available
that support SCO TCP/IP connections, including most major third-party databases
such as Oracle, Ingres, Unify, Progress, and Sybase.  The following SCO products
utilize SCO TCP/IP as a network transport subsystem.  Refer to the SCO Directory
for additional products.

o  SCO Xsight -- Provides X11 windowing environment over SCO TCP/IP

o  SCO NFS -- Provides distributed file system for SCO UNIX Systems 
   in TCP/IP environments

o  Microsoft LAN Manager for UNIX Systems -- Provides MS-DOS and OS/2
   distributed file system connections from UNIX servers 

o  JSB MultiView DeskTop -- Provides Microsoft Windows interface to 
   MS-DOS and UNIX System applications

o  SCO XENIX-NET -- Provides distributed file system for SCO XENIX 
   in TCP/IP environments.  Compatible with Microsoft LAN Manager


8.  	What software do I need on an MS-DOS or Windows-based machine 
        to connect to machines running SCO TCP/IP?

Any TCP/IP software implementation available for MS-DOS or Windows-based
machines should be able to communicate with SCO TCP/IP and SCO TCP/IP utilities.
TCP/IP packages for MS-DOS and Windows are available from Novell, FTP Software,
Wollongong, and Racal Datacom.

9.  How many remote logins (telnet and rlogin) does SCO TCP/IP  support?

SCO TCP/IP for SCO XENIX and SCO TCP/IP for the SCO UNIX System support
different numbers of remote logins.  Release 1.2 of SCO TCP/IP for the SCO UNIX
System supports 254, which is the maximum number of simultaneous socket
connections available.  Of course, this would require a lot of memory, and the
power to process a lot of users.   Remember that the sockets and queues are
system resources;  If you use any of the sockets for something else (like
network daemons), they aren't available for use by  rlogin.

Release 1.2 of SCO TCP/IP for SCO XENIX supports 32 remote logins, which is the
number of pseudo tty's that are supported. 

10.	How does SCO TCP/IP impact the performance of SCO systems?

While this is difficult to quantify, SCO TCP/IP generally has minimal impact on
a system.  Using TCP/IP to run an application places a similar load on the
system as using an intelligent serial port connection.

11.	Does SCO TCP/IP support distributed printing?  What is LPD?

Yes.  SCO TCP/IP for the SCO UNIX System allows optional support of LPD, the
standard distributed print spooling subsystem supported by BSD4.3.  By
supporting  the lp, lpstat, and cancel commands, SCO TCP/IP's LPD subsystem
supports heterogeneous distributed printing between SCO and other  BSD
LPD-conformant systems such as SunOS, PC-NFS, FTP's TCP, and  HP-UX.

SCO TCP/IP for SCO XENIX supports distributed printing through the rcmd
utility.

12.	Does SCO TCP/IP support routing between networks?

Yes.  SCO TCP/IP includes a standard IP (Internet Protocol) network layer which
supports TCP/IP routing between networks.  This is useful for connecting
Token-Ring and Ethernet networks, for connecting remote networks via
asynchronous SLIP or PPP links, and for controlling network traffic. 

13.	Can SCO TCP/IP be used to connect remote TCP/IP LANs together?  
        What are SLIP and PPP?

Yes.  Serial Line Internet Protocol (SLIP) and Point-to-Point Protocol (PPP)
allow bridge and wide-area gateway support between TCP/IP networks via standard
serial ports and modems.  SLIP is oriented toward non-switched (leased) lines,
while PPP is oriented toward switched (dial-up) lines.

The SLIP and PPP drivers provided with SCO TCP/IP for the SCO UNIX System, and
the SLIP driver provided with SCO TCP/IP for SCO XENIX, are inexpensive
alternatives to dedicated bridges or routers to connect remote LANs. These
drivers will work with any serial card supported by standard XENIX or UNIX
System serial I/O drivers.  Both environments support up to four lines at a
time. 

SCO's SLIP and PPP both use Van Jacobson header compression algorithms for
improved throughput and response.  SLIP support conforms to RFC 1144 and PPP
support conforms to RFCs 1171 and 1172.  PPP also features integrated SCO
dialing support.

Note that new RFCs for PPP standards have been developed (RFC 1331 and 1333),
and SCO will add support for these in future releases of SCO TCP/IP for the SCO
UNIX System.

14.	What is gated?  Why is it useful for routing control?

SCO TCP/IP for the SCO UNIX System supports gated, an advanced routing program
originally developed at Cornell University.  Gated enables the administrator to
set up the system to selectively act as an adaptive router -- learning of 
changes in network topology and status, and passing that information on to 
external networks, public and private.  Gated combines standard RIP, HELLO, 
and EGP routing protocol support with a set of rules that constrains how it 
advertises routes to other gateways.  RIP and HELLO, the interior gateway 
protocols, are used to collect, and act on, routing and status information 
from within a network.  This dynamic routing information is also utilized in 
advertising routes to other networks using EGP, the exterior gateway protocol.

The rules allow the administrator to specify which systems are advertised and 
to artificially raise the ``distance'' metric to control network traffic flow.

15.	What network management facilities does SCO TCP/IP include?  
	What is SNMP?

SNMP (Simple Network Management Protocol) is a standard protocol used by network
management stations to monitor TCP/IP networks.  It defines a set of variables
that are kept to monitor and control network nodes.  SCO TCP/IP for the SCO UNIX
System includes an SNMP agent that supports MIB II (Management Information BASE
II), a new,  expanded set of variables.  SCO's MIB II support conforms to the
mandatory sections of the RFC 1258 Internet standard.  SCO TCP/IP also includes
a command-line-based management facility for obtaining and displaying network
statistics.

16.	What is bootp?  Does SCO TCP/IP support diskless booting?

Bootp is a TCP/IP protocol designed to support network booting of diskless
devices and other centrally configured/controlled network devices.  Bootp can
supply a diskless device with a boot file and information required to utilize
resources in an internetworked environment.  Bootp is specified in RFC951, with
extensions specified in RFC1048 and RFC1084.

Bootp was designed as a more complete single-protocol replacement for an earlier
network bootstrapping scheme that utilized the RARP (RFC903) and TFTP (RFC783,
RFC986) protocols.  RARP was used by a diskless node to determine its Ethernet
address and the address of a boot server, then TFTP was used to transfer a boot
image.  Bootp incorporates these functionalities in a single, more efficient
protocol.

SCO TCP/IP for the SCO UNIX System (included in SCO Open Desktop 2.0) includes
the bootp and rarpd protocols to support network booting of the various network
devices that require them (i.e.  X terminals, printers, perhaps even DOS
machines).  SCO does not currently support network booting of machines running
SCO operating systems.


17.	Does SCO TCP/IP support e-mail?

Yes.  

o  SCO TCP/IP for the SCO UNIX System supports standard e-mail 
   through sendmail or MMDF II mailers and SMTP and UUCP delivery agents.  

o  SCO TCP/IP for SCO XENIX supports e-mail through sendmail 
   and SMTP (Simple Mail Transfer Protocol).

SCO TCP/IP for SCO XENIX includes sendmail Release 5.59, and SCO TCP/IP for the
SCO UNIX System includes sendmail Release 5.65.  Both SCO TCP/IP packages take
advantage of routed and gated,  allowing the use of the TCP name server for
simplified configuration management. SCO TCP/IP's SMTP delivery agent conforms
to MIL-STD 1781 and the minimum requirements of RFC821 and RFC822.

18.	Can I use TCP/IP to connect to other types of e-mail systems?  How?

Yes.  TCP/IP SMTP gateways are either included in or available for most
commercial e-mail packages.  Contact your e-mail vendor for more information
about your particular package.

19.	What are the differences between sendmail and MMDF II?

Sendmail is primarily for UNIX System environments that already use sendmail,
and for XENIX environments that need network e-mail.  For SCO UNIX System sites,
SCO highly recommends using Multi-Channel Memorandum Distribution Facility II
(MMDF II).  MMDF II is considerably more powerful and manageable, and provides
many features not available in sendmail.  These features include:

o  Full conformance to ARPAnet mail standards as specified in 
   RFC822, RFC733, and RFC974.

o  Highly manageable configuration language. MMDF II is composed of
   easy-to-understand, keyword-based configuration files. Separate 
   configuration files control each aspect of the system, making 
   configuration much more intuitive and easy to understand than sendmail.

o  Load control and management.  MMDF II's multi-queue design 
   provides implicit load control and management.  Unlike sendmail, 
   MMDF II is designed to degrade gracefully under a heavy load or 
   the failure of one or more of its delivery channels.

MMDF II and sendmail are both highly configurable mailers that can be used to
reach other sites, gateways, and networks.  They both work with the standard SCO
mail user interface programs, such as mail, opmail, and the SCO X11 Motif mail
client programs, to deliver mail over the network.  Both MMDF II and sendmail
allow users to implement the user@site.domain style of address, as well as
standard local and uucp-type addresses.

SCO only supports sendmail configurations that are generated with SCO-supplied
installation scripts, which allow configuration of local, uucp, and TCP-based
connections.

20.	Does SCO TCP/IP conform to the U.S. government's C2 security 
        provisions when used on SCO UNIX System V/386?

No.  SCO TCP/IP on SCO UNIX System V/386 does not currently conform to C2
security provisions.

21.	What are the new features in Release 1.2 of SCO TCP/IP for SCO XENIX?

The Release 1.2 Update to SCO TCP/IP for SCO XENIX provides performance
improvements with new capabilities:

o  Added LAN card support
o  Updated telnet and telnetd for wider connectivity
o  Updated sendmail (to Release 5.59)
o  Updated SLIP support

22.	What are the new features in Release 1.2 of SCO TCP/IP for 
	the SCO UNIX System?

The Release 1.2 Update to SCO TCP/IP provides performance improvements with new
capabilities:

o  Berkeley lpd support
o  SNMP agent with MIB II support
o  gated support
o  bootp support
o  Updated telnet and telnetd for wider connectivity
o  Updated sendmail (to UCB Release 5.65)
o  Updated SLIP support
o  New dial-in/out PPP asynchronous support
o  Network Time Protocol (NTP) support
o  Support for additional LAN cards

23.	What is included in the SCO TCP/IP package?

The SCO TCP/IP Runtime System includes Release and Installation Notes, User's
and Administrator's Guide, Command Reference, and 96tpi dshd 5.25S or 135tpi
3.5S diskettes.

The SCO TCP/IP Development System includes Release and Installation Notes,
Programmer's Guide, Programmer's Reference, and 96tpi dshd 5.25S or dsdd 3.5S
diskettes.


SCO NFS
-------

24.	What features and programs does SCO NFS include?

In addition to providing the NFS distributed file system, SCO NFS includes other
standard Sun ONC components:

o  Standard RPC and XDR libraries for invoking procedures and 
   transmitting data remotely

o  Lock Manager for file and record locking, including System V 
   record locking 

o  Remote Procedure Call Generator (RPCGEN) for writing subroutine 
   calls on remote systems, and Remote EXecution (REX), for executing 
   programs remotely

25.	Is TCP/IP required to run SCO NFS?  Which implementations of TCP/IP are
	compatible with SCO NFS?

Yes, TCP/IP is required to run SCO NFS.  SCO TCP/IP is the networking foundation
upon which SCO NFS is based, providing file-sharing capabilities across TCP/IP
LANs.  While it is possible for SCO NFS to run over other vendor's TCP/IP
implementations in SCO UNIX System environments, SCO is not aware of any vendors
who currently support SCO NFS.

26.	Is SCO NFS compatible with other implementations of NFS?

Yes, SCO NFS is compatible with Sun Microsystems' NFS Version 3.2.  SCO
regularly participates in cross-vendor RconnectathonS test sessions to ensure
interoperability between SCO NFS and other vendors' NFS implementations.

27.	Is NFS file sharing possible between the SCO UNIX System and 
	MS-DOS or Apple MacIntosh systems?  Does SCO NFS support PC-NFS?

Yes, NFS products are available for both MS-DOS and MacIntosh environments.
Products such as Sun Microsystems' PC-NFS and other NFS vendors' MS-DOS NFS
software are supported through the pcnfsd program (NFSSRC Version 4.1) supplied
with SCO NFS.  Note that MS-DOS-based NFS implementations usually only allow the
MS-DOS machines to be NFS clients, not NFS servers.

28.	Does SCO NFS support both client and server functions?

Yes, SCO NFS provides both client and server capabilities.  Client machines may
request resources and locally mount file systems provided by remote servers.
SCO NFS-based machines can be configured to serve as both clients and servers
simultaneously.

29.	Does SCO NFS support diskless workstations?

No, SCO NFS does not currently support diskless boot.  See question #17 for more
information on diskless booting in TCP/IP environments.

30.	Is SCO NFS available for SCO XENIX?

No.  Because SCO XENIX does not implement File System Switch (FSS), which SCO
NFS requires, SCO XENIX does not support SCO NFS.  SCO XENIX-NET supports
distributed file systems over TCP/IP in SCO XENIX environments.

31.	Can SCO NFS help with administration of a group of systems?  
	What is NIS?

Yes.  With NIS (Network Information Services), formerly known as NFS Yellow
Pages, a group of systems can be administered as a single system from a single
server's configuration files.  This simplifies the often complicated task of
administering TCP/IP networks.  NIS provides an extensible database used by the
TCP/NFS network for storing and accessing system information such as hostnames,
network addresses, and user names, as well as the tools to administer that
database.

32.	What is the NFS Automounter?  What benefits does it provide?

The NFS Automounter is a new facility that allows remote file hierarchies (file
systems and directories) to be automatically and transparently mounted. The
automount program enables users to mount and unmount remote directories on an
as-needed basis.  Whenever a user on a client machine running Automounter
invokes a command that accesses a remote file or directory, such as opening a
file with an editor, the hierarchy to which that file or directory belongs is
mounted.  That hierarchy remains mounted for as long as it is needed.  No
mounting is done at boot-time, greatly reducing the time needed to boot up your
system.

33.	What is the maximum number of inodes supported in an SCO NFS 
	Release 1.2 file system?  What is the maximum number of opened files?

SCO NFS supports approximately 65,500 inodes, and 150 open files.

34.	What are the new features in Release 1.2 of SCO NFS?

Release 1.2 provides the following new features:

o  NIS
o  Automounter
o  Lock Manager performance improvements
o  Long filename support
o  Symbolic link support
o  New /etc/exportfs options
o  Atomic rename support
o  New PCNFS source base

SCO NFS Release 1.2 includes new options to the exportfs command.  These options
allow you to specify NFS access configurations in greater detail than was
previously possible.  For example, you can now specify root privileges for
certain hosts and file systems.

SCO NFS Release 1.2 supports atomic rename capability, a file system enhancement
that extends the list of operations that can be performed on NFS-mounted file
systems.  For example, it was previously necessary to issue several commands to
rename an NFS-mounted file or directory;  this can now be accomplished
atomically (that is, as a single, indivisible operation) using only the mv or
mvdir command.

35.	What is included in the SCO NFS package?

The SCO NFS package includes Release and Installation Notes, Administrator's
Guide, Programmer's Guide and Command Reference, and 96tpi dshd 5.25S or dsdd
3.5S diskettes.


Programmatic Interfaces
-----------------------

36.	What programmatic interfaces does SCO TCP/IP support?  
	Does SCO TCP/IP support BSD Sockets?  TLI?  XTI?

SCO TCP/IP supports three programmatic interfaces: 

1)	The optional SCO TCP/IP Development System provides a 
	4.3BSD-compatible socket library for developing distributed 
	applications.  Sockets use file I/O to perform interprocess 
	communications both locally and across networks using
	TCP/IP protocols.  Within the socket interface, only the 
	AF_INET socket family is currently supported.  

2)	The Transport Layer Interface (TLI) libraries are included 
	in the SCO Streams package for SCO XENIX 386 systems, and 
	in the SCO UNIX System V/386 Development System.

3)	The X/Open Transport Layer Interface (XTI) libraries are 
	included in the SCO UNIX System V/386 Development System.


37.	What programmatic interfaces/services are available with SCO NFS?

SCO NFS includes standard Remote Procedure Call (RPC) and eXternal Data
Representation (XDR) libraries.  RPC allows remote procedures to be invoked as
if they were local subroutines, allows processes running on one machine to call
procedures that execute on remote machines across a network, and relieves the
applications programmer from the details of the underlying network
implementation.  XDR provides a system- and machine-independent format for
representing data transmitted between heterogeneous systems.

38.	Does SCO TCP/IP support NetBIOS?

Yes.  SCO TCP/IP includes an RFC 1001, 1002-compliant NetBIOS protocol module.
Under SCO XENIX this module is accessed through SCO XENIX-NET;  under SCO UNIX
System V/386, it is accessed through SCO's Microsoft LAN Manager for UNIX
Systems.  Future releases of SCO TCP/IP will provide NetBIOS access directly
through XTI with NetBIOS names.

39.	How many TCP/IP sockets can be opened simultaneously?

Up to 256 sockets may be opened simultaneously, limited by the number of minor
devices available, and depending on the Streams configuration.  SCO intends to
increase this number to 1,024 in future releases of SCO TCP/IP for the SCO UNIX
System.

40.	Can developers write applications that use all of the TCP layers?

Yes.  Developers can access the TCP and UDP protocols via the socket library.
They can also use the IP layer, by linking the Raw IP driver into their kernel.
The Raw IP driver is provided in the SCO TCP/IP Runtime System, but is not
linked in by default.  Networking protocols may also be accessed by programs
that ``speak'' TLI.


System Requirements
-------------------

41.	What LAN hardware does SCO TCP/IP for SCO XENIX support?

SCO TCP/IP for SCO XENIX has a built-in set of LLI drivers.  SCO TCP/IP for the
SCO UNIX System includes the separately engineered SCO LLI Driver Disk.

Release 1.2 of SCO TCP/IP for SCO XENIX supports the following cards:

3Com Etherlink I 3C501
3Com Ethetlink II 3C503
3Com Etherlink/MC 3C523
3Com Etherlink/MC 3C523B
Western Digital WD8003E EtherCard PLUS
Western Digital WD8003EB EtherCard PLUS
Western Digital WD8003EP EtherCard PLUS
Western Digital WD8013EBT EtherCard PLUS16
Western Digital WD8013EP EtherCard PLUS16
Western Digital WD8003E/A EterCard PLUS/A
Excelan EXOS 205 
Excelan EXOS 205T
IBM Token-Ring Adapter
IBM Token-Ring Adapter II
IBM Token-Ring Adapter 4/16
IBM Token-Ring Adapter/A
IBM Token-Ring Adapter/A 4/16
All standard XENIX asynchronous tty drivers (via SLIP)

42.	What LAN hardware does SCO TCP/IP for the SCO UNIX System support?  
	What is the SCO LLI Driver Disk?

SCO supplies a separate LLI drivers package for SCO UNIX System and SCO Open
Desktop network environments. This package is included in the box with all SCO
networking products to provide easier integration of multiple-protocol
environments such as TCP/IP and NetBEUI, or TCP/IP and IPX/SPX. Because SCO
continues to add drivers to the SCO LLI Driver Disk, the latest package, Release
3.1, is also available as an EFS (Extended Feature Supplement) for SCO
networking products.  This EFS may be ordered or, for those with SCO Support
contracts, downloaded from the SCO Online Support (SOS) system. 

Release 1.2 of SCO TCP/IP for the SCO UNIX System includes the new SCO LLI
Driver Disk Release 3.1, which provides support for the following LAN cards:

3Com 3C501 EtherLink
3Com 3C503 EtherLink II
3Com 3C503 EtherLink II TP
3Com 3C503-16 EtherLink II/16
3Com 3C503-16 EtherLink II/16 TP
3Com 3C507 EtherLink 16
3Com 3C507 EtherLink 16 TP
3Com 3C523 EtherLink/MC
3Com 3C523B EtherLink/MC
3Com 3C523 EtherLink/MC TP (1)
IBM Token-Ring Network PC Adapter
IBM Token-Ring Network PC Adapter II (short card)
IBM Token-Ring Network PC Adapter II (long card)
IBM Token-Ring Network 16/4 Adapter
IBM Token-Ring Network PC Adapter/A
IBM Token-Ring Network 16/4 Adapter/A
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
Microdyne (Excelan) EXOS 205
Microdyne (Excelan) EXOS 205T
Microdyne (Excelan) EXOS 205T/16
Hewlett-Packard 27250A HPThinLAN Adapter Card/8
Hewlett-Packard 27245A EtherTwist Adapter Card/8
Hewlett-Packard 27247A EtherTwist Adapter Card/16
Hewlett-Packard 27248A EtherTwist EISA Adapter Card/32
Racal Datacomm NI6510
Racal Datacomm ES3210
Compaq 32-bit DualSpeed Token-Ring Controller
Anthem NE3200
Anthem NE2000
Standard Microsystems SMC8003EP EtherCard PLUS Elite
Standard Microsystems SMC8003WC EtherCard PLUS Elite 10T
Standard Microsystems SMC8013WC EtherCard PLUS Elite 16T
Standard Microsystems SMC8013EPC EtherCard PLUS Elite 16
Standard Microsystems SMC8013EWC EtherCard PLUS Elite 16 Combo
Standard Microsystems SMC8013EP/A EtherCard PLUS16 Elite/A
Standard Microsystems SMC8013WP/A EtherCard PLUS16/A Elite 10T/A
Western Digital WD8003 EtherCard PLUS series
Western Digital WD8003 EtherCard PLUS Elite series
Western Digital WD8013 EtherCard PLUS series
Western Digital WD8013 EtherCard PLUS Elite series

SCO TCP/IP for the SCO UNIX System also supports serial lines via SLIP and PPP.
The SLIP and PPP protocol drivers supplied with the SCO TCP/IP Runtime System
use the standard SCO tty device interface, and will work with any serial card
supported by the SCO Serial I/O (SIO) driver.

43.	Which versions of the SCO LLI Driver Disk are compatible with 
	which versions of SCO TCP/IP and other SCO networking products?

The following table shows the compatibility matrix between SCO operating system
versions, SCO LLI versions, and SCO networking product versions.

Where more than one SCO networking product is listed against an LLI version, any
combination of the networking products listed may be simultaneously used over
the common LLI driver set.

SCO XENIX 
Release 2.3.4: 

NO LLI	TCP/IP 1.0.1	XENIX-NET 1.3	Streams Runtime 1.0
NO LLI 	TCP/IP 1.2.0	XENIX-NET 1.3	Streams Runtime 1.0


SCO UNIX System V/386 Release 3.2 Version 2.0
or
SCO Open Desktop Release 1.1:

LLI 1.0.0	TCP/IP 1.1.3	NFS 1.1.1
LLI 1.0.1	TCP/IP 1.1.3	NFS 1.1.1	OSI 1.0.0
LLI 1.0.2	TCP/IP 1.1.3	NFS 1.1.1	OSI 1.0.0	LMU 1.1.0
LLI 3.0.0	TCP/IP 1.1.3	NFS 1.1.1	OSI 1.0.0	LMU 1.1.0


SCO UNIX System V/386 Release 3.2 Version 4.0
or
SCO Open Desktop Release 2.0:

LLI 1.0.0	TCP/IP 1.1.3	NFS 1.1.1
LLI 3.0.0	TCP/IP 1.1.3	NFS 1.1.1   OSI 1.0.0	LMU 1.1.0
LLI 3.1.0	TCP/IP 1.2.0	NFS 1.2.0   OSI 1.0.0	LMU 1.1.0   IPX 1.0
LLI 3.1.0	TCP/IP 1.2.0	NFS 1.2.0   OSI 1.0.0	LMU 2.1.1   IPX 1.0

44.	What do Independent Hardware Vendors (IHVs) need to provide in 
	order to run SCO TCP/IP on their cards?  Specifically, does SCO 
	supply a Link Layer Interface (LLI)?  Is its implementation 
	specification available?

SCO has an LLI driver specification, available through the SCO Developer
Relations Department, that provides the information third-party LAN or WAN
hardware companies need to develop their own LLI drivers for use with SCO TCP/IP
and other SCO networking products.

45.	What are the system requirements for SCO TCP/IP?

SCO TCP/IP Runtime System:

Software:		SCO XENIX 386 Release 2.3 and 
			the SCO Streams Runtime System;  or 
			SCO UNIX System V/386 Release 3.2 

Incremental RAM:     	2 Mbytes (minimum)

Incremental Disk Space: 5 Mbytes


SCO TCP/IP Development System:

Software:  		SCO XENIX 386 Release 2.3 and 
			the SCO Streams Runtime System;  or 
			SCO UNIX System V/386 Release 3.2 and 
			the SCO UNIX System V/386 Release 3.2 Development System 			or SCO XENIX 386 Development System

Incremental RAM:     	N/A

Incremental Disk Space: 1 Mbyte


46.	What are the system requirements for SCO NFS?

Software:		SCO UNIX System V/386 Release 3.2 Operating System 
			and SCO TCP/IP Release 1.1.0 Runtime System

Incremental RAM:     	5 Mbytes (minimum)

Incremental Disk Space: 40 Mbytes (minimum)



For more information on SCO products and services, please contact your sales
representative.

The Santa Cruz Operation, Inc. reserves the right to change or modify any of the
product or service specifications or features described herein without notice.
This product summary is for information only. SCO makes no express or implied
warranties in this summary.

SCO and the SCO logo are registered trademarks of The Santa Cruz Operation, Inc.
in the U.S.A. and other countries. All other brand or product names are or may
be trademarks of, and are used to identify products or services of, their
respective owners.

Copyright (c) 1992 The Santa Cruz Operation, Inc. All Rights Reserved
 							926-000-013 (A) 9/92
Newsgroups: biz.sco.announce