4

I've only done that and the window turns frozen while executing the program:

debug.exe
-a0100
073F:0100 MOV AX,0002
073F:0103 MOV BX,0004
073F:0106 ADD AX,BX
073F:0108 INT 20
073F:010A
-g

...and it fails. It doesn't fail if I try:

-g108

Because, it ignores "int20" and, of course, it doesn´t work with:

-g10A

What can I do?

Michael Petch
  • 46,082
  • 8
  • 107
  • 198
Pablo Ramirez
  • 49
  • 1
  • Try int21/4c if you just want to terminate your program. – Jester Jan 31 '17 at 22:00
  • 1
    Did you try 20h instead of just 20? – Jose Manuel Abarca Rodríguez Jan 31 '17 at 22:04
  • @JoseManuelAbarcaRodríguez : debug.exe is pretty ancient - it doesn't take prefixes or suffixes to specify base. Everything is in hex. – Michael Petch Jan 31 '17 at 23:39
  • 7
    You likely have a program called `debug.exe` .It was likely acquired from a 32-bit Windows distribution. Unfortunately `debug.exe` from Windows is known to have issues like this under DOSBox. You should delete `debug.exe` and download a version of `debug.com` for DOS. You can download it from my webserver at http://www.capp-sysware.com/misc/DEBUG.COM – Michael Petch Jan 31 '17 at 23:55
  • 1
    I have a suspicion we'll find that this question will probably be a duplicate (or a variant of) of http://stackoverflow.com/questions/36230551/dosbox-debug-exe-reads-file-processes-commands-incorrectly – Michael Petch Jan 31 '17 at 23:59
  • 1
    Instead of INT 20, try | MOV AX,4C00 | INT 21 | . – rcgldr Feb 01 '17 at 15:17
  • Definitely i had to use the debug.com file instead of debug.exe. Thanks for the file. – Pablo Ramirez Feb 02 '17 at 07:53

0 Answers0