Report - Speedcrypt File Encryption

File Encryption
Encrypted Files
Go to content
Partial Self-Test and Speedcrypt Exceptions
Another important section of the Main Program Window is certainly the one called Report. In this section, the report with the results of the partial Self-Test and the Exceptions that keep the data flow intact with which Speedcrypt works are displayed.

Note: if the partial self-test fails, refer to this section of the main page immediately to understand which algorithm did not pass Speedcrypt's initialization. In that case, run the complete test, and if you obtain a successful result, restart Speedcrypt.
Partial Self-Test and Exceptions Log
This section is also divided into two panels. On the left is the one called Partial Self-Test, which displays a report related to the Partial Self-Test that Speedcrypt performs when the program starts. On the right is the panel called Exception Log, which shows the exceptions with which Speedcrypt informs the user of any anomalies that may have occurred.
Speedcrypt Exceptions Log
Please note that Speedcrypt displays and stores all types of Exceptions, including those related to messages that the user can accept or reject when prompted by the program. This allows you to have a complete overview of the data flow through which Speedcrypt governs the program, and you can benefit from valuable collaboration. In this version, you can delete the entire List of Exceptions, but not individual values. You also have the option to save the entire list to a TXT file for convenient reference and future use.
This section is updated when the program starts and during all operations that the user performs with Speedcrypt, not only in the main window but also in all those that make up the project.
Partial Self-Test
At startup, Speedcrypt performs a partial Self-Test on some essential algorithms for the proper functioning of the encryption processes. This way, the user is informed that they can Encrypt and Decrypt their data with algorithms that have passed the suitability test.

The success or failure of the test is indicated in the status bar by an LED that turns green if everything went well, otherwise it turns red. The algorithms and engines subjected to the Self-Test are listed in the appropriate panel, preceded by the date and time the Partial Self-Test was performed, which corresponds to the program startup.
As mentioned earlier, the report available in the section described on this page of the guide corresponds to the Partial Self-Test. Speedcrypt provides its users with an additional complete Self-Test, which verifies the proper functioning of all the algorithms used in the project. The complete test can be run in the Self-Test window, as described in the relevant page of Online Guide.
Exceptions Log
Speedcrypt does everything to ensure that the visible and background data flow can be as stable as possible, trying in every way to give the user complete control of the program. To do this, it uses an exception-based strategy, some of which are visible and controllable by the user, while others are invisible and return program control to the user. Each created exception is stored in an archive and displayed through a report that can be printed in a text file, if deemed necessary.

A complete list of both visible and invisible exceptions can be found in the help page called Exceptions Log. The list also includes possible workarounds and solutions to ensure that the program always functions correctly.
The Report section is extremely important, as well as interesting, to consult with some frequency to always keep the correct functioning of the Speedcrypt Project under control. Through the exception registry it is possible to identify any bugs that can be reported and subsequently corrected by the developer.
Back to content