Launch.exe And Persistent Storage - Honeywell Thor VM3 User Manual

The auto-launch process proceeds as follows:
1. The launch utility opens the registry database and reads the list of CAB files to auto-
2. First it looks for FileName to see if the CAB file is present. If not, the registry entry is
3. If the Installed flag is set, auto-launch looks for the FileCheck file. If it is present, the
4. Then, the whole process repeats for the next entry in the registry, until all registry
5. To force execution every time (for example, for AUTOEXEC.BAT), use a FileCheck of
6. For persist keys specifying .EXE or .BAT files, the executing process is started, and
7. Note that the auto-launch process can also launch batch files (*.BAT), executable
Note: Registry entries may vary depending on software revision level and options ordered with
the Thor VM3.

LAUNCH.EXE and Persistent Storage

If any of the following directories are created in the System folder, Launch automatically
copies all of the files in these directories:
System\Desktop
System\Favorites
System\Fonts
System\Help
System\Programs
AppMgr
138
dialog from appearing. Once the drivers are loaded, the slot can be turned on. The
value in the PCMCIA field is a DWORD, representing the number of seconds to wait
after installing the CAB file, but before activating the slot (a latency to allow the
thread loading the driver to finish installation). The default value of 0 means the slot
is not powered on. The default values for the default radio drivers (listed below) is 1,
meaning one second elapses between the CAB file loading and the slot powering up.
launch.
ignored. If it is present, and the Installed flag is not set, auto-launch makes a copy of
the CAB file (since it gets deleted by installation), and runs the Microsoft utility
WCELOAD to install it.
CAB file is installed, and that registry entry is complete. If the FileCheck file is not
present, memory has been lost, and the utility calls WCELOAD to reinstall the CAB
file.
entries are analyzed.
"dummy", which will never be found, forcing the item to execute.
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.
files (*.EXE), registry setting files (*.REG), or sound files (*.WAV). The mechanism is
the same as listed above, but the appropriate application is called, depending on file
type.
copied to
copied to
copied to
copied to
copied to
copied to
Thor VM3 with Microsoft Windows Embedded Compact 7 User Guide
Windows\Desktop
Windows\Favorites
Windows\Fonts
Windows\Help
Windows\Programs
Windows\AppMgr