Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!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: <4093@altos86.Altos.COM>
Date: 20 Sep 90 15:33:43 GMT
References: <1990Sep16.194605.11968@ecn.purdue.edu> <4383@bwdls58.UUCP> <14110@mentor.cc.purdue.edu> <4387@bwdls58.UUCP>
Reply-To: rcollins@altos86.UUCP (Robert Collins)
Organization: Altos Computer Systems, San Jose, CA
Lines: 23

In article <4387@bwdls58.UUCP> mlord@bwdls58.bnr.ca (Mark Lord) writes:
>
>Good in theory.. but cannot be done.  In order to "time" them, 
>you need to know the exact CPU clock rate, which is another unknown.

It's easy to determine CPU speed.  I've had an algorithm to do this for
over a year.  It works on 8086, 186, 286, 386SX, 386DX, 486 at any speed
up to (over) 50Mhz.  Though, I haven't tried it on a 50Mhz CPU (we won't
get any until next quarter), I have tried it on 386's and 486's up to
33Mhz in each case.  The algorithm is accurate to 2 decimal places.

The algorithm is independent of, and isn't affected by cache or memory
speed.

It seems to me that you claim to have a generic algorithm to determine
an 386SX from a 386DX.  I'll make you a deal.  If you post yours (provided
it works), I'll post mine!

-- 
"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