Slic3r-console: saving problem where value might be "yes" or "no"

Hi All.
Sorry for my English.
I have problem with slic3r-console.exe on Windows 8. I want to save config file with my params. Problem with values where need "yes" or "no". For example: I want to turn on cooling:
in cmd:

slic3r-console.exe --cooling yes --save config.ini

it works well. In config file value becomes equal 1. But when I want to turn off cooling:

slic3r-console.exe --cooling no --save config.ini

It doesn't work. In config value not changes. Why?
Slic3r version is 1.1.7 stable.

Edited 1 time(s). Last edit at 09/07/2014 05:24AM by Boomerang.

"config.exe"? Was that supposed to be "config.ini"?

Quote
DeepSOIC
Was that supposed to be "config.ini"?

Oh, sorry. Yes, config.ini.

Edited 1 time(s). Last edit at 09/07/2014 03:57AM by Boomerang.

No one had this problem?

Have you successfully saved with other settings changed? Is this specific to "yes/no" options? Is the file being written at all, or is there a chance that it is writing the config.ini to another location?

Quote
anXofY
Have you successfully saved with other settings changed?

Yes. Any settings with numeric value.

Quote
anXofY
Is the file being written at all, or is there a chance that it is writing the config.ini to another location?

No. I checked this many times. Other parameters are written succesfully. But parameter described above just leaves no changes.
For example, config contains parameter:
avoid_crossing_perimeters = 0

This command:
slic3r-console.exe --avoid_crossing_perimeters yes --save config.ini
works. Now config.ini contains:
avoid_crossing_perimeters = 1
slic3r-console.exe --avoid_crossing_perimeters no --save config.ini
not works.
Config.ini still contains: avoid_crossing_perimeters = 1

With previous versions of Slic3r I found that settings sometimes did not "take" and I had to change them a few times (and sometimes together with other parameters). Try changing the setting as well as other related settings, saving, re-loading and if it has not "taken" change again and re-save. When it saves correctly change back the other settings you changed and re-save (then re-load to check). I sometimes had to fiddle several timers to get a good save.

Dave