From:	CSBVAX::CSBVAX::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 19-MAR-1989 00:20
To:	MRGATE::"ARISIA::EVERHART"
Subj:	RE: RE: Unibus address changes on 5.0??


Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Sat, 18 MAR 89 12:30:12 PDT
Received: from rcca.bbn.com by KL.SRI.COM with TCP; Sat, 18 Mar 89 12:13:15 PST
Date: Sat, 18 Mar 89 15:11 EST
From: RMCEWEN@rcca.bbn.com
Subject: RE: RE: Unibus address changes on 5.0??
To: info-vax@kl.sri.com


> Bad documentation strikes again!
>
> The situation is that the AUTOCONFIGURE operation detacts that the devices are
> at the "old" addresses. The system treats this correctly and everything works.
> So, as specified in the release notes, you re-address the involved devices. You
> reboot. You get the warning message again!
> 
> The answer is in the release notes. There is a SYSGEN parameter (I don't
> remember just which one, and the release notes are at the office) that controls
> the behavior. If set to a 0, it uses the old addressing scheme. If set to 1, it
> checks the hardware and guesses if the old or new system should be used. BUT,
> it send out the warning message REGARDLESS. The only way to eliminate the
> message is to change the SYSGEN parameter to 2.

> The idea is that the default (1) will usually work OK, and will warn the
> manager of the potential problem. If you don't want to change or the system
> guessed wrong and things don't work, set the value to 0 and everything is as in
> V4. Once you've re-addressed things, you change the parameter to 2 and the new
> scheme will be used exclusively. No warnings, but if things are not
> re-addressed, they won't work!

[...]

	The undocumented parameter is VMS8.

	VMS8=1 will use the "old" (pre-VMS 5.x) scheme.

					-Regis