Xref: utzoo comp.sys.ibm.pc:32663 alt.msdos.programmer:267
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!sppy00!jmv
From: jmv@sppy00.UUCP (Jim Vickroy)
Newsgroups: comp.sys.ibm.pc,alt.msdos.programmer
Subject: Identifying processors...
Keywords: identifying processors
Message-ID: <490@sppy00.UUCP>
Date: 4 Aug 89 15:24:03 GMT
Organization: Online Computer Library Center, Dublin, Ohio.
Lines: 31

Just recently a friend forwarded to me an assembler routine which
identifies the type (i.e. 8086,80286, etc) of microprocessor is 
present in the machine which the probgram is running. The method
was to execute cpu-specific op codes and see if you get to the 
illegal op-code interrupt handler (which was previously stolen). I
was wondering if there was possibly a more reliable way (such that
you don't have to have an assembler which generates 286, 386, op-codes?
I have been told that there was an artical in PC TechJournal some time
ago which explained a different method. Unfortunately I am unable to 
locate this artical. I did find, however, a Tech Notebook which outlined
an algorythm which identified co-processors (Aug '87 - if your interested).

Any help would be appreciated.


Thanks,

jim
__
==============================================================================
:::: ::: ::  ::   :    :   Jim Vickroy
|OC| ||| ||  ||   |    |   Technical Services Department
|LC| ||| ||  ||   |    |   Online Computer Library Center, Inc.
:::: ::: ::  ::   :    :   Dublin, Ohio
------------------------------------------------------------------------------
UUCP:    {att|pyramid|killer}!osu-cis!sppy00!jmv  
domain:	 jmv@sppy00.uucp
USSNAIL: 6565 Frantz Rd., Dublin, Ohio 43017-0702
------------------------------------------------------------------------------
"Don't it always seem to go; you don't know what you've got 'til it's gone"-jm
==============================================================================