The .417 release worked very well, like the previous three or four releases did. Have I to report an “all working very well” post? :-)
My PC is stil working very hard. So I think I’m getting eBoostr under pressure, but it’s working great. I think eBoostr is now a reliable software: the developing team could start working on the speed performances again.
Today I’ll upgrade eBoostr to the last release.
I am having very regular Delayed Write Errors for the file eboostr.dat on my flash drive which disables the cache. This most often happens during a re-build. It also happens when I re-boot the computer. Removing the flash drive and reinstalling seems to get things set back right again, but it’s extremely annoying. Drive properties are set correctly (Optimized for Quick Removal). This is severely limiting the effectiveness of the program.
While using the RAM as a cached device is a great idea, it’ll be even better if eBoostr can emulate Vista’s SuperFetch features.
Mainly:
– Dynamic RAM-cache allocation/deallocation. If an app needs more RAM (or the VM is running low), eBoostr should reduce the size of the RAM cache; conversly, it should increase the cache size if there’s plenty of free RAM. Of course, there should be options to set the absolute upper and lower limits.
Perhaps at a later stage:
– Heuristics to determine which apps are used most frequently, on which days, and at what times, so that eBoostr can precache those files
– Ability to prioritize certain files/programs so you can be sure its always cached.
– Options for adding per-process cache preference. For eg, eBoostr could automatically resize or disable the RAM-cache when certain apps are loaded that you know will require a lot of free RAM, like Photoshop or VMware.
This may seem a lot right now, but I don’t see why it can’t be done. I certainly hope the devs consider adding these features in the roadmap at the least.
For all you people getting wierd thing happen when you have 417 installed and use ram cache you can solve your problems by going back to 416. I have had many weird things happen when using ram cache on version 417 and since going back to 416 this has solved it for me.
Pay NO attention to this post as it just turns out it takes longer for eboostr to mess up the system when using ram cache with this build than it does for version 417
In version 417, just downloaded and testing it.
Why this happens to me? When in system memory cahce, 512 mb cache, it really speeds up but it crashes when i want to see cache’s inside? disturbing
Running under WindowsXP PRO with 2 gigs of Ram and using 510 Ram as Cache, WindowsXP WILL NOT run Chkdsk /f.
After uninstalling eboostr chkdsk ran the very first time.
April 21, 2008 Additional Info:
This problem only happens when you are using MEMORY as cache. Tested it today and when I did not using memory as cache Check Disk Fix worked fine.
Bill Haynie
Im just wondering that would it be useful to add network drives into cashe? By this I mean cashe data from network drives instead of local hardisks only.
Just upgraded to release 417 and note my computer VIRTUALLY NEVER stops rebuilding cache and rarely shows the correct percent full indication. If it finishes rebuilding cache, it only lasts until I pause my work then starts AGAIN, to rebuild. It spends more time rebuilding that it does working between rebuilds.
As far as working with Windows 2000, Release 417 appears to be a step backwards in functionality.
Update 4/19/08 – I totally uninstalled 417, reinstalled 416, it worked well, it autoupdated itself to 417, and has been working fine. Maybe there were some old artifacts causing the problems. I’ll run this for a while and update any further situations.
Hy everyone, i’m an “old” eBoostr user, and today I’ll start the new release testing. I never had any kind of problem while using the previous 416 release. I use my PC for 8 to 10 hours a day, for working. My WinXP is working very well. Soon I’ll send some speed test.
I’m not sure what was changed between Beta 416 and version 417. But after installing version 417 and leaving the PC for a few hours I came back to this message on MOST applications. It was all fine after a reboot. here’s the message for explorer.exe
