Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!decwrl!waikato.ac.nz!comp.vuw.ac.nz!badger!srlncnc
From: srlncnc@dosli.govt.nz (Chris Crook)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: Borland C and _8087/matherr bugs? HELP
Summary: Use of 87 environment variable
Keywords: Borland C FPU 8087
Message-ID: <1991May7.021146.18094@dosli.govt.nz>
Date: 7 May 91 02:11:46 GMT
References: <2397@wet.UUCP>
Sender: srlncnc@badger.dosli.govt.nz (Chris Crook)
Organization: Department of Survey and Land Information, New Zealand
Lines: 19

In article <2397@wet.UUCP> smiller@wet.UUCP (Gregory Shane Miller) writes:
>
>I looked in c0.asm (arced in the examples Borland provides) to see how
>they arrived at its value.  Am I crazy, or does it assign a value depending
>on what's in the DOS environment space?! (c0.asm/c0x.obj provides the startup 
>code for any Borland EXE or COM).
>

No - you're not crazy.  Borland provide the option of over-riding the system
derived value by setting an enviroment variable.  Thus you can effectively
disable the FPU at run time by setting the 87 enviroment variable, i.e.

SET 87=N

This doesn't answer much of your question, but it may be a start.  


Chris Crook
srlncnc@badger.dosli.govt.nz