Orpheas said:
Sorry for being such a weirdo, but could you please explain a little what
this 'prefetch' folder is all about? What does it have to do with my problem?
I'm a little afraid to erase all this... Considering all the 'nay sayers' and
stuff... Anyway, thanks!
Prefetch has nothing to do with your problem and does not exist in
Vista, having been replaced by Superfetch. In fact, deleting Prefetch
contents in XP will usually slow the machine until the contents are
rebuilt again. In any case, Prefetch doesn't have anything to do with
slow booting. Here is the official Microsoft explanation of Prefetch (XP):
"The files in the Prefetch folder are data files related to enhancing
the speed at which applications start. Windows XP Professional monitors
the files that are used when the computer starts and when you start
applications. By monitoring these files, Windows XP Professional can
prefetch them. Prefetching data is the process whereby data that is
expected to be requested is read ahead into the cache. Prefetching boot
files and applications decreases the time needed to start Windows XP
Professional and start applications."
Here's a good article about Prefetch and Superfetch:
http://articles.techrepublic.com.com/5100-10877_11-6039379.html?tag=nl.e132
Relevant quote:
"As the next version of Windows XP's Prefetch, SuperFetch does
everything that Prefetch does and more.
"To begin with, SuperFetch overcomes one of the big drawbacks in Windows
XP's Prefetch technology. As I've explained, Prefetch improves
efficiency by loading the majority of the files and data needed by an
application or process into memory so that they can be accessed very
quickly when needed. However, because these files and data exist in
memory, they are subject to the laws governing virtual memory. In other
words, when other applications need access to memory, any prefetched
data is moved out to the page file on the hard disk. When it is needed
again, it then must be moved back from the page file to memory, which of
course offsets the performance enhancement.
"SuperFetch goes one step further to ensure that you get the most out of
the performance enhancement. In addition to constructing the map files I
described earlier, SuperFetch also constructs profiles of the
applications you use that include information about how often and when
you use them. SuperFetch then will keep track of the applications in
your profile and note when any prefetched data is moved out to the page
file. SuperFetch will then monitor the progress of the application that
caused the prefetched data to be moved out to the page file and, as soon
as that application is done, it will pull the prefetched data back into
memory. So when you go to access the application, the prefetched data
will again be available in memory and the application will be very
responsive."
And here's a shorter quote from a Microsoft site about Superfetch:
http://www.microsoft.com/windows/products/windowsvista/features/details/superfetch.mspx
"Windows SuperFetch enables programs and files to load much faster than
they would on Windows XP–based PCs.
"When you're not actively using your computer, background
tasks—including automatic backup programs and antivirus scans—run when
they will least disturb you. These background tasks can take up system
memory space that your programs had been using. On Windows XP–based PCs,
this can slow progress to a crawl when you attempt to resume work.
"SuperFetch monitors which applications you use the most and preloads
these into your system memory so they'll be ready when you need them.
Windows Vista also runs background programs, like disk defragmenting and
Windows Defender, at low priority so that they can do their job but your
work always comes first."
So your slow booting problem has nothing to do with Superfetch. The slow
booting can be caused by lots of things such as faulty drivers, the
machine looking for network resources that may not exist (and therefore
timing out), large programs such as antivirus/security software running,
other programs loading into memory, etc. Hence the suggestion to manage
your startup programs and do a clean boot (basically starting Windows
without all of that other stuff loading into memory) in order to
discover the culprit.
HTH,
Malke