Symantec WISE MOBILE DEVICE PACKAGE EDITOR 8.0 - REFERENCE FOR WISE PACKAGE STUDIO... Service manual

Wise Mobile Device Package Editor
Reference

Mobile Device Package Editor Reference 2
Mobile Device Package Editor
The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the
agreement.
Documentation version 8.0
Legal Notice
Copyright © 2009 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, and Altiris are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and
other countries. Other names may be trademarks of their respective owners.
The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse
engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec
Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE
DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT
BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS
DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to
restricted rights as defined in FAR Section 52.227-19 “Commercial Computer Software - Restricted Rights” and DFARS 227.7202, “Rights in
Commercial Computer Software or Commercial Computer Software Documentation”, as applicable, and any successor regulations. Any use,
modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government
shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com

Mobile Device Package Editor Reference 3
Technical Support
Symantec Technical Support maintains support centers globally. Technical Support’s
primary role is to respond to specific queries about product features and functionality.
The Technical Support group also creates content for our online Knowledge Base. The
Technical Support group works collaboratively with the other functional areas within
Symantec to answer your questions in a timely fashion. For example, the Technical
Support group works with Product Engineering and Symantec Security Response to
provide alerting services and virus definition updates.
Symantec’s maintenance offerings include the following:
zA range of support options that give you the flexibility to select the right amount of
service for any size organization
zTelephone and Web-based support that provides rapid response and up-to-the-
minute information
zUpgrade assurance that delivers automatic software upgrade protection
zAdvanced features, including Account Management Services
For information about Symantec’s Maintenance Programs, you can visit our Web site at
the following URL:
www.symantec.com/techsupp/
Contacting Technical Support
Customers with a current maintenance agreement may access Technical Support
information at the following URL:
www.symantec.com/techsupp/
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be at the
computer on which the problem occurred, in case it is necessary to replicate the
problem.
When you contact Technical Support, please have the following information available:
zProduct release level
zHardware information
zAvailable memory, disk space, and NIC information
zOperating system
zVersion and patch level
zNetwork topology
zRouter, gateway, and IP address information
zProblem description:
Error messages and log files
Troubleshooting that was performed before contacting Symantec
Recent software configuration changes and network changes

Mobile Device Package Editor Reference 4
Licensing and registration
If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
www.symantec.com/techsupp/
Customer service
Customer service information is available at the following URL:
www.symantec.com/techsupp/
Customer Service is available to assist with the following types of issues:
zQuestions regarding product licensing or serialization
zProduct registration updates, such as address or name changes
zGeneral product information (features, language availability, local dealers)
zLatest information about product updates and upgrades
zInformation about upgrade assurance and maintenance contracts
zInformation about the Symantec Buying Programs
zAdvice about Symantec’s technical support options
zNontechnical presales questions
zIssues that are related to CD-ROMs or manuals
Maintenance agreement resources
If you want to contact Symantec regarding an existing maintenance agreement, please
contact the maintenance agreement administration team for your region as follows:
Additional enterprise services
Symantec offers a comprehensive set of services that allow you to maximize your
investment in Symantec products and to develop your knowledge, expertise, and global
insight, which enable you to manage your business risks proactively.
Enterprise services that are available include the following:
Asia-Pacific and Japan [email protected]
Europe, Middle-East, and Africa [email protected]
North America and Latin America [email protected]
Symantec Early
Warning Solutions These solutions provide early warning of cyber attacks, comprehensive threat analysis, and countermeasures to prevent
attacks before they occur.
Managed Security
Services These services remove the burden of managing and monitoring security devices and events, ensuring rapid response to real
threats.

Mobile Device Package Editor Reference 5
To access more information about Enterprise services, please visit our Web site at the
following URL:
www.symantec.com
Select your country or language from the site index.
Consulting
Services Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. Symantec
Consulting Services offer a variety of prepackaged and
customizable options that include assessment, design,
implementation, monitoring, and management capabilities. Each
is focused on establishing and maintaining the integrity and
availability of your IT resources.
Educational
Services Educational Services provide a full array of technical training, security education, security certification, and awareness
communication programs.

