Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!decwrl!world!aep
From: aep@world.std.com (Andrew E Page)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Think C programming (SysEnvirons)
Message-ID: <1991Apr4.142549.28035@world.std.com>
Date: 4 Apr 91 14:25:49 GMT
References: <1991Mar25.192630.6028@ncs.dnd.ca>
Distribution: ca,edu
Organization: The World Public Access UNIX, Brookline, MA
Lines: 17


  The most efficient(and stable) and stable of determining
the presence of a coprocessor would be through the use of the
_SysEnvirons trap.  Consult IM V-5 for more detailed info.
This routine is provided for just the purpose of determining
the environment.

   If you would like a bit more of a brute force method:
Patch the exception vector for unimplemented instructions and 
execute a floating point instruction right afterwards.  An intereception
of the interupt will indicate the lack of the processor.  I do not
recommend this however.  It just might be more of an interesting method.

-- 
Andrew E. Page (Warrior Poet)   |   Decision and Effort The Archer and Arrow
Concepts Engineering            |     The difference between what we are
CIS:70202,234  BIX:page1        |           and what we want to be.