Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: X11R3 and X11R4 compatibility under unicos
Message-ID: <9001092222.AA02011@expire.lcs.mit.edu>
Date: 9 Jan 90 22:22:28 GMT
References: <23045@ut-emx.UUCP>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 17


    There seems to be a problem with X11R3 and X11R4 compatibility under unicos.

The R4 server checks for a correct length on OpenFont requests (and other
requests); the R3 server did not.  Apparently something you are using in
the R3 client generates a bad length (probably including the NUL in the
length of the string?).

    Does anybody have a fix for this yet.

Rebuild the client?

    I am running with "xset bc".

This only "fixes" a few specific things that we knew would be big problems
for many R3 clients.  It was not intended as a door to reinstate all possible
R3 bugs.