Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!cg-atla!fredex
From: fredex@cg-atla.UUCP (Fred Smith)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Microsoft Quick Basic doesn't detect 80387 under SimulTask
Message-ID: <8193@cg-atla.UUCP>
Date: 22 Dec 89 16:52:09 GMT
References: <1989Dec21.234703.15536@cec1.wustl.edu>
Reply-To: fredex@cg-atla.UUCP (Fred Smith)
Organization: Agfa Compugraphic Division
Lines: 31

In article <1989Dec21.234703.15536@cec1.wustl.edu> dale@wucs1.wustl.edu (Dale Frye) writes:
>I was given a program to install on an ATT 6386 WGS. the program
>was written by a professor (Mech. Eng.) using Quick Basic. The
>program does a great deal of computations. Running in native DOS
>the program will invert and do some calculations on a test matrix
>in 20 seconds. Under Simultask (VP/ix) it takes almost 5 minutes.
>We have concluded that QB is checking for and not finding the 80837.
>
>Any ideas or suggestions?
>
>Dale Frye
>Washington University in St. Louis


Dale et al:

You can attempt to verify your conclusion by setting an environment
variable named NO87=(any value you like) then running your program.
Do this OUTSIDE the SimulTask enviornment.

The presence of this variable should cause the qB runtime to assume
that there is no math coprocessor availalbe, even if there is one.
You should be able then to approximately duplicate the performance
measurements you got while using SimulTask, if in fact the problem IS
as you guess.

As to how to fixit, I am afraid I can't help there!

Good luck!

Fred