Path: utzoo!utgpu!cunews!bnrgate!bwdls58!mlord
From: mlord@bwdls58.bnr.ca (Mark Lord)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Difference between a 386 and a 386sx
Message-ID: <4404@bwdls58.UUCP>
Date: 22 Sep 90 18:55:45 GMT
References: <1412@svin02.info.win.tue.nl> <4388@bwdls58.UUCP> <1990Sep20.185214.780@sj.ate.slb.com> <1990Sep21.002015.1201@thyme.jpl.nasa.gov>
Sender: mlord@bwdls58.UUCP
Reply-To: mlord@bwdls58.bnr.ca (Mark Lord)
Organization: Bell-Northern Research, Ottawa, Canada
Lines: 18

In article <1990Sep21.002015.1201@thyme.jpl.nasa.gov> kaleb@thyme.jpl.nasa.gov (Kaleb Keithley) writes:
>>In article <4388@bwdls58.UUCP> mlord@bwdls58.bnr.ca (Mark Lord) writes:
>>>>This suggests that a way to distinguish a 386dx from a 386sx in software
>>>>would be to put some value in existing memory at address 0x00xxxxxx
>>>>and read it from address 0x01xxxxxx. If it comes out the same you would
>>>>be running on a 386sx (not having the upper 8 bits of address bus),
>>>>otherwise a 386dx.
>
>and numerous other (farfetched) ways to distinguish an SX from a DX deleted.

Kaleb, and others, please be more careful to assosiate the proper quotes
with the proper people.  The above text is NOT mine.  For that matter,
it describes yet another method which will not work.
-- 
 ___Mark S. Lord__________________________________________
| ..uunet!bnrgate!mlord%bmerh724 | Climb Free Or Die (NH) |
| MLORD@BNR.CA   Ottawa, Ontario | Personal views only.   |
|________________________________|________________________|