Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!ncrlnk!wright!thor.wright.edu
From: amercer@thor.wright.edu (Art Mercer)
Newsgroups: comp.windows.x
Subject: Re: Amiga 500 X server  (was: Re: X Windows on AT&T DMD's and Blits?)
Message-ID: <872@thor.wright.EDU>
Date: 8 Dec 89 15:43:09 GMT
References: <303@nap1.cds.wpafb.af.mil>
Sender: news@wright.EDU
Reply-To: amercer@thor.wright.edu
Lines: 34

From article <303@nap1.cds.wpafb.af.mil>, by staatsvr@asdcds.cds.wpafb.af.mil ( Vern Staats;;):
>> In article <3482@jhunix.HCF.JHU.EDU> kay@jhunix.HCF.JHU.EDU (Jon Kay) writes:
>>>
>>>	Another possibility you might want to consider is buying Amiga-500's;
[... omitted ...]
>> Seriously, I think the Amiga 500 would make a great (medium-res) X terminal,
>> but the only way I can think of to get ethernet would be to use an A2000
>> ethernet card in an expansion box.  The 3rd party expansion boxes shouldn't
[... omitted ...]

It's not only getting the ethernet hooked up, the user will have to contend
with the flickering high-res screen.  While non-interlaced high-res is 
promised for future updates from Commodore, getting rid of it now requires
an additional $400.00 outlay for a "Flicker-Fixer" board.  Again, this
board is intended for a 2000/2500, not the 500.

The Amiga does work well with X, we have two A2500's set up now and have
been very pleased with their performance. (BTW: one of these  replaced
an A2000 with also performed very well.)  Both the X implementation and
the ethernet hardware and software have performed flawlessly.
 
>> INET:  staatsvr@asd.wpafb.af.mil      Vern Staats  (513) 255-2714      \\\///
>> UUCP:  -Maybe- nap1!asd!staatsvr       ASD/SCED   WPAFB OH 45433        \XX/
>> Boolean orthogonal(char *my_opinions, char *employer_opinions)  {return(TRUE);}

Art Mercer
Associate Director, Academic Computing Resources
Wright State University
Col Glenn HWY
Dayton, OH 45435

BITNET:  amercer@wsu.bitnet

---