I ran as admin and it still didn't work, I'll try moving to a user directory. In this case the file create would still fail, so I think there should be error checking at least instead of saying the dump was saved. Writes from unprivileged programs to Program Files don't fail, they get redirected to …

I ran as admin and it still didn't work, I'll try moving to a user directory. In this case the file create would still fail, so I think there should be error checking at least instead of saying the dump was saved.

I wouldn't think so, but then I'd also think the file is being created. What is the current directory in your case? I just tested again by running as an admin. Again for some reason this works with DOSBox-X and not regular DOSBox. My mount is in C:\dosprogs, DOSBox-X runs out of my user Downloads …

In the debugger, the MEMDUMP command creates a text file named MEMDUMP.TXT, the MEMDUMPBIN command creates a binary file named MEMDUMP.BIN. The files are created in the current directory, sometimes referred to as the working directory, which is not necessarily the same as a mounted directory …

I'm having an issue with memdump/memdumpbin - for some reason it's not producing a memory dump. I've tried with and without running the program under DEBUG (MS-Debug). DosBox gives me the correct log message of "DEBUG: Memory dump success.", however I cannot find memoydump.txt/bin under my current …

I'm having an issue with memdump/memdumpbin - for some reason it's not producing a memory dump. I've tried with and without running the program under DEBUG (MS-Debug). DosBox gives me the correct log message of "DEBUG: Memory dump success.", however I cannot find memoydump.txt/bin under my current …

Just wanted to drop a quick thank you for the precompiled debug versions, along with a nice debugger. Perhaps more notes on how to build from source would be great, like which versions of SDL you're using, what version of VS, etc. Again, much appreciated.