[comp.unix.xenix.sco] TCP/IP on XENIX 386 : SUMMARY

s892024@minyos.xx.rmit.oz (Admiral Richard Muirden) (10/22/90)

hi,

Last week I posed a series of questions about SCO's TCP/IP product for 
Xenix 386. Here is the summary of replies that I received.


---

Date: Wed Oct 17 10:11:08 1990
From: lance%uunet.uu.net@munnari.oz

Subject: Re: SCO TCP/IP for XENTX Runtime System: OPINIONS/COMMENTS WANTED!

s892024@minyos.xx.rmit.oz (Admiral Richard Muirden):
> hi,
> 
> Today I was given a blank order form and asked to order SCO's TCP/IP. Now
> this is all very nice but I'd like to know how well [or badly] it performs
> on a 386 system. We are running SCO Xenix 2.3.2 on an 80386/20.
> 
> Some things I would like to know:
> 
> * What is the latest version available

Several months ago I received CP/IP RTS 1.0.1 (this is for Xenix)  The
Unix version is 1.1.1 and they are NOT interchangable.  There is a free
upgrade (may be in the latest release) that modifies the scheme to
prevent two systems using the same serial numbered program.  Now it only
checksonce,apretly saving a lot of system time and makng it more efficient.

> * What are its features (ie: telnet, rlogin, ftp, else?)

here is SCO's list

rsh, rlogin, rcp, TELNET, FTP and other utilities
NetBIOS support

> * What are its limits?
> * Have you found any bugs in the s/w?

In the controlled release I could never get the Sendmail package to work
correctly. Apparently I couldn't set the sendmail.cf file properly. 
WHen I installed the final version I let out the sendmail package, which
is ok now since my systems serves PCs and Mac but no other Unix boxes. 
I use Smail2.5 for routing and that seems fine.  If I go to other unix
systems I may try to switch to Smail3.1 (but I was told that I may need
the TCP devsys to get that to work properly).

> * Is there a better (cheaper?) product availble that will run on SCO Xenix.

I don't know the price, but I think Excelan makes a product that works
with Xenix

> * Will it run with a 3Com Etherlink I (3C501) or Etherlink II (3C503) without
>   problems?

It claims to.  It also has a 3Com523 driver but without support.  I have
a WD8003e card in my system.


****** ALSO, you need SCO Streams to run tcp/ip.  Thi costs about $100 US.

> 
> Also we are looking at getting the runtime system. Will this have all I nned?
> what exactly is the difference between the TCP/IP RTS and the Devsys.
> 
> I will post a summary of any/all replies.
> 

Thanks, I need all the help I can get. 

---

From: cch0241@smarine.UUCP (Chris Hapgood)
Date: 17 Oct 90 21:57:31 GMT
Organization: Sperry Marine, Inc.

You might try looking at LAN WorkPlace for XENIX 386 from Excelan, now
a division of Novell.  I have been using their product for about a year
and I am very impressed with the telnet/FTP/r-utilities/SMTP suite.
I am somewhat dissappointed with their XENIX-NET integration, but 
that may not be an issue.

---

From: uunet!dmdev!rohit@munnari.oz (Rohit Mehrotra)
Date: Thu, 18 Oct 90 12:37:44 EDT
Message-Id:  <9010181637.aa21160@dmdev.dmdev.UUCP>
Status: RO

Hi,

We use LanWorkplace from Excelan on SCO Xenix, and it works great,
however Excelan would not do any enhancements / updates on their 
product as they are shifting their priorities from TCP/IP. They 
would still presently support their product, however they are 
phasing it out.

Also the LWP from excelan available for SCO Unix does not include
the driver for delivering mail on ethernet, and they do not plan
to have one either, because of the reasons above.

I am also looking an answer for the question you have posted, but on
both SCO Xenix and SCO Unix platform.

Please EMAIL a copy of your summary to me too.

Thanks

Rohit
E-MAIL Address uunet!dmdev!rohit  or dmdev!rohit@uunet.uu.net or
	       dmdev!rohit@uunet.UUCP
VOICE 1-(305)-477-0390 Ext 469

Rohit Mehrotra
Fleet Credit Corporation
8325 NW 53rd St, Miami, Fl 33166.

---

Date: Thu, 18 Oct 90 10:40 EDT
From: uunet!tct!chip@munnari.oz (Chip Salzenberg)
Organization: Teltronics/TCT, Sarasota, FL

I used the "Controlled Release" of SCO TCP/IP Runtime for Xenix/386.
It worked well with a WD8003, though the 3C50[13] are supposed to be
supported as well.  The dev sys includes a socket library, but you can
write network applications without it if you're willing to use the
System V TLI interface.
-- 
Chip Salzenberg at Teltronics/TCT     <chip@tct.uucp>, <uunet!pdn!tct!chip>
    "I've been cranky ever since my comp.unix.wizards was removed
         by that evil Chip Salzenberg."   -- John F. Haugh II

---

Date: Wed, 17 Oct 90 20:32 EDT
From: cliffb%cjbsys.bdb.com@munnari.oz (cliff bedore)
Organization: BDB Systems

In article <6044@minyos.xx.rmit.oz> you write:
>hi,
>
>Today I was given a blank order form and asked to order SCO's TCP/IP. Now
>this is all very nice but I'd like to know how well [or badly] it performs
>on a 386 system. We are running SCO Xenix 2.3.2 on an 80386/20.
>
>Some things I would like to know:
>
>* What is the latest version available
1.0.1h

>* What are its features (ie: telnet, rlogin, ftp, else?)
all the standard things work ok

