Archived from groups: microsoft.public.windowsxp.basics (
More info?)
I've removed the page file completely, then ran defrag, then re-created it,
seems to work for me!!!
-Tiaira
"Colin Barnhorst" <colinbarharst@msn.com> wrote in message
news:OK%23g8lKtEHA.2688@TK2MSFTNGP14.phx.gbl...
> Diskeeper 9, like 8, defrags the page file during a boottime defrag run
> that is set up manually.
>
> --
> What's another word for synonym?
>
> "Alex Nichol" <alexn.mvpdts@ntlworld.delete.com> wrote in message
> news:cu65n05huk6a9knevhqk4m2s15ptf1vnkv@4ax.com...
>> Andrew E. wrote:
>>
>>>You can/should do that periodically,actually if you run other hds and
>>>have
>>> them set to "let windows manage" in system properties or have them set
>>> for
>>> the page file you'll see fragmented files that were unable to be
>>> defragged
>>> because thier in/were in use when defragging.The trick is to set the hd
>>> with
>>> "no page file" then click set 2X to set,when enabling,a restart will be
>>>prompted
>>> to verify you did this correctly.For details om page file,try search at
>>>microsoft,
>>
>> Provided the initial size of the file is set adequate to cover normal
>> needs (and on larger size RAM, say 512 MB up) it will almost certainly
>> be excessive, and you start it up on a disk that is not fragmented, then
>> it will be in one piece and will stay that way. If the disk has free
>> space in fragments the inbuilt defrag tool will not consolidate them,
>> nor will Diskeeper (unless they have changed policy in recent versions)
>> though Perfect disk will. The file might then be started in at least a
>> partly fragmented state.
>>
>> Fragmentation of the file on the whole is over-hyped. On a large modern
>> RAM it has little actual traffic, and retrieval from it is essentially
>> random, so fragmentation makes little difference.
>>
>> See my page www.aumha.org/win5/a/xpvm.htm
>>
>> --
>> Alex Nichol MS MVP (Windows Technologies)
>> Bournemouth, U.K. Alexn@mvps.D8E8L.org (remove the D8 bit)
>
>