by H.G.Muller » 13 May 2011, 13:48
I don't think so. Timestamp / timeseal read the clock of your own computer when they hand your opponent's move to WinBoard, and then read that clock again when WinBoard hands them the move of your engine. It then subtracts the two, and sends the difference to the ICS (together with your move), to let it know how long you have been thinking.
Only when you run something that would cause such a severe system load that you get delays between timeseal and WinBoard, or between WinBoard and the engine, this lag would be added to yor thinking time. But WinBoard could never know the latter. The only way to know it is let the engine record how long it has been thining on the last move, and then compare that to how much the GUI (or ICS) decreased the time on its clock because of that move. Any difference must have been lag (or rounding).