ROOKIE HERE, but have the same virtual memory problem.

What is "cashemen" and how do I dump it to help my virtual memory problem.

Also, I installed an additional hard drive (blindly, but effectively). How
can I utilize this extra drive to improve my performance?

Any help would be GREATLY appreciated.

"Walter Clayton" wrote:

> Do yourself an extremely large favor.
>
> Dump cacheman.
>
> It had a modicum of merit on Windows 95 *only* and is useless on all other
> platforms.
>
> Change your pagefile settings to system managed, but only after you dump
> cacheman.
>
> Of course if you keep cacheman, then good luck. You'll need it.
>
> --
> Walter Clayton
> Any technology distinguishable from magic is insufficiently advanced.
>
>
> "Bill Woods" <woods_b@emercom.com> wrote in message
> news:961AEA752A4BF51D7E@130.133.1.4...
> > XP sometimes has to extend my Virtual Memory. I get a warning
> > message saying:
> >
> > "Virtual Memory Minimum Too Low. Your system is low
> > on virtual memory. Windows is increasing the size of
> > your virtual memory paging file. During this process,
> > memory requests for some applications may be denied."
> >
> > I have got 768 MB physical memory and the paging file is set to have
> > an Initial Size of 380 MB and Maximum Size of 750 MB.
> >
> > IMMEDIATELY after the last virtual memory message I took some
> > readings (see below). I can't see why the virtual memory needed to
> > be increased. Can someone explain what made XP need more virtual
> > memory?
> >
> > Thanks.
> > Bill
> >
> >
> > ============== START DATA ==============
> >
> > Using an application called Cacheman, I saw these two sets of
> > data about 60 seconds apart:
> >
> > Physical memory = 768 MB, usage = 388 MB (approx 51%)
> > Paging file = 750 MB, usage = 145 MB (38%)
> >
> > Physical memory = 768 MB, usage = 380 MB (approx 49%)
> > Paging file = 750 MB, usage = 151 MB (20%)
> >
> > ---
> >
> > XP's task manager showed the following:
> >
> > TOTALS
> > handles 7676
> > threads 436
> > processes 45
> >
> > COMMIT CHARGE (K)
> > total 422,076
> > limit 1,132,876
> > peak 1,506,596
> >
> > PHYSICAL MEMORY (K)
> > total 785,904
> > available 384,156
> > system cache 158,648
> >
> > KERNEL MEMORY (K)
> > total 58,864
> > paged 50,460
> > nonpaged 8,404
> >
> > ============== END DATA ==============
>
>

"Wadsworth Paul" <Wadsworth Paul@discussions.microsoft.com> wrote in message
news:25A71D62-2050-4818-BBAA-A60E7BE99B23@microsoft.com...
> ROOKIE HERE, but have the same virtual memory problem.
>
> What is "cashemen" and how do I dump it to help my virtual memory problem.
>
> Also, I installed an additional hard drive (blindly, but effectively). How
> can I utilize this extra drive to improve my performance?
>
> Any help would be GREATLY appreciated.
>
Add another pagefile on the extra drive.
Jim

Wadsworth Paul wrote:

> ROOKIE HERE, but have the same virtual memory problem.
>
> What is "cashemen" and how do I dump it to help my virtual memory problem.
>
> Also, I installed an additional hard drive (blindly, but effectively). How
> can I utilize this extra drive to improve my performance?
>
> Any help would be GREATLY appreciated.

Take a look at this:
http://aumha.org/win5/a/xpvm.htm

--
Rock
MS MVP Windows - Shell/User