Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!ssbell!dsndata!wayne
From: wayne@dsndata.uucp (Wayne Schlitt)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Difference between a 386 and a 386sx
Message-ID: <WAYNE.90Sep19180242@dsndata.uucp>
Date: 19 Sep 90 22:02:42 GMT
References: <1990Sep16.194605.11968@ecn.purdue.edu> <4383@bwdls58.UUCP>
	<14110@mentor.cc.purdue.edu>
Sender: wayne@dsndata.UUCP
Followup-To: comp.sys.ibm.pc.misc
Organization: Design Data
Lines: 13
In-reply-to: edgincd2@mentor.cc.purdue.edu's message of 18 Sep 90 22:21:50 GMT

In article <14110@mentor.cc.purdue.edu> edgincd2@mentor.cc.purdue.edu (Chris Edgington *Computer Science Major*) writes:
> 
> If you wanted to determine whether or not the chip you are using is a 386
> or a 386sx, couldn't you just execute some 32 bit intructions and time the
> number of machine cycles it takes to execute them.
> 

no, because you cant tell if the extra time is because of slow memory
causing wait states, or if the smaller bus is causing the wait states.
all you know is that the time to do something is slower than the
theoretical maximum.

-wayne