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.