| During a kitinstal, where should the UID file be placed? I've been
told that a kitinstal is supposed to explicitly state the directory a file is
destined for. Assuming this is true, should the UID file be placed in
VMI$ROOT:[DECW$DEFAULTS.USER]
VMI$ROOT:[DECW$DEFAULTS.SYSTEM]
or
VMI$ROOT:[SYSLIB]
Jim
|
| RE: is this true for font files too?
The short answer is yes. Read on for the long answer.
From: STAR::ORGOVAN "Vince Orgovan" 18-MAY-1989 17:43:14.06
To: SQM::LEN
CC: SQM::HARLOW,ORGOVAN,GEORGE
Subj: SQM guidelines for Layered Product installation with DECwindows
Christina,
We've received several questions regarding how layered products interact
with VMS DECwindows during installations and startup. Rather than just try
to answer the couple of questions you asked, I thought that I would use
this as an opportunity to document most of the common questions that folks
have asked along the way. Sorry that I couldn't get this to you sooner.
Please feel free to circulate this to any layered products that need this
information.
DECwindows facility prefixes
============================
The DECW$, CDA$, DDIF$, etc. prefixes are NOT generic - they are
specifically reserved for use by base VMS supplied DECwindows
components. No layered product should contain any files with these
prefixes.
DECwindows directories of interest to layered products
======================================================
SYS$COMMON:[VUE$LIBRARY.USER]
This directory holds VUE command procedures for layered products.
The parallel directory SYS$COMMON:[VUE$LIBRARY.SYSTEM] is reserved
for usage by VMS, and should not be used by layered products.
SYS$COMMON:[DECW$DEFAULTS.USER]
This directory holds UID and Xresource (Xrm) files for layered products.
The parallel directory SYS$COMMON:[DECW$DEFAULTS.SYSTEM] is reserved
for usage by VMS, and should not be used by layered products. Note
that the logical name DECW$SYSTEM_DEFAULTS should be used locate
these files, since this is a search list through the .user and
.system subdirectories. Layered products should not be putting UID
or Xresource files in SYS$LIBRARY.
SYS$COMMON:[SYS$KEYMAP.DECW.USER]
This directory holds keymap files for layered products. The parallel
directory SYS$COMMON:[SYS$KEYMAP.DECW.SYSTEM] is reserved for usage
by VMS, and should not be used by layered products.
SYS$COMMON:[SYSFONT.DECW.USER_75DPI]
This directory holds 75 dot per inch fonts for layered products.
The parallel directory SYS$COMMON:[SYSFONT.DECW.75DPI] is reserved
for usage by VMS, and should not be used by layered products.
SYS$COMMON:[SYSFONT.DECW.USER_100DPI]
This directory holds 100 dot per inch fonts for layered products.
The parallel directory SYS$COMMON:[SYSFONT.DECW.100DPI] is reserved
for usage by VMS, and should not be used by layered products.
SYS$COMMON:[SYSFONT.DECW.USER_CURSOR16]
This directory holds 16 bit by 16 bit cursors for layered products.
The parallel directory SYS$COMMON:[SYSFONT.DECW.CURSOR16] is reserved
for usage by VMS, and should not be used by layered products.
SYS$COMMON:[SYSFONT.DECW.USER_CURSOR32]
This directory holds 32 bit by 32 bit cursors for layered products.
The parallel directory SYS$COMMON:[SYSFONT.DECW.CURSOR32] is reserved
for usage by VMS, and should not be used by layered products.
SYS$COMMON:[DECW$INCLUDE]
Reserved for usage by VMS DECwindows and should not be used by layered
products.
SYS$COMMON:[SYSHLP.EXAMPLES.DECW]
Reserved for usage by VMS DECwindows and should not be used by layered
products. As per existing SQM guidelines, layered products should
create their own subdirectories to [syshlp.examples] and should not
use decw$examples.
There are no specific guidelines today about creating subdirectories
under any of the DECwindows supplied directories. Since this could
potentially cause problems in the future, layered products should be
encouraged to discuss any such subdirectory creation with the DECwindows
project leader prior to shipping products that do this.
Pre-VMS V5.1
============
There is no DECwindows support for VMS versions prior to V5.1. Layered
products should not assume the existence of any DECwindows directories
or files.
VMS V5.1
========
DECwindows support for VMS V5.1 is packaged as a separately installed
option. Layered products can assume that SYS$COMMOM:[VUE$LIBRARY.USER]
exists since this directory is created on all V5.1 (and later) systems.
Otherwise layered products should not assume the existence of any
DECwindows directories or files.
V5.1 DECwindows can be installed completely or in portions. The installation
always provides the DECwindows runtime libraries and client applications,
and allows the system manager to optionally install DECwindows device support
and programming support.
To determine if any of the DECwindows components have been installed,
the recommended method is to test for the existence of the file:
sys$share:decw$xlibshr.exe
To determine if the DECwindows device support has been installed, the
recommended method is to test for the existence of the file:
sys$system:decw$server_main.exe
To determine if the programming support has been installed, the recommended
method is to test for the existence of the file:
sys$system:decw$uilcompiler.exe
VMS V5.2
========
DECwindows support for VMS V5.2 is packaged as part of the VMS installation
process. There is a required portion containing the DECwindows runtime
libraries that is automatically installed on all V5.2 systems, and several
optional portions:
DECwindows compute server support
DECwindows device support
DECwindows programming support
Layered products can assume that V5.2 systems contain the required
DECwindows files including decw$xlibshr.exe, decw$dwtlibshr.exe, and
cda$access.exe.
To determine if the DECwindows compute server support has been installed,
the recommended method is to test for the existent of the file:
sys$system:decw$session.exe
Checking for the device support and programming support can be done as
described previously for V5.1.
Use of undocumented interfaces
==============================
Several layered products may inadvertenly be relying on undocumented
DECwindows interfaces that are subject to change. These products may
obtain source and/or object code from groups contributing to the
DECwindows kit and then include it in their products. If the code uses
undocumented interfaces within DECwindows and we subsequently change them,
the layered product will no longer work properly.
Known examples of code in this category include the DECwindows print
widget and the dectermport source interface.
|