Path: utzoo!attcan!uunet!sjsca4!poffen
From: poffen@sj.ate.slb.com (Russell Poffenberger)
Newsgroups: comp.windows.ms
Subject: Re: MS has NO free support for new SDK
Keywords: SDK Windows
Message-ID: <1990Oct1.164153.11563@sj.ate.slb.com>
Date: 1 Oct 90 16:41:53 GMT
References: <37745@ut-emx.uucp> <1990Sep28.180704.17439@wrl.dec.com>
Reply-To: poffen@sj.ate.slb.com (Russell Poffenberger)
Organization: Schlumberger Technologies, San Jose, CA.
Lines: 38

In article <1990Sep28.180704.17439@wrl.dec.com> leadfoot@leftlane.ucs.dec.com (Mark Curtis) writes:
>I use picked up the 3.0 SDK, and I have already run into this problem.
>It's very hard to get questions answered, even simple setup questions.
>
>I haven't loaded the software on my system yet, because I'm not sure
>I'm going to keep it.  While in the store I didn't notice that I needed a
>second monitor to use the debugger.  I am using a PS2 system that
>only has 1 full size slot and one half size slot, a P70.  The full size
>slot is already used for a dual async board, so adding another video
>card is impossible.  I also don't look forward to picking up a 8514
>card and another monitor $$$$.  I do have one serial port COM3 free
>to use with a dumb term, but from what I have seen this will not
>cut it.  Is Windows Code View the only debugger that is usable?  Or
>will I be able to still get real work done with what ever else comes
>with SDK?  I haven't loaded the software yet, I didn't want to open
>all the packing if it wasn't going to be useable.
>
>Second, how much disk space do I need to install SDK?

You need a second monitor to succesfully use any of the debuggers provided.

Think about it, when debugging windows, the debugger takes over the entire
windows kernel. That being the case, output to the windows screen is not
possible.

I don't know what you mean about the 8514, the second monitor only needs to be
a simple monochrome monitor. I got a half card mono adapter card for $39, and
a used mono monitor for $49 from a surplus store near here. It works great.

Even if you don't have the monitor, you can still do debugging (sort of) by
outputting messages to the screen (using TextOut) or popping up MessageBox'es
with info at various places in your program. Not as thorough, but it can help.


Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies       UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110             (408)437-5254