After downloading and extracting the EUC Score ZIP archives into a local folder, run the EUC Score installer packages:
The first EUC Score Toolset deployment step is installing the base installer package Install-EUCScore.exe on each target system. This base package includes Simloads, standard data files and supporting tools. Only this base installation wizard shows a text input field for selecting the local installation path.
After the base package was installed, the next optional step is the installation of additional packages, for example the EUC Score Media Pack or an EUC Score Service Pack including updates and bug fixes. The installer of an optional package checks if the registry value Software\EUCScore\Folders\InstallPath exists in HKLM or HKCU and aborts if it does not. If the value exists, it holds the target root folder where EUC Score files and folders are copied to during the installation.
After a successfull installation of the EUC Score Toolset, the following files and folders were created in the local file system of the target system:
Each Simload that was deployed by an EUC Score installer package is registered in the Windows registry. The registry key Software\EUCScore\Simloads contains a REG_SZ value with the full executable path for each Simload. The location in the registry is defined by the installation mode which can be per user (= HKCU) or per machine (= HKLM), where the later requires administrative privileges. This registration mechanism allows any script or tool to launch a Simload from the correct folder.
The registry key HKCU\Software\EUCScore (per user installation) or HKLM\Software\EUCScore (per machine installation) includes a range of subkeys with settings. For details, see the table below.
|InstallPath [SZ]||EUC Score root installation path (default: C:\EUCScore).|
|Data [SZ]||Folder that contains the common data subfolders for documents, HTML files, images and videos.|
|Results [SZ]||Target folder for results and log files.|
|SimLoads [SZ]||Folder that contains the subfolders with each simload executable and .ini file.|
|Tools [SZ]||Folder that contains EUC Score tools|
|SL0-... [SZ]||Registered Type 0 Simload = System / Test / Prototype.|
|SL1-... [SZ]||Registered Type 1 Simload = Single application.|
|SL2-... [SZ]||Registered Type 2 Simload = Multiple Apps / Persona.|
|SL3-... [SZ]||Registered Type 3 Simload = Score.|
|iCountdownScreen [DWORD]||Sets the initial number of seconds in the countdown screen. The default value is 3, but when recording the Simload screen output with a frame grabber, there may be situations when it's better to change this value to 1.|
|bLogVerbose [DWORD]||If set to 1, INFO and WARNING messages are added the log file located in the Results folder. NOTE: Verbose mode may influence the runtime behavior of a Simload. Do not use it during real test runs.|
|bDebug [DWORD]||If set to 1, DEBUG messages are added to the log file located in the Results folder. NOTE: Debug mode may influence the runtime behavior of a Simload. Do not use it during real test runs.|
|bShowControl [DWORD]||If set to 1, Simload controls are displayed on the screen (such as the type 2 Simload exit button).|
Each Simload writes into a log file named Simload_<ComputerName>_<UserName>.log, located in the Results folder (typically C:\EUCScore\Results). With default settings, only system and error messages are sent to the log file. By setting the bLogVerbose registry value in Software\EUCScore\Settings in HKCU or HKLM to 1, also warning and info messages go to the log file. By setting the bDebug registry value in Software\EUCScore\Settings to 1, also debug messages go to the log file.
NOTE: A Simload can also be launched when it is not registered. In this case, it tries to find the necessary global configuration settings (such as folder locations or countdown settings) in the registry under HKCU\Software\EUCScore. If this fails, it reads the required values from the side-by-side .ini file that must have the same name as the Simload .exe file. This allows a copy-and-paste deployment into a user session in cases where the required privileges for deploying an installer package are not available.