It seems to be an issue with the automatic-memory-address finder getting invalid memory addresses. I just don't currently have the time to fix it. Sorry.
It seems to be an issue with the automatic-memory-address finder getting invalid memory addresses. I just don't currently have the time to fix it. Sorry.