TurboSFV - eXtended Edition (XE) Overview The eXtended edition (XE) of TurboSFV has all the features of the Private Edition (PE) and the Commer­cial Edition (CE), except the Mobile Edition (ME), which is only available in CE. In addition, XE provides a Windows service appli­cation for the calcu­lation and verifi­cation of checksums, running as service jobs in the back­ground. A Trial Version (XE) is available for download. Checksum service appli­cation for Windows TurboSFV LE: PE: CE: XE: TurboSFV XE provides a service module: This module can be installed as a Windows service appli­cation and can run hash value calcu­lation and checksum vali­dation jobs auto­mated in the back­ground, with­out having a user logged on. Calcu­lation jobs can be the creation of a hash file, the vali­dation of check­sums or analysis jobs, for example the search for new files. The activities can be logged in detail in a log file. Impor­tant events will be written to the Windows event log (application). The service can be configured from within the main program, where there are also options to define specific jobs for the service. For the service configu­ration, adminis­tration rights are needed, a normal user can only view these settings. Jobs can also be con­figured by normal users, if reques­ted. Service configu­ration The service con­figu­ration dialog allows to control the service. On this screen, the service can be star­ted and stopped as well as installed and uninstalled. An account must be specified to define a context, in which the service will be running. It's even possible to use a special crafted account. The entire configu­ration of the ser­vice (setup, log­ging, permis­sions) can be exported to a configu­ration file as well as impor­ted, if needed. Service logging In this dialog, options for the logging can be defined. The location of the log file and the file name can be ad­justed in various ways. It's possible to use another log folder than the default, or to have the log file in sub folders separated by date or by the computer name and to name the file with such a prefix. Service: Per­missions for normal users On this page it can be defined, which functionality will be available for normal users. Some adminis­trative tasks like adjusting jobs or checking log files can be delegated to normal users. For each group of tasks, the options "None", "Read only" and "Modify" are available. Service Job list This dialog allows to setup and control jobs, to be executed by the service. The job list con­sists of various columns, in which the most impor­tant infor­mation for each job is displayed. The columns can be resized and sorted Name The name of the job, appears also in the log file. Type Job type, possible values are: Crea­tion, Vali­dation, Ana­lysis. Status The status of the job, which can be enabled, disabled or deleted. Schedule Provides basic schedule infor­mation. Boot delay Number of minutes that a job will wait for being executed at system startup. Last Run Date and time when job finished last. Last Result Return value from the job execution. Queue Queue information for the job. Next Run Calculated date and time, when job is scheduled next. Last change Last time, job parameters were changed. Changed by Who changed the job parameters? Created Time when job was created. Author Who created the job? The column headers of the job list can be right clicked, so that a menu appears, which provides options to hide and show specific columns. Each job has a context menu where you can trigger specific actions for a job: A job can be en- or disabled, deleted, the job properties can be shown and it's possible to run jobs out of the row. "Details: Last Run" points to the appropriate entry in the service log file. The job list itself has also a context menu, which has options to setup new jobs. In addition, the job list can be re­freshed and from here, the service log folder can be investi­gated. Service jobs: General parameters For all type of jobs, this tab sheet provides general options. Name Name of the job, appears also in the log file. Start the job The job will be exe­cuted after the system start with a delay or at a specific time. Boot delay Time in minutes the execution of a job will be delayed at system startup. Date and time Here it can be speci­fied, when a job should run. Repeat every If checked, then a job runs perio­dically (automatic repetition). Reschedule last job At system startup, a job can be sche­duled again, if it didn't run as planned. Service job type: Creation This kind of job can be used to calculate check­sums for a set of files and to save them in a hash file for a later vali­dation or analysis. Source The folder where the files are loca­ted, for which you want to calculate and save checksums. Algorithm The hash type to be used for calculating checksums. Similar to the main program, all supported hash functions are available: CRC-32, MD5, SHA-1, XXH32, XXH64, SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224, SHA-512/256, BLAKE2S-256, BLAKE2SP-256, BLAKE2B-256, BLAKE2B-384, BLAKE2B-512, BLAKE2BP-256, BLAKE2BP-384, BLAKE2BP-512, BLAKE3-256, BLAKE3-512, BLAKE3-1024, BLAKE3-2048, SHA3-224, SHA3-256, SHA3-384 and SHA3-512. Use SSE instruc­tions Instead of the normal x86/x64 CPU instruc­tions, for SHA-256 and SHA-224 the SSE based instruc­tions: SHA256RNDS2, SHA256MSG1, SHA256MSG2, for SHA-1, the SSE based instruc­tions: SHA1RNDS4, SHA1MSG1, SHA1MSG2, SHA1NEXTE and for algo­rithms from the BLAKE3 family (BLAKE3-256, BLAKE3-512, BLAKE3-1024, BLAKE3-2048), a special SSE based imple­men­tation will be used for the calcu­lation of checksums, if the CPU supports these instruc­tions. Hash file The location and file name of the checksum file. Log file Path and file name of a job specific log file. Recursive scan mode Provides options for specifying the way, how a folder tree is scanned for files. The file order in checksum files changes accor­dingly. Encoding The encoding for the hash file. Line feed Characters to be used for new lines in a hash file. Options Various options to control the creation process, including backup of an existing checksum file and a recursive search for files. This dialog provides options to further limit the number of files. It's possible to filter by file attributes or by file names and / or extensions. If you use both filters with either the option include or exclude, then a file must meet the criteria of both filters. Service job type: Validation This job type can be used to validate checksums of files, which you have previously calcu­lated and saved in a hash file. Thus, the checksum file must be specified and optionally a job specific log file. For SHA-1, SHA-224, SHA-256, BLAKE3-256, BLAKE3-512, BLAKE3-1024 and BLAKE3-2048 check­sums, special SSE (Stream­ing SIMD Exten­sions) based instruc­tions can be used for the compu­tation, if they are supported by the CPU. Service job type: Analysis This kind of job can be used for a further analysis of a hash file. A hash file can be ana­lyzed in a way, that the last validation results can be reviewed or files can be checked against availability. Additionally it can be searched for new files, not listed in the hash file. The output of this functio­nality can be seen in the service log as well as in a job-specific log. Hash file Specifies the hash file to analyze. Log file Path and file name of a job specific log file. Options Along with ana­lyzing the last validation results, the file availability can be checked and it can be searched for new files, which are not listed in the checksum file. Optionally, a recursive search is also possible. Filter For the functio­nality "Search for new files", the above shown filter capabilities for file attributes and extensions are also available here. Job monitor Along with the service module, an application is avail­able, which can monitor service jobs and inform about their results. The job monitor runs as a system tray application in the context of a speci­fic user and can be confi­gured in a way, that it automa­tically starts on each user logon. The job monitor can display a balloon hint for a finished job: These events will also be logged in the tray log, which can be opened by double-clicking the tray icon: The tray icon pro­vides a context menu, which can be used to confi­gure the job monitor and which offers additional functio­nality. View tray log Opens a window which displays the tray log. This func­tionality is also available by double-clicking the tray icon. Open current log file Opens a windows which displays the actual service log file. Browse log folder Displays a list of log files in the service log folder. Trigger balloon Specifies, in which case a balloon is displayed for a finished job. Possible options in any combination are succeeded jobs, warnings and errors. On balloon click Action to be taken if a balloon was clicked: Either view tray log or dismiss. Auto-start If checked, then the job-monitor starts automatically. Exit Terminates the tray application. Service events The service pro­gram writes impor­tant events (such as service started or stopped or other events, which impact the service) to the Windows event log (appli­cation). Job specific messages are written to the service log or to a job specific log file. It's possible to setup a custom view in the event viewer, in order to see only events triggered by the TurboSFV check­sum service appli­cation.   Pre­vi­ous page Table of con­tents
Privacy Policy Copyright © 2007-2025 Jörg Krahe. All Rights reserved!