Creating A Splash Screen; Xml Provisioning - Symbol MC909X Integrator Manual

Creating a Splash Screen

Use a bitmap file to create a customized splash screens for the mobile computer. Use Image Update with a
bitmap file, rather than a package file, to update the splash screen.
To create a custom splash screen:
Create a .bmp file using a graphic program with the following specifications:
1.
Size: 240 x 296.
•
Colors: 8 bits per pixel (256 colors) for color displays.
•
Modify the bitmap file and save.
2.
To load the splash screen on the mobile computer:
Create a text file named pkgs.lst which contains the name of the bmp file. For example, mysplash.bmp.
1.
Copy the bmp file and the pkgs.lst file to one of the following:
2.
SD card root directory
•
mobile computer's \temp directory
•
mobile computer's \Windows directory.
•
If using an SD card, insert the SD card into the mobile computer.
3.
Perform a cold boot.
4.
Press the trigger or side scan button for 5 seconds while booting to invoke the Update Loader and install
5.
the splash screen.

XML Provisioning

To configure the settings on a mobile computer XML provisioning should be used. To install an XML
provisioning file on the mobile computer, create a Cabinet Provisioning File (CPF) file. A CPF file is similar to a
CAB file and contains just one file: _setup.xml. Like a CAB file, the CPF extension is associated with
WCELoad.EXE. Opening a CPF extracts the XML code and uses it to provision and configure the mobile
computer. The user receives an e-mail notification indicating success or failure.
XML Provisioning provides the ability to configure various features of the mobile computer (i.e., registry and file
system). However, some settings require security privileges. To change registry settings via a CPF file, you
need to have certain privileges (roles). Some registry keys require you to simply be an Authenticated User,
while other registry keys require you to be a Manager. Refer to the Windows Mobile 5.0 Help file, Metabase
Settings for Registry Configuration Service Provider section, for the default role settings in Windows Mobile
5.0.
For those registry settings that require the Manager role, the CPF file must be signed with a privileged
certificate installed on the device. Refer to the Microsoft Windows Mobile 5.0 Help file and the Windows Mobile
5.0 SDK for instructions and sample test certificates.
Application Deployment for Mobile 5.0 8 - 7