LXE mx7 Verweisanleitung
Utilities
139
E-EQ-MX7RG-H
MX7 Reference Guide
ActiveSync indicator on the host remains gray
The host doesn't know you are trying to connect. May mean a bad cable, with no control lines
connected, or an incompatible baud rate. Try the connection again, with a known-good cable.
connected, or an incompatible baud rate. Try the connection again, with a known-good cable.
Testing connection with a terminal emulator program, or a serial port monitor
You can use HyperTerminal or some other terminal emulator program to do a rough test of
ActiveSync. Set the terminal emulator to 8 bits, no parity, 1 stop bits, and the same baud rate as
the connection on the CE device. After selecting Start | Programs | Communication | Connect on
the CE device, the word "CLIENT" appears on the CE display in ASCII format. When using a
serial port monitor, you see the host echo "CLIENT", followed by "SERVER". After this point,
the data stream becomes straight (binary) PPP.
ActiveSync. Set the terminal emulator to 8 bits, no parity, 1 stop bits, and the same baud rate as
the connection on the CE device. After selecting Start | Programs | Communication | Connect on
the CE device, the word "CLIENT" appears on the CE display in ASCII format. When using a
serial port monitor, you see the host echo "CLIENT", followed by "SERVER". After this point,
the data stream becomes straight (binary) PPP.
Drop down list is blank in the ActiveSync dialog box
The wireless link is broken. Make sure that the network card has a valid IP address.
Utilities
These utilities are pre-loaded by LXE. In previous versions .REG files were placed in the MX7
Windows file structure – they are now available using the MX7 Options tab in the Control Panel.
Windows file structure – they are now available using the MX7 Options tab in the Control Panel.
Note: AppLock Administrator Control panel file Launch option does not inter-relate with
similarly-named options contained in other LXE Control Panels or programs.
LAUNCH.EXE
All applications to be installed into memory are normally in the form of Windows CE CAB files.
The CAB files exist as separate files from the main installation image, and need to be copied to
the mobile device using an internal Flash card or from a PC using ActiveSync. The CAB files are
loaded into the folder System, which is the internal Flash drive.
The CAB files exist as separate files from the main installation image, and need to be copied to
the mobile device using an internal Flash card or from a PC using ActiveSync. The CAB files are
loaded into the folder System, which is the internal Flash 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
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