James Wells ([EMAIL PROTECTED]) wrote: > > I may be wrong here, but as the child never returns control to the parent a > timeout in the parent would have no effect on the problem that I'm having. > My suggestion would be to put the timeout in the child where it's waiting > for an interrupt as this is where it seems to be hanging. > > Would this work or have I not understood what's going on? Sorry, my C isn't > very good! > > James Wells >
Well i had no time to build the 1.1 tonight (i've to finish a school report and that takes me lot of of time) btw, the timeout must be set in parent, it waits for a usr2 signal from child and if the child is blocked in the read call, that means the modem doesn't send an interrupt (we can do nothing there). BUT we must keep reading the endpoint in child otherwise the modem freezes. AND the program that users see locked is the parent process not the child (because it is bacgrounded) Well this week end the 1.1 will be out and a 1.1.1 will follow soon. -- Edouard Gomez Liste de diffusion modem ALCATEL SpeedTouch USB Pour se d�sinscrire : mailto:[EMAIL PROTECTED]?subject=unsubscribe
