Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!princeton!udel!gatech!bloom-beacon!tut.cis.ohio-state.edu!mailrus!iuvax!pur-ee!a.cs.uiuc.edu!uxc.cso.uiuc.edu!uxe.cso.uiuc.edu!mcdonald
From: mcdonald@uxe.cso.uiuc.edu.UUCP
Newsgroups: comp.windows.misc
Subject: Re: Compiling under Windows
Message-ID: <68600009@uxe.cso.uiuc.edu>
Date: 30 Jun 88 23:29:00 GMT
References: <152@pt1.Wichita.NCR.COM>
Lines: 21
Nf-ID: #R:pt1.Wichita.NCR.COM:152:uxe.cso.uiuc.edu:68600009:000:1164
Nf-From: uxe.cso.uiuc.edu!mcdonald    Jun 30 18:29:00 1988


>This seems awfully basic, but does anyone actually compile and link their
>Windows applications under Windows?  I haven't been able to determine the 
>right combination of PIF files and/or whatever else is needed.  Is this
>documented in the SDK manuals?

Probably not, unless they have a 386 with mucho megabytes and Windows
386. I do, and it works fine if you set up a command.com PIF with "exclusive"
and say 530 kbytes. You get in that screen (it isn't a window) and work
as usual. Compilers and linkers seem to work OK in windowed command.com's.
Be sure to get your path and environment variables right before entering
Windows.  I tried to use regular Windows on my 386, using a RAMdisk for
swapping, before I got the Windows 386. It was a disaster. Too slow. 
I have also used Desqview 386 for compiling, and try my final files
in regular Windows run as a task under Desqview. This also works just
fine. In fact, it is better because frequently (but not always) when
my Windows program dies, taking Windows along with it, Desqview survives,
and I don't have to reboot. In general, though, I just use regular DOS.
None of this is documented.

Doug McDonald