Well, the reason I’m doing this is because Steam VR tries to change the power profile. It shouldn’t, but good luck trying to get Valve to change this.
So, I want to be able to make Wine/Crossover not throw an exception since the power management APIs don’t exist.
Wine shouldn’t (IMHO) actually change the power profiles on its host. It should just respond with the expected query values and any changes to those values should just be an OK (assuming the parameters are correct, then it should throw an error).
On Feb 17, 2025, at 3:51 AM, Stefan Dösinger stefandoesinger@gmail.com wrote:
Am Montag, 17. Februar 2025, 00:45:32 Ostafrikanische Zeit schrieb robert lippmann:
- Default power profiles are stored in the registry under
HKLM\System\CurrentControlSet\Control\Power. The subtree is pretty huge (about a 1.5m .reg file when I exported it.
What's your ultimate goal? I guess you have an application that tries to read and/or change power settings.
If the application is merely reading to e.g. figure out if it is running on a laptop powered by battery you probably don't need most of the registry values,
If you want to make a power management tool work then you are in for a lot of work. Powerprof would have to talk to lower level Linux components to actually apply changes to the hardware settings - that's going to be tricky.