Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!rutgers!mailrus!cornell!uw-beaver!fluke!ssc-vax!benoni
From: benoni@ssc-vax.UUCP (Charles L Ditzel)
Newsgroups: comp.sys.apollo
Subject: Re: Apollo xterm problems
Keywords: apollo, x, xterm
Message-ID: <2408@ssc-vax.UUCP>
Date: 10 Dec 88 05:12:14 GMT
References: <15672@iuvax.cs.indiana.edu> <23315@cornell.UUCP>
Distribution: na
Organization: Boeing Aerospace Corp., Seattle WA
Lines: 31


>> SAMPLE FIX :
>>    Buy a Sun.

> If you think X is bad on Apollo's, just try to run it on a Sun with 4 MB of
> memory...You'll get lots of work done.....You know things a bad when X runs
> faster than SunView/Suntools (whatever it's called) on a Sun

I have used MIT's X on Apollos and seemed *really* slow to me...and I just
imagined that the MIT tape was just not optimized for Apollos or Suns...

Incidentally, I worked on Apollos for two years before I did *just* that...
I decided to buy a workstation...I bought a  4 megabyte Sun 3/50
...and it *did* fix my problems.

I now use Apollo and Suns daily.  SunView's programmatic and user interface
is light years ahead of the DM...(goodbye dm_$etc_etc and gpr_$etc ) and it 
seems relatively fast to me ... but a couple of things come to mind ... whether
you have a Sun or Apollo  :it is worth the effort to make sure you don't have
lots of unnecessary system  processes running .. (that could slow down
any machine)


as for X...I haven't even bothered to load the tape...(I'll wait for
Sun's X11/NeWS/ and Open Look merge)...I also use NeWS and find it much faster 
than X on the Apollo ... not to mention that NeWS allows all sorts of 
things that X11 cannot do ... but that's another story entirely). Oh, and I
run it on 4 megabyte Sun 3/50 (that's their low end machine).

_____
My Opinions are my own and not my employers.