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 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 used the change-the-name
trick in the past. It has been suggested that I permanently
change the module name, but I'm a bit loth to do that. Mark
(Hammond) was talking about a patch which would prevent
imports from picking up the false .dll, but I don't know
if it's gone anywhere.
TJG
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+
Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----
--
http://mail.python.org/mailman/listinfo/python-list
