Disabling is not a good thing. Virtual Memory disabled Error _WINDOWSXP

Recently we have often talked about the topic is the DDR memory of the big price reduction, DDR266 from the position of more than 400 yuan plunged to about 200 yuan, many people have used 512MB or even 1GB of memory, so there is a view of some players in the popular, that is to disable virtual memory, Prohibit Windows paging file Exchange, forced command data processing in memory, can speed up data read and write efficiency, is it really so?

　　 set up according to application requirements

The author thinks, this kind of argument wants to divide the situation to treat, can't say to ban casually is good.

First, find out what a "Big Memory" configuration is. The original design of Windows using virtual memory itself is because physical memory is very expensive, generally do not exceed 128MB capacity, need hard disk space for temporary buffering-that is, you should be the application of how much physical memory and their actual memory to make a comparison, if the actual memory is less than the peak application, You'll get into trouble.

In general, if you want to do large graphics, 3D animation rendering, such as the volume of data is very big task, should not disable virtual memory, if you often want to print documents with a large number of pictures, the ban on virtual memory can also cause errors in the program. Because like Word software before printing to generate buffer files, and then transferred to the printer, the picture size larger, higher resolution, the need for the buffer capacity is also very large, the author of the previous help to create a design map, the writer has encountered printing a picture of the production will be nearly 300MB temporary files. Because Windows and the application itself also requires a certain amount of memory to run, if you are 512MB configuration, disable the virtual memory, it is very likely to report the virtual memory is not enough, forced out of print paper and ink waste.

Therefore, you must apply the environment to your task to decide whether to disable virtual memory. Even if the virtual memory size fixed set, you must be cautious, otherwise in the running of large application software only when the virtual memory is not enough, the whole system will be because the CPU occupancy rate is very high and become very slow, at this time again change is not so convenient.

　　 consider the factors of the operating system

Under different operating systems, virtual memory settings or disabled are different, can not be generalized.

Because of architectural problems, Windows 9x/me has a congenital shortage of memory larger than 256MB, which is larger than this amount of memory, and Windows 98 is unstable and starts to slow down. If you use large memory plus disabling virtual memory, the factors that are unstable will increase further. Windows 2000/XP can effectively manage up to 1GB of memory, more than this number will be unstable, and depending on the motherboard BIOS model and chipset performance.

In addition, the design of Windows itself is that once a process is found to be inactive, the memory space allocated to it is mapped to the swap file, as far as possible to empty out the physical memory to other active threads, rather than using the physical memory to start using the swap file. Because if you wait until the physical memory is exhausted, it's too late, and it's bound to cause data transfer and processing stagnation on a lower-configured machine. Therefore, the prohibition of virtual memory in principle, the most likely to cause Windows exceptions, even if not run out of trouble, will frequently hint that virtual memory is not enough, please reset so, let you annoying.

　　 How to disable virtual memory

For a friend with a lot of memory, if you really want to disable virtual memory to speed up the speed, in fact, can be a compromise to "cheat" windows, is a part of the physical memory to virtual into a physical hard disk:

　　 1.Windows 98

Can add a sentence in Config.sys: Device=c:\windows\ramdrive. SYS 23000/e (please set appropriately according to your own partition of Windows) This is the use of memory by Ramdrive.sys virtual out of a partition, where 23000 is how much you want to use physical memory, the unit is KB, if you have 1GB, you can set this number to 300000 to 500000, that is, 300~500MB, and then set the virtual memory to the virtual partition, the program Runs completely in the physical memory.

　　 2.Windows 2000/xp

You must rely on Third-party tool software to virtual physical hard disks, and then set the Pagefile.sys paging file on the virtual disk to achieve the same effect, or add a sentence to the bottom of the "[386enh]" in System.ini, conservativeswapfileusage=1, let windows give priority to physical memory, and try not to force the virtual memory interchange file directly.

　 Conclusions

The author believes that disabling virtual memory to achieve the accelerated effect is very limited, plus the general Windows default settings are more appropriate, especially the Windows 2000/xp default settings for virtual memory management is good, try not to change, or out of the problem you are difficult to judge and analyze.

　　 Some fault analysis about memory

Sometimes, Windows has some memory-related fault tips that are not necessarily related to memory, and some seemingly unrelated memory failures are really memory-generated and very covert.

For example: You use a tool such as PQ Division master to turn the size of the partition cluster, when the cluster is less than the default, Windows 98 runs a disk scan that may report low memory and is normal under Windows 2000 and Windows XP-that is, it does not matter with memory at all.

Another example: Sometimes the boot into Windows, the system will prompt you registry error, whether recovery, when you choose to restore, restart again, or the same hint, this fault, but most of the memory or heat dissipation problems caused by the need to replace the memory or fan.

Therefore, Windows prompts sometimes mislead the user, if the same failure repeated, the prompt can not be resolved, should consider the possibility of Windows false positives