I'm going to have to disagree with at least one point:

As long as VarsInStrings' default is to allow the behavior, I contend that it *IS* a matter of style. I'm well aware of situations where this can cause a function to fail, and I'm well aware of the pros and cons of not doing it.

Also, I'm not sure how to make any clearer that I understand the suggestions that you're making. I'm well aware that I have an additional variable that needs localized and Redirect that needs fixed. I don't take any issue with adding a piece of $exedir logic to this (and future scripts) -- BUT, this script, because of it's purpose, will probably always write log files, and will probably, for my sanity alone, always include vars in strings. Perhaps I'll just start including bastardized headers and footers.

Quote:

Tough croud huh? Give 'em an inch and they want a mile!

Actually, yeah. This is a pretty useful script. In the example above, it's probably easier to adjust the ProxyByUser/ProxyByMachine policy bit, lacking a policy bit, or the ability to move things into HKCM and have them work, writing to all HKUs is quite valuable.