[pywin32-bugs] [ pywin32-Bugs-3156202 ] windows script host behaviour changes after pywin32 install

[SourceForge.net <no...@so...>]

Bugs item #3156202, was opened at 2011-01-12 21:48
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3156202&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Cyrille Bollu (cyrillebollu)
Assigned to: Nobody/Anonymous (nobody)
Summary: windows script host behaviour changes after pywin32 install

Initial Comment:
Hi,

This problem has been reported on http://pythonforum.org/topic62-pywin32-and-windows-script-host-problem.html.

I'm experiencing the same problem.

The bug is reproductible (validated with http://surfnet.dl.sourceforge.net/sourceforge/pywin32/pywin32-214.win32-py2.5.exe):

1- take a computer where pywin32 is not installed
2- open a cmd prompt and type "wscript //h:wscript" => you get a prompt telling you that the default script host has been changed
3- install http://surfnet.dl.sourceforge.net/sourceforge/pywin32/pywin32-214.win32-py2.5.exe
4- open a new cmd prompt and type "wscript //h:wscript" => you get "can't change the default script host"

This problem might seem minor but in my company we use this "wscript //h:wscript" command to silently install softwares on client computers. And, when this problem occurs, our silent installation fails.

I will gladly help but I don't have visual studio.

Best regards,

Cyrille



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

>Comment By: Mark Hammond (mhammond)
Date: 2011-01-13 12:15

Message:
In my (limited) testing, I unregistered the AXScript engine (python
...\axscript.py --unregister), which deletes that key and a number of
others, and the problem remains.  I can't verify it ever did work for me
though...

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

Comment By: Christoph Gohlke (cjgohlke)
Date: 2011-01-13 11:26

Message:
Try rename or delete HKEY_CLASSES_ROOT\pysFile

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

Comment By: Mark Hammond (mhammond)
Date: 2011-01-13 09:33

Message:
I can't see how python could manage to do this.  Some googling shows other
people are having a similar issue without Python being installed - I wonder
if the installation of *any* WSH-compatible scripting language is causing
the problem?

> I will gladly help but I don't have visual studio.

You don't need visual studio - running wscript.exe like that shouldn't be
loading Python at all (and certainly can't once it is uninstalled but the
problem remains).  I expect something we write to the registry isn't being
cleaned up or something...

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3156202&group_id=78018