If you don't wish to write memory, then don't write memory?

MemProcFS does not write memory by itself. It requires user-action.

But yeah, I guess I can add a -read-only startup argument in next update.

If you don't wish to write memory, then don't write memory?

MemProcFS does not write memory by itself. It requires user-action.

But yeah, I guess I can add a -read-only startup argument in next update.

Thank you for answering my question.
I am concerned that other software may secretly write to memory after calling vmm.dll. Is the -read-only startup parameter effective against calls from other software?
If possible, could a read-only code version of vmm.dll be released?
(I'm trying to remove the write operation from the source code, but I haven't been successful so far.)

I'm not going to create a separate binary.

Besides, even if I were to do such a thing there is nothing preventing other software from bringing their own write-capable version anyway so it wouldn't do anything at all...