From: MERC::"uunet!WKUVX1.BITNET!FILESERV-Mgr" 10-APR-1992 11:56:35.46 To: galaxy::gleeve CC: Subj: SUPERVISOR.README The Supervisor Series is distributed as VMS_SHARE'd, MFTU'ed, LZDCMP'ed savesets. You will need the FILESERV_TOOLS to unpack the savesets. You can get them by sending the following command in the body of a mail message to FILESERV@WKUVX1.BITNET SEND FILESERV_TOOLS --------------------------------------------------------------------------- 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. 5. ADVISOR and OBSERVER should be installed with WORLD privilege. You can add it to the priv list in SUPSER_ROOT:[COM]SUPSER_STARTUP.COM, if you're installing them. 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