-=> Quoting Chris Hoppman to Scott Adams <=-

 SA>      Another thing is why do you need the timeslice?  A multi-tasking
 SA>      software? A TSR? A game?  The particular type of software
 SA>      also indicates how to go.  A game sometimes need fast and
 SA>      sometimes slow timeslices, for example.
 SA> 

 CH> 16-Bit Real Mode BBS software.

        Then likely you'll not need much of a timeslice since real
        modes tend to be exclusive programs.  Though with windows
        and dos boxes that's somewhat true today.  So its up to
        you if you need it for 16 bit work.
 
 SA>      Now with that stuff said have you checked out SWAG?  It has
 SA>      at least 3 sample codes using the keyword time slice in it.
 SA>      One for os/2 and Desqview and 2 others general code sources.
 SA>      Keep in mind though those are in pure assembler.  But ASM
 SA>      is a good way to go with timeslices.

 CH> Yes, but I don't need to learn how to do them, *except if there is
 CH> others for  Win2k*, I needed to learn the proper ways to execute them. 
 CH> The Where and When..  As, my example program shows.

     We'll I'd still look at SWAG it might give you that advice.

     As to where and when its judgemental.  Theres no solid rule
     of thumb.  It depends on the program.

     If your running a program that takes alot of constant input
     like a game then they are good.  If your using a when needed
     input like a spreadsheet then theres not much need for them
     unless you plan to allow shared programs.








... "Well, this is it." - Garibaldi
--- Fringe BBS