Hi Mike:

MB> I suggested that the 
MB> remedy for this specific problem is to run the thread that 
MB> sleeps at a high priority, so that it will be made ready at 
MB> the expiration of its sleep and will be scheduled 
MB> immediately.

This is not meant as a technical critisism of your suggestion, but
does an on-screen clock really warrant a high priority thread?  If the
clock looks wacky, perhaps it is because there isn't enough resource to
adequately run a clock.  Again, your comment was accurate and
informative.  This is just an opportunity for me to vent.  I like the
analog clock that comes with WARP;  I can set it such that it only
refreshes once a minute.  This seems like a more resource friendly
clock.


Best wishes,

Tom

 * KWQ/2 1.2g * Floppy not responding...Format HARD DISK instead (Y/n)?

--- GEcho/2 1.20/Pro