Mobile Device Package Editor Reference 6
Contents
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 1: Introduction to Mobile Device Package Editor . . . . . . . . . . . . . . . . . . . . . . . . 7
About Mobile Device Package Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
About Windows Mobile Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Starting the Mobile Device Package Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Using Installation Expert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Using the INF Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Compiling a Mobile Device Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Product Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2: Creating Installations for Mobile Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
About Installation Expert in Mobile Device Package Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Defining Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
About Multiple Device Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Defining Device Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Entering Platform Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Adding Files to a Mobile Device Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Editing File Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Adding Registry Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Defining Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Mobile Device Package Editor Reference 7
Chapter 1
Introduction to Mobile Device Package Editor
This chapter includes the following topics:
zAbout Mobile Device Package Editor on page 7
zAbout Windows Mobile Installations on page 7
zStarting the Mobile Device Package Editor on page 8
zUsing Installation Expert on page 9
zUsing the INF Editor on page 10
zCompiling a Mobile Device Installation on page 10
zProduct Documentation on page 11
About Mobile Device Package Editor
Mobile Device Package Editor is an installation development tool that lets you create an
.INF file and compile it to one or more .CAB files that install a mobile device application.
It supports the Microsoft® Windows Mobile™ platform for Pocket PC and Smartphone
devices.
In the Installation Expert interface in Mobile Device Package Editor, you complete dialog
boxes to specify the installation resources and parameters. These installation options
generate the project file in .INF format, which is used to compile the installation .CAB
files.
For advanced customization, you can edit the .INF directly within the Mobile Device
Package Editor. Changes that you make in Installation Expert are automatically reflected
in the .INF file, and vice versa.
You can open an .INF file from any vendor or other third party in the Mobile Device
Package Editor, and compile it to a .CAB. You also can open a Pocket PC .CAB to edit and
recompile it.
Mobile Device Package Editor is included with the following products:
zWise Installation Studio
zWise Package Studio®
The functionality is the same in both products.
About Windows Mobile Installations
The Microsoft® Windows Mobile™ platform supports Pocket PC and Smartphone
devices. A Windows Mobile device installation consists of a single, self-extracting .CAB
file and an optional Setup.dll file. The .CAB file contains all the resources (files, registry
keys, and shortcuts) that comprise the application. The Setup.dll file provides functions
for performing certain operations during the installation and removal of your application.

Mobile Device Package Editor Reference 8
Introduction to Mobile Device Package Editor
Mobile device .CAB files are generated by the CabWiz program from an information file
(.INF). The .INF is a text file that specifies directories, files, settings, and configurations
that are used to install a mobile device application.
(Pocket PC applications only.) A single .INF file can contain information to produce
multiple .CAB files. Example: An application supports the Windows Mobile and Pocket PC
2002 platforms, but several of the application files are platform-dependent. When you
create the installation, you assign the files to the device that supports that platform.
When you compile, the Windows Mobile-specific files are placed in the Windows Mobile
.CAB file, and the Pocket PC 2002-specific files are placed in the Pocket PC 2002 .CAB
file.
A mobile device application can be installed in the following ways:
zThe .CAB file and an .INI file that describes the .CAB are included in an installation
that runs on the desktop computer. The desktop computer contains Application
Manager (CeAppMgr.exe), which is installed with ActiveSync. Application Manager
installs the mobile device application on the device.
zThe end user copies the .CAB file to the mobile device and opens it. The .CAB file
extracts its contents to the directories that were specified in the .INF file.
Uninstall of the mobile device application is controlled by the mobile device and
ActiveSync. Uninstalling the mobile device installation from the desktop computer does
not affect the application that is installed on the mobile device.
To add mobile device .CAB files to a desktop installation:
zWindows Installer installations: use Installation Expert > Mobile Devices page in
Windows Installer Editor.
zWiseScript installations: use the Install Windows Mobile Application script action in
WiseScript Package Editor or Wise Script Editor.
See:
About the Mobile Devices Page in the Windows Installer Editor Help
Install Windows Mobile Application in the WiseScript Package Editor or WiseScript Editor
Help
Starting the Mobile Device Package Editor
The way you start Mobile Device Package Editor depends on which of the following
products you are using.
In Wise Installation Studio
Select Start > Programs > Symantec > Wise Installation Studio > Mobile Device
Package Editor.
In Wise Package Studio
Do one of the following:
zOn the Projects tab, click the Run link to the right of the task or tool associated with
Mobile Device Package Editor.
zOn the Tools tab, double-click Mobile Device Package Editor.

