BAD DOWNLOAD: "NOT A VALID WIN32 EXECUTABLE"
A common reason for OAK to fail to install is that the file that has been downloaded is incomplete, or, less often, corrupted. The usual signal that this is the case is that your computer complains that the file is "not a valid WIN/32 executable". There is material at www.operisanalysiskit.com/TryOak.htm offering various alternative methods of downloading the file if this proves a problem.
GOOD DOWNLOAD: no action or SELF TESTS FAIL
Some workstations, particularly ones that are locked down in secure environments, may present obstacles to the normal installation process. You may be told directly that you don't have the necessary privileges to install software on that machine, and your computer won't run the OAK installer at all. Alternatively, the installation may appear to happen, but be prevented from doing some necessary thing when it tries to.
This has proved to be a significant issue among the many users of the previous version of OAK, who operate in security conscious businesses in financial services. The setup program has therefore been engineered to perform a variety of preinstallation tests, to inspect the environment in which it finds itself and form an impression (but not a certainty) of the likelihood that OAK will run without problems.
If one or more of those tests fail, the OAK installer will display the results of all of the tests.
Operis will likely ask to see the output from the installer in preinstallation test mode where users are having difficulty installing the product; or an organization's IT department may find it gives all that is needed to overcome installation obstacles. A text summary of the tests suitable for emailing can be generated by pressing the Report button.
See also
Forcing preinstallation testing