Would anyone tell me that if the Comodo DiskShield can set its cache area in the RAM only?
I am using a computer with SSD (Soild-State-Drive), a type of flash memory drive with the finite erase/program cycle capability.
Therefore, I am looking for a software that can redirect Windows XP’s all (or most) physical disk writing activieis into RAM. In this way, the writing activities toward the SSD can be greatly reduced, and the life of SSD can be extended.
I found no information about the RAM cache of Comodo DiskShield, instead I found that the Cache of the Comodo is “the whole of the free HD space that can be used”
I believe if the Comodo DiskShield can set its cache area in the RAM only, a lot of SSD users will use the DiskShield to extend their SSD life.
Just thinking out loud, but I’m pretty sure the cache file has to be on the physical disk being shielded. The only way I can see around this is to load Windows to a RAM Disk and then shield this logical disk.
hello, I think it is easy for the developer make a RAM-Cached version of this program. But they will meet a problem that a driver can not allocate much ram space due to this ram space must be non-pageable, that means you can’t work on this way for long time or you will get the windows delay write error.
some ways to solve this problem includeing :
disable your page file in control pannal, this will significantly reduced the usage of cache area.
you must have enough ram space for the cache’s use, and try to only shield the volume you need to(like system volume).
No’, I"m not part of staff - just a user and a volunteer moderator. I know because I asked. I wanted to know if RAM caching could be added and was told that the trade offs in speed and efficiency had to be evaluated. Another thing they need to consider is the availability of disk space as compared to available RAM.
IMHO, for the vast majority of users, while utilising a RAM cache for Disk Shield would improve its performance, it would do so at the expense of overall system throughput, as you would be reducing the amount of RAM available to the rest of the O/S and any running apps. All this would do is force more extensive and more frequent use of the paging file, which dumps us back in the realm of writing to disk, which is exactly what we are trying to avoid.
I don’t think it will happen, as you wold then have people complaining that their system slowed down too much.
It’s just a mode, an option, if you don’t have a large RAM, you can use another mode like disk caching. A real RAM caching mode will be popular for two reasons: one is large RAMs are very cheap, two is SSD will replace the traditional harddisk.
Thanks a lot, now I’v already installed it and it works well. But there is a problem, it doesn’t release spaces automaticly. I copied a file which was 50mb to c:\ in order to see the effect, when I deleted the file ,it still occupied the RAM spaces.
The problem is that ewf doesnt know what is a file … it work at NTFS level.
When you create a file you have two thing.
the file information are writen to disk sectors
A table point the file to the region on the disk
When you delete the file
The entry is removed from the table
the space no more reserved and another file can take it
but the bit changed on the disk are still changed wich is why
you can undelete file
you need secure delete if you do not want a file to be recovered
The space is not freed by ewf as the disk is still changed…
This is why i tougth that fbwf was an interesting approach.
It’s less powerfull but it understand what are the file being created.
(it probably can apply protection per file/folder too)
FBWF (file based write filter) offers some important advantages. FBWF uses less ram (you can reclaim ram overlay space when you delete files), you can also commit on the fly (without restarting or disabling), and have persistent (write through) folders that write straight to the drive (so you can have a persistent My Documents for example).
Commiting change is done file per file , you got script to automate this task on post 19 and 24
[edit]
I beleive the information here is interesting and can be usefull even for comodo dev.
However, those interested in this solution should post on the other forums as this is a comodo support forum ans I do not want to start an off-topic discution.
