DEC clients running under MIT X11R4?

[Jim Gettys]

In article <1991Feb14.160319.2761 at vax5.cit.cornell.edu> bqsy1 at vax5.cit.cornell.edu writes:
>
>       We recently built X11R4 on a DECstation 3100 running Ultrix 4.1,
>using DEC's cc. Everything went well with no reported compilation or
>linking errors. However, we have run into the following problem - we seem
>to be unable to run the dx* binaries under X11R4. Any attempt to run these
>produces a core dump.
>       My understanding of DEC's Xserver, and from looking at the
>libraries and include files for DEC's X11, is that is an R4 port, without
>the extensions. What else did DEC do to its clients to make them not work
>under MIT's R4??
>       I should say that we've run MIT clients under the DEC Xserver with
>no problem. Even clients that require the shape extension run,though they
>default to DEC's Server when opening windows and creating buttons and
>widgets.
>       Any help at all would be appreciated.

If you look at the frequently asked questions list posted periodically
in comp.windows.x, you'd find a reference to the fact the DECwindows
clients depend on fonts you may not have.

If you install an appropriate fonts.alias file you should be all set.
Pointers to the file are in the FAQ list, or you can grovel around
gatekeeper.dec.com's anonymous ftp area to find it (I don't remember the
file name off the top of my head.

Also note you should do an "xset bc" to enable bug compatibitity on an R4
server; if you happen to be using older DECwindows versions, you may run into 
problems if you don't (the more recent the DECwindows release, the less
likely this may be necessary.  This is true actually when running any
client from before R4; a number of bugs were fixed in R4 that may cause
buggy older clients to break.
				- Jim Gettys


--
Digital Equipment Corporation
Cambridge Research Laboratory