Forget most of the above, I just made a very interesting observation! :-)
Currently, the RAM size/disk size of my repaired image is only a couple of megabytes below 2^27 bytes. The defect image is 10 MB larger than this threshold. After loading a 100 MB file into the repaired image and restarting it, the module loading fails again. After freeing the file in the image and restarting it again, the module loading works again.
So the next question is: How could this happen? Are there any RAM size limits that I should be aware of? Or could this even be a bug in the
LoadModule() function because its error message (E_NOACCESS) does not mention exceeded size limits in any way? I have never dealt with such issues before, maybe you have some tips for me.
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.