postnews@cvbnet2.UUCP (postnews login account) (03/31/88)
As was mentioned by someone else here, I too find that the X implementation running on suns os 3.2 has problems. If anyone out there understands the following detailed description of the problem and has a solution by all means get in touch with me. The problems as far as I've been able to track it is this. The sun X server (Xsun) runs fine. It can communicate with all of its clients that I've tested EXCEPT xterm. Xterm causes the server to try to pad a pixmap (I think) which is referenced in routine mfbPadPixmap() at line 147, ddx/mfbpixmap.c. I don't understand why this illegal value only crops up for xterm. Anyone out there understand this code? The other clients I've checked the server against are xload, uwm, and perhaps a few others. If anyone has any suggestions... Another question I have is this. After about a week of recompiling, editing makefiles, editing header files, editing...(jeez, what haven't I edited :-) I finally got andrew to run on both 68010 and 68020 based suns. It blew my socks off!! What a great idea! I do have some problems with it, unfortunately. One is - I cannot for the life of me get help to work. It dies a gory death by a segmentation fault. No pretty pictures come up, nothing. Just a dirty, old core file. Any ideas before I attack it whole- (well, maybe only half) heartedly? Finally, I notice that in the typescript window, sometimes it runs full-duplex, i.e. it echoes what I type, and other times it doesn't. If I wait a little bit the chances of it echoing my input improves quite a bit. And, as if to razz me a bit, it seems to echo newlines as 'X'. Very destracting. Anyone have any ideas on this? Thanx for reading my ramblings! This is a general purpose account, so please, if you reply directly to me send your responses to.. aperez@cvbnet Arturo Perez Prime nee Computervision MS 5-1 14 Crosby Drive Bedford, MA (617) 275-1800 x4388
rapatel@porthos.rutgers.edu ( Rakesh Patel) (04/03/88)
[ I have some brief questions at the end of this posting for those who have spent some time with the Andrew system.] Here are my experiences with the X11R2 and Andrew installations on Sun 3s running 3.2: The X server will not work when optimized. Most of the clients seem to work fine though. In order to get the Andrew system compiled and at least running (we do get core dumps at times, but it is definitely worth bringing up), you should make sure to get the files in the updates directory within the X.V11R2 distribution from expo.lcs.mit.edu. Also get the README.updates file to find out where the files go. In addition (and also important), you will find fixes in ~ftp/contrib/andrew which help make the system usable. After taking care of the update files and the fixes, there are some things you want to change for a Sun. You want to make sure to change andrew/be2/support/print.c to use the appropriate formating and printing commands. (The default is to look in /usr/ibm for eqn and troff - when on the Sun they are in /usr/bin). You really want to read the installation directions (in the top level README) very carefully. The help program has will run if the fixes are applied and you build the help index as they say to do in the README. The programs are very nice. The help program is great for looking at man pages. For those of you who have things working, I found that the preview program doesn't work. It turned out to be dumping core in nroff!?!?!?! Anyone have any ideas why? Also, has anyone figured out how to set up messages to read newsgroups directly from /usr/spool/news? Rakesh Patel.