Path: utzoo!attcan!uunet!husc6!rutgers!mailrus!cornell!hal
From: hal@gvax.cs.cornell.edu (Hal Perkins)
Newsgroups: comp.sys.mac
Subject: Re: DiskExpress Version 1.5
Keywords: DiskExpress
Message-ID: <22702@cornell.UUCP>
Date: 17 Nov 88 19:41:40 GMT
References: <1746@cadre.dsl.PITTSBURGH.EDU> <88Nov16.150749est.9522@neat.ai.toronto.edu>
Sender: nobody@cornell.UUCP
Reply-To: hal@gvax.cs.cornell.edu (Hal Perkins)
Organization: Cornell Univ. CS Dept, Ithaca NY
Lines: 25

In article <gibberish deleted>  dudek@ai.toronto.edu (Gregory Dudek) writes:
>  How does the Quick optimization actually do differently, as compared
>to the standard optimize?  The flyer didn't explain what it avoided
>doing to get so quick.

Quick optimize attempts to copy only the fragmented files to contiguous
sections of free space.  If it can't find a block of free space large
enough for a particular file, it displays a warning and skips the file.

The standard optimization rearranges the entire disk.  Quick optimize
is much faster, but it doesn't leave you with a single area of free
space, and it may be unable to do much if the free space is badly
fragmented.

The two optimizations complement each other.  Do a quick optimize
regularly to unfragment files; do a full optimize every now and then
when the free space gets too chopped up.

My opinion is that the new features are definitely worth the cost of	
the upgrade--we're not talking about a whole lot of money here, and the
company has to recover its costs somehow.

Hal Perkins              hal@cs.cornell.edu

Disclaimer:  No connection with ALSoft except as a satisfied customer.