Installation and first run

CheckLog doesn't demand of any special installation/setup program, all the software is delivered in distributive archives (ZIP). To expand files from an archive and place it in a desired folder on a hard disk – still is not a problem. But at once in the course of copying you are convinced that the software doesn't contain viruses and won't break safety of your computer. Simply follow the step-by-step instruction, and everything will be OK. 

For a start download the version you need from the official site. The free trial version consists of the one and only distributive archive. The productive version consists of a Kernel package, and it can extend additional INFO, SYNC packages and others (according to your desire).


Operations:

  1. I create the folder on a hard disk for all the programs, files and folders of a system. For example, the D:\CheckLog folder. I extract files from distributive archive and I place them in this folder. As a result there, at least, there have to be files: CheckLog.exe – itself the executed program code, and two libraries – libeay32.dll and ssleay32.dll. If there is a message of "This application has failed to start because MSVCR71.dll isn't found", use a solution as it is written here. To start work in most cases it is enough only these files.
  2. If I use the productive version – I create for placement of the connected plug-ins the Plugins folder under the root folder of system (in my example – D:\CheckLog\Plugins). The free trial version contains all necessary functions in the CheckLog.exe module, and doesn't demand installation and connection of plug-ins.
  3. I start CheckLog.exe directly from that folder where I copied it at initial installation. The free trial version doesn't need an activation key, and the productive version will request it. I import a key in the field named "New activation key" of the opening form, I can use function of copying of a key through a clipboard. I add a key to the list, having pressed [Add]. I press [Apply] for preservation of results.
  4. If it is required to keep contents of the logbook at several consecutive starts in the same file, I establish through a menu call: Set -> Continue system log. At the established mark former contents of the system log at restart of the program will be kept, new lines will be added in the end of log file.
  5. For an exit I use a call through the main menu: Set -> Exit, or simply I close the main form. Confirmations of an exit aren’t required.

Result:

  • System is installed on the computer, it is possible to work with it in the regular mode.
  • Needed "empty" database containing necessary tables and reference books is created.