System memory’s eboostr.dat on non-system drive
By blueadmin7 | January 4th, 2009 | 6:31 am
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. :)
Jan 04, 2009
I’ve always thought that system memory meant RAM… Didn’t notice that extra drive letter on the end Oo. System RAM isn’t assigned a partition anyway, so it’s not actually being written to your local partition.
Jan 04, 2009
well its written on your c drive with the name eboostr.dat just tick show hidden files in folder options
Jan 04, 2009
I actually found the way to move eboostr.dat to different drive. Didn’t think it was possible but the method was introduced in someone else’s post by Andrew. Anyways thank guys, cheers.
Jan 04, 2009
Come to think of it I have another question…
Let me start with my machine setup.
I have Vista64 with 2 hard drive, 1st drive is SSD with “C:” & “D:”. Another one is regular HDD with drive letter “E:”
So I start off with no cache device. When I try to add new cache device on “E:” drive it will recognize as harddisk case and not system memory cache. Normally I want this to be memory cache because their is not much benefit on using hdd as a cache. BTW I do have “showpartitions=1” triggered so I can see other device.
I’ve also tested this on a single HDD configuration with 2 partition “C:” & “D:” and selecting “D:” would create system memory for the cache like it suppose to be. Just wondering why I can’t do the same in my 1st machine setup…?
Jan 06, 2009
We just think that physical device in most cases will be used as another cache layer.
But you can move eboostr.dat from system partition to another one in regular file manager.
Jan 07, 2009
Thanks Ilya for the response and information.
Initially I didn’t think the eboostr.dat file was movable, but now my concern and problem is solved. :)
I really dig eboostr as I just don’t feel like using superfetch+readyboost. With eboostr it’s more flexible in which files to be cached.