[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:	DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:	See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:	STAR::VATNE

Created:	Mon Oct 30 1989
Last Modified:	Mon Dec 31 1990
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3726
Total number of notes:	19516

2135.0. "DECwindow Components vs DECW$KITBLD.DAT?" by ASD::GUDITZ () Wed Jan 24 1990 17:29

I've done a number of directory searches and can't find any topics on
the following. If this has been discussed before please point me to the
right note.


Is there a way to determine which of the three components of DECwindows,

    - VMS DECwindows Compute Server
    - VMS DECwindows Device Support
    - VMS DECwindows Programming Support

as described in most layered product Software Support Addendums, actually
exist on a target machine?  Is there a correlation between these components
and the savesets/classes listed in DECW$KITBLD.DAT?  If I can use 
DECW$KITBLD.DAT to determine the presence or absence of these components,
which files are required or optional for a given system or processor? 

Paul

T.R Title User Personal
Name Date Lines

2135.1 STAR::ORGOVAN Vince Orgovan Wed Jan 24 1990 23:05 70

T.R	Title	User	Personal Name	Date	Lines
2135.1		STAR::ORGOVAN	Vince Orgovan	`Wed Jan 24 1990 23:05`	70
	The recommended way to determine which if any of the VMS DECwindows optional components have been installed is described below. 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. VMS V5.3 ======== V5.3 is just like V5.2 above.

    The recommended way to determine which if any of the VMS DECwindows
    optional components have been installed is described below. 
    
    
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.

    
    VMS V5.3
    ========
    
    V5.3 is just like V5.2 above.