Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!cornell!uw-beaver!mit-eddie!ll-xn!ames!ucbcad!ucbvax!JPLOPTO.JPL.NASA.GOV!earle
From: earle@JPLOPTO.JPL.NASA.GOV (Greg Earle)
Newsgroups: comp.windows.x
Subject: Re: X catalog
Message-ID: <8711120558.AA07488@jplopto.Jpl.Nasa.Gov>
Date: Thu, 12-Nov-87 00:58:04 EST
Article-I.D.: jplopto.8711120558.AA07488
Posted: Thu Nov 12 00:58:04 1987
Date-Received: Sat, 14-Nov-87 15:51:16 EST
References: <871106144744.5.RWS@KILLINGTON.LCS.MIT.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Jet Propulsion Lab, Pasadena, CA
Lines: 22

In article <871106144744.5.RWS@KILLINGTON.LCS.MIT.EDU> Robert Scheifler
writes:
>(BTW, one of the most commonly asked questions is availability of an X
>server on 286+DOS.  The other is for general overview and programmer's
>guide documentation.  There's a killing to be made ...)

I've been wondering about this (286+DOS).  Given that (a) Sun's PC-NFS Toolkit
(1.0FCS) includes a complete implementation of the 4.2BSD socket library,
and good old select(2) besides, and (b) there are companies that advertise in
PC type magazines for high-res monitors for PC-AT's (I forget the name, but
one offers a 19" 1600x1280!), what is there to keep one from being able to
port the X server to such a setup (other than porting issues, like `What
will Microsoft C V 4.0 hiccup on this time?' and `Gee, the whole world is
not a VAX or RT/PC after all, right Toto?') ??  Taken a step further, what
is to prevent running a server *and* clients on an 80386 based DOS box?  I
thought I heard that 386-based DOS PC's could do some sorta multitasking ...

-- 
	Greg Earle		earle@jplopto.JPL.NASA.GOV
	S(*CENSORED*)t		earle%jplopto@jpl-elroy.ARPA	[aka:]
	Rockwell International	earle%jplopto@elroy.JPL.NASA.GOV
	Seal Beach, CA		...!cit-vax!elroy!smeagol!jplopto!earle