Answering msg from andrew clarke to rowan crowe,
on Friday April 28 1995 at 21:50

 ac>         case T_DV:
 ac>             asm {
 ac>                 mov ax, 101ah
 ac>                 int     15h
 ac>                 mov     ax,1000h
 ac>                 int     15h
 ac>                 mov     ax,1025h
 ac>                 int     15h
 ac>             }
 ac>             break;

    Oooh, it's a well behaved timeslice, saves and restores the stacks too.
Most people just use INT 15h/AX=1000h

    BTW, the above code will have undefined results if DV is not present,
and I wouldn't recommend it be called if DV has not been detected.

 ac> The code is there (partially), but ironically pause() is not called
 ac> from anywhere in the program!

    Bummer.

 rc>> DV timeslicing is easy, as is Doze and OS/2

 ac> Is INT 28h safe to call in native DOS, Windows or OS/2 ?

    It's safe within DOS, since it's a DOS interrupt. :) It's called while
DOS is doing stuff like waiting for a keypress, but it's fairly useless as
a generic timeslice because it's also called at other times when DOS is
actually doing something. I wrote a simple utility to convert INT 28h
timeslices to DESQview timeslices, and even a simple "dir" gets
very jerky -- because INT 28h is being called several times while it's
drawing out.

---