•If the Installed flag is set,
•Then, the whole process repeats for the next entry in the registry, until all registry entries are analyzed.
•To force execution every time (for example, for AUTOEXEC.BAT), use a FileCheck of “dummy”, which will never be found, forcing the item to execute.
•For persist keys specifying .EXE or .BAT files, the executing process is started, and then Launch will continue, leaving the loading process to run independently. For other persist keys (including .CAB files), Launch will wait for the loading process to complete before continuing. This is important, for example, to ensure that a .CAB file is installed before the
.EXE files from the .CAB file are run.
•Note that the
Note: Registry entries may vary depending on software revision level and options ordered with the MX7.
LAUNCH.EXE and Persistent StorageIf any of the following directories are created in the System folder, Launch automatically copies all of the files in these directories to the respective folder on the flash drive:
•AppMgr
•Desktop
•Favorites
•Fonts
•Help
•Programs
•Recent
Note: Files in the Startup folder are executed, but only from System > Startup. They are not copied to another folder.
REGEDIT.EXERegistry Editor – Use caution when editing the Registry and make a backup copy of the registry before changes are made.
REGLOAD.EXERegistry dump – Saves a copy of the registry as a text file. The file, REG.TXT, is located in the root folder.
Note: The REG.TXT file is not saved in persistent storage. To use the REG.TXT file as a reference in the event of a coldboot, copy the file to the System folder on the MX7 or store a copy of the REG.TXT file on a PC.