C
Curt
I'm running Win XP on 3 PC's on a firewalled home
network. Around Dec 8, one PC popped
up the "virtual memory too low.." system message. Within
a day, my main PC showed the same message. I'd never seen
that before in almost 2 years of use.
PC 1 uses the default, windows managed swap file, PC2 has
512MB ram and was set for a max size of 1300mb. I ran a
swap file size monitor on PC2 and the most it used
was about 200mb. The error pops up with the amount used
is only 20mb.
There doesn't appear to be any correlation with the
timing of the error and the current or peak virtual
memory usage reported by the XP computer management,
performance snap-in. It reports a problem that doesn't
exist.
It doesn't matter if the swap file is managed by XP, set
to 250% of RAM size, set to 1GB minus ram size or set to
1.8GB permanent size, the error still pops up.
Nothing in common has been loaded on the two systems
except for windows and Norton updates.
I saw on Symantec's site that their updater "can" cause
that condition but their fix didn't make any difference.
I've ran virus and trojan scans and nothing was found.
I was suprised that I didn't find a single mention of
this specific problem anywhere on the internet.
Based on the circumstances, I expected to find loads of
posts and articles about a bug in either a win XP or
Norton updated file, or a new virus or something.
Has anyone else experienced this?
network. Around Dec 8, one PC popped
up the "virtual memory too low.." system message. Within
a day, my main PC showed the same message. I'd never seen
that before in almost 2 years of use.
PC 1 uses the default, windows managed swap file, PC2 has
512MB ram and was set for a max size of 1300mb. I ran a
swap file size monitor on PC2 and the most it used
was about 200mb. The error pops up with the amount used
is only 20mb.
There doesn't appear to be any correlation with the
timing of the error and the current or peak virtual
memory usage reported by the XP computer management,
performance snap-in. It reports a problem that doesn't
exist.
It doesn't matter if the swap file is managed by XP, set
to 250% of RAM size, set to 1GB minus ram size or set to
1.8GB permanent size, the error still pops up.
Nothing in common has been loaded on the two systems
except for windows and Norton updates.
I saw on Symantec's site that their updater "can" cause
that condition but their fix didn't make any difference.
I've ran virus and trojan scans and nothing was found.
I was suprised that I didn't find a single mention of
this specific problem anywhere on the internet.
Based on the circumstances, I expected to find loads of
posts and articles about a bug in either a win XP or
Norton updated file, or a new virus or something.
Has anyone else experienced this?