I got the Virtual Memory on, because of the heavy load of applications, but would like to disable the Kernel Paging. So, how to I do that?Thanks, johan1 person needs an answerI do too

Is this what you are talking about?Here is an MS article that tells you how to do it:http://support.microsoft.com/kb/Q184419Before making any changes to your registry, back it up with this popular free tool:http://www.snapfiles.com/get/erunt.htmlDisabling this feature is generally not a good idea on workstations and home environments where applications and memory requirements might change frequently. XP usually knows what it is doing.If you make the adjustment and are hoping for a performance increase, you may end up with a performance decrease as XP might then be forced to perform otherwise unnatural acts.It is sometimes a good idea in a server environment where applications running are fairly static.Surely you have read the myths and legends about this feature and how to use it appropriately.You can read all about it by performing a Google search for:DisablePagingExecutiveMaybe you will get some benefit from it in your environment.You can certainly make the adjustment and hopefully do some timing measurements to see if things get better or worse and it would be interesting to know what happens.After you conduct some before and after benchmarking performance tests to see what effect it has on your system, get back to us with the results. If you can pinpoint a specific issue you are having and why you think this might help, let us know about that too. I can always use more information.Don't guess what the problem might be - figure it out and fix it. I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!

Hi, I've followed the instructions from the link and it does not work at all. So, in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory ManagementI've set the key DisablePagingExecutive entry to 1, but with no result at all. (Note that the Base value in the key is Hexadecimal, so not Decimal.) In the Taskmanager it is clear that the kernel keeps on being paged out to disk all the time and only a smaller portion of the kernel stays in RAM, even when no applications are running. There is another very peculiar thing though. Alongside the folder ...\CurrentControlSet\... in the registry, there are also the folders ...\ControlSet001\..., ...\ControlSet002\..., ...\ControlSet003\..., and ...\ControlSet004\... Furthermore, the following folders:HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet004\ have the same folder- and data structure asHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ So, DisablePagingExecutive appears FOUR (4) times in the registry and they are all different keys. If I change the value of one of them, DisablePagingExecutive in another branch does NOT change. Note that HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\ has a completely different folder structure and content than 001, 003 and 004. So, why does DisablePagingExecutive =1 not work, and why are there 4 times DisablePagingExecutive?---

I've done some tests with all possible DisablePagingExecutive subkeys =1, and than all =0, and I could not really see any difference in the Taskmanager/perfomance tab. At the bottom the Kernal Memory(K) pane kept on showing 68 MB paged and 24 MB non-paged.I then finally switched off the Virtual Memory and removed the Pagefile.sys file from the root. I've rebooted the computer a few times just to be sure there there was no pagefile on disk.However, the Kernal Memory(K) pane in the Taskmanager/perfomance tab still shows 74 MB paged and 24 MB non-paged, although there is definitely no pagefile on disk. All this makes me wonder what the exact definition is of notions like "Pagefile", "Paging out to disk" and especially how to interpret the info in the Taskmanager?!I did notice, though, that applications run indeed a bit faster, until they crash when the system reaches the 1 GB limit (the RAM size in my case).The whole paging issue of the Kernel remains a bit of mystery in Windows XP, I think.johan---

On 10/18/2010 2:55 PM, Formalhaut wrote:Hi,I've followed the instructions from the link and it does not work at all. So, inHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory ManagementI've set the key DisablePagingExecutive entry to 1, but with no result at all. (Note that the Base value in the key is Hexadecimal, so not Decimal.) In the Taskmanager it is clear that the kernel keeps on being paged out to disk all the time and only a smaller portion of the kernel stays in RAM, even when no applications are running.There is another very peculiar thing though. Alongside the folder ...\CurrentControlSet\... in the registry, there are also the folders ...\ControlSet001\..., ...\ControlSet002\..., ...\ControlSet003\..., and ...\ControlSet004\...Furthermore, the following folders:HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet004\have the same folder- and data structure asHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\So, DisablePagingExecutive appears FOUR (4) times in the registry and they are all different keys. If I change the value of one of them, DisablePagingExecutive in another branch does NOT change.Note that HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\ has a completely different folder structure and content than 001, 003 and 004.So, why does DisablePagingExecutive =1 not work, and why are there 4 times DisablePagingExecutive?The only one that you should concern yourself with is the CurrentControlSet read here:What are Control Sets? What is CurrentControlSet?http://support.microsoft.com/kb/100010and:http://technet.microsoft.com/en-ca/library/cc960234.aspxJohn

On 10/20/2010 6:52 AM, Formalhaut wrote:I've done some tests with all possible DisablePagingExecutive subkeys =1, and than all =0, and I could not really see any difference in the Taskmanager/perfomance tab. At the bottom the Kernal Memory(K) pane kept on showing 68 MB paged and 24 MB non-paged.I then finally switched off the Virtual Memory and removed the Pagefile.sys file from the root. I've rebooted the computer a few times just to be sure there there was no pagefile on disk.However, the Kernal Memory(K) pane in the Taskmanager/perfomance tab still shows 74 MB paged and 24 MB non-paged, although there is definitely no pagefile on disk. All this makes me wonder what the exact definition is of notions like "Pagefile", "Paging out to disk" and especially how to interpret the info in the Taskmanager?!I did notice, though, that applications run indeed a bit faster, until they crash when the system reaches the 1 GB limit (the RAM size in my case).The whole paging issue of the Kernel remains a bit of mystery in Windows XP, I think.Don't bother with these tweaks, there is little to gain from most of them and some are just plain detrimental. Don't try to run without a pagefile, as you have already seen it just causes problems that you don't need.John

On 10/20/2010 6:52 AM, Formalhaut wrote:I've done some tests with all possible DisablePagingExecutive subkeys =1, and than all =0, and I could not really see any difference in the Taskmanager/perfomance tab. At the bottom the Kernal Memory(K) pane kept on showing 68 MB paged and 24 MB non-paged.I then finally switched off the Virtual Memory and removed the Pagefile.sys file from the root. I've rebooted the computer a few times just to be sure there there was no pagefile on disk.However, the Kernal Memory(K) pane in the Taskmanager/perfomance tab still shows 74 MB paged and 24 MB non-paged, although there is definitely no pagefile on disk. All this makes me wonder what the exact definition is of notions like "Pagefile", "Paging out to disk" and especially how to interpret the info in the Taskmanager?!I did notice, though, that applications run indeed a bit faster, until they crash when the system reaches the 1 GB limit (the RAM size in my case).The whole paging issue of the Kernel remains a bit of mystery in Windows XP, I think.Don't bother with these tweaks, there is little to gain from most of them and some are just plain detrimental. Don't try to run without a pagefile, as you have already seen it just causes problems that you don't need.John