home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x.motif
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!swrinde!emory!gatech!usenet.ins.cwru.edu!agate!spool.mu.edu!umn.edu!noc.msc.net!uc.msc.edu!apctrc!zjmw36
- From: zjmw36@trc.amoco.com (Joe M. Wade)
- Subject: Re: HP Motif vs. xnews
- Message-ID: <C0Dyr7.2t3@trc.amoco.com>
- Sender: usenet@trc.amoco.com
- Organization: Amoco Production Company, Tulsa Research
- X-Checksum-Snefru: bab89c2f 82806a60 3af2be4a 1807b85e
- References: <1992Dec30.124950.4825@draco.macsch.com> <C052o7.En4@hpuerca.atl.hp.com>
- Date: Tue, 5 Jan 1993 14:54:42 GMT
- Lines: 47
-
- In article <C052o7.En4@hpuerca.atl.hp.com> amga@hpuerca.atl.hp.com (Anne Gale) writes:
- >In <1992Dec30.124950.4825@draco.macsch.com> matt@sparc6.pisces.macsch.com (Matt Jackson) writes:
- >
- >>If I run my application on an HP9000 with X11R4 and Motif1.1, and display
- >>it on a SPARC 1+ with Openwin 3.0, it takes about *10 minutes* to start
- >>up (on other machines, it takes a few seconds). The holdup appears to be
- >>in a routine called XRefreshKeyboardMapping(). "hpterm" does the same
- >>thing, but other Motif programs do not. Running Motif programs on an SGI
- >>Indigo and displaying them on the SPARC works like a champ. Running any
- >>application anywhere and displaying it on SPARC using the X11R5 server
- >>works fine, so it appears to be an incompatibility between xnews and HP
- >>Motif 1.1.
- >
- >I haven't seen this personally, but I've spoken with several customers
- >who have had the problem with hpterm. The information that we normally
- >give customers is as follows:
- >
- > The hpterm X client is waiting to get the value of some selection
- > ("Customize Data:") and not succeeding. The Sun server should
- > realize that there is no owner of that selection and should return
- > None as the selection value.
- >
-
- I experienced this same problem from clients I built on our HP.
- A program written in pure Xlib using XOpenDisplay worked fine,
- whereas any program calling XtAppInitialize would hang as Matt described.
- I didn't bother to track in down further as Matt did. I just turned it
- in to the HP guys and ran to our admin.... ;^)
-
- > The bug has been reported to Sun (Sun bug id is 1076332). The problem
- > exists only with OpenWindows 3.0. Any Motif 1.1 client will have this
- > problem. A work-around is to set the following reso X server:
- >
- > *useColorObj: false
- >
- >Hope this helps,
- >Anne
-
- You're right here. That fixes the problem. Our administrator also
- turned me on to an OpenWindows 3.0 server that had the patches up
- to level 28 applied to it. That also worked for me.
-
- --
- * Joe M. Wade (jwade@trc.amoco.com) * - "programmer without a cause" *
- * Amoco Research Center * growth sucks. stop making babies.*
- * 4502 E. 41st St. Tulsa, OK 74102 * - Oliver Wendell Jones *
- * (918) 660-4387 * dyffff ?? *
-