c++.dos.32-bits - Is the DMC++ debugger compatible with programs which use the 32X DOS extender ?
- "Jurek Wozniak" <jurek_wozniak zdnetonebox.com> Jun 16 2001
- "Walter" <walter digitalmars.com> Jun 16 2001
- "Jurek Wozniak" <jurek_wozniak zdnetonebox.com> Jun 17 2001
- "Walter" <walter digitalmars.com> Jun 17 2001
- NancyEtRoland <nancyetroland free.fr> Jun 19 2001
- "Walter" <walter digitalmars.com> Jun 16 2001
- Jan Knepper <jan smartsoft.cc> Jun 16 2001
- "Kar Gay Lim" <kagay kimay.net> Jun 16 2001
Hi to all on the group ! Back in 1990 I used Zortech C++ and the DOSX extender when writing an application for controlling ATE equipment. I had a lot of trouble in debugging it because the Zortech debugger would not work with DOSX programs. Guess what - I now have to add new features to that application, just when I'd forgotten all about it ! I thought Zortech C++ was dead and buried, so you can imagine my excitement when I accidentally found the DigitalMars website ! So back to my question - is it now possible to use the debugger to debug 32X programs ? Any help and advice gratefully received. TIA. A message for Walter: Hi Walter ! Seeing your name in this newsgroup brought back many memories - I'd seen your name so many times before in the header files and sample code supplied with the Zortech compiler, that it was almost like meeting a long-lost friend ! It's good to know that you're still around ! :-) Regards to all, Jurek
Jun 16 2001
I'm still around and still doing compilers! The debugger still doesn't support DOSX. The solutions are: 1) bug Doug Huffman for the DOSX debugger 2) debug the program as a win32 console app, then port it to DOSX 3) debug with printf <g>. Sorry! Jurek Wozniak wrote in message <9gf81j$20bq$1 digitaldaemon.com>...Hi to all on the group ! Back in 1990 I used Zortech C++ and the DOSX extender when writing an application for controlling ATE equipment. I had a lot of trouble in debugging it because the Zortech debugger would not work with DOSX
Guess what - I now have to add new features to that application, just when I'd forgotten all about it ! I thought Zortech C++ was dead and buried,
you can imagine my excitement when I accidentally found the DigitalMars website ! So back to my question - is it now possible to use the debugger to debug 32X programs ? Any help and advice gratefully received. TIA. A message for Walter: Hi Walter ! Seeing your name in this newsgroup brought back many memories - I'd seen your name so many times before in the header files and sample code supplied with the Zortech compiler, that it
almost like meeting a long-lost friend ! It's good to know that you're still around ! :-) Regards to all, Jurek
Jun 16 2001
Walter wrote:The debugger still doesn't support DOSX. The solutions are: 1) bug Doug Huffman for the DOSX debugger 2) debug the program as a win32 console app, then port it to DOSX 3) debug with printf <g>.
Thanks for the info, Walter. Option 1 - I'm still a newbie on this newsgroup. Who is Doug Huffman ? Option 2 - Despite a programming career of over 25 years, I have still never written a Windows application! No-one ever offered me money to write one, and though I was tempted to write one for my own self-education, you know what it's like when you write code for a living - the last thing you want to do when you get home is to turn the computer on ! :-) The main part of my application runs in real-time, accesses the I/O ports directly, and uses memory mapped I/O, so I guess it would be very difficult (if not impossible) to get it to run satisfactorily under Windows. However, a subsidiary program is just a compiler which translates a verbose ATE test programming language into a compact set of instructions, which are then executed by the real-time application. I'd like to have a go at trying your suggestion on this program. So, how easy is it to convert an existing DOSX application to run as a win32 console app, and then to port it back to DOSX ? I'd appreciate a summary of the steps required to do this, and any pitfalls to watch out for. Option 3 - Ahh, good old "printf" - anyone who hasn't had to resort to this method at some point, isn't a true programmer !! :-) Jurek.
Jun 17 2001
"Walter" <walter digitalmars.com> Doug Huffman wrote the DOSX extender. His colleague, Phil Murray, wrote the DOSX debugger. Doug can be reached at www.dosextender.com. A win32 console app you should find very familiar. It isn't a gui, has no graphical interface, you just run it from the command line like a DOS app. Jurek Wozniak wrote in message <9ghubh$dsr$1 digitaldaemon.com>...Walter wrote:The debugger still doesn't support DOSX. The solutions are: 1) bug Doug Huffman for the DOSX debugger 2) debug the program as a win32 console app, then port it to DOSX 3) debug with printf <g>.
Thanks for the info, Walter. Option 1 - I'm still a newbie on this newsgroup. Who is Doug Huffman ? Option 2 - Despite a programming career of over 25 years, I have still
written a Windows application! No-one ever offered me money to write one, and though I was tempted to
one for my own self-education, you know what it's like when you write code for a living - the last thing you want to do when you get home is to turn the computer on ! :-) The main part of my application runs in real-time, accesses the I/O ports directly, and uses memory mapped I/O, so I guess it would be very difficult (if not impossible) to get it to run satisfactorily under Windows. However, a subsidiary program is just a compiler which translates a verbose ATE test programming language into a compact set of instructions, which are then executed by the real-time application. I'd like to have a go at trying your suggestion on this program. So, how easy is it to convert an existing DOSX application to run as a
console app, and then to port it back to DOSX ? I'd appreciate a summary
the steps required to do this, and any pitfalls to watch out for. Option 3 - Ahh, good old "printf" - anyone who hasn't had to resort to
method at some point, isn't a true programmer !! :-) Jurek.
Jun 17 2001
Walter a écrit :I'm still around and still doing compilers! The debugger still doesn't support DOSX. The solutions are: 1) bug Doug Huffman for the DOSX debugger 2) debug the program as a win32 console app, then port it to DOSX 3) debug with printf <g>.
4) write your code compatible for dos 16 bit and dos 32 bit model as well using macros, debug the 16 bit app with DM C++ 16 bit idde (scwn16.exe or something loke that) and recompile for 32 bit dosx model once 16 bit model app is ok. It's the way i do. (printf too of course..) regards Roland
Jun 19 2001
The Zortech compiler was dead and buried for years. It needed a little "re-animation" <g>. Being back in the business is, for me, like putting on that old green shirt again (you Zortechies know what I mean!). It feels good, and this time around I have no one to answer to other than you guys, the loyal customers. I decided to get back into doing this because, in cruising the net, I discovered that there was quite a lot of talk about the zortech compiler still, after nearly a decade. Having all that latent interest has made for a great kickoff for the Digital Mars compiler. It is deja vu all over again, though, because the same characters who told me I was doomed to failure with zortech are telling me the same with DM. I'll enjoy proving them wrong again! Jurek Wozniak wrote in message <9gf81j$20bq$1 digitaldaemon.com>...Hi to all on the group ! Back in 1990 I used Zortech C++ and the DOSX extender when writing an application for controlling ATE equipment. I had a lot of trouble in debugging it because the Zortech debugger would not work with DOSX
Guess what - I now have to add new features to that application, just when I'd forgotten all about it ! I thought Zortech C++ was dead and buried,
you can imagine my excitement when I accidentally found the DigitalMars website ! So back to my question - is it now possible to use the debugger to debug 32X programs ? Any help and advice gratefully received. TIA. A message for Walter: Hi Walter ! Seeing your name in this newsgroup brought back many memories - I'd seen your name so many times before in the header files and sample code supplied with the Zortech compiler, that it
almost like meeting a long-lost friend ! It's good to know that you're still around ! :-) Regards to all, Jurek
Jun 16 2001
It is deja vu all over again, though, because the same characters who told me I was doomed to failure with zortech are telling me the same with DM. I'll enjoy proving them wrong again!
Yeah! Yeah! Yeah! Yeah!
Jun 16 2001
Symantec had the opportunities to make lots of things successful. They had SC++ and for a while was beating Microsoft with the code quality. At one time when M$ stopped the 16-bit in VC++, the obvious choice for everyone who still have to maintain those tons of legacy code (like up till now with DOSX etc) - SC++ could fill in the void. Unfortunately, trying to go for the mass market and with the addition of Expresso/Cafe, the whole compiler thing became blurred. Visiual Page is another product.... Just look at the scene - Symantec sold the Java products to Webgain and Webgain became more successful than Symantec with the same product. Something is telling us the management at Symantec is not thinking. Jan Knepper <jan smartsoft.cc> wrote in message news:3B2B991E.BAC4BE10 smartsoft.cc...It is deja vu all over again, though, because the same characters who told me I was doomed to failure with zortech are telling me the same with DM. I'll enjoy proving them wrong again!
Yeah! Yeah! Yeah! Yeah!
Jun 16 2001