• Steve & Denise De Chellis (6/6) Dec 23 2001 I can't get the debugger to work with DOS programs. No matter which IDDE...
• Roland (24/30) Feb 20 2002 a little long to answer, i don't use to look at this folder..

"Steve & Denise De Chellis" <dbouton snet.net> writes:

I can't get the debugger to work with DOS programs. No matter which IDDE I
use I either get "can't create dos application window" error or a line in
the output window says " Warning this debugger can only debug Win32s
applications"

Can anyone help me with this?

I've got a 950 Athlon with Windows ME.

Roland <rv ronetech.com> writes:

Steve & Denise De Chellis a écrit :

 I can't get the debugger to work with DOS programs. No matter which IDDE I
 use I either get "can't create dos application window" error or a line in
 the output window says " Warning this debugger can only debug Win32s
 applications"

 Can anyone help me with this?

 I've got a 950 Athlon with Windows ME.

a little long to answer, i don't use to look at this folder..

To use DOS 16 bit debugger use 16 bit IDDE:

\SC\bin\SCWMN16.EXE

..on SC 7.5, i guess

\DM\bin\SCWMN16.EXE

now.

There is no DOS 32 bit debugger in the idde yet and probably never,

I never tested Windows Me, i use Win 98 SE.

If you want to debug dos graphic application, you have to run Windows in
standard VGA mode..
not very practical, windows seem very small. I can't understand how i could
work so long years in vga (not to speak of EGA).
For that, i create a windows hardware profile (in system properties) with no
graphic card at all.

At last, the 16 bit DOS debugger is VERY slow..except if you have a 950
Athlon.

Conclusion:
- use DOS 16 bit debugger only if all other technic (puts, assert..) had
failed,
- if you want to debug DOS 32 bit, make your code conditionaly compilable in
DOS 16 bit as well, recompile it for DOS 16 bit
and debug it with the idde.

Roland