Jim,

> Perhaps all signaled event handler have been replaced by threads
> (and maybe professional wrestling is for real). Or maybe all
> Unix's (no, plural of Unix is not Multix) have fixed malloc
> to be AST-re-entrant. And maybe Borland has fixed gds_alloc
> to be AST-re-entrant. If not, you will need to find a work
> around.

I have taken a look at the source code once more and now I believe that
asynchronous events delivery is implemented on the client via threads on all
platforms which support multithreading. Signals are used otherwise.
MULTI_THREAD macro is used to determine which mechanism should be used. But
it seems to be undefined for Win16 (WINDOWS_ONLY) and the classic versions
of the server for HP10, DGUX, LINUX.

Cheers,
Dmitry