Mobile Device Package Editor Reference 9
Introduction to Mobile Device Package Editor
See also:
About Mobile Device Package Editor on page 7
Using Installation Expert on page 9
Using the INF Editor on page 10
Using Installation Expert
To display Installation Expert, click Installation Expert at the lower left of the editor’s
main window.
Installation Expert window in Mobile Device Package Editor
Page Groups
Pages are organized into page groups. Click the group name to expand or collapse its
pages. Click a page name to display that page.
Page Area
When you click a page name in a page group, this area displays the page’s options. Each
page lets you define a specific aspect of the mobile device package. (Examples: On the
Files page, you define what files are included in the package.) Complete just the pages
that are pertinent to your particular package, in any order. If required information is
missing, an error message appears during compile.
zUse on the toolbar to navigate from page to page, or click the page name in
the list of pages.
zTo display help for the current page, press F1.
Page Area
Page Groups
View Navigation Compile

Mobile Device Package Editor Reference 10
Introduction to Mobile Device Package Editor
View Navigation
Click these tabs to change views.
Compile
Click the Compile button to build the package.
Using the INF Editor
As you specify settings in Installation Expert, an .INF file is created, containing
information about the installation. The INF Editor lets you view and edit that .INF file.
You might do this to add functionality that isn’t possible with Installation Expert alone.
To display the INF Editor, click the INF Editor tab at the lower left of the main window.
The INF Editor is a basic text editor. Changes that you make in Installation Expert are
automatically reflected in the .INF file, and vice versa.
Warning
The INF Editor does not validate any changes you make to the .INF file. Edit the .INF file
directly only if you have a clear understanding of the .INF file contents and syntax.
Search for “.inf Files for Devices” in the MSDN library (msdn.microsoft.com/library/).
Compiling a Mobile Device Installation
Mobile device .CAB files are generated by the CabWiz program from an information
(.INF) file. The Application Type option on the Application Information page
determines which CabWiz program is used:
zPocket PC applications use Cabwiz.exe.
zSmartphone applications use CabwizSP.exe.
Compiled Files
When you compile an .INF file with the Mobile Device Package Editor, the following files
are created:
zinstallation_name.device_name.CAB
The installation file, containing all the resources (files, registry keys, and shortcuts)
that comprise the application. The compile process creates a .CAB file for the default
device and every additional device that is defined in the installation.
zinstallation_name.device_name.DAT
(Pocket PC only.) Stores the instructions for installing the application.
zWiseErr.txt
Records error messages that result from the compile.
To compile a mobile device installation
1. Click Compile at the lower right of the main window.
If you have not saved the installation, the Save As dialog box appears. Save the
.INF file.

