Date: Fri, 22 Oct 93 14:51:24 EDT
From: peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock)
To: djgpp AT sun DOT soe DOT clarkson DOT EDU
Subject: clock() blows up under windows 3.1

> { return (float) clock()/CLOCKS_PER_SEC; }
> In a Windows 3.1 DOS window, it blows the window away!

I think somebody pointed out shortly after 1.10 was released that clock()
assumes that the first MB of memory is mapped to 0xe000000, which is not
true under DPMI.  It needs to do something similar to what is done in
dosmem.s, namely check whether the 1.10 extender is being used, and if so,
use a selector to get at low memory.  I haven't seen a fix posted, but then
I somehow got dropped from the mailing list, and only recently resubscribed.