Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ucbvax!info-vax
From: stokes%cmc.cdn%ubc.CSNET@CSNET-RELAY.ARPA (Peter Stokes)
Newsgroups: mod.computers.vax
Subject: TCP/IP for VMS
Message-ID: <488:stokes@cmc.cdn>
Date: Fri, 3-Jan-86 14:31:48 EST
Article-I.D.: cmc.488:stokes
Posted: Fri Jan  3 14:31:48 1986
Date-Received: Sat, 4-Jan-86 09:16:52 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 43
Approved: info-vax@sri-kl.arpa


>I would like to rally some support from info-vax readers. I would like
>to see TCP/IP from DEC. This would be well integrated with VMS mail
>and other system utilities. Yes, I know that there are a few software
>groups who sell TCP/IP but I think that DEC would do a better job of
>integrating it with VMS.
			Marty Sasaki


Guess what Marty....  According to our local DEC sales rep, DEC is selling
TCP/IP software for their VMS Vaxes.   How did they do it so fast... they
have made a deal with the "Wollogong Group" and are selling their package.
I doubt now that DEC will spend any time/money on re-inventing the wheel
even though a custom VMS software package would have more features.

Incidently, we purchased TCP/IP software for our VMS V4.2 780 from the 
"Wollogong Group" and are very satisfied with its performance.  If anybody
would like more info (company address, questions....) please write.

Question...  Our 780 has two Ethernet software packages installed on it.
One is TCP/IP protocol type from the Wollogong group and the other is XNS
protocol type from Daisy Systems Inc.  We have one Ethernet board in the 
Vax, the Interlan NI1010A.   At any one time only one of the two software
packages is running since both cannot have control of the Ethernet hardware
simultaneously.  The decision as to which package is running is decided
at boot time in the systartup.com file.  We have not been able to shut
down one software package and then start the other.  It seems that 
shutting down either one of the two software packages does not remove
it "enough" from the system to allow another Ethernet package to be started
and take control of the Ethernet board.  The symptons:  The ethernet simply
does not work.   It is of course inconvenient to reboot every time we 
wish to communicate with the other protocol.  Has anyone reading infovax
experienced this and has information possibly leading to a solution ???????

Peter Stokes
Canadian Microelectronics Corporation
Carruthers Hall
Queens University
Kingston Ontario  K7L 3N6
(613) 547-6947