Mobile Device Package Editor Reference 11
Introduction to Mobile Device Package Editor
Note
The CabWiz program does not support UNC paths. To prevent compile errors caused
by UNC paths, save the .INF file to a local or mapped drive.
The Save Information dialog box appears.
2. Complete the dialog box:
Working Directory
Specify the directory in which to store the compiled files.
Cabwiz Directory
Specify the location of the Cabwiz.exe or cabwizSP.exe to use. Typically, you
should accept the default, unless you want to use a different version of CabWiz.
3. Click Build.
The compiled files are created in the location that you specified.
Product Documentation
This documentation assumes that you are proficient in the use of the Windows operating
system. If you need help using the operating system, consult its user documentation.
Use the following sources of information to learn about this product.
Online Help
The online help contains detailed technical information and step-by-step instructions for
performing common tasks.
Access help in the following ways:
zTo display context-sensitive help for the active window or dialog box, press F1.
zTo select a help topic from a table of contents, index, or search, select Help menu >
Help Topics.
Reference Manual
All the material in the online help is also available in a .PDF-format reference manual,
which you can access by selecting Help menu > Reference Manual.
Getting Started Guide
The Getting Started Guide contains system requirements and installation instructions.
You can access a .PDF version of the Getting Started Guide from the Windows Start
menu.
Release Notes
The product release notes cover new features, enhancements, bug fixes, and known
issues for the current version of this product. To access the release notes, select Release
Notes from the Symantec program group on the Windows Start menu.

Mobile Device Package Editor Reference 12
Chapter 2
Creating Installations for Mobile Devices
This chapter includes the following topics:
zAbout Installation Expert in Mobile Device Package Editor on page 12
zDefining Application Information on page 12
zAbout Multiple Device Support on page 13
zEntering Platform Information on page 15
zFiles Page on page 16
zAdding Registry Entries on page 18
zDefining Shortcuts on page 19
About Installation Expert in Mobile Device Package
Editor
Installation Expert lets you create and edit mobile device installations and provides an
easy-to-use, task-oriented user interface to perform the most common installation
tasks. Each page of Installation Expert lets you configure a specific aspect of your
installation.
In Installation Expert, the pages are organized into logical groups and listed in the order
in which you usually use them.
For advanced customization, you can edit the .INF directly within the Mobile Device
Package Editor. Changes that you make in Installation Expert are automatically reflected
in the .INF file, and vice versa. To display the INF Editor, click the INF Editor tab at the
lower left of the main window.
Defining Application Information
Use the Application Information page to enter information about this mobile device
installation.
In Mobile Device Package Editor, select Installation Expert > Application Information and
complete the page:
zApplication Name
Enter the name of the application you are installing. This name appears in the
desktop computer’s mobile device software (the Add/Remove Programs dialog box,
accessible from the Microsoft ActiveSync window).
zCompany Name
Enter the name of the company that developed the application. This further
describes the application to the end user during installation.

Mobile Device Package Editor Reference 13
Creating Installations for Mobile Devices
zDevice Installation Directory
Select or create a directory in which to store files on the mobile device. To create a
directory, select a directory and add the name of your directory at the end.
(Example: select \Program Files and then type \MyDirectory at the end.)
zApplication Type
The Microsoft® Windows Mobile™ platform supports Pocket PC and Smartphone
devices. This option determines which CabWiz program is used to compile the
installation.
Pocket PC
Uses Cabwiz.exe.
Smartphone
Uses CabwizSP.exe.
About Multiple Device Support
¾Pocket PC applications only.
The Microsoft® Windows Mobile™ platform supports Pocket PC and Smartphone
devices. Both the Pocket PC and Smartphone operating systems are based on Windows
CE, and are very similar except for their platform and processor support. Smartphone
only supports Smartphone devices, but Pocket PC is compatible with many different
platforms and processors. Therefore, when you create a Pocket PC installation, you can
specify additional platform and processor information. A single .CAB file can install to
only one platform-processor combination. An installation that supports multiple
platforms and processors requires multiple .CAB files. At run time, the mobile device
installation queries the connected mobile device for its platform and processor, and then
runs the .CAB file that has support for that system.
A single .INF file can contain information to produce multiple .CAB files for installation on
multiple platforms. The platform-specific information is identified in the CEDevice
section of the .INF file. In Mobile Device Package Editor, you provide the information for
the CEDevice section by defining devices on the Device Support page.
See Defining Device Support on page 14.
Every installation contains a Default device. If an application is platform-independent,
then you can add all the application’s resources to the Default device. Compiling the
installation creates a single .CAB file that can install the application on any platform.
If an application contains resources that are platform-dependent, you can define
multiple devices within a single installation project, and assign the platform-specific
resources to the appropriate device. Compiling the installation creates a separate .CAB
file for the Default device and for each additional device that you defined.
The resources that you add to the Default device are included in every .CAB that is
compiled from the installation. Resources that you add to a specific device are included
in the .CAB file for that device only.
Example: An application, named Sample, contains three devices: Default, Device1, and
Device2.

