From:	jjf AT dsbc DOT icl DOT co DOT 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 DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199701210106.21327.0.cygnus.gnu-win32@dsbc.icl.co.uk>
Original-To:	colin AT bird DOT fu DOT is DOT saga-u DOT ac DOT jp (Colin Peters)
Original-Cc:	flitterio AT amulet DOT com, gnu-win32 AT cygnus DOT 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]
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

> From: Colin Peters <colin AT bird DOT fu DOT is DOT saga-u DOT ac DOT jp>
> 
> 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 AT cygnus DOT com" with one line of text: "help".

- Raw text -