Re: W2K Defrag Exclusions
OK, sounds like maybe I'll just send the analyzer packing and arbitrarily do
it twice a year.
Bob I wrote:
> No I was referring to the "analyzer" getting confused. I have seen it
> not recommend a defrag when it was choking on broken files and then
> repeatedly recommend defragging when only a couple files were broken.
>
> Roger Fink wrote:
>> Yup, just an opinion from Micro$oft, but in this case I give it more
>> credence, since they can't make/lose any money on the deal.
>>
>> Bob I wrote:
>>
>>> If it doesn't lie. ;-) Unless you are doing a bunch of loading and
>>> unloading files to and from the hard-drive, most people worry too
>>> much about defragging.
>>>
>>> Roger Fink wrote:
>>>
>>>
>>>> Ah, no wonder I couldn't find it.
>>>> I can still use it to "analyze" though, which has the advantage of
>>>> offering up an opinion as to whether defrag is necessary or not.
>>>>
>>>> Bob I wrote:
>>>>
>>>>
>>>>> It's a "simple" defrag tool. It doesn't have that level of
>>>>> options.
>>>>>
>>>>> Roger Fink wrote:
>>>>>
>>>>>
>>>>>
>>>>>> In order to defragment my hard drive I need to exclude the file
>>>>>> gobackio.bin (the file Goback writes to, which takes up 10% of
>>>>>> the drive space). I can do this for my Fix-It Utilities defrag
>>>>>> program, but I haven't been able to figure out how to do it with
>>>>>> the OS System Tools defrag program, which I think is a better
>>>>>> choice here. How do I do this?