On 24/06/2011 15:29, Tim Golden wrote:
The __setattr__ logic does involve a certain level of cacheing
and redirection, so there definitely is scope for an error in
the WMI code
... and here I mean "in the code of the wmi.py module" ;)
TJG
___
python-
On 24/06/2011 15:09, Graham Bloice wrote:
On 24/06/2011 14:59, M Saunders TAS wrote:
Graham Bloice wrote:
In the Python call to AddVirtualSystemResources() you've reversed the order of
the parameters.
Additionally the method signature for AddVirtualSystemResources() returns
(Job, NewResou
On 24/06/2011 14:59, M Saunders TAS wrote:
>
> Graham Bloice wrote:
>> In the Python call to AddVirtualSystemResources() you've reversed the order
>> of the parameters.
> Additionally the method signature for AddVirtualSystemResources() returns
>
> (Job, NewResources[], ReturnValue)>
> Which is
Tim Golden wrote:
> Thanks for posting. Nothing's jumping out at me I'm afraid.
I've had another chance to look at this today and have found a workaround using
win32com.client but still cannot figure why it exempts when using the WMI
module.
Using WMI module
HD =
c.Msvm_ResourceAllocationSett
