Path: utzoo!attcan!uunet!wuarchive!usc!elroy.jpl.nasa.gov!thyme!kaleb
From: kaleb@thyme.jpl.nasa.gov (Kaleb Keithley	)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: 386SX capabilites
Message-ID: <1990Oct15.161015.417@thyme.jpl.nasa.gov>
Date: 15 Oct 90 16:10:15 GMT
References: <1990Oct9.212047.21053@infonode.ingr.com> <1990Oct10.001733.1299@thyme.jpl.nasa.gov> <2056@sixhub.UUCP>
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 30

In article <2056@sixhub.UUCP> davidsen@sixhub.UUCP (bill davidsen) writes:
>In article <1990Oct10.001733.1299@thyme.jpl.nasa.gov> kaleb@thyme.jpl.nasa.gov (Kaleb Keithley	) writes:
>
>| Even if it's an SX.  There's nothing a DX can do that an SX can't.
>
>  Whoops! The 16 bit data bus prevents doing 32 bit i/o to memory mapped
>devices, and the addressing space is only 16 MB.
>

Got any memory mapped devices in mind?  We are talking about Intel 
architecture here, not Motorola ;-)  Accuse me of "small world" if you
want, I haven't seen memory mapped i/o for PC's in ten years, that's
what the i/o bus is for.  As for memory, yeah, you're right, but how
many people do you know who are using DOS are being limited by the SX's
16Meg limit?  I don't know anyone, including UNIX and OS/2 users.  How 
many people are being limited by DOS's 640K limit?  Everyone.  Remember, 
not everyone has DesqView/QEMM or Windows 386/3.0

Actually, I think I'll let this whole thread go, since I just upgraded
my 386SX to a 486 (Can you say $1100?)  Defending my SX from ignorance 
has become a non-issue to me.  Anyone want to buy a slightly used 386SX 
w/ 0k, plus an AT case and 200W p/s?  It has run DOS, OS/2, ESIX SysV 
UNIX, DesqView/QEMM, and Windows 386.  Up to 8 Meg on the M/B, AMI BIOS, 
C&T chipset.

-- 
Kaleb Keithley                      Jet Propulsion Labs
kaleb@thyme.jpl.nasa.gov

causing trouble again.