www.digitalmars.com         C & C++   DMDScript  

c++.dos.32-bits - Compiling and debugging X32 Projects

reply Bernhard Emese <Bernhard_member pathlink.com> writes:
Hello!
In the late 80th I bought the Zortech Compiler and used it a long time to
compile X32 Dos Extender programs. Later I bought Symantec 6.0 and used it the
same way. Now some days ago I bought Digital Mars, also giving my tribute to
this wonderful compilers in buying the newest version. I still compile projects
which dont use the windows operation system. My selfwritten libraries have
enough features to stand alone without windows (only the problem of printing
without printer drivers will probably never be solved).
For debugging I use the Flashtec FlashView Debugger. For assembler modules I use
MASM.
Now I found that the compiler scppn.exe cannot be run under DOS. It  can only be
started in a WIN98 DOS Box. But my Debugger fv.exe cannot be run in a DOS Box,
it needs normal DOS Mode to execute, the same is with MASM. So debugging after
compiling is nearly impossible. What I need are executables, Compiler
(scppx.exe) and Linker (link386.exe) etc, which can be run in DOS Mode. Or can
you tell me, is there a debugger and assembler for X32 available which runs in a
Windows DOS Box. Can You give me advice how I can work with DM compiling and
debugging my X32 projects. 


Thank you very much
Bernhard Emese
Oct 08 2003
parent reply "Walter" <walter digitalmars.com> writes:
"Bernhard Emese" <Bernhard_member pathlink.com> wrote in message
news:bm0h01$270$1 digitaldaemon.com...

 Hello!
 In the late 80th I bought the Zortech Compiler and used it a long time to
 compile X32 Dos Extender programs. Later I bought Symantec 6.0 and used it


the

 same way. Now some days ago I bought Digital Mars, also giving my tribute


to

 this wonderful compilers in buying the newest version. I still compile


projects

 which dont use the windows operation system. My selfwritten libraries have
 enough features to stand alone without windows (only the problem of


printing

 without printer drivers will probably never be solved).
 For debugging I use the Flashtec FlashView Debugger. For assembler modules


I use

 MASM.
 Now I found that the compiler scppn.exe cannot be run under DOS. It  can


only be

 started in a WIN98 DOS Box. But my Debugger fv.exe cannot be run in a DOS


Box,

 it needs normal DOS Mode to execute, the same is with MASM. So debugging


after

 compiling is nearly impossible. What I need are executables, Compiler
 (scppx.exe) and Linker (link386.exe) etc, which can be run in DOS Mode. Or


can

 you tell me, is there a debugger and assembler for X32 available which


runs in a

 Windows DOS Box. Can You give me advice how I can work with DM compiling


and

 debugging my X32 projects.


 Thank you very much
 Bernhard Emese


The easiest way to do it is to debug the program as a win32 application.
Then, port it to X32, that will minimize the debugging. The best way to
proceed with that is to compile/link on one machine, copy the exe to a
floppy, and read it on your DOS machine to debug it. It's tedious, but
workable.
Oct 08 2003
next sibling parent reply Heinz Saathoff <hsaat bre.ipnet.de> writes:
Walter schrieb...

 
 The easiest way to do it is to debug the program as a win32 application.
 Then, port it to X32, that will minimize the debugging. The best way to
 proceed with that is to compile/link on one machine, copy the exe to a
 floppy, and read it on your DOS machine to debug it. It's tedious, but
 workable.


Or have a DOS machine connected via network. Compile on the Win machine, 
debug on the DOS machine.
I don't use the debugger but test my X32 app this way.

- Heinz
Oct 09 2003
parent "Kar Gay Lim" <kagay kimay.net> writes:
Heinz Saathoff <hsaat bre.ipnet.de> wrote in message
news:MPG.19ef34831c6b727c9896d4 news.digitalmars.com...

 Walter schrieb...

 The easiest way to do it is to debug the program as a win32 application.
 Then, port it to X32, that will minimize the debugging. The best way to
 proceed with that is to compile/link on one machine, copy the exe to a
 floppy, and read it on your DOS machine to debug it. It's tedious, but
 workable.


 Or have a DOS machine connected via network. Compile on the Win machine,
 debug on the DOS machine.
 I don't use the debugger but test my X32 app this way.

 - Heinz


And good old Laplink III for DOS still do wonders; or even Kermit.
Oct 09 2003
prev sibling parent reply Bernhard Emese <Bernhard_member pathlink.com> writes:
The easiest way to do it is to debug the program as a win32 application.
Then, port it to X32, that will minimize the debugging. The best way to
proceed with that is to compile/link on one machine, copy the exe to a
floppy, and read it on your DOS machine to debug it. It's tedious, but
workable.


Unfortunately most of my applications are complex graphic applications which
cannot be run as win32 applications. As I see now, the best for me is to use the
scppx.exe compiler from symantec 6.0, which obviously was the last compiler,
which allowed DOS32 compiling and debugging together with Flashteks debugger.

Thanks for your replies
Bernhard Emese
Oct 10 2003
parent reply "Walter" <walter digitalmars.com> writes:
"Bernhard Emese" <Bernhard_member pathlink.com> wrote in message
news:bm6dht$fmg$1 digitaldaemon.com...

The easiest way to do it is to debug the program as a win32 application.
Then, port it to X32, that will minimize the debugging. The best way to
proceed with that is to compile/link on one machine, copy the exe to a
floppy, and read it on your DOS machine to debug it. It's tedious, but
workable.


 Unfortunately most of my applications are complex graphic applications


which

 cannot be run as win32 applications. As I see now, the best for me is to


use the

 scppx.exe compiler from symantec 6.0, which obviously was the last


compiler,

 which allowed DOS32 compiling and debugging together with Flashteks


debugger.

Why not use the scppx from symantec 7.5?
Oct 10 2003
parent reply Bernhard Emese <Bernhard_member pathlink.com> writes:
Why not use the scppx from symantec 7.5?


Its some years ago, when I tried to upgrade from Symantec 6.0 to 7.5 and I
remember that I had difficulties in creating X32 Applications and debugging, but
I dont remember exactly what difficulties. Sorry. Is 7.5 much better than 6.0
concerning X32 applications?


Bernhard Emese
Oct 13 2003
parent reply "Walter" <walter digitalmars.com> writes:
"Bernhard Emese" <Bernhard_member pathlink.com> wrote in message
news:bmeh07$2836$1 digitaldaemon.com...

Why not use the scppx from symantec 7.5?


 Its some years ago, when I tried to upgrade from Symantec 6.0 to 7.5 and I
 remember that I had difficulties in creating X32 Applications and


debugging, but

 I dont remember exactly what difficulties. Sorry. Is 7.5 much better than


6.0

 concerning X32 applications?


I think it's about the same.
Oct 13 2003
parent Bernhard Emese <Bernhard_member pathlink.com> writes:
In article <bmf4kn$85$1 digitaldaemon.com>, Walter says...

"Bernhard Emese" <Bernhard_member pathlink.com> wrote in message
news:bmeh07$2836$1 digitaldaemon.com...

Why not use the scppx from symantec 7.5?


 Its some years ago, when I tried to upgrade from Symantec 6.0 to 7.5 and I
 remember that I had difficulties in creating X32 Applications and


debugging, but

 I dont remember exactly what difficulties. Sorry. Is 7.5 much better than


6.0

 concerning X32 applications?


I think it's about the same.


Thank you for Your fast replies (and for Your fast compiler).

Bernhard Emese
Oct 14 2003