Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ames!xanth!mcnc!ecsvax!uccjcm From: uccjcm@ecsvax.UUCP (John McLendon) Newsgroups: comp.sys.hp Subject: Re: HP Contracts Message-ID: <6953@ecsvax.UUCP> Date: 8 May 89 01:00:53 GMT References: <547@mmlai.UUCP> <5570171@hpfcdc.HP.COM> <549@mmlai.UUCP> Reply-To: uccjcm@ecsvax.uncecs.edu.UUCP (John McLendon) Organization: UNC Educational Computing Service Lines: 39 In article <549@mmlai.UUCP> burzio@mmlai.UUCP (Tony Burzio) writes: >In article <5570171@hpfcdc.HP.COM>, gates@hpfcdc.HP.COM (Bill Gates) writes: >> >Now, if HP could only get the quality into the software support itself that >hard. Most problems are solved with the first call. I have noticed, >however, that X Window System calls require weeks to complete, with most >being pumped back to the factory for help. I have a list of 6 X bugs waiting >in the queue for the response center to finish with my call about the static >raster widget not working. Could HP get an X guru assigned to the response >center? I too have several X bugs in the queue... Perhaps we could get together here and report them to each other, provide workarounds, etc. I, for one, fail to see why I should be paying for what is essentially a beta test service for hp. That is not to say that support services isn't helpful for general problems, but for me, all it's been is X bugs in the hp widget set. Documented, verifiable bugs. Let's get with it guys. ... On another note, has anyone else noticed the slow server response for hp machines under X (HP-UX 6.2)? I run a 360 with 8 meg and lot's of swap space, 1024x768 4-plane color, etc. When I run phoon it takes more than 10 seconds to come up. When we connected one of these new X terminals (I forget which one) to the same machine, it came up in under 2 seconds. It's not due to the color card either, the mono box does the same. Also, has anyone noticed the 1.2 meg ipc (shared memory) space X allocates when run. Why is it so big? ... And while I'm complaining, why does it take so long to create widgets from the hp widget set. I have what I consider to be a moderate application with around 1000 widget instantiations, primarily push button and menu buttons in cascades on about fifteen forms. I found that in order to get acceptable performance when actually running the application, it was necessary to create all widgets ahead of time and then manage and unmanage them when called. The problem is that the application takes about four minutes to start up. It also takes about 3 meg of memory. I'm doing all the normal speed up stuff that I can think of. Anybody got any helpful hints? John... -- Signed: John McLendon uunet\ (919) 846-7931 (home) >mcnc!ecsvax!uccjcm (919) 941-5730 (play) gatech/