Enterprise Client Pack; Thor Vm3 Utilities; Launch.exe - Honeywell Thor vm3 User Manual

Enterprise Client Pack

There are several components of the Enterprise Client Pack installed on the Thor VM3. For more information on these pro-
grams visit the Thor VM3 product page at www.honeywellaidc.com.
Enterprise TE
Start > All Programs > Honeywell > Enterprise TE
Optional terminal emulation software. The application can also be accessed by double-clicking the Enterprise TE
desktop icon.
Enterprise Browser
Start > All Programs > Honeywell > Enterprise Browser
Optional lock-down web client software. The application can also be accessed by double-clicking the Enterprise
Browser desktop icon.
Enterprise Browser is designed for users running web-based applications to limit access to other applications, web
sites, or other parts of the operating system
Enterprise Browser can be used alone or with Launcher.
Launcher
Start > All Programs > Honeywell > Launcher
Optional lock-down menu software. The application can also be accessed by double-clicking the Launcher desktop
icon.
End users must log in and can only access authorized programs.
Launcher can be used alone or with Enterprise Browser .

Thor VM3 Utilities

The following files are pre-loaded.

LAUNCH.EXE

Launch works in coordination with registry settings to allow drivers or applications to be loaded automatically into DRAM at
system startup. Registry settings control what gets launched; see the App Note for information on these settings. For
examples, you can look at the registry key
HKEY_LOCAL_MACHINE \ Software \ HSM \ Persist
Launch will execute .CAB files, .BAT files, or .EXE files.
App Note
All applications to be installed into persistent memory must be in the form of CAB files. These CAB files exist as sepa-
rate files from the main installation image, and are copied to the device using ActiveSync, or using removable media
such as a USB drive. The CAB files are copied from into the folder System, which is the persistent storage virtual
drive. Then, information is added to the registry, if desired, to make the CAB file auto-launch at startup.
The registry information needed is under the key HKEY_LOCAL_MACHINE \ Software \ HSM \ Persist, as follows. The
main subkey is any text, and is a description of the file. Then four mandatory values are added:
FileName is the name of the CAB file, with the path (usually \System).
Installed is a DWORD value of 0, which changes to 1 once auto-launch installs the file.
FileCheck is the name of a file to look for to determine if the CAB file is installed. This will be the name of one of the
files (with path) installed by the CAB file. Since the CAB file installs into DRAM, when memory is lost this file is lost,
and the CAB file must be reinstalled.
Order is used to force a sequence of events. Order=0 is first, and Order=99 is last. Order must be greater than 4 for
the Thor VM3. Two items which have the same order will be installed in the same pass, but not in a predictable
sequence.
5 - 3