About Windows Mobile Installations - Symantec WISESCRIPT PACKAGE EDITOR 7.0 SP2 - FOR WISE INSTALLATION STUDIO V1.0 Installation Manual

About Windows Mobile Installations

WiseScript Package Editor Reference
Update Filename
Enter a name for the WiseUpdate update file. This file, which resides in the host
directory, is a text file in .INI format that the WiseUpdate client reads to determine
if a new version exists, and if so, where the new version and its ReadMe can be
found. You must use the same file name when you use WiseUpdate in the future
(example: WiseUpdate.INI).
See About the WiseUpdate Update File
Product Version
Enter the version of the current installation. This version will be stored in the
configuration file specified in Update Filename.
Check Interval (days)
This works in conjunction with the Add client to Startup Group check box (see
below). Enter the number of days between update reminders for the end user.
Alternate Web Page
Enter the location of a Web page to display if the WiseUpdate client cannot check for
updates or download the installation. Examples: A page with technical support,
upgrade information, or troubleshooting.
Start Menu Icon
Enter a name for a shortcut to the WiseUpdate Client, which appears in the Windows
Start menu, giving end users the ability to check for updates. To communicate the
shortcut's purpose, give it a descriptive name, such as "Update Productname." If
this is left blank, mark Add client to Startup Group so that the WiseUpdate Client
runs automatically.
Add client to Startup Group
Mark this to add a shortcut for the WiseUpdate Client to the Windows Startup group.
The WiseUpdate Client runs silently every time the destination computer is restarted
or the end user logs into Windows. If the Check Interval time has not been
reached, is simply runs silently, checks the time interval, and quits. However, after
the number of days in Check Interval elapse, instead of running silently and
quitting, it runs with its normal interface and prompts the end user to check for
updates.
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 .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.
on page 91.
WiseScript Actions
101