From: jjf@dsbc.icl.co.uk (J.J.Farrell) Subject: Re: DLL Data and Copy-on-write (was RE: Why is cygwin.dll?) 20 Jan 1997 20:28:10 -0800 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <199701210106.21327.0.cygnus.gnu-win32@dsbc.icl.co.uk> Content-Type: text Original-To: colin@bird.fu.is.saga-u.ac.jp (Colin Peters) Original-Cc: flitterio@amulet.com, gnu-win32@cygnus.com In-Reply-To: <01BC06F2.09F5FEA0@gbird0> from "Colin Peters" at Jan 20, 97 04:50:12 pm X-Mailer: ELM [version 2.4 PL23] Content-Length: 686 Original-Sender: owner-gnu-win32@cygnus.com > From: Colin Peters > > By the way, from another part of Advanced Windows by Jeffery Richter > (Microsoft Press): > > "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. The system then copies the > file from the floppy into the system's RAM and the system's > paging file; the paging file is said to back the RAM." > > In other words a large DLL does in fact use virtual memory even if > you don't ever call any of it's functions. Hmmm ... how often do you expect to use programs which load cygwin32.dll from a floppy? Regards, jjf - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".