PF>
  > The pipe is a message pipe.   The dos program calls
  > DosSetNmPHandState() to change the read mode to nowait.  So
  > far so good. When I call DosWrite from the dos program
  > under real dos,  it ends up in an INT 3 in some library
  > somewhere!
PF>

 JdBP>   Are these calls from the 1.x Toolkit Family API 
 JdBP> library ?  If so, then
 JdBP>   you are on you own.  (-:

Yes and no.  The 1.x fapi code works better,  but the pipe _always_ blocks
on a DosWrite,  which is unacceptable.  IBM's lan server comes with a new
set of 16bit dos lib's, which is what I was having the problem with.

I have since discovered that the INT 3 program only happens on one PC so
far --- mine.  Out of desperation,  I set myself up as a server,  and the
normal server as the dos client,  and everything worked!  I installed it on
about 6 PC's in production last night,  and they all worked too.   I have
no idea what it doesn't like about my pc.

 JdBP>   An explicit INT 3 instruction in a library is either an indication
 JdBP>   that the programmer never finished that portion of the library, or
 JdBP>   that that portion of code is only ever expected to execute under
 JdBP>   exceptional circumstances.

Exactly my thoughts.

 JdBP>   What version of DOS is this ?  Versions prior to 4.01 (hello Andrew

I tried more than one (4.0 and 6.22).

 JdBP>   How does this DOS program fare in a VMB ?

Works perfectly,   even on my PC.

--- Maximus/2 3.00