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: rick@NGP.UTEXAS.EDU (Rick Watson)
Newsgroups: mod.computers.vax
Subject: Re:  TCP/IP for VMS
Message-ID: <8601041857.AA02010@ngp.UTEXAS.EDU>
Date: Sat, 4-Jan-86 13:57:35 EST
Article-I.D.: ngp.8601041857.AA02010
Posted: Sat Jan  4 13:57:35 1986
Date-Received: Mon, 6-Jan-86 06:41:50 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 23
Approved: info-vax@sri-kl.arpa

One possible solution would be to use a DEUNA instead of the NI1010A. The 
DEUNA driver allows sharing by multiple protocols. For instance, we run
DECnet and Wollongong TCP/IP on the same board. This solution would depend
on there being a DEUNA driver interface for your XNS package, and no 
overlap in the protocol numbers used. (If XNS uses ARP, there would
be a problem.) This would also require that you run the Wollongong
shared DEUNA driver (more $ I think), which uses more overhead than
the internal driver. There may be other problems, so I would be careful
before going out and buying a DEUNA.

You could probably run another NI1010A. (I know, more $, etc.)

My guess on why switching packages on the fly doesn't work is that there
is some problem with who gets the interrupts for the NI1010. Maybe you 
could figure out how to patch this.

Rick Watson
University of Texas Computation Center
 arpa:   rick@ngp.UTEXAS.EDU   rick@ngp.ARPA
 uucp:   ...seismo!ut-sally!ut-ngp!rick   rick@ut-ngp.UUCP
 bitnet: ccaw001@utadnx
 phone:  512/471-3241