🚀 go-pugleaf

Newsgroups: comp.windows.x.pex
Subject: Re: How to get my server to support PEX?
Summary:
Expires:
References: <1992Apr8.191357.3536@sunova.ssc.gov>
Sender:
Reply-To: lilleyc@cs.man.ac.uk (Chris Lilley)
Followup-To:
Distribution:
Organization: Department of Computer Science, University of Manchester UK
Keywords:

In article <1992Apr8.191357.3536@sunova.ssc.gov> chow@sdc1.ssc.gov writes:

>From the FAQ, I know if I do a xdpyinfo and I don't see X3D-PEX.  It means
>my server does not support PEX.  The question is how to get my server
>support PEX?

On the other hand, if you _do_ see X3D-PEX it doesn't mean diddly. Logged
onto a unix machine with display set to a VAXstation4000 I did xdpyinfo
and it gave me a whole pile of extensions:

----------------------------------------------------
...
vendor string:    DECWINDOWS DigitalEquipmenttCorp.
vendor release number:    11
...
number of extensions:    7
    DEC-Server-Mgmt-Extension
    ServerManagementExtension
    Adobe-DPS-Extension
    X3D_PEX
    Xie
    DEC-XTRAP
    Multi-Buffering
...
--------------

Well it does have DPS (display postscript) so I believed it for a while.
But then, I set the display to a VT1000 terminal (if you have used one of
these, read on and weep - with laughter). The same set of extensions were
listed. Ho hum.  Is there another way to tell, or is this a bug in the
server?

	Chris