The second option is to load the system into memory. The installation of this scheme is quite complicated, but the system performance is greatly improved, the system loading speed is greatly improved, and the program loading speed is also very fast. However, at present, this scheme has great limitations. The whole system disk must be less than 2GB, otherwise the loading process will fail, that is to say, either the extremely simplified version of Windows 7 system or ordinary Windows XP system can be installed, but large application software can not be installed in the system disk, and only commonly used non-large application software can be installed.
In the previous analysis, we talked about that it is very complicated to install Windows 7 into memory successfully, and it is required that the space occupied by the files of the whole system disk should not exceed 2GB. Ordinary Windows 7 will take up about 10GB of space after installation. If you count the page file of virtual memory and the image file of system hibernation, the system with 16GB memory will occupy about 30GB of space, and it is impossible to mirror successfully. And the common method of slimming in Windows 7 is not very effective. After slimming, Windows 7 still occupies about 7GB of space, so we can only install an extremely streamlined Windows 7 system.
Because the Windows 7 Extreme Compact Edition downloaded by the engineer is automatically decompressed and installed, and the Windows 7 Extreme Compact Edition cannot be used because there is no system boot program, it is necessary to install the Windows 7 Extreme Compact Edition in two steps.
The first step is to install the standard Windows 7 system on the hard disk in the normal way. This step is very simple, so I won't say much.
Then enter the more complicated second step. After the system is installed, you don't need to install any drivers, just restart it directly, and use the WinPE tool tray to boot into the WinPE system. Enter the disk management interface from WinPE's computer management window. At this point, you can see the 100MB partition reserved by disk "c:" for the system. This partition stores the system boot program of Windows 7, which will not be displayed in Windows 7 system, but will be displayed in WinPE. Right-click disk "C:" and select "Change drive letter and path", then change its drive letter to "B" in the new window that pops up, and then change its drive letter to "C" in the same way for the partition where the system has just been installed (normally it should be disk "D:" now). In this way, the disk "C:" is the partition where we just installed the system, and then right-click the disk "C:" with the system and select "Format". After the formatting is completed, we run the installation program of Extreme Lite Windows 7. The installation program will automatically decompress the file to the disk "C:", restart the computer after the decompression is completed, and the installation of Extreme Lite Windows 7 will begin. After installation, we found that the actual space occupied by disk C is about 1.26GB, so we can install the driver normally or turn on Aero.
After the system installation is completed, install the drivers of all devices, and then install the FiraDisk driver of the memory virtual hard disk. First, enter the device manager, right-click the top column of the hardware device list, select "Add obsolete hardware (see the above figure)", then click "Manually select hardware from the list", locate the FiraDisk.inf file in the FIRADisk folder, and install the disk controller named "FIRADisk Virtual Disk Enumerator" into the system.
Then you need to modify the system startup information, otherwise bootmgr will find that the disk size has changed, resulting in a Winload.exe error at startup, and the system cannot be successfully started directly from memory. The modification method is simple: as an administrator, run the command prompt program in Start → All Programs → Attachments, and input bcdedit/set {default} OS device boot, bcdedit/set {default} device boot and bcdedit /set {default} detection Hal 1 respectively. At this point, the modification of the system startup information is completed, and then we will add the startup options menu.
First, extract Grub4dos to drive C and rename the folder Grub. Then copy grldr and grldr.mbr in the grub folder to the root directory of drive C, and then enter "bcdedit/create/d \" GRUB \ "/application boot sector" in the "command prompt" interface and press enter. At this point, the system will return a long string of characters. What we return here is "{4bc205f9-d2d6-1E0-a1B9-916d6c33702}", and then we continue to enter three commands in the "command prompt" interface:
Bcdedit/set {4bc205f9-d2d6-11E0-a1B9-9116d6c33702} Device partition =c:
bcdedit/set { 4 BC 205 f 9-d2d 6- 1 1 E0-a 1 B9-9 1 16d6c 33702 } path \ \ gr ldr . MBR
bcdedit/display order { 4b c205 F9-d2d 6- 1 1 E0-a 1 B9-9 1 16d6c 33702 }/add last
(The characters returned by different systems are different, and the characters in "{}" in the following commands should also be changed to correspond). Press Enter every time you enter a command, and the system will prompt the program to finish execution.
At this point, we can say that all the changes in Windows 7 system have been completed, and then we restart to WinPE system. Run VDM, create a 2GB image named "Ramwin7.img" on the system disk of Windows 7 extreme compact version (displayed as D disk in WinPE system), and then load this 2GB image into the system. At this point, a 2GB disk "A:" will appear in the system. Click the disk A: and select the formatted disk A:. Then copy all files and folders on the D drive except System Volume Information, Recycler and Ramwin7.img to the A: drive, and the mirroring is completed.
The next step is to modify the secondary startup menu. Open the "menu.lst" file under the "grub" folder on disk D with wordpad, and finally write down the following six lines of code:
Title Ramwin7
find ——set-root /Ramwin7.img
map ——mem /Ramwin7.img (hd0)
Map (hd0) (hd 1)
Maps-hooks
Chain loader (hd0,0)/bootmgr
All the work is done here. Restart the computer, select "grub" in the startup selection menu, wait for more than 20 seconds, and automatically enter the memory version of Windows 7. Because the extreme compact version of Windows 7 we use is a 32-bit version, at this time, the memory version of Windows 7 occupies 2GB, leaving 1.46GB of available memory. At this time, the running speed of Windows 7 system is really fast, but the extreme simplification has also brought many problems: due to being too simple, the system can only run a few applications such as Office and IE, and PCMark7, Sisoftware Sandra 2011can't run normally, and various games including Paradise 2.5 can't load normally.
2. Install Windows XP in memory.
Because many software can't be used normally after installing Extreme Lite Windows 7 in memory, we installed Windows XP system in memory instead. Compared with installing Windows 7 in memory, installing the memory version of Windows XP is much simpler. After installing the system, drivers and application software, you can delete some unused components to simplify the system. Then right-click the FiraDisk.inf file under the firadisk folder and select "Install". The system will automatically restart and start to install the driver of FiraDisk Virtual Disk Enumerator. You can install the Fira Disk Virtual Disk Enumerator disk controller by manually navigating to the FiraDisk folder.
Next, you need to manually change the drive letter of the system disk, otherwise you will not be able to boot to the memory version of Windows XP. Click "Start → Run" and click [HKEY_LOCAL_MACHINE\SYSTEM\
MountedDevices] "Rename" \DosDevices\C: "to" \DosDevices\B: ",so that when we boot to the memory version of Windows XP system, the original C disk will become B disk, and the memory version of Windows XP system disk will be automatically assigned as C disk.
After the modification, restart the computer to enter the WinPE system, run the VDM tool as mentioned above, create a 2GB image named "RamXP.img" in the system disk "C:" of Windows XP, and load this image, and a disk will also appear. Just like making a memory version of Windows 7 image, copy all files and folders in the system disk except system volume information, recycler and RamXP.img to the disk "a:" and the image will be made.
Engineer's tip: It should be noted that the path of the system partition in the boot.ini file must be "multi (0) disk (0) rdisk (0) partition (1) \ Windows".
Just like making the memory version of Windows 7 before, unzip Grub4dos to drive C, rename the folder as Grub, then copy the grldr file in the grub folder to the root directory of drive C, edit the boot.ini file, and enter "c:\\grldr=\"GRUB\" in the last line. Finally, use WordPad to open the "menu.lst" file under the "grub" folder of drive C, and finally write down the following six lines of code:
Title RamXP
find ——set-root /RamXP.img
map ——mem /RamXP.img (hd0)
Map (hd0) (hd 1)
Maps-hooks
Chain loader (hd0,0)/ntldr
After all operations are completed, restart the computer, select "Grub" from the startup menu, and then select RamXP from the Grub menu. It takes about 10 seconds to enter the memory version of Windows XP system. Similarly, due to the poor compatibility of 64-bit Windows XP, we still installed 32-bit Windows XP. At this time, the memory version of Windows XP occupies 2GB, and the system still has 1.46GB of available memory, which significantly improves the system performance and runs like a fly. Because the Windows XP system itself is not large, a considerable number of applications can be installed after installation and moderate streamlining, and these applications can be used normally, and the playability is higher than that of the memory version of Windows 7.
The third scheme is to virtualize part of the memory into the hard disk. In this way, a partition with very fast reading and writing speed will appear in the system. After installing some applications in the virtual hard disk, the speed of starting these applications will be greatly improved, but the performance of the whole system will not be greatly affected. However, the current virtual hard disk software also supports writing the data in the virtual hard disk into the mirror when it is turned off, so that the data will not be lost when it is turned off again. At present, this scheme also has some limitations-the current virtual hard disk software can only create a virtual hard disk with a capacity of less than 4GB.
Many users with large memory have had the idea of virtualizing some memory to hard disk, and virtualizing memory to hard disk is the simplest application scheme of large memory. We use VSuite Ramdisk software to realize the virtualization of large memory hard disk. This kind of software uses a unique algorithm to virtualize the memory into a hard disk, so that the data reading and writing of hard disk files can be transformed into data access to the memory, which greatly improves the speed of data access, and is especially helpful for users who often exchange large-capacity files through the network. Because the memory has the characteristics of power failure and data disappearance, it is best to store temporary files. The new version of VSuite Ramdisk provides mirroring function, which supports automatically saving data to the mirror file when shutting down and automatically loading the data in the mirror file to the virtual hard disk when booting up, thus avoiding the problem of data loss caused by the original memory virtual hard disk software when shutting down. Moreover, VSuite Ramdisk also has the function of detecting and utilizing the unrecognized memory of the system, which can solve the problem that the 32-bit Windows operating system cannot make full use of more than 4GB of memory. We open a virtual hard disk with a maximum of 4GB in a 64-bit Windows 7 system, and then set the system's swap files into the virtual hard disk, and install Paradise 2.5 into the virtual hard disk. In this mode, we can see that for the virtual hard disk, the disk reading and writing performance has been greatly improved, but for the whole system, the performance of the whole system has not been greatly improved except for the obvious speed increase when loading the programs installed on the virtual hard disk.
The fourth scheme is to virtualize the memory into a disk cache, allocate the memory for the hard disk as a cache, and intercept the IO request sent by the system to the hard disk. If the data requested by IO is already in the cache, directly read the data in the cache to complete the IO request; Otherwise, read the data from the hard disk and store it in the cache, and complete the IO request at the same time. It can be seen that the more data read from the cache, the more the system performance will be improved. By avoiding reading the slow hard disk frequently, the system performance will be improved. Since the Windows 98 era, many players are happy to modify the hard disk cache entries in the registry in order to obtain higher hard disk performance. Now many hard disk caches have reached 64MB, but for users who are crazy about performance, 64MB hard disk cache is not enough. When our memory reaches 16GB, we can consider using memory as hard disk cache. We use FancyCac.
He, a software that virtualizes system memory into hard disk cache, is used for testing. FancyCache can store the data read from the hard disk into the system memory, so that the system can quickly read it from the memory the next time it accesses the data, and FancyCache also supports virtualizing other disks into the hard disk as a secondary cache, so we tested two schemes in the test. The first is to simply use 4GB of memory as the cache of the hard disk. The second scheme is to virtualize 4GB of memory into a hard disk, and then use this virtual hard disk as the secondary cache of the main hard disk. It can be seen that in the 64-bit Windows 7 system, the performance improvement brought by the open memory virtual hard disk cache is very huge, and the score of PCMark7 even jumped to more than 565,438+000. We know that Futuremark has stated in the official explanation that their goal is to control the score of the high-end system composed of Core i7-980X six-core processor, GeForce GTX 580 graphics card and Micron Crucial C300 solid-state drive at around 5000. Without the need of SSD, only the systems of Core i7-2600K, GeForce GTX 560Ti and Seagate 7200. 12 1TB HDD have exceeded 5000 points, which shows us the rapid performance improvement brought by the large HDD cache, which is also the result we most hope to get. In the random reading and writing test of HD Tune, we can also see the obvious changes brought by large cache. The random read-write performance of 4KB is only 59 IOPS for the first time, which is not much different from that of ordinary hard disk. However, the advantages of large cache are only revealed after the second test, and its random read-write performance of 4KB reaches 15 1263 ops, which is about twice as high as that of the current solid-state hard disk with the highest performance.
The engineer concluded that the memory version of the system is still immature. Installing the operating system and common software in memory can certainly greatly improve the performance and response speed of the system. However, since the boot program of the memory version system can only support the system image of 2GB at most, it is necessary to simplify the system if the memory version of Windows is to be installed. Windows XP system is fine, it doesn't need to be simplified too much, and it won't affect the use, but the memory system can't hold large software. Windows 7 system needs to be greatly simplified, which leads to the incompatibility of the system and many programs can't run normally. In view of this situation, we think that the current scheme of building a fast memory version system by putting the system into memory is not mature, and we suggest that you do not consider it. When the boot program of the memory version system can support 8GB~ 12GB image in the future, then consider installation.
The memory version of Windows is not too late. Looking at these schemes, we can find that virtualizing memory into hard disk cache is the best way to improve the performance of the whole system, which not only greatly improves the performance of random access data, but also improves the running speed of the whole system to some extent. In fact, for the whole hard disk, the capacity of virtual cache doesn't have to reach 4GB, and 1GB or even several hundred MB can obviously improve the system performance. This scheme is also very suitable for users with 4GB of memory and 32-bit operating system. Because FancyCache can identify the unused memory of the system, it will not affect the memory capacity of the 32-bit system itself, and can also improve the system performance. Of course, if the memory is large enough, we suggest to virtualize a part of the memory into a hard disk that will not lose its contents when it is turned off, and put games, commonly used large-scale software and temporary folders in it, which will also improve the system performance to a certain extent. Software download/download/UPfiles/201108/16g.rar.