Path: utzoo!attcan!uunet!samsung!dali.cs.montana.edu!milton!oregon!cs.uoregon.edu!akm
From: akm@cs.uoregon.edu (Anant Kartik Mithal)
Newsgroups: comp.windows.ms
Subject: Re: how not to develop in SDK
Summary: I haven't had a problem yet
Keywords: sdk msc 6.0
Message-ID: <1990Oct25.173018.22691@cs.uoregon.edu>
Date: 25 Oct 90 17:30:18 GMT
References: <5270@crash.cts.com>
Sender: news@cs.uoregon.edu (Netnews Owner)
Organization: Department of Computer Science, University of Oregon
Lines: 41

In article <5270@crash.cts.com> alen@crash.cts.com (Alen Shapiro) writes:
>Did you know (and not a lot of people know this :-)) that...
>
>You can't be in the MSWindows 3.0 environment and compile an
>MSC 6.0 program so that you can remain in the environment
>while you compile-debug your windows application (SDK).
>The compiler runs out of heap space!!

This hasn't happened to me as yet, though I will admit that I am still
compiling the sample programs

>nmake when run from a DOS-PROMPT within windows 3.0, hangs
>my PS2/80 (4Mb RAM DOS3.3).

I regularly run nmake, and, as I said before, haven't had a problem
yet. I also run PWB from within windows without a problem. I have a
clone, with 4MB and DOS 3.3. Perhaps it is more compatible??? :-)

>Microsoft will not deal with SDK questions over the phone
>and on-line questions must go through Compuserve :-(

This I agree is lousy policy.

>Looks like I've bought myself a cross compiler and will
>have to run the compiles from another PC (on a shared disk)
>if I intend to remain in windows for testing. WHAT A PAIN!!

>Comments/hints suggestions on the above anyone?

You could run everything in PWB... I'd check things like config.sys,
TSRs and so on first.

kartik



-- 
Anant Kartik Mithal                                     akm@cs.uoregon.edu
Network Manager, 					(503)346-4408 (msgs)
Department of Computer Science,                         (503)346-4156 (direct)
University of Oregon, Eugene, OR 97403-1202