Romex Software Forum

I tested an earlier version of PrimoCache on Windows Server 2019 and it caused ReFS filesytems on Mirrored or Parity Storage spaces to be unable to self-heal or repair bit-rot corruption. Can you please confirm whether that problem has been fixed in the new version? Also, is it possible to cache the...

I'm not putting beta versions of anything on my machines. Still waiting for the release to try it out, and in particular looking forward to the server version.

Microsoft changed the policy of third-party software for Server 2016, we have to do much extra work for the server edition for each release. To reduce work overload, we decided to bypass the releases from v2.5.0 to v2.7.3 since updates in these versions are mainly for Win10/Server2016, and will sup...

I am very keen on a server version. Will there be a server edition of this when it is stable? From the download page it looks like the server edition is abandoned and there has been no new release supporting Server 2016.

Hi, I used PrimoCache 1.0.1 to test out on a couple of my systems and I ran into some bugs which caused crashes and disk corruption. I would like to try out PrimoCache 2 and see if it suffers the same problems. Since my trial of PrimoCache has expired and I chose not to buy it at the time, can I ins...

This seems to be the case. I experimented by installing PrimoCache on my old laptop at home just for experimenting and it caused corruption in the WinSxS component store during a windows update run. The next boot reverted the update and required me to "dism /online /cleanup-image /restorehealth...

Good to hear that this is being looked into. Let me know if you need more details like a step-by-step on how to re-create the problem I experienced.

While I am sure it would work OK with a smaller cache, it does not inspire confidence in the software for bugs such as these to go unfixed for months at a time. As I stated earlier (in another thread), I am reluctant to trust any valuable data to PrimoCache until such time as these bugs are fixed.

Since you had hardware errors, it seems inappropriate to blame any issues on software, so in your case at least, the RAM is solely to blame. There is no question of hardware error in my case however, and the bug still exists and manifested in some Windows-to-Go workspaces I created last Friday. I am...

(This should have been in the previous comment, but I posted it accidentally trying to preview; Sorry.) As for diagnosing it, all one needs is Windows 8.1 Enterprise x64 and a Sandisk Cruzer Extreme USB 3 flash drive (min 32GB). The error can then be reproduced on any machine with more than 16GB of ...