home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.lang.c:13000 comp.lang.c++:13075 comp.sys.ibm.pc.hardware:22999 comp.sys.intel:1612
- Path: sparky!uunet!usc!rpi!batcomputer!munnari.oz.au!goanna!minyos.xx.rmit.oz.au!kjb
- From: kjb@cgl.citri.edu.au (Kendall Bennett)
- Newsgroups: comp.lang.c,comp.lang.c++,comp.sys.ibm.pc.hardware,comp.sys.intel
- Subject: CoProcessor detection and emulation libraries...
- Message-ID: <kjb.715224980@godzilla.cgl.citri.edu.au>
- Date: 31 Aug 92 01:36:20 GMT
- Sender: usenet@minyos.xx.rmit.oz.au (Njuiz noveles nova newes)
- Organization: RMIT Advanced Computer Graphics Centre, CITRI, Melbourne
- Lines: 24
-
- I have an interesting question. One of the routines in a library that I am
- developing detects the type of CPU and co-processor installed in am IBM PC
- type machine. It works correctly on all the machines that I have tried it
- on. One of my beta testers mentions that on his machine it said he has
- an 80387 installed when he had none.
-
- Since the co-processor is detected by checking the status of the processor's
- control and status words, is it possible that 387 emulation libraries
- (such as FRANKIE.387) would show up as a co-processor in this type of
- check? Is there any way to check that such a library is installed, rather
- than a co-processor (in the docs for FRANKIE.387 is says that programs will
- not be able to tell the difference between a real co-pro and the emulation
- library)?
-
- Thanks in advance,
-
- +------------------------------------------+-------------------------------+
- | Kendall Bennett, | Internet: |
- | Advanced Computer Graphics Centre, | kjb@citri.edu.au |
- | Royal Melbourne Institute of Technology, | rcskb@minyos.xx.rmit.oz.au |
- | Victoria, AUSTRALIA. | |
- +------------------------------------------+-------------------------------+
- | CoSysop (Bossman), PC Connection Australia: +61 3 688 0909 |
- +--------------------------------------------------------------------------+
-