🚀 go-pugleaf

Is your Comms thread using Synchronize to send info back to the main thread?
If it is, it might be locking up waiting for the main thread to complete the
Sleep()
as I think that the main thread won't get messages until the sleep has
completed.
(I think anyway)
HTH Pete

"Chris Phillips" <chris.phillips@corusgroup.com> wrote in message
news:40eea7bc@newsgroups.borland.com...
>
> I have an application with 3 threads to it.  One thread is simply
processing
> serial IO but must run close to real-time - I have given it priority
> tpTimeCritical.  This thread is executed by the main program.  However, if
> the main program is doing something processor intensive (such as
retreiving
> a number of database records), then my Comms thread doesn't get a look in
> until the processor intensive part has finished.  I have put a Sleep
command
> into the processor intensive loop thinking that it will allow the Comms
> thread to continue with its stuff, but to no avail.