From: chepelov@rip.ens-cachan.fr ("Cyrille Chépélov") Subject: Re: DLL Data and Copy-on-write (was RE: Why is cygwin.dll?) 20 Jan 1997 17:19:28 -0800 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <199701202230.XAA03979.cygnus.gnu-win32@nemo.rip.ens-cachan.fr> Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Original-To: "Colin Peters" Original-Cc: "'GNU-Win32'" X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1160 Original-Sender: owner-gnu-win32@cygnus.com Colin, > "When an EXE or a DLL file is loaded from a floppy disk, both > Windows 95 and Windows NT allocate storage for the entire > file from the system's paging file. [snip]" > In other words a large DLL does in fact use virtual memory even if > you don't ever call any of it's functions. This does not, however, > eliminate your point as far as physical RAM is concerned (only as > much as is needed is swapped in). Did he really say "floppy" ? NT, by design, severely distrusts small removable disks (ie floppies). But what does Richter say about NT's behavior on DLL stored on hard disks ? I have always heard that NT's way of handling MapViewOfFile etc.. was to simply "merge" the files to the paging file, with a read-only or "write-only-by-this-process" flag. -- Cyrille - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".