Wow - that's definitely weird. Based on the error message (really long, but dealt with not being able to find part of the path blah blah blah...), I was able to figure out that in addition to renaming the commands file to commands_en.cfg and putting the renamed commands file in the same folder as SetKey is in, you also have to create a copy of the commands file in that same folder and call it "commands_en.bak".
Once that was done, SetKey saved the changes down just fine, without error messages.
Now, just have to compare the changed file to the old one and see if it made all the changes I asked it to without breaking something inside the file.
[EDIT] Good suggestion to just find the specific commands that got changed and then paste the new key lines into a clean copy of the SH4 commands.cfg file, because SetKey really does screw up/change a bunch of unintended stuff inside that file when it's doing its thing. However, just pasting in to a clean copy only the changed key line in the specific commands you know you changed worked just fine. I was able to map a key to "get depth below sub keel" and use the key in game just fine.
(Note for those interested - there is also a command called "report depth below keel" or something like that. I tried that first, but while the mapping worked and the key called up a report in game, the answer was always wrong - it always said depth below keel was 0. So you need to use the one that starts with "get" - using the key mapped to that command brought back the same answer that clicking the depth-below-keel button did.)
Now to map the other commands and get them entered into the speech recognition program files, then it's out to sea again
