Gustaf said:
I recently replaced the RAM in my laptop (running Win XP SP3), so that
there's now 2 GB. But I never see Windows come even close to using 2 GB;
there seem to be a limit at 1 GB. When dad did the same with his laptop,
a seller told him that there's no use installing more than 1 GB, because
XP can't handle it. But surely, there must be a way of tweaking the
settings so that it uses 2...? Where are those settings, and is there
anything I need to know before meddling with them?
Gustaf
Here is your homework assignment.
http://blogs.technet.com/markrussinovich/archive/2008/11/17/3155406.aspx
Now, the problem is, getting a copy of the testlimit
program, so you can play with it. I would have
thought the file would be on Sysinternals, but
perhaps it is only included with his book now.
In any case, I was able to find a non-descript
version of the program here. I tested it
enough, to get a demonstration of it working,
and that is what is described below.
http://web.archive.org/web/20060913215548/http://www.sysinternals.com/Files/Testlimit.zip
Now, what is wrong with this file ? Well,
it appears the staff at web.archive.org don't
care about careful archiving. Their archiver is
ripping the last byte off every data file that gets
archived (like archived downloads). So the ZIP
is "damaged", which is a challenge for the users
of the archive site, to fix.
When you double click on that file, to unzip it,
there may be a claim it is corrupted. I tried
to use my hex editor this morning, and it refused
to extend the file (and I don't know why it is
doing that). I used a copy of PKZIP and PKZIP
repaired the file, and allowed me to unzip it.
So that will be a challenge for you, to get
it to unzip. But the reason it won't unzip, is
there is a byte missing from the end. If your
hex editor is working, just add a byte (00) hex
to the end of the file.
Assuming you get it unzipped, this is what you do.
In Start
rogram:Accessories is a thing called
Command Prompt. It opens a window in which you
can type commands. Mine shows the current
directory as C:\Documents and Settings\Paul
when started.
If you type in there
cd My Documents
that should change the directory to something
like C:\Documents and Settings\Paul\My Documents.
That would correspond to the My Documents folder
on your desktop, as near as I can tell.
Copy the testlimit.exe file from the unzip step,
into "My Documents". That way, you won't have to
learn too much about using the "cd" or change
directory command.
Once the file is in position, at the command prompt type
testlimit -m 16
What that does, is allocate memory in 16MB chunks.
If you have the Task Manager open (control-alt-delete)
and click the Performance tab, just before executing
that command, you can watch that single task
(testlimit) eating your system memory.
My computer only has 2GB of memory. When the testlimit
program stops allocating memory (because it cannot get
any more), it reports "2000 MB" on my machine. That may
be related to the 2GB/2GB split for the address space
on my machine. You may observe a similar limit, unless
the system has been booted to be large address aware.
In which case, a different limit might be seen.
I think Photoshop users see similar issues, with
a limitation on memory usage. A program like
Photoshop has a control, which affects what
percentage of available memory will be used.
Photoshop has its own notions of memory management,
and perhaps (just a guess), you might see up to about
1.8GB of memory used. But this may not represent
the system limits as such, and what you're seeing
is Adobe's opinion of what a safe amount of memory
is, that can be allocated without upsetting the
usage of the computer.
To stop the testlimit program, you can type <control> c.
With the mouse clicked on the window, holding down
control and typing "c", is a signal to the program
to stop. I had to do it a couple times, before the
program would exit. You can also try just closing the
Command window as well.
When the program is stopped, Task Manager should show
a much smaller total memory usage. That is because
when testlimit stopped execution, it gave up the
memory it laid claim to.
The purpose of this experiment, is to show you how
a Windows program can get pretty close to 2GB, without
the user working up a sweat. Running two large programs
could use closer to 4GB of memory, and so on. So
at some point, the extra memory helps you run
multiple big programs. I don't recommend messing
with the machine further, unless you're prepared to
repair the consequences. (Setting the machine to be
large address aware, is OK if you're a rocket scientist
who can put everything back if there are problems.)
HTH,
Paul