Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!wuarchive!uunet!maverick.ksu.ksu.edu!kitty.ksu.ksu.edu!neil
From: neil@kitty.ksu.ksu.edu (Neil Erdwien)
Newsgroups: comp.windows.ms
Subject: Re: how not to develop in SDK
Keywords: sdk msc 6.0
Message-ID: <1990Oct29.234805.5003@maverick.ksu.ksu.edu>
Date: 29 Oct 90 23:48:05 GMT
References: <5270@crash.cts.com> <1990Oct25.173018.22691@cs.uoregon.edu> <26929@cs.yale.edu>
Sender: news@maverick.ksu.ksu.edu (The News Guru)
Organization: Kansas State University
Lines: 15

In article <26929@cs.yale.edu> spolsky-joel@cs.yale.edu (Joel Spolsky) writes:
>Use "nmk", not "nmake", it takes up a lot less memory.
>

Pre-windows 3.0, I always used nmk rather than nmake.  However, in a window,
nmk always gives me a FILE SHARING VIOLATION after each make.  It also leaves
temporary files in the directory pointed to by TMP.  Nmake works
OK.  Both successfully run the compiler, linker, etc.


--
Neil Erdwien
Kansas State University
neil@ksuvm.ksu.edu