Build 204 of pywin32 has a change so that the working dir
for a service is the folder where its executable is located
instead of \system32, hopefully avoiding trying
to import wmi.dll instead of wmi.pyd.
Roger
Tim Golden [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]
[EMAIL
Tim,
Changing the path didn't do anything, but changing the name of the
module to my_wmi did the trick.
Thanks very much,
Cam.
Tim Golden wrote:
[EMAIL PROTECTED]
| Hi,
|
| When trying to import the WMI module in a Python Windows
| Service, I get
| the following:
|
| dynamic module
[EMAIL PROTECTED]
|
[.. re problems running WMI in a service ...]
| Changing the path didn't do anything, but changing the name of the
| module to my_wmi did the trick.
|
| Thanks very much,
|
| Cam.
|
Thanks for the feedback; I'll try to find the time to
experiment a bit but I know I've
Hi,
When trying to import the WMI module in a Python Windows Service, I get
the following:
dynamic module does not define init function (initwmi)
The WMI version is 0.6. Python 2.4 on Win32, Python Win32 extensions
version 203
Code below,
Cam.
def SvcDoRun(self):
import
[EMAIL PROTECTED]
| Hi,
|
| When trying to import the WMI module in a Python Windows
| Service, I get
| the following:
|
| dynamic module does not define init function (initwmi)
|
| The WMI version is 0.6. Python 2.4 on Win32, Python Win32 extensions
| version 203
This is almost certainly
