home *** CD-ROM | disk | FTP | other *** search
Wrap
Received: from convex.convex.com (convex.convex.com [130.168.1.1]) by nacm.com (8.6.10/8.6.9) with ESMTP id FAA07107 for <executor@nacm.com>; Mon, 19 Jun 1995 05:47:12 -0700 Received: from convex1.convex.com by convex.convex.com (8.6.4.2/1.35) id HAA17317; Mon, 19 Jun 1995 07:46:33 -0500 Received: from r3pc2.convex.com by convex1.convex.com (5.64/1.28) id AA20093; Mon, 19 Jun 95 07:53:29 -0500 Message-Id: <9506191253.AA20093@convex1.convex.com> X-Sender: kemp@convex1.convex.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 19 Jun 1995 07:40:00 -0500 To: Tim Cutts (Zoology) <tjrc1@mole.bio.cam.ac.uk>, Per Erik Gullberg <pergull@fubar.cs.montana.edu> From: kemp@convex.convex.com (Phil Kemp) Subject: Re: Linux executor help Cc: executor@nacm.com, jdc@xinside.com Sender: owner-paper@nacm.com Precedence: bulk At 08:17 AM 6/19/95 +0100, Zoology wrote: >In your message (Sat, 17 Jun 1995 18:38:18 -0600 (MDT)), you wrote: >>I just installed executorlinux199m (demo) for Linux. >> >>It seems like executor is not responding to any X-events. >>No response to the mouse, keyboard or any update events. >> >>Executor will display the desktop properly at first. >>Once the desktop has been displayed it seems to freeze. >> >>I am using: >> >> Linux 1.1.72 >> XFree86 3.1 >> Pentium, with 32 Meg >> Logitech serial mouse > >The problem appears to be with the Linux X server, rather than >Executor, per se. I get very slow pointer updates too when running >executor displaying on a Linux X display. However, I tried running >it displaying on a Sun SparcStation running Solaris 2 and OpenWindows >3, and it behaved perfectly. Executor seems to be falling foul of >something in XFree86, possibly only in particular X servers. If >people with this problem mail me and tell me what their video >hardware is, I will post a summary to the list in the next couple of >days, see if we can establish a pattern. I had some really nasty problems with executor under linux using the xinside. After extensive testing the xinside folks determined that the something in executor was eating memory like crazy. It seems to me that Thomas said something about the cursor code having memory holes. I've copied the xinside for further comments. The xinside folks were able to fix this on the server end with a slight performance reduction( ~1 or 2 percent) Sounds like the executor folks might want to pursue this further. Comments, Jeremy? Cheers PK