How to install Fujitsu Eco PowerScheme - Lifebook A357?

[DB452]

Dear all,

yesterday I bought a Lifebook A357 without OS. On support page in download section, there is an entry for "Powerscheme: Fujitsu Power Settings".

Screenshot_20181107-143104_Chrome.jpg (758.81 KiB) Viewed 6940 times

The downloaded ZIP-file contains an INI-file, but no instruction how to install or import this scheme to windows 10. Does anybody know what I have to do? Thanks a lot for your replies,

DB452

[me@work]

Strange; when I download the .zip file, I do find an accompanying installation .cmd file "FujitsuEcoSettings.cmd", which subsequently calls a configuration .cmd file EcoPowercfg.cmd to actually implement the power configuration scheme...

Of course, all these command files finally do is to call Windows' powercfg.exe...

[DB452]

I've already executed that .cmd file... But it didn't create a powerscheme called "Fujitsu Computers EcoSettings" (mentioned when you open the .cmd file with notepad). I'm only seeing the powerscheme "Balanced" in windows' energy settings... What did I forget to do?

[me@work]

Sorry, haven't got a test system available currently...

Did you check the log files that (should) get created during the cmds' runtime?
Executed the cmds with elevated privileges?
EDIT: Oh, and you actually did open the list of "Additional Power Plans", didn't you?

[DB452]

Sorry me@work, I'm an absolutely "Greenhorn" with command line parameters. I've figured out myself that I have to copy the content of the downloaded ZIP-file to "c:\" first and then I'm able to execute the cmd. File correctly. Now I have that Fujitsu powerscheme in my battery settings.

Thank you so much for your help!

[me@work]

You're welcome, and I'm glad having been able to suggest.

Though looking at the cmd scripts in the .zip, you don't actually need to copy to "C:\". You may uncompress the .zip anywhere; it's only necessary to re-create the directory structure there with the "scripts" folder.
Anyway, perhaps Fujitsu will finally consider creating either an executable to facilitate the handling, or the instruction file you've missed in the beginning