![]() |
||||
| What is it? | ||||
| This demo application is an example of an automatically generated TPS-Repair tool. It comes with all necessary .DLL-Files and installs in the directory you specify. The application was build with Clarion for Windows 5.5 (f) and our I.Con TPS.repair Template Set, no handcoding, no manual modifications, just the plain template generated application. If you choose to deinstall it, the application and all the files that came with it will be removed from your computer. You can download the demo application at our download area. |
||||
| What does it do? | ||||
| When you start the demo tool, it will scan the provided .TPS-files for corruption. It will find an error in the file named INVHIST.TPS. It will first compress and backup the file and an error log file to a sub-directory. Next it will repair the corrupted file. Finally the keys of all provided .TPS-files will be rebuild. | ||||
| How exactly does it work? | ||||
| The tool uses the TPSFIX.EXE command line interface to scan a .TPS-file. If it finds any errors, a logfile is generated. In this case, the corrupted file is backuped and compressed using a high-speed and fully GZIP compatible deflation algorithm. (Thus the backuped files can easily be restored with e.g. WinZip or ZipMagic). The backups are stored in a unique sub-directory (The name of the subdirectory is build from a date-and-time stamp). Next, an example file is created. Then TPSFIX.EXE is run to repair the corrupted file, using the created example file. This repair work is done in a temporary directory (C:\tmp). When TPSFIX has done its work, the file consistency is being checked again. This is necessary, because sometimes errors in .TPS-files mask each other, so that multiple repair runs are necessary. The repair tool will perform as many check/repair cycles as necessary in order to completely repair the corrupted file (or the user definable retry limit is reached). After all files have been checked, and if errors were found and have been corrected, the key information of the .TPS-files is being rebuild. This is because the TPSFIX.EXE program does intentionally not restore the keys for performance reasons. |
||||