CW>> int 2Fh func 1680h worked great under Warp 2.x and 3..  But
CW>> under Warp 4 I get 100% cpu-load again, even with int 2Fh..
CW>> Any ideas?

 DN> I'm still sorting it out under 3.0's VMB support. It'll be another
 DN> week or so before I get 4.0 installed. [Have to move NT out of the
 DN> way.]

 DN> At present, my main concern is with VMB sessions. These hammer the
 DN> CPU even when I have an ISR installed to issue the HLT.

yes, i've seen this as well...

 DN> Since I received no reply from this echo, I ended up wading through
 DN> object code using DEBUG in a VDM. The magic code hasn't changed,
 DN> but the register convention has. The AX register _must_ contain
 DN> zero under Warp. It is no longer the number of milliseconds for
 DN> DosSleep() to suspend the VDM.

"no longer" as in "this is how it was in v2.x but not in
v3.x and now different again in v4.x" ???  hummm... time to start
checking the OS version before loading AX and/or deciding which call to
give up... hummm 

 DN> However, it still doesn't work in a VMB session. [Mutter, mutter]
 DN> [Note that that is "mutter" in English, not a reference to my
 DN> mother in German. ... :-) ]

does grumble mean anything in another language? > i use
it instead of muttering, LOL!

)\/(ark