> My apologies for the sarcasm -- this entire thread was driving me nutty. All these complicated, Rube Goldberg approaches without ever trying the simple, obvious one. I can understand why Rex wishes he'd never implemented this feature, or never mentioned it in public. Honestly, guys: was I the only one who tried this documented New Feature during the beta cycle?
>
> I'll post step-by-step instructions sometime in the next few days. There's only one other gotcha I'm aware of. The first time you run your registered TCC-on-a-stick on another machine, you need to run it as administrator; otherwise it can't create registry keys that it needs to create, and you get a confusing error message. (If you're running TCC on someone else's machine, you probably want to run it as administrator anyway, because you're performing black magic and don't want to be hampered by file permissions and the like.)
>
> Otherwise it's all pretty straightforward. Copy your TCStart, .INI file, default alias list, and so on to the stick; then check them and modify as needed. Don't use hard-coded paths in TCStart, aliases, and so on. If you have directives with hard-coded paths in your .INI file, convert them to OPTION commands and move them to TCStart. If you have a toolkit of command-line utilities you want available, copy them to the stick somewhere, and modify the PATH variable accordingly in TCStart.
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Charles Dye