T
Tiny Tim
I've just rebuilt my Win XP Pro laptop this week and applied all MS updates.
I have 512MB RAM and like to set a custom pagefile size of 512MB-512MB in
contiguous disk space - i.e. fully defragged and unable to get fragged.
However, Windows seems to have taken it into its head to make my pagefile
768MB. If I go into the advanced performance settings I still see my 512-512
custom settings on the C: drive but Windows Explorer tells a different story
and the defrag disk analysis picture shows a huge pagefile fragged all over
the place.
I do not recall seeing this behaviour in the past. I am not running anywhere
near enough programs to even exceed the 512MB RAM and indeed, as I write
this I currently have the pagefile disabled altogether with no ill-effects.
I've tried the MS Knowledgebase and can see nothing about this little quirk.
Does anyone know why my pagefile has a mind of its own?
On a separate note I saw in the Knowledgebase that MS recommends setting up
the pagefile on a separate PARTITION from the system partition. I can see
the sense in a separate DRIVE but fail to see the merit in having the drive
heads skipping back and forth from system files to a separate partition. Can
anyone shed any light on why keeping the pagefile far apart from the system
files makes for a speedier system? Remember, my intention is to have a fixed
size 512MB pagefile that is not fragged and will not fragment if the size
stays fixed, and is physically close to the system files. It's just a pity
that Windows has other ideas.
Thanks for any help.
Tim.
I have 512MB RAM and like to set a custom pagefile size of 512MB-512MB in
contiguous disk space - i.e. fully defragged and unable to get fragged.
However, Windows seems to have taken it into its head to make my pagefile
768MB. If I go into the advanced performance settings I still see my 512-512
custom settings on the C: drive but Windows Explorer tells a different story
and the defrag disk analysis picture shows a huge pagefile fragged all over
the place.
I do not recall seeing this behaviour in the past. I am not running anywhere
near enough programs to even exceed the 512MB RAM and indeed, as I write
this I currently have the pagefile disabled altogether with no ill-effects.
I've tried the MS Knowledgebase and can see nothing about this little quirk.
Does anyone know why my pagefile has a mind of its own?
On a separate note I saw in the Knowledgebase that MS recommends setting up
the pagefile on a separate PARTITION from the system partition. I can see
the sense in a separate DRIVE but fail to see the merit in having the drive
heads skipping back and forth from system files to a separate partition. Can
anyone shed any light on why keeping the pagefile far apart from the system
files makes for a speedier system? Remember, my intention is to have a fixed
size 512MB pagefile that is not fragged and will not fragment if the size
stays fixed, and is physically close to the system files. It's just a pity
that Windows has other ideas.
Thanks for any help.
Tim.