eco@ece-csc.UUCP (ECO) (04/08/89)
Hi. The xterm (X11R2) distributed with IBM's AIX 2.2.1 does not have
Tektronix mode. So we are interested in obtaining the MIT X11R2 xterm
(assuming it has Tek mode). I would appreciate information on where I
can get a R2 xterm or the entire R2 release.
B
Thanks,
Amy <johnson%eceugs@ncsuvx.ncsu.edu>
jw@pan.UUCP (Jamie Watson) (04/11/89)
In article <4003@ece-csc.UUCP> eco@ece-csc.UUCP (ECO) writes: >Hi. The xterm (X11R2) distributed with IBM's AIX 2.2.1 does not have >Tektronix mode. So we are interested in obtaining the MIT X11R2 xterm >(assuming it has Tek mode). I would appreciate information on where I >can get a R2 xterm or the entire R2 release. Unless you are willing to do a *lot* of work, you are out of luck. The xterm on the MIT R2 release doesn't come anywhere close to compiling on AIX (or any other system with SysV tty drivers). The xterm on the R3 release appears to have been significantly overhauled (looks like it was someone at HP that did it), but it still doesn't compile on AIX. I have been able to get it to compile and sort of run, but there are still lots of serious problems with it. By the way, the xterm that is on the IBM X 2.1 release for AIX 2.2.1 is *not* a V11R2 xterm; it is a vintage V10R4 that has been modified to run on X.V11. This is probably the single largest complaint I have about X on the RT with AIX right now, and I have had several big arguments with IBM about it. They refuse to say whether it is a V10 xterm, but it is easy enough to determine: - It puts up its own title bar by default - It doesn't understand most of the command line arguments that were introduced with V11. - It doesn't set window name or the window class. It would be very nice if IBM would either update their xterm to V11R3. Or, if they really believe that there are a significant number of people who depend on the V10 xterm, they could put both in their distribution. jw
geb@amber.Rational.COM (Gary E. Barnes) (04/13/89)
I've managed to get xterm running on AIX under IBM's 2.2.1 X Windows. What I did was take X11R2 xterm, diff it with X11R3 xterm, put in, by hand, all changes that did not pertain to widgets or other XLib/XTk interface changes, add a bunch of AIX specfic junque to make it work, called IBM various times (they responded very nicely to my problems), and it all worked. If anyone is curious I can show them what to do AIX-wise. IBM's X Windows is a curious mixture of almost-X11R3 guts with a definitely-X11R2 interface. They have at least one XTk bug that is unique to X11R3 but they still ship the X11R2 interface. The full diffs between X11R2 xterm and our current hybrid are about 6000 lines long. The AIX OS-specific stuff isn't too big/bad. There is some rather silly cruft that you have to do in order to disable what they call HFT Emulation that things like vi and telnet keep trying to force upon your poor unsuspecting pty port but most things are relatively easy. Another thing that you have to be aware of is that X11R2 and X11R3 have differences in the truth that they tell to an application about textual extents and such. The X11R3 code does a few "bad" things since AIX is using the X11R2 textual stuff. You get cursor ghosts and descending characters leave droppings. I've given our xterm some switches, -/+X11R2 and -/+X11R3 so that you can tell it which text model to use depending upon the server that you will be talking to. Fun, huh? Gary Gary E. Barnes geb@rational.com