| 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 |
Hi,
Our product went out with ULTRIX3.1/UWS2.1, so it was compiled on
ULTRIX3.1. I upgraded my workstation to ULTRIX4.0/UWS4.0 and installed
the product there. When I run the product on UWS4.0, the window
doesn't get displayed on my workstation under the following situation:
When DISPLAY=:0.0 (by default), I entered command to run the product,
nothing happened.
But if I a) set the display to be: DISPLAY=mynode:0
or
b) specify the "-d mynode:0" option
or
c) recompile the source and UIL files on ULTRIX4.0
and let the display be: DISPLAY=:0.0
the window comes up fine on my workstation.
Also, this problem only happens on the VAX ULTRIX4.0. It does not
happen on RISC ULTRIX4.0
Does any one know what might cause the problem and why? Any idea would
be appreciated.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2715.1 | GILROY::klee | Ken Lee | Fri May 04 1990 14:51 | 12 | |
UWS2.1 on VAXes only used a shared memory default local transport (DISPLAY=:0). There was a bug in the SM transport implementation that caused the client to hang if the server did not support the same SM transport. For various reasons, UWS2.2 and later releases did not support the same SM transport, so VAX clients linked with UWS2.1 Xlib trying to connect to a UWS2.2 or later local server by specifying DISPLAY=:0 will run into this bug and hang. The workarounds are to specify DISPLAY=unix:0, specify DISPLAY=host:0, recompile the client with a UWS2.2 or later Xlib, and/or buy a PMAX. This is mentioned, though somewhat tersely, in both the UWS2.2 and UWS4.0 release notes. Ken | |||||