LXE vx3x Verweisanleitung
110
VX3X Utilities
VX3X Reference Guide
E-EQ-VX3XRG-D
PCMCIA slots are off on powerup, to prevent the “Unidentified 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 wireless
client drivers (listed below) is 1, meaning one second elapses between the CAB file loading and
the slot powering up.
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 wireless
client drivers (listed below) is 1, meaning one second elapses between the CAB file loading and
the slot powering up.
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 CE application is called, depending on file type.
registry setting files (*.REG), or sound files (*.WAV). The mechanism is the same as listed
above, but the appropriate CE application is called, depending on file type.
Registry information is already in the default image for the following:
;; ------- autoexec batch file - for users convenience
[HKEY_LOCAL_MACHINE\SOFTWARE\LXE\Persist\AUTOEXEC]
"FileName"="\\System\\Autoexec.bat"
"Installed"=dword:0
"FileCheck"="ALWAYSEXEC"
"Order"=dword:50
;; The file name “ALWAYSEXEC” or “dummy” does not really matter as long as there is
;; no file of that name in the directory. You can use any name that you want for this entry
;; as long as it is a non existent file name. The purpose of this value is that if someone
;; wants to only execute this file one time then you would replace the value of FileCheck
;; with the name of a file that would exist the next time a warm boot occurs.
;; ------- RFTerm support
[HKEY_LOCAL_MACHINE\SOFTWARE\LXE\Persist\LXE TE]
"FileName"="\\System\\RFTERM.CAB"
"Installed"=dword:0
"FileCheck"="\\WINDOWS\\LXE\\RFTERM.EXE"
"Order"=dword:11
;; run the app after it has loaded and client device is ready
[HKEY_LOCAL_MACHINE\SOFTWARE\LXE\Persist\RFTERM]
"FileName"="\\WINDOWS\\LXE\\RFTERM.EXE"
"Installed"=dword:0
"FileCheck"="ALWAYSEXEC"
"Order"=dword:40
"Delay"=dword:1
[HKEY_LOCAL_MACHINE\SOFTWARE\LXE\Persist\AUTOEXEC]
"FileName"="\\System\\Autoexec.bat"
"Installed"=dword:0
"FileCheck"="ALWAYSEXEC"
"Order"=dword:50
;; The file name “ALWAYSEXEC” or “dummy” does not really matter as long as there is
;; no file of that name in the directory. You can use any name that you want for this entry
;; as long as it is a non existent file name. The purpose of this value is that if someone
;; wants to only execute this file one time then you would replace the value of FileCheck
;; with the name of a file that would exist the next time a warm boot occurs.
;; ------- RFTerm support
[HKEY_LOCAL_MACHINE\SOFTWARE\LXE\Persist\LXE TE]
"FileName"="\\System\\RFTERM.CAB"
"Installed"=dword:0
"FileCheck"="\\WINDOWS\\LXE\\RFTERM.EXE"
"Order"=dword:11
;; run the app after it has loaded and client device is ready
[HKEY_LOCAL_MACHINE\SOFTWARE\LXE\Persist\RFTERM]
"FileName"="\\WINDOWS\\LXE\\RFTERM.EXE"
"Installed"=dword:0
"FileCheck"="ALWAYSEXEC"
"Order"=dword:40
"Delay"=dword:1
When you are installing your custom CAB file to the mobile device’s operating sytem, refer to the
default image segments that are commented with “… RFTERM …” to see the expected Registry
format.
default image segments that are commented with “… RFTERM …” to see the expected Registry
format.
One special key is included to force the system folders (Desktop, Fonts, Programs, etc.) to copy
from the internal ATA card (\System) to the \Windows directory. This is implemented as a persist
key so the sequence of startup events can be controlled (especially for AppLock). The filename is
a special internal trigger for the Launch utility, to activate the CopyFolders function. DO NOT
EDIT OR ALTER THIS KEY, OR IT MAY NO LONGER FUNCTION. You may however change
the Order or Delay values if necessary for a particular startup sequence.
from the internal ATA card (\System) to the \Windows directory. This is implemented as a persist
key so the sequence of startup events can be controlled (especially for AppLock). The filename is
a special internal trigger for the Launch utility, to activate the CopyFolders function. DO NOT
EDIT OR ALTER THIS KEY, OR IT MAY NO LONGER FUNCTION. You may however change
the Order or Delay values if necessary for a particular startup sequence.
[HKEY_LOCAL_MACHINE\SOFTWARE\LXE\Persist\COPYFOLDERS]
“FileName”=”COPYFOLDERS”
“FileCheck”=””
“Order”=dword:0F
“FileName”=”COPYFOLDERS”
“FileCheck”=””
“Order”=dword:0F
To have files (CAB, EXE, REG, or WAV files) loaded on startup, when sequence of execution is
not important, you can put these files in the \System\Startup folder (on the internal ATA card).
This is parsed by the Launch utility, and these programs are started or executed.
not important, you can put these files in the \System\Startup folder (on the internal ATA card).
This is parsed by the Launch utility, and these programs are started or executed.