D
Dom
Hi,
I'm running into problems with XP embedded (but also seen on all versions of
XP) when disabling virtual memory. It appears that CPU and Memory
performance counters are no longer accessible on the system, via perfos, pdh
or WMI. Perfos.dll has been disabled in the registry:
HKLM\SYSTEM\CurrentControlSet\Services\PerfOS\Performance\Disable
Performance Counters = 1.
These counters worked fine on Win2K and NT4 with VM disabled.
Doing a quick search reveals that other people are seeing the problem too:
http://groups.google.co.uk/groups?q...=off&[email protected]&rnum=1
The general consensus is its a bug in XP that is causing the counters in
perfos to crash, so the service dies and XP disables it
If I enable virtual memory the problem goes away, however this is not a
satisfactory solution for various reasons.
Anyone seen this before, or know if MS is working on a fix for it? I can't
see a mention of it on MSDN.
Thanks,
Dom
I'm running into problems with XP embedded (but also seen on all versions of
XP) when disabling virtual memory. It appears that CPU and Memory
performance counters are no longer accessible on the system, via perfos, pdh
or WMI. Perfos.dll has been disabled in the registry:
HKLM\SYSTEM\CurrentControlSet\Services\PerfOS\Performance\Disable
Performance Counters = 1.
These counters worked fine on Win2K and NT4 with VM disabled.
Doing a quick search reveals that other people are seeing the problem too:
http://groups.google.co.uk/groups?q...=off&[email protected]&rnum=1
The general consensus is its a bug in XP that is causing the counters in
perfos to crash, so the service dies and XP disables it
If I enable virtual memory the problem goes away, however this is not a
satisfactory solution for various reasons.
Anyone seen this before, or know if MS is working on a fix for it? I can't
see a mention of it on MSDN.
Thanks,
Dom