I have had to void eBooster-Beta479 when detecting problems in the start of Windows XP-Prof-SP3. eBooster only had in use 512 MB of Ram. The system doesn’t begin, it is locked, in the moment to select the user account. Greetings.
WINDOWS XP PROF. SP3
4 GB RAM Corsair DDR2.800 Mhz.
Intel Q6600.
I’m using build 479, and previously I have reported frequent freezing problem after hibernation/standby. It will freeze with black screen before or after windows logon. Now I find out that the incidence is much less when I close the Opera browser before hibernation.
This problem maybe due to the utilisation of ram to speedup in Opera.
I have installed “eBoostr beta Build 479” and after running “Western Digital Data LifeGuard Diagnostics 1.09b” I get a blue screen of death with the following error:
STOP 0x0000019 (0x0000020, 0x86132430, 0x86132490, 0x1A0C0006)
There are some descriptions about stop 0x19 here: http://msdn.microsoft.com/en-gb/library/ms793223.aspx
I have saved the kernel dump and the compressed file is about 25MB. Please let me know if you need this dump.
the first picture is from a vista os runing eboostr cache with a allocated memory of 128mb. how to do this:
1. add system memory as a cache device
2. you will be prompted for uac confirmation
3. when asked to be a build the cache on the device press no
4. voila
running fine in xp and 2003
when enabling the cache device the allocated size is fine without any bug
second picture not much a bug ,maybe a translation problem: instead of restart change to start caching or when pressing stop cache automatically change to start cache
All the machines are running inside virtualbox so is possible that eboostr has issues being inside a virtual machine
User configurable option grayed out. though you can still enter any value.
when i look inside the cache file list and mark somthing for deletion the file remains even after restart of the pc. im not sure if this is for a reason or a bug so just thought id post it thanks for all the hard work guys :D
I was wondering if you can choose ‘eboostr.dat’ to be created on non-system partition(c:)
on System Memory cache device.
The reason I demand this is because I like to minimize the write access on my MLC-SSD drive to increase the life-span. If I can select ‘eboostr.dat’ to be created on other HDD just like ‘filestat.dat’ via ‘setting.ini’
If this is possible I think eboostr would be a great tool for SSD user. :)
In eboostr control panel when i hit the stop caching button (shouldn’t eboostr still read from the cache but never refresh it ? ) and after i press the disable system memory button and then i decide that i want to remove the system memory from being a caching device it doesn’t let me. Possible bug or a security measure ?
Installed eboostr into a xp sp2 virtual machine with 191 mb memory. when going to the add cache device i select memory cache. The bar has only 2 option and it is not letting me to change the cache memory size . It has only 48 mb and 256 mb though the minimum cache requirement is 64 mb.
When i click the bar to select more than 48 mb of cache it automatically changes to 256 mb of cache without a second option.
A picture.
Installed a application bsplayer. When building a new cache to apply my new priority of bsplayer it fails to cache. eboostr is the latest installed program and bsplayer had been used before. Here is a picture of what i’m talking about. Running XP sp3 with all the updates.
LE: the build cache now button need to be pressed several times for changes to take effect
