EYRING@cc.utah.edu (01/01/91)
Our client is a Sun 3/470 4.1 OS with Openwindows 2.0 our server is an HP 700/x x window terminal. The OW 2.0 is x11R4, but the HP server code is x11R3. After about an hour of intensive work the server will blow up. Like it had a glych in its memory manager. Every once an a while I will get bad atoms messages at the client terminal, but it still works. Can R4 calls to a R3 server cause the R3 server to become brain damaged? nx
strike@pixel.convex.com (M Streicher) (01/04/91)
In article <105110@cc.utah.edu>, EYRING@cc.utah.edu writes: |> Can R4 calls to a R3 server cause the R3 server to become |> brain damaged? |> When we first installed R4 on our Suns and CONVEXen, we still had a few systems running R3 servers. For the most part, we did not see any problems, but occasionally strange things did happen. Most of the problems seem related to R3 window managers and not the server. For example, an R4 xterm would not size properly on an R3 window manager. The xterm window would come up 8x4 or some random, tiny size. Right now we use several old R3 servers on HPs and old Tek X terminals. Everything works ok, except for shape extensions and multi-buffering. Beware R3 window managers and R4 Xt applications. Martin Streicher Manager, Graphics and Windowing Software Development Group Software Environments Product Department CONVEX Computer Corporation Richardson, TX email: strike@convex.com or uunet!convex!strike phone: 214/497-4469