Romex Software Forum

Yes, actually we can do it. But we also need to update the VSuite Ramdisk program.

Does the error still exist after computer reboot?

Did you also install the FancyCache For Disk?

Nice, thanks for your suggestion!

mmm...quite strange...

Thank you very much for your detail feedback!

We will check it and find a solution.

Stubi wrote:But normally Windows should block the memory areas.

Yes, i think so.

We can defer to boot ramdisk to solve your problem, but it introduces other issues in some use cases. So we requires the same file system.
Anyway if later we can find a perfect way to solve the issue, of course we'd like to correct it.

Is it possible that the problem is caused by the incompatible physical RAM bar? Actually we have the cases that the hardware is not good or compatible.

Thanks, i see. Did you ever see the corruption of the image file in this case? because when it beyonds the available memory, system will try to get more free memory by swapping some data in memory to paging file. Thus although system might slow, but ramdisk still can get correct data. In worst case,...

This is because file system might not ready to read the file when we boot up the ramdisk.

Hi, I checked intel i3 datasheet. But I am sorry that currently I can't find anything to confirm that if it uses OS Invisible memory or visible memory. Perhaps something are also related to BIOS settings. However there is one way for your reference. Since HD Graphics shares system memory, generally ...