>* What are its limits?
latest version is stable for the standard things
no talk /talk demon

>* Have you found any bugs in the s/w?
no but we're not pushing it too hard.

>* Is there a better (cheaper?) product availble that will run on SCO Xenix.
not that I've heard of

>* Will it run with a 3Com Etherlink I (3C501) or Etherlink II (3C503) without
>  problems?
Yes but the 503 will do a better job

>
>Also we are looking at getting the runtime system. Will this have all I nned?
>what exactly is the difference between the TCP/IP RTS and the Devsys.
you will need the TCP/IP dev sys if you want to compile rrn or other things that
use tcp


Cliff

---

From: ronald@robobar.co.uk (Ronald S H Khoo)
Date: 17 Oct 90 18:22:01 GMT
Organization: Robobar Ltd., Perivale, Middx., ENGLAND.

s892024@minyos.xx.rmit.oz (Admiral Richard Muirden) writes:

> SCO's TCP/IP
> I'd like to know how well [or badly] it performs
> on a 386 system. We are running SCO Xenix 2.3.2 on an 80386/20.

>* What is the latest version available

The first "proper release" is the current 1.0.1, which I haven't had time
to unpack yet -- I've only used the "beta" 1.0.0 version.

>* What are its features (ie: telnet, rlogin, ftp, else?)

All that, yes.  Only thing you can't have is NFS, because the marketing
folks at SCO refuse to allow themselves to develop/sell the FileSystemSwitch
for Xenix because that would nuke 90% of the sales of SCO Unix :-)

>* Is there a better (cheaper?) product availble that will run on SCO Xenix.

Not that I know of.

> Also we are looking at getting the runtime system. Will this have all I nned?

You will need to purchase the "streams" runtime package as well.  I found this
out halfway through the installation guide to the TCP runtime :-(

> what exactly is the difference between the TCP/IP RTS and the Devsys.

The devsys provides a 4.3 BSD compatible socket library.  I used the beta
version to compile NNTP 1.5.<I can't remember which patchlevel> more or less
out of the packet, and it worked fine.  You need to purchase the devsys
*in addition* to the RTS if you want to compile any networking programs
on your own.

> I will post a summary of any/all replies.

--
ronald@robobar.co.uk +44 81 991 1142 (O) +44 71 229 7741 (H)

---

From: tkevans@fallst.UUCP (Tim Evans)
Date: 19 Oct 90 00:08:18 GMT
Organization: Fallston, MD

In <6044@minyos.xx.rmit.oz> s892024@minyos.xx.rmit.oz (Admiral Richard Muirden) writes:

>Today I was given a blank order form and asked to order SCO's TCP/IP.

>Some things I would like to know:

>* What is the latest version available

I've heard of 1.0.1h.

>* What are its features (ie: telnet, rlogin, ftp, else?)

telnet, rlogin, ftp, rcmd (what's usually called rsh), routed (no gated)

>* Will it run with a 3Com Etherlink I (3C501) or Etherlink II (3C503) without
>  problems?

Don't know about the 301, but it runs with the 3c503.  It does NOT run
with the 3c505.
-- 
UUCP:		{rutgers|ames|uunet}!mimsy!woodb!fallst!tkevans
INTERNET:	tkevans%fallst@wb3ffv.ampr.org
Tim Evans	2201 Brookhaven Ct, Fallston, MD 21047

---


==============================================================================
Richard Muirden,    NIC/DDN Handle: RM480|Humble Computer Science Student &
System Administrator,                    |Star Trek Fan!
Wesley College Melbourne (Prahran Campus)+--My opinions are my own-----------
mail: ram@lionet.wesley.OZ.AU            |mail: s892024@minyos.xx.rmit.OZ.AU
-----------------------------------------------------------------------------
Quote: "Humans smile with such little provocation", Spock, "Journey to Babel"
=============================================================================

nelson@sun.soe.clarkson.edu (Russ Nelson) (11/01/90)

In article <6064@minyos.xx.rmit.oz> s892024@minyos.xx.rmit.oz (Admiral Richard Muirden) writes:

   >* What are its features (ie: telnet, rlogin, ftp, else?)
   all the standard things work ok

   >* What are its limits?
   latest version is stable for the standard things
   no talk /talk demon

   >* Have you found any bugs in the s/w?
   no but we're not pushing it too hard.

According to my sources, SCO has acknowledged a bug in the name server
resolution code that crashes the machine.  After I disabled the name server
resolution, all the tcp-related crashes went away...

--
--russ (nelson@clutx [.bitnet | .clarkson.edu])  FAX 315-268-7600
It's better to get mugged than to live a life of fear -- Freeman Dyson
I joined the League for Programming Freedom, and I hope you'll join too.

skl@van-bc.wimsey.bc.ca (Samuel Lam) (11/02/90)

In article <NELSON.90Nov1002926@image.clarkson.edu>, nelson@clutx.clarkson.edu
 (Russ Nelson) wrote:
>According to my sources, SCO has acknowledged a bug in the name server
>resolution code that crashes the machine.  After I disabled the name server
>resolution, all the tcp-related crashes went away...

We were also having trouble with the SCO TCP/IP named.  I finally
ported Andy Poling's SysV port of BIND 4.7 to XENIX, and things
work much smoother after that.  (Still not quite perfect though...)

Someday I will either get the latest BIND ported or write "domaind",
(or "dnsd").

...Sam
-- 
Internet: <skl@wimsey.bc.ca>	UUCP: {van-bc,ubc-cs,uunet}!wimsey.bc.ca!skl