• Mark A. Munza (14/14) May 17 2002 Is it possible to debug DOS programs under Win9x?
• Roland (8/13) May 17 2002 SCWMN16.EXE is the one to use.
• John Lance (9/9) Jun 07 2002 I believe in an upgrade from 16 bit to 32 bit versions of the product,
• Jeff Peil (9/18) Jan 17 2003 Now this is just from memory, but I believe that in 7.5 adding the
• roland (7/29) Jan 17 2003 with Symantech i think you have to run
• Jeff Peil (5/11) Jan 17 2003 Right, but I believe SC 7.5 shipped with scwmn16 on the CD.

Mark A. Munza <flyinghorse[AT] bellsouth[DOT].net> writes:

Is it possible to debug DOS programs under Win9x?

Trying to follow the supplied tutorials (From CD), Using SCW32.EXE version 7.51,
results in an error message in the output box...

"Warning: This debugger can only debug Win32 applications."

Using SCWMN16.EXE version 7.51 results in a dialog box:

"Cannot create DOS application window"

I assume that I must use the 16-bit version of the IDDE to do DOS development
but I am not sure what I am missing.

Also, while following the tutorials, I discovered that I cannot create any new
work spaces if there are 5 already existing... is this the limit?

-- 
Best Regards,
Mark A. Munza <flyinghrose[AT]bellsouth[DOT]net>
Flying Horse Productions, LLC

Roland <rv ronetech.com> writes:

"Mark A. Munza" a écrit :

 Is it possible to debug DOS programs under Win9x?

yes

 Using SCWMN16.EXE version 7.51 results in a dialog box:

 "Cannot create DOS application window"

 I assume that I must use the 16-bit version of the IDDE to do DOS development
 but I am not sure what I am missing.

SCWMN16.EXE is the one to use.
"Cannot create DOS application window" is a message that remind me something
but i'm
sorry
i can't remember how i turn around.
Try to set "Debug application startup" option and see if it's better ?

roland

"John Lance" <JDLance prodigy.net> writes:

I believe in an upgrade from 16 bit to 32 bit versions of the product,
Symantec did away with the 16 bit debugger.  I am sure that Walter would
know about this or at least would know someone that knows the full scooop.
You had to upgrade in place from 7.21 to 7.5 or something like that to keep
the files for 16 bit debugging.  If you did a fresh install of 7.5 or above,
you lost that capability.  I don't know if the DM product rectified this
situation.

Walter, could you shed more light on this?  And also straighten out any
misinformation (unintended) that I might have done here.

"Jeff Peil" <jpeil bigfoot.com> writes:

"John Lance" <JDLance prodigy.net> wrote in message
news:adrfmc$1k6c$1 digitaldaemon.com
 I believe in an upgrade from 16 bit to 32 bit versions of the product,
 Symantec did away with the 16 bit debugger.  I am sure that Walter
 would know about this or at least would know someone that knows the
 full scooop. You had to upgrade in place from 7.21 to 7.5 or
 something like that to keep the files for 16 bit debugging.  If you
 did a fresh install of 7.5 or above, you lost that capability.  I
 don't know if the DM product rectified this situation.

 Walter, could you shed more light on this?  And also straighten out
 any misinformation (unintended) that I might have done here.

Now this is just from memory, but I believe that in 7.5 adding the
scwdebug.386 and windebug.386 drivers to the [386enh] section of your
system.ini and rebooting was all that was necessary to get this to work (and
I imagine this is sill the case in DM)  Of course this is only possible on
Win9x.



-- 
Jeff Peil

roland <--rv ronetech.com> writes:

Jeff Peil wrote:

 "John Lance" <JDLance prodigy.net> wrote in message
 news:adrfmc$1k6c$1 digitaldaemon.com
 
I believe in an upgrade from 16 bit to 32 bit versions of the product,
Symantec did away with the 16 bit debugger.  I am sure that Walter
would know about this or at least would know someone that knows the
full scooop. You had to upgrade in place from 7.21 to 7.5 or
something like that to keep the files for 16 bit debugging.  If you
did a fresh install of 7.5 or above, you lost that capability.  I
don't know if the DM product rectified this situation.

Walter, could you shed more light on this?  And also straighten out
any misinformation (unintended) that I might have done here.

 
 Now this is just from memory, but I believe that in 7.5 adding the
 scwdebug.386 and windebug.386 drivers to the [386enh] section of your
 system.ini and rebooting was all that was necessary to get this to work (and
 I imagine this is sill the case in DM)  Of course this is only possible on
 Win9x.
 
 


with Symantech i think you have to run


\SC\bin\SCWMN16.EXE

I don't know if it is still there with DM ( I have 2 DM CDs  but i've 
never installed them: Symantec idde works fine with me and i don't like 
to fix something that already works )

roland

"Jeff Peil" <jpeil bigfoot.com> writes:

"roland" <--rv ronetech.com> wrote in message
news:3E288997.1000307 ronetech.com
 with Symantech i think you have to run


 \SC\bin\SCWMN16.EXE

 I don't know if it is still there with DM ( I have 2 DM CDs  but i've
 never installed them: Symantec idde works fine with me and i don't
 like
 to fix something that already works )

Right, but I believe SC 7.5 shipped with scwmn16 on the CD.

-- 
Jeff Peil