Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!microsoft!kensy
From: kensy@microsoft.UUCP (Ken SYKES)
Newsgroups: comp.windows.ms
Subject: Re: Pleasures and Penanties of the Large Model
Message-ID: <57229@microsoft.UUCP>
Date: 6 Sep 90 21:09:45 GMT
References: <82934@aerospace.AERO.ORG>
Reply-To: kensy@microsoft.UUCP (Ken SYKES)
Organization: Microsoft Corp., Redmond WA
Lines: 18

In article <82934@aerospace.AERO.ORG> slewis@aerospace.aero.org () writes:
>	If I have a well behaved application which requires say about 10K of
>local storage and 200K global storage which it manages with the GlobalAlloc
>mechanism, is there any real penalty in specifying the large model and buying
>a great simplification on my pointer management???

You won't be able to run multiple instances of your program, and if you
leave the malloc() and other C runtime memory functions as is the memory is not
only FIXED but PAGE LOCKED as well.  This is a very bad thing - page locked
means it can't be swapped to disk which means you will be confined to 
physical memory.  If you use GlobalAlloc to allocate moveable memory then
immediately lock it down you can get memory that is FIXED but not page 
locked.  My suggestion is to write it in small or medium model and replace
the pointers with far pointers.  This will make it a more friendly windows
app.

Ken Sykes
Disclaimer: The above opinions are solely my own.