This program searches for TA installation folders and tries to identify the exact state by comparing the files in the folders against checksums generated from well defined reference installations. The main purpose of the program is to check out whether the files currently residing in a particular TA folder are consistent with a given version. For example, the program may be helpful to track down the reason why CDE's 3.1c patch installer refuses to apply the patch.
The check process is split into three parts:
modinfosub folder. Every time you click on the
Run Checkbutton the sets are re-loaded from the disk which allows to change/add sets between check runs without re-starting the application.
totala.execan be found in it. The backup folders created by the installers of TA:CC and TA:BT and folders with the system attribute set are excluded from the search process.
On the GUI of the program you have to options to influence the check process:
If an installation fit a set then check it against the remaining sets as well
File missing in set passes check
You can add your own MD5 fingerprint sets (for example generated from your own TA MOD files) by storing a new MD5 set definition text file into the
modinfo sub folder. The file structure is as follows:
modid=<n> modname=<MOD name displayed in GUI> modcomment=<MOD comment displayed in GUI> <filepath 1>+<MD5 fingerprint file1> <filepath 2>+<MD5 fingerprint file2> ... <filepath n>+<MD5 fingerprint filen>
<n>must be unique across all definition files in the
<br>at any position in the
<MOD comment displayed in GUI>value.
modcommentline is followed by one or more lines with filepath/MD5 fingerprint pairs. The
+character serves as field separator.
<filepath >can be a stand alone file name, a relative file path or an absolute file path.
It would be a quite tedious task to generate the MD5 fingerprints for a new file set definition one by one, especially when you had to traverse a folder structure as well. An easy way to create MD5 fingerprints for all files in a folder structure is provided by the tool md5setcheck.exe. Run
md5setcheck.exe in a Windows
cmd.exe shell window without any parameters to make it output its call syntax help info, it should be self explanatory.
TAConsistencyChecker is a Windows GUI application that comes without an installer. You need to copy all files required to run it manually to your computer:
To run TAConsistencyChecker open a Windows File Explorer, navigate to the extraction folder and double click on the
Note that the
MODLOCATOR.DLL must reside in the same folder as
TAConsistencyChecker.exe otherwise the program will refuse to run. Also
TAConsistencyChecker.exe assumes that the MD5 reference set files are to be found in a sub folder named
modinfo. So if you decide to move the DLL and EXE files then move the
modinfo sub folder to the new location as well.
Since the program is supposed to run interactively it doesn't sport any command line parameters right now.
Because the program is an interactive GUI application it doesn't return any meaningful exit codes yet.
The GUI front end
MODLOATOR.DLL are two independent software modules, therefore the version list isn't ordered by versions but build dates.
totala.exefiles any folder (and its sub folders) that can't be accessed for whatever reason is now silently excluded from the search.
MODLOCATOR.DLLcode is executed under has no access rights to no longer causes the front end program
TAConsistencyChecker.exeto abort. A thank you goes to Abimilech who found this bug and was so kind to test the updated DLL version also.