> 	Now that the test cycle for stopping the clock is shorter, I
> think that my symptoms are due to serial activity (not netscape as

Odd.. maybe there's interference caused by calling delay() from the zs
driver on sun4s? The serial chip interrupts at a higher priority than
does the clock. You could experiment with a strategically placed splhigh()
in clockintr() and see what happens.

-pk