Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!hc!beta!cmcl2!rutgers!im4u!ut-sally!utah-cs!utah-gr!uplherc!nrc-ut!nrcvax!kvc
From: kvc@nrcvax.UUCP (Kevin Carosso)
Newsgroups: comp.os.vms
Subject: Re: VMS 4.6 and Tek-Tcp
Message-ID: <1270@nrcvax.UUCP>
Date: Tue, 3-Nov-87 14:52:42 EST
Article-I.D.: nrcvax.1270
Posted: Tue Nov  3 14:52:42 1987
Date-Received: Sun, 8-Nov-87 02:03:48 EST
References: <4929@oberon.USC.EDU>
Reply-To: kvc@minnie.UUCP (Kevin Carosso)
Organization: Network Research Corp.  Oxnard, CA
Lines: 18
Keywords: VMS 4.6 TEK TCP

In article <4929@oberon.USC.EDU> asbed@acrux.usc.edu (Asbed Bedrossian) writes:
>
>Has anyone heard anything about VMS 4.6 breaking Tek-TCP (the one that
>has been under care of Kevin Carosso)?

Someone else reported this to me.  I believe the problem is that the silly
XEDRIVER sense-mode parameter structure has changed again, or some such.
In any case, I started using the CMU version some time ago and haven't tried
my modified Tek one beyond VMS V4.5.  You really ought to just get the
CMU code.

In any case, since I work for a TCP/IP vendor now, I won't be too active in the
Tek or CMU stuff...  I'll continue to answer questions and such when I can,
however.

	/Kevin Carosso               kvc@nrcvax.uucp
	 Network Research Co.        kvc@engvax.scg.hac.com
				     kvc@ymir.bitnet