Mobile Device Package Editor Reference 14
Creating Installations for Mobile Devices
About the Current Device Drop-Down List
The Current Device drop-down list is populated with the devices that you define on the
Device Support page. To add a resource to a specific device, select it from the Current
Device drop-down list before you add the resource to the installation.
Defining Device Support
¾Pocket PC applications only.
The buttons on this page are not available for Smartphone applications.
If an application contains resources that are platform-dependent, you can define
multiple devices within a single installation project, and assign the platform-specific
resources to the appropriate device. Use the Device Support page to define devices for
an installation.
The devices that you define on the Device Support page populate the Current Device
drop-down list that appears on the Files, Registry, and Shortcuts pages.
Every installation contains a Default device. You can edit the Default device but you
cannot delete or rename it.
When you delete a device, all resources that have been added to that device are deleted
from the installation.
To define a device:
In Mobile Device Package Editor, select Installation Expert > Device Support page, click
Add, and complete the Device Support dialog box:
zDevice Name
Enter a unique name to describe this device. Do not use spaces. The device name
becomes part of the compiled .CAB file name.
zProcessor Supported
The .INF file identifies target CPUs by a processor type. Select the processor with
which this device is compatible, or select All.
When you add these files to
each device The compiled .CABs contain these files
Default
File_A
File_B
Sample.Default.CAB
File_A
File_B
Device1
File_C_1
Sample.Device1.CAB
File_A
File_B
File_C_1
Device2
File_C_2
Sample.Device2.CAB
File_A
File_B
File_C_2

Mobile Device Package Editor Reference 15
Creating Installations for Mobile Devices
Note
All Pocket PC devices are based on the ARM4 family of central processing units.
zPlatforms Supported
Select one or more platforms that are supported by this device.
The new device appears in the list. To edit it, select it and click Details.
See also:
For information about platforms, processors, and versions, search for “Processor Types
and Platforms” in the MSDN Library (msdn.microsoft.com/library)
Entering Platform Information
Use the Platform Information page to define version and build information for the mobile
device platforms that are supported by each device in the installation. Also specify the
Setup.dll file to use, if any.
To enter platform information:
In Mobile Device Package Editor, select Installation Expert > Platform Information and
complete the page.
If you have defined multiple devices for a Pocket PC application, click a device in the
Device list to enter information for that device.
zMinimum Version, Maximum Version
Enter the minimum and maximum versions of the platform that the application runs
on. When the application is installed on a mobile device, it queries the mobile
device’s system and verifies that it is supported according to the versions you enter
on this page. If you specify a minimum version, you must also specify a maximum
version. To indicate that the application runs on any version higher than the
minimum, enter 100 as the maximum.
(Pocket PC application only.) The versions are pre-filled according to the Windows
CE version of the platform you selected for the device. If the device supports
multiple platforms, the minimum version is the earliest of any of the platforms and
the maximum version is the latest of any of the platforms.
zMinimum Build, Maximum Build
(Optional.) If you specify a minimum build, you must also specify a maximum build,
but you can specify a maximum build by itself. Builds are intermediate releases
between major releases. Example: the full platform version might be 2.1.03. In this
case, 2.1 is the version number and the build is .03.
zSetup.dll Path
(Optional.) Specify the Setup.dll to include with this device’s installation. The
Setup.dll is executed during installation and lets you perform custom operations
during installation and removal of the application. For information on how to create
this file, refer to the Microsoft Pocket PC or Smartphone SDK documentation, or
search for “Setup.dll” in the MSDN Library (msdn.microsoft.com/library).
See also:

