>Anyone know why?  (Dim recollections of `timing data' mention in a
>FAQ somewhere.)

This seems to happen on my machine too.  I imagine RISC OS is relying on the 
state of some of its workspace after a reset.  It can get into the same state 
if a RISC OS program screws up particularly badly.

p.


unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]

Reply via email to