Yes, that was a typo , I use 'settxfee' and verify it is set via "getwalletinfo" which shows the proper rate.  And it works perfectly for smaller (size) transactions (they use my set fee no problem). I don't use any command line arguments, I don't believe I need to.

Thanks for the wiki info, I've seen it. Was hoping to reach someone who knows the code to see what it's actually doing in this case, and hopefully save people from the same fate in future releases by at least giving a warning should the .1 BTC fee be set overriding their existing setting.