Re: Replacing XP Notepad under SP2?

From: george (anonymous_at_discussions.microsoft.com)
Date: 02/25/05


Date: Fri, 25 Feb 2005 20:43:26 +0100


"cmsix" <cmsix@cmsix.com> wrote in message
news:OCuq1btGFHA.1392@TK2MSFTNGP10.phx.gbl...
>
> "cmsix" <cmsix@cmsix.com> wrote in message
> news:ufBdfVtGFHA.2156@TK2MSFTNGP09.phx.gbl...
>>
>> "george" <anonymous@discussions.microsoft.com> wrote in message
>> news:eAE8mhpEFHA.3780@TK2MSFTNGP09.phx.gbl...
>>> You are experiencing the 'self-healing' capabilities of Windows XP.
>>> (Nothing to do with SP2 for that matter)
>>> Whenever XP detects that (according to MS) 'vital' system files are
>>> replaced by 'whatever' it automatically puts back the original version
>>> of that file in it's rightfull place in the system. (This happens
>>> virtually instantaneously).
>>> Notepad is considered one such file.
>>> XP has a hidden folder called \system32\dllcache (anywhare from 230-250
>>> MB and up in size) containing copies of all those 'vital' files and
>>> serving them up when needed.
>>> So at the very least you would have replace both copies in order to get
>>> 'your' version of the truth.
>>
>> I am having the same problem, trying to replace notepad.exe with a
>> different text editor, the one I like will read the text to me with a
>> text to speech engine. The thing is, I already knew about the dllcache -
>> I searched for all copies of notepad.exe on the local drive and deleted
>> them all. I turned on advanced options, told search to look in system
>> folders and to search hidden files and folders and subfolders. I deleted
>> anyfile that had "notepad" in it but after replacing notepad, the old
>> version still comes back in seconds.
>>
>> This is a fresh install of xp pro sp1. I can't figure out where it is
>> copying the file from and I'd really like to get rid of it. If anyone has
>> a clue, please speak up.
>
> Nevermind, I fixed it by sending my file to the dllcache. XP then did the
> replacement for me. I still can't figure out where it was getting the
> original notepad.exe when I was trying to delete them all.
>
> cmsix
>
Maybe from the install location, if you happen to havedone the install from
a copy of i386 held on your harddisk.
SFC (System File Checker) 'knows' about the originating location and would
be capable of 'healing' from there.

george



Relevant Pages

  • Re: New SBS2003 setup quagmire
    ... Please feel free to use this newsgroup. ... This newsgroup only focuses on SBS technical issues. ... Adding my users went without a hitch and the respective folders ... |> SBS CD1 is installed stop the install temporarily and format the D drive ...
    (microsoft.public.windows.server.sbs)
  • Re: Why New Installs Not Accessible for *All* Users?
    ... Am I doing something wrong when I install? ... sections of the Windows registry or protected Windows system folders. ... limited accounts, you can fix it to allow limited users to access the ...
    (microsoft.public.windowsxp.general)
  • Re: update troubles
    ... ACAD program seems to be compatible since a few folders and the data inside ... It's possible that your ACAD program is not compatible with IE8. ... Customers must be running Windows XP or Windows Vista in a non-domain ... to install IE8, ...
    (microsoft.public.windowsxp.general)
  • Update: A three hour tour....a three hour tour.....
    ... PC2 has folders on a second drive shared with Everyone having full control ... When I install NOD32 or AVG things go all to hell. ... PC1 cannot access any shared folders on PC2. ... I called Eset at 1-619-876-5400 after not hearing ANYTHING from their email ...
    (microsoft.public.windowsxp.general)
  • Re: Why New Installs Not Accessible for *All* Users?
    ... Am I doing something wrong when I install? ... Quite simply, the application doesn't "know" how to handle individual user profiles with differing security permissions levels, or the application is designed to make to make changes to "off-limits" sections of the Windows registry or protected Windows system folders. ... limited accounts, you can fix it to allow limited users to access the ...
    (microsoft.public.windowsxp.general)