The 128, 256 or 512MB size limit on the modified non-write thru cache only for the users TEMP folder is too restrictive and can result in writes to the users TEMP folder overflowing the restricted space allocated… in MOST systems multi-gigabytes of physical RAM is available to the systems drive cache and to only reserve a tiny fraction for the TEMP when it should be dynamically adjusted according the RAM usage and expanded as needed IF spare RAM is available. I’d like to see the other cache manipulation program they do offered as a giveaway to try out for more than 30 days “GiMeSpace RAM Folder Pro” as I can see value in making the event log folders non-write through to the SSD to as well as some other system folders which contain regularly updated logs that are never used for the end users benefits but are used by Microsoft telemetary for reporting back the state of the system for their statistics on which bugs to address and which ones to not bother with. And make the systems SSD last longer.