garyo@THINK.COM (Gary Oberbrunner) (01/06/90)
If you have the following resource set in your resource database, R3 xterm will not work with an R4 server (color Sun4/110, color or b/w screen): XTerm*scrollBar: on Here's the error: X Protocol error: BadValue, integer parameter out of range for operation Major opcode of failed request: 2 (X_ChangeWindowAttributes) Minor opcode of failed request: 0 Resource id in failed request: 0x20030 Serial number of failed request: 61 Current serial number in output stream: 62 The same effect can be obtained by calling the R3 xterm with the -sb option. Any idea why? What other clients will this affect? Anything I can do about this for the duration while we still have some R3 stuff around? - Gary Oberbrunner Thinking Machines Corporation 245 First St Cambridge, MA 02142 garyo@think.com
rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (01/06/90)
Read xpert before you write. :-)
This will probably be one of those frequently asked questions for a while.
The vanilla R3 xterm is buggy, and the R4 server catches. If you want to
run an R3 xterm, use "xset bc", or use the "bc" command line option to the
R4 server.
What other clients will this affect?
A fair number, including some products.