Romex Software Forum

You were testing the drive with Windows on it? That can be problematic given how Windows monitors and updates itself. You'd have to switch back and forth from a drive image of windows for a real apples to apples comparison. Also, how long was the new version of PrimoCache installed, the whole two we...

Afaik your 2.7.0 key should work on the beta. That's what I have. But let support confirm this first. I think you have nothing to worry about though.

WinRar works the same way, I'm using the latest beta, and my key works fine with that.

Which drivers do you use? With that variety, I might be tempted to use the Win 10 native NVMe driver. What happens when you enter Device Manager and "uninstall" the drive -- meaning its driver? You would reboot, and Win should find the device to configure the native driver to it. Once you...

No Samsung SSDs here. I have two Mushkins, a MyDigitalSSD BPX M.2 NVMe, and an ADATA that was partitioned to house a Level 2 cache. Though I do have a Samsung flash drive, but no Samsung software. Hmm, I wonder if Microsoft updated their OS to accommodate Intel's Optane technology, and that caused a...

Huh, I too was running an L2 cache but ended up ditching it as part of my uninstall of Primocache before reinstalling it. Maybe that was what fixed the "scanning/repairing" issue I was having? Either way, I'm relieved it's gone now.

I uninstalled Primocache and then installed the latest version, instead of installing on top, and now I no longer get that quick message at every boot saying Windows is repairing some Volume with a very long naming scheme. I was getting that for days and I tried a lot of different things. I think un...

The file size is a tiny bit different, 5,786,360 bytes vs. the 5,786,248 bytes of version 2.70. Though you only see that when clicking on Properties. The timestamp is from April 12. I'm guessing this is a small bug fix to something that came to their attention in regards the Windows Anniversary build.

As seen in this picture, almost nothing is written to the L2 cache, and consequently the cache hit ratio is ridiculously low. I've already rebooted waiting before logging in, and I've already set the gather interval to 1 sec. Nothing else I can try ? Hopefully that changes, but it's important to re...

geneo wrote:I guess not. Is anybody minding the store?

Hopefully this indicates it's "all hands on deck" and "battle-stations" because they are testing the new version.

Yes, you would just want to make two cache tasks, one for each (Use the green "+" button at the top/left to create a new cache task). That's what I'm sort of doing now. You'll maybe want to set a large block size (32KB or higher) for the L1 cache, otherwise the memory overhead can be disma...