persaud@seas.gwu.edu (Steve Persaud) (04/09/90)
Some new info brought to my attention about dead clocks:
1. The V1.3 SETCLOCK command has a problem. Therefore, SETCLOCK RESET
will not work properly. BTW, SETCLOCK RESET is supposed to completely
reset clocks who have been turned off or whose test bits have been
set by a wild program.
2. V1.2 SETCLOCK doesn't have the RESET option, so you'll need V1.3.2
which I don't have.
3. I did have a program go out of control before my clock died.
4. Maybe the clock battery is low on charge and needs to be recharged.
5. Maybe it really is dead.
-Steve
--
Steven Persaud | UUCP: uunet!seas.gwu.edu!persaud@uunet.uu.net
{space reserved} | INTERNET: persaud@seas.gwu.edu
{for future use} | BITNET: DX926C@GWUVM