From: Endlisnis <s257m AT unb DOT ca>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Game loop
Date: Sun, 30 Aug 1998 11:44:36 -0300
Organization: NBTel Internet
Lines: 17
Message-ID: <35E96554.A1CD2A92@unb.ca>
References: <6s2mth$c70$1 AT towncrier DOT cc DOT monash DOT edu DOT au> <35E56969 DOT 8B2E05F3 AT unb DOT ca> <35E606F5 DOT 844DA7A1 AT cartsys DOT com> <35E883AF DOT 3046 AT geocities DOT com>
NNTP-Posting-Host: fctnts12c40.nbnet.nb.ca
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Adam Brown wrote:
> > Be aware this will only work on a Pentium; many clones won't.
> However, if it does work, it is about 2 zillion times better than
> uclock. So is there some way of checking whether you are running on a
> pentium?
	There is a CPUID command, but that only works on some 486's and should work
on all Pentium machines.  There are other ways to see if the machine is a 386,
so if you rule out it being a 386, then you can try the CPUID command and find
out if it is capable of the cycle-timer command.

-- 
     (\/) Endlisnis (\/)
          s257m AT unb DOT ca
          Endlisnis AT GeoCities DOT com
          Endlis AT nbnet DOT nb DOT ca