MISS 6GB--MORE DEFRAGGLER PROBLEMS

From: "chanook*xyz*" <>
Subject: Re: Help--what happened to 6GB?
Date: Tuesday, September 30, 2008 12:08 PM

chanook*xyz thankyou for getting back to me. I did go to the website and
found out in the defraggler forum I was not the only person to have 6gb
disappear! The idea was that --yes-- something to with restore points--so I
did
that--uninstalled the defraggler!!! But now, the touchpad doesn't work
right and tried to do a check disk at startup
for the volume to fix any errors----problems with that. Screen comes up "ck
disk scheduled" next line says "ck
disk cancelled"!!!! It WON"T fix errors, just boots up. Boots up after
that fine. Help please any ideas??
Thankyou for any help - in layman's terms.

"Paul Montgomery" <> wrote in message
news:...
> On Tue, 30 Sep 2008 07:57:18 -0400, "Richard Urban"
> <> wrote:
>
>>Defragmenting a drive neither adds to, nor detracts from, the amount of
>>free
>>space available on the drive. All it does is rearrange the "file cabinet"
>>into something more logical for the operating system to work with.
>
> Correct - IF the disk being defragged isn't a disk that is protected
> by System Restore, OR if it is protected and the cluster size is 16k
> or greater. Most default NTFS formatting results in a 4k cluster
> size.
>
> The System Restore function and the Shadow Copies that are saved by
> Vista are operating at the sector level on the disk. Any changes in
> the use of sectors is seen by System Restore and the Shadow Copy
> Service to be file system updates that need to be stored. The more
> files that are moved around during a defragging, the larger the
> increase in the amount of space used by those services and the larger
> the reduction in the free space on the drive.
>
> Space can be regained after a defrag and System Restore by deleting
> all but the most recent restore point in Disk Cleanup.
>
> The situation can be rectified (at a cost of starting disk space) so
> that it won't happen again by changing the cluster size to 16k or
> larger.
>
>
>
>
>

STOP MAKING PROBLEMS FOR YOURSELF, ALL OF THIS COULD HAVE BEEN AVOIDED
MAYBE THIS WILL TEACH YOU A LESSON

chanook*xyz* wrote:
>
> From: "chanook*xyz*" <>
> Subject: Re: Help--what happened to 6GB?
> Date: Tuesday, September 30, 2008 12:08 PM
>
> chanook*xyz thankyou for getting back to me. I did go to the website and
> found out in the defraggler forum I was not the only person to have 6gb
> disappear! The idea was that --yes-- something to with restore
> points--so I
> did
> that--uninstalled the defraggler!!! But now, the touchpad doesn't work
> right and tried to do a check disk at startup
> for the volume to fix any errors----problems with that. Screen comes up
> "ck
> disk scheduled" next line says "ck
> disk cancelled"!!!! It WON"T fix errors, just boots up. Boots up after
> that fine. Help please any ideas??
> Thankyou for any help - in layman's terms.
>
> "Paul Montgomery" <> wrote in message
> news:...
>> On Tue, 30 Sep 2008 07:57:18 -0400, "Richard Urban"
>> <> wrote:
>>
>>> Defragmenting a drive neither adds to, nor detracts from, the amount of
>>> free
>>> space available on the drive. All it does is rearrange the "file
>>> cabinet"
>>> into something more logical for the operating system to work with.
>>
>> Correct - IF the disk being defragged isn't a disk that is protected
>> by System Restore, OR if it is protected and the cluster size is 16k
>> or greater. Most default NTFS formatting results in a 4k cluster
>> size.
>>
>> The System Restore function and the Shadow Copies that are saved by
>> Vista are operating at the sector level on the disk. Any changes in
>> the use of sectors is seen by System Restore and the Shadow Copy
>> Service to be file system updates that need to be stored. The more
>> files that are moved around during a defragging, the larger the
>> increase in the amount of space used by those services and the larger
>> the reduction in the free space on the drive.
>>
>> Space can be regained after a defrag and System Restore by deleting
>> all but the most recent restore point in Disk Cleanup.
>>
>> The situation can be rectified (at a cost of starting disk space) so
>> that it won't happen again by changing the cluster size to 16k or
>> larger.
>>
>>
>>
>>
>>
>