delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2000/04/03/12:33:31

Message-Id: <200004031633.MAA21665@delorie.com>
Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: "Parker, Ron" <rdparker AT butlermfg DOT com>
To: Matt <matt AT use DOT net>
Cc: "'cygwin-developers AT sourceware DOT cygnus DOT com'"
<cygwin-developers AT sourceware DOT cygnus DOT com>
Subject: RE: Known DLLS (Was: Mo Dejong's install problems)
Date: Mon, 3 Apr 2000 11:29:09 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)

> From: Matt [mailto:matt AT use DOT net]

> On Fri, 31 Mar 2000, Parker, Ron wrote:
> 
> > > -----Original Message-----
> > > From: Mumit Khan [mailto:khan AT NanoTech DOT Wisc DOT EDU]
> > <snip>
> > 
> > > A long time ago, I added Cygwin dll to the "Known DLLs" list, 
> > > but I don't
> > > remember if I saw any significant improvements. 
> > 
> > <snip>
> > 
> > FWIW, Microsoft added a new "feature" to "Known DLLs" with 
> Windows 2000. If
> > a file is listed as a "Known DLL" nothing may replace it short of an
> > operating system service pack. If you try replacing it, 
> success will be
> > reported but nothing will be changed. Microsoft will 
> re-replace it with a
> > cached copy that you cannot modify.

<snip>

> What you are referring to in Win2k is "system File 
> Protection". 

<snip>

I read a MS article that implied that a Known DLL is under "System File
Protection", now known as "Windows File Protection".  After performing a
test I determined that it was merely coincidental that all of the default
"Known DLLs" on my machine were under WFP.  Adding a new file to "Known
DLLs" does not cause it to be WFP'd.  Please ignore my original post. :^)

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019