Conference bulova::decwindows

	The problem is actually DECwindows/Motif related.  When I advised
him to do a   
		$ view/interf=decw/form=ps   xxxx.ps

it gave him exactly the same message as when he tried invoking CDA to view a
postscript file:

	' Server does not have postscript extension'

He is not using x-display terminals, but a proper alphastation 200-4/233, so
I would expect the Xserver to have all the bells and whistles, including
display postscript extension, what is missing here?

	configuration: alphastation 200 running OpenVMS V6.2-1H3, and
		       motif 1.2


Thanks,

/David

< He is not using x-display terminals, but a proper alphastation 200-4/233, so
< I would expect the Xserver to have all the bells and whistles, including
< display postscript extension, what is missing here?

David,
     Running xdpyinfo ($run decw$utils:xdpyinfo) will tell you if the Xserver
has the DPS Extension enabled.

yakka_kingsmill> run decw$utils:xdpyinfo
name of display:    _WSA54:
version number:    11.0
vendor string:    DECWINDOWS DigitalEquipmentCorporation
vendor release number:    568
maximum request size:  65535 longwords (262140 bytes)
motion buffer size:  0
bitmap unit, bit order, padding:    32, MSBFirst, 32
image byte order:    MSBFirst
number of supported pixmap formats:    2
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
keycode range:    minimum 8, maximum 255
number of extensions:    5
    SHAPE
    XInputExtension
    BIG-REQUESTS
    DPSExtension             <-------------
    .
    .

If its doesn't exist then I'd look at the DECwindows startup.

Cheers,
Geoff..

  DECwindows Motif V1.2 is pretty old -- V1.2-4 is current.

	Thanks for you replies.

	I am still having problem with it, the Alphastation 200 4/233,
running VMS V6.2-1H3 still don't have the Display PS extention, we have
applied ALPMOTF07_U3012 to the 1.2-3 Motif, and rebooted the system, and
still xdpyinfo showed only the following:

name of display:    _WSA6:
version number:    11.0
vendor string:    DECWINDOWS DigitalEquipmentCorp. AXP
vendor release number:    6002
maximum request size:  65535 longwords (262140 bytes)
motion buffer size:  0
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    6
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 12, bits_per_pixel 32, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
number of extensions:    10
    DEC-Server-Mgmt-Extension
    ServerManagementExtension
    SHAPE
    MIT-SHM
    XTEST
    MIT-SUNDRY-NONSTANDARD
    AccessX
    Xie
    DEC-XTRAP
    Multi-Buffering
default screen number:    0
number of screens:    1

note the absence of DPSExtension.

	What do I have to do to get that particular extension?  I looked 
through decw$startserver.com, and it was checking bit 0 of SECURITY_POLICY,
before defining "Adobe-DPS-Extension" extension, and SECURITY_POLICY is 7 in
my case! and I am still not getting the extension.

	Any idea?

	/David

Are you defining the global symbol decw$server_extensions in
sys$manager:decw$private_server_setup?  Maybe you're giving the server a
list of extensions which doesn't include DPS, instead of letting it use
its default list.

				-- Bob

   Looks like the DECwindows Motif installation has been tailored and
   tweaked, or has something weird going on...

   There were some field test baselevels of OpenVMS where the DECwindows
   Motif server code lacked display Postscript support, but these were
   resolved (added) in the final OpenVMS release.

   Here's the standard set of extensions found in DECwindows Motif V1.2-4,
   with the associated V1.2-4 ECO kit, under OpenVMS Alpha V7.1, where two
   `DPS' extensions are visible:

number of extensions:    15
    DEC-Server-Mgmt-Extension
    ServerManagementExtension
    SHAPE
    MIT-SHM
    XTEST
    BIG-REQUESTS
    MIT-SUNDRY-NONSTANDARD
    MIT-SCREEN-SAVER
    SYNC
    AccessX
    Adobe-DPS-Extension
    DPSExtension
    Xie
    DEC-XTRAP
    Multi-Buffering

The DPS extension might also be disabled due to a nondefault value of the
SECURITY_POLICY parameter in SYSGEN. See bit 0 below.

Edwin

--------------------------------------------------------------------------

Parameters

  SECURITY_POLICY

       SECURITY_POLICY allows a system to run in a C2 or B1
       configuration and subset out particular pieces of functionality
       that are outside of the evaluated configuration or to preserve
       compatibility with previous versions of the operating system. See
       the OpenVMS VAX Guide to System Security for further information
       on the C2 and B1 evaluated configurations.

       The following bits are defined:

       Bit   Description

       0     Allows DECwindows Display PostScript extensions
       1     Allows multiple user names to connect to DECW$SERVER
       2     Allows unevaluated DECwindows transports (such as TCP/IP)
       3     Allows $SIGPRC and $PRCTERM to span job trees
       4     Allows security profile changes to protected objects on
             a local node when the object server is absent and cannot
             update the cluster database VMS$OBJECTS.DAT
       5     Allows creation of protected objects on a local node when
             the object server is absent and cannot update the cluster
             database VMS$OBJECTS.DAT
       6     Allows SPAWN or LIB$SPAWN commands in CAPTIVE accounts

       The default value of 7 preserves compatibility with existing
       DECwindows Motif behavior. A value of 0 disables all unevaluated
       configurations.