Thanks for all the links about Prefetch
. I'd read some of it before - in fact I contributed to one of them, but other stuff was new.
My suspicion was confirmed that the only
stuff that belongs in prefetch is the layout.ini file and files ending in .pf; thus, I have gotten rid of the .gg, .st, and .rr files. What they were doing in there is anybody's guess, but it sure looked like a bunch of garbage; maybe something got garbled when the power went out suddenly when I was using the computer - who knows. I'd sure like to know what programs they were associated with though.
I also thought I'd see what would happen if I followed these directions since I have been installing and uninstalling quite a bit lately:
# knightcrawler Says:
July 20th, 2005 at 1:35 pm
You can delete it if you made big changes otherwise the layout.ini will have a lot of old data.
1. Delete all the files in the folder
2. Turn on the Task Schedule service to automatic and start it if it isnít already.
3. Open a cmd window and type or paste this:
4. The folder will be rebuilt with the current apps and drivers.
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager \ Memory Management \ PrefetchParameters
dword value = EnablePrefetcher
0 = Disable,
1 = App launch prefetch
2 = Boot Prefetch
3 = Both (recommended)
My recommendation for the prefetcher is based on the amount of RAM that you have:
128MB - Disabled (reg value 0)
256MB - Boot only (reg value 1)
512MB or more - Both (reg value 3)
found on this page: http://www.edbott.com/weblog/archives/000743.html
I also checked to see what the registry value was, and observed that it was at 3. I'm keeping it there even though my RAM is only 256. Considering that I use Adobe photoshop and other large programs, I wouldn't want to be without the prefetch.
I've also been keeping the prefetch folder open to see what pops up in it; that way I'll get a better idea of what programs the files relate to. Thus far, those mysterious files have not reappeared
It will also be interesting to discover whether it will take care of some error messages I've been receiving.
Theory: If windows goes to prefetch to find out what files to open in what order when booting or loading a program and if the prefetch file layout tells it to open x file, but x file is gone this might result in an error message such as "can't find the driver specified."