NOTE: DCTEdit v0.04 [7]
 VK>The serial port has it's own interupt which puts/gets data
 VK>in a que, the timer then looks at that que, if it's empty
 VK>it waits until something's there.
 GW> If that is the case why wait in the timer interrupt? Just exit the
 GW> timer interrupt handler and deal with it next time round...
Ok I think this thread should stop pretty soon, two reasons: 1. It's off 
topic, and 2. I have already solved the problem by populating the main code 
with calls to the routine that was previously the timer ISR, and timed too.
The reason for waiting in the ISR and not skipping until the next one was 
because the next one occured 55ms later which was too much of a delay to be 
acceptable.
Thanks to everyone who has helped with this, took me a while to see that 
there really was a more reliable(albeit not so nice) way of doing it.
... Love your neighbour...  Just don't get caught.
--- Maximus 3.01
---------------