Xref: utzoo comp.lang.c:12263 comp.windows.misc:658
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!apple!voder!kontron!optilink!cramer
From: cramer@optilink.UUCP (Clayton Cramer)
Newsgroups: comp.lang.c,comp.windows.misc
Subject: Re: Mysteries of Microsoft Windows and C
Keywords: Microsoft, C, Windows, MSC, Bugs
Message-ID: <428@optilink.UUCP>
Date: 31 Aug 88 18:34:05 GMT
References: <7050@umn-cs.cs.umn.edu> <390@infmx.UUCP>
Organization: Optilink Corporation, Petaluma, CA
Lines: 15

In article <390@infmx.UUCP>, greggy@infmx.UUCP (greg yachuk) writes:
> In article <7050@umn-cs.cs.umn.edu> kehyoe@umn-cs.cs.umn.edu (Ong Keh Yoe) writes:
> You cannot use Codeview to debug a Windows program (something about
> competing for the screen was the pseudo-explanation that I got from MS).
> You must use SYMDEB, with either a second monitor, or with a terminal
> hanging from the COM1 port.  The documentation for Windows 1.04 gives
> an example of using COM2, but this hangs the system.  I don't know if
> they corrected it for 2.0x.  You MUST use COM1.

Time marches on.  The most recent issue of MSJ mentions that a special
version of CodeView is now (or soon) available to debug Windows apps.

I haven't used it, so I don't know how good a job it does.

Clayton E. Cramer