I have two cache devices configured. One in System memory and the other on an SD card. When using the “Show Cache Content” option I can’t see which cache is used for a certain file. This could be nice to have to only put files for which I need fast access in the system meory and leave the others on the SD card.
With the newest build I’ve had my system freeze completely when adding a “System Memory” cache. This has happened both on Windows XP (systerm crash) and Vista (freeze). After the reboot the cache is there and working.
Hi everyone,
I’ve tryed to map 2 disks (1 gb for each disk) and one high speed pen drive (4 gb).
Application priority works ok.
It seems to work perfectly!!
Where to start so many things are fixed with this Beta, I use this primarly on my work laptop with a docking station, I keep a 1 gig USB drive in the dock and undock many times throughout the day. The beta has fixed my issue where my video would not properly restore once redocked, and once I had undocked before it was no different than pulling the USB drive directly out instead of disabling it, now it disables automaticly “safely”. The boot up time was tremendiously fixed, it was using a burst mode before manybe loading 20-30mg per burst of cache per second, takeing a good 10-15 seconds to burst fill the ram Cache, now its a steady stream of data flowing from the hard disk to the ram cache, about 1/2 the time of before directly limited by the speed of the harddrive now. I had not used the Application Priority before, added my apps in there didn’t see the significance of that but will keep testing.
Enhansment request: If it could be implemented easily, I’d like to know on which USB controller a drive was mounted so that I didn’t have multiple drives on the same controller sharing the bandwidth, possibly a suggestion pop-up to alert me to plug seperate usb drives into seperate controllers.
Tried to install it on Windows 7 and got an error message saying You are running Windows, This OS is not supported
Too bad I’m sure it would be better than Ready Boost.
Oh well
Bob Benedetti
I tried E1000 sugestion and here are my results. I may say that I tried several configurations till this last one that is the best as we can see by its astonishing numbers. First: my Intel Turbo Memory is 1 GB sized. It reserves for ReadyBoost just an half of it. The other half I think is used by Intel Turbo Memory’s Windows ReadyDrive that continues enabled. So, only 506 MB are being used by eBoostr. My laptop has 3 GB of RAM so I use 768 MB for eBoostr System Memory. The 4 GB SD Flash Card now is being used for Windows ReadyDrive. The final results:
Monday, January 05, 2009 23:58:30
Direct access speed: 16.417068 MB/s
Cache enabled access speed: 225.981491 MB/s
Ratio: 13.765033
Absolutely amazing!
HP Pavilion AMD 3400 2.19GHz 2GB ram
Windows XP Service Pack 2
PNY 8gb readyboost enhanced USB drive… 2gb allocated for eboostr cache
Beta3 all vers freeze my system for several seconds at a time sometimes up to a couple of minutes
have tried beta3 vers 479, 482, 483 all with the same result
however when I revert back to RC2 Ver424 system works perfectly with no freeze problems at all
Problem with the size calculation whenrebuilding files in bulild version 483
I have the HP 2133 Mini Note, 1.6gHz version, 2 GB RAM, running Vista Business 32. I have eBoostr 3.0, Build 483 and am caching 4095 MB to a SanDisk Ultra II 8 GB SD card. Did not have any problems installing. Just wanted to provide feedback for this configuration.
I’m running Windows Vista Ultimate x64 SP1 on an Acer Aspire 4520G laptop, I have been using eBoostr 3.0 Build 483 with no real problems, actually since Build 479.
I just wanted to submit feedback regarding the control panel functionality with regards to ejecting a cache device, with Build 483 I cannot eject the SD-Card from the eBoostr control panel anymore, even if I disable the device, it used to work on Build 479.
The device is a Transcend 4GB class6 MicroSD Card mounted on the built-in Ricoh Multi-Card Reader.
I can eject it via Vista’s “Safely Remove Hardware” though, so it’s no big deal.
