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

There are two optional fields that may be added:
1. Delay is used to add a delay after the item is loaded, before the next is loaded. The delay is given in seconds, and
defaults to 0 if not specified. If the install fails (or the file to be installed is not found), the delay does not occur.
2. PCMCIA is used to indicate that the file (usually a CAB file) being loaded is a radio driver, and the PCMCIA slots
should be started after this file is loaded. By default, the PCMCIA slots are off on powerup, to prevent the "Uniden-
tified PCMCIA Slot" 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.
The auto-launch process proceeds as follows:
1. The launch utility opens the registry database and reads the list of CAB files to auto-launch.
2. First it looks for FileName to see if the CAB file is present. If not, the registry entry is 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.
3. If the Installed flag is set, auto-launch looks for the FileCheck file. If it is present, the 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 WCE-
LOAD to reinstall the CAB file.
4. Then, the whole process repeats for the next entry in the registry, until all registry entries are analyzed.
5. 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.
6. 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.
7. Note that the auto-launch process can also launch batch files (*.BAT), executable 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.
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 direc-
tories:
System\Desktop
System\Favorites
System\Fonts
System\Help
System\Programs
AppMgr
Recent
This function copies only the folder contents, no sub-folders.
The Windows\Startup folder is not copied on startup because copying this folder has no effect on the system or an incorrect
effect.
Files in the Startup folder are executed, but only from System\Startup. Windows\Startup is parsed too early in the boot pro-
cess so it has no effect.
Executables in System\Startup must be the actual executable, not a shortcut, because shortcuts are not parsed by Launch.
Note: Files in the Startup folder are executed, but only from System > Startup. They are not copied to another folder.
5 - 4
copied to
copied to
copied to
copied to
copied to
copied to
copied to
Windows\Desktop
Windows\Favorites
Windows\Fonts
Windows\Help
Windows\Programs
Windows\AppMgr
Windows\Recent