Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!uwmcsd1!csd4.milw.wisc.edu!hammen
From: hammen@csd4.milw.wisc.edu (Robert Joseph Hammen)
Newsgroups: comp.sys.mac
Subject: Re: JClock???
Message-ID: <2953@uwmcsd1.UUCP>
Date: Mon, 28-Sep-87 12:53:41 EDT
Article-I.D.: uwmcsd1.2953
Posted: Mon Sep 28 12:53:41 1987
Date-Received: Tue, 29-Sep-87 05:54:35 EDT
References: <1783@crash.CTS.COM>
Sender: daemon@uwmcsd1.UUCP
Reply-To: hammen@csd4.milw.wisc.edu.UUCP (Robert Hammen)
Organization: Computer Applications, Inc.
Lines: 27
Keywords: JClock, unsubstantiated rumors
Summary: JClock works fine for me

>Someone out there is using JClock? Hope you don't have an SCSI hard-drive!

Over the past couple years, I have seen references to the fact that JClock
is 'a known killer of hard drives.' I personally have used JClock all of 
the time on virtually every machine (except the Mac II) with and without
hard drives. I have never had a disk crash (hard or floppy) with it installed,
and have had no problems with it at all. I think that it is time that this 
rumor about it end, unless someone can come up with evidence that JClock 
destroyed his disk.

BTW, everyone using System 3.2 or later should really take advantage of the
JClock INIT resource that you simply copy into your System Folder. That way
you don't have to run an application to install it and use ResEdit to remove 
it. What probably happened to someone is that they ran the JClock installer
to put the INIT in their System file and their System file was damaged for
some reason or another.

>UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!maddie
>ARPA: crash!pnet01!maddie@nosc.mil
>INET: maddie@pnet01.CTS.COM

Robert Hammen	Computer Applications, Inc.
hammen@csd4.milw.wisc.edu	Delphi: HAMMEN		GEnie: R.Hammen


Robert Hammen	Computer Applications, Inc.
hammen@csd4.milw.wisc.edu	Delphi: HAMMEN		GEnie: R.Hammen