🚀 go-pugleaf

In article <5270@crash.cts.com> alen@crash.cts.com (Alen Shapiro) writes:
>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!!
>
>nmake when run from a DOS-PROMPT within windows 3.0, hangs
>my PS2/80 (4Mb RAM DOS3.3).

Are you sure that this has anything to do with Windows?  It's most likely
that losing the few K that Windows steals from each DOS session is enough
to push you over the edge into not having enough memory to use NMAKE.
Even if I'm *not* running Windows, my 3+Open network drivers alone take
up enough RAM to prevent me running NMAKE and the compiler simultaneously.

(Incidentally, NMAKE and C 6.0 will work fine under Windows if you have
almost no TSRs or drivers loaded.  I've done it before.)

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

Don't call it an SDK question.  Call it a C 6.0 question, since it'll
happen whether you're compiling a Windows app or not.  Of course, they
still probably won't be able to help you.

>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!!

Better idea:  I don't recall if C 6.0 comes with MAKE or not, but if
so, use it instead.  If you have a previous version of MSC, it'll have
MAKE with it.  (I think MASM comes with it too.)  Alternatively, get
one of the many alternative PD/shareware/commercial make-like programs.

I don't understand why the NMAKE executable had to be so much larger
than MAKE.  We can hope that in 6.1 they'll manage to trim it down a bit.

-- 
Jim Seidman (Drax), the accidental engineer.
"There's a certain freedom to being completely screwed." - The Freshman
UUCP: ames!vsi1!hsv3!jls	      Internet: hsv3.UUCP!jls@apple.com