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.

[@hack_attACK] The Pro version is available for a bargain this week. Windows software is not a good market, I have to make some profit from this else I might as well end the GiMeSpace project.

[@GiMeSpace]

So what’s your website so we can read/learn more about the PRO version and possibly buy it?

[@GiMeSpace]

I totally get it!.. I was in your shoes when I started out years ago.. but honestly, the market was way better back then. Keep shipping, your product is solid!

GiMeSpace wrote:

[@TK] You keep insisting get everything for free. Windows software is not a good market, I have to make some profit from this else I might as well end the GiMeSpace project. The Pro version is available for a bargain this week.

The GiMeSpace RAM Temp Folder 1.3.0 might as well be freeware for all it does… check out the sysinternals freeware and see what you are up against, well functional USEFUL programs offered for free not crippled programs sold or attempted to be sold and offered for free, why not be honest how many people have actually bought “GiMeSpace RAM Temp Folder 1.3.0” and said they were happy to spend the money on it? Remember you used to have it limited to just 128MBytes allocation and only added 256 and 512MB options since receiving feedback from the likes of me on giveaway sites other than this one… I don’t want everything for free and do occasionally find software worth paying for and much of the software on these sites from Chinese and at least one German and I think a Brazilian developers are illegal to distribute as they steal intellectual property so are not legal to distribute and not legal to buy as that would be knowingly receiving stolen property which is a crime here in the UK and other jurisdictions!

The business model of these giveaways is limited install authorisation to a specific period of time and a fully functional license in the hopes the users will like it and recommend it to their social network and if and when they re-install windows which is a solution often resorted to by the computer illiterate to solve PC problems or buy a new PC the vendor participating in the genuine giveaway is hoping their given away product has become indispensable to the giveaway participant that they will buy a fresh license for their re-installed PC or new PC. IMHO the product “GiMeSpace RAM Temp Folder 1.3.0” is not worth installing as it’s too limited in scope so not worth installing even for free so does not fit into the normal giveaway sites sponsors business models. Offer your best not your worst if you want a good reception and possible sale in the future when the giveaway is no longer on and the participants have lost the original license due to windows system churn… These sites are not intended to be up-sell squeeze pages to manipulate end users into buying a functional program after only being offered a crippled pointless one. Such abuse of these sites only fosters bad will towards the manipulative vendor in my experience.

[@GiMeSpace] Excellent customer relations… Trump never wrecked your economy allowing capitalism to use communist cheap labour and taking USA resources and spending them on that cheap communist labour instead of paying your own peoples living wage is what’s fundamentally ruined yours and other capitalist economies in addition to putins unprovoked invasion of Ukraine on the pretext that NATO was in any way a threat to Russia if Russia chose a peaceful and non-expansionist path. Admittedly Trumps tariff actions where an massive own goal for his countries citizens and businesses but that’s what you get when he considers the federal government to be America and not the people… when he claims the tariffs has made money for “America”… it only made some money for the federal government at the expense of the USA population and business. Also forgetting that America is not just the USA but includes ALL the other countries of both American continents.
Remember the Love of money is the root of all kinds of evil… and Trump once boasted on TV how he “loved money, especially other peoples money”… it’s as if he has no knowledge of the faith he tries to court.

Question came to my mind the other nigh how do maintain file system integrity when the size limit of the (in this programs case) TEMP folder content writes exceeds the preset limit? DO you just deny further writes or do let the file system fragments overflow the non-write-thru cache and make it onto the real NTFS file system and produce a corrupted file system as the non-written parts of the filesystem remain missing… does the file system and journaling survive such inconsistent writes to the NTFS persistent structures… I’m beginning to think that without in-depth knowledge of what happens to the data after the size of the allocation is exceeded I don’t want to risk messing up my disks with potentially inconsistent writes and also how it would affect VSS store too.

[@GiMeSpace] Just tried out your RAM folder Pro 64bit edition and it would not let me add
“C:\Windows\System32\winevt”
or “C:\Windows\System32\winevt\Logs” claiming the file was not writable…

It wasn’t a file but a folder and the folder is writable!

Making the evtx files temporary would be a good use of this IF it worked but for some odd reason it did not work.
Same occurred for C:\Windows\temp … debugged it… the UI is launched without elevated rights so on folders that require elevated rights to write to throw up this faulty error. A: it’s not a file and B: it is writable by elevated processes. The workaround is to launch the program as an administrator either manually or via windows comparability settings.

Any reason why you don’t require elevated rights to run this program? It’s easy to do. Personally it should NOT matter if the target folder is writable or not since this is a non-write-thru cache that should not need to write to it anyway!
I note the default settings for max RAM usage is 14GB on my 16GB system… if that is suitable for this program why cripple REM TEMP Folder so badly?