NO ng's: Memory, Optimization or Ram?

  • Thread starter Thread starter Johann Backer
  • Start date Start date
J

Johann Backer

At least not with the SBC Prodigy News Servers. :mad:

FreeRAM XP Pro 1.40 indicates that "Virtual Memory is disabled on this
system."

A 2,048 (Min/Max a/k/a 'permanently set') (2GB) swapfile is set on Drive
D: - at the BEGINNING.

According to Windows Task Manager/Performance: Commit Charge 298M / 2452M

I have re-set Virtual Memory both Up and Down; re-booting each time -
according to FreeRAM XP Pro: it is still disabeled on this system? :hmm:

A resolution/work-around please.

Thanks.
 
Resolution:
Uninstall "FreeRAM" and let Windows XP manage memory.
Click to expand...

It does. It simply does not "return memory" that it does NOT need. I would
prefer to use RAM, which is faster than the "swapfile".

Installed RAM: 512MB (Shared - 32MB Video) - Available RAM: 480MB.
 
Rick said:
Agreed.
Click to expand...

Agreed— to which:

1.( Resolution:
Uninstall "FreeRAM" and let Windows XP manage memory.

OR

2.( It does. It simply does not "return memory" that it does NOT need. I
would
prefer to use RAM, which is faster than the "swapfile".
 
My statement pertained to #1. But to digress a bit.....

There is no need to use any third-party memory manager- period. Windows does
just fine without this kind of "help". In actuality, all those programs do
is force Windows to strip the memory cache to "free up" the physical ram -
something that is entirely unnecessary and is contrary to the design of
memory management in WinXP. The simple fact is, these programs actually do
more damage than good as they fight the system for control of the physical
memory causing conflicts and necessitating a reload of stripped cached data
and programs. Those sorts of utilities might be useful if you are running
Win95 or earlier, or if you have a program that was not written properly and
is causing a "memory leak", but that's about it. In the latter case, this is
a fault of the designer for not following the memory model, and should be
resolved by the vendor.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
Rick said:
My statement pertained to #1. But to digress a bit.....

There is no need to use any third-party memory manager- period.
Windows does just fine without this kind of "help". In actuality, all
those programs do is force Windows to strip the memory cache to "free
up" the physical ram - something that is entirely unnecessary and is
contrary to the design of memory management in WinXP. The simple fact
is, these programs actually do more damage than good as they fight
the system for control of the physical memory causing conflicts and
necessitating a reload of stripped cached data and programs. Those
sorts of utilities might be useful if you are running Win95 or
earlier, or if you have a program that was not written properly and
is causing a "memory leak", but that's about it. In the latter case,
this is a fault of the designer for not following the memory model,
and should be resolved by the vendor.
Click to expand...

Thanks for the clarification.
 
Back
Top