From:	CSBVAX::MRGATE!@KL.SRI.Com:info-vax-request@kl.sri.com@SMTP 22-OCT-1987 23:14
To:	EVERHART
Subj:	Re: CMU TCP/IP on an 8530

Received: from ucbvax.Berkeley.EDU by KL.SRI.COM with TCP; Thu 22 Oct 87 11:44:23-PDT
Received: by ucbvax.Berkeley.EDU (5.58/1.27)
	id AA07634; Thu, 22 Oct 87 10:43:52 PDT
Received: from USENET by ucbvax.Berkeley.EDU with netnews
	for info-vax@kl.sri.com (info-vax@kl.sri.com)
	(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 22 Oct 87 06:12:40 GMT
From: munnari!comp.vuw.ac.nz!jonathan@uunet.uu.net  (Jonathan)
Organization: Comp Sci, Victoria Univ, Wellington, New Zealand
Subject: Re: CMU TCP/IP on an 8530
Message-Id: <13032@comp.vuw.ac.nz>
References: <8710210517.AA25313@ucbvax.Berkeley.EDU>
Sender: info-vax-request@kl.sri.com
To: info-vax@kl.sri.com

In article <8710210517.AA25313@ucbvax.Berkeley.EDU> LUSGR@LEHICDC1.BITNET (Steve Roseman) writes:
>
>    We are running CMU TCP/IP (v6.0) on an 8530.  It simply(!!!) took a patch
>to change one occurance of 'XE' to 'ET' at address 6A8. 

I came against something like this when using the last Tektronix
distribution on a Microvax II, using a configuration file that
specified XEA0. The ACP wouldn't start, because of course the Microvax
had a DEQNA not a DEUNA. The first solution I came up with was to
	$ DEFINE/SYS XEA0 XQA0
 (or maybe it was $ DEFINE/SYS/EXEC, I forget which), and to leave the
reference to XEA0 in the configuration file. It worked just fine.
Actually, the software *did* support DEQNAs; the documentation was out
of date.

I don't see why you could't just
	$ DEFINE/SYS XEA0 ETA0
and put
	Device_Init:XEA0:...:
in your internet.config file. No patches, no hassles when a new
release of the software comes out :-).  After all, this sort of
problem is just why VMS has logical names!
-- 
Sane mailers: jonathan@comp.vuw.ac.nz           |``Toto, I have a feeling we're
UUCP: ...!uunet!vuwcomp!jonathan                |  not in Kansas anymore ...''
						|      - Dorothy,arriving in Oz