Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!acorn!moncam!loki From: loki@moncam.uucp (Never Kid A Kidder) Newsgroups: comp.windows.x Subject: texx (and others) R3-client -> R4-server incompatability. Keywords: X Protocol error Message-ID: Date: 1 Nov 90 21:52:52 GMT Sender: loki@moncam.co.uk Distribution: comp Organization: (n) The process of becoming an organ. Lines: 40 Setup: R3 on Sun3/160 SunOS 4.0, R4 on Sun4/110 SunOS 4.0 I'm not sure if this is a recognised problem, but one or two clients with R3 libraries are having problems talking to an R4 server. It's always an `X Protocol error', eg: [ home grown program... ] X Protocol error: BadMatch, invalid parameter attributes Major opcode of failed request: 62 (X_CopyArea) Minor opcode of failed request: 0 Resource id in failed request: 0xa00011 Serial number of failed request: 53 Current serial number in output stream: 54 [ texx... ] X Protocol error: BadMatch, invalid parameter attributes Major opcode of failed request: 70 (X_PolyFillRectangle) Minor opcode of failed request: 0 Resource id in failed request: 0x0 Serial number of failed request: 33 Current serial number in output stream: 214 I can guess that the R3 code is either doing something `unofficial' that is no longer valid, or that R4 really does expect different attributes from the ones being sent. If the former, perhaps I only need to set up something that should have been done anyway, but it somehow didn't matter in R3? Any help greatly appreciated. Also, what's the best book for introducing X from the programmer's point of view? -- Harry Fearnhamm, ,---.'\ EMAIL: loki@moncam.uucp Monotype ADG, (, /@ )/ ...!ukc!acorn!moncam!loki Science Park, /( _/ ') VOICE: +44 (0)223 420018 Cambridge, \,`---' FAX: +44 (0)223 420911 CB4 4FQ, DISCLAIMER: Nothing is True. ENGLAND. Everything is Permitted.