socket malfunction with phindow running

I have some code to have a socket established, server side is under qnx
4.25, client side is under WinNT. the socket
works normally, and server keeps running if NT side is dead either by
unplugging the network cable or
lost power…

However, From my NT side, I added piece of code that spawns phindow, then if
I unplugged t he network cable
or turn off NT machine, my server on QNX side hangs, it wouldn’t process
any code.

Is there any known conflict between Socket and Phindow?

I just realized that this has nothing to do with socket, I can run any app
under qnx, and phindow from NT
to it, unplugged the cable, or turn off the NT machine, app under Qnx
wouldn’t run… wha’s the problem here??

sorry that I wasn’t getting much response from qnx4 newsgroup. Pl help!
Mario Charest <goto@nothingness.com> wrote in message
news:a6tc97$hh7$1@inn.qnx.com

“ran zhang” <> rzhang@vamcointernational.com> > wrote in message
news:a6t9ek$ftg$> 1@inn.qnx.com> …
I have some code to have a socket established, server side is under qnx
4.25, client side is under WinNT. the socket
works normally, and server keeps running if NT side is dead either by
unplugging the network cable or
lost power…

This is a QNX6 conference, please use qdn.public.qnx4 for QNX4 related
question, that will increase your chance of getting a response.


However, From my NT side, I added piece of code that spawns phindow,
then
if
I unplugged t he network cable
or turn off NT machine, my server on QNX side hangs, it wouldn’t
process
any code.

Is there any known conflict between Socket and Phindow?
\

“ran zhang” <rzhang@vamcointernational.com> wrote in message
news:a6t9ek$ftg$1@inn.qnx.com

I have some code to have a socket established, server side is under qnx
4.25, client side is under WinNT. the socket
works normally, and server keeps running if NT side is dead either by
unplugging the network cable or
lost power…

This is a QNX6 conference, please use qdn.public.qnx4 for QNX4 related
question, that will increase your chance of getting a response.

However, From my NT side, I added piece of code that spawns phindow, then
if
I unplugged t he network cable
or turn off NT machine, my server on QNX side hangs, it wouldn’t process
any code.

Is there any known conflict between Socket and Phindow?