IOW, if I write an editor and handle file types such as .txt .doc .srt whatever, instead of just putting "%1" as param, if I put a bogus pararm that is different for each file type, chances are I could end up with multiple entries in the prefetch. People would marvel how fast my editor loads compared to SuperEditWhatever brand. One more way to give the home team an edge.
You risk pushing other people out of the limited amount of prefix cache entries, yes (unless multiple /prefetch:n
shortcuts for one app are counted as single entries, I don't know) - but I really do think this was implemented because it was believed to be a genuinely good idea, not for nefarious purposes.
That was XP, anyway Vista/Win7 SuperFetch has had a lot of changes (and works much better), so I dunno how relevant it is today
PS: reason I asked if SpeedyFox (and friends, for that matter) do anything but sqlite VACUUM was that it could make sense to defrag the files as well - after VACUUM handling crud and internal fragmentation, the sqlite databases can have a fair amount of filesystem fragmentation as well.