"Warwick Michael Dumas" wrote in message I
thought JavaScript used timeouts based on the system clock-ticks.
Mind you, that hasn't stopped the same thing happening to me.

The problem is that because it was coded on a very slow machine, the timeout
was set to 10ms. This was negligible compared to the whole second it took
the code to run. Effectively the 10ms was doing nothing. Now that the code
is running on a fast machine, the flaw is obvious.

Martin