Cab file does not install when downloaded in an AirBEAM Package

Article ID: 09866750

Symptom

Cab file does not install when downloaded in an AirBEAM Package

Facts

MC90xx, MK20xx, MK1150, PPT88xx, MC50xx, PPT28xx, PDT81xx

Root Cause

Improper use AirBEAM when downloading Cab file.

Resolution

Setup theAirBEAMPackage to install a Cab file.
  1. Create an application specific registry file to reset the “installed” registry flag.
The installation of a CAB file creates a registry entry that indicates the application has been installed.  The presence of this registry flag will cause the wceload utility to prompt the end-user when the application is updated.  This prompt can be avoided by resetting the registry setting that indicates the application has been installed.  The registry setting can be reset by downloading a .REG file that contains the following lines:

[HKEY_LOCAL_MACHINE\SOFTWARE\Apps\provider appname]

"Instl"=dword:00000000


The provider and appname values are defined in CAB file’s .INF file.  If this information is unavailable, the Microsoft remote registry editor can be used to determine the registry setting after the CAB file has been installed.
  1. Create an installation “flag” file
Generally, CAB files install the application into the \windows directory, which is in volatile RAM.  The contents of the \windows directory are lost after a cold boot.  The AirBEAM alternate storage logic can be used to recognize when volatile components of the application have been lost due to a cold boot. 

In order to enable the AirBEAM alternate storage logic, an installation “flag” file is downloaded into the \windows directory as part of the AirBEAM package.  If the device is cold booted the AirBEAM client logic will recognize that this component is missing and will automatically re-load the package.  The .CAB file cannot be used to recognize when a cold boot has occurred because the .CAB file is automatically deleted by the wceload utility after the application is installed.

The contents of the “flag” file are unimportant.  Generally the “flag” file is a small text file that can be created using Notepad or a text editor.  The AirBEAM client simply verifies that the file exists.

The “flag” file should have the same name as the package and have a .FLG file extension:

\windows\package.flg
  1. Create a shortcut file if the application is to be automatically launched by the AirBEAM client
If AirBEAM is to automatically launch the installed application a shortcut file must be downloaded to the \Application directory.  The shortcut file should be configured to launch the installed application’s executable.  The shortcut file must have the same name as the AirBEAM package:
 
\Application\package.lnk
 
  1. Add the package component files to the AirBEAM package
----------------------
Use the package builder to add the various component files to the AirBEAM package.  The AirBEAM package will generally include the following files:
appname.cab
--------------------------
This component is the application’s CAB file.

This component should be downloaded to the \windows directory.  The component’s delete after install attribute must be set in order for the alternate storage logic to work correctly.
------------------------------
package.lnk

------------------------------
This component is the package’s shortcut, which is used by AirBEAM to launch the application.

This component should be downloaded to the \Application directory.

-----------------------------------------------
package.flg

------------------
This component is the application’s “flag” file.

This component should be downloaded to the \windows directory.  The component’s delete after install attribute must NOT be set in order for the alternate storage logic to work correctly.
------------------------

package.reg
-------------------------------
This component is the .REG file used to reset the “installed” registry setting.

This component should be downloaded to the \Application directory.
  1. Configure the AirBEAM package’s install command
The package’s install command is used to invoke the wceload utility to install the downloaded CAB file:

\windows\wceload \windows\appname.cab 
  1. Configure the AirBEAM package’s alternate storage setting
The package’s alternate storage setting is configured to indicate part of the package is stored in alternate storage.  This setting will cause the AirBEAM client to test for the loss of package components during the boot processing.

\windows\
  1. Configure the AirBEAM package to automatically soft reset
The package specifies a soft reset in order to force the downloaded .REG file to be processed.

 
    Document Name/Location Description
    MCD-00116.zip Download Files>> Installing Cab Files