Do you know if it works on 64 bit versions of Windows? It doesn't mention 64 bit on the product page.
I didn't manage to determine this via some searching.
As far as making info available to FolderCache is concerned, some kind of merging is what I currently have in mind. No point in duplicating paths. Perhaps there is some date / time info (may be the last accessed or modification info for FolderCache.txt?) that can be leveraged for this purpose.
Also you need to make sure FolderCache is not running while you do this since it rewrites the FolderCache.txt on closing.
The situations under which it occurred to me to use this is when FolderCache has not been running, so ordinarily it doesn't seem like it'd be a problem, but thanks for the warning. It'd be good to check for a running FolderCache. For reference, the cases I have considered so far are:
- When you first install FolderCache
- While performing maintenance / debugging of some sort, it's not unusual for me to shut down a lot of utilities -- sometimes I stop certain things and not others and don't always remember to restart everything (though I wrote a little utility that's been helping me to "fill in the missing processes").
- Accidental process killing without noticing
I am happy to report that I have not yet witnessed FolderCache crashing on its own
A few lines of batch should do it depending on what you have to do to format the output of the ShellBagsView.
He he. I will probably avoid batch as I still find it hard to use -- though it's nice that I don't typically need to install anything extra. (I find coming back to batch good from time to time -- it helps in my appreciation of other programming languages.)
By having your lines first in the FolderCache.txt file they won't be discarded because the stack has reached its limit. They will be the last entries pushed on.
Thanks for this explanation.
edit: looking at the output I don't see what the information is. It shows the root of the folder opened for all I can see. A bunch of C: X: F: with no particular folder info.. unless something escapes me.
Interesting -- I typically get full path info, though not always. My current leaning is just to work with full path information, at least to start with. Hmm, a random thought -- if FolderCache could be handed folder info from other programs (e.g. via command line invocation) whether it's running or not, may be that'd open up some interesting possibilities...
edit2: Sifting through registry mish mash, esp. 32 vs 64 bit is not my thing. That's why I do the active window in the first place. If you can some up with something yourself I'd be curious to see it though.
If ShellBagsView isn't managing to extract anything useful, my first inclination would be after doing some further testing and searching to see if others had similar experiences, to try to bug Nir Sofer about it -- I think sifting through registry stuff is one of his things