Resolving A Common Windows Memory Error
There are times when you have to access your computer’s command prompt mode out of necessity, and when you cannot continue with your computing unless you run a command in this mode. A common example of this kind situation is where you need to ‘Ping’ your internet connection to see if and how well it is working. Unfortunately sometimes when you attempt to run the computer’s command prompt, windows might give an error, with an explanation that the system does not have enough memory to run the program in question, and that you need to close one or more programs you are currently running before you can access your computer’s command prompt. Now this can be a baffling windows memory error, given that it occurs even in computers with massive amounts of Random Access Memory (RAM) Installed.
The windows memory error where the computer is unable to run the command prompt is mainly caused by the cache system consuming all memory addresses (these are usually reserved when the system is initialized) so that there are no virtual memory addresses left for operations like accessing the system’s command prompt – which in computing terms, actually constitutes opening another ‘virtual machine’ as Windows ‘sees’ it.
This problem tends to occur in the earlier versions of windows – most notably Windows 95 (for which support has since ceased), Windows 98 and Windows Millennium edition or ME as it is commonly known.
Paradoxically, one of the ways to resolve this Windows memory error – where the computer is unable to run the command prompt, is by reducing the amount of memory installed on the computer to 512 Megabytes, or less – given that the versions of Windows that tend to experience this Windows Memory error were meant to work with that level of RAM.
Rather than reduce the amount of memory manually though, you can also reduce the amount of memory that the systems virtual cache uses to less than the 512 MB we mentioned in the first approach. This can be done by accessing the system’s MaxFileCache setting (which can be found in the computer’s system.ini file), and this way, the maximum amount of virtual cache memory that the computer can reserve for other operations is reduced to 512 MB, leaving you with enough memory addresses that can be allocated to operations like running the command prompt, which as mentioned, constitutes another virtual machine in Window’s way of seeing things.
Alternatively, if you don’t want to change the MaxFileCache setting and don’t want to manually reduce the amount of memory in the system, you can leave the MaxFileCache setting as it was, and not limit the amount of memory in the system either, but rather through the use of the utility you use to configure the system limit its memory usage to 512 MB or less. This too, should in turn limit the amount of memory that the system allocates to Virtual cache, so that you are left with enough memory to undertake operations like running the computer’s command prompt.
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.
