Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!quasi-eli!cs.yale.edu!spolsky-joel
From: spolsky-joel@cs.yale.edu (Joel Spolsky)
Newsgroups: comp.windows.ms
Subject: Re: Windows Virtual Memory???
Message-ID: <26000@cs.yale.edu>
Date: 4 Sep 90 19:51:37 GMT
References: <43727.26e4142e@vaxc.cc.monash.edu.au> <3271@PEDEV.Columbia.NCR.COM> <8698@ccncsu.ColoState.EDU>
Sender: news@cs.yale.edu
Organization: Yale University Computer Science Dept., New Haven, CT 06520-2158
Lines: 21
Nntp-Posting-Host: zoo-gw.cs.yale.edu
Originator: spolsky@suned.CS.Yale.Edu

In article <8698@ccncsu.ColoState.EDU> mcjilton@handel.UUCP (charles mar mcjilton) writes:
>Windows 3.00 is supposed to have virtual memory, but when we compile our
>program using MSC Meduim model, we only have 64K to put all of our data, as
>well as our stack and heap.  We were thinking of going to the Large model,
>but were told that would make the program fixed in memory (due to FAR pointers)
>and it would not be able to swap any part of the program out (including the
>library functions, etc...  That doesn't sound like virtual mamory to me.

First of all, I assume you have a 386, because if you don't, you don't
have virtual memory anyway. Now if you are running in 386 protected
mode, you can either go to large model and not worry about stuff being
fixed in memory (it won't, in enhanced mode) or you could do what the
book recommends and use GlobalAlloc to allocate yourself as much
global memory as you want.

This kind of stuff is really basic Windows stuff; please do take a few
minutes to look over the manuals or Petzold before posting stuff like
this...

Joel Spolsky
spolsky@cs.yale.edu                                        Talk Hard.