> When you start up, the cache process might not have started yet. It
> starts as soon the explorer has loaded our shell extension and asks for
> an overlay. Problem is, the cache takes some time to start up - and
> during that time, all overlay requests are answered with "unversioned"
> (to not block the explorer!). Once the cache process runs, you can hit
> F5 to refresh the overlays.
>
> Not much we can do about that, without blocking explorer.
Would it be beneficial to try to start the cache even before a request is issued?
I guess we could add the cache to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run in order to get it started as soon as possible on logon. That might mitigate the problem?
(Maybe make it an (confusing :-) ) option in the installer?)
Hans-Emil
Received on Fri Mar 24 13:35:39 2006