Mark Hammond wrote:
> On Vista, it's necessary to register python COM objects from an "elevated"
> process. In practice, this means I tend to keep a command-prompt open
> started with "run as administrator", do registration and unregistration
> there, then switch back to the normal command-prompt
> From: [EMAIL PROTECTED] [mailto:python-win32-
> [EMAIL PROTECTED] On Behalf Of Tim Roberts
> Sent: Saturday, 19 January 2008 5:02 AM
...
> It is possible (since XP) to register a COM object in
> HKEY_CURRENT_USER\Software\Classes instead of
> HKEY_LOCAL_MACHINE\Software\Classes (which is HKEY_CL
Mark Hammond wrote:
> In your opinion, is my patch an improvement to the status-quo, or does it
> have the potential to cause confusion?
>
I think your patch is probably the right way to go. It solves the
problem for unsophisticated users, and sophisticated users will want to
do their own th
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Mark Hammond
> Sent: Thursday, January 17, 2008 11:10 PM
> To: 'Python-Win32 List'
> Subject: [python-win32] COM registration/unregistration and
> elevation onVista
>
> On Vista, it's necessary to reg
> -Original Message-
> From: MACKEITH Andrew [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 19 January 2008 1:00 AM
> To: Mark Hammond; Python-Win32 List
> Subject: RE: [python-win32] COM registration/unregistration and
> elevation onVista
>
> > -Original Message-
> > From: [EMAIL P
"Mark Hammond" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Vista, it's necessary to register python COM objects from an "elevated"
> process. In practice, this means I tend to keep a command-prompt open
> started with "run as administrator", do registration and unregistration
