The Fail Safe Mode is a great improvement for initial testings, but it needs to be improved for regular use.
Today my PC froze due to a problem unrelated to eBoostr. After it rebooted I was focused on other issues, and it took me over 15 minutes to notice that eBoostr was not caching. I only noticed the yellow system tray icon (instead of green) by accident. Although technically oriented people (and eBoostr beta testers in particular) will notice the paused caching, non-technical users might not notice at all ... and some might not know how to turn it back on. We need to recognise that PC's will regularly crash for reasons that have nothing to do with eBoostr.
I suggest that we should look at one of two refinements:
1) Make the Fail Safe Mode an option that can be turned on and off. So it can be turned on for initial testing, then turned off.
2) Implement a way for caching to restart automatically if the system is booting sucessfully. Perhaps it would restart caching after one sucessful reboot, plus ten minutes (which would give one enought time to change the configuration is eBoostr had caused the crash or freeze.) Or Perhaps eBoostr restarts caching after two sucessful reboots.
I'm in favor of some way of automatic restart on sucessful booting, so that the user doesn't have to think about it when the PC does it's regular, occasional crash. But something should be done to improve the current implementation!