by H.G.Muller » 03 Aug 2010, 16:21
I sometimes have that problem too. Have you tried setting a /delayAfterQuit? I think a problem might be that WinBoard kills the adapter before the adapter gets the chance to kill the engine. Normally, WinBoard would send a quit command to the adapters when PSWBTM tries to kill it, and if the adapters don't respond, kill them. But when the engines are running, they might soak up all CPU time, and the adapter might not get some before WinBoard gets impatient and kills it. With a /delayAfterQuit, (in msec) WinBoard will grant the adapter more time to terminate the engine.