You can create a new package or modify an existing
package. There are three types of Pocket PC packages, and a
different method for creating each.
Table 1-1 describes the three types of
Pocket PC packages.
Table 1-1 Types of Pocket PC
packages
Package type
|
Description
|
File-based install
|
The package installs the files that you
choose to include in it. When the package is executed on the
managed Pocket PC, the files are copied to the appropriate
locations, appropriate shortcuts are created, and registry values
are set.
You can also use this method to create a
Configuration package. A Configuration package may contain no
files, but executing it modifies the registry settings on the
managed Pocket PC.
|
CAB-based install
|
The package uses an existing Pocket PC
CAB-based install file provided by a software vendor. The CAB file
is included in the package.
When the package is executed on the managed
Pocket PC, it runs the install file to install the
application.
|
CAB unpacked to a file-based install
|
The package uses an existing Pocket PC
CAB-based install file provided by a software vendor. The CAB file
is unpacked and its component files are included in the
package.
When the package is executed on the managed
Pocket PC, the files are copied to the appropriate locations.
|
Note: CAB files are Pocket PC installation files
that are provided by application vendors. For information on
locating and identifying the files that you need to create a Pocket
PC package, see Locating and identifying CAB files.
When you deploy a package that uses a CAB file to
a Pocket PC, the installed application appears in the System/Remove
Programs utility on the Pocket PC device. This lets the user of the
device remove the application from the Pocket PC without
administrator action. If you want to prevent the user from being
able to remove an application in this way, you should use a
file-based install package.
When you modify a package, you need to be aware of
the following:
- If you change the package ID, you are creating a new
package.
- You cannot replace a package that is already assigned to a
managed Pocket PC.
Before you add the modified package
to the Package Depot, you need to remove the original package from
all Pocket PCs on which it is installed. When you have done this,
you can add the modified package to the database and reassign the
package to Pocket PCs.
To create a new package
1.
|
|
Click one of the following:
|
Create a new package
|
Create a package to install the files that
you choose to include in the package.
Choose this option if you want to create a
Configuration package that does not include any files. You can use
package properties and administration parameters to set registry
values.
|
Create a new package (using a CAB file as a
template)
|
Create a package that uses an existing
Pocket PC CAB-based install file provided by a software
vendor.
|
2.
|
|
If you are creating a package from a CAB file,
in the Full pathname to the CAB file box, specify the appropriate
CAB file.
|
You can type the full path and name
of the CAB file, or click ... to open the
Select a CAB file to include window and select the appropriate
file.
3.
|
|
If you want to unpack the CAB file to create a
file-based install package, uncheck Use this CAB
file during the install (instead of unpacking contents).
|
4.
|
|
Click Next.
|
To modify an existing package
1.
|
|
Click Modify a previously
created package.
|
2.
|
|
In the Full pathname to the PAK file box,
specify the appropriate PAK file.
|
You can type the full path and name
of the PAK file, or click ... to open the
Select a PAK file to modify window and select the appropriate
file.
3.
|
|
Click Next.
|