Persuading XP to use 1GB RAM

[Larry(LJL269)]

I recently upgraded to 1GB 2100 DDR RAM 4 my 1.8GHz P4 &
opened the Task Manager (TM) to find PF Usage = 250MB even
tho Available Physical Memory = 750MB. This contradicts
'Windows will always try to find some use for all of RAM —
even a trivial one" @ http://aumha.org/win5/a/xpvm.htm !!
I had set Pagefile=(10,50) on C & let XP manage it in its
own partition S on HD#2. Xp had set it to 1.5GB. So in
spirit of Alex's page above, I changed this to (20,1000)
giving it plenty of room to expand if it need be.
That's when the shit hit the fan. This did NOT get XP to
keep more code & variable memory & buffers & stack state &..
into RAM. Moreover these TM numbers r not even consistent
given the definitions in TM Help file. Here are some
problems but for the bottom line go to (4) below:

1-I cant find any N numbers that sum to total physical
memory(1048MB).
Available + System Cache = 1051MB

2-Total Commit Charge = 201MB but Page File Usage = 196MB.
TM help says 'The value for Total is the same as that
depicted in the Page File Usage History graph.'

3-Total Commit Charge = 201MB < Sum of all 36 processess'
Memory Usage. ( add Total Kernel Memory & they are about
equal. Coinsidence? ).

4-My Peak Commit hit 961MB so VM increased to 760MB & my PF
Usage= 197MB yet I have 752MB Available Physical Memory,
which is where I started.

So it would seem the only way to get XP to max RAM usage is
to set Max & minVM=~100MB & hope u DONT run out.

Pardon my French but I dont know whether 'to shit or go
blind'

Your help is MUCH appreciated as are comments /suggestions/
corrections. Thanks- bye- Larry


Any advise given is my attempt to show appreciation for all
the excellent help I've received here but I'm no MVP so it
may only apply NUGS (Normally, Usually, Generally, Sometimes

 

[SlowJet]

Yaaaaaaaaaaaaaaaawnnnnnnnn

It works the way it works and so far the ones complaining show a complete
lack of understanding about Windows Vurtual memory.

Think of the Pyhsical memory as a high speed buffer for your DLL's, paged
file and all the vurtual memory allocated by programs. Like a database
buffer pool.

OK, think of your phyical memory as the observatory on the Empire State
building and behind you are several elavators going up and down with
precesion JIT schedules making room for more observers as others leave. Now,
on ocation (99% of the time for a simple PC), there's hardly anyone
observing, the eleavators are settings, waiting for a button to be pushed,
and just in case one of the obsevers that left whats to take another look,
zip, he's up there in no time and his fav spot is still there. And any left
over floor space is used lost and found back packs.

SJ