Glad you got it working now!
Actually after I made that last post, I got what I think was the exact same error you mentioned when I shut down SetKeys. I had made several "nested" folders and put Commands.cfg at the bottom level, opened it, made a change and saved, to see if maybe the depth of folders had something to do with it. Worked fine, so I deleted the folders I'd set up. Then, when I quit SetKeys it popped up an error dialog complaining about a missing path, was like 8 or 10 lines long. Bet it was the same error you saw
So, I'm wondering if you accidentally deleted something SetKeys expected to see, before you saved?
BTW, my experience is that
SetKeys makes the Commands_en.bak when you save. It's a backup of the original file in case your mods don't work. You can just rename it and undo your changes. Shouldn't be necessary for you to create it yourself to make SetKeys save your changes!
OK, now that you've got it working all you need to do is open your
edited copy in one text editor, and your
live file in another. Then for each command you mapped to a key, copy the new "Key0=" line from the edited file, and paste it into the live file as the last line for the relevant command. Then save, and you should be able to use the new keymap to execute the command!
One thing to keep in mind is, if you add a mod that affects Commands.cfg it will blow away all your hard work. I
always replace the mod's Commands.cfg with my custom one before installing the mod. That way I can keep my keymap! If there are newly-mapped keys in the mod that I want, I add them to my Commands.cfg before I do that, that way I get the best of both worlds.
Good luck, hope you get it working like you want - that voice recog absolutely rules! I use Shoot! and won't think of playing without it
DH