Known DLLS (Was: Mo Dejong's install problems)

Parker, Ron rdparker@butlermfg.com
Mon Apr 3 09:32:00 GMT 2000


> From: Matt [ mailto:matt@use.net ]

> On Fri, 31 Mar 2000, Parker, Ron wrote:
> 
> > > -----Original Message-----
> > > From: Mumit Khan [ mailto:khan@NanoTech.Wisc.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. :^)


More information about the Cygwin-developers mailing list