Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!batcomputer!itsgw!steinmetz!uunet!dalcs!dalegass
From: dalegass@dalcs.UUCP (Dale Gass)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Norton SD program problem
Message-ID: <3057@dalcs.UUCP>
Date: 26 Oct 88 13:02:04 GMT
References: <12440034836014@KL.SRI.COM> <11@gsy1.UUCP> <1062@acornrc.UUCP> <4374@rayssd.ray.com>
Reply-To: dalegass@dalcs.UUCP (Dale Gass)
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada
Lines: 20

In article <4374@rayssd.ray.com> cc@rayssd.ray.com (Charles R. Coday) writes:
>I had the identical problem happen to me with an IBM AT.  I only use
>PCTOOL's compress now, but I have no guarantee it wouldn't do the same.

Watch out for PCTOOL's compress.  I had a friend using PCTOOL's compress on
a badly fragmented disk, and it popped out with some bizarre error number,
leaving his hard disk hopelessly scrambled (of course, he neglected to do a
backup of vital information).

I use DOG (disk organizer) and have never had a problem with it; I find it to
be the most efficient, reliable and flexible optimizer around.  Takes a bit
longer to learn how to use, but it's worth it.  It allows you to place files
exactly where you want for optimum performance (I place all directories at
the beggining, for lightning fast chkdsk's and dir's, and file opens; then
I put small frequently accessed programs, then big static applications, then
dynamically changing programs, then data; it really improves performance
better than a straight SD or COMPRESS.)

-dalegass@dalcsug.uucp
{watmath | uunet}!dalcs!dalcsug!dalegass