Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!beach.cis.ufl.edu!jma
From: jma@beach.cis.ufl.edu (John 'Vlad' Adams)
Newsgroups: comp.sys.amiga
Subject: Killing the Clock (Was Re: Blowing up your 1950)
Message-ID: <25702@uflorida.cis.ufl.EDU>
Date: 3 Dec 90 07:03:11 GMT
References: <964.2754A82B@weyr.FIDONET.ORG> <36456@cup.portal.com> <90336.141018DXB132@psuvm.psu.edu>
Sender: news@uflorida.cis.ufl.EDU
Reply-To: jma@beach.cis.ufl.edu (John 'Vlad' Adams)
Organization: UF CIS Department
Lines: 15

In article <90336.141018DXB132@psuvm.psu.edu> DXB132@psuvm.psu.edu writes:
>This is one of my pet peeves. It SEEMS like every crash messes up the clock.
>I'm lucky if my clock is still set properly at the end of a busy day.
>

Hmmm, that's weird!  I've had many crashes (from running uncooperative
programs with Paragon) but have yet to have my clock screwed up.  I'm
not saying it can't happen, as my buddy, a developer, sitting next to
me working on his Amiga 500 (030-33MHZ) Portable says it's happened to
him.
--
John  M.  Adams   --**--   Professional Student on the eight-year plan!     ///
Internet:   jma@beach.cis.ufl.edu   -or-   vladimir@maple.circa.ufl.edu    ///
"We'll always be together, together in electric dreams" Moroder & Oakey \\V//
Sysop of The Beachside.   FIDOnet 1:3612/557.   904-492-2305  (Florida)  \X/