From: Mike '/m' 


The reason I used it was to allow four DOS programs to play nicely in their
respective DOS boxes on OS/2.

For that purpose, it worked very well, with each program able to maintain
19600bps communications over the modem without losing a character. Before I
put the yield call into the loop, only one program would run, the other
three just stalled.

 /m



On Mon, 23 Jun 2003 19:34:10 -0400, "Tony Ingenoso"
 wrote:

>This still results in the CPU getting pegged when a DOS app runs.  Whoever you
hand off to is running, and the DOS app just swings
>to the back of the scheduling line.  A yield isn't the same thing as a sleep,
which DOS apps do by burning CPU and watching the
>clock or BIOS countdown ticker.  What you can get with the yield is better
overall responsivness by not waiting for the scheduler to
>preempt the DOS app.
>
>"Mike '/m'"  wrote in message
news:stdefvgsbdippfmb1jfjj7rks0p4819n3l{at}4ax.com...
>>
>> There was an Int 0x21 call you could do that would yield the CPU to
>> another process.   I used that call whenever I wrote a loop to wait for
>> keyboard input.
>>
>>  /m
>

--- BBBS/NT v4.01 Flag-4