LXE vx3x Verweisanleitung
VX3X Utilities
109
E-EQ-VX3XRG-D
VX3X Reference Guide
VX3X Utilities
The following files are pre-loaded by LXE.
LAUNCH.EXE
All applications to be installed into persistent memory are normally in the form of Windows CE
CAB files. These CAB files exist as separate files from the main installation image, and need to be
copied to the mobile device using an internal ATA card or from a PC using ActiveSync. The CAB
files are loaded into the folder System, which is the internal ATA drive.
CAB files. These CAB files exist as separate files from the main installation image, and need to be
copied to the mobile device using an internal ATA card or from a PC using ActiveSync. The CAB
files are loaded into the folder System, which is the internal ATA drive.
Then, information is added to the registry, if desired, to make the CAB file auto-launch at startup.
The CAB file can update the registry as desired and cause the unpacked file(s) to be placed in the
appropriate location.
The CAB file can update the registry as desired and cause the unpacked file(s) to be placed in the
appropriate location.
The registry information needed is under the key HKEY_LOCAL_MACHINE \ SOFTWARE \ LXE
\ Persist, as follows. The main subkey is any text, and is a description of the file. Then 3 values
are added:
\ Persist, as follows. The main subkey is any text, and is a description of the file. Then 3 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.
The value in FileCheck is 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.
the CAB file installs into DRAM, when memory is lost this file is lost, and the CAB file must be
reinstalled.
Three optional fields are also added: Order, Delay, and PCMCIA. These are all DWORD fields,
described below.
described below.
The auto-launch process goes as follows. The launch utility opens the registry database and reads
the list of CAB files to auto-launch. 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. 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 WCELOAD to reinstall the CAB file. Then,
the whole process repeats for the next entry in the registry, until all registry entries are analyzed.
the list of CAB files to auto-launch. 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. 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 WCELOAD to reinstall the CAB file. 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.
“dummy”, which will never be found, forcing the item to execute.
For persist keys specifying .EXE or .BAT files, the executing process will be 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.
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.
The Order field is used to force a sequence of events; Order=0 is first, and Order=99 is last.
Two items which have the same order will be installed in the same pass, but not in a predictable
sequence. Note: If the order of loading is not critical, it may be easier to use the \System\Startup
folder instead; see below.
Two items which have the same order will be installed in the same pass, but not in a predictable
sequence. Note: If the order of loading is not critical, it may be easier to use the \System\Startup
folder instead; see below.
The Delay field 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.
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.
The PCMCIA field is used to indicate that the file (usually a CAB file) being loaded is a wireless
client driver, and the PCMCIA slots should be started after this file is loaded. By default, the
client driver, and the PCMCIA slots should be started after this file is loaded. By default, the