Unable to set custom pagefile over 4096MB

[Guest]

I just added a second hard drive to my Vista Home Premium machine (Intel 6700
core 2 CPU; 4 GB of physical memory).

I successfully and easily moved my pagefile to the new blank (formatted in
Vista) drive. However, when I try to set a custom size on the pagefile, an
information window pops up and tells me to set the maximum size greater than
or equal to the minimum and less than 4096. Funny, because system managed
picks >6500 MB. I've set no page file on any drive, rebooted and tried again
several times, and each time I'm limited to <= 4096 as max. custom size.

Why the limitation? Its a 320GB HD, BTW and I'm using the 32bit version of
Vista.

 

[Guest]

It was formatted as NTFS, not FAT32.

 

[Guest]

Having 1Gb/1024Mb of memory I have never used a pagefile exept when
running a poorly written P.C. game called Dark Messiah. If you have 4 GB
of memory, unless your P.C. is running an IT departement, you do not
need to allocate a pagefile at all, despite what you will hear from others
on the subject

If you insist on its use, so that no unsecured data is contained in the
paging
file: do search on ClearPageFileAtShutdown and consider clearing it. Would
take some time to clear 4Gb at shutdown.

 

[Michael Palumbo]

Having 1Gb/1024Mb of memory I have never used a pagefile exept when
running a poorly written P.C. game called Dark Messiah. If you have 4 GB
of memory, unless your P.C. is running an IT departement, you do not
need to allocate a pagefile at all, despite what you will hear from others
on the subject

If you insist on its use, so that no unsecured data is contained in the
paging
file: do search on ClearPageFileAtShutdown and consider clearing it.
Would
take some time to clear 4Gb at shutdown.

Actually, no matter the RAM you have it's a good thing to have at least a
small page file.

Unused parts of the OS and other running software will be removed from RAM
and swapped to the page file, making room in RAM for other, used/useful
things.

Even the "tweak" to force none of the kernel to be paged is a bit foolish.
Why have parts of the kernel that are used rarely, or in some cases, not at
all, loaded into RAM when you can page it to the hard drive and use that RAM
for something else? If it's needed, it's in the page file and can easily
(if not very quickly) be loaded into RAM for use.

Okay, I admit with RAM so plentiful and inexpensive these days (at least for
DDR 2) fifty or so megabytes of kernel isn't a big deal, but it's a good
example.

Mic