John,

> >At times, we do (or else I wouldn't have bothered looking into this
> >issue at all ;-) The best solution I came up with was to 
> exploit native
> >timer services and then reset the interrupt check counter in order to
> >force an interrupt check. The speed loss is almost neglectable (I
> >measured below 1%) which is a number I am willing to trade 
> for accurate
> >timing behavior.
> 
> Alright do you have a patch lurking somewhere?

The patch is completely platform specific.

> I'm assuming you need an external call in 
> primitiveSignalAtMilliseconds

No; all I'm doing is resetting the interrupt check counter each msec.

> also if we do have hosted OS timer support could we alter
> primitiveResponse the timerPending logic to avoid looking at 
> the clocks.

I didn't think about this yet - I just needed an msecs accurate timer so
I hacked the place I needed to. If you've got a proposal on how to solve
the problem more generally I'd be glad to hear about it.

Cheers,
  - Andreas