Miscellaneous > 16 bit DOS Programming

Debugger?

<< < (3/3)

FORTRANS:
Hi,

   Just wanted to say I found the error.  Or at least an error, EAX
should have been EDX on one line.  And it solved the test puzzle.  Now
to yank out all the superfluous debugging and diagnostic code wedged
into the program.  And while debugging, I crashed the OS/2 VDM, which
should be looked into, if possible.

   Thanks to all who helped out or made suggestions!

Cheers,

Steve N.
   

FORTRANS:
Hi,

   Shintaro and TimoVJL pointed out links to versions of CodeView that I
downloaded and tried out.  Thanks to both of you.

   The link Shintaro used was easier to unpack and investigate.  The program
ran in a Windows NTVDM and is a menu driven debugger.  Unfortunately
it crashes in an OS/2 VDM.  (Where I had everything set up.)

   TimoVJL's link was a bit harder to figure out due to Google searches and
Windows behavior adding up to misleading information.  But when the
program was successfully unpacked, it does work.  A somewhat older version
than the one from Shintaro.  Back to Google I suppose to find out how to
use Codeview.

   As _japheth's debugger solved the immediate problem, this will
undoubtedly be a rather slow process at best.  Oh well.

   Thanks again to all who responded.

Regards,

Steve N.

Shintaro:

--- Quote from: FORTRANS on November 07, 2022, 12:04:42 AM ---
Unfortunately it crashes in an OS/2 VDM.  (Where I had everything set up.)


--- End quote ---
OS/2 VDM?? Are you running an old version of Windows NT or OS/2 Warp?

FORTRANS:
Hi,


--- Quote from: Shintaro on November 07, 2022, 08:41:59 AM ---
--- Quote from: FORTRANS on November 07, 2022, 12:04:42 AM ---
Unfortunately it crashes in an OS/2 VDM.  (Where I had everything set up.)


--- End quote ---
OS/2 VDM?? Are you running an old version of Windows NT or OS/2 Warp?

--- End quote ---

   Well, one machine is set up for a dual boot of Windows 2000 and OS/2 4.0.
That is set up for program development, games, forum access, and problem
research (playing with algorithms and such).  Another is Windows XP, used for
playing DVDs mostly.  Another is Windows 8.1, which did the downloads, Google
searches, my e-mail, and is used when "modern" software is needed.

   Others in intermittent use run all sorts of things, unless they have recently
died, Win 10 (boots up for updates), eCs (OS/2 follow-on), and some others.
I think the last Win 98 has died.  The Win 3.11 fW is disconnected, and so forth.
Another dual boot has problems and was never used much anyway.  And some
MS-DOS 80186 palmtops might still be working, haven't looked for a while.

   If you get involved with computers and have a hard time throwing stuff out
you end up with a lot of stuff, mostly inert.  Need a dead PC/AT?

Cheers,

Steve N.

Shintaro:
You could try Borland Turbo Debugger from that era, HERE
Books on TD are HERE on the Internet Archive.
There is also the OS/2 SDK HERE. Not sure if you already have that. It might have some tools or information that helps.

Yea, my family think I am a hoarder, but I am real happy that I held on to some of the old stuff. I really enjoy messing with the old hardware and software.
I am just a novice at fixing old boards, which is quite satisfying, but I don't have the time.

I mostly run VM's, but that is limited as some code can crash in a VM but work ok on real hardware. One of my current problems is finding a 1GB 2.5 inch disk for my Dell Latitude 610. I am going to use a compact flash card, until a DOM (Disk on Module) arrives. The DOM is better suited to replace a spinning disk.

I have 486 VLB waiting for a case. I just can't seem to find a case that I like, locally.

Navigation

[0] Message Index

[*] Previous page

Go to full version