|
|
#22 |
|
Techorator
Winamp & Shoutcast Team Join Date: Jun 2000
Posts: 35,894
|
Basically, it's a Windows bug where all your available physical RAM gets used up (All RAM is used for DiskCache), including the virtual memory created by the swap file (win386.swp), and Windows doesn't free-up/release it properly even after the programs that were using it have been shut down.
Usually, the only way to free up your memory is to reboot. However, there are plenty of memory management software programs out there, and many of them are freeware. MemoryElevator & RAMBooster & MaxMem spring to mind. I've just searched http://www.pc911.com for a few helpful articles, so check out these links for more info: Re: CacheMan (freeware) http://www.pcnineoneone.com/downloads/system.html Resource Leaks vs Memory Leaks: http://www.pcnineoneone.com/howto/resources1.html Troubleshooting Memory Leaks: http://www.pcnineoneone.com/howto/ts1.html However, all I could find @ M$ Support was this: http://support.microsoft.com/support.../q242/1/61.asp http://support.microsoft.com/support.../Q128/3/27.ASP One very useful tip I can give you is to manually edit your system.ini file as follows [vCache] MaxFileCache=xxxxx xxxxx should be equal to exactly ¼ of your physical RAM. eg. if you have 96MB RAM, a ¼ of 96 = 24 To turn 24MB into the required figure in KiloBytes, multiply by 1024. Therefore, 96 divided by 4 = 24 x 1024 = 24576 MaxFileCache=24576 system.ini is found in the Windows dir and can be edited in Notepad. Do not change anything else in this file, but only what I've outlined above. The [vCache] line should already exist, so just type in the MaxFileCache value underneath it. Save the file, and reboot. |
|
|
|
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|