When beginning a new session with START the new TCC instance is initialized with the TCMD.INI found during the standard search process as documented.
I use non-default ini-files to kick-off shells that are specialized for certain (groups of) purposes.
If the first process was started with an inifile with a non-default name and/or from a non-default location, those setting will not be found or be eclipsed by other existing standard inifiles. In that case the new shell is not initialized...
Read more
I use non-default ini-files to kick-off shells that are specialized for certain (groups of) purposes.
If the first process was started with an inifile with a non-default name and/or from a non-default location, those setting will not be found or be eclipsed by other existing standard inifiles. In that case the new shell is not initialized...
Read more