LUSGR@LEHICDC1.BITNET (Steve Roseman) (10/21/87)
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. If you are running a different version, you will have to look around for it. The change is made in the source module CONFIG, so a listing of the routine can help to find literals storage area. Steve Roseman Lehigh University <LUSGR@LEHICDC1.BITNET> (preferred address) <LUSGR@VAX1.CC.LEHIGH.EDU>
carl@CITHEX.CALTECH.EDU (Carl J Lydick) (10/21/87)
> 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. If you are running a > different version, you will have to look around for it. The change is made in > the source module CONFIG, so a listing of the routine can help to find > literals storage area. If this is the case, then it's pretty likely that there is an easier solution: you can probably get it to run by having the system startup procedure issue the command: $ DEFINE/SYS/EXEC XEA0 ETA0 prior to starting TCP/IP. This technique worked for getting a different TCP/IP to run on a microvax (there the command was: $ DEFINE/SYS/EXEC XEA0 XQA0 as I recall).
jonathan@comp.vuw.ac.nz (Jonathan) (10/22/87)
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