Well you can see faq329-3578 for a link to a Microsoft page that itself has both the scripting documentation (see the WSH doc for the most comprehensive info) and the Script Encoder. The Script Encoder documentation is part of the downloadable CHM file at the link in that FAQ.
Keep in mind that this form of script obfuscation is not highly secure. Some deviants have posted tools for reversing it at various places on the web.
It is the only common one available though.
I'm using other techniques myself. But since they are messy, have some disadvantages, and offer only a marginal advantage in resistance to breakage anyway - there is no point in disclosing them here.
Even encapsulating critical or sensitive code as a compiled DLL has its drawbacks. For one, a big plus with HTAs is the lack of a need for the full installation and registration of components. For another, depending on how you wrote/compiled these DLLs/OCXs you might need to supply bulky runtime DLLs along with them.
Script Encoder may be perfect for you if you just want to discourage casual tinkering.
