If 16-bit Windows had a single input queue, how did you debug applications?
1–10 of 30 posts
Re: If 16-bit Windows had a single input queue, how did you debug applications?
#2Sounds much more complicated than I remember it. I wrote a game called MVP Backgammon in 1991 using Borland C++ (5.x) and their integrated debugger, and do not recall any specific issues related to input queue deadlocks. You set up your PeekMessage loop or whatever and hung a breakpoint on the switch statement for the message type you needed to debug, and followed it down from there. I assume the debugger was smart enough to run its own PeekMessage loop while waiting for commands.
Re: If 16-bit Windows had a single input queue, how did you debug applications?
#3Sounds much more complicated than I remember it. I wrote a game called MVP Backgammon in 1991 using Borland C++ (5.x) and their integrated debugger, and do not recall any specific issues related to input queue deadlocks. You set up your PeekMessage loop or whatever and hung a breakpoint on the switch statement for the message type you needed to debug, and followed it down from there. I assume the debugger was smart e…
Did you use OWL with BC++? That was so much better than MFC although the non-standard C++ extension was a little unsavory.
I also remember the BC++ debugger being pretty nice although I preferred CodeView.
Re: If 16-bit Windows had a single input queue, how did you debug applications?
#4"How did you debug applications on it? "
With this bad boy:
Re: If 16-bit Windows had a single input queue, how did you debug applications?
#5"How did you debug applications on it? " With this bad boy: http://en.wikipedia.org/wiki/SoftICE
I remember meeting some hackers at their house a friend of mine took me to in the middle of nowhere, and I asked them where they got their software cracks, and they kind of blinked, and showed me the first dual monitor setup I had ever seen in person, with a regular system on the left, and the output of SoftICE on the right. I guess before that I had just assumed lower level things were unknowable, but after that I sure didn't.
Re: If 16-bit Windows had a single input queue, how did you debug applications?
#6"How did you debug applications on it? " With this bad boy: http://en.wikipedia.org/wiki/SoftICE
I remember meeting some hackers at their house a friend of mine took me to in the middle of nowhere, and I asked them where they got their software cracks, and they kind of blinked, and showed me the first dual monitor setup I had ever seen in person, with a regular system on the left, and the output of SoftICE on the right. I guess before that I had just assumed lower level things were unknowable, but after that I s…
Was it the old VGA/Hercules combination? That was so badass
It was also the only way to run dual-screen for a while, since it used a different memory region than colour displays. There was literally no way to run multiple colour adapters on the same computer at one point
Re: If 16-bit Windows had a single input queue, how did you debug applications?
#7Earlier quoted context omitted.
I remember meeting some hackers at their house a friend of mine took me to in the middle of nowhere, and I asked them where they got their software cracks, and they kind of blinked, and showed me the first dual monitor setup I had ever seen in person, with a regular system on the left, and the output of SoftICE on the right. I guess before that I had just assumed lower level things were unknowable, but after that I s…
Was it the old VGA/Hercules combination? That was so badass It was also the only way to run dual-screen for a while, since it used a different memory region than colour displays. There was literally no way to run multiple colour adapters on the same computer at one point
Man I am just not sure. I had a Hercules green screen / more shades than CGA setup myself, but if it helps I do think both of their screens were color. I know Hercules probably did other stuff, but I guess I think monochrome whenever I think about it, heh. I do believe this was the old DOS version, not the Windows version of SoftICE, although when I was over there seemed was just before the time of Windows 95 possibly.
Re: If 16-bit Windows had a single input queue, how did you debug applications?
#8[deleted]
Re: If 16-bit Windows had a single input queue, how did you debug applications?
#9http://blogs.msdn.com/b/matt_pietrek/archive/2005/02/14/3724...
I am surprised Raymond did not mention it.
Re: If 16-bit Windows had a single input queue, how did you debug applications?
#10Sounds much more complicated than I remember it. I wrote a game called MVP Backgammon in 1991 using Borland C++ (5.x) and their integrated debugger, and do not recall any specific issues related to input queue deadlocks. You set up your PeekMessage loop or whatever and hung a breakpoint on the switch statement for the message type you needed to debug, and followed it down from there. I assume the debugger was smart e…
Did you use OWL with BC++? That was so much better than MFC although the non-standard C++ extension was a little unsavory. I also remember the BC++ debugger being pretty nice although I preferred CodeView.
+1 for OWL. It was my first "real" C++ framework, and it was a great way to start.
Borland had a nice tool suite but somehow just couldn't hang on to market share.