Mobile Device Package Editor Reference 16
Creating Installations for Mobile Devices
Defining Device Support on page 14
For information about platforms, processors, and versions, search for “Processor Types
and Platforms” in the MSDN Library (msdn.microsoft.com/library)
Files Page
On the Files page, you specify the directories and files to be installed on the mobile
device.
Files page in Mobile Device Package Editor
About Installation Directories
The My Documents, Program Files, and Windows directories represent the corresponding
directories on the mobile device.
The Windows directory represents the system directory (regardless of its actual name)
on the mobile device. Some standard directories are already created under Windows,
such as System32 and Fonts. To create a subdirectory of the system directory, create it
under the Windows directory.
The Device Installation Directory that you specified on the Application Information
page also appears here.
Working with the Files Page
z(Pocket PC applications only.) If the installation supports multiple devices, specify
the device you are configuring by selecting it from the Current Device drop-down
list.
zUse the right-click menu to expand or collapse the directory structure.
zDrag directories or files from the upper list boxes to the lower list boxes.
zUse the following buttons:
Add Contents
Add an entire directory and its contents to the installation.
Files in the
directoryselected
on the left.
Directories
available to
your computer.
Directories to
be installed on
the mobile
device.
Files to be
installed on the
mobile device
Current Device
drop-down list.

Mobile Device Package Editor Reference 17
Creating Installations for Mobile Devices
Add File
Add files to the directory that is selected in the lower-left list box.
See Adding Files to a Mobile Device Installation on page 17.
New Folder
Create directories to be installed on the mobile device.
Delete Folder
Remove a directory from the installation. This does not delete the folder from
the mobile device.
Delete File
Remove a file from the installation. This does not delete the file from the mobile
device.
Details
View and edit details about a file, including error handling, replacement options,
shared .DLL count, and self-registration.
See Editing File Details on page 17.
Adding Files to a Mobile Device Installation
A mobile device installation must contain files. Trying to compile an empty .CAB results
in a compile error.
To add files to a mobile device installation
1. In Mobile Device Package Editor, select Installation Expert > Files page.
2. (Pocket PC applications only.) From Current Device, select a device. Resources
that you add to a specific device are included in the .CAB file for that device only. If
you select All, the resources are installed to all of the devices that are defined for
this installation.
3. If the directory where the file is to be added is not listed in the lower-left list box:
a. Select the directory under which the new directory should be created.
b. Click New, enter a directory name, and click OK.
The directory you specify will be created on the mobile device if it does not exist.
4. In the lower-left list box, select the directory to which the file will be added.
5. In the upper list boxes, navigate to a file and double-click it or drag it to the lower-
right list box. You can select multiple files.
The file is added to the selected directory and appears in the lower-right list box.
Editing File Details
When you add a file to an installation, it inherits the attributes of the original file. If you
edit the attributes of a file in an installation, the file reflects your edits when installed on
the mobile device.
To edit file details
1. In Mobile Device Package Editor, select Installation Expert > Files page.
2. Double-click a file in the lower-right list box.

Mobile Device Package Editor Reference 18
Creating Installations for Mobile Devices
The File Details dialog box appears.
3. Complete the dialog box:
Source Pathname
This is the full path of the file on your computer. To replace this file, specify a
new file.
Destination File Name
Enter the name for the file when it is installed on the mobile device.
File Copy Errors
Specify how the installation should respond if a file error occurs during the
installation of this file.
Skip silently if error occurs
Do not install this file and do not notify the end user if an error occurs.
Warn if attempting to skip
Warn the end user if an attempt is made to skip a file after an error occurs.
Do not allow file to be skipped
Do not allow the end user to skip copying a file.
Increment Shared .DLL Count
Mark this to increment the counter for this file (if it is a .DLL, .OCX, or .VBX) in
the registry of the mobile device. The shared .DLL counter prevents the file
from being uninstalled if any programs are still using it.
Self-Register File
Some files (examples: .OCXs and some .DLLs) support self-registration. Mark
this to have the file register itself in the registry of the mobile device.
Replace Existing File
Specify how the installation should respond if the file being installed is already
on the mobile device.
Install Only if File Already Exists
Mark this to install this file only if a file of the same name already exists in the
installation directory of the mobile device.
See also:
See Adding Files to a Mobile Device Installation on page 17
Adding Registry Entries
Use the Registry page to specify the registry entries to be created or edited on the
mobile device.
To add registry entries
1. In Mobile Device Package Editor, select Installation Expert > Registry page.
The left list box shows registry keys and the right list box shows the key values.
2. (Pocket PC applications only.) From Current Device, select a device. Resources
that you add to a specific device are included in the .CAB file for that device only. If
you select All, the resources are installed to all of the devices that are defined for
this installation.

Mobile Device Package Editor Reference 19
Creating Installations for Mobile Devices
3. To add a new key or value, click New Key.
The Registry Details dialog box appears:
4. Complete the dialog box:
Root
Select the parent key under which the new key will reside.
Key
Enter the name of the key to create or update. Create an entire key path by
separating key names with backslashes. (Example: Entering
NewDocument\Protocol\StdFileEditing creates the StdFileEditing key inside the
Protocol key, which is created inside the NewDocument key.) Any keys in the
path that do not exist are created.
Value Name
Enter the name of a new named value.
Data Value
The data you enter should be valid data for the Data Type you select below.
Press Ctrl+Enter to insert a carriage return.
Data Type
Select the type of data contained in the named value. Available types are:
String
(REG_SZ prefix.) An expandable string.
Multiple Strings
(REG_MULTI_SZ prefix.) Identifies a value entry as a multiple string. These
are multiple pieces of text, separated by carriage returns.
Binary/Hex
(REG_BINARY prefix.) A series of bytes in hexadecimal notation. Separate
the bytes with commas. Do not use the “0x” hexadecimal prefix.
Double Word
(REG_DWORD prefix.) Identifies a value entry as a 4-byte (DWORD) entry.
This must be a valid DWORD value.
Don’t Overwrite if Key Already Exists
Mark this to prevent this registry setting from overwriting the key value if it
already exists on the mobile device. Clear this to have this registry value
overwrite the existing key value.
5. Click OK.
After you add a registry entry, you can edit it by selecting the key name in the left list
box and double-clicking the value in the right list box.
Defining Shortcuts
The Shortcuts page lets you add, edit, and delete shortcuts for files in the installation.
The shortcuts appear on the mobile device.
To define shortcuts
1. In Mobile Device Package Editor, select Installation Expert > Shortcuts page.

Mobile Device Package Editor Reference 20
Creating Installations for Mobile Devices
2. (Pocket PC applications only.) From Current Device, select a device. Resources
that you add to a specific device are included in the .CAB file for that device only. If
you select All, the resources are installed to all of the devices that are defined for
this installation.
3. Click Add at the right of the page.
The Shortcut Details dialog box appears.
4. Complete the dialog box:
Source Pathname
Browse to the file in the installation to create a shortcut for. Only files that are
specified on the Files page are displayed. If you have defined multiple devices,
only files that are specified for the current device are displayed.
Shortcut Name
Enter a name for the shortcut. This defaults to the file name.
Shortcut Location
Enter or select the directory on the mobile device to contain the shortcut. The
drop-down list contains the most common locations for shortcuts on mobile
devices.
5. Click OK.
The new shortcut appears in the list. To edit it, select it and click Details.
See also:
Adding Files to a Mobile Device Installation on page 17