same function as exclude path, can I include path into cache list?
same function as exclude path, can I include path into cache list?
I second that, also exclude/include would be nice to be configurable per cache-media. One other configuration I would like to see is specify max-filesize of items being cached.
I agree. I would very much like to add entire directories to the cache. In my case I have a 48GB expresscard SSD that is way faster than my hard drive. I want to use it plus my hard drive as a hybrid system: the SSD for fast bootup and app launch, the hard drive for data files, storage, and backup. To speed up Windows boot I'd like for eBoostr to cache any file that loads after eBoostr starts (including drivers and system files), and I'd like to add the Windows prefetch directory to the cache.
I suggested an Include function already 2 years ago and i also wrote an Email to Andrew Z. 2 month ago about that but i never got any reaction.
Instead of excluding endless folders, it would work better the opposite way, where i just tell Eboostr what to cache and what to skip.
So i basicaly had something like a Ramdisk at the end which i would prefer instead of Eboostr collecting data from all over my harddisks.
In example if i just want Eboostr to cache >
c:\Windows\System32
c:\Programs\xxxxxx
d:\data
e:\data2
f:\data3
g:\GameXYZ
then i have to exclude the whole rest of my Drives folders. it would be easier to just tell eboostr to cache these few.
Regards
Andrew
It's a good and bad idea. Eboostr doesn't really help with "boot up" but only "start up." Boot up is where the drivers and system files are read by boot.ini. Startup is all your programs like yahoo messager is started up. If you use ram as the cache drive, you'll end up with a longer boot up than a better start up. Reason being is cause you'll have to reload everything back into the ram drive after a shutdown or restart. This is why eboostr takes a bit before actully speeding up anything. Keep things simple, boot.ini can only do a few things at once while windows can do many things at onces resulting in a better start up than a boot up.... (Ff you don't understand, I'm sorry; it's really hard say unless you know windows works when starting up.)
Also, you're wasting cache on files you may never really use or notice while things in your Windows file should be the ones getting most of the cache to start up/take less stress off your game because files that are most used are the ones cached in the fastest drive for faster/less stress use.
Yes, it's the right idea to cache the program rather than the data. In a simple way to say data is variable then the program is fixed.
You must log in to post.