The only debuggers i have are Borland's turbo debugger and Microsoft's Debug. Both are incapable of dealing with 32bit registers. Can someone please tell me what debugger you use and where I can find it.
Posted on 2001-11-24 20:49:04 by LOLTH
Try Ollydbg at Its non-symbolic, except maybe for Tasm output, but very good IMHO.
Posted on 2001-11-25 03:42:14 by peterverstappen
Go for softice. It's the one and only :)
Buy at or pay a visit to your local warez dealer..

Posted on 2001-11-25 15:15:00 by latigo
OllyDbg is very good for ring3. There's a 32bit version of tdebug
you can get (for free, legally) at There's microsoft's
windbg. And then there's softice.

I recommend OllyDbg for ring3 debugging. Unless you need you
know softice, you probably don't ;)..
Posted on 2001-11-25 15:43:29 by f0dder
ring3? I have tried OllyDbg, and it appears to only be capable of dealing with windows 32bit applications. As for tdebug, my version can recognize 32bit commands, but it has trouble dealing with 66h or 67h commands. As for WinDbg i keep getting an
ERROR - Could not execute: Invalid paramter(Win32 error 87)
Start failed
if i try to debug a .exe, and a no debuggee specified error when i try to run a .asm file.
I have not been able to successfully use any of these debuggers for 32bit register code in a dos environment.
Posted on 2001-11-25 17:16:20 by LOLTH
For 32 bit DOS code, Microsoft shipped SYMDEB with MASM 5. You may have trouble finding it for free, since it was part of the retail package. :)

Oops, I made a mistake. SYMDEB came with MASM 4, and was still only 16 bit. MASM 5 included CodeView (CV.EXE), that had the option to support 32 bit. :)
Posted on 2001-11-25 17:24:45 by S/390
If you want to debug *protected-mode* DOS programs, use softice
for windows, it's the only thing that really has the grunt that's
needed. If the dos app is too dirty to run under windows... you'll
have a hard time finding anything that'll work =).
Posted on 2001-11-25 19:20:53 by f0dder
Well, really dirty DOS apps could be debugged in an emulator.
Posted on 2001-11-25 19:23:54 by bitRAKE
all i want to do is to be able to trace through a 32bit dos program... every debugger that accepts dos programs misinterprets
mov eax,somenum
as a combination of a
mov ax,sumenum
and some other command
is there some command i need to use to make these debuggers (debug, td, symdbg) understand that i am using 32(not 16)bit immediate data?
If there is no way for the debugger to tell what size the immediate data is, how does the processor know?
Posted on 2001-11-25 21:02:14 by LOLTH
to debug 32 bit dpmi dos programs use softice or trw2000
Posted on 2001-11-26 04:13:27 by japheth