Comments on: Build 543 : Automatic Configuration fixes http://beta.eboostr.com/blog/feedback/build-543/ eBoostr Version 4 Public Beta Test Program Sat, 24 Apr 2010 17:36:06 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: msilva http://beta.eboostr.com/blog/feedback/build-543/comment-page-1/#comment-2166 msilva Thu, 26 Nov 2009 18:38:03 +0000 http://beta.eboostr.com/?p=1507#comment-2166 Hi, Version 543 has been working very well on my Toshiba Satelite U-400 12E the only problem a have is that E-boostr keeps telling me that the license Key will expire in four days from today. Is there a license key I should use to solve this? Thanks, Mário Hi,

Version 543 has been working very well on my Toshiba Satelite U-400 12E the only problem a have is that E-boostr keeps telling me that the license Key will expire in four days from today.
Is there a license key I should use to solve this?
Thanks,

Mário

]]> By: Robert Persons http://beta.eboostr.com/blog/feedback/build-543/comment-page-1/#comment-2163 Robert Persons Fri, 20 Nov 2009 02:37:24 +0000 http://beta.eboostr.com/?p=1507#comment-2163 I originally posted this on the general forum, but later realized that it should have been posted here: 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 improvements: 1) Make the Fail Safe Mode an option that can be turned on and off. So it can be turned on for initial configuration and 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.) 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 has it's regular, occasional crashes. At least we should have a setting in the settings.ini to disable Fail Safe Mode after initial configuration. I originally posted this on the general forum, but later realized that it should have been posted here:

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 improvements:

1) Make the Fail Safe Mode an option that can be turned on and off. So it can be turned on for initial configuration and 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.)

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 has it’s regular, occasional crashes.

At least we should have a setting in the settings.ini to disable Fail Safe Mode after initial configuration.

]]> By: freddy67 http://beta.eboostr.com/blog/feedback/build-543/comment-page-1/#comment-2162 freddy67 Tue, 17 Nov 2009 14:42:27 +0000 http://beta.eboostr.com/?p=1507#comment-2162 Andrey I tested using more than 1023mb of unmanaged (1280mb tested of 1289mb found), system crashed as with previous versions, the auto config 1023mb seems to be the cut off point. Freddy Andrey

I tested using more than 1023mb of unmanaged (1280mb tested of 1289mb found), system crashed as with previous versions, the auto config 1023mb seems to be the cut off point.

Freddy

]]> By: CAPTAHA http://beta.eboostr.com/blog/feedback/build-543/comment-page-1/#comment-2160 CAPTAHA Sat, 14 Nov 2009 22:55:13 +0000 http://beta.eboostr.com/?p=1507#comment-2160 Installed 543 on Dell Precision T3400 Windows 7 64bit. Unable to reboot. Unable to reboot in safe mode. Computer ran self repair for about 1.5 hours and then rebooted successfully. I will wait for another release addressing this before trying again. Installed 543 on Dell Precision T3400 Windows 7 64bit. Unable to reboot. Unable to reboot in safe mode. Computer ran self repair for about 1.5 hours and then rebooted successfully. I will wait for another release addressing this before trying again.

]]> By: freddy67 http://beta.eboostr.com/blog/feedback/build-543/comment-page-1/#comment-2158 freddy67 Fri, 13 Nov 2009 11:19:05 +0000 http://beta.eboostr.com/?p=1507#comment-2158 Andrey Upgraded to 543 from 539 & all was well until I came to shutdown pc, windows closed as normal but pc kept running. After each reboot windows would shut down on it's own & pc would keep running, uninstalled in safe mode & did a fresh install, no problems since. Freddy Andrey

Upgraded to 543 from 539 & all was well until I came to shutdown pc, windows closed as normal but pc kept running. After each reboot windows would shut down on it’s own & pc would keep running, uninstalled in safe mode & did a fresh install, no problems since.

Freddy

]]>