Path: utzoo!attcan!uunet!lll-winken!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!altos!altos86!rcollins
From: rcollins@altos86.Altos.COM (Robert Collins)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Difference between a 386 and a 386sx
Keywords: 386 386sx
Message-ID: <4103@altos86.Altos.COM>
Date: 24 Sep 90 19:59:33 GMT
References: <1990Sep16.194605.11968@ecn.purdue.edu> <4383@bwdls58.UUCP> <14110@mentor.cc.purdue.edu> <4387@bwdls58.UUCP> <4093@altos86.Altos.COM> <4405@bwdls58.UUCP>
Reply-To: rcollins@altos86.UUCP (Robert Collins)
Organization: Altos Computer Systems, San Jose, CA
Lines: 21

In article <4405@bwdls58.UUCP> mlord@bwdls58.bnr.ca (Mark Lord) writes:
>
>Impressive.  I have yet to see a program which correctly informs me of 
>the 18Mhz speed of my 386sx.  Congratulations!
>
I put a 30Mhz crystal in a '486 and it says 30Mhz.  I'm sure it will 
work @ 18Mhz as well.

>But I'm still doubtful of the applicability of this to determining the
>exact CPU type, as in that case the bus-width, caches, wait states etc..
>all interfere with any timing-based method of cpu identification.
>
I'm sorry if I implied I used timing as a means to determine CPU type...
I don't.  I determine the CPU type, then time it.


-- 
"Worship the Lord your God, and serve him only."  Mat. 4:10
Robert Collins                 UUCP:  ...!sun!altos86!rcollins
HOME:  (408) 225-8002
WORK:  (408) 432-6200 x4356