http://bugs.winehq.org/show_bug.cgi?id=18403
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #1 from Anastasius Focht focht@gmx.net 2009-05-09 07:58:27 --- Hello,
you have .NET 2.0 Framework in your WINEPREFIX, right? Although that message generally harmless (FIXME's are not errors), it is sometimes really annoying (especially when debugging).
When an application installs assemblies into GAC, .NET's native image generator worker service is triggered to compile them to native executables. That usually leads to a flood of:
--- snip --- ... fixme:ntdll:NtPowerInformation Unimplemented NtPowerInformation action: 16 fixme:ntdll:NtPowerInformation Unimplemented NtPowerInformation action: 16 ... --- snip ---
sometimes a long time after the initial install process exited (or on wineboot/restart due to queued work items from previous run)
The ngen service periodically queries all kinds of machine power classes along with other informational requests. Actually I'm not sure about the real purpose of querying all that info, it might be used to determine if the machine is in "idle" state. If the service determined the machine is in "idle" state it might carry out some deferred work to prevent "disturbance" at times when the user is active. On the other side it could be to detect situations when not to run any (cpu intensive) ngen jobs to enhance the run time when low on battery.
I've seen some semi-stub for that power information class a while ago on wine-patches.
MSDN:
http://msdn.microsoft.com/en-us/library/aa372675.aspx (CallNtPowerInformation)
http://msdn.microsoft.com/en-us/library/aa373208.aspx (SetThreadExecutionState)
The fasted way would be just to silence this noisy FIXME with a static variable along with "SystemExecutionState" class separated from other unimpl. classes (prevent hiding of other unimpl. class FIXME's).
Regards