🚀 go-pugleaf

While testing an application against the Windows 3.1 final release
yesterday I stumbled on a problem I can't explain.  Note it's
*not* a 3.1 problem - it happens with 3.0, we just never noticed
it before.

Our program fails as follows:  Open one copy.  Leave it open, and
open a second copy.  Close the first copy.  Open a third copy -
well, try to, it'll UAE in the startup code.

Poking with the debugger seems to point the finger at the floating
point code - the program DOES use FP, and we compile it to use the
emulator.

To test this, we took one of the Borland sample apps (the bitmap
scroller, in particular.)  Compile it as is, and it works fine.
Add a couple lines to it:

	float	f;
	f = 3.0 * f;

..and it blows up just like our application.  Which argues it's not
*our* problem.

Note that opening the third copy after 1) LEAVING the first copy
running, or b) closing BOTH the first and second copies works
fine.

Compiling to use the 80287 directly doesn't improve things.

We've also got an OWL app that exhibits the identical behavior.

Now we can grossly theorize what's going on here with DLLs, but
more importantly - how do we get around it?  ('Course, knowing WHY
it is this way would be nice, too.)
-- 
    Dave Anderer        danderer@brahms.udel.edu       (302) 831-8805
Instructional Technology Center, University of Delaware, Newark, De.  19716
		"Sinners can repent; stupid is forever."