-=> Quoting Craig Swanson to Phil Crown <=- 

 PC> APAR= PJ16508
 PC>  DOSCONNECTNPIPE() FAILS ON A FAST SYSTEM WITHOUT A DOSSLEEP.
 
 CS> Overall, I'd have to say that named pipes in OS/2 2.x and 3.0 are
 CS> buggy and apparently have a reputation within IBM of being a mess
 CS> nobody wants to touch -- maybe because they have stuck around since
 CS> OS/2 1.x (yes, it's still 16-bit code!) and may have originally been
 CS> written by Microsoft.  For example,recently I've again had problems

I haven't used named pipes much, except for debugging.

 CS> From this, it looks like you get a TID that is not 0xFFFF, but the
 CS> thread doesn't start.  How are you determining if the thread is or is
 CS> not starting? Can you write something to stdout (or to a file) at the
 CS> start of the thread and see if this shows up?  Maybe the thread has
 CS> started and has gotten stuck or screwed up somehow?

My problem with _beginthread() not starting was that I was assuming that it
had retunred before it may actually have, or something like that.

Calling WinSendMsg instead of WinPostMsg fixed that. :-)

phil.crown{at}bluecafe.com

--- Blue Wave/Max v2.21a Beta