Windows XP - Speed up the time to load data/applications

Already at elsewhere Windows-Tweaks already reported on the Prefetcher, which shortens the application startup time.

How does the prefetcher work? A short introduction, the readers?
The system startup of a computer consists of several stages: In the first stage, system files are loaded that activate the basic functions of the computer and make them operational. These include drivers which, for example, activate the File system or the initialization of devices such as the Graphics card and the sound card. Later on, the Windows interface (also known as the desktop), its functions and various Services in the Memory loaded. Services provide various functions of a modern Operating system such as automatic updates, network or Internet.
However, the startup process in Windows XP also consists of the so-called prefetcher, which translates as an early fetcher. It is the component that finds out your digital habits and asks itself: Which application do you start frequently? The prefetcher logs and moves files that are needed to start your frequently executed programs to the working memory at system startup. This works faster than the hard disk, which ultimately only consists of mechanical components.

Windows 2000, the direct XP predecessor, does not have this function. In the first stages of the startup process (initialization of the devices), only about 120 input/output processes per second can be executed simultaneously - such processes consist, for example, of loading, executing and passing on data. It is not possible for Win 2000 to execute further processes and therefore users complain about coffee break-like start processes. XP takes a different approach: When devices are initialized, they load prefetch files and lead to approx. 200 (or more) processes per second. This means that the prefetcher hardly influences the length of the startup process and cleverly exploits the system's waiting times, recording data about the prefetcher and these frequently required data each time an XP computer is started. The Prefetcher recognizes whether its retrieval of data was actually an advantage for the user and optimizes or leaves the setting accordingly.
The prefetcher is controlled via the registry, as you have already seen in this article have experienced. Follow the steps in this article and view the right-hand pane of the PrefetchParameters-key. The value EnablePrefetcher controls the behavior of the prefetcher with 3 different parameters: If you double-click on the value and enter a 1 the preloading of Application data one during 2 only data of the Start procedure (system files, services, etc.) for faster start-up. Both features can be added together by entering a 3 enter. Windows Server 2003 or later server variants are only started with a 2, as administrators do not start regular applications and focus on a faster start process. A 0 is enough to deactivate the prefetcher and send it to the bench.

Note: Windows saves the data in the folder E:\WINDOWS\Prefetch. If your computer habits change frequently, it is advisable to empty this folder approx. every 4 weeks.

Now let's move on to the actual tip: How do I convince the prefetcher to preload an application? The answer is easier than you might think...

1. Right-click on the shortcut of the application that you want to load faster. From the context menu that appears, select Properties.

2. Complete the entry for Goal by the parameters /prefetch:1. Example:

3. Click on OK. From now on, the prefetch is used independently of the setting in the registry for PhotoImpact is used. Unfortunately, this setting is very experimental and does not work with all applications. Therefore, if you receive an error message, we advise you to remove the parameter.

What's the point behind it? I also asked myself this question! If application prefetch is switched off (EnablePrefetcher = 2 in the registry, see above), the switch /prefetch:1 is not operational. When Prefetch is enabled, Windows automatically recognizes frequently used programs and loads them into the PF folder. So why does this switch exist? Unfortunately, there is no official Microsoft documentation on the subject, so I suspect that /prefetch:1 is useful for users who want to load certain applications ALWAYS at startup - the conventional prefetch recognizes in many cases when programs have not been used for a long time and removes them. This allows users to control the prefetch in their favor. This is merely an assumption, which I will fill in with more detailed information at this point.