Printable View
Hey everyone, i have one small question that i think i might have already answered myself, but i'm not sure, my problem lies with the fact i have set NO pagefile and restarted my PC, then when i look in task manager it shows a pagefile :ehh:
Screenie here :
http://img285.echo.cx/img285/6818/explainthis2rv.png
How about when you click the change button do you have "system managed size" selected?
Also did you reboot after setting the 0 size?
I have "No Page File" selected, risky choice i suppose, but my computer is at least twice as fast at doing things this way, and with 768mb RAM it seems like a good thing to do.Quote:
Originally Posted by RobDog888
I did reboot after setting 0, as it told me to do so :)
I dont think its that risky since windows doesnt really crash like it used to in older versions. If it did crash you wouldnt be able to
get a memory dump but I guess thats ok.
What if you changed it from none to a zero min and max custom size?
The minimum is 2Mb, yet you can set No Pagefile, so i selected that option.Quote:
Originally Posted by RobDog888
Is it possible its showing the RAM as a pagefile instead f the actual pagefile ? It would make sense at the bar seems to go upto 768 (ish)
Maybe but it doesnt make sense that you can select no pagefile and yet have a restriction of 2Mb when setting a custom size.
Go to startup and recovery, and choose "automaticaly restart" then choos "none" for the write debug information combo. Then restart your machine and see what happens.
'
ØØ
So by not having a pagefile what happens when you run out of physical memory?
I believe at that point, the computer will crash...If my memory serves me correctlyQuote:
Originally Posted by RobDog888
I guess you get a "out of memory" exception. Then I guess it is up to the app on what to do. If it is written to deal with that, then nothing will happen. But if it isn't made to deal with it, something I guess most apps are, then I guess your OS will restart.
Hack number two.
Go to your registry, and find this location:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\Memory Management]
then find the key: DisablePagingExecutive.
Then set it to 1. This disables pageable code (Drivers, executables, etc.) from being sent to the Pagefile, rather being kept in RAM instead.
BTW, how can you find out how much L2 Cache you have? Is it possible at all to find out? Here is a tweak from this site:
http://www.techspot.com/tweaks/memor.../xpmem-3.shtml
Quote:
SecondLevelDataCache. For those of you with older CPUs (Pre-Pentium 2 basically), this DWORD Value specifies the amount of L2 (Secondary) Cache on your CPU. Normally this amount will be determined via the HAL, although with older CPUs with off-die L2 Cache this may not be the case. Those with semi-modern CPUs (Pentium 2 or newer) should leave this set to 0 (As should those with Multiple CPUs). If you have greater than, or less than 256KB of L2 Cache on your (old) CPU then Right click on this entry & select Modify. Select the Decimal button & enter in the amount of L2 Cache available, e.g. If you have 512KB L2 Cache then enter in 512. Thanks Ojatex. Where Windows XP in unable to determine the L2 Cache available & this is set to 0 it will default to assuming 256KB L2 Cache is available.
i'm tempted to try generating an out of memory exception but i'm afraid i may not be able to pull out of it even by restarting....ooooo the temptation!!!
It isn't hard..:)...in C++ you can catch the exception even if you are just signing a normal datatype as an integer..:)..but I guess no one is doing that these days. Thats why I guess you will have an automatic restart..:)
Come on Andy, try it and crash your system. :p
You can also get the L2 cache by using WMI. ;)
Guid me...:)
I wanna, i wanna!!! i'm at work though so i can't :(Quote:
Originally Posted by RobDog888