Paging files in XP

  • Thread starter Thread starter John L Ward
  • Start date Start date
J

John L Ward

This is probably an obvious one, but:
Why is the paging file in XP bigger than that which you
set in the systems settings? Even when I set the paging
file to zero, system information still shows a paging
file exists. With the standard machines that we are
ghosting, our best-guess paging file size means that we
are then having to span two CDs which is a pain. Can
anyone point me to an article that describes why the
paging file behaves in this way, and what I can do about
it?

Cheers

John L Ward
 
I am not certain that it is the paging file that is the cause of your image
file having to span 3 dc's.

It has been my experience, using Drive image, that the completed image file
size is smaller than that estimated by Drive Image, by "exactly" the total
of the pagefile and the hibernation file. My guess is that these files are
not really included in the image (no reason to be), but that starting and
ending "markers" for the files are somehow retained. These markers then
indicate on the first reboot where these files should be placed by the
operating system.

On using my defrag program, I find that both the pagefile and the
hibernation file are in the same "relative positions" after restoring an
image. This could be a result of the fact that Drive Image performs a
"sector by sector" copy (it copies only sectors that have information in
them).

I have noticed this action since using version 4 of drive image, and it
continues still in Drive Image 7!

I may be wrong, but I believe that Ghost would do the same thing! If it is
not, it is imaging unnecessary information!
 
Back
Top