There is such a widely circulated Windows XP optimization technique: reducing the number of laps in the Windows XP progress bar and increasing the system startup speed. This can be achieved by changing the key value of EnablePrefetcher to "1" under the "HKEY_LOCAL_MacHINESYSTEMCurrentControlSetControlSessionManagerMemory
ManagementPrefetchParameters" branch in the registry. This can reduce the number of pre-read files and reduce the wait time of the progress bar. The effect is that the progress bar runs into the login screen after one lap.
Hands-on practice:
The author follows this technique to practice, set the value of EnablePrefetcher to 0, 1, 2, 3, respectively, and measure the settings from the POST screen to the computer The time when the welcome screen appears. The result of multiple statistics is that the time difference in these four cases is almost negligible. In this startup process, although the number of scrolling of the scroll bar is significantly lower than before the unmodified, the black screen time between the appearance of the screen and the welcome screen is increased a lot, so the total time measured is almost equal. At this point, the author has to question the optimization method. In fact, there are two questions worthy of questioning.
point a question: to reduce the number of files that can be pre-read shorten system boot time?
registry key EnablePrefetcher this key can be set to the following values. Meaning respectively:
"0" - un-read function;
"1" - the system will only pre-read applications;
"2 "- The system will only pre-read Windows system files;
"3" - the system will pre-read Windows system files and applications (Windows XP defaults).
test results have shown that the modified value after system startup time and is not significantly reduced. This means that reducing the number of prefetched files is not a major factor in optimizing system startup time.
question point two: the progress bar to reduce the number of turns means that the system start-up times? After
modify the registry, we only see a progress bar of waiting time (ie, number of turns rolling) reduction, but practice shows that this is only the illusion of surface. Then why is the system startup time still not significantly reduced? This requires an understanding of the system startup process.
system startup optimization focus: start-up time the computer starts to see the whole process
want to speed up the system, the most important is to start the process of optimizing your computer. Let's first take a look at what happens when the computer starts up.
After the computer is powered on, the first step is to perform a power-on self-test, which is POST (Power On Self Test), check RAM, drive, etc.; the second step BiOS will read the active partition master boot record The boot loader of the third step starts the loader initialization and the operating system starts officially. This process is mainly divided into four stages: the boot phase, the load kernel phase, the initialization kernel phase, and the login system startup. The initialization of the kernel phase is a very complicated process. The system needs to load many drivers of the underlying hardware, read the registration information, find new hardware devices, start related services, initialize the display device and display the user interface. And implement various user-defined configurations, such as security configuration.
Looking back at the technique mentioned earlier, changing from the default value to pre-reading only does reduce the number of pre-read files. However, Windows XP startup is still a very complicated process. Simply modifying the number of pre-read files does not effectively achieve the purpose of optimizing system startup.
With the increase of system and program files, system startup slowdowns is quite normal. To significantly optimize the system startup process, you mainly need to adjust the hardware startup options, reduce the system to detect hardware time, regularly defragment the disk, reduce unnecessary self-starting programs in the system, and so on.