[Python-bugs-list] [ python-Bugs-818029 ] installer wakes up Windows File Protection

[SourceForge.net]

Bugs item #818029, was opened at 2003-10-05 04:49
Message generated for change (Comment added) made by tim_one
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=818029&group_id=5470

Category: Windows
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Pete (thegoldenear)
>Assigned to: Mark Hammond (mhammond)
Summary: installer wakes up Windows File Protection

Initial Comment:
installing Python 2.3.2 on Windows 2000 SP4 induced the

Windows File Protection, presumably bcos an existing

system file had been replaced by an older version

----------------------------------------------------------------------

>Comment By: Tim Peters (tim_one)
Date: 2003-10-06 11:50

Message:
Logged In: YES 
user_id=31435

msvcirt.dll was in the installer when I inherited it from Guido.  

He probably inherited it from Mark (Hammond).  If Mark can't 

remember why it's there either, we should check all the .pyd 

(not just python23.dll) for references to it.  Assigned to Mark.

----------------------------------------------------------------------

Comment By: Thomas Heller (theller)
Date: 2003-10-06 11:38

Message:
Logged In: YES 
user_id=11105

I *can* reproduce it - look into the event viewer, category

'System': File replacement was attempted on the protected

system file d:\winnt\system32\msvcirt.dll...



The windows installer tries (in my case) to replace the

version 6.1.8637.0 with 7.0.2600.0.



Looking at python23.dll's dependencies with Dependency

Walker, it seems that msvcirt.dll isn't required by Python

at all, so the solution would be simple: leave msvcirt.dll

out of the installer.



Why is it in the installer at all? Tim?

----------------------------------------------------------------------

Comment By: logistix (logistix)
Date: 2003-10-05 17:21

Message:
Logged In: YES 
user_id=699438

I couldn't reproduce this on a stock install of W2K SP 4.





If you're in a position to do so (you'll need the physical CD 

media), could you rebuild your DLL cache?  From the 

command-line "sfc /purgecache && sfc /scannow" should do 

this.  After that, try to install python2.3.2 and see if sfc kicks 

in again.



If you can't do that, you might want to see if the file 

python23.dll somehow manually ended up in the %windir%

\system32\dllcache directory.  As far as I know, thats the 

only file that should be getting shoved into an area the sfc 

cares about.

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2003-10-05 14:12

Message:
Logged In: YES 
user_id=31435

Changed category to Windows and assigned to Thomas Heller.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=818029&group_id=5470