🚀 go-pugleaf

In article <369@esquire.UUCP> sbb@esquire.UUCP (Stephen B. Baumgarten) types:
>In article <3979@cup.portal.com> M_David_Green@cup.portal.com writes:
>>I seem to recall that a few months back there was a discussion going on h
>>about the JCLOCK init and the way that it seems to destroy hard drives.  Well,
>>these things never come to mind until after the fact, eh?

Let's try to put this rumor to rest, again. I have used JClock on many different
machines, still do (except on the Mac II or under MultiFinder, and only for
cosmetic reasons) and I have NEVER had a problem. I seriously doubt JClock is
the culprit here.

>well worth it.  As a side note, if anything terrible does happen to
>your hard disk (i.e., more than just needing to rebuild the desktop),
>DON'T (I repeat, DON'T), let any so-called "disk saver" utilities
>"fix" the disk.  This includes Disk First Aid (which usually only
>works on mountable disks anyway)

I disagree with this as well. Disk First Aid is a limited recover program.
It usually attempts to check all of the HFS data structures on a disk (which
must be mountable). I find that often it is able to "repair" my disk when 
there is nothing visibly wrong - because the amount of free space is usually
wrong. It is a good idea to run this utility every once in a while (I do it
weekly) just for that reason. I have never seen Disk First Aid make a disk
any worse than it was. But it's not always useful for damaged disks, and that
is where MacZap is useful.

///////////////////////////////////////////////////////////////////////////
/ Robert Hammen		Computer Applications	hammen@csd4.milw.wisc.edu /
/ Delphi: HAMMEN	GEnie: R.Hammen		CI$: 70701,2104		  /
///////////////////////////////////////////////////////////////////////////