Aha...thanks Bob.
I'd actually got around the problem with:
xlapp.ActiveSheet.Shapes.AddOLEObject(Filename=...)
But it's good to know what was wrong.
Mark
-Original Message-
From: Bob Gailer [mailto:[EMAIL PROTECTED]
Sent: 30 October 2006 18:25
To: Mark Norley
Cc: python-win32@python
Hi,
I am trying to get processor performance stats using the pywin32pdh and
pywin32pdhutil modules. It works fine on Windows 2000 and Windows XP, but
not on Windows server 2003(SP1). I am using Python 2.4.3 and
pywin32-210.win32-py2.4.
Error:
--
S.Ramaswamy wrote:
>I am trying to get processor performance stats using the pywin32pdh and
>pywin32pdhutil modules. It works fine on Windows 2000 and Windows XP, but
>not on Windows server 2003(SP1). I am using Python 2.4.3 and
>pywin32-210.win32-py2.4.
>
>Error:
>
At Tuesday 31/10/2006 14:48, Tim Roberts wrote:
>I am trying to get processor performance stats using the pywin32pdh and
>pywin32pdhutil modules. It works fine on Windows 2000 and Windows XP, but
>not on Windows server 2003(SP1). I am using Python 2.4.3 and
>pywin32-210.win32-py2.4.
>
Windows er
> Also, the names are localized, so if you have a non-english version
> of Windows, you have to look up what are the translated names.
> (I don't know how to obtain a "neutral" name usable everywhere)
Although it is far from perfect, the find_pdh_counter_localized_name()
function in win32pdhutil d
At Tuesday 31/10/2006 19:32, Mark Hammond wrote:
> Also, the names are localized, so if you have a non-english version
> of Windows, you have to look up what are the translated names.
> (I don't know how to obtain a "neutral" name usable everywhere)
Although it is far from perfect, the find_pdh
>
> Windows error messages are better handled in hex. -1073738810 is
> CBC6, and a quick Google on that shows it is basically "performance
> counter not found".
>
Thanks for the tip.
> You can use "perfmon" to explore what counters are really present.
> Perhaps the "privileged time" counter
