jlh@excalibur.tn.cornell.EDU (Jeff Henslin) (02/07/91)
Here's a problem I'm having with OpenWindows and aixterm from IBM.
I am running OpenWindows 2.0, SunOS 4.1 on a SparcStation 1+.
The aixwindow originates on an RS6000 with AIX 3.0. Here is the message
I get when I try:
aixterm: BadAlloc, insufficient resources for operation
Request code 1, minor code 0, serial #142, resource id 32505865
IOT/Abort trap
Under X11R4 it works fine. Any suggestions?
---------------------------------------------------------------------------
Jeff Henslin jlh@theory.tn.cornell.edu
Workstation Systems Specialist
Cornell National Supercomputer Facility
Cornell University
---------------------------------------------------------------------------jhlee1@aisun.kaist.ac.kr ( Lee Jai Hyuk) (02/09/91)
------------------------------------------------------------------------------------- Dear ..... I had been programed using X-lib in 'mwm'. Resently, I have a new enviroment openlook in SUN-SPARK-station-2 But, there are some problems in new enviroment. first. some programs using only x-lib (not X/view) does not execute in Openlook. when key-event alise ( I press a keyboard ), this enviroment does not supply key event ( KeyPress ) to process. only beep sounds occured. Of course, these program nomally execute in 'mwm' or 'twm'. And,, Now I can't use 'olwm' no more. How can I overcome this problem ? Second, I wish I could append new event in x/view programming. this event is for new device, tablet. I can control this device, But I can't program to control this device using x/view. How can I append new event to my x/view program ? I wish your return as soon as possible . Thanks you... From Jai-Hyuk Lee jhlee1@solgai.kaist.ac.kr -------------------------------------------------------------------------------------
lwv27%CAS.BITNET@CUNYVM.CUNY.EDU (03/24/91)
To: openlook of unify.com at bitnet Subject: Re: Misc OpenWindows 2.0 questions Cc: Bcc: -------- Newsgroups: comp.windows.open-look In-Reply-To: <5j0u823 of openlook.Unify.Com> at bitnet Reply-To: Larry W. Virden <osu-cis!chemabs!lwv27> Organization: Nedriv Software and Shoe Shiners, Uninc. Gee - I dont understand how you folks who have gotten the client software from MIT X11R4 got some of it to work. When I try to run the makes there are missing libraries, header files, etc. When I try to run xman I get streams of msgs about widget problems and a window which has only one button highlighted - the quit button. When I tried xpostit I got similar behaviour. As I have mentioned in previous postings (maybe they never got out of here) I am just trying to figure out a) how to set things up so the std clients as posted to the net will compile without a lot of headaches and b) how to tell shelltool I want escape sequences for F1-F12, R1-F15 or so, L1-L10 and those darn +,-, Enter, Ins, Del keys. Right now, I get 9 of the F keys, all of the R keys, none of the L keys, and the extra key pad keys - but they wont act as keypad keys with the numlock turned on. -- Larry W. Virden UUCP: osu-cis!chemabs!lwv27 Same Mbox: BITNET: lwv27@cas INET: lwv27%cas.BITNET@CUNYVM.CUNY.Edu Personal: 674 Falls Place, Reynoldsburg,OH 43068-1614 America Online: lvirden
lwv27%CAS.BITNET@CUNYVM.CUNY.EDU (03/26/91)
To: openlook of unify.com at bitnet Subject: Re: Setting the correct DISPLAY when starting up OpenWindows Cc: Bcc: -------- Newsgroups: comp.windows.open-look In-Reply-To: <JC.91Mar25174544 of raven.bu.edu> at bitnet Reply-To: Larry W. Virden <osu-cis!chemabs!lwv27> References: <JC.91Mar25042243 of raven.bu.edu> at bitnet Organization: Nedriv Software and Shoe Shiners, Uninc. The syntax being generated for DISPLAY is a proper syntax. From reading the various X reference manuals, for instance the book X Window System C Library and Protocol Reference by Schiefler, Gettys and Newman of MIT page 10 of my edition in the section on "Opening the Display", it is explained that X11 clients use the string in DISPLAY to determine how to open a connection to the server. raven:0.0 means that the toolkit MUST open a TCP socket to the server unix:0.0 means that the toolkit MUST use Unix domain IPC streams. :0.0 means that the toolkit is free to use whatever is faster. on the other hand, when I log into an OpenWindows session and type xhost I am not shown anything. So I have added a: xhost +`hostname` to my .openwin-init file, and do not seem to get the access errors that I occasionally saw before. What is interesting is that very few pgms ever gave me the access error- emacs was one. -- Larry W. Virden UUCP: osu-cis!chemabs!lwv27 Same Mbox: BITNET: lwv27@cas INET: lwv27%cas.BITNET@CUNYVM.CUNY.Edu Personal: 674 Falls Place, Reynoldsburg,OH 43068-1614 America Online: lvirden
** Sender Unknown ** (05/10/91)
~r nn_ ~r nn_ ~p ~v
fgreco@govt.shearson.com (Frank Greco) (06/08/91)
In article <1991Jun06.060759.420@shawn.uucp> you write: >Performance: I have used both. The MIT stuff is faster by my perception. What OS? What machine? What graphics accelerator? What X version, How much RAM? What is your typical network bandwidth? What type of applications? What language are you using? What other non-X stuff is running concurrently? Faster at doing: Creating windows? Moving windows? Mouse movement? Event handling? Destroying windows? Drawing lines? Filling polygons? Rendering Postscript? Doing animation? Opinion is fine, but "is faster by my perception" needs a bit of qualification, wouldn't you say? >Portability: OpenWin has little or none of the standard utilities of >X-Windows. It is largely a politically motivated product, I suppose that DEC and IBM initially funding MIT for X Window wasn't? > meant to continue looking as much like Sun's old technology > as possible. I have to deal with many an X Window student > who is bewildered by the nearly total lack of similarity > between what the world largely regards as a "typical" X > environment and what OW sticks them with. This, to me, is > a valid component of "portability". Consider also that no > Athena toolkit example programs can be demonstrated in OW. Why not? I run Athena stuff (and anything else from MIT) on my SS with OW all the time. Granted I had to snarf them off the net, but they work here. We have Sun3's and SPARC machines that are identical in "similarity" (ie, non-computer type users cannot tell them apart). Perhaps you are not configuring your machines correctly. Heck, students that I know all use as many window managers and applications as they can find using both MIT X and Sun's OW. They understand what X is and what it is not. Perhaps their bewilderment could be tempered with some education about window systems and toolkits. It also seems that your definition of "typical" is your own opinion and not fact. >Quality: The server core dumps often, both on Sun 3's and Sparcs. Dbxtool > constantly crashes with no good reason. Scrollbars erratically > jump you in the wrong direction and have virtually worthless > visual feedback. Guide is bug ridden and breaks data consistently. > Cursor warping is inconsistent, which is worse that having it > always or never. Is this enough, or do I have to have more? > The MIT port is better. SImple as that. Wow. My server doesn't core dump often. Yes it dumps, but just as "often" as the MIT server. I've never had dbxtool break (although dbx has). While they're not optimal, our users find OL scrollbars very intuitive. I have found bugs with devGUIDE, but its an overexaggeration to say its bug-ridden (how many rev 1's of products do you know were perfect?); and what data does it "break"? I don't follow what you're saying about cursor warping, so I don't follow you there. I simply don't agree with you. The MIT folks have done a great job; the Sun people have done a great job (considering that their server handles X and NeWS and Sunview is just less than a miracle). They're not perfect, but considering the relative immaturity of window systems, both groups are doing a phenomenal job. If you think a product that you are using has bugs, report them to the vendor so that it can be fixed if it is truly broken. Its your responsibility as a user. >I did not elaborate because I have limited time to read news >and even less time to write long dissertations (sp?). E x c u s e M e.... So do a lot of us, but your posting just hit a nerve so I had to reply. Frank G.