NTCacheSetter

Under Windows NT, Windows 2000 and XP the file Cache can theoretically take nearly all the physical RAM. The upper limits are 512 MB under NT4 and 960 MB under 2000/XP. Often it seems that the memory of applications is swapped out in favor a large file cache. If you need the application again you see and hear how it is digged up from the pagefile... Under Windows 9x you where able to limit the size of the file cache thru an entry in the SYSTEM.INI. But there is no Similar way under NT, 2000 and XP. It becomes really worse when a Windows optimizing tool has set `LargeSystemCache` to 1. This means something like "If Window needs memory, take it from anywhere but not from the file cache". The only way to get a bit control over the file cache is to trim its `Working Set`. The Working Set is the memory that has been recently used so Windows expects that it is used again in the near future.Trimming the Working Set doesn`t mean that the memory is taken away from its owner. It only means that the Windows memory management thinks that it`s not important to hold it in physical RAM. Trimming the Working Set of a program is also made by Windows whenever you minimize the program. You can observe it in the TaskManager.