Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!sun!misc!jdn
From: jdn@misc.Sun.COM (Jeff Nisewanger)
Newsgroups: comp.windows.x
Subject: Re: X11R3 and X11R4 compatibility under unicos
Message-ID: <130041@sun.Eng.Sun.COM>
Date: 9 Jan 90 20:54:45 GMT
References: <23045@ut-emx.UUCP>
Sender: news@sun.Eng.Sun.COM
Reply-To: jdn@sun.UUCP (Jeff Nisewanger)
Organization: Sun Microsystems, Mountain View
Lines: 32

In article <23045@ut-emx.UUCP> jones@ut-emx.UUCP (William L. Jones) writes:
>There seems to be a problem with X11R3 and X11R4 compatibility under unicos.
>
>I get the following message when I try to run a X11R3 client on unicos with
>a X11R4 server.
>
>>/usr/adm/bin/crayperf
>>X Protocol error:  BadLength, poly request too large or internal Xlib length e\
>rr
>>or
>>  Major opcode of failed request:  45 (X_OpenFont)
>>  Minor opcode of failed request:  0
>>  Resource id in failed request:  0xb00002
>>  Serial number of failed request:  13
>>  Current serial number in output stream:  13
>
>Does anybody have a fix for this yet.
>
>I am running with "xset bc".
>
>
>Bill Jones

	We ran across this problem recently between a cray X client
and the OpenWindows server. What we found was that the client
was sending an X OpenFont protocol request that had 7 trailing pad
bytes instead of the legal maximum of 3.


Jeff Nisewanger                         ARPA: jdn@sun.com
Window Systems Group                    UUCP: ...!sun!jdn
Sun Microsystems, Inc.                  415/336-5743