[comp.windows.x] X v10r4+ on Pyramid scribbles on Sun's screen

bob@osu-eddie.UUCP (02/21/87)

When running X v10r4+ clients on a Pyramid 98x (OSx 4.0c) talking to
an X v10r4+ server on a Sun 3/50 (Sun UNIX 3.0), things they don't
work so good.

On the Sun, I see about a dozen vectors scribbled all over the bitmap,
not respecting window boundaries, but generally in the northwest area
of the screen.  On the Pyramid, I see:

# /u/osu/bin/xload aargh:0
X Error: parameter not a Window
         Request code: 2
         Request function: 59
         Request window 0x0
         Error Serial #35
         Current serial #35
#

Similar things happen when trying to talk to an ULTRIX-32w 1.0 server
on a uVAXII station, only the Request function is `78'.  Similar
things happen with other clients on the Pyramid.

If it were a byte ordering problem wouldn't I expect much more to see
it in interactions between a Sun server and a VAX client?  (But I
don't see it there.)  What else should I be looking for?  Any
suggestions?  Thanks muchly!
 Bob Sutterfield, Computer and Information Science Department
 The Ohio State University; 2036 Neil Ave. Columbus OH USA 43210-1277
 bob@ohio-state.{arpa,csnet} or ...!cbosgd!osu-eddie!bob
 (614) 292 - 0915

barry@mind.UUCP (02/23/87)

In article <3177@osu-eddie.UUCP> bob@osu-eddie.UUCP (Bob Sutterfield) writes:
>When running X v10r4+ clients on a Pyramid 98x (OSx 4.0c) talking to
>an X v10r4+ server on a Sun 3/50 (Sun UNIX 3.0), things they don't
>work so good.
>
>On the Sun, I see about a dozen vectors scribbled all over the bitmap,
>not respecting window boundaries, but generally in the northwest area
>of the screen.  On the Pyramid, I see:
>
># /u/osu/bin/xload aargh:0
>X Error: parameter not a Window
>         Request code: 2
>         Request function: 59
>         Request window 0x0
>         Error Serial #35
>         Current serial #35
>#
>
> Bob Sutterfield, Computer and Information Science Department
> The Ohio State University; 2036 Neil Ave. Columbus OH USA 43210-1277
> bob@ohio-state.{arpa,csnet} or ...!cbosgd!osu-eddie!bob
> (614) 292 - 0915


I asked the same question about a week ago.  I got the following
answer that solved the problem.

    Subject: X problems


    We had some problems with a different alignment strategy in structures
    between Pyramids and others machines (Vaxen, Suns) ...
    For example, sizeof(Vertex) is 6 bytes on Vaxen and 8 bytes on Pyramids.
    You can try the -q option of cc.

    [Francis Dupont] dupont@inria.inria.fr or ..!seismo!mcvax!inria!dupont


Would someone from Pyramid care to comment on the undocumented "-q"
option to cc?

Barry Lustig
Cognitive Science Laboratory, Princeton University

dmb@its63b.UUCP (02/26/87)

I had the same problem which, according to our local xpert is caused
by a bug in Xcreate on the pyramid. To solve the problem you need to
give the full geometry specification e.g. xterm =80x34+0+0. Easy eh!

	Duncan Baillie