- May
- 12,622
- 152
On Wed, 25 May 2011 22:25:06 -0400, Steve Fabian <> wrote:
|Sorry, executing TCCBATCH.BTM (or any of the TC*HERE.BTM files) is NOT part of the installation process. They are executed by the just-installed TCC.EXE. That's why the UNINSTALLER cannot remove their effects. Maybe a version of the batch file in C. Dye's response to this post should be included with the TCMD distribution (and also UNDO versions of the TC*HERE.BTM files).
That could be easily added as an option in TCCBATCH.BTM. TCC doesn't monkey
with batfile or cmdfile; it only points .bat and .cmd elsewhere. It should only
be necessary to ASSOC them back. You can leave the TCC.Batch file type there
(possibly for future use) ... I doubt any other app will use it (and leaving
file types and classes (and more) lying around the registry seems to be the
uninstall paradigm!).
|Sorry, executing TCCBATCH.BTM (or any of the TC*HERE.BTM files) is NOT part of the installation process. They are executed by the just-installed TCC.EXE. That's why the UNINSTALLER cannot remove their effects. Maybe a version of the batch file in C. Dye's response to this post should be included with the TCMD distribution (and also UNDO versions of the TC*HERE.BTM files).
That could be easily added as an option in TCCBATCH.BTM. TCC doesn't monkey
with batfile or cmdfile; it only points .bat and .cmd elsewhere. It should only
be necessary to ASSOC them back. You can leave the TCC.Batch file type there
(possibly for future use) ... I doubt any other app will use it (and leaving
file types and classes (and more) lying around the registry seems to be the
uninstall paradigm!).