VOGONS

Common searches


Search results

Display options

Re: DOSBox debugger

"Program Files" is likely the problem, as you'd tend to run into UAC. You could try making a shortcut that puts the current directory somewhere not restrictive; or just put the vanilla debugger executable where you're putting the fork executable. The SaveMemory() code in DOSBox-X appears no …

Re: DOSBox debugger

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 …

Re: DOSBox debugger

DOSBox emulates only the hardware that games use directly, otherwise it emulates at the BIOS level, so I guess you could say it's partly a high-level emulation. In any case, a real PC BIOS needs pretty much all of the hardware to be emulated, so loading one in DOSBox won't really work.

Re: DOSBox debugger

The debugger causes changes to the memory layout for the programs running inside the emulated environment? Only when the DEBUG.COM launcher on the Z: drive is used, because it is a parent process that allocates memory blocks ahead of the launched child process. You can start debugging at the entry …

Re: DOSBox game blaster emulation vs. SAAYM

In my tests, pitch changes occur when the saa1099 sample generation rate does not match the mixing sample rate. After the clock rate changes committed in r4010, subsequent updating to the then-latest MAME sound cores introduced a difference in rates. The attached patch (experimental for now) appears …

Page 3 of 195