info-vax@ucbvax.ARPA (03/15/85)
From: *Hobbit* <AWalker@RUTGERS.ARPA> I don't know if this is under 4.0 or everywhere, but if you add commands to sys$library:dcltables.exe, they will *not* take effect if you have the *old* tables installed in the known file list. This is not explained in the manual... euuytch! _H* -------
info-vax@ucbvax.ARPA (03/15/85)
From: Richard Garland <OC.GARLAND@CU20B.ARPA> In Re CLD gotcha: It was always true that for the CLD tables (and other installed images) you had to do a replace: $ RUN SYS$SYSTEM:INSTALL SYS$LIBRARY:DCLTABLES/REPLACE However I do seem to notice a slightly different behavior with installed images. I seem to remember in V3.0 if you purged the old versions of an installed image, and the version number was not specified when it was installed, you got the new (latest) version when you ran it (if you didn't purge you got the old installed version as Hobbit found out). Now it seems that purging won't do the trick - you must do a /REPLACE with install (under V4.0). This is probably the correct behavior now. Has anyone else noticed this change or is my memory faulty? Rg -------
info-vax@ucbvax.ARPA (03/16/85)
From: Ronald A. Jarrell <JARRELLRA@VPIVAX3.BITNET> Haven't run into it myself, but I woldn't be surprised. I have noticed the concept of a "greater access" set in install. It now honors protection set on an .EXE file, and doesn't grant world access unless the file has it already. You can give a segment Write access, install it, then remove the write access, and the world looses write, but you can't install it read only, then give it write access, because install doesn't let you widen the scope, just narrow it. You have to /REPLACE it. -Ron