[comp.unix.i386] Problems With Intel's X11R3

heasley@bu-ast.bu.edu (Jim Heasley) (07/24/90)

I've just installed Intel's X implementation (X11R3) on my 386 which is
running under Intel's System V 3.2.2.  After a brief false start (due to
my desire to run X and not the Open Look) it came up and runs well,
except for the two things listed below.  If anyone else has encountered
these problems or if an X guru can suggest a fix it would be most
appreciated. 

1) When I'm using the server on my 386 to run xterm on other machines (a
Decstation 3100 and Sun 3/160 -- that is, xterm is really running on the
other host and just using the display on the 386), when I move the
cursor into an xterm window and use the CTRL-mouse buttons to bring up
the xterm control menus, the menu starts to come up but vanishes
immediately as apparently somewhere a kill gets generated which zaps the
window! This is rather annoying to say the least, and I have to iconify
the Tek window to get it out of the way as I can't get at the menu entry
to hide it.  This is a new "feature" with X11R3, as the server in the
X11R2 release worked properly with xterm on remote hosts (but was in
general *very* slow). 

2) When I use the image display program xim from either of the remote
machines mentioned above to display on my 386, the image is scrambled. 
(The binary of xim which came with my X release won't display these
images as it's apparently unhappy with the headers for some reason.)
Before going to Unix and the X11R3, the xim on the remote hosts
displayed on the 386 quite nicely using the PC-Xsight server I was
running under DOS.  I think the problem has to do with the fact that
PC-Xsight server (and the server on the Decstation, which also works
correctly with xim) indicate that they expect the image byte order to be
MSBFirst, whereas the 386 server (AT&T 6386 WGS with color VDC-600) says
its image byte order is LSBFirst.  That would be consistent with the
scrambled images I see.  Does anyone know a way to change this in the
server? Digging through the manuals don't seem give any indication this
can be changed. 

As these are pretty specific questions it'd probably be best to e-mail
directly to me.  If others inidicate they're having the same problems
I'll post a summary of responses.

Jim Heasley

Department of Astronomy
Boston University (on leave from University of Hawaii)

heasley@bu-ast.bu.edu