From:	MERC::"uunet!ARISIA.dnet.ge.com!CRDGW2::CRDGW2::MRGATE::SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 12-APR-1992 20:34:24.68
To:	galaxy::GleEve
CC:	
Subj:	Supervisor Series Installation Notes (sorry)

From:	RELAY-INFO-VAX@CRVAX.SRI.COM@SMTP@CRDGW2
To:	Everhart@Arisia@MRGATE

Received:  by crdgw1.ge.com (5.57/GE 1.137)
	 id AA04169; Sun, 12 Apr 92 19:11:07 EDT
Received: From ucbvax.Berkeley.EDU ([128.32.133.1]) by CRVAX.SRI.COM with TCP; Sun, 12 APR 92 11:13:23 PDT
Received: by ucbvax.Berkeley.EDU (5.63/1.43)
	id AA29875; Sat, 11 Apr 92 16:28:22 -0700
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: 9 Apr 92 18:03:30 GMT
From: vlsi!wkuvx1.bitnet!goathunter@g.ms.uky.edu
Organization: Western Kentucky University, Bowling Green, KY
Subject: Supervisor Series Installation Notes (sorry)
Message-Id: <1992Apr9.130330.1286@wkuvx1.bitnet>
Sender: info-vax-request@kl.sri.com
To: info-vax@kl.sri.com

A few gotchas about installing the Supervisor Series v5.1 (I *knew*
something would pop up):

  1.  The ADVISE command conflicts with VPA's ADVISE.  If you have
      VPA, *don't* add the ADVISE/OBSERVE commands to DCLTABLES.

      Notice that the default is NO for installing them in DCLTABLES.
      I recommend that you define foreign symbols for it.

  2.  The OBSERVE CLD file (OBSADV.CLD) has a type: the image name
      given is OBSERVE.EXE; it should be OBSERVER.EXE.  You can either
      rename the image to OBSERVE, or, better, modify the .CLD file
      (SUPSER_ROOT:[EXE]OBSADV.CLD) and re-SET COMMAND it to replace
      it in DCLTABLES.EXE.

  3.  The /QUIET option requires that SECURITY privilege be an
      *authorized* privilege, not just a default.  I didn't notice
      this until last night.  I will be changing it to either check
      for a default privilege or use an identifier for /QUIET.

  4.  When installing, do not use a concealed logical name for the
      device name.  I'd recommend just always using the *real* device
      name (DUA0:[SUPSER], for example).  Something like
      SYS$SYSROOT:[SUPSER] will cause the installation to fail.

Sorry for the hassles.  I'll be correcting all of these things in the
next release (either v5.2 or a sub-release of v5.1).

Hunter
------
Hunter Goatley, VMS Systems Programmer, Western Kentucky University
goathunter@WKUVX1.BITNET, 